← Back to home
Comparison · Analytics

fabletools vs riem

A side-by-side editorial comparison of fabletools and riem — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

fabletools vs riem: at a glance

Featurefabletoolsriem
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, tidyverts, model-combination, reconciliationweather-data, api-client, r-package, ropensci
Last editorial update3h ago56m ago
WebsiteVisit →Visit →

What is fabletools?

The tidyverts forecasting core rebuilt model combination on full residual covariance.

fabletools is the framework layer under fable and fpp3 — mables, fables, accuracy measures, reconciliation, and the model arithmetic that lets forecasters express ensembles as expressions. Version 0.8.0 reworked that arithmetic: combination now uses a joint N-way convolution accounting for the full residual covariance across components rather than composing pairwise, and every arithmetic operator collapses to a single model_combination with correctly implied weights, so nested expressions like ((m1 + m2)/2 + m3)/2 flatten automatically. In parallel, the package has been shedding graphics to {ggtime} on a deliberately slow deprecation clock.

Read the full fabletools trajectory →

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.

Read the full riem trajectory →

fabletools vs riem: editorial side-by-side

F
fabletools
ANALYTICS
0.0

The tidyverts forecasting core rebuilt model combination on full residual covariance.

◆ Current state

fabletools is the framework layer under fable and fpp3 — mables, fables, accuracy measures, reconciliation, and the model arithmetic that lets forecasters express ensembles as expressions. Version 0.8.0 reworked that arithmetic: combination now uses a joint N-way convolution accounting for the full residual covariance across components rather than composing pairwise, and every arithmetic operator collapses to a single model_combination with correctly implied weights, so nested expressions like ((m1 + m2)/2 + m3)/2 flatten automatically. In parallel, the package has been shedding graphics to {ggtime} on a deliberately slow deprecation clock.

◆ Where it's heading

The framework is being narrowed and deepened at the same time. Narrowed, because plotting is moving out to a dedicated package over an announced two-year deprecation, leaving fabletools to modeling infrastructure. Deepened, because the recent statistical work targets correctness in places users could not easily inspect — combination weights, inverse-variance weighting computed on response rather than innovation residuals, reconciliation coherency matrices exposed via coherent_smat() and coherent_cmat(). Class hygiene follows the same instinct, with mdl_lst replacing lst_mdl and gaining augment(), glance(), and tidy() so global and reconciliation models report statistics like any other.

◆ Prediction

With combination and reconciliation infrastructure freshly reworked, the remaining announced work is the ggtime separation, so expect the graphics re-exports to keep degrading toward removal while modeling changes stay incremental.

R
riem
ANALYTICS
0.0

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 fabletools 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 fabletools or riem.

See all fabletools alternatives → · See all riem alternatives →

Recent activity from fabletools and riem

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agofabletoolsModel combination rebuilt on joint N-way convolution
  2. 3mo agofabletoolsCoherency matrices exposed, mdl_lst gains tidier methods
  3. 5mo agofabletoolsGraphics methods now require fabletools to be attached
  4. 6mo agofabletoolsTime series graphics migrating out to ggtime
  5. 8mo agofabletoolsggplot2 4.0.0 compatibility patch
  6. 8mo agofabletoolsIRF() generic and multivariate bootstrap sample paths
  7. 1y agoriem1.0.0 removes defaults and adds query arguments
  8. 1y agoriemDrops the last vcr usage in favour of httptest2
  9. 2y agoriemTimezone and timestamp-parsing fixes
  10. 4y agoriemMoves to httr2 and httptest2
  11. 4y agoriemSwitches to newer IEM metadata web services
  12. 9y agoriemReduces dependencies to tibble alone

Frequently asked questions

What is the difference between fabletools and riem?

Both compete on the same themes — r-package — within Analytics. fabletools 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 fabletools better than riem?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fabletools 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 fabletools?

Top fabletools alternatives in Analytics are ranked by recent ship velocity. Browse the "fabletools alternatives" section above for the current picks, or visit /alternatives/fabletools 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.