rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of fastpos and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
Dormant three years, then a two-line release nobody using it would notice
fastpos finds the critical point of stability for a Pearson correlation, a simulation problem whose C++ implementation is the entire reason the package exists. Its substantive work concluded in 2022 with 0.5.0, the release prepared during R Journal review, which renamed the precision parameters, moved multicore work to pbapply and let users set corridor limits directly. After three years of silence, 0.6.0 removes an internal restriction to cpp11 and changes index_pop to an integer.
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.
fastpos finds the critical point of stability for a Pearson correlation, a simulation problem whose C++ implementation is the entire reason the package exists. Its substantive work concluded in 2022 with 0.5.0, the release prepared during R Journal review, which renamed the precision parameters, moved multicore work to pbapply and let users set corridor limits directly. After three years of silence, 0.6.0 removes an internal restriction to cpp11 and changes index_pop to an integer.
This is a finished piece of research software in low-effort upkeep. The changelog's centre of gravity is the R Journal review process, and once that concluded the package stopped changing. The single release since is toolchain work of the kind that keeps a package compiling rather than anything a user would see.
Expect nothing beyond occasional compilation or CRAN-check fixes unless the accompanying paper draws requests for other correlation types or resampling schemes.
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 fastpos or PEIMAN2.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all fastpos 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. fastpos 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. fastpos 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 fastpos alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "fastpos alternatives" section above for the current picks, or visit /alternatives/fastpos 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.