rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of gofedf and mpactr — release velocity, themes, recent moves, and the top alternatives to consider.
A two-test goodness-of-fit package opens itself up to any weight function
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
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.
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
The package is generalising rather than accumulating. Each release removed a hard-coded decision: first how eigenvalues are computed, offering both the analytical route and a matrix approximation; then which weight function defines the statistic at all. The maintainer's own framing in 1.1.0 is a contrast against what earlier versions would not let you do, which is the shape of a package aiming to become a framework.
An arbitrary weight function is the extensibility point that matters for EDF tests; what it lacks is calibration guidance, since Type I error behaviour was the argued benefit of the analytical eigenvalue route. Documented recommendations or diagnostics for user-chosen weights are the natural follow-up, though the entries do not announce one.
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 gofedf 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 gofedf alternatives → · See all mpactr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gofedf 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. gofedf 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 gofedf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gofedf alternatives" section above for the current picks, or visit /alternatives/gofedf 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.