rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of mdatools and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
mdatools spun out its cross-validation method, then came back for three-way data.
mdatools is a long-running chemometrics package covering PCA, PLS regression, SIMCA and DD-SIMCA classification, MCR resolution and a large spectral preprocessing framework. Its releases are infrequent and each one tends to carry one substantive idea plus a handful of fixes. The June release opens a direction the package had not previously taken: DD-SIMCA classification of three-way data, through PARAFAC and Tucker decompositions.
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.
mdatools is a long-running chemometrics package covering PCA, PLS regression, SIMCA and DD-SIMCA classification, MCR resolution and a large spectral preprocessing framework. Its releases are infrequent and each one tends to carry one substantive idea plus a handful of fixes. The June release opens a direction the package had not previously taken: DD-SIMCA classification of three-way data, through PARAFAC and Tucker decompositions.
The shape of the package has been managed deliberately rather than allowed to sprawl. Procrustes cross-validation grew large enough to warrant its own package and was moved out to pcv in 0.14.0; preprocessing was consolidated in 0.12.0 into a composable prep() framework rather than a set of loose functions. Around that, the recurring work is numerical: a more stable SIMPLS implementation, cross-validation rewritten to accept user-supplied segment indices, prep.savgol() and prep.alsbasecorr() rewritten for speed, and now the baseline iteration default raised to match the web applications the maintainer also runs.
Three-way DD-SIMCA arrives with two decompositions and no companion regression or resolution methods for multiway data, so extending the multiway path to the rest of the toolkit is the obvious follow-up. The alignment of defaults with the maintainer's web applications suggests those two codebases will keep being reconciled.
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 mdatools 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 mdatools alternatives → · See all PEIMAN2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. mdatools 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. mdatools 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 mdatools alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mdatools alternatives" section above for the current picks, or visit /alternatives/mdatools 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.