← Back to home
Comparison · Analytics

intsurv vs rdataone

A side-by-side editorial comparison of intsurv and rdataone — release velocity, themes, recent moves, and the top alternatives to consider.

intsurv vs rdataone: at a glance

Featureintsurvrdataone
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationresearch-data, data-repository, r-client, access-control
Last editorial update44m ago2h ago
WebsiteVisit →Visit →

What is intsurv?

A Cox cure-rate model package woke up after four years to simplify its own interface.

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

Read the full intsurv trajectory →

What is rdataone?

The R client for DataONE ships slow, correctness-focused maintenance

rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.

Read the full rdataone trajectory →

intsurv vs rdataone: editorial side-by-side

I
intsurv
ANALYTICS
0.0

A Cox cure-rate model package woke up after four years to simplify its own interface.

◆ Current state

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

◆ Where it's heading

The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.

◆ Prediction

The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.

R
rdataone
ANALYTICS
0.0

The R client for DataONE ships slow, correctness-focused maintenance

◆ Current state

rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.

◆ Where it's heading

This is long-cycle infrastructure maintenance, not feature development. Release intervals run to years, and the content is dominated by access-control correctness, CRAN compliance and TLS/platform fixes rather than new client capability. The one consistent thread is hardening how permissions and checksums survive a round trip to a member node.

◆ Prediction

Expect continued low-frequency releases driven by CRAN check failures and platform TLS changes, with any functional work staying in the upload and permissions path rather than the query surface.

Alternatives to intsurv and rdataone

Other Analytics 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 intsurv or rdataone.

See all intsurv alternatives → · See all rdataone alternatives →

Recent activity from intsurv and rdataone

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agordataonePermission bugs fixed in data package uploads
  2. 8mo agordataoneWindows TLS 1.2 fix unblocks client connections
  3. 10mo agointsurvModel configuration moves into dedicated control functions
  4. 5y agointsurvCross-validated model selection and offset terms added
  5. 5y agordataoneSHA-256 checksums and changed lazyLoad behaviour
  6. 6y agordataonedataone 2.1.4
  7. 6y agordataonedataone 2.1.3
  8. 6y agointsurvC++ headers relocated so other packages can link them
  9. 7y agointsurvCox cure models for uncertain event status arrive
  10. 7y agointsurvParameter initialization methods added to the alpha
  11. 7y agointsurvAlpha cut for paper submission and simulation reproducibility
  12. 7y agordataonedataone 2.1.2

Frequently asked questions

What is the difference between intsurv and rdataone?

They serve adjacent needs but don't currently overlap on shipped themes. intsurv and rdataone 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 intsurv better than rdataone?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. intsurv and rdataone 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 Analytics products to evaluate alongside.

What are the best alternatives to intsurv?

Top intsurv alternatives in Analytics are ranked by recent ship velocity. Browse the "intsurv alternatives" section above for the current picks, or visit /alternatives/intsurv for the full list with editorial commentary on each.

What are the best alternatives to rdataone?

Top rdataone alternatives in Analytics are ranked by recent ship velocity. Browse the "rdataone alternatives" section above for the current picks, or visit /alternatives/rdataone for the full list with editorial commentary on each.