r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of mirai and pharmaverseadam — release velocity, themes, recent moves, and the top alternatives to consider.
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.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
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.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
Coverage tracks the pharmaverse's own therapeutic-area expansion with a lag of one release: pediatrics arrived in 1.1.0, metabolic in 1.2.0, neurology in 1.3.0. The other consistent thread is a slow move off development versions — 1.1.0 and 1.2.0 both had to pin unreleased upstream builds to get working templates, while 1.3.0 cites released versions throughout. Reorganising the reference page by therapeutic area is the same maturation showing up in documentation.
Expect the next release to follow the established pattern — a refresh against current upstream versions plus datasets from whichever admiral therapeutic-area package reaches a stable release next.
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 mirai or pharmaverseadam.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all mirai alternatives → · See all pharmaverseadam 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 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.
Top pharmaverseadam alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaverseadam alternatives" section above for the current picks, or visit /alternatives/pharmaverseadam for the full list with editorial commentary on each.