massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
Comparison · Infra & APIs
rollupTree vs traumar
A side-by-side editorial comparison of rollupTree and traumar — release velocity, themes, recent moves, and the top alternatives to consider.
rollupTree vs traumar: 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 traumar?
Trauma registry statistics in R, tightening the numbers it reports against the literature.
traumar computes trauma-centre performance measures from registry data, including relative mortality metrics, SEQIC quality indicators and predicted survival probability. The recent releases are dominated by correctness rather than coverage: 1.2.5 changed how the denominator for SEQIC indicator 7 is derived so it reflects the definitive care population rather than a raw row count, and 1.2.3 realigned probability_of_survival() with published coefficients. Version 1.2.6 completes a deprecation, turning the old n_decimal argument into an error.
rollupTree vs traumar: 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.
traumar
0.0INFRA · APIS
Trauma registry statistics in R, tightening the numbers it reports against the literature.
◆ Current state
traumar computes trauma-centre performance measures from registry data, including relative mortality metrics, SEQIC quality indicators and predicted survival probability. The recent releases are dominated by correctness rather than coverage: 1.2.5 changed how the denominator for SEQIC indicator 7 is derived so it reflects the definitive care population rather than a raw row count, and 1.2.3 realigned probability_of_survival() with published coefficients. Version 1.2.6 completes a deprecation, turning the old n_decimal argument into an error.
◆ Where it's heading
This is a package whose outputs are reported numbers, and it is behaving accordingly: the notable changes in this window alter results rather than add features. A denominator computed as a row count instead of a filtered population, and a survival calculation not matching the coefficients it cites, are both the kind of defect that quietly propagates into published figures, and both were corrected here. Around that sit in-house validation helpers written deliberately to avoid a new dependency, and a steady tidy-up of tests and tooling.
◆ Prediction
Expect the validation family introduced in 1.2.4 to be applied more widely across the package's entry points, now that it exists and is deliberately kept internal. Further SEQIC indicators being reviewed against their definitions looks likely given indicator 7 needed it, though the entries name no specific one as next.
Alternatives to rollupTree and traumar
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 traumar.
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 traumar alternatives →
Recent activity from rollupTree and traumar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agotraumarn_decimal deprecation completed; percentages allow negatives
- 3mo agotraumarSEQIC indicator 7 denominator corrected to definitive care
- 6mo agorollupTreeMissing column names in the new row setters
- 6mo agotraumarIn-house validation family added to avoid a dependency
- 6mo agorollupTreeRow-level get and set accessors by key and by id
- 7mo agotraumarSurvival probability realigned with published coefficients
- 7mo agotraumarBinning and survival documentation clarified
- 1y agotraumarInternal renaming and a faster CRAN test path
- 1y agorollupTreeMinor vignette improvements
- 1y agorollupTreeBadges and GitHub Actions added to the README
- 1y agorollupTreedefault_validate_dag() extends validation past strict trees
Frequently asked questions
What is the difference between rollupTree and traumar?
They serve adjacent needs but don't currently overlap on shipped themes. rollupTree and traumar 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 traumar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rollupTree and traumar 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 traumar?
Top traumar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "traumar alternatives" section above for the current picks, or visit /alternatives/traumar for the full list with editorial commentary on each.