← Back to home
Comparison · Infra & APIs

campsismod vs inlabru

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

Shared themes:api-consolidation

campsismod vs inlabru: at a glance

Featurecampsismodinlabru
SectorInfra & APIsInfra & APIs
Velocity score2.52.5
Sparks · 30d00
Top themespharmacometrics, model-objects, json-interface, api-consolidationbayesian-modelling, spatial-statistics, r-package, api-consolidation
Last editorial update1h ago34m ago
WebsiteVisit →Visit →

What is campsismod?

The model layer under Campsis, renamed in step with it and increasingly JSON-addressable.

Campsismod holds the model object layer for the Campsis pharmacometric simulation suite: reading, editing and writing model definitions that Campsis then simulates. Its recent releases track a single programme, adding a JSON route into model objects and then renaming the whole API to snake_case in 1.4.0, a week before Campsis 1.9.0 did the same. Release notes are terse issue lists, so the reasoning behind each change has to be read from the sibling package.

Read the full campsismod trajectory →

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 →

campsismod vs inlabru: editorial side-by-side

C
campsismod
INFRA · APIS
2.5

The model layer under Campsis, renamed in step with it and increasingly JSON-addressable.

◆ Current state

Campsismod holds the model object layer for the Campsis pharmacometric simulation suite: reading, editing and writing model definitions that Campsis then simulates. Its recent releases track a single programme, adding a JSON route into model objects and then renaming the whole API to snake_case in 1.4.0, a week before Campsis 1.9.0 did the same. Release notes are terse issue lists, so the reasoning behind each change has to be read from the sibling package.

◆ Where it's heading

This package moves when Campsis needs it to move. The JSON constructor landed here in 1.3.0 and reached Campsis datasets a day later; parameter uncertainty generation was handed down from Campsis in that package's 1.6.0; and the snake_case migration started here before propagating up. That ordering makes Campsismod the place where suite-wide interface decisions are taken first, even though the visible payoff shows up in Campsis.

◆ Prediction

Expect Campsismod to keep absorbing model-level responsibilities that Campsis currently handles, and to extend the JSON mapping to whatever parts of the model object it does not yet cover. The entries give no signal on a 2.0, and with the rename already spent there is little reason to expect one soon.

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.

Alternatives to campsismod and inlabru

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

See all campsismod alternatives → · See all inlabru alternatives →

Recent activity from campsismod and inlabru

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

  1. 21d agocampsismodsnake_case migration lands here first
  2. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  3. 3mo agocampsismodBundled model suite refreshed
  4. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  5. 5mo agocampsismodJSON argument added to the CampsisModel constructor
  6. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  7. 7mo agocampsismodJSON import for Campsis models
  8. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  9. 1y agocampsismodreplaceAll fixed for unrecognised statements
  10. 1y agocampsismodPerformance tests skipped on CRAN
  11. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack

Frequently asked questions

What is the difference between campsismod and inlabru?

Both compete on the same themes — api-consolidation — within Infra & APIs. campsismod and inlabru are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 campsismod better than inlabru?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. campsismod and inlabru are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 campsismod?

Top campsismod alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "campsismod alternatives" section above for the current picks, or visit /alternatives/campsismod for the full list with editorial commentary on each.

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.