← Back to home
Comparison · Infra & APIs

inlabru vs mdatools

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

inlabru vs mdatools: at a glance

Featureinlabrumdatools
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationchemometrics, spectroscopy, classification, multiway-analysis
Last editorial update2h ago44m 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 mdatools?

mdatools spun out its cross-validation method, then came back for three-way data.

mdatools is a long-running chemometrics package covering PCA, PLS regression, SIMCA and DD-SIMCA classification, MCR resolution and a large spectral preprocessing framework. Its releases are infrequent and each one tends to carry one substantive idea plus a handful of fixes. The June release opens a direction the package had not previously taken: DD-SIMCA classification of three-way data, through PARAFAC and Tucker decompositions.

Read the full mdatools trajectory →

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

M
mdatools
INFRA · APIS
0.0

mdatools spun out its cross-validation method, then came back for three-way data.

◆ Current state

mdatools is a long-running chemometrics package covering PCA, PLS regression, SIMCA and DD-SIMCA classification, MCR resolution and a large spectral preprocessing framework. Its releases are infrequent and each one tends to carry one substantive idea plus a handful of fixes. The June release opens a direction the package had not previously taken: DD-SIMCA classification of three-way data, through PARAFAC and Tucker decompositions.

◆ Where it's heading

The shape of the package has been managed deliberately rather than allowed to sprawl. Procrustes cross-validation grew large enough to warrant its own package and was moved out to pcv in 0.14.0; preprocessing was consolidated in 0.12.0 into a composable prep() framework rather than a set of loose functions. Around that, the recurring work is numerical: a more stable SIMPLS implementation, cross-validation rewritten to accept user-supplied segment indices, prep.savgol() and prep.alsbasecorr() rewritten for speed, and now the baseline iteration default raised to match the web applications the maintainer also runs.

◆ Prediction

Three-way DD-SIMCA arrives with two decompositions and no companion regression or resolution methods for multiway data, so extending the multiway path to the rest of the toolkit is the obvious follow-up. The alignment of defaults with the maintainer's web applications suggests those two codebases will keep being reconciled.

Alternatives to inlabru and mdatools

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

See all inlabru alternatives → · See all mdatools alternatives →

Recent activity from inlabru and mdatools

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 1mo agomdatoolsDD-SIMCA classification arrives for three-way data
  3. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  4. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  5. 5mo agomdatoolsv. 0.15.0
  6. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  7. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  8. 2y agomdatoolsData frames converted to matrices automatically for model training
  9. 3y agomdatoolscv.scope lets centering and scaling follow the global or local set
  10. 3y agomdatoolsProcrustes cross-validation moves out to its own pcv package
  11. 3y agomdatoolsgetRegcoeffs() fixed for unscaled models; ipls() gains a full mode

Frequently asked questions

What is the difference between inlabru and mdatools?

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

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

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