rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of stochvol and traumar — release velocity, themes, recent moves, and the top alternatives to consider.
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
stochvol runs MCMC for stochastic volatility models, with a C++ sampler underneath an R interface. Five years of releases in this window contain no new models: the work is compiler and dependency compatibility, CRAN check notes, and a steady trickle of corrections to the sampler itself. Its methodological milestone, the Journal of Statistical Software paper, is recorded in a 2021 tag.
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.
stochvol runs MCMC for stochastic volatility models, with a C++ sampler underneath an R interface. Five years of releases in this window contain no new models: the work is compiler and dependency compatibility, CRAN check notes, and a steady trickle of corrections to the sampler itself. Its methodological milestone, the Journal of Statistical Software paper, is recorded in a 2021 tag.
This is what a finished computational package looks like. The formula interface arrived at 3.1.0 and nothing has been added since; what changes is the ground underneath — RcppArmadillo major versions, UBSan checks, error-handling conventions moving from Rf_error to Rcpp::stop for correct memory management. The recurring pattern worth watching is that several releases fix real errors in the sampler's proposal distributions, found by users and by CRAN's own instrumented checks rather than by the maintainer.
Nothing in these notes suggests new methodology. Expect the next release when RcppArmadillo or a CRAN check flavour forces one, and treat any bug report against the samplers as the more consequential event.
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.
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.
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.
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 stochvol or traumar.
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 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 stochvol alternatives → · See all traumar alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. stochvol 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. stochvol 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.
Top stochvol alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "stochvol alternatives" section above for the current picks, or visit /alternatives/stochvol for the full list with editorial commentary on each.
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.