← Back to home
Comparison · Analytics

intsurv vs semmcci

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

Shared themes:r-package

intsurv vs semmcci: at a glance

Featureintsurvsemmcci
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationstructural-equation-modeling, monte-carlo, confidence-intervals, r-package
Last editorial update48m ago5h 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 semmcci?

Monte Carlo confidence intervals for SEM, now mostly reacting to upstream deprecations

semmcci generates Monte Carlo confidence intervals for structural equation model parameters, working alongside lavaan. Its four-year release history is a run of patch versions from the jeksterslab account, each adding a function or adjusting method detail. The recent ones are quieter still: the latest addresses a lavaan::getCov() deprecation in tests, and the one before it is described only as minor method edits.

Read the full semmcci trajectory →

intsurv vs semmcci: 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
semmcci
ANALYTICS
0.0

Monte Carlo confidence intervals for SEM, now mostly reacting to upstream deprecations

◆ Current state

semmcci generates Monte Carlo confidence intervals for structural equation model parameters, working alongside lavaan. Its four-year release history is a run of patch versions from the jeksterslab account, each adding a function or adjusting method detail. The recent ones are quieter still: the latest addresses a lavaan::getCov() deprecation in tests, and the one before it is described only as minor method edits.

◆ Where it's heading

The functional build-out finished some time ago. MCGeneric() in 1.1.3 and Func()/MCFunc() in 1.1.4 opened the package to user-defined functions of parameters, which is the natural end point for a Monte Carlo interval tool — once arbitrary functions are supported, there is little left to add. Since then releases have tracked lavaan's changes rather than semmcci's own direction, and the gap between them has stretched from months to over a year.

◆ Prediction

Expect the next release to be triggered by another lavaan deprecation rather than by new capability.

Alternatives to intsurv and semmcci

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

See all intsurv alternatives → · See all semmcci alternatives →

Recent activity from intsurv and semmcci

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

  1. 2mo agosemmccilavaan getCov() deprecation handled in tests
  2. 10mo agosemmcciMinor method edits
  3. 10mo agointsurvModel configuration moves into dedicated control functions
  4. 2y agosemmcciUser-defined parameter functions via Func() and MCFunc()
  5. 2y agosemmcciMCGeneric() opens up arbitrary parameter targets
  6. 3y agosemmcciMultiple-imputation support via MCMI()
  7. 3y agosemmcciData generation internals refactored
  8. 5y agointsurvCross-validated model selection and offset terms added
  9. 6y agointsurvC++ headers relocated so other packages can link them
  10. 7y agointsurvCox cure models for uncertain event status arrive
  11. 7y agointsurvParameter initialization methods added to the alpha
  12. 7y agointsurvAlpha cut for paper submission and simulation reproducibility

Frequently asked questions

What is the difference between intsurv and semmcci?

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

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

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