tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
cfr vs riem
A side-by-side editorial comparison of cfr and riem — release velocity, themes, recent moves, and the top alternatives to consider.
cfr vs riem: at a glance
What is cfr?
cfr packaged delay-corrected severity estimation, then went quiet on maintenance.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
What is riem?
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.
cfr vs riem: editorial side-by-side
cfr
0.0ANALYTICS
cfr packaged delay-corrected severity estimation, then went quiet on maintenance.
◆ Current state
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
◆ Where it's heading
The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.
◆ Prediction
The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.
riem
0.0ANALYTICS
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to cfr and riem
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 cfr or riem.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
Recent activity from cfr and riem
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agocfrR-devel difftime patch and an individual-data vignette
- 1y agoriem1.0.0 removes defaults and adds query arguments
- 1y agoriemDrops the last vcr usage in favour of httptest2
- 2y agocfrSeverity estimator picks its own likelihood approximation
- 2y agoriemTimezone and timestamp-parsing fixes
- 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN ⚡
- 4y agoriemMoves to httr2 and httptest2
- 4y agoriemSwitches to newer IEM metadata web services
- 9y agoriemReduces dependencies to tibble alone
Frequently asked questions
What is the difference between cfr and riem?
They serve adjacent needs but don't currently overlap on shipped themes. cfr and riem 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.
Is cfr better than riem?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cfr and riem 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.
What are the best alternatives to cfr?
Top cfr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfr alternatives" section above for the current picks, or visit /alternatives/cfr for the full list with editorial commentary on each.
What are the best alternatives to riem?
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.