← Back to home
Comparison · Analytics

intsurv vs rphylopic

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

Shared themes:r-package

intsurv vs rphylopic: at a glance

Featureintsurvrphylopic
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, cure-models, censored-data, regularizationphylogenetics, data-visualization, r-package, ggplot2
Last editorial update45m ago4h 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 rphylopic?

The R package that puts organism silhouettes on plots keeps widening where they can be drawn.

rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.

Read the full rphylopic trajectory →

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

The R package that puts organism silhouettes on plots keeps widening where they can be drawn.

◆ Current state

rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.

◆ Where it's heading

Development is expanding the set of places a silhouette can appear rather than changing what the package does. Base plots came first, then ggplot2 aesthetics and legend glyphs, then trees, then network vertices via an igraph shape registered automatically when both packages load. The other running thread is defensive maintenance against upstream churn: retries on failed API calls, fixes for ggplot2 4.0.0, and now an in-memory cache so repeated calls stop hammering the PhyloPic API. The ysize and size deprecation, opened in 1.5.0, is now complete and the arguments are scheduled for removal.

◆ Prediction

The deprecated ysize and size arguments look set to be removed in the next release, and on the pattern of the last four, another plotting context is a likelier addition than a change to the retrieval layer.

Alternatives to intsurv and rphylopic

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

See all intsurv alternatives → · See all rphylopic alternatives →

Recent activity from intsurv and rphylopic

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

  1. 1mo agorphylopicSilhouettes become igraph vertices; API responses cached
  2. 8mo agorphylopicBase R phylogenies gain silhouette annotation
  3. 10mo agointsurvModel configuration moves into dedicated control functions
  4. 1y agorphylopicExplicit width and height replace the old sizing arguments
  5. 2y agorphylopicSilhouette legends and attribution permalinks
  6. 2y agorphylopicSilhouette resolution helper and safer colour defaults
  7. 2y agorphylopicRendering dependencies bumped for grImport2 and rsvg
  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 rphylopic?

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

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

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