bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
A side-by-side editorial comparison of HydroPortailStats and OptimalBinningWoE — release velocity, themes, recent moves, and the top alternatives to consider.
France's national flood statistics, ported out of Fortran and into R.
HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.
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.
HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.
The package started as a straight extraction of the portal's existing functions and is now absorbing the surrounding legacy toolchain: HBay was a separate compiled program with its own config files, and this release brings both the method and its configuration format inside R. Releases are sparse — three in two years, with an eighteen-month gap before the latest — and the intervening one was CRAN paperwork.
The HBay import came with a configuration-file reader for continuity with the old executable, which suggests further legacy hydrological tooling could follow the same path; the entries name no specific next target.
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 HydroPortailStats or OptimalBinningWoE.
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.
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all HydroPortailStats 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 HydroPortailStats alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HydroPortailStats alternatives" section above for the current picks, or visit /alternatives/hydroportailstats 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.