metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of admiralpeds and mirai — release velocity, themes, recent moves, and the top alternatives to consider.
admiralpeds has shipped nothing but documentation for four releases running.
The paediatric extension to admiral provides growth-parameter derivations against WHO and CDC metadata. Across its last four releases the notes contain no new functions and no changed derivations — the entries are vignettes, website theming, badges, an LLM documentation widget, lint configuration and a roclet migration to admiraldev.
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.
The paediatric extension to admiral provides growth-parameter derivations against WHO and CDC metadata. Across its last four releases the notes contain no new functions and no changed derivations — the entries are vignettes, website theming, badges, an LLM documentation widget, lint configuration and a roclet migration to admiraldev.
Development has moved almost entirely into the shared pharmaverse infrastructure: subject test data went out to pharmaversesdtm, lint configuration and the custom admiral roclets moved to admiraldev, and the website now follows the same PR-triggered build workflow as its sibling packages. What is left in the package itself is the growth derivations, which have not changed in these entries.
On this evidence the growth-derivation surface is considered complete; the next release is more likely to track an admiraldev or admiral change than to add a derivation.
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.
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.
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.
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 admiralpeds or mirai.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all admiralpeds alternatives → · See all mirai alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top admiralpeds alternatives in Analytics are ranked by recent ship velocity. Browse the "admiralpeds alternatives" section above for the current picks, or visit /alternatives/admiralpeds for the full list with editorial commentary on each.
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.