haze
Four dormant years end with a modernization pass and an off-by-one fix in the C++ core
A side-by-side editorial comparison of animovement and collinear — release velocity, themes, recent moves, and the top alternatives to consider.
animovement stopped being a package and became a metapackage over seven focused ones.
animovement handles animal movement data — tracking output from pose-estimation and centroid trackers, cleaned into a standard form. Its 0.7.3 release, the first GitHub tag since November 2024, bundles the 0.5 through 0.7 development series and records a structural change: the codebase was split into aniframe, aniread, aniprocess, anicheck, animetric, anivis and anispace, which animovement now bundles and re-exports. The package has done this before at smaller scale, having renamed itself from trackballr in 0.2.0 to match a widened scope.
collinear has broken its API twice to stop making the user pick thresholds.
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
animovement handles animal movement data — tracking output from pose-estimation and centroid trackers, cleaned into a standard form. Its 0.7.3 release, the first GitHub tag since November 2024, bundles the 0.5 through 0.7 development series and records a structural change: the codebase was split into aniframe, aniread, aniprocess, anicheck, animetric, anivis and anispace, which animovement now bundles and re-exports. The package has done this before at smaller scale, having renamed itself from trackballr in 0.2.0 to match a widened scope.
Development has moved to the constituent packages, which release far more often than animovement itself — aniframe, aniread and aniprocess have each shipped multiple times in 2026 while animovement tagged once. That makes animovement a stable install surface rather than where the work happens, and the ani_df data class plus the frame-rate to sampling-rate terminology change are the contracts holding the suite together. Optional dependencies are handled through animovement_install_suggested() against r-universe and Bioconductor mirrors.
With the split done and the constituent packages iterating independently, animovement releases are likely to become periodic roll-ups of the suite rather than carriers of new functionality.
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
The through-line is removing decisions the user was never well placed to make. Preference-order functions were renamed twice — first onto a metric-and-model scheme in 2.0.0, then onto a response-type scheme in 3.0.0 — and f_auto() picks one when none is given; target encoding went from automatic to opt-in; max_cor and max_vif now default to NULL and trigger a data-driven threshold derived from the 75th percentile of pairwise correlations through a sigmoid and a fitted correlation-to-VIF mapping. Each change is defensible and each one broke callers, which is the cost of this approach.
3.0.1 moved the example datasets out into a separate spatialData package and fixed four crashes rather than adding anything, so the next release is most likely more consolidation on the 3.0 surface than a fourth interface.
Other Analytics 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 animovement or collinear.
Four dormant years end with a modernization pass and an off-by-one fix in the C++ core
A VAR-model fitting package acquiring the standard R methods it launched without
A C++ mesh renderer grinding through CRAN's gate, one policy fix at a time
soilDBdata exists so soilDB's tests can run without a NASIS connection.
nert put fourteen TERN datasets behind one dispatcher and called it stable.
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
See all animovement alternatives → · See all collinear alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. animovement and collinear 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. animovement and collinear 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 Analytics products to evaluate alongside.
Top animovement alternatives in Analytics are ranked by recent ship velocity. Browse the "animovement alternatives" section above for the current picks, or visit /alternatives/animovement for the full list with editorial commentary on each.
Top collinear alternatives in Analytics are ranked by recent ship velocity. Browse the "collinear alternatives" section above for the current picks, or visit /alternatives/collinear for the full list with editorial commentary on each.