← Back to home
Comparison · Infra & APIs

inlabru vs TrendLSW

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

inlabru vs TrendLSW: at a glance

FeatureinlabruTrendLSW
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationtime-series, wavelets, defaults, plotting
Last editorial update5h ago54m 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 TrendLSW?

Wavelet trend estimation tightens the defaults it shipped with.

TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.

Read the full TrendLSW trajectory →

inlabru vs TrendLSW: 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
TrendLSW
INFRA · APIS
0.0

Wavelet trend estimation tightens the defaults it shipped with.

◆ Current state

TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.

◆ Where it's heading

The package has moved from getting onto CRAN to correcting the choices it launched with: the spectrum filter defaults were swapped to their trend counterparts, the plot.CI switch was removed in favour of inferring it from what was actually computed, and an example was shrunk to fit check timings. This is consolidation around a stable API rather than expansion.

◆ Prediction

Further releases most likely continue tuning TLSW() defaults and plot behaviour; the entries show no work toward new estimators.

Alternatives to inlabru and TrendLSW

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

See all inlabru alternatives → · See all TrendLSW alternatives →

Recent activity from inlabru and TrendLSW

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. 8mo agoTrendLSWTrend filter defaults replace spectrum defaults; plot.CI dropped
  5. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  6. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  7. 2y agoTrendLSWNew z.acc and z.labels datasets shipped with the package
  8. 2y agoTrendLSWDescription field and plot.TLSW documentation fixes

Frequently asked questions

What is the difference between inlabru and TrendLSW?

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

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

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