← Back to home
Comparison · Analytics

intsurv vs rtrek

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

Shared themes:r-package

intsurv vs rtrek: at a glance

Featureintsurvrtrek
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationstar-trek, web-scraping, datasets, api-client
Last editorial update2h 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 rtrek?

A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.

rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.

Read the full rtrek trajectory →

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

A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.

◆ Current state

rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.

◆ Where it's heading

The package's centre of gravity shifted once, at 0.2.0, from shipping static data to querying Memory Alpha and Memory Beta at runtime. Everything since has been the maintenance bill for that decision: HTML update fixes, parser improvements, portal retrieval bugs. Note that version numbers on this feed do not track time — 0.2.5 is stamped a year before 0.1.0, and three tags were backfilled within four minutes in November 2020 — so neither rank nor version ordering here indicates release sequence.

◆ Prediction

Expect the next release to fix retrieval against another Memory Alpha layout change, which is what the last four have done. The entries give no indication of new datasets or functions in progress.

Alternatives to intsurv and rtrek

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

See all intsurv alternatives → · See all rtrek alternatives →

Recent activity from intsurv and rtrek

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

  1. 10mo agointsurvModel configuration moves into dedicated control functions
  2. 1y agortrekMemory Alpha series portal retrieval fix
  3. 1y agortrekrtrek 0.5.1 release
  4. 2y agortrekParser improvements for wiki retrieval
  5. 2y agortrekDead external content and data dependencies removed
  6. 5y agointsurvCross-validated model selection and offset terms added
  7. 5y agortrekFixes for source website HTML changes
  8. 5y agortrekMemory Alpha and Memory Beta web APIs 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 rtrek?

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

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

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