← Back to home
Comparison · Analytics

intsurv vs simlandr

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

Shared themes:r-package

intsurv vs simlandr: at a glance

Featureintsurvsimlandr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationr-package, dynamical-systems, visualization, api-consolidation
Last editorial update3h ago1h 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 simlandr?

Potential landscape tooling settling onto standard R generics after two rounds of renaming.

simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.

Read the full simlandr trajectory →

intsurv vs simlandr: 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.

S
simlandr
ANALYTICS
0.0

Potential landscape tooling settling onto standard R generics after two rounds of renaming.

◆ Current state

simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.

◆ Where it's heading

Every release trades a package-specific name for a conventional one - var and par became arg and ele, get_geom() became an autolayer() method, get_barrier_height() became a summary() method, hash_big.matrix became hash_big_matrix. The one methodological change, an adjusted minimal energy path algorithm, arrived inside a release otherwise full of renames. Removing default values for barrier calculation because they were often unsuitable reads as the maintainer deciding the defaults were doing harm.

◆ Prediction

The feed stops at 0.3.0 in late 2022, mid-consolidation; these entries give no indication of what followed, if anything did.

Alternatives to intsurv and simlandr

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 simlandr.

See all intsurv alternatives → · See all simlandr alternatives →

Recent activity from intsurv and simlandr

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

  1. 10mo agointsurvModel configuration moves into dedicated control functions
  2. 3y agosimlandrAccessors replaced by autolayer and summary methods
  3. 3y agosimlandrroxygen2 updated for HTML5 compatibility
  4. 4y agosimlandrBatch simulation arguments renamed; energy path algorithm adjusted
  5. 4y agosimlandrManual improved and a test function added
  6. 5y agosimlandrPackage cleaned for CRAN compatibility
  7. 5y agointsurvCross-validated model selection and offset terms added
  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

Frequently asked questions

What is the difference between intsurv and simlandr?

Both compete on the same themes — r-package — within Analytics. intsurv and simlandr 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 simlandr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. intsurv and simlandr 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 simlandr?

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