HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
adjustedCurves vs bkmrhat
A side-by-side editorial comparison of adjustedCurves and bkmrhat — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
adjustedCurves vs bkmrhat: 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 bkmrhat?
A parallel-chain helper for bkmr that has settled into pure upkeep.
bkmrhat wraps Bayesian kernel machine regression (bkmr) so users can run and diagnose multiple MCMC chains in parallel, then combine or continue them. The functional surface has been stable since 2022, when chain-combining picked up a low-memory path and a seed-collision bug was corrected. The most recent release adds only diagnostic metadata to the package description.
adjustedCurves vs bkmrhat: 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.
bkmrhat
0.0INFRA · APIS
A parallel-chain helper for bkmr that has settled into pure upkeep.
◆ Current state
bkmrhat wraps Bayesian kernel machine regression (bkmr) so users can run and diagnose multiple MCMC chains in parallel, then combine or continue them. The functional surface has been stable since 2022, when chain-combining picked up a low-memory path and a seed-collision bug was corrected. The most recent release adds only diagnostic metadata to the package description.
◆ Where it's heading
Three releases across five years, and the newest carries no user-facing change at all. The package is in maintenance: it does what it set out to do for bkmr users, and updates now arrive only when CRAN or an upstream dependency forces them.
◆ Prediction
Expect the next release to be another compliance or dependency-driven patch rather than new functionality; the entries show no in-progress feature work.
Alternatives to adjustedCurves and bkmrhat
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 bkmrhat.
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 adjustedCurves alternatives → · See all bkmrhat alternatives →
Recent activity from adjustedCurves and bkmrhat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 9mo agobkmrhatDebugging metadata added to package description
- 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
- 4y agobkmrhatLow-memory chain combining plus a seed-collision fix
- 5y agobkmrhatFirst release: parallel chains and continuation for bkmr
Frequently asked questions
What is the difference between adjustedCurves and bkmrhat?
Both compete on the same themes — r-package — within Infra & APIs. adjustedCurves and bkmrhat 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.
Is adjustedCurves better than bkmrhat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. adjustedCurves and bkmrhat 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.
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 bkmrhat?
Top bkmrhat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bkmrhat alternatives" section above for the current picks, or visit /alternatives/bkmrhat for the full list with editorial commentary on each.