← Back to home
Comparison · Infra & APIs

BAS vs CptNonPar

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

BAS vs CptNonPar: at a glance

FeatureBASCptNonPar
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesbayesian-statistics, model-averaging, mcmc, r-packagechange-point-detection, nonparametric, defaults, preprocessing
Last editorial update1h ago46m 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 CptNonPar?

Nonparametric change point detection swaps p-values for importance scores.

CptNonPar implements nonparametric MOJO change point detection for possibly multivariate, serially dependent data, through single-lag, multi-lag and multiscale entry points. Recent releases concern how results are reported and how data is preprocessed rather than new detection machinery. The underlying method was accepted at Biometrika during the 0.3.0 cycle.

Read the full CptNonPar trajectory →

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

C
CptNonPar
INFRA · APIS
0.0

Nonparametric change point detection swaps p-values for importance scores.

◆ Current state

CptNonPar implements nonparametric MOJO change point detection for possibly multivariate, serially dependent data, through single-lag, multi-lag and multiscale entry points. Recent releases concern how results are reported and how data is preprocessed rather than new detection machinery. The underlying method was accepted at Biometrika during the 0.3.0 cycle.

◆ Where it's heading

The package is tightening the statistical interface it exposes: p-values gave way to importance scores across all three detection functions, manual thresholds became specifiable per lag, and the latest release makes centring and scaling the default preprocessing step. Each change folds a decision the user previously had to make into the package itself.

◆ Prediction

Expect further work on defaults and reporting around the existing MOJO estimators rather than a new detection method.

Alternatives to BAS and CptNonPar

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

See all BAS alternatives → · See all CptNonPar alternatives →

Recent activity from BAS and CptNonPar

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

  1. 8mo agoBASBAS 2.0.2
  2. 8mo agoBASBAS 2.0.0
  3. 8mo agoCptNonParData centred and scaled by default before detection
  4. 1y agoCptNonParImportance scores replace p-values; per-lag manual thresholds
  5. 1y agoBASBAS 1.7.5
  6. 1y agoBASBAS 1.7.3
  7. 1y agoBASBAS 1.7.2
  8. 2y agoCptNonParPaper link updated for CRAN checks
  9. 2y agoBASBAS 1.7.1
  10. 3y agoCptNonParDescription field and example cleanups

Frequently asked questions

What is the difference between BAS and CptNonPar?

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

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

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