← Back to home
Comparison · Infra & APIs

BayLum vs ggdist

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

Shared themes:bayesian-statisticsr-package

BayLum vs ggdist: at a glance

FeatureBayLumggdist
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, luminescence-dating, geochronology, jagsdata-visualization, uncertainty, bayesian-statistics, ggplot2
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 ggdist?

The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.

ggdist supplies ggplot2 with a compositional vocabulary for distributions — slabs, intervals, dotplots and the sub-geometries that combine them. The last three years moved it from a drawing library to an estimation library: bounded density estimation with Sheather-Jones bandwidth became the default, weights propagate through every density, interval and point summary, and blurred dotplots render Monte Carlo standard error as visual fuzz. The 2025 release rounds this out with per-geometry thickness subscales and settable global defaults.

Read the full ggdist trajectory →

BayLum vs ggdist: 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.

G
ggdist
INFRA · APIS
0.0

The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.

◆ Current state

ggdist supplies ggplot2 with a compositional vocabulary for distributions — slabs, intervals, dotplots and the sub-geometries that combine them. The last three years moved it from a drawing library to an estimation library: bounded density estimation with Sheather-Jones bandwidth became the default, weights propagate through every density, interval and point summary, and blurred dotplots render Monte Carlo standard error as visual fuzz. The 2025 release rounds this out with per-geometry thickness subscales and settable global defaults.

◆ Where it's heading

Two threads run in parallel and keep converging. One is statistical: pluggable density estimators arrived first, then became the default, then gained weights and quantile histograms. The other is compositional: sub-geometries acquired their own guides, then their own scales, so a slab's thickness axis is now a first-class annotated dimension. Cadence has stretched from twice-yearly to roughly annual, with the recent work tightening existing surface rather than opening new.

◆ Prediction

Subguides gained subscales a release later, so the remaining asymmetry is in the sub-geometry system rather than the statistics; expect the next release to continue that fill-in work.

Alternatives to BayLum and ggdist

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 ggdist.

See all BayLum alternatives → · See all ggdist alternatives →

Recent activity from BayLum and ggdist

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

  1. 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
  2. 1y agoggdistPer-geometry thickness subscales and settable defaults
  3. 2y agoBayLumOne data-file function and a YAML config replace the folder layout
  4. 2y agoggdistBlurred dotplots draw Monte Carlo error; weights reach every estimator
  5. 2y agoggdistC++ dotplot binning and safer bandwidth fallbacks
  6. 3y agoggdistBounded density becomes the default; existing charts change
  7. 3y agoBayLumMCMC memory halved; density plots for age distributions
  8. 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
  9. 3y agoggdistCategorical distributions, hex layouts, pluggable density estimators
  10. 4y agoggdistComputed variables shared across sub-geometries
  11. 4y agoBayLumCustom model injection and RNG control for parallel runs
  12. 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data

Frequently asked questions

What is the difference between BayLum and ggdist?

Both compete on the same themes — bayesian-statistics, r-package — within Infra & APIs. BayLum and ggdist 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 ggdist?

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

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