mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of see and timetk — release velocity, themes, recent moves, and the top alternatives to consider.
see grows wherever easystats adds a diagnostic, one plot method at a time.
see is the visualization layer for the easystats ecosystem, supplying plot() methods for performance, parameters and datawizard objects. Each release adds methods for whatever those packages shipped — prior predictive checks, DAG diagrams, factor-analysis graphs — alongside steady theme and geom refinement.
timetk swallowed anomalize whole, then went quiet for two years
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
see is the visualization layer for the easystats ecosystem, supplying plot() methods for performance, parameters and datawizard objects. Each release adds methods for whatever those packages shipped — prior predictive checks, DAG diagrams, factor-analysis graphs — alongside steady theme and geom refinement.
Growth here is downstream-driven rather than self-directed: see expands to cover new diagnostics as easystats produces them. Running alongside that is a sustained investment in presentation control — theme arguments on plot methods, elements that scale with base_size — which suits users embedding these plots in documents rather than glancing at them interactively.
Expect new plot methods to keep arriving in step with performance and parameters releases, with continued theming work rather than any change in the package's scope.
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.
The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.
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 see or timetk.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning is rebuilding its async machinery under a stable public surface
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
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. see and timetk 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. see and timetk 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.
Top see alternatives in Analytics are ranked by recent ship velocity. Browse the "see alternatives" section above for the current picks, or visit /alternatives/see-r for the full list with editorial commentary on each.
Top timetk alternatives in Analytics are ranked by recent ship velocity. Browse the "timetk alternatives" section above for the current picks, or visit /alternatives/timetk for the full list with editorial commentary on each.