← Back to home
Comparison · Analytics

modeltime.ensemble vs pecan

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

modeltime.ensemble vs pecan: at a glance

Featuremodeltime.ensemblepecan
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestime series forecasting, ensembles, tidymodels, compatibility maintenanceecosystem-modeling, data-assimilation, scientific-workflow, r-package
Last editorial update7h ago59m ago
WebsiteVisit →Visit →

What is modeltime.ensemble?

modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.

modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.

Read the full modeltime.ensemble trajectory →

What is pecan?

PEcAn v1.10 makes land-management events a first-class input and parallelises the whole SDA workflow

PEcAn is a workflow framework for ecosystem modelling — it standardises meteorological and initial-condition inputs, drives a set of coupled process models such as SIPNET, ED2, BioCro and LDNDC, and runs uncertainty analysis and state data assimilation over the results. Version 1.10.0 adds an events schema with validation and a SIPNET writer, so disturbance and management events can be declared in JSON and turned into model input, and runs the entire SDA workflow in parallel. It also adds CH4 and N2O to the standard variable table and an AmeriFlux meteorological ensemble path with ERA5 fallback.

Read the full pecan trajectory →

modeltime.ensemble vs pecan: editorial side-by-side

M0.0

modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.

◆ Current state

modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.

◆ Where it's heading

This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.

◆ Prediction

Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.

P
pecan
ANALYTICS
0.0

PEcAn v1.10 makes land-management events a first-class input and parallelises the whole SDA workflow

◆ Current state

PEcAn is a workflow framework for ecosystem modelling — it standardises meteorological and initial-condition inputs, drives a set of coupled process models such as SIPNET, ED2, BioCro and LDNDC, and runs uncertainty analysis and state data assimilation over the results. Version 1.10.0 adds an events schema with validation and a SIPNET writer, so disturbance and management events can be declared in JSON and turned into model input, and runs the entire SDA workflow in parallel. It also adds CH4 and N2O to the standard variable table and an AmeriFlux meteorological ensemble path with ERA5 fallback.

◆ Where it's heading

Two directions are visible. The framework keeps widening what it can represent — more standard variables, more carbon pools in BADM-based initial conditions, more coupled models — and it keeps industrialising the parts that used to be manual, from automated package documentation to qsub job-array expansion to parallel assimilation. The events schema is the first of these that gives users a declarative input format rather than a function to call, which is a different kind of extension than adding another model coupling.

◆ Prediction

The events schema currently has one model writer, for SIPNET, so the obvious next step is writers for the other coupled models — otherwise the format only benefits a single backend of the several PEcAn drives.

Alternatives to modeltime.ensemble and pecan

Other Analytics 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 modeltime.ensemble or pecan.

See all modeltime.ensemble alternatives → · See all pecan alternatives →

Recent activity from modeltime.ensemble and pecan

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

  1. 7mo agopecanEvents schema, parallel SDA workflow, CH4 and N2O standard variables
  2. 11mo agomodeltime.ensembleRealigned for tune 2.0.0 resampling changes
  3. 11mo agomodeltime.ensembleDrops the tidyverse dependency ahead of tune 2.0
  4. 1y agopecanAutomated pkgdown docs for all packages; qsub job-array support
  5. 1y agopecanLDNDC coupling, soilgrids carbon extraction, SDA observation prep
  6. 1y agopecanPFT-specific sensitivity analysis and BioCro 1.0 support
  7. 1y agopecanBioCro output renamed to PEcAn standard names; RCE fix
  8. 1y agopecanPEcAn.utils namespace cleanup; deprecated model2netcdf removed
  9. 5y agomodeltime.ensemblePer-series calibration IDs and parallel refitting
  10. 5y agomodeltime.ensembleRecursive ensembles for single and panel series

Frequently asked questions

What is the difference between modeltime.ensemble and pecan?

They serve adjacent needs but don't currently overlap on shipped themes. modeltime.ensemble and pecan 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 modeltime.ensemble better than pecan?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. modeltime.ensemble and pecan 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 Analytics products to evaluate alongside.

What are the best alternatives to modeltime.ensemble?

Top modeltime.ensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.ensemble alternatives" section above for the current picks, or visit /alternatives/modeltime-ensemble for the full list with editorial commentary on each.

What are the best alternatives to pecan?

Top pecan alternatives in Analytics are ranked by recent ship velocity. Browse the "pecan alternatives" section above for the current picks, or visit /alternatives/pecan-r for the full list with editorial commentary on each.