← Back to home
Comparison · Analytics

survminer vs tulpa

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

survminer vs tulpa: at a glance

Featuresurvminertulpa
SectorAnalyticsAnalytics
Velocity score0.07.5
Sparks · 30d02
Top themesr, survival-analysis, ggplot2, dependency-reductionbayesian-inference, cran-release, r-packages, spatial-modeling
Last editorial update4d ago8h ago
WebsiteVisit →Visit →

What is survminer?

survminer is back after a five-year gap, and spending it cutting dependencies loose.

survminer draws Kaplan-Meier curves and Cox diagnostics on top of ggplot2, and it sits under a large share of published survival figures. After a long dormancy it has shipped three releases since late 2024, and all of them are about staying compatible: with ggplot2 3.5, then 4.0, and now without survMisc, whose weighted log-rank tests are computed internally in base R as of 0.5.2. The plotting API itself has not changed.

Read the full survminer trajectory →

What is tulpa?

The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.

tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.

Read the full tulpa trajectory →

survminer vs tulpa: editorial side-by-side

S
survminer
ANALYTICS
0.0

survminer is back after a five-year gap, and spending it cutting dependencies loose.

◆ Current state

survminer draws Kaplan-Meier curves and Cox diagnostics on top of ggplot2, and it sits under a large share of published survival figures. After a long dormancy it has shipped three releases since late 2024, and all of them are about staying compatible: with ggplot2 3.5, then 4.0, and now without survMisc, whose weighted log-rank tests are computed internally in base R as of 0.5.2. The plotting API itself has not changed.

◆ Where it's heading

This is a revival by maintenance, not by feature work — the same pattern as its sibling packages from the same author. The dependency surface is being reduced rather than extended, and each release absorbs a breaking change from ggplot2 that would otherwise leave existing scripts producing errors or misaligned risk tables. Compatibility fixes now arrive within months of the upstream change rather than years.

◆ Prediction

Continued ggplot2 4.x tracking is the most likely next release content, since 0.5.2 already carries fixes for 4.0.x aesthetics and the GeomConfint stairstep problem.

T
tulpa
ANALYTICS
7.5

The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.

◆ Current state

tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.

◆ Where it's heading

Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.

◆ Prediction

Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.

Alternatives to survminer and tulpa

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 survminer or tulpa.

See all survminer alternatives → · See all tulpa alternatives →

Recent activity from survminer and tulpa

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

  1. 18h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198
  2. 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
  3. 8d agotulpaDense batched joint path could silently drop a grid cell
  4. 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics
  5. 9d agotulpaCUDA backend had two definitions; link order decided if it ran
  6. 9d agotulpaHyperparameter bounds now flag when they leave the node range
  7. 5mo agosurvminersurvMisc dependency removed; weighted log-rank tests moved in-house
  8. 11mo agosurvminerRisk-table misalignment fixed via dynamic panel detection
  9. 1y agosurvminerggcoxzph() sd scaling corrected; tidyverse deprecations cleared
  10. 5y agosurvminerGehan-Breslow p-value corrected for log.rank.weights = n
  11. 6y agosurvminerbroom 0.7.0 compatibility fix in ggforest()
  12. 6y agosurvminersurv_adjustedcurves() separates computation from plotting

Frequently asked questions

What is the difference between survminer and tulpa?

They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is survminer better than tulpa?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to survminer?

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

What are the best alternatives to tulpa?

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