pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of multimark and serocalculator — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A seroincidence engine grows up: whole API renamed, then clustered survey designs
serocalculator turns cross-sectional antibody measurements into infection-rate estimates, and it spent its last two releases making itself safe to depend on. Version 1.4.0 renamed nearly every user-facing function into a consistent est_seroincidence()/sr_params vocabulary; 1.4.1 shipped the migration crosswalk that admits how much that broke. The newest capability is cluster-robust variance estimation for household- and school-based surveys.
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.
serocalculator turns cross-sectional antibody measurements into infection-rate estimates, and it spent its last two releases making itself safe to depend on. Version 1.4.0 renamed nearly every user-facing function into a consistent est_seroincidence()/sr_params vocabulary; 1.4.1 shipped the migration crosswalk that admits how much that broke. The newest capability is cluster-robust variance estimation for household- and school-based surveys.
The arc runs from method to instrument. Early releases added example data and plotting; recent ones fix the API surface, satisfy CRAN's offline-failure policy, and extend the estimator to sampling designs field epidemiology actually uses — multi-level clustering, stratification, and the two combined. Each release also carries visible refactoring discipline (one function per file, linting, per-PR website previews) that reads like a package preparing for contributors it does not have yet.
With cluster_var and stratum_var now threaded through both est_seroincidence() and est_seroincidence_by(), survey weights are the remaining piece of a complex-survey design the sandwich estimator does not cover. The entries do not name it, so read that as direction rather than a promise.
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 multimark or serocalculator.
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 multimark alternatives → · See all serocalculator alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. multimark and serocalculator 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. multimark and serocalculator 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 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.
Top serocalculator alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "serocalculator alternatives" section above for the current picks, or visit /alternatives/serocalculator for the full list with editorial commentary on each.