← Back to home
Comparison · Infra & APIs

inlabru vs traumar

A side-by-side editorial comparison of inlabru and traumar — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

inlabru vs traumar: at a glance

Featureinlabrutraumar
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationtrauma-registry, healthcare-quality, statistical-correctness, data-validation
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is inlabru?

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

Read the full inlabru trajectory →

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.

Read the full traumar trajectory →

inlabru vs traumar: editorial side-by-side

I
inlabru
INFRA · APIS
2.5

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

◆ Current state

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

◆ Where it's heading

The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.

◆ Prediction

The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.

T
traumar
INFRA · APIS
0.0

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 inlabru 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 inlabru or traumar.

See all inlabru alternatives → · See all traumar alternatives →

Recent activity from inlabru and traumar

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agotraumarn_decimal deprecation completed; percentages allow negatives
  3. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  4. 3mo agotraumarSEQIC indicator 7 denominator corrected to definitive care
  5. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  6. 6mo agotraumarIn-house validation family added to avoid a dependency
  7. 7mo agotraumarSurvival probability realigned with published coefficients
  8. 7mo agotraumarBinning and survival documentation clarified
  9. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  10. 1y agotraumarInternal renaming and a faster CRAN test path
  11. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack

Frequently asked questions

What is the difference between inlabru and traumar?

Both compete on the same themes — r-package — within Infra & APIs. inlabru 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 inlabru better than traumar?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru 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 inlabru?

Top inlabru alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inlabru alternatives" section above for the current picks, or visit /alternatives/inlabru 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.