← Back to home
Comparison · Infra & APIs

BayLum vs simDAG

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

Shared themes:r-package

BayLum vs simDAG: at a glance

FeatureBayLumsimDAG
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesbayesian-statistics, luminescence-dating, geochronology, jagsr-package, causal-inference, dag-simulation, discrete-event-simulation
Last editorial update30m ago3h 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 simDAG?

simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.

simDAG generates data from directed acyclic graphs, with a library of node types covering Gaussian, binomial, Poisson, negative binomial, zero-inflated, ordered regression, Cox, and Aalen models. The 1.0.0 milestone opened node_cox() to arbitrary baseline hazard functions, which lets continuous time-dependent hazards drive discrete-event simulations. The two most recent releases exist only to keep the package on CRAN through breakage in lme4 and simr.

Read the full simDAG trajectory →

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

S
simDAG
INFRA · APIS
2.5

simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.

◆ Current state

simDAG generates data from directed acyclic graphs, with a library of node types covering Gaussian, binomial, Poisson, negative binomial, zero-inflated, ordered regression, Cox, and Aalen models. The 1.0.0 milestone opened node_cox() to arbitrary baseline hazard functions, which lets continuous time-dependent hazards drive discrete-event simulations. The two most recent releases exist only to keep the package on CRAN through breakage in lme4 and simr.

◆ Where it's heading

The package has been widening what a simulation can represent rather than deepening any one node. Networks arrived in 0.4.0 so individuals could depend on each other, discrete-event simulation in continuous time arrived in 0.5.0 as an alternative to the discrete-time engine, and 1.0.0 connected the two by letting continuous hazards feed the event-driven path. Alongside that, node types keep accumulating for outcome families the framework could not previously generate.

◆ Prediction

Expect the node library to keep expanding into outcome types the discrete-event engine can now support, though the recent releases suggest upstream dependency churn will keep consuming release slots.

Alternatives to BayLum and simDAG

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

See all BayLum alternatives → · See all simDAG alternatives →

Recent activity from BayLum and simDAG

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

  1. 18d agosimDAGCRAN-retention patch for upstream lme4 breakage
  2. 3mo agosimDAGArbitrary baseline hazards connect node_cox() to discrete-event sims
  3. 4mo agosimDAGTest-only fix for an upstream simr update
  4. 5mo agosimDAGAdds node_polr() for ordinal outcomes and rsurv node support
  5. 7mo agosimDAGAdds continuous-time discrete-event simulation
  6. 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
  7. 10mo agosimDAGAdds link functions to node types and fixes a broken seed default
  8. 2y agoBayLumOne data-file function and a YAML config replace the folder layout
  9. 3y agoBayLumMCMC memory halved; density plots for age distributions
  10. 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
  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 simDAG?

Both compete on the same themes — r-package — within Infra & APIs. simDAG is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is BayLum better than simDAG?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. simDAG is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 simDAG?

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