rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of mdatools and mpactr — 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.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
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.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
The package is stabilizing its input contract rather than growing its filtering methods. Metadata column names are now forced lowercase inside import_data() regardless of how the file was written, imported peak_tables names not present in the injection column are lowercased too, and get_meta_data() was renamed to get_metadata() in the same pass. Before that the work was infrastructural — Rcpp introduced to speed up filtering, data.table moved from Depends to Imports, and memory errors cleared so the package passes Valgrind and both sanitizers. Note the earliest entry compares against a v1.0.0 tag that precedes 0.1.0 in the repository, so version ordering in this feed is not reliable.
The case-normalization work has now touched both metadata columns and peak table names across two consecutive releases, which suggests the input-matching problem is not fully closed and a third pass is plausible. Nothing in these entries points to new filtering methods.
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 mpactr.
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 mpactr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. mdatools and mpactr 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 mpactr 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 mpactr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mpactr alternatives" section above for the current picks, or visit /alternatives/mpactr for the full list with editorial commentary on each.