← Back to home
Comparison · Infra & APIs

BayLum vs FoRecoML

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

Shared themes:r-package

BayLum vs FoRecoML: at a glance

FeatureBayLumFoRecoML
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, luminescence-dating, geochronology, jagsforecasting, machine-learning, hierarchical-reconciliation, time-series
Last editorial update1d ago54m ago
WebsiteVisit →Visit →

What is BayLum?

Bayesian luminescence dating that finally replaced its folder-structure input format.

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

Read the full BayLum trajectory →

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 →

BayLum vs FoRecoML: editorial side-by-side

B
BayLum
INFRA · APIS
0.0

Bayesian luminescence dating that finally replaced its folder-structure input format.

◆ Current state

BayLum runs Bayesian age models for luminescence and combined OSL/C-14 dating on top of JAGS. The 2024 release rebuilt the front end: a single create_DataFile() replaces the separate single-grain and multi-grain generators, reads BIN/BINX and XSYG directly, and takes a YAML config in place of the old prescribed folder layout. Since then the work has been CRAN compliance and documentation.

◆ Where it's heading

Two long-running threads have converged: making JAGS runs survivable (parallel methods, halved MCMC memory, injectable custom models) and making the inputs survivable (YAML config, consistency checks, auto-detected sample names). With the deprecated generators on their way out, the next phase is removal rather than addition. Release cadence is roughly annual and slowing.

◆ Prediction

The deprecated Generate_DataFile(), Generate_DataFile_MG() and LT_RegenDose() are the obvious next casualties; a release that drops them would be the first breaking change since the YAML rework.

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.

Alternatives to BayLum and FoRecoML

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 BayLum or FoRecoML.

See all BayLum alternatives → · See all FoRecoML alternatives →

Recent activity from BayLum and FoRecoML

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. 10mo agoBayLumCRAN anchor fixes and an R 4.4 floor
  5. 2y agoBayLumOne data-file function and a YAML config replace the folder layout
  6. 3y agoBayLumMCMC memory halved; density plots for age distributions
  7. 3y agoBayLumParallel JAGS runs and a file-scaffolding helper
  8. 4y agoBayLumCustom model injection and RNG control for parallel runs
  9. 5y agoBayLumParallel JAGS experiment plus IntCal20-era calibration data

Frequently asked questions

What is the difference between BayLum and FoRecoML?

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

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

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

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.