rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of massProps and remap — release velocity, themes, recent moves, and the top alternatives to consider.
A mass-properties rollup spends a year on documentation and follows its sibling's API
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
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.
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
Every release in the window is documentation, benchmarks, or keeping in step with rollupTree. The inertia tensor and radius-of-gyration uncertainty equations have been reformatted and re-explained three separate times, which suggests the hard part of this package is not the computation but making the covariance treatment legible to the engineers meant to trust it. Development effort clearly sits in the engine underneath, not here.
The pattern is unambiguous: rollupTree ships an API change and massProps follows within a fortnight. Whatever the engine does next is what appears here next, and on this evidence it will arrive as a one-line release note.
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 massProps or remap.
The recursive-computation engine under massProps grows the accessors its consumer needed
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
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
Spatial thinning grows a result object, and the API breaks to make room for it
See all massProps alternatives → · See all remap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. massProps 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. massProps 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 massProps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "massProps alternatives" section above for the current picks, or visit /alternatives/massprops 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.