HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of BayLum and bsvarSIGNs — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
bsvarSIGNs estimates structural vector autoregressions identified by sign, zero and narrative restrictions, with the sampler in C++ and the objects, workflows and code structure deliberately matched to the bsvars package. Since the 1.0 launch in mid-2024 the releases have been consolidation: a fix pass, then a vignette, citation metadata and C++ changes to stay ahead of an upcoming compiler check.
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.
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.
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.
bsvarSIGNs estimates structural vector autoregressions identified by sign, zero and narrative restrictions, with the sampler in C++ and the objects, workflows and code structure deliberately matched to the bsvars package. Since the 1.0 launch in mid-2024 the releases have been consolidation: a fix pass, then a vignette, citation metadata and C++ changes to stay ahead of an upcoming compiler check.
The package launched with a published roadmap and the stated intention of intensive development, then spent its next two releases on documentation and compliance rather than new identification schemes. The 2.0 version number is not matched by the changes described under it. What the feed shows is a methods package settling in after launch, not one expanding.
The roadmap referenced at launch is the only stated plan, and the entries since do not say which part of it is next.
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 bsvarSIGNs.
France's national flood statistics, ported out of Fortran and into R.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
A column-key toolkit for stitching decades of ecological field data into one table.
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all BayLum alternatives → · See all bsvarSIGNs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — bayesian-statistics, r-package — within Infra & APIs. BayLum and bsvarSIGNs 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BayLum and bsvarSIGNs 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.
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.
Top bsvarSIGNs alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bsvarSIGNs alternatives" section above for the current picks, or visit /alternatives/bsvarsigns for the full list with editorial commentary on each.