HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
adjustedCurves vs mize
A side-by-side editorial comparison of adjustedCurves and mize — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
adjustedCurves vs mize: 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 mize?
A numerical optimization toolkit that has been feature-complete and quiet since 2017
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
adjustedCurves vs mize: 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.
mize
0.0INFRA · APIS
A numerical optimization toolkit that has been feature-complete and quiet since 2017
◆ Current state
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
◆ Where it's heading
The pattern is a stable library rather than an abandoned one. Fixes address real reports - a bracket_step error when the Schmidt line search exhausts its function evaluation budget, an incorrect gradient count under backtracking with a specified step_down - and the maintainer used one release note to clarify that backtracking behaviour differs depending on whether step_down is supplied, which reads as answering a recurring question. The five and a half year gap between 0.2.4 and 0.2.5 is the clearest signal: the package is maintained on demand, not developed.
◆ Prediction
Expect nothing until an R or CRAN policy change forces another compliance patch, which is what triggered the most recent release.
Alternatives to adjustedCurves and mize
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 mize.
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 mize alternatives →
Recent activity from adjustedCurves and mize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agomizeCRAN compliance patch after five years of silence
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 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
- 5y agomizeBacktracking line search reporting and documentation fix
- 6y agomizeR-devel compatibility fix for class checking
- 7y agomizeSchmidt line search error when the evaluation budget is exhausted
- 7y agomizeStage check fix for bold driver and backtracking
- 9y agomizeCRAN release 0.1.1
Frequently asked questions
What is the difference between adjustedCurves and mize?
Both compete on the same themes — r-package — within Infra & APIs. adjustedCurves and mize 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 mize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. adjustedCurves and mize 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 mize?
Top mize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mize alternatives" section above for the current picks, or visit /alternatives/mize for the full list with editorial commentary on each.