HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
adjustedCurves vs finnts
A side-by-side editorial comparison of adjustedCurves and finnts — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
adjustedCurves vs finnts: 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 finnts?
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
finnts automates time-series forecasting end to end — feature engineering, model selection, hierarchical reconciliation — on a tidymodels backbone. Recent releases have concentrated on global models (one model fitted across many series) and on hierarchical reconciliation, which has needed repeated correction at weekly granularity. Release notes are auto-generated pull-request lists, so the detail lives in the PRs rather than in the changelog.
adjustedCurves vs finnts: 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.
finnts
0.0INFRA · APIS
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
◆ Current state
finnts automates time-series forecasting end to end — feature engineering, model selection, hierarchical reconciliation — on a tidymodels backbone. Recent releases have concentrated on global models (one model fitted across many series) and on hierarchical reconciliation, which has needed repeated correction at weekly granularity. Release notes are auto-generated pull-request lists, so the detail lives in the PRs rather than in the changelog.
◆ Where it's heading
Cadence is roughly annual and the commit history is almost entirely one maintainer, with occasional outside contributions. The direction across the last four releases is consolidation of the forecasting internals — multi-horizon models, feature selection, reconciliation fixes — rather than new surface for users. The changelogs themselves are unedited PR dumps, which makes the arc harder to read than the work probably warrants.
◆ Prediction
Hierarchical reconciliation has produced a bug fix in three of the last four releases, so the next one likely touches it again; nothing in the entries points to a specific new capability.
Alternatives to adjustedCurves and finnts
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 finnts.
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 finnts alternatives →
Recent activity from adjustedCurves and finnts
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 11mo agofinntsGlobal model updates and a weekly reconciliation fix
- 1y agoadjustedCurvesIPTW curves can now extend to the last observed time
- 1y agofinntsMulti-horizon models, hierarchy drivers, Synapse 3.4 migration
- 2y agoadjustedCurvesDropped arguments and a wrong multiple-imputation pooling formula
- 2y agoadjustedCurvesRisk tables, contrast consolidation and faster bootstrapping
- 2y agofinntsARIMAX support and feature selection added
- 3y agoadjustedCurvestmle and ostmle methods dropped
- 3y agofinntsdplyr 1.1.0 compatibility and a reconciliation fix
- 3y agoadjustedCurvesDependency compatibility and installation documentation
Frequently asked questions
What is the difference between adjustedCurves and finnts?
Both compete on the same themes — r-package — within Infra & APIs. adjustedCurves and finnts 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 finnts?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. adjustedCurves and finnts 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 finnts?
Top finnts alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "finnts alternatives" section above for the current picks, or visit /alternatives/finnts for the full list with editorial commentary on each.