← Back to home
Comparison · Analytics

dynwrap vs intsurv

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

dynwrap vs intsurv: at a glance

Featuredynwrapintsurv
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessingle-cell, trajectory-inference, bioinformatics, maintenance-modesurvival-analysis, cure-models, censored-data, regularization
Last editorial update2h ago46m ago
WebsiteVisit →Visit →

What is dynwrap?

A dormant trajectory-inference wrapper wakes up for maintenance only

dynwrap is the dynverse component that wraps single-cell trajectory inference methods behind a common interface, handling containerised method execution and the trajectory data model. The visible history is dominated by a burst of feature work in 2019 and then near-silence: the only recent release, v1.3.0, is a package modernisation with a minimum-version bump and no user-facing capability. The three entries in the feed span seven years.

Read the full dynwrap trajectory →

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 →

dynwrap vs intsurv: editorial side-by-side

D
dynwrap
ANALYTICS
0.0

A dormant trajectory-inference wrapper wakes up for maintenance only

◆ Current state

dynwrap is the dynverse component that wraps single-cell trajectory inference methods behind a common interface, handling containerised method execution and the trajectory data model. The visible history is dominated by a burst of feature work in 2019 and then near-silence: the only recent release, v1.3.0, is a package modernisation with a minimum-version bump and no user-facing capability. The three entries in the feed span seven years.

◆ Where it's heading

The direction is custodial rather than developmental. The 2019 releases built out the substance — RNA velocity in the wrapper, velocity-oriented topologies, directed geodesic distances, Singularity 3.0 and sparse matrices throughout — and nothing since has extended it. The 2026 release reads as keeping the package installable against a modern R toolchain, which is what a maintained dependency of a benchmark suite needs rather than what an actively developed tool looks like.

◆ Prediction

On this evidence, expect further releases to be compatibility maintenance triggered by R or dependency changes; the entries give no indication of resumed feature work.

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.

Alternatives to dynwrap and intsurv

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 dynwrap or intsurv.

See all dynwrap alternatives → · See all intsurv alternatives →

Recent activity from dynwrap and intsurv

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

  1. 4mo agodynwrapPackage modernisation, no user-facing change
  2. 10mo agointsurvModel configuration moves into dedicated control functions
  3. 5y agointsurvCross-validated model selection and offset terms added
  4. 6y agointsurvC++ headers relocated so other packages can link them
  5. 7y agointsurvCox cure models for uncertain event status arrive
  6. 7y agointsurvParameter initialization methods added to the alpha
  7. 7y agointsurvAlpha cut for paper submission and simulation reproducibility
  8. 7y agodynwrapRNA velocity support and directed geodesic distances
  9. 7y agodynwrap1.0.0: Singularity 3.0 only, sparse matrices throughout

Frequently asked questions

What is the difference between dynwrap and intsurv?

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

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

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

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.