HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
BayLum vs Luminescence
A side-by-side editorial comparison of BayLum and Luminescence — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:luminescence-datinggeochronologyr-package
BayLum vs Luminescence: at a glance
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.
What is Luminescence?
Luminescence is revisiting the statistical assumptions baked into its dose-response fits.
The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.
BayLum vs Luminescence: editorial side-by-side
BayLum
0.0INFRA · APIS
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.
Luminescence
2.5INFRA · APIS
Luminescence is revisiting the statistical assumptions baked into its dose-response fits.
◆ Current state
The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.
◆ Where it's heading
Two kinds of change dominate. The first is deliberate breaking changes made for correctness or consistency: the weighting rework, and import functions now uniformly appending the detector to record types so all formats behave as one always did. The second is a steady stream of new analysis functions contributed by the wider research community, covering crosstalk correction, spatial autocorrelation on grain discs, and incomplete bleaching models. Deprecated functions are being removed on a clear schedule rather than left indefinitely.
◆ Prediction
Expect further consolidation of defaults that were inherited rather than chosen, since the weighting change is framed as correcting earlier reasoning rather than adding an option.
Alternatives to BayLum and Luminescence
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 Luminescence.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
See all BayLum alternatives → · See all Luminescence alternatives →
Recent activity from BayLum and Luminescence
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
- 4mo agoLuminescenceFixes an uninitialised array and background overcounting
- 5mo agoLuminescenceImport functions now append detector type to record names
- 7mo agoLuminescenceAdds crosstalk correction, Moran's I, and dose-response fitting
- 7mo agoLuminescenceFixes baSAR reporting, fading input checks, and plot regressions
- 7mo agoLuminescenceAdds automatic background subtraction and record removal helpers
- 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
- 2y agoBayLumOne data-file function and a YAML config replace the folder layout ⚡
- 3y agoBayLumMCMC memory halved; density plots for age distributions
- 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
- 4y agoBayLumCustom model injection and RNG control for parallel runs
- 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data
Frequently asked questions
What is the difference between BayLum and Luminescence?
Both compete on the same themes — luminescence-dating, geochronology, r-package — within Infra & APIs. Luminescence 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 Luminescence?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Luminescence 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 Luminescence?
Top Luminescence alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Luminescence alternatives" section above for the current picks, or visit /alternatives/luminescence for the full list with editorial commentary on each.