WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
FoReco vs PESTO
A side-by-side editorial comparison of FoReco and PESTO — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
FoReco vs PESTO: at a glance
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.
What is PESTO?
A calibration toolkit that found its core PEST++ bridge had never actually run
PESTO wraps PEST++ inversion for APSIM crop models from R. Version 0.10.0 rebuilt the PEST++ invocation layer after the maintainer found the shell-out had never executed: control variables were passed as /h :name=value, a syntax PEST++ has never accepted. Fifteen defects were present since the initial April 2026 release and shipped in every version after it. 0.10.1 followed with APSIM binary discovery via APSIM_EXE_PATH and a benchmark battery against real PEST 18, pestpp-ies 5.2.16 and native APSIM that reproduced the prior baseline at 0.0% deviation on every accuracy metric.
FoReco vs PESTO: editorial side-by-side
FoReco
0.0INFRA · APIS
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.
PESTO
0.0INFRA · APIS
A calibration toolkit that found its core PEST++ bridge had never actually run
◆ Current state
PESTO wraps PEST++ inversion for APSIM crop models from R. Version 0.10.0 rebuilt the PEST++ invocation layer after the maintainer found the shell-out had never executed: control variables were passed as /h :name=value, a syntax PEST++ has never accepted. Fifteen defects were present since the initial April 2026 release and shipped in every version after it. 0.10.1 followed with APSIM binary discovery via APSIM_EXE_PATH and a benchmark battery against real PEST 18, pestpp-ies 5.2.16 and native APSIM that reproduced the prior baseline at 0.0% deviation on every accuracy metric.
◆ Where it's heading
The arc runs from packaging discipline toward working software, and the ordering is unusual. Releases 0.4.0 and 0.4.1 were governance and metadata passes: citation files, code of conduct, canonical URL migration to AAGI. 0.7.0 broadened the forward-model templates to ODE, crop-growth and SEIR forms and promoted the observation schema to public API. Only at 0.10.0 did the project ground itself against the actual USGS sources and a real pestpp binary, which is precisely when the defects surfaced.
◆ Prediction
Expect the next releases to widen the real-engine test matrix - more PEST++ variants and pinned APSIM versions exercised in CI - rather than add new forward-model families, since verification is now the stated priority in every release note.
Alternatives to FoReco and PESTO
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 PESTO.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all FoReco alternatives → · See all PESTO alternatives →
Recent activity from FoReco and PESTO
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoPESTOAPSIM auto-discovery and a full real-engine benchmark pass
- 1mo agoPESTOPEST++ invocation layer rebuilt after 15 defects left it non-functional ⚡
- 1mo agoFoRecoStrict argument validation and a pruned help index
- 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object ⚡
- 2mo agoPESTOODE, crop-growth and SEIR forward-model templates enter the public API
- 2mo agoPESTOValidation delegation and import hygiene pass
- 2mo agoPESTORepository governance and citation metadata migration
- 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
- 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
- 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
- 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions
Frequently asked questions
What is the difference between FoReco and PESTO?
Both compete on the same themes — r-package — within Infra & APIs. FoReco and PESTO 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 PESTO?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoReco and PESTO 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 PESTO?
Top PESTO alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PESTO alternatives" section above for the current picks, or visit /alternatives/pesto for the full list with editorial commentary on each.