bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Comparison · Infra & APIs
adjustedCurves vs OptimalBinningWoE
A side-by-side editorial comparison of adjustedCurves and OptimalBinningWoE — release velocity, themes, recent moves, and the top alternatives to consider.
adjustedCurves vs OptimalBinningWoE: at a glance
What is adjustedCurves?
A survival curve package spending release after release correcting its own estimates
adjustedCurves computes confounder-adjusted survival and cumulative incidence curves across a range of estimators - IPTW, AIPTW, Aalen-Johansen, direct standardisation - with support for multiple imputation and bootstrapping. The recent releases are dominated by corrections to numbers the package already reported. Version 0.11.4 fixed cumulative incidence estimates under method="aalen_johansen" that were being read one time step early, which the maintainer notes could differ substantially when events are few, and added risk and event counts to the ggsurvplot conversion including correctly pooled values under multiple imputation.
What is OptimalBinningWoE?
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.
adjustedCurves vs OptimalBinningWoE: editorial side-by-side
adjustedCurves
0.0INFRA · APIS
A survival curve package spending release after release correcting its own estimates
◆ Current state
adjustedCurves computes confounder-adjusted survival and cumulative incidence curves across a range of estimators - IPTW, AIPTW, Aalen-Johansen, direct standardisation - with support for multiple imputation and bootstrapping. The recent releases are dominated by corrections to numbers the package already reported. Version 0.11.4 fixed cumulative incidence estimates under method="aalen_johansen" that were being read one time step early, which the maintainer notes could differ substantially when events are few, and added risk and event counts to the ggsurvplot conversion including correctly pooled values under multiple imputation.
◆ Where it's heading
Multiple imputation is the recurring fault line. The standard error pooling formula was implemented incorrectly until 0.11.2, then fixed again in 0.11.3 for the bootstrapping-plus-imputation combination, and 0.11.4 added the pooled risk table values that had previously been omitted entirely. A separate thread quietly removed capability: tmle and ostmle methods went in 0.10.0, and tmle support was pulled again in 0.11.1 after the concrete package left CRAN. Feature work does happen - risk tables, contrast arguments, the extend_to_last control on IPTW curves - but it is outweighed by correction.
◆ Prediction
Expect continued estimator-level corrections rather than new methods, and a possible return of tmle support if its upstream dependency returns to CRAN, since the removal was described as temporary.
OptimalBinningWoE
2.5INFRA · APIS
OptimalBinningWoE spent two releases auditing a C++ engine that was crashing R sessions.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to adjustedCurves and OptimalBinningWoE
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 adjustedCurves or OptimalBinningWoE.
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.
finnts
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all adjustedCurves alternatives → · See all OptimalBinningWoE alternatives →
Recent activity from adjustedCurves and OptimalBinningWoE
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoOptimalBinningWoEv1.11.0 — Runtime audit: crash, hang, data-loss and reproducibility fixes
- 3mo agoOptimalBinningWoEv1.10.0 — C++ Engine Audit & Hardening
- 5mo agoOptimalBinningWoECRAN fix: proper C++ stack unwinding in error paths
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 6mo agoOptimalBinningWoEFixes LTO link errors from One Definition Rule violations
- 6mo agoOptimalBinningWoERemoves sketch binning cache while chasing UBSAN errors
- 1y agoadjustedCurvesIPTW curves can now extend to the last observed time
- 2y agoadjustedCurvesDropped arguments and a wrong multiple-imputation pooling formula
- 2y agoadjustedCurvesRisk tables, contrast consolidation and faster bootstrapping
- 3y agoadjustedCurvestmle and ostmle methods dropped
- 3y agoadjustedCurvesDependency compatibility and installation documentation
Frequently asked questions
What is the difference between adjustedCurves and OptimalBinningWoE?
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.
Is adjustedCurves better than OptimalBinningWoE?
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.
What are the best alternatives to adjustedCurves?
Top adjustedCurves alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "adjustedCurves alternatives" section above for the current picks, or visit /alternatives/adjustedcurves for the full list with editorial commentary on each.
What are the best alternatives to OptimalBinningWoE?
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.