rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of midr and remap — release velocity, themes, recent moves, and the top alternatives to consider.
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
midr explains black-box models by fitting an interpretable surrogate through Maximum Interpretation Decomposition — main effects plus second-order interactions, with exact Shapley values for the surrogate. Two months after its first CRAN release it can take a matrix response, which covers multi-class classification and survival models, and hold collections of fitted interpretations in midlist and midrib objects for comparison.
A regional-model smoother in long-term maintenance, four years past its last real feature.
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
midr explains black-box models by fitting an interpretable surrogate through Maximum Interpretation Decomposition — main effects plus second-order interactions, with exact Shapley values for the surrogate. Two months after its first CRAN release it can take a matrix response, which covers multi-class classification and survival models, and hold collections of fitted interpretations in midlist and midrib objects for comparison.
The releases move outward along two axes at once: what can be interpreted, and how much of it fits in memory. Version 0.5.3 rebuilt the fitting path to avoid materialising large design matrices and added a save.memory option; 0.6.0 widened the response from a vector to a matrix and added parametric link functions. Class and argument names were shortened in the same release, so the package is still willing to break itself this early.
With multiple models now held in one object and visualisation methods for them, comparison across models is the surface most likely to fill out next — the collection classes exist but the notes describe manipulation and plotting rather than any comparison metric.
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
This is a stable academic package tracking its ecosystem rather than growing. The visible pattern is reactive maintenance: sf's 1.0.0 transition, ggplot2's size-to-linewidth rename, a gcc-UBSAN error on zero-point distance calculations, and now a check that distance matrices passed to remap() and predict() are converted to kilometres. Note that the feed's timestamps invert the version order — 0.3.1 is stamped seconds after 0.3.2 despite being the earlier release, so recency in this feed is not a reliable guide to sequence.
Nothing in these entries points to new capability. The realistic expectation is more of the same: a patch whenever sf, ggplot2 or a CRAN check surfaces an incompatibility, at roughly the observed cadence of one release every year or two.
Other Infra & APIs 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 midr or remap.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
Spatial thinning grows a result object, and the API breaks to make room for it
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. midr and remap 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. midr and remap 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 Infra & APIs products to evaluate alongside.
Top midr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "midr alternatives" section above for the current picks, or visit /alternatives/midr for the full list with editorial commentary on each.
Top remap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "remap alternatives" section above for the current picks, or visit /alternatives/remap for the full list with editorial commentary on each.