mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of anticlust and samplr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A cognitive-science sampling package ships once, then goes quiet for eighteen months
samplr compares human performance against sampling algorithms, giving cognitive scientists the MCMC machinery to test whether people behave like samplers. Its entire public history is three releases: a 1.0.0 in August 2024, a floating-point fix eighteen seconds later, and then nothing until a February 2026 patch. The release notes are unusually thin even by CRAN standards.
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.
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.
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.
samplr compares human performance against sampling algorithms, giving cognitive scientists the MCMC machinery to test whether people behave like samplers. Its entire public history is three releases: a 1.0.0 in August 2024, a floating-point fix eighteen seconds later, and then nothing until a February 2026 patch. The release notes are unusually thin even by CRAN standards.
The feed shows a package that shipped and stopped. The 2024 tags were both created in one sitting and say almost nothing; the 2026 release is a row-count bug in Mean_Variance() bundled with citation metadata, a dropped dependency and http-to-https link fixes — the housekeeping profile of a package being kept alive for the paper that cites it rather than actively developed.
Adding citation information to the README is usually the move of a maintainer expecting the package to be referenced rather than extended. On this cadence the next release is more likely another CRAN-hygiene patch than new algorithms; there is not enough in these notes to say otherwise.
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 samplr.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all anticlust alternatives → · See all samplr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. anticlust and samplr 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. anticlust and samplr 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 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.
Top samplr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "samplr alternatives" section above for the current picks, or visit /alternatives/samplr for the full list with editorial commentary on each.