mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of mlr3viz and Trackingplan — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Trackingplan turns tracking-plan validation into AI-assisted, consent-aware observability.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
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.
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.
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.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
The product is moving from passive tracking-plan validation toward active, guided remediation. Each release tightens the loop between detecting a problem (a warning, a consent gap) and resolving it — AI Debugger is spreading from generic warnings to consent warnings, and the UI is being rebuilt around single-surface investigation rather than scattered reports.
Expect AI Debugger to reach more warning types and Consent Monitoring to add further CMP integrations, continuing the pattern of extending both features to new surfaces rather than shipping a new pillar.
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 Trackingplan.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk swallowed anomalize whole, then went quiet for two years
modelbased is turning marginal effects into a full contrast grammar
easystats' parameters package absorbs one more model class every few weeks
A finished Bayesian model-comparison package in pure maintenance mode
See all mlr3viz alternatives → · See all Trackingplan alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Trackingplan is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Trackingplan is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
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.
Top Trackingplan alternatives in Analytics are ranked by recent ship velocity. Browse the "Trackingplan alternatives" section above for the current picks, or visit /alternatives/trackingplan for the full list with editorial commentary on each.