artoo
artoo makes any-to-any clinical dataset conversion lossless by construction.
Comparison · Infra & APIs
radiatR vs traumar
A side-by-side editorial comparison of radiatR and traumar — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
radiatR vs traumar: at a glance
What is radiatR?
A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.
radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.
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.
radiatR vs traumar: editorial side-by-side
radiatR
2.5INFRA · APIS
A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.
◆ Current state
radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.
◆ Where it's heading
Three releases in twelve days show a package hardening in public rather than accreting features. The direction of travel is toward refusing bad input instead of quietly working around it: non-finite coordinate rows now error by default rather than being dropped silently, combining Tracks objects rejects colliding trajectory ids and conflicting calibration metadata instead of merging them and discarding one side, and the Shiny app clears prior state before reading a new upload. The statistical surface is growing in parallel, but within the scope the first release already claimed.
◆ Prediction
Expect the remaining goodness-of-fit gap the notes name explicitly, Jones-Pewsey, to be filled in a later release, and the error-on-bad-input treatment to reach the parts of the loader it has not yet covered. A CRAN submission is the natural next step for a package this young, though nothing in these entries commits to one.
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 radiatR 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 radiatR or traumar.
tabular
tabular went from clinical tables to complete TFL output in under two months.
usmapdata
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
glcdp
glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.
prova
prova adds expected-utility calculation on top of its Bayesian inference core.
checkhelper
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
See all radiatR alternatives → · See all traumar alternatives →
Recent activity from radiatR and traumar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 29d agoradiatRctrax loader dropped; bad coordinates now error by default
- 1mo agoradiatRWrapped-Cauchy and Pycke tests close two statistical gaps
- 1mo agoradiatRFirst public release ⚡
- 3mo agotraumarn_decimal deprecation completed; percentages allow negatives
- 3mo agotraumarSEQIC indicator 7 denominator corrected to definitive care
- 6mo agotraumarIn-house validation family added to avoid a dependency
- 7mo agotraumarSurvival probability realigned with published coefficients
- 7mo agotraumarBinning and survival documentation clarified
- 1y agotraumarInternal renaming and a faster CRAN test path
Frequently asked questions
What is the difference between radiatR and traumar?
Both compete on the same themes — r-package — within Infra & APIs. radiatR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is radiatR better than traumar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. radiatR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to radiatR?
Top radiatR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "radiatR alternatives" section above for the current picks, or visit /alternatives/radiatr 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.