← Back to home
Comparison · Analytics

censored vs mlr3tuning

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

censored vs mlr3tuning: at a glance

Featurecensoredmlr3tuning
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themessurvival-analysis, tidymodels, parsnip, enginesmlr3, hyperparameter-tuning, async-optimization, callbacks
Last editorial update6h ago1h 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 mlr3tuning?

mlr3tuning is rebuilding its async machinery under a stable public surface

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

Read the full mlr3tuning trajectory →

censored vs mlr3tuning: 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.

M
mlr3tuning
ANALYTICS
2.5

mlr3tuning is rebuilding its async machinery under a stable public surface

◆ Current state

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

◆ Where it's heading

Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.

◆ Prediction

With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.

Alternatives to censored and mlr3tuning

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 mlr3tuning.

See all censored alternatives → · See all mlr3tuning alternatives →

Recent activity from censored and mlr3tuning

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

  1. 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
  2. 4mo agocensoredcensored 0.3.4
  3. 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
  4. 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
  5. 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
  6. 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
  7. 1y agocensoredQuantile prediction format follows new parsnip requirements
  8. 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage
  9. 2y agocensoredSurvival probabilities at infinite evaluation times now computed
  10. 2y agocensoredcensored 0.3.1
  11. 2y agocensoredmulti_predict() for all glmnet prediction types; aorsf predicts time
  12. 3y agocensoredeval_time replaces time; matrix fitting for censored regression

Frequently asked questions

What is the difference between censored and mlr3tuning?

They serve adjacent needs but don't currently overlap on shipped themes. mlr3tuning is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.

Is censored better than mlr3tuning?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3tuning is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.

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 mlr3tuning?

Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.