← Back to home
Comparison · Infra & APIs

BAS vs valr

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

BAS vs valr: at a glance

FeatureBASvalr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, model-averaging, mcmc, r-packagegenomics, interval-arithmetic, bioinformatics, bigwig
Last editorial update1h ago3h 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 valr?

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

Read the full valr trajectory →

BAS vs valr: 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.

V
valr
INFRA · APIS
0.0

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

◆ Current state

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

◆ Where it's heading

Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.

◆ Prediction

Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.

Alternatives to BAS and valr

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

See all BAS alternatives → · See all valr alternatives →

Recent activity from BAS and valr

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

  1. 1mo agovalrInterval verbs read bigWig and bigBed files directly
  2. 7mo agovalrbed_slop() and bed_flank() preserve input row order
  3. 8mo agoBASBAS 2.0.2
  4. 8mo agoBASBAS 2.0.0
  5. 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
  6. 1y agovalrTest updated for ggplot2 3.6.0
  7. 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
  8. 1y agoBASBAS 1.7.5
  9. 1y agoBASBAS 1.7.3
  10. 1y agoBASBAS 1.7.2
  11. 1y agovalrCRAN Rd link NOTE and maintainer email change
  12. 2y agoBASBAS 1.7.1

Frequently asked questions

What is the difference between BAS and valr?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BAS and valr 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 valr?

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