← Back to home
Comparison · Infra & APIs

FoRecoML vs jstable

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

Shared themes:r-package

FoRecoML vs jstable: at a glance

FeatureFoRecoMLjstable
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriesbiostatistics, r-package, clinical-research, survey-weighted
Last editorial update56m ago1d 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 jstable?

A clinical table generator paying down years of edge cases in survey-weighted models

jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.

Read the full jstable trajectory →

FoRecoML vs jstable: 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.

J
jstable
INFRA · APIS
0.0

A clinical table generator paying down years of edge cases in survey-weighted models

◆ Current state

jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.

◆ Where it's heading

Each CRAN release bundles several GitHub patch versions, so the notes read as rolled-up fix lists rather than feature announcements. The substantive thread is pcut.univariate, introduced across seven display functions in 1.3.11 to allow multivariable analysis restricted to significant variables, and repaired repeatedly since as it collided with interaction terms, single-variable selections, clustered models and data.table inputs. The survey-weighted path is the other recurring source: counts, labels and family handling that worked for unweighted data kept failing once weights were involved.

◆ Prediction

Expect further patches in the survey-weighted subgroup functions, since 1.3.25 fixed four separate issues there and each recent release has surfaced more in the same area.

Alternatives to FoRecoML and jstable

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

See all FoRecoML alternatives → · See all jstable alternatives →

Recent activity from FoRecoML and jstable

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. 4mo agojstableSurvey-weighted logistic regression and sample counts corrected
  5. 6mo agojstableCompeting-risk counts drawn from original rather than transformed data
  6. 9mo agojstableMulti-state Cox models detected without a manual flag
  7. 10mo agojstableWide fix pass across the display functions
  8. 1y agojstableCrude p-values computed from raw data via data_for_univariate
  9. 1y agojstableSignificance-filtered multivariable analysis added across seven functions

Frequently asked questions

What is the difference between FoRecoML and jstable?

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

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

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