marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A side-by-side editorial comparison of epiparameter and metatools — release velocity, themes, recent moves, and the top alternatives to consider.
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.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
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.
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.
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.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
The package's development has been concentrated on one function, combine_supp(), which is where the messy realities of supplemental qualifiers surface — whitespace in join keys, empty supp datasets, colliding names. 0.1.6 also drew three first-time contributors, which is the healthiest signal in the history, but no release has followed. Sibling packages have meanwhile been dropping metatools as a dependency.
Without a release in two years the package looks stable rather than active; the plausible trigger is a controlled-terminology or dplyr change that forces the checks to be updated.
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 metatools.
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.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all epiparameter alternatives → · See all metatools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. epiparameter and metatools are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. epiparameter and metatools are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
Top metatools alternatives in Analytics are ranked by recent ship velocity. Browse the "metatools alternatives" section above for the current picks, or visit /alternatives/metatools for the full list with editorial commentary on each.