palettecore
Accessible palettes generated from one seed, with every audit number computed on the hex you actually get
A side-by-side editorial comparison of animovement and aniprocess — 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.
aniprocess rebuilt its filter API into three tiers and removed the old one outright.
aniprocess is the signal-processing half of the animovement ecosystem for animal movement data — smoothing, outlier flagging and gap handling for tracking coordinates. Version 0.3.0 restructured the entire public interface into three tiers: bare functions over a vector or a frame of coordinate columns, *_with() to select a method by name, and *_across() to apply one to a whole aniframe. Two functions were removed rather than deprecated, and argument names were normalized across the package.
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.
aniprocess is the signal-processing half of the animovement ecosystem for animal movement data — smoothing, outlier flagging and gap handling for tracking coordinates. Version 0.3.0 restructured the entire public interface into three tiers: bare functions over a vector or a frame of coordinate columns, *_with() to select a method by name, and *_across() to apply one to a whole aniframe. Two functions were removed rather than deprecated, and argument names were normalized across the package.
The redesign pushes aniframe metadata into the processing layer — *_across() reads sampling rate and the time column off the object instead of asking the caller, which is the division of labour aniframe's own class work assumes. Defaults are shifting toward not destroying information: filters preserve gaps unless inferring across them is the point, and a missing confidence score now warns rather than being read as a poor one. The bug fixes tell a consistent per-group story, with speed computed within each track so a step never forms across a track boundary.
With the across-style API landed and issue #29 (filter_by_pose) still open, the next release most likely extends the same three-tier pattern to pose data rather than adding more filters.
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 aniprocess.
Accessible palettes generated from one seed, with every audit number computed on the hex you actually get
A provenance-first corpus tool hands its verification core to agents over MCP
Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed
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
See all animovement alternatives → · See all aniprocess alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — animal tracking, r package — within Analytics. aniprocess is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. aniprocess is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 aniprocess alternatives in Analytics are ranked by recent ship velocity. Browse the "aniprocess alternatives" section above for the current picks, or visit /alternatives/aniprocess for the full list with editorial commentary on each.