rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
anticlust vs mpactr
A side-by-side editorial comparison of anticlust and mpactr — release velocity, themes, recent moves, and the top alternatives to consider.
anticlust vs mpactr: at a glance
What is anticlust?
Anticlustering keeps absorbing constraints — must-link, cannot-link, blocks, missing data
anticlust partitions a set of items into groups that are as similar to each other as possible — assembling matched stimulus sets, balanced experimental conditions, comparable teaching groups. The current surface is one function, anticlustering(), with a growing list of things it will honour: must-link and cannot-link constraints, categorical variables as factors, NAs, blocking by a categorical level, and a choice among exact solvers and heuristics.
What is mpactr?
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.
anticlust vs mpactr: editorial side-by-side
anticlust
0.0INFRA · APIS
Anticlustering keeps absorbing constraints — must-link, cannot-link, blocks, missing data
◆ Current state
anticlust partitions a set of items into groups that are as similar to each other as possible — assembling matched stimulus sets, balanced experimental conditions, comparable teaching groups. The current surface is one function, anticlustering(), with a growing list of things it will honour: must-link and cannot-link constraints, categorical variables as factors, NAs, blocking by a categorical level, and a choice among exact solvers and heuristics.
◆ Where it's heading
Two years of releases have gone almost entirely into constraint handling and input tolerance rather than new objectives. The methods list grew by absorbing outside work — the three-phase search of Yang et al. contributed by an external author, a 2PML heuristic for must-link problems, a Gurobi backend for the exact formulations. Meanwhile categories_to_binary() has been rewritten twice, which is where the recent bugs have come from.
◆ Prediction
The constraint types now interact combinatorially — blocks, must-link, cannot-link, missing values and each objective — and the last two releases were both regressions in the encoding layer underneath them. Consolidating that layer is the more likely next move than another solver.
mpactr
0.0INFRA · APIS
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to anticlust and mpactr
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 anticlust or mpactr.
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 anticlust alternatives → · See all mpactr alternatives →
Recent activity from anticlust and mpactr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agompactrPeak table names lowercased when absent from the injection column
- 3mo agompactrMetadata column names forced lowercase; get_metadata() renamed
- 4mo agoanticlustOne-hot encoding regression from 0.8.13 reverted
- 8mo agoanticlustblocks argument applies anticlustering level by level
- 9mo agoanticlustMissing values, factor columns, and the three-phase search
- 10mo agompactrValgrind and sanitizer memory issues cleared
- 1y agoanticlustEdge cases in the previous release's cannot-link handling
- 1y agoanticlustVector cannot-link constraints skip the solver entirely
- 1y agoanticlustUncaught test error flagged by CRAN additional checks
- 1y agompactrRcpp added to speed up filtering; data.table moved to Imports
- 1y agompactrmpactr 0.1.0
Frequently asked questions
What is the difference between anticlust and mpactr?
They serve adjacent needs but don't currently overlap on shipped themes. anticlust 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.
Is anticlust better than mpactr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. anticlust 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.
What are the best alternatives to anticlust?
Top anticlust alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "anticlust alternatives" section above for the current picks, or visit /alternatives/anticlust for the full list with editorial commentary on each.
What are the best alternatives to mpactr?
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.