metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
epiparameter vs mirai
A side-by-side editorial comparison of epiparameter and mirai — release velocity, themes, recent moves, and the top alternatives to consider.
epiparameter vs mirai: at a glance
What is epiparameter?
epiparameter split its parameter library out of the package — and relicensed what remained.
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
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.
epiparameter vs mirai: editorial side-by-side
epiparameter
0.0ANALYTICS
epiparameter split its parameter library out of the package — and relicensed what remained.
◆ Current state
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
◆ Where it's heading
Each release has clarified the boundary between the data and the tools that operate on it. 0.2.0 added coercion from {epireview} tables, 0.3.0 rewrote the classes and renamed much of the API, and 0.4.0 completed the separation while adding caching so loading the library stays cheap. Breaking changes have been frequent and deliberate rather than incidental.
◆ Prediction
With code and data separated, the two can version independently — expect parameter additions to appear in {epiparameterDB} releases while this package's changes stay focused on classes and methods.
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 epiparameter 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 epiparameter or mirai.
marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
logrx
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
lobstr
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
GSODR
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all epiparameter alternatives → · See all mirai alternatives →
Recent activity from epiparameter 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
- 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
- 8mo agomiraiTelemetry span timing and daemon-switch fix
- 1y agoepiparameterCRAN check fixes
- 1y agoepiparameterParameter library moves to epiparameterDB; package relicensed to MIT alone ⚡
- 1y agoepiparameterClasses and methods reworked; large-scale renaming
- 2y agoepiparameterInteroperability with epireview via as_epidist()
- 2y agoepiparameterFirst release: 122 parameter sets and the epidist class
Frequently asked questions
What is the difference between epiparameter 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 epiparameter 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 epiparameter?
Top epiparameter alternatives in Analytics are ranked by recent ship velocity. Browse the "epiparameter alternatives" section above for the current picks, or visit /alternatives/epiparameter 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.