qtl2fst
The out-of-memory backend for R/qtl2, feature-complete since 2020 and now purely on upkeep
Comparison · Analytics
animovement vs PurpleAir
A side-by-side editorial comparison of animovement and PurpleAir — release velocity, themes, recent moves, and the top alternatives to consider.
animovement vs PurpleAir: at a glance
What is animovement?
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.
What is PurpleAir?
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
animovement vs PurpleAir: editorial side-by-side
animovement
0.0ANALYTICS
animovement stopped being a package and became a metapackage over seven focused ones.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
PurpleAir
0.0ANALYTICS
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
◆ Current state
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
◆ Where it's heading
The recurring theme is time aggregation. Weekly, monthly and yearly average intervals were wrong and fixed in one release; the weekly average was wrong again and fixed in the next. For an air quality package that is not incidental — averaging window is what turns a stream of sensor readings into an exposure estimate, and downstream analyses inherit the error silently. The other thread is failing earlier and more clearly: explicit errors for spatial inputs the sensor query does not accept, better index parsing so malformed requests never reach the API, and handling for history calls that return nothing. Local sensor discovery is the one genuine capability addition, opening a path that does not depend on the cloud API at all.
◆ Prediction
On this record, further aggregation and input-validation fixes are the likeliest next releases; whether local network access grows past discovery into full local data retrieval is not something the entries indicate.
Alternatives to animovement and PurpleAir
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 PurpleAir.
mmconvert
A single-purpose mouse map interpolator that solved its problem in 2023 and has coasted since
qtl2convert
A conversion utility in pure maintenance mode, tracking R-devel breakage release by release
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
See all animovement alternatives → · See all PurpleAir alternatives →
Recent activity from animovement and PurpleAir
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoanimovementanimovement becomes a metapackage over seven packages ⚡
- 3mo agoPurpleAirWeekly averages fixed again; API key argument dropped
- 10mo agoPurpleAirLocal sensor discovery, and averaging intervals corrected
- 1y agoanimovementread_animalta() patch
- 1y agoanimovementReaders for seven tracking and pose-estimation formats
- 1y agoPurpleAirBounding box sensor queries fixed
- 1y agoanimovementtrackballr becomes animovement as scope widens ⚡
Frequently asked questions
What is the difference between animovement and PurpleAir?
They serve adjacent needs but don't currently overlap on shipped themes. animovement and PurpleAir 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 animovement better than PurpleAir?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. animovement and PurpleAir 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.
What are the best alternatives to animovement?
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.
What are the best alternatives to PurpleAir?
Top PurpleAir alternatives in Analytics are ranked by recent ship velocity. Browse the "PurpleAir alternatives" section above for the current picks, or visit /alternatives/purpleair for the full list with editorial commentary on each.