r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of serofoi and ymlthis — release velocity, themes, recent moves, and the top alternatives to consider.
serofoi grew a serosurvey simulator alongside the force-of-infection models it was built to fit.
serofoi estimates the force of infection from serological survey data using Bayesian serocatalytic models fitted through Stan. Beyond fitting it now simulates serosurveys — specifying a model and a survey design and generating the data such a survey would produce. The most recent release is visualisation and naming work.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
serofoi estimates the force of infection from serological survey data using Bayesian serocatalytic models fitted through Stan. Beyond fitting it now simulates serosurveys — specifying a model and a survey design and generating the data such a survey would produce. The most recent release is visualisation and naming work.
The package moved from fitting-only to a fit-and-simulate pair. 0.1.0 added simulation from time- or age-varying force-of-infection trends and simplified the fitted object down to a Stan fit; 1.0.2 broadened simulation into full serosurvey generation with its own vignette. 1.0.3 then spent its effort on naming consistency and plotting options, which is what a package does once its scope is set.
With simulation and fitting both in place, the natural next step is tooling that closes the loop between them — recovery checks or study-design guidance built on simulated surveys.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
The retirement is the endpoint of a long drift. Between 2020 and 2022 every release was reactive — patching around a crayon update that mangled rendered YAML, tracking shiny 1.6, following roxygen2 7.0.0, fixing a typo in an add-in. No new capability has landed in six years, and the four-year gap before 1.0.0 had already answered the question the release note finally makes explicit.
Nothing further of substance is expected — the stated policy is changes only where CRAN requires them, so the next release, if any, will be a compatibility patch.
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 serofoi or ymlthis.
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 serofoi alternatives → · See all ymlthis alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. serofoi and ymlthis 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. serofoi and ymlthis 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 serofoi alternatives in Analytics are ranked by recent ship velocity. Browse the "serofoi alternatives" section above for the current picks, or visit /alternatives/serofoi for the full list with editorial commentary on each.
Top ymlthis alternatives in Analytics are ranked by recent ship velocity. Browse the "ymlthis alternatives" section above for the current picks, or visit /alternatives/ymlthis for the full list with editorial commentary on each.