HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
adjustedCurves vs nfs-ganesha
A side-by-side editorial comparison of adjustedCurves and nfs-ganesha — release velocity, themes, recent moves, and the top alternatives to consider.
adjustedCurves vs nfs-ganesha: 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 nfs-ganesha?
NFS-Ganesha is porting its management plane from DBUS to gRPC, four major versions in a month.
NFS-Ganesha is a user-space NFS server with pluggable FSAL backends for CEPH, GPFS and others. It is releasing major versions at an unusual rate — 12.0 through 15.1 since mid-July — and the connecting thread across all of them is gRPC: infrastructure first, then stats collection ported from DBUS, then more commands, then CacheMgr APIs and export management. Version 15.0 adds memory statistics and accounting alongside those APIs.
adjustedCurves vs nfs-ganesha: 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.
nfs-ganesha
6.3INFRA · APIS
NFS-Ganesha is porting its management plane from DBUS to gRPC, four major versions in a month.
◆ Current state
NFS-Ganesha is a user-space NFS server with pluggable FSAL backends for CEPH, GPFS and others. It is releasing major versions at an unusual rate — 12.0 through 15.1 since mid-July — and the connecting thread across all of them is gRPC: infrastructure first, then stats collection ported from DBUS, then more commands, then CacheMgr APIs and export management. Version 15.0 adds memory statistics and accounting alongside those APIs.
◆ Where it's heading
This is a control-plane migration carried out release by release in the open. Each version moves another slice of management surface onto gRPC — stats, exports, cache manager, a fake recall API for testing — while the data path work continues separately with XCOPY and clustered quality of service at 14.0. The 15.1 release extends ShowExports with a protocol summary and adds a gRPC FakeRecall API, which reads as filling in coverage rather than opening new ground. Note 15.0 and 15.1 are stamped seventy-nine seconds apart, so they were cut together rather than released as separate events.
◆ Prediction
Expect the remaining DBUS-era management commands to keep landing as gRPC APIs at this cadence. The open question these entries do not answer is whether DBUS is eventually removed or kept indefinitely alongside.
Alternatives to adjustedCurves and nfs-ganesha
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 nfs-ganesha.
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 nfs-ganesha alternatives →
Recent activity from adjustedCurves and nfs-ganesha
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agonfs-ganeshaShowExports gains a protocol summary; gRPC FakeRecall API added
- 1d agonfs-ganeshaMemory accounting and CacheMgr gRPC APIs
- 13d agonfs-ganeshaMore gRPC commands and RDMA rpcbind registration
- 15d agonfs-ganeshaXCOPY server-side copy and clustered quality of service ⚡
- 24d agonfs-ganeshagRPC expands with more stats collection
- 1mo agonfs-ganeshagRPC stats collection ported over from DBUS
- 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
Frequently asked questions
What is the difference between adjustedCurves and nfs-ganesha?
They serve adjacent needs but don't currently overlap on shipped themes. nfs-ganesha is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 nfs-ganesha?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nfs-ganesha is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 nfs-ganesha?
Top nfs-ganesha alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nfs-ganesha alternatives" section above for the current picks, or visit /alternatives/nfs-ganesha for the full list with editorial commentary on each.