← Back to home
Comparison · Analytics

timetk vs workflowsets

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

timetk vs workflowsets: at a glance

Featuretimetkworkflowsets
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestime-series, anomaly-detection, visualization, feature-engineeringtidymodels, model-comparison, clustering, tuning
Last editorial update45m ago1h ago
WebsiteVisit →Visit →

What is timetk?

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.

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

timetk vs workflowsets: editorial side-by-side

T
timetk
ANALYTICS
0.0

timetk swallowed anomalize whole, then went quiet for two years

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

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

See all timetk alternatives → · See all workflowsets alternatives →

Recent activity from timetk and workflowsets

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

  1. 11mo agotimetktimetk 2.9.1 makes date parsing consistent across time classes
  2. 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
  3. 2y agoworkflowsetsCensored regression evaluation; eval_time breaks positional args
  4. 2y agotimetktimetk 2.9.0 absorbs the anomalize package
  5. 3y agoworkflowsetsClustering models enter workflow sets via tidyclust
  6. 4y agoworkflowsetsCase weights supported across a workflow set
  7. 4y agotimetktimetk 2.8.1 exposes trelliscope plotting parameters
  8. 4y agotimetktimetk 2.8.0 adds trelliscopejs support for many-series plots
  9. 4y agoworkflowsetsUpdate models and recipes across a set; mixed inputs accepted
  10. 4y agotimetktimetk 2.7.0 adds tk_tsfeatures() for grouped feature matrices
  11. 4y agotimetktimetk 2.6.2 adds .week_start and facet direction controls
  12. 5y agoworkflowsetsextract_*() supersedes pull_*() across tidymodels

Frequently asked questions

What is the difference between timetk and workflowsets?

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

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

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.

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.