← Back to home
Comparison · Analytics

parameters vs workflowsets

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

parameters vs workflowsets: at a glance

Featureparametersworkflowsets
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeseasystats, model-parameters, standardization, mixed-modelstidymodels, model-comparison, clustering, tuning
Last editorial update45m ago1h ago
WebsiteVisit →Visit →

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.

Read the full parameters trajectory →

What is workflowsets?

workflowsets keeps widening what counts as a model worth comparing.

workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.

Read the full workflowsets trajectory →

parameters vs workflowsets: editorial side-by-side

P
parameters
ANALYTICS
0.0

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.

W
workflowsets
ANALYTICS
0.0

workflowsets keeps widening what counts as a model worth comparing.

◆ Current state

workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.

◆ Where it's heading

The package's job is comparison, so its direction is set by what tidymodels can express: every time a new model paradigm lands elsewhere, workflowsets has to learn to rank it. Clustering was the largest of those steps because it has no outcome column to score against. Alongside that runs a slower cleanup — named-only optional arguments, type checking on inputs, informative errors when someone passes a workflow set to fit() — that reads as a package hardening after its API settled.

◆ Prediction

Expect the tailor postprocessors that workflows added in 1.3.0 to need representation here next, since a workflow set that cannot vary the postprocessor cannot compare calibration choices.

Alternatives to parameters and workflowsets

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

See all parameters alternatives → · See all workflowsets alternatives →

Recent activity from parameters and workflowsets

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

  1. 1mo agoparametersparameters 0.29.2 extends lavaan support and fixes label dropping
  2. 2mo agoparametersparameters 0.29.1 adds a cluster argument and fixes vcov handling
  3. 3mo agoparametersparameters 0.29.0 stops standardizing the intercept in post-hoc methods
  4. 8mo agoparametersparameters 0.28.3 adds Kenward-Roger and Satterthwaite for glmmTMB
  5. 11mo agoparametersparameters 0.28.2 updates tests for the latest fixest release
  6. 11mo agoparametersparameters 0.28.1 adds robust standard errors for glmmTMB
  7. 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
  8. 2y agoworkflowsetsCensored regression evaluation; eval_time breaks positional args
  9. 3y agoworkflowsetsClustering models enter workflow sets via tidyclust
  10. 4y agoworkflowsetsCase weights supported across a workflow set
  11. 4y agoworkflowsetsUpdate models and recipes across a set; mixed inputs accepted
  12. 5y agoworkflowsetsextract_*() supersedes pull_*() across tidymodels

Frequently asked questions

What is the difference between parameters and workflowsets?

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

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

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