webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
Comparison · Analytics
admiralonco vs mirai
A side-by-side editorial comparison of admiralonco and mirai — release velocity, themes, recent moves, and the top alternatives to consider.
admiralonco vs mirai: 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 mirai?
mirai removed its dispatcher process and added memory backpressure to the queue.
The async evaluation framework releases roughly monthly and moves fast at the architecture level. In 2.7.0 the dispatcher stopped being a separate process and became a thread, after its loop had already been rewritten in C inside nanonext one release earlier. The same release added an opt-in memory budget for queued task payloads and try_mirai(), which returns NULL immediately rather than blocking when that budget is exhausted.
admiralonco vs mirai: 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.
mirai
2.5ANALYTICS
mirai removed its dispatcher process and added memory backpressure to the queue.
◆ Current state
The async evaluation framework releases roughly monthly and moves fast at the architecture level. In 2.7.0 the dispatcher stopped being a separate process and became a thread, after its loop had already been rewritten in C inside nanonext one release earlier. The same release added an opt-in memory budget for queued task payloads and try_mirai(), which returns NULL immediately rather than blocking when that budget is exhausted.
◆ Where it's heading
Two threads of work run together: cutting overhead out of the task path — thread-based dispatcher, in-process transport for synchronous daemons, lower per-element dispatch cost in mirai_map() — and making the framework safe to embed in an event loop, where blocking the host R thread is not acceptable. Deployment reach is growing too, with http_config() launching remote daemons over HTTP APIs and auto-configuring for Posit Workbench. Each release pins a minimum nanonext version, so the two packages advance as one unit.
◆ Prediction
With backpressure in place but opt-in, the open question these notes leave is whether a default memory budget arrives; continued overhead reduction and Shiny-facing non-blocking paths are the safer bet.
Alternatives to admiralonco and mirai
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 mirai.
sftime
The spatiotemporal companion to sf, moving at the pace of the packages around it.
ReLTER
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
waywiser
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
taxizedb
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
fellingdater
Went from estimating felling dates to doing the crossdating that produces them.
See all admiralonco alternatives → · See all mirai alternatives →
Recent activity from admiralonco and mirai
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 25d agomiraiMap collection and daemon lifecycle fixes
- 2mo agomiraiAgent skill ships in-package; HTTP headers take over auth
- 2mo agoadmiraloncoTemplate explorer vignette added to Get Started
- 3mo agomiraiDispatcher becomes a thread, and the queue gains a memory budget ⚡
- 5mo agomiraiParallel RNG seeding leaves experimental status
- 6mo agomiraiRemote daemons over HTTP, and a C dispatcher loop
- 6mo agoadmiraloncoPSA endpoints land as function deprecation begins ⚡
- 8mo agomiraiTelemetry span timing and daemon-switch fix
- 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 mirai?
They serve adjacent needs but don't currently overlap on shipped themes. mirai is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 mirai?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mirai is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 mirai?
Top mirai alternatives in Analytics are ranked by recent ship velocity. Browse the "mirai alternatives" section above for the current picks, or visit /alternatives/mirai for the full list with editorial commentary on each.