pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of BAS and multimark — 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.
Five years of compiler and CRAN fixes on a capture-recapture package.
multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.
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.
multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.
This is preservation rather than development. The one substantive entry, in 2021, corrected an MCMC error in multimarkClosedSCR() serious enough that the author told users to revisit past analyses; everything since has been keeping the C code compiling across platforms. Release intervals now stretch to years.
Expect the pattern to hold, with a release whenever a toolchain or upstream dependency forces one and no change to the samplers.
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 multimark.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all BAS alternatives → · See all multimark alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcmc — within Infra & APIs. BAS and multimark 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 multimark 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 multimark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "multimark alternatives" section above for the current picks, or visit /alternatives/multimark for the full list with editorial commentary on each.