rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of massProps and smam — 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.
Animal-movement models in R, where new stochastic processes arrive years apart.
smam fits statistical models of animal movement, covering moving-resting processes with and without measurement error, moving-resting-handling, and moving-moving processes, with simulation, point estimation and variance estimation for each. The last three releases are pure upkeep: guarding Rf_error calls after an Rcpp update, a maintainer email change, and a compiler warning fix. The substantive work in this window is 0.7.0, which added estimate and vcov generics across all fit functions, and 0.6.0, which added the moving-moving process.
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.
smam fits statistical models of animal movement, covering moving-resting processes with and without measurement error, moving-resting-handling, and moving-moving processes, with simulation, point estimation and variance estimation for each. The last three releases are pure upkeep: guarding Rf_error calls after an Rcpp update, a maintainer email change, and a compiler warning fix. The substantive work in this window is 0.7.0, which added estimate and vcov generics across all fit functions, and 0.6.0, which added the moving-moving process.
This package grows by adding process models, and it does so rarely. Between the moving-moving process in 2021 and now, the only interface-level change has been the 0.7.0 generics that gave every fit function a common way to retrieve estimates and their covariance, which is consolidation of an accumulated collection rather than expansion of it. The three releases since are entirely reactive to toolchain and CRAN pressure, and they arrive in step with the maintainer's other package coga, which received the same Rcpp guard within twenty minutes on the same day.
Expect further releases to be CRAN and Rcpp maintenance unless a new movement process is published, which is what has historically prompted a minor version here. The generics added in 0.7.0 give any future process model a ready-made interface to slot into.
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 smam.
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 smam 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 smam 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 smam 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 smam alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "smam alternatives" section above for the current picks, or visit /alternatives/smam for the full list with editorial commentary on each.