pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of jSDM and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
jSDM fits joint species distribution models by Gibbs sampling, with the sampler written in C++ against GSL and Armadillo and exposed through binomial probit, binomial logit, Poisson log and Gaussian entry points. The 0.2 line extended it with species traits, constrained factor loadings and residual-association plots. The one entry since 2023 carries only a compare link.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
jSDM fits joint species distribution models by Gibbs sampling, with the sampler written in C++ against GSL and Armadillo and exposed through binomial probit, binomial logit, Poisson log and Gaussian entry points. The 0.2 line extended it with species traits, constrained factor loadings and residual-association plots. The one entry since 2023 carries only a compare link.
The package built out its model family quickly and then stopped: five of the six visible entries are stamped the same day as a backfilled archive, and the only later release says nothing about its contents. The direction the 0.2 line was heading, toward trait-mediated species effects and better convergence on latent variable models, has no visible continuation.
The feed does not support a confident prediction; the latest entry publishes no notes, so whether the package is still developing or only being kept CRAN-clean cannot be read from it.
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
The package has been moving from a fixed snapshot toward versioned, user-selectable data. Earlier releases updated the bundled database in place — 1.0.0 shipped the March 2025 version and said little else — which meant the annotation vintage was whatever the package version implied. Now update_peiman_database() downloads and caches external database files and UniProt PTM lists, enrichment workflows take a database_version argument, and the mass-spec translators take a ptmlist_version, so an analysis can pin a dated database rather than a package release. The CRAN-safe default is preserved deliberately: loading, examples and checks still use the bundled internal data and need no network.
Version pinning is now expressible but the release notes do not describe how a chosen version is recorded in output, so surfacing the active database version in results is the natural companion. The database and the UniProt PTM list are versioned separately, which leaves room for a combined manifest.
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 jSDM or PEIMAN2.
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.
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.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
See all jSDM alternatives → · See all PEIMAN2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. jSDM and PEIMAN2 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. jSDM and PEIMAN2 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 jSDM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "jSDM alternatives" section above for the current picks, or visit /alternatives/jsdm for the full list with editorial commentary on each.
Top PEIMAN2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PEIMAN2 alternatives" section above for the current picks, or visit /alternatives/peiman2 for the full list with editorial commentary on each.