metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of DataSpaceR and mlr3fda — 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.
A functional-data feature factory for mlr3, shipping a new extractor almost every month.
mlr3fda adds functional data support to mlr3 pipelines through PipeOps that turn functional columns into tabular features. Five releases since March 2026 have taken it from Fourier features to a catalogue covering wavelets, derivatives, depth, registration, integration and the catch22 time-series feature set. Development tracks the {tf} package closely.
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.
mlr3fda adds functional data support to mlr3 pipelines through PipeOps that turn functional columns into tabular features. Five releases since March 2026 have taken it from Fourier features to a catalogue covering wavelets, derivatives, depth, registration, integration and the catch22 time-series feature set. Development tracks the {tf} package closely.
The pattern is one or two new PipeOps per release with fixes to the previous batch alongside — Fourier in 0.4.0, registration in 0.5.0, depth and derivatives in 0.6.0, catch22 and integration in 0.7.0. Performance and parallel-safety work is folded in as it becomes necessary rather than deferred, as with the Fourier speedup and the mlr_reflections registration fix.
The extraction catalogue is filling out along established functional-data methods, so further tf-backed PipeOps are the likely next additions; the {tf} 0.5.0 compatibility release suggests upstream churn will keep setting the pace.
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 mlr3fda.
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 mlr3fda 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 mlr3fda 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 mlr3fda 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 mlr3fda alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3fda alternatives" section above for the current picks, or visit /alternatives/mlr3fda for the full list with editorial commentary on each.