tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
censored vs probably
A side-by-side editorial comparison of censored and probably — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:tidymodels
censored vs probably: at a glance
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.
What is probably?
The package that made calibration a step instead of an afterthought.
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
censored vs probably: editorial side-by-side
censored
0.0ANALYTICS
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.
probably
0.0ANALYTICS
The package that made calibration a step instead of an afterthought.
◆ Current state
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
◆ Where it's heading
The recent releases are about making these objects survive leaving the session. butcher and required_pkgs() methods are what a model needs to be pinned, containerised and served, and their arrival alongside workflows adding a tailor postprocessing stage and vetiver adding probably support points the same way: calibration is being moved out of analysis scripts and into the deployed pipeline. The cal_*_none() reference implementations are the tell that calibration is now something people tune rather than apply once.
◆ Prediction
Expect the calibration functions to be reachable directly from a tuned workflow's postprocessing stage rather than applied to predictions afterwards, following the tailor integration that workflows just shipped.
Alternatives to censored and probably
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 probably.
textrecipes
Text features finally stay sparse all the way to the model.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork
patchwork stopped being a ggplot composer and became a page composer.
See all censored alternatives → · See all probably alternatives →
Recent activity from censored and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agocensoredcensored 0.3.4
- 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
- 1y agoprobablyggplot2 test updates and a clearer validation-set error
- 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
- 1y agocensoredQuantile prediction format follows new parsnip requirements
- 2y agocensoredSurvival probabilities at infinite evaluation times now computed
- 2y agocensoredcensored 0.3.1
- 2y agoprobablyFix grouping sensitivity to variable type
- 2y agocensoredmulti_predict() for all glmnet prediction types; aorsf predicts time
- 3y agoprobablySplit conformal and conformal quantile regression added
- 3y agoprobablyCalibration and conformal inference arrive in tidymodels ⚡
- 3y agocensoredeval_time replaces time; matrix fitting for censored regression
Frequently asked questions
What is the difference between censored and probably?
Both compete on the same themes — tidymodels — within Analytics. censored and probably 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 probably?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. censored and probably 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 probably?
Top probably alternatives in Analytics are ranked by recent ship velocity. Browse the "probably alternatives" section above for the current picks, or visit /alternatives/probably for the full list with editorial commentary on each.