vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of mmpca and multimark — release velocity, themes, recent moves, and the top alternatives to consider.
Back from CRAN removal under a new maintainer, with the compiled layer rebuilt.
mmpca implements multiple matrix principal component analysis with a compiled GSL backend. The package spent time off CRAN, and its recent history is a rescue operation rather than a feature program: a new maintainer took it over, moved the native build path onto RcppGSL, and folded the hand-written C bindings into Rcpp. The two most recent entries landed the same day, one restoring the package and one clearing residual CRAN comments.
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.
mmpca implements multiple matrix principal component analysis with a compiled GSL backend. The package spent time off CRAN, and its recent history is a rescue operation rather than a feature program: a new maintainer took it over, moved the native build path onto RcppGSL, and folded the hand-written C bindings into Rcpp. The two most recent entries landed the same day, one restoring the package and one clearing residual CRAN comments.
Work is concentrated on making the package installable and check-clean rather than on the decomposition itself. The version stamps run out of order, with 2.0.3 predating both 2.0.2 and 2.0.4 by three years, so the feed reads as an archive flush around the CRAN return. Nothing in the entries points at method-level work.
Expect maintenance releases that keep the compiled code passing CRAN checks; the entries give no signal about new decomposition features.
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 mmpca or multimark.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all mmpca alternatives → · See all multimark alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — cran — within Infra & APIs. mmpca 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. mmpca 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 mmpca alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mmpca alternatives" section above for the current picks, or visit /alternatives/mmpca 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.