mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
parameters vs workflows
A side-by-side editorial comparison of parameters and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
parameters vs workflows: at a glance
What is parameters?
easystats' parameters package absorbs one more model class every few weeks
parameters extracts and formats coefficients from an enormous range of R model objects, and its releases read as a running ledger of that range expanding — lavaan and lavaan.mi, survey, lcmm, glmmTMB, fixest, marginaleffects, ordinal. Recent versions ship roughly monthly with a mix of new support, new arguments, and fixes for label handling and standard errors. The most consequential recent change is behavioral: post-hoc standardization no longer standardizes the intercept, setting it and its inferential statistics to NA.
What is workflows?
The tidymodels pipeline grew a third stage, and it happens after the model runs.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
parameters vs workflows: editorial side-by-side
parameters
0.0ANALYTICS
easystats' parameters package absorbs one more model class every few weeks
◆ Current state
parameters extracts and formats coefficients from an enormous range of R model objects, and its releases read as a running ledger of that range expanding — lavaan and lavaan.mi, survey, lcmm, glmmTMB, fixest, marginaleffects, ordinal. Recent versions ship roughly monthly with a mix of new support, new arguments, and fixes for label handling and standard errors. The most consequential recent change is behavioral: post-hoc standardization no longer standardizes the intercept, setting it and its inferential statistics to NA.
◆ Where it's heading
The package's job is to be the universal adapter for model output, so its roadmap is effectively set by what the R modelling ecosystem produces. Two threads are visible beyond coverage: getting standard errors right for awkward cases such as frailty terms and robust vcov matrices, and getting labels right when factors are converted on the fly or character variables appear in a formula. Interoperability inside easystats keeps tightening, with equivalence_test() gaining methods for modelbased objects.
◆ Prediction
Given the cadence, the next release will most likely add another model class alongside label and standard-error fixes rather than change how the package works.
workflows
0.0ANALYTICS
The tidymodels pipeline grew a third stage, and it happens after the model runs.
◆ Current state
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
◆ Where it's heading
The object is filling out into a complete pipeline description rather than a preprocessing-plus-model pair. Postprocessing is the structural addition — calibration and threshold selection were previously done by hand after prediction, outside anything tidymodels could tune or record — and the fact that it arrived integrated with tunable() and tune_args() rather than as a standalone step is the point. The rest of the arc is the steady tidymodels habit of converting silent guesses into errors.
◆ Prediction
Expect tailor postprocessors to spread through tune and workflowsets next, since the parameter and tuning generics were wired up first, and expect sparse support to extend to more engines after lightgbm.
Alternatives to parameters and workflows
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 parameters or workflows.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk
timetk swallowed anomalize whole, then went quiet for two years
modelbased
modelbased is turning marginal effects into a full contrast grammar
tidyposterior
A finished Bayesian model-comparison package in pure maintenance mode
See all parameters alternatives → · See all workflows alternatives →
Recent activity from parameters and workflows
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoparametersparameters 0.29.2 extends lavaan support and fixes label dropping
- 2mo agoparametersparameters 0.29.1 adds a cluster argument and fixes vcov handling
- 3mo agoparametersparameters 0.29.0 stops standardizing the intercept in post-hoc methods
- 8mo agoparametersparameters 0.28.3 adds Kenward-Roger and Satterthwaite for glmmTMB
- 11mo agoparametersparameters 0.28.2 updates tests for the latest fixest release
- 11mo agoparametersparameters 0.28.1 adds robust standard errors for glmmTMB
- 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor ⚡
- 1y agoworkflowsSparse matrices work through fit() and predict()
- 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
- 3y agoworkflowsRegister tuning generics unconditionally
- 3y agoworkflowsMissing parsnip extensions now error early; unsupervised specs supported
- 3y agoworkflowsMode guessing removed; silent offset handling now errors
Frequently asked questions
What is the difference between parameters and workflows?
They serve adjacent needs but don't currently overlap on shipped themes. parameters and workflows 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 parameters better than workflows?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. parameters and workflows 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 parameters?
Top parameters alternatives in Analytics are ranked by recent ship velocity. Browse the "parameters alternatives" section above for the current picks, or visit /alternatives/parameters-r for the full list with editorial commentary on each.
What are the best alternatives to workflows?
Top workflows alternatives in Analytics are ranked by recent ship velocity. Browse the "workflows alternatives" section above for the current picks, or visit /alternatives/workflows-r for the full list with editorial commentary on each.