← Back to home
Comparison · Infra & APIs

inlabru vs JointFPM

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

inlabru vs JointFPM: at a glance

FeatureinlabruJointFPM
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationsurvival-analysis, recurrent-events, parametric-models, api-stability
Last editorial update6h ago1h 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 JointFPM?

Recurrent-event modelling settles, with mean_no() promoted to stable.

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

Read the full JointFPM trajectory →

inlabru vs JointFPM: 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.

J
JointFPM
INFRA · APIS
0.0

Recurrent-event modelling settles, with mean_no() promoted to stable.

◆ Current state

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

◆ Where it's heading

The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.

◆ Prediction

With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.

Alternatives to inlabru and JointFPM

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 JointFPM.

See all inlabru alternatives → · See all JointFPM alternatives →

Recent activity from inlabru and JointFPM

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  3. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  4. 1y agoJointFPMmean_no() promoted to a stable interface
  5. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  6. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  7. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  8. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  9. 2y agoJointFPMStandardized marginal estimates plus input validation
  10. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between inlabru and JointFPM?

They serve adjacent needs but don't currently overlap on shipped themes. 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 JointFPM?

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 JointFPM?

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