ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
Comparison · Infra & APIs
coga vs PEIMAN2
A side-by-side editorial comparison of coga and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
coga vs PEIMAN2: at a glance
What is coga?
A gamma-convolution density package that reached completion in 2018 and has coasted since.
coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.
What is PEIMAN2?
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.
coga vs PEIMAN2: editorial side-by-side
coga
0.0INFRA · APIS
A gamma-convolution density package that reached completion in 2018 and has coasted since.
◆ Current state
coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.
◆ Where it's heading
This is a finished package being kept alive rather than developed. The releases track external pressure exactly: CRAN documentation requirements, compiler warnings, Rcpp API changes. Its maintenance is visibly shared with smam, the same maintainer's animal-movement package, which received the same email update, the same format-security fix and the same Rcpp guard within a minute or twenty of coga each time. Neither package is being extended; both are being kept installable.
◆ Prediction
Expect nothing but CRAN and toolchain maintenance, arriving whenever Rcpp or R's check requirements change, and arriving alongside smam. There is no signal in these entries of planned functional work.
PEIMAN2
0.0INFRA · APIS
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to coga and PEIMAN2
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 coga or PEIMAN2.
mpactr
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore
surveycore declared its API stable with every survey design type covered.
prospectr
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
standardlastprofile
A German electricity load-profile package added gas and doubled the market it serves.
See all coga alternatives → · See all PEIMAN2 alternatives →
Recent activity from coga and PEIMAN2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoPEIMAN2Database updates decouple from package releases ⚡
- 5mo agocogaRcpp attributes regenerated; email updated
- 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
- 1y agoPEIMAN2Documentation fix for the second example dataset
- 2y agocogaMaintainer email updated
- 2y agocogaCompiler format-security warning resolved
- 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped
- 3y agocogaPackage documentation alias added for CRAN
- 6y agocogaUnexported density variant added for research use
- 8y agocoga1.0.0 declares the package complete and documented
Frequently asked questions
What is the difference between coga and PEIMAN2?
They serve adjacent needs but don't currently overlap on shipped themes. coga 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.
Is coga better than PEIMAN2?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. coga 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.
What are the best alternatives to coga?
Top coga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "coga alternatives" section above for the current picks, or visit /alternatives/coga for the full list with editorial commentary on each.
What are the best alternatives to PEIMAN2?
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.