massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
Comparison · Infra & APIs
rollupTree vs ShortForm
A side-by-side editorial comparison of rollupTree and ShortForm — release velocity, themes, recent moves, and the top alternatives to consider.
rollupTree vs ShortForm: at a glance
What is rollupTree?
The recursive-computation engine under massProps grows the accessors its consumer needed
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
What is ShortForm?
Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.
ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.
rollupTree vs ShortForm: editorial side-by-side
rollupTree
0.0INFRA · APIS
The recursive-computation engine under massProps grows the accessors its consumer needed
◆ Current state
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
◆ Where it's heading
The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.
◆ Prediction
On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.
ShortForm
0.0INFRA · APIS
Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.
◆ Current state
ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.
◆ Where it's heading
The defects being fixed are in the search itself rather than around it. An optimizer that does not correctly retain its best candidate, and a search that mis-specifies models after the first iteration, both produce plausible-looking short forms that are not the ones the method should have found, which is a harder class of problem to notice than a crash. Alongside that the package is shedding dependencies, with ggplot2, ggrepel and tidyr dropped from the plotting methods in 0.5.8. The stated intent to refactor the major functions and standardise their arguments suggests the maintainer regards the current interface as the obstacle to further work.
◆ Prediction
The roadmap repeated across these notes points to a 0.6.0 focused on refactoring the major functions, with argument and output standardisation deferred to 0.7.0. On the evidence of this window, more unit tests and further algorithm-level fixes are likelier to arrive first than either milestone.
Alternatives to rollupTree and ShortForm
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 rollupTree or ShortForm.
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
GeoThinneR
Spatial thinning grows a result object, and the API breaks to make room for it
See all rollupTree alternatives → · See all ShortForm alternatives →
Recent activity from rollupTree and ShortForm
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoShortFormTabu search fixed for parallel and multidimensional models
- 3mo agoShortFormAnt colony search failed to retain its best model
- 6mo agorollupTreeMissing column names in the new row setters
- 6mo agorollupTreeRow-level get and set accessors by key and by id
- 1y agorollupTreeMinor vignette improvements
- 1y agorollupTreeBadges and GitHub Actions added to the README
- 1y agorollupTreedefault_validate_dag() extends validation past strict trees
- 1y agoShortFormlavaan model specification defaults made forgiving
- 2y agoShortFormCompatibility fixes for a new lavaan release
- 2y agoShortFormAdapted to changed lavaan error and warning messages
- 2y agoShortFormDefault specification tweaks and documentation fixes
Frequently asked questions
What is the difference between rollupTree and ShortForm?
They serve adjacent needs but don't currently overlap on shipped themes. rollupTree and ShortForm 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.
Is rollupTree better than ShortForm?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rollupTree and ShortForm 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.
What are the best alternatives to rollupTree?
Top rollupTree alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rollupTree alternatives" section above for the current picks, or visit /alternatives/rolluptree for the full list with editorial commentary on each.
What are the best alternatives to ShortForm?
Top ShortForm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ShortForm alternatives" section above for the current picks, or visit /alternatives/shortform for the full list with editorial commentary on each.