tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of poissonreg and riem — release velocity, themes, recent moves, and the top alternatives to consider.
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
poissonreg is a tidymodels extension that wires Poisson and zero-inflated count regression into the parsnip interface. Its defining event was giving up ownership: the model definition functions moved into parsnip itself, leaving this package as engine bindings and prediction plumbing. The current dev release is entirely correctness and hygiene work — glmnet predictions now default to mean counts rather than the linear predictor, and single-observation prediction works at last.
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.
poissonreg is a tidymodels extension that wires Poisson and zero-inflated count regression into the parsnip interface. Its defining event was giving up ownership: the model definition functions moved into parsnip itself, leaving this package as engine bindings and prediction plumbing. The current dev release is entirely correctness and hygiene work — glmnet predictions now default to mean counts rather than the linear predictor, and single-observation prediction works at last.
Release cadence has collapsed from yearly to a four-year gap between 1.0.1 and the current development version, and the content has shifted from features to deduplication against parsnip — copied helper functions replaced by the upstream originals, obsolete generic registrations removed, tests migrated to the shared extension-package pattern. This is what a stabilized tidymodels satellite looks like: the interface lives upstream, and the package's job is to not drift from it.
The dev version's accumulated fixes point to a CRAN release of 1.0.2 as the next move, with content limited to the glmnet prediction corrections rather than any new engine or model type.
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.
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 poissonreg or riem.
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 poissonreg alternatives → · See all riem alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. poissonreg 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. poissonreg 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.
Top poissonreg alternatives in Analytics are ranked by recent ship velocity. Browse the "poissonreg alternatives" section above for the current picks, or visit /alternatives/poissonreg for the full list with editorial commentary on each.
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.