rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
PEIMAN2 vs prospectr
A side-by-side editorial comparison of PEIMAN2 and prospectr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
PEIMAN2 vs prospectr: at a glance
| Feature | PEIMAN2 | prospectr |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | proteomics, post-translational-modification, enrichment-analysis, reproducibility | spectroscopy, signal-processing, preprocessing, calibration-sampling |
| Last editorial update | 1h ago | 1h ago |
| Website | Visit → | Visit → |
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.
What is prospectr?
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.
PEIMAN2 vs prospectr: editorial side-by-side
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.
prospectr
0.0INFRA · APIS
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
◆ Current state
prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.
◆ Where it's heading
The recent work is corrective rather than additive, and several items changed results silently before being caught. continuumRemoval() derived its convex-hull boundary offset from a fixed one-wavelength assumption that broke for fine-resolution spectra or non-nanometre units; cochranTest() passed an invalid argument name to prcomp() and produced incorrect principal component scores; readASD() silently dropped spectra in one branch of its text path. Two file readers were leaking connections. Alongside that runs a smaller thread of decoupling preprocessing steps from each other, most visibly detrend() gaining an snv argument so polynomial detrending can run without the SNV transform that Barnes et al. bundled with it.
◆ Prediction
The detrend() decoupling is the only recent addition and it fits a broader pipeline-composition direction, so similar separation of other bundled preprocessing steps is the plausible next move. The misspelled substraction argument now carries a deprecation warning, which schedules its removal for a future release.
Alternatives to PEIMAN2 and prospectr
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 PEIMAN2 or prospectr.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all PEIMAN2 alternatives → · See all prospectr alternatives →
Recent activity from PEIMAN2 and prospectr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoprospectrdetrend() can run without a prior SNV transformation
- 2mo agoPEIMAN2Database updates decouple from package releases ⚡
- 2mo agoprospectrContinuum removal, SNV and cochranTest corrected; readers stop leaking
- 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
- 1y agoPEIMAN2Documentation fix for the second example dataset
- 1y agoprospectrread_nircal() sample ID field fix
- 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped
- 3y agoprospectrNon-UTF8 sample IDs no longer become NA
- 4y agoprospectrkenStone() bug fix
- 4y agoprospectrread_nircal() execution failure fixed
Frequently asked questions
What is the difference between PEIMAN2 and prospectr?
Both compete on the same themes — r-packages — within Infra & APIs. PEIMAN2 and prospectr 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 PEIMAN2 better than prospectr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PEIMAN2 and prospectr 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 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.
What are the best alternatives to prospectr?
Top prospectr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "prospectr alternatives" section above for the current picks, or visit /alternatives/prospectr for the full list with editorial commentary on each.