← Back to home
Comparison · Infra & APIs

BayLum vs estimatr

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

Shared themes:r-package

BayLum vs estimatr: at a glance

FeatureBayLumestimatr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, luminescence-dating, geochronology, jagscausal-inference, experiments, robust-standard-errors, econometrics
Last editorial update58m ago54m ago
WebsiteVisit →Visit →

What is BayLum?

Bayesian luminescence dating that finally replaced its folder-structure input format.

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

Read the full BayLum trajectory →

What is estimatr?

Fast design-based estimators for experiments, coasting on CRAN patches.

estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.

Read the full estimatr trajectory →

BayLum vs estimatr: editorial side-by-side

B
BayLum
INFRA · APIS
0.0

Bayesian luminescence dating that finally replaced its folder-structure input format.

◆ Current state

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

◆ Where it's heading

Two long-running threads have converged: making JAGS runs survivable (parallel methods, halved MCMC memory, injectable custom models) and making the inputs survivable (YAML config, consistency checks, auto-detected sample names). With the deprecated generators on their way out, the next phase is removal rather than addition. Release cadence is roughly annual and slowing.

◆ Prediction

The deprecated Generate_DataFile(), Generate_DataFile_MG() and LT_RegenDose() are the obvious next casualties; a release that drops them would be the first breaking change since the YAML rework.

E
estimatr
INFRA · APIS
0.0

Fast design-based estimators for experiments, coasting on CRAN patches.

◆ Current state

estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.

◆ Where it's heading

Direction cannot be read from this feed. The release notes are unedited merge-commit messages, so the only signal is cadence — roughly annual, each release framed as a CRAN patch rather than as feature work. That pattern is consistent with a package whose estimators are considered finished and which now moves only when CRAN policy requires it.

◆ Prediction

On the evidence here the next release is another CRAN compliance patch, but the notes are too thin to support a confident read of what the maintainers are actually working on.

Alternatives to BayLum and estimatr

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 BayLum or estimatr.

See all BayLum alternatives → · See all estimatr alternatives →

Recent activity from BayLum and estimatr

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

  1. 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
  2. 1y agoestimatrCRAN version 1.0.4
  3. 2y agoBayLumOne data-file function and a YAML config replace the folder layout
  4. 2y agoestimatrCRAN version 1.0.2
  5. 3y agoestimatrCRAN version 1.0.0
  6. 3y agoBayLumMCMC memory halved; density plots for age distributions
  7. 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
  8. 4y agoBayLumCustom model injection and RNG control for parallel runs
  9. 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data

Frequently asked questions

What is the difference between BayLum and estimatr?

Both compete on the same themes — r-package — within Infra & APIs. BayLum and estimatr 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 BayLum better than estimatr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BayLum and estimatr 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 BayLum?

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

What are the best alternatives to estimatr?

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