← Back to home
Comparison · Infra & APIs

inlabru vs Nematode

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

inlabru vs Nematode: at a glance

FeatureinlabruNematode
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationsoil-ecology, nematodes, community-indices, reference-data
Last editorial update3h 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 Nematode?

A nematode ecology toolbox whose last two releases corrected the arithmetic in its own indices.

Nematode packages the standard soil-nematode community indices — maturity, enrichment, structure and channel indices, trophic diversity, plant parasite index — alongside ordination helpers and a bundled taxonomy and traits dataset drawn from Nemaplex. The visible history is short: a large function drop in 0.2.0, then a run of releases correcting formulas and refreshing the reference data.

Read the full Nematode trajectory →

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

N
Nematode
INFRA · APIS
0.0

A nematode ecology toolbox whose last two releases corrected the arithmetic in its own indices.

◆ Current state

Nematode packages the standard soil-nematode community indices — maturity, enrichment, structure and channel indices, trophic diversity, plant parasite index — alongside ordination helpers and a bundled taxonomy and traits dataset drawn from Nemaplex. The visible history is short: a large function drop in 0.2.0, then a run of releases correcting formulas and refreshing the reference data.

◆ Where it's heading

Two of the four documented releases fix a formula in an index the package already shipped — the Species Richness Index in 0.2.1 and a missing division by two in the Functional Metabolic Footprints calculation in 0.3.1 — and the 0.2.1 note tells users their earlier values were wrong. That, more than the feature additions, is what the feed records. The other thread is keeping the bundled taxonomy current against Nemaplex, which grew the genus table from 2,484 to 2,524 entries and the body-mass table from 987 to 1,094 in March.

◆ Prediction

Given the pattern of index formulas being corrected after release, further verification of the remaining indices against their source publications is the likeliest next work. The Nemaplex datasets carry a revision date and are refreshed on the upstream schedule, so another data update is the other predictable item.

Alternatives to inlabru and Nematode

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

See all inlabru alternatives → · See all Nematode alternatives →

Recent activity from inlabru and Nematode

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 1mo agoNematodeMissing division by two fixed in Functional Metabolic Footprints
  3. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  4. 4mo agoNematodecp_rel_abundance() added
  5. 4mo agoNematodeNemaplex taxonomy and body-mass datasets refreshed
  6. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  7. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  8. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack

Frequently asked questions

What is the difference between inlabru and Nematode?

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

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

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