← Back to home
Comparison · Infra & APIs

FoReco vs microeco

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

Shared themes:r-package

FoReco vs microeco: at a glance

FeatureFoRecomicroeco
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, hierarchical-reconciliation, time-series, s3-classesmicrobiome, metabolomics, r-package, network-analysis
Last editorial update53m ago1d ago
WebsiteVisit →Visit →

What is FoReco?

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

Read the full FoReco trajectory →

What is microeco?

A microbiome analysis framework quietly grew a metabolomics half

microeco is a class-based R framework for microbial community data, organised as trans_* analysis objects layered over a microtable container. The 2.x line added trans_metab for metabolomics in 2.1.0, built pathway calculation, enrichment and network functions onto it in 2.2.0, and reached 2.3.0 with trans_niche and trans_phylo classes plus graphml export from the network module. Release notes are dense bullet lists where a handful of new classes sit among fifteen to twenty parameter fixes.

Read the full microeco trajectory →

FoReco vs microeco: editorial side-by-side

F
FoReco
INFRA · APIS
0.0

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

◆ Current state

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

◆ Where it's heading

The package is completing a reversal it started in 1.0.0. That release simplified outputs to plain matrices and pushed metadata into attributes reachable via recoinfo(); 1.3.0 removed recoinfo() outright and put the structure back as a class with components(), summary(), and plot() methods. The direction is toward being infrastructure rather than a function library — the class is exported through new_foreco_class() and a sibling package has already adopted it. Method coverage has meanwhile broadened from optimal combination into non-negative algorithms, bounded reconciliation, and Gaussian and sample-based probabilistic variants.

◆ Prediction

The soft-deprecated res2matrix() is flagged for removal, so a subsequent release should finish that cleanup; with the class now exported, expect more methods to hang off foreco objects rather than more top-level functions.

M
microeco
INFRA · APIS
0.0

A microbiome analysis framework quietly grew a metabolomics half

◆ Current state

microeco is a class-based R framework for microbial community data, organised as trans_* analysis objects layered over a microtable container. The 2.x line added trans_metab for metabolomics in 2.1.0, built pathway calculation, enrichment and network functions onto it in 2.2.0, and reached 2.3.0 with trans_niche and trans_phylo classes plus graphml export from the network module. Release notes are dense bullet lists where a handful of new classes sit among fifteen to twenty parameter fixes.

◆ Where it's heading

The package expands by adding analysis classes rather than rewriting existing ones, and the 2.x series widened its scope from microbial community structure to paired omics. trans_metab was the pivot; niche and phylogenetic classes in 2.3.0 extend the original microbiome side in parallel. Alongside that, a long maintenance thread tracks upstream churn - linewidth replacing size for ggplot2 v4.0, igraph namespace changes, lifecycle deprecations - which accounts for most of the bullet volume in any given release.

◆ Prediction

Expect further trans_* classes filling gaps around the metabolomics arm, since every 2.x release so far has introduced at least one new class alongside its fix list.

Alternatives to FoReco and microeco

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 FoReco or microeco.

See all FoReco alternatives → · See all microeco alternatives →

Recent activity from FoReco and microeco

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

  1. 1mo agoFoRecoStrict argument validation and a pruned help index
  2. 1mo agomicroecoNiche and phylogenetic analysis classes join the framework
  3. 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object
  4. 3mo agomicroecoPathway calculation, enrichment and network functions build out trans_metab
  5. 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
  6. 4mo agomicroecotrans_metab class brings metabolomics into a microbiome framework
  7. 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
  8. 6mo agomicroecoStatistical functions gain direct visualization, plus a volcano plot
  9. 9mo agomicroecoggplot2 v4.0 compatibility pass plus network and normalization options
  10. 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
  11. 1y agomicroecoParameter renames and namespace fixes across the trans_ classes
  12. 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions

Frequently asked questions

What is the difference between FoReco and microeco?

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

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

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

What are the best alternatives to microeco?

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