metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of DataSpaceR and xplainfi — 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.
xplainfi treats feature importance as an estimate with error bars, not a number.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
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.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
Two lines of work run in parallel. The statistical side keeps adding inference options — variance corrections, conditional predictive impact, and the Lei et al. observation-wise loss-difference test — while the computational side attacks the cost of refit-based methods, most recently with a batch_size argument that parallelises refits and a default of one refit per resampling iteration. Support for pre-trained learners in 1.1.0 removes the refit requirement entirely in some workflows.
The stated reasoning that budget is better spent on resampling iterations than repeated refits suggests n_repeats may be removed from WVIM and LOCO outright, as the release notes hint.
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 xplainfi.
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 xplainfi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. DataSpaceR and xplainfi are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. DataSpaceR and xplainfi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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 xplainfi alternatives in Analytics are ranked by recent ship velocity. Browse the "xplainfi alternatives" section above for the current picks, or visit /alternatives/xplainfi for the full list with editorial commentary on each.