Tplyr
Tplyr made clinical summary tables explain where every number came from.
A side-by-side editorial comparison of mlr3spatial and tidytlg — release velocity, themes, recent moves, and the top alternatives to consider.
Raster prediction in mlr3 finally returns class probabilities, not just hard labels.
mlr3spatial connects mlr3 learners to raster and vector spatial data, handling chunked prediction over large rasters through DataBackendRaster. Development is slow and fix-heavy: most releases in the last two years were compatibility work against mlr3 and paradox rather than new capability. 0.7.0 is the exception.
A tables-listings-graphs package that reached CRAN and then went quiet.
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
mlr3spatial connects mlr3 learners to raster and vector spatial data, handling chunked prediction over large rasters through DataBackendRaster. Development is slow and fix-heavy: most releases in the last two years were compatibility work against mlr3 and paradox rather than new capability. 0.7.0 is the exception.
The package tracks the mlr3 core rather than leading it — 0.5.0 and 0.6.1 exist to absorb upstream changes in paradox and mlr3. Against that background, 0.7.0 adding probability predictions to predict_spatial() is the first genuine capability increase in a while, arriving alongside two DataBackendRaster fixes for multi-band sources and similarly-named layers. Cadence is roughly one release per year.
Given the pattern, the next release is more likely to be compatibility work against a new mlr3 or terra version than another feature; further raster-backend edge cases around layer naming are the visible loose end.
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
The visible arc is getting onto CRAN and staying installable — vignette corrections per CRAN comments, a badge, a check fix, and replacing the timber logging package with logrx. The one functional addition is multiple-file support. There has been no release since October 2023, so on this evidence the package is stable or dormant rather than actively developing.
The entries give no signal about planned work; with nothing shipped in roughly two years, the more likely next event is a maintenance release triggered by a dependency or CRAN check than a feature.
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 mlr3spatial or tidytlg.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all mlr3spatial alternatives → · See all tidytlg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mlr3spatial and tidytlg 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. mlr3spatial and tidytlg 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 mlr3spatial alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3spatial alternatives" section above for the current picks, or visit /alternatives/mlr3spatial for the full list with editorial commentary on each.
Top tidytlg alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytlg alternatives" section above for the current picks, or visit /alternatives/tidytlg for the full list with editorial commentary on each.