tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of riem and serofoi — release velocity, themes, recent moves, and the top alternatives to consider.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
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.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.
With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing again.
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.
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 riem or serofoi.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all riem alternatives → · See all serofoi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. riem and serofoi 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. riem and serofoi 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 riem alternatives in Analytics are ranked by recent ship velocity. Browse the "riem alternatives" section above for the current picks, or visit /alternatives/riem for the full list with editorial commentary on each.
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.