HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
adjustedCurves vs ipaddress
A side-by-side editorial comparison of adjustedCurves and ipaddress — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
adjustedCurves vs ipaddress: 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 ipaddress?
IP address vectors for R that hit 1.0 and then went quiet.
ipaddress gives R first-class IPv4 and IPv6 vector types with the arithmetic, netmask and subnet operations that come with them, backed by C++. The 1.0.0 release in 2023 was the deliberate breaking cleanup: one result per input from the hostname functions, vectorised subnets(), several arguments forced to be named, and a country_networks() downloader added. Since then the only release has been a testthat deprecation fix.
adjustedCurves vs ipaddress: 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.
ipaddress
0.0INFRA · APIS
IP address vectors for R that hit 1.0 and then went quiet.
◆ Current state
ipaddress gives R first-class IPv4 and IPv6 vector types with the arithmetic, netmask and subnet operations that come with them, backed by C++. The 1.0.0 release in 2023 was the deliberate breaking cleanup: one result per input from the hostname functions, vectorised subnets(), several arguments forced to be named, and a country_networks() downloader added. Since then the only release has been a testthat deprecation fix.
◆ Where it's heading
The package reached the interface it wanted and stopped. The five releases before 1.0.0 were almost entirely CRAN check compliance — deprecated C++ calls, HTML5 notes, a Windows toolchain change — with functional work confined to a couple of releases that shed heavy dependencies. That pattern, long compliance runs punctuated by rare interface work, is what the feed shows now.
◆ Prediction
On this cadence the next release is most likely another CRAN or upstream-testing compliance patch; nothing in the entries indicates new functionality in progress.
Alternatives to adjustedCurves and ipaddress
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 ipaddress.
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.
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 ipaddress alternatives →
Recent activity from adjustedCurves and ipaddress
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agoadjustedCurvesOff-by-one-step error corrected in cumulative incidence estimates
- 0y agoipaddresstestthat deprecation warnings resolved
- 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 agoipaddress1.0.0 breaks the interface to make it vector-native ⚡
- 3y agoipaddressDeprecated C++ sprintf calls replaced
- 3y agoadjustedCurvesDependency compatibility and installation documentation
- 4y agoipaddressroxygen upgrade to clear HTML5 check notes
- 4y agoipaddressWindows compiler toolchain compatibility for R 4.2
- 5y agoipaddressHotfix for CRAN check warnings
Frequently asked questions
What is the difference between adjustedCurves and ipaddress?
Both compete on the same themes — r-package — within Infra & APIs. adjustedCurves and ipaddress 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 ipaddress?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. adjustedCurves and ipaddress 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 ipaddress?
Top ipaddress alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ipaddress alternatives" section above for the current picks, or visit /alternatives/ipaddress for the full list with editorial commentary on each.