mlr3mbo
mlr3mbo picked its defaults from a benchmark study, not from taste
Comparison · Analytics
censored vs dbparser
A side-by-side editorial comparison of censored and dbparser — release velocity, themes, recent moves, and the top alternatives to consider.
censored vs dbparser: 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 dbparser?
dbparser shed its database and CSV writers to become just a DrugBank parser.
dbparser reads DrugBank's XML release into R tibbles. Its 2.0 line removed the persistence features that defined 1.x, writing to a database or to CSV, in favour of returning a dvobject the caller handles. Releases since have been column-naming normalization and test updates against newer DrugBank versions.
censored vs dbparser: 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.
dbparser
0.0ANALYTICS
dbparser shed its database and CSV writers to become just a DrugBank parser.
◆ Current state
dbparser reads DrugBank's XML release into R tibbles. Its 2.0 line removed the persistence features that defined 1.x, writing to a database or to CSV, in favour of returning a dvobject the caller handles. Releases since have been column-naming normalization and test updates against newer DrugBank versions.
◆ Where it's heading
The arc is scope reduction. Version 1.2.0 was the high-water mark of ambition, adding collective parsers, an R6 redesign and progress bars; 2.0.1 then deprecated the database and CSV writers and the old public methods outright. What remains is a narrower package whose ongoing work is keeping column names consistent and tests current with DrugBank's schema.
◆ Prediction
The last two releases track DrugBank data versions rather than adding features, so the next is most likely another compatibility pass against a newer DrugBank release.
Alternatives to censored and dbparser
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 dbparser.
loo
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
mlr3fselect
mlr3fselect turned feature selection into an asynchronous, distributable job
lime
lime survives on compatibility patches years after its research moment
mlr3measures
mlr3measures is systematically retrofitting sample weights across every metric
mlr3cluster
mlr3cluster went from a handful of clusterers to covering the field
See all censored alternatives → · See all dbparser alternatives →
Recent activity from censored and dbparser
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agocensoredcensored 0.3.4
- 1y agocensoredQuantile prediction format follows new parsnip requirements
- 2y agocensoredSurvival probabilities at infinite evaluation times now computed
- 2y agodbparserDuplicate drugbank_id column fixed in drug targets
- 2y agocensoredcensored 0.3.1
- 2y agodbparserTibble column names normalized to snake_case and drugbank_id
- 2y agocensoredmulti_predict() for all glmnet prediction types; aorsf predicts time
- 3y agocensoredeval_time replaces time; matrix fitting for censored regression
- 3y agodbparserPersistence layer dropped; parsers now return a dvobject ⚡
- 5y agodbparserCollective parsers added; parsers reimplemented as R6 classes
- 6y agodbparserMemory and performance gains across parsers
- 6y agodbparserFixes for SQL Server column sizes and dplyr compatibility
Frequently asked questions
What is the difference between censored and dbparser?
They serve adjacent needs but don't currently overlap on shipped themes. censored and dbparser 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 dbparser?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. censored and dbparser 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 dbparser?
Top dbparser alternatives in Analytics are ranked by recent ship velocity. Browse the "dbparser alternatives" section above for the current picks, or visit /alternatives/dbparser for the full list with editorial commentary on each.