← Back to home
Comparison · Infra & APIs

BAS vs TrendLSW

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

BAS vs TrendLSW: at a glance

FeatureBASTrendLSW
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, model-averaging, mcmc, r-packagetime-series, wavelets, defaults, plotting
Last editorial update1h ago35m ago
WebsiteVisit →Visit →

What is BAS?

A Bayesian model-averaging package spending its 2.0 on memory, not methods.

BAS performs Bayesian variable selection and model averaging for linear and generalized linear models, sampling from a model space too large to enumerate. The visible history splits cleanly: 2023-2024 added sampling machinery — an adaptive independent MCMC sampler with Horvitz-Thompson estimation, hereditary-constraint counting — while 2.0.0 in late 2025 reworked how sampler output is allocated in C. The 2.0.2 patch is a PROTECT fix for rchk warnings.

Read the full BAS 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 →

BAS vs TrendLSW: editorial side-by-side

B
BAS
INFRA · APIS
0.0

A Bayesian model-averaging package spending its 2.0 on memory, not methods.

◆ Current state

BAS performs Bayesian variable selection and model averaging for linear and generalized linear models, sampling from a model space too large to enumerate. The visible history splits cleanly: 2023-2024 added sampling machinery — an adaptive independent MCMC sampler with Horvitz-Thompson estimation, hereditary-constraint counting — while 2.0.0 in late 2025 reworked how sampler output is allocated in C. The 2.0.2 patch is a PROTECT fix for rchk warnings.

◆ Where it's heading

Memory is the binding constraint and the releases say so directly. The hereditary-constraint counter, the GROW option, and the replacement of over-allocation with resizing all attack the same problem: n.models is a guess, and guessing high wastes memory on problems where few unique models are actually visited. The 2.0.0 work was additionally forced by R tightening its C API against non-API calls like SETLENGTH, a constraint every C-heavy CRAN package has been absorbing. Method development has been quiet since 1.7.x.

◆ Prediction

The 1.7.5 notes call the hereditary-constraint counting a first step and say future updates will cover other constraint types, including polynomials, which remain unhandled. That is the one concrete commitment in this history, though nothing since has returned to it.

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

See all BAS alternatives → · See all TrendLSW alternatives →

Recent activity from BAS and TrendLSW

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

  1. 8mo agoBASBAS 2.0.2
  2. 8mo agoBASBAS 2.0.0
  3. 8mo agoTrendLSWTrend filter defaults replace spectrum defaults; plot.CI dropped
  4. 1y agoBASBAS 1.7.5
  5. 1y agoBASBAS 1.7.3
  6. 1y agoBASBAS 1.7.2
  7. 2y agoTrendLSWNew z.acc and z.labels datasets shipped with the package
  8. 2y agoTrendLSWDescription field and plot.TLSW documentation fixes
  9. 2y agoBASBAS 1.7.1

Frequently asked questions

What is the difference between BAS and TrendLSW?

They serve adjacent needs but don't currently overlap on shipped themes. BAS and TrendLSW are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 BAS better than TrendLSW?

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

Top BAS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BAS alternatives" section above for the current picks, or visit /alternatives/bas 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.