← Back to home
Comparison · Analytics

fabletools vs lightr

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

Shared themes:r-package

fabletools vs lightr: at a glance

Featurefabletoolslightr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, tidyverts, model-combination, reconciliationspectrometry, file-parsers, breaking-change, extensibility
Last editorial update53m ago1h 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 lightr?

Reorganised its parsers by vendor, then opened the parser slot to users.

lightr reads spectrometry files from the proprietary formats that instrument vendors ship, and its recent releases have been about the structure of that parser collection rather than adding one more format. Version 2.0.0 renamed every low-level parser from lr_parse_<extension>() to lr_parse_<brand>_<extension>(), a breaking change made specifically so two vendors can share a file extension without colliding, and restored binary parsing for Avantes AvaSoft 8.4 using vendor-supplied format documentation. Version 2.1.0 follows through by exposing a parser argument on the high-level functions.

Read the full lightr trajectory →

fabletools vs lightr: 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.

L
lightr
ANALYTICS
0.0

Reorganised its parsers by vendor, then opened the parser slot to users.

◆ Current state

lightr reads spectrometry files from the proprietary formats that instrument vendors ship, and its recent releases have been about the structure of that parser collection rather than adding one more format. Version 2.0.0 renamed every low-level parser from lr_parse_<extension>() to lr_parse_<brand>_<extension>(), a breaking change made specifically so two vendors can share a file extension without colliding, and restored binary parsing for Avantes AvaSoft 8.4 using vendor-supplied format documentation. Version 2.1.0 follows through by exposing a parser argument on the high-level functions.

◆ Where it's heading

The package is moving from a fixed set of formats it knows about to a dispatch system users can extend. The brand-qualified naming and the parser argument are two halves of the same design: name parsers unambiguously, then let callers select or supply one. Alongside that runs steady attention to metadata fidelity — measurement timestamps, checksum verification against tampering, and timezone handling that survived upstream tzdata removing legacy codes.

◆ Prediction

Expect additional vendor parsers to arrive under the new brand-qualified scheme, and the custom-parser path to absorb formats the maintainers do not want to support directly. The entries do not name specific instruments planned next.

Alternatives to fabletools and lightr

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 lightr.

See all fabletools alternatives → · See all lightr alternatives →

Recent activity from fabletools and lightr

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

  1. 1mo agolightrHigh-level functions accept a custom parser argument
  2. 1mo agofabletoolsModel combination rebuilt on joint N-way convolution
  3. 1mo agolightrParsers renamed by vendor; Avantes binary support restored
  4. 3mo agofabletoolsCoherency matrices exposed, mdl_lst gains tidier methods
  5. 5mo agofabletoolsGraphics methods now require fabletools to be attached
  6. 6mo agofabletoolsTime series graphics migrating out to ggtime
  7. 8mo agofabletoolsggplot2 4.0.0 compatibility patch
  8. 8mo agofabletoolsIRF() generic and multivariate bootstrap sample paths
  9. 1y agolightrChecksum verification and measurement timestamps in metadata
  10. 1y agolightrReworks timezone handling after tzdata dropped legacy codes
  11. 2y agolightrAdds lintr and stabilises floating-point tests
  12. 4y agolightrParser errors surface as warnings instead of being silenced

Frequently asked questions

What is the difference between fabletools and lightr?

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

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

Top lightr alternatives in Analytics are ranked by recent ship velocity. Browse the "lightr alternatives" section above for the current picks, or visit /alternatives/lightr for the full list with editorial commentary on each.