← Back to home
Comparison · Infra & APIs

BAS vs states

A side-by-side editorial comparison of BAS and states — release velocity, themes, recent moves, and the top alternatives to consider.

BAS vs states: at a glance

FeatureBASstates
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, model-averaging, mcmc, r-packagepolitical-science, panel-data, country-codes, datasets
Last editorial update1h ago40m ago
WebsiteVisit →Visit →

What is BAS?

A Bayesian model-averaging package spending its 2.0 on memory, not methods.

BAS performs Bayesian variable selection and model averaging for linear and generalized linear models, sampling from a model space too large to enumerate. The visible history splits cleanly: 2023-2024 added sampling machinery — an adaptive independent MCMC sampler with Horvitz-Thompson estimation, hereditary-constraint counting — while 2.0.0 in late 2025 reworked how sampler output is allocated in C. The 2.0.2 patch is a PROTECT fix for rchk warnings.

Read the full BAS trajectory →

What is states?

State-panel tooling holding steady since its 2020 data and ergonomics release.

states supplies the Gleditsch & Ward and Correlates of War state lists and the tooling to turn them into country-year or country-month panels, with plot_missing() for coverage checks. The substantive work landed in 2020; the releases since are compatibility fixes against ggplot2, dplyr, readr and testthat. The most recent entry is a single test repair.

Read the full states trajectory →

BAS vs states: editorial side-by-side

B
BAS
INFRA · APIS
0.0

A Bayesian model-averaging package spending its 2.0 on memory, not methods.

◆ Current state

BAS performs Bayesian variable selection and model averaging for linear and generalized linear models, sampling from a model space too large to enumerate. The visible history splits cleanly: 2023-2024 added sampling machinery — an adaptive independent MCMC sampler with Horvitz-Thompson estimation, hereditary-constraint counting — while 2.0.0 in late 2025 reworked how sampler output is allocated in C. The 2.0.2 patch is a PROTECT fix for rchk warnings.

◆ Where it's heading

Memory is the binding constraint and the releases say so directly. The hereditary-constraint counter, the GROW option, and the replacement of over-allocation with resizing all attack the same problem: n.models is a guess, and guessing high wastes memory on problems where few unique models are actually visited. The 2.0.0 work was additionally forced by R tightening its C API against non-API calls like SETLENGTH, a constraint every C-heavy CRAN package has been absorbing. Method development has been quiet since 1.7.x.

◆ Prediction

The 1.7.5 notes call the hereditary-constraint counting a first step and say future updates will cover other constraint types, including polynomials, which remain unhandled. That is the one concrete commitment in this history, though nothing since has returned to it.

S
states
INFRA · APIS
0.0

State-panel tooling holding steady since its 2020 data and ergonomics release.

◆ Current state

states supplies the Gleditsch & Ward and Correlates of War state lists and the tooling to turn them into country-year or country-month panels, with plot_missing() for coverage checks. The substantive work landed in 2020; the releases since are compatibility fixes against ggplot2, dplyr, readr and testthat. The most recent entry is a single test repair.

◆ Where it's heading

The package has reached the point where its own data and API are settled and the release trigger is upstream churn in the tidyverse. What movement there is goes toward making the two state lists interchangeable, with the microstates coding carried from G&W onto the COW data as the clearest example, rather than toward new datasets.

◆ Prediction

The next release is most likely another compatibility pass; a data refresh would be the signal that the package is active again.

Alternatives to BAS and states

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either BAS or states.

See all BAS alternatives → · See all states alternatives →

Recent activity from BAS and states

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 8mo agoBASBAS 2.0.2
  2. 8mo agoBASBAS 2.0.0
  3. 0y agostatesplot_missing() test fixed for the next ggplot2
  4. 1y agoBASBAS 1.7.5
  5. 1y agoBASBAS 1.7.3
  6. 1y agoBASBAS 1.7.2
  7. 2y agoBASBAS 1.7.1
  8. 2y agostatesggplot2 and dplyr deprecation cleanup
  9. 2y agostatesBundled state data stripped to plain data frames
  10. 5y agostatesMicrostate coding for COW data and state_panel() shortcuts
  11. 7y agostatesSimpler defaults for state_panel() and plot_missing()

Frequently asked questions

What is the difference between BAS and states?

They serve adjacent needs but don't currently overlap on shipped themes. BAS and states are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is BAS better than states?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BAS and states are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to BAS?

Top BAS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BAS alternatives" section above for the current picks, or visit /alternatives/bas for the full list with editorial commentary on each.

What are the best alternatives to states?

Top states alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "states alternatives" section above for the current picks, or visit /alternatives/states for the full list with editorial commentary on each.