Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
admiralonco vs tulpa
A side-by-side editorial comparison of admiralonco and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
admiralonco vs tulpa: at a glance
What is admiralonco?
The oncology ADaM helper is dissolving into admiral core, one deprecation at a time.
admiralonco is the oncology companion to admiral, and it ships response-criteria recipes rather than code: RECIST, iRECIST, IMWG, GCIG and PCWG3 each arrive as a vignette plus an ADaM template. Cadence is one or two releases a year, each adding a criteria vignette. The 1.4.0 release began deprecating most of the package's own exported functions in favour of generic admiral equivalents.
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.
admiralonco vs tulpa: editorial side-by-side
admiralonco
0.0ANALYTICS
The oncology ADaM helper is dissolving into admiral core, one deprecation at a time.
◆ Current state
admiralonco is the oncology companion to admiral, and it ships response-criteria recipes rather than code: RECIST, iRECIST, IMWG, GCIG and PCWG3 each arrive as a vignette plus an ADaM template. Cadence is one or two releases a year, each adding a criteria vignette. The 1.4.0 release began deprecating most of the package's own exported functions in favour of generic admiral equivalents.
◆ Where it's heading
The package is converging on a documentation-and-templates model: reusable derivation logic moves upstream into admiral, and admiralonco keeps only the oncology-specific know-how. Every release since 1.0.0 has added a criteria vignette rather than new exported functions, and 1.4.1 extends that by making the template set browsable from the Get Started menu. The surface users program against is shrinking while the guidance they read is growing.
◆ Prediction
Expect the deprecation cycle started in 1.4.0 to advance through its warning and error phases across the next one or two releases, with new work arriving as another response-criteria vignette rather than new functions.
tulpa
7.5ANALYTICS
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 admiralonco 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 admiralonco or tulpa.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all admiralonco alternatives → · See all tulpa alternatives →
Recent activity from admiralonco and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198 ⚡
- 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 8d agotulpaDense batched joint path could silently drop a grid cell
- 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 9d agotulpaCUDA backend had two definitions; link order decided if it ran
- 9d agotulpaHyperparameter bounds now flag when they leave the node range
- 2mo agoadmiraloncoTemplate explorer vignette added to Get Started
- 6mo agoadmiraloncoPSA endpoints land as function deprecation begins ⚡
- 11mo agoadmiraloncoPCWG3 response criteria vignette added
- 1y agoadmiraloncoGCIG response criteria vignette added
- 2y agoadmiraloncoIMWG response criteria vignette added
- 2y agoadmiraloncoiRECIST response criteria vignette added
Frequently asked questions
What is the difference between admiralonco 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 admiralonco 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 admiralonco?
Top admiralonco alternatives in Analytics are ranked by recent ship velocity. Browse the "admiralonco alternatives" section above for the current picks, or visit /alternatives/admiralonco 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.