← Back to home
Comparison · Analytics

censored vs workflows

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

Shared themes:tidymodels

censored vs workflows: at a glance

Featurecensoredworkflows
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, tidymodels, parsnip, enginestidymodels, pipelines, postprocessing, sparse-data
Last editorial update5h ago53m ago
WebsiteVisit →Visit →

What is censored?

censored keeps survival models aligned with parsnip's shifting prediction contracts

censored supplies survival-analysis engines to parsnip, and its release history is dominated by staying in step with the rest of tidymodels rather than shipping independent features. The 0.2.0 and 0.3.0 releases added engines and prediction types; everything since has been contract alignment — quantile prediction format, hardhat test adaptation, flexsurv preparation.

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

censored vs workflows: editorial side-by-side

C
censored
ANALYTICS
0.0

censored keeps survival models aligned with parsnip's shifting prediction contracts

◆ Current state

censored supplies survival-analysis engines to parsnip, and its release history is dominated by staying in step with the rest of tidymodels rather than shipping independent features. The 0.2.0 and 0.3.0 releases added engines and prediction types; everything since has been contract alignment — quantile prediction format, hardhat test adaptation, flexsurv preparation.

◆ Where it's heading

The package is settling into a downstream role where parsnip and hardhat set the interface and censored implements it for censored regression. Breaking changes arrive from upstream, not from new ideas here. The substantive engine work — aorsf, flexsurvspline, glmnet multi_predict — is behind it, and recent cycles are thin.

◆ Prediction

Expect the next releases to track further parsnip prediction-type changes rather than add engines; the entries do not show new survival methods in progress.

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

See all censored alternatives → · See all workflows alternatives →

Recent activity from censored and workflows

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

  1. 4mo agocensoredcensored 0.3.4
  2. 11mo agoworkflowsWorkflows gain a postprocessing stage via tailor
  3. 1y agoworkflowsSparse matrices work through fit() and predict()
  4. 1y agocensoredQuantile prediction format follows new parsnip requirements
  5. 2y agocensoredSurvival probabilities at infinite evaluation times now computed
  6. 2y agocensoredcensored 0.3.1
  7. 2y agoworkflowsaugment() aligns with parsnip; censored regression supported
  8. 2y agocensoredmulti_predict() for all glmnet prediction types; aorsf predicts time
  9. 3y agocensoredeval_time replaces time; matrix fitting for censored regression
  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 censored and workflows?

Both compete on the same themes — tidymodels — within Analytics. censored and workflows 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 censored better than workflows?

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

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