HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of BayLum and OptimalBinningWoE — 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.
OptimalBinningWoE spent two releases auditing a C++ engine that was crashing R sessions.
The package wraps 37 binning algorithms in C++, and the last two releases have been dedicated audits of that engine rather than new functionality. The 1.11.0 runtime audit found a segmentation fault in categorical binning that killed the R session for any predictor with no more levels than max_bins — with the default of five, that covers sex, marital status, region, and education. Earlier releases were CRAN compliance patches.
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.
The package wraps 37 binning algorithms in C++, and the last two releases have been dedicated audits of that engine rather than new functionality. The 1.11.0 runtime audit found a segmentation fault in categorical binning that killed the R session for any predictor with no more levels than max_bins — with the default of five, that covers sex, marital status, region, and education. Earlier releases were CRAN compliance patches.
The engineering practice is visibly maturing: a static audit in 1.10.0, then a runtime audit in 1.11.0 driven by address and undefined-behaviour sanitizers, a degenerate-input stress harness, and a golden-output regression suite of roughly 3,200 comparisons, with every fix pinned by a test that fails on the prior version. No public API has changed across either release. The package is buying back trust in results that were silently wrong or unreproducible.
With the audit programme apparently complete across both static and runtime passes, the next release is more likely to resume feature work on the binning algorithms than to continue hardening.
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 OptimalBinningWoE.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
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.
See all BayLum alternatives → · See all OptimalBinningWoE alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OptimalBinningWoE 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OptimalBinningWoE 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.
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 OptimalBinningWoE alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OptimalBinningWoE alternatives" section above for the current picks, or visit /alternatives/optimalbinningwoe for the full list with editorial commentary on each.