← Back to home
Comparison · Infra & APIs

FoRecoML vs ggdist

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

Shared themes:r-package

FoRecoML vs ggdist: at a glance

FeatureFoRecoMLggdist
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriesdata-visualization, uncertainty, bayesian-statistics, ggplot2
Last editorial update53m ago23h ago
WebsiteVisit →Visit →

What is FoRecoML?

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

Read the full FoRecoML trajectory →

What is ggdist?

The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.

ggdist supplies ggplot2 with a compositional vocabulary for distributions — slabs, intervals, dotplots and the sub-geometries that combine them. The last three years moved it from a drawing library to an estimation library: bounded density estimation with Sheather-Jones bandwidth became the default, weights propagate through every density, interval and point summary, and blurred dotplots render Monte Carlo standard error as visual fuzz. The 2025 release rounds this out with per-geometry thickness subscales and settable global defaults.

Read the full ggdist trajectory →

FoRecoML vs ggdist: editorial side-by-side

F
FoRecoML
INFRA · APIS
0.0

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

◆ Current state

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

◆ Where it's heading

This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.

◆ Prediction

With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.

G
ggdist
INFRA · APIS
0.0

The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.

◆ Current state

ggdist supplies ggplot2 with a compositional vocabulary for distributions — slabs, intervals, dotplots and the sub-geometries that combine them. The last three years moved it from a drawing library to an estimation library: bounded density estimation with Sheather-Jones bandwidth became the default, weights propagate through every density, interval and point summary, and blurred dotplots render Monte Carlo standard error as visual fuzz. The 2025 release rounds this out with per-geometry thickness subscales and settable global defaults.

◆ Where it's heading

Two threads run in parallel and keep converging. One is statistical: pluggable density estimators arrived first, then became the default, then gained weights and quantile histograms. The other is compositional: sub-geometries acquired their own guides, then their own scales, so a slab's thickness axis is now a first-class annotated dimension. Cadence has stretched from twice-yearly to roughly annual, with the recent work tightening existing surface rather than opening new.

◆ Prediction

Subguides gained subscales a release later, so the remaining asymmetry is in the sub-geometry system rather than the statistics; expect the next release to continue that fill-in work.

Alternatives to FoRecoML and ggdist

Other Infra & APIs 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 FoRecoML or ggdist.

See all FoRecoML alternatives → · See all ggdist alternatives →

Recent activity from FoRecoML and ggdist

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

  1. 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
  2. 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
  3. 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN
  4. 1y agoggdistPer-geometry thickness subscales and settable defaults
  5. 2y agoggdistBlurred dotplots draw Monte Carlo error; weights reach every estimator
  6. 2y agoggdistC++ dotplot binning and safer bandwidth fallbacks
  7. 3y agoggdistBounded density becomes the default; existing charts change
  8. 3y agoggdistCategorical distributions, hex layouts, pluggable density estimators
  9. 4y agoggdistComputed variables shared across sub-geometries

Frequently asked questions

What is the difference between FoRecoML and ggdist?

Both compete on the same themes — r-package — within Infra & APIs. FoRecoML and ggdist 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 FoRecoML better than ggdist?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoRecoML and ggdist 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to FoRecoML?

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

What are the best alternatives to ggdist?

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