← Back to home
Comparison · Analytics

ggeffects vs workflowsets

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

ggeffects vs workflowsets: at a glance

Featureggeffectsworkflowsets
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmarginal-effects, r-stats, statistics, breaking-changestidymodels, model-comparison, clustering, tuning
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is ggeffects?

ggeffects hands its contrast engine to modelbased and keeps the interface

ggeffects computes and plots marginal effects for a long tail of R model classes. Its recent line has two threads: steadily broadening model support and argument surface, and repeatedly absorbing breaking changes from the packages it computes on top of. In 2.2.0 it stopped absorbing them and delegated test_predictions() and johnson_neyman() to modelbased instead.

Read the full ggeffects 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 →

ggeffects vs workflowsets: editorial side-by-side

G
ggeffects
ANALYTICS
0.0

ggeffects hands its contrast engine to modelbased and keeps the interface

◆ Current state

ggeffects computes and plots marginal effects for a long tail of R model classes. Its recent line has two threads: steadily broadening model support and argument surface, and repeatedly absorbing breaking changes from the packages it computes on top of. In 2.2.0 it stopped absorbing them and delegated test_predictions() and johnson_neyman() to modelbased instead.

◆ Where it's heading

The package is settling into a front-end role — a consistent predict_response() interface over other people's estimation engines — rather than owning the computation itself. The 2.x releases also show a pattern of removing deprecated arguments and clarifying mixed-model semantics, so the interface is being tightened as the backend is outsourced.

◆ Prediction

Expect the features lost in the modelbased handover to return as that package's contrast and slope estimation matures, rather than being reimplemented locally.

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

See all ggeffects alternatives → · See all workflowsets alternatives →

Recent activity from ggeffects and workflowsets

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

  1. 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
  2. 1y agoggeffectsggeffects delegates contrasts and slopes to modelbased
  3. 1y agoggeffectsFive focal terms and formula-based contrast tests
  4. 1y agoggeffectsMixed-model predictions split type from interval
  5. 1y agoggeffectsBias correction for back-transformed mixed-model predictions
  6. 1y agoggeffectsSupport for WeightIt model classes
  7. 2y agoggeffectsglmgee support and vcov controls for ggemmeans()
  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 ggeffects and workflowsets?

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

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

Top ggeffects alternatives in Analytics are ranked by recent ship velocity. Browse the "ggeffects alternatives" section above for the current picks, or visit /alternatives/ggeffects 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.