tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dbparser and mlr3fselect — release velocity, themes, recent moves, and the top alternatives to consider.
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.
mlr3fselect turned feature selection into an asynchronous, distributable job
mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.
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.
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.
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.
mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.
Two threads run in parallel: scaling the search itself through async execution and the rush backend, and making ensemble selection results easier to analyse via Pareto fronts, knee points and now removal of empty result rows. The rush backward-compatibility shim was dropped in 1.6.0, so the async path is now the assumed one.
Expect the ensemble result API to keep gaining analysis helpers, with async execution treated as the default rather than an option.
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 dbparser or mlr3fselect.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all dbparser alternatives → · See all mlr3fselect alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbparser and mlr3fselect 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbparser and mlr3fselect 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.
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.
Top mlr3fselect alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3fselect alternatives" section above for the current picks, or visit /alternatives/mlr3fselect for the full list with editorial commentary on each.