tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
logrx vs riem
A side-by-side editorial comparison of logrx and riem — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
logrx vs riem: at a glance
What is logrx?
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
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.
logrx vs riem: editorial side-by-side
logrx
0.0ANALYTICS
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
◆ Current state
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
◆ Where it's heading
Feature work concentrated in the 0.1 line — return codes, a results writer, a to_report parameter, and logging of unapproved package and function use — and the 0.2 releases have been compatibility maintenance and hotfixes. Three years of silence in a pharmaverse that has otherwise kept shipping suggests the package reached the shape its users needed rather than that it was abandoned mid-design.
◆ Prediction
Nothing in these entries points to planned work; the likeliest trigger for a release is a breaking change in tidyverse dependencies, which is what produced the last one.
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 logrx 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 logrx 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 logrx and riem
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agoriem1.0.0 removes defaults and adds query arguments
- 1y agoriemDrops the last vcr usage in favour of httptest2
- 2y agoriemTimezone and timestamp-parsing fixes
- 3y agologrxAlignment with tidyselect and dplyr changes
- 3y agologrxRelease v0.2.1
- 3y agologrxFormatted log output plus CRAN readiness work
- 4y agologrxPackage renamed to logrx; return codes and results writer land
- 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 logrx and riem?
Both compete on the same themes — r-package — within Analytics. logrx 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 logrx better than riem?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. logrx 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 logrx?
Top logrx alternatives in Analytics are ranked by recent ship velocity. Browse the "logrx alternatives" section above for the current picks, or visit /alternatives/logrx 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.