← Back to home
Comparison · Analytics

aniread vs tidyclust

A side-by-side editorial comparison of aniread and tidyclust — release velocity, themes, recent moves, and the top alternatives to consider.

aniread vs tidyclust: at a glance

Featureanireadtidyclust
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importtidyclust, clustering, tidymodels, dbscan
Last editorial update10h ago5d ago
WebsiteVisit →Visit →

What is aniread?

aniread stops asking you to know which tracker wrote the file

aniread is the reader package of the animovement suite, importing output from pose-estimation, centroid and behavioural-scoring tools into aniframe objects. Through 0.5.x the work was per-reader: get_supported_sources() exposed the format list programmatically, read_boris() added behavioural events, and Octron and BORIS each got targeted fixes. 0.6.0 changes the shape of the interface itself — read_dataset() takes any supported file through one entry point and detect_source() works out which software wrote it by inspecting contents, not just the suffix.

Read the full aniread trajectory →

What is tidyclust?

tidyclust just tripled the model types it can fit, and handed finalization back to tune

tidyclust brings clustering into the tidymodels interface, and 0.3.0 was the release where its model coverage stopped being k-means and hierarchical clustering. DBSCAN and HDBSCAN, Gaussian mixtures, and mean shift all arrived at once as proper clustering specifications. The two releases since have been bug fixes on the metric and sparse-data paths, which is the usual pattern after a large surface addition.

Read the full tidyclust trajectory →

aniread vs tidyclust: editorial side-by-side

A
aniread
ANALYTICS
3.8

aniread stops asking you to know which tracker wrote the file

◆ Current state

aniread is the reader package of the animovement suite, importing output from pose-estimation, centroid and behavioural-scoring tools into aniframe objects. Through 0.5.x the work was per-reader: get_supported_sources() exposed the format list programmatically, read_boris() added behavioural events, and Octron and BORIS each got targeted fixes. 0.6.0 changes the shape of the interface itself — read_dataset() takes any supported file through one entry point and detect_source() works out which software wrote it by inspecting contents, not just the suffix.

◆ Where it's heading

The package is moving from a set of named readers to a dispatcher with the readers behind it, and the hard part is being handled rather than hidden: twelve sources emit .csv, so detection narrows by suffix then inspects content, and DeepLabCut and LightningPose files are structurally identical so it returns the combined 'deeplabcut/lightningpose' rather than guessing wrong. The honesty extends to gaps — optional-dependency detectors are skipped when the package is absent and the error names what was skipped, and SLEAP's csv suffix was withdrawn because auto-detection would have routed files into a reader that cannot read them. Alongside this, read_trackball() was substantially repaired for real two-sensor Bonsai captures, where alignment, clocks, corrupt rows and gap filling were each independently wrong.

◆ Prediction

Expect the withdrawn SLEAP csv suffix to return once read_sleap() gains support, since the changelog explicitly parks it against issue #87. Further detectors are the natural next increment, and the sensor-local-clock warning class suggests trackball alignment is not finished.

T
tidyclust
ANALYTICS
0.0

tidyclust just tripled the model types it can fit, and handed finalization back to tune

◆ Current state

tidyclust brings clustering into the tidymodels interface, and 0.3.0 was the release where its model coverage stopped being k-means and hierarchical clustering. DBSCAN and HDBSCAN, Gaussian mixtures, and mean shift all arrived at once as proper clustering specifications. The two releases since have been bug fixes on the metric and sparse-data paths, which is the usual pattern after a large surface addition.

◆ Where it's heading

The package is converging with the rest of tidymodels rather than maintaining a parallel API: finalize_model_tidyclust() and finalize_workflow_tidyclust() are deprecated because tune::finalize_model() and tune::finalize_workflow() now handle cluster_spec objects natively. That removes the last place where clustering needed its own version of a shared verb. With density-based and model-based clustering now present, the interface has to cover model families with genuinely different assumptions than the centroid methods it started with.

◆ Prediction

The recent fixes to cluster_metric_set() labeling and custom-metric authoring suggest evaluation is the current focus, so metrics suited to density-based clusters are the likely next addition.

Alternatives to aniread and tidyclust

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 aniread or tidyclust.

See all aniread alternatives → · See all tidyclust alternatives →

Recent activity from aniread and tidyclust

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 20h agoanireadv0.6.0 — one entry point for every format
  2. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  3. 1mo agotidyclusttidyclust 0.3.2 fixes k_means() on sparse predictors
  4. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  5. 1mo agotidyclusttidyclust 0.3.1 stops same-named metrics silently merging
  6. 2mo agotidyclusttidyclust 0.3.0 adds DBSCAN, Gaussian mixture, and mean shift models
  7. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  8. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  9. 1y agotidyclusttidyclust 0.2.4 switches distance calculations to philentropy
  10. 2y agotidyclusttidyclust 0.2.3 resolves a clustMixType reverse-dependency issue
  11. 2y agotidyclusttidyclust 0.2.2 resolves a ClusterR reverse-dependency issue

Frequently asked questions

What is the difference between aniread and tidyclust?

They serve adjacent needs but don't currently overlap on shipped themes. aniread 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.

Is aniread better than tidyclust?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniread 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.

What are the best alternatives to aniread?

Top aniread alternatives in Analytics are ranked by recent ship velocity. Browse the "aniread alternatives" section above for the current picks, or visit /alternatives/aniread for the full list with editorial commentary on each.

What are the best alternatives to tidyclust?

Top tidyclust alternatives in Analytics are ranked by recent ship velocity. Browse the "tidyclust alternatives" section above for the current picks, or visit /alternatives/tidyclust for the full list with editorial commentary on each.