← Back to home
Comparison · Analytics

mlr3viz vs workflows

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

mlr3viz vs workflows: at a glance

Featuremlr3vizworkflows
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesmlr3, visualization, ggplot2, roc-curvestidymodels, pipelines, postprocessing, sparse-data
Last editorial update49m ago1h ago
WebsiteVisit →Visit →

What is mlr3viz?

mlr3viz keeps the ecosystem's plots working while the plots themselves move out

mlr3viz supplies autoplot methods across mlr3 objects — learners, resample and benchmark results, tuning instances, ensemble feature-selection results. Recent releases are mostly defensive: suppressing ggplot2::fortify() warnings on ROC and PRC curves, pinning legend order so plots are deterministic across ggplot2 environments, and tracking mlr3 1.7.2. A visible piece of scope also left, with the LearnerSurvCoxPH plot moving to mlr3proba.

Read the full mlr3viz trajectory →

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.

Read the full workflows trajectory →

mlr3viz vs workflows: editorial side-by-side

M
mlr3viz
ANALYTICS
2.5

mlr3viz keeps the ecosystem's plots working while the plots themselves move out

◆ Current state

mlr3viz supplies autoplot methods across mlr3 objects — learners, resample and benchmark results, tuning instances, ensemble feature-selection results. Recent releases are mostly defensive: suppressing ggplot2::fortify() warnings on ROC and PRC curves, pinning legend order so plots are deterministic across ggplot2 environments, and tracking mlr3 1.7.2. A visible piece of scope also left, with the LearnerSurvCoxPH plot moving to mlr3proba.

◆ Where it's heading

The package is being narrowed toward generic plotting infrastructure while learner-specific plots migrate to the packages that own those learners. What it does add is access rather than new charts — passing parameters through to precrec::autoplot(), better hints when the wrong autoplot type is requested, and a confidence-interval plot for mlr3inferr. Determinism across ggplot2 versions has become a recurring concern, which is what happens when a visualization package is depended on by documentation and tests.

◆ Prediction

Following the Cox proportional-hazards precedent, further learner-specific plots are likely to move to their owning packages, leaving mlr3viz with the cross-cutting result objects.

W
workflows
ANALYTICS
0.0

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 mlr3viz 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 mlr3viz or workflows.

See all mlr3viz alternatives → · See all workflows alternatives →

Recent activity from mlr3viz and workflows

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

  1. 18d agomlr3vizmlr3viz 0.11.1 pins legend order for deterministic plots
  2. 5mo agomlr3vizmlr3viz 0.11.0 quiets ggplot2 fortify warnings on ROC curves
  3. 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor
  4. 1y agomlr3vizmlr3viz 0.10.1 passes plotting parameters through to precrec
  5. 1y agoworkflowsSparse matrices work through fit() and predict()
  6. 1y agomlr3vizmlr3viz 0.10.0 adds a LearnerSurvCoxPH plot
  7. 2y agomlr3vizmlr3viz 0.9.0 adds EnsembleFSResult plots
  8. 2y agomlr3vizmlr3viz 0.8.0 tracks paradox 1.0.0
  9. 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
  10. 3y agoworkflowsRegister tuning generics unconditionally
  11. 3y agoworkflowsMissing parsnip extensions now error early; unsupervised specs supported
  12. 3y agoworkflowsMode guessing removed; silent offset handling now errors

Frequently asked questions

What is the difference between mlr3viz and workflows?

They serve adjacent needs but don't currently overlap on shipped themes. mlr3viz is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is mlr3viz better than workflows?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3viz is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to mlr3viz?

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