← Back to home
Comparison · Infra & APIs

FoRecoML vs Transmission

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

FoRecoML vs Transmission: at a glance

FeatureFoRecoMLTransmission
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriesbittorrent, json-rpc, api-migration, beta-freeze
Last editorial update54m ago15d 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 Transmission?

Transmission rewrote its RPC API to JSON-RPC 2.0 — then the 4.1 beta train stalled.

The whole visible history is the 4.1.0 beta series, running from December 2024 to January 2026 and developed in parallel with the 4.0.x bug-fix line since 2023. Across those betas the client picked up sequential downloading, a selectable µTP-versus-TCP preferred transport, proxy support for web connections, IPv6 and dual-stack UDP trackers, native platform icons, and a JSON-RPC 2.0-compliant RPC API with snake_case unified across RPC and settings.json. Feature freeze was declared at beta.5 in January 2026, and nothing has shipped since.

Read the full Transmission trajectory →

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

T
Transmission
INFRA · APIS
0.0

Transmission rewrote its RPC API to JSON-RPC 2.0 — then the 4.1 beta train stalled.

◆ Current state

The whole visible history is the 4.1.0 beta series, running from December 2024 to January 2026 and developed in parallel with the 4.0.x bug-fix line since 2023. Across those betas the client picked up sequential downloading, a selectable µTP-versus-TCP preferred transport, proxy support for web connections, IPv6 and dual-stack UDP trackers, native platform icons, and a JSON-RPC 2.0-compliant RPC API with snake_case unified across RPC and settings.json. Feature freeze was declared at beta.5 in January 2026, and nothing has shipped since.

◆ Where it's heading

The interesting work is at the integration boundary, not in the download engine: the RPC surface has been standardised and renamed, and beta.5 was largely spent repairing what those changes broke, including backwards-incompatible keys accidentally written into settings files. That is the cost profile of an API migration in a project with a large ecosystem of third-party remotes. With feature freeze held for seven months and no 4.1.0 final, the release is late relative to its own stated plan.

◆ Prediction

The next release should be 4.1.0 final or a further beta rather than new features, since the branch is frozen — but the entries give no signal on what is holding it.

Alternatives to FoRecoML and Transmission

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

See all FoRecoML alternatives → · See all Transmission alternatives →

Recent activity from FoRecoML and Transmission

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. 7mo agoTransmission4.1.0-beta.5 enters feature freeze and repairs settings-file damage
  5. 8mo agoTransmission4.1.0-beta.4 replaces the RPC API with a JSON-RPC 2.0 one
  6. 9mo agoTransmission4.1.0-beta.3 adds proxy support and streaming-friendly sequential writes
  7. 1y agoTransmission4.1.0-beta.2 adds sequential downloading and BEP-7 tracker fallback
  8. 1y agoTransmission4.1.0-beta.1 opens a branch two years in development

Frequently asked questions

What is the difference between FoRecoML and Transmission?

They serve adjacent needs but don't currently overlap on shipped themes. FoRecoML and Transmission 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 Transmission?

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

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