pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of anticlust and JointFPM — 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.
Recurrent-event modelling settles, with mean_no() promoted to stable.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
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.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.
With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.
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 JointFPM.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all anticlust alternatives → · See all JointFPM 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 JointFPM 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 JointFPM 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 JointFPM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "JointFPM alternatives" section above for the current picks, or visit /alternatives/jointfpm for the full list with editorial commentary on each.