metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of DataSpaceR and mlr3cmprsk — release velocity, themes, recent moves, and the top alternatives to consider.
DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.
The R client for the CAVD DataSpace reached 1.0.0 in July 2026 after five years of small fixes. The release removed the mAb grid filtering and view methods in favour of filtering an availableMabs object with data.table syntax, applied that pattern to every query method, and added a class for querying DAASH, the Database of Annotated Antibody Sequences for HIV-1. The August patch restored the LANL monoclonal-antibody metadata requests and batched BCR sequence queries.
Competing risks arrive in mlr3, going from a non-parametric baseline to Fine-Gray regression in seven weeks.
mlr3cmprsk extends mlr3 to competing-risks analysis: learners predicting cumulative incidence functions, plus measures to score them. It appeared in February 2026 and reached 0.0.5 by April, adding a Fine-Gray learner and a Brier score along the way. The version numbers say pre-release; the cadence says active build-out.
The R client for the CAVD DataSpace reached 1.0.0 in July 2026 after five years of small fixes. The release removed the mAb grid filtering and view methods in favour of filtering an availableMabs object with data.table syntax, applied that pattern to every query method, and added a class for querying DAASH, the Database of Annotated Antibody Sequences for HIV-1. The August patch restored the LANL monoclonal-antibody metadata requests and batched BCR sequence queries.
The package is converging on one query idiom — build a filtered object, then fetch — instead of per-domain grid methods, and each class now accepts multiple studies or antibodies rather than one. The 1.0.1 patch suggests the rewrite dropped functionality that users noticed, and it was put back rather than redesigned.
With DAASH access in place and the query surface unified, the next work is most likely more sequence-domain coverage and follow-up fixes to the batched query paths introduced in 1.0.1.
mlr3cmprsk extends mlr3 to competing-risks analysis: learners predicting cumulative incidence functions, plus measures to score them. It appeared in February 2026 and reached 0.0.5 by April, adding a Fine-Gray learner and a Brier score along the way. The version numbers say pre-release; the cadence says active build-out.
The package assembled a working evaluation stack fast. It started with the Aalen-Johansen estimator as a non-parametric baseline, added Fine-Gray as a regression alternative, then filled in the scoring side with an AUC refactor and a fixed-time Brier score. Development has run in lockstep with survdistr and mlr3extralearners, which picked up the dependency at 1.5.2.
The visible gaps are more learners — cause-specific Cox and boosting variants — and the tuning and pipeline integration the rest of mlr3 expects; the measure side currently looks further along than the model side.
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 DataSpaceR or mlr3cmprsk.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all DataSpaceR alternatives → · See all mlr3cmprsk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. DataSpaceR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DataSpaceR 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.
Top DataSpaceR alternatives in Analytics are ranked by recent ship velocity. Browse the "DataSpaceR alternatives" section above for the current picks, or visit /alternatives/dataspacer for the full list with editorial commentary on each.
Top mlr3cmprsk alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3cmprsk alternatives" section above for the current picks, or visit /alternatives/mlr3cmprsk for the full list with editorial commentary on each.