trackeR
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
A side-by-side editorial comparison of BAS and ncmR — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Three weeks from first CRAN submission to a point-and-click neutral community model
ncmR fits the neutral community model to microbiome and ecological abundance data. The whole feed is three weeks long: fit_ncm() and summary methods at 0.1.0 on 1 April, a scatter plot with fitted curve and confidence interval at 0.2.0, then a Shiny application wrapping both at 0.3.0, then a row-name bugfix. It is a new package moving fast in its first month.
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.
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.
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.
ncmR fits the neutral community model to microbiome and ecological abundance data. The whole feed is three weeks long: fit_ncm() and summary methods at 0.1.0 on 1 April, a scatter plot with fitted curve and confidence interval at 0.2.0, then a Shiny application wrapping both at 0.3.0, then a row-name bugfix. It is a new package moving fast in its first month.
The direction is toward users who do not write R. Version 0.2.0 added plotting, 0.3.0 wrapped fitting and plotting in Shiny modules, and the same release deleted the Unicode plotting helpers introduced one version earlier because the dependency they existed for was removed. That willingness to throw away a week-old API suggests the surface is still being negotiated rather than settled.
With a fitting module and a plotting module in the app, the remaining gap is getting results back out — export of fitted parameters or figures from the Shiny session. The bugfix at 0.3.1 was in file upload, which is where a GUI's problems usually start.
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 ncmR.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
State-panel tooling holding steady since its 2020 data and ergonomics release.
Five years of compiler and CRAN fixes on a capture-recapture package.
A first release that turns meta-analytic heterogeneity into interpretable subgroups.
A meta-analysis toolkit still renaming its own API as it adds effect sizes.
Recurrent-event modelling settles, with mean_no() promoted to stable.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. BAS and ncmR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BAS and ncmR 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.
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.
Top ncmR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ncmR alternatives" section above for the current picks, or visit /alternatives/ncmr for the full list with editorial commentary on each.