← Back to home
Comparison · Analytics

aniread vs timeplyr

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

aniread vs timeplyr: at a glance

Featureanireadtimeplyr
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importtime-series, r, dplyr, data.table
Last editorial update11h ago3d 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 timeplyr?

timeplyr cut everything that wasn't time, then rebuilt intervals as fixed-width vectors.

timeplyr is a time-aware companion to dplyr and data.table, built around a fixed-width time_interval vector class. The 1.0.0 rewrite removed most non-time functions and pushed the C++ layer out into the separate cheapr package, leaving a narrower surface than the 0.8.x line. Releases since have been small: one feature batch in 1.1.1 and a pair of bug fixes in 1.1.2.

Read the full timeplyr trajectory →

aniread vs timeplyr: 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
timeplyr
ANALYTICS
0.0

timeplyr cut everything that wasn't time, then rebuilt intervals as fixed-width vectors.

◆ Current state

timeplyr is a time-aware companion to dplyr and data.table, built around a fixed-width time_interval vector class. The 1.0.0 rewrite removed most non-time functions and pushed the C++ layer out into the separate cheapr package, leaving a narrower surface than the 0.8.x line. Releases since have been small: one feature batch in 1.1.1 and a pair of bug fixes in 1.1.2.

◆ Where it's heading

The arc is consolidation, not expansion. Each release since 1.0.0 trims arguments, renames functions toward a single vocabulary (width, timespan, grid), or fixes an interaction with data.table's own rolling functions. The package increasingly acts as a thin time layer over cheapr and data.table rather than carrying its own implementation.

◆ Prediction

Expect continued small releases tracking cheapr and data.table changes rather than new function families; the entries show no in-progress feature work beyond the ggplot2-friendly breakpoint helpers introduced in 1.1.1.

Alternatives to aniread and timeplyr

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 timeplyr.

See all aniread alternatives → · See all timeplyr alternatives →

Recent activity from aniread and timeplyr

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

  1. 21h agoanireadv0.6.0 — one entry point for every format
  2. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  3. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  4. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  5. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  6. 4mo agotimeplyrLeap-day and time_complete(.by=) bug fixes
  7. 10mo agotimeplyrtime_breakpoints added; rolling calcs realigned to data.table
  8. 1y agotimeplyrFixed-width time intervals; non-time functions removed
  9. 2y agotimeplyrtime_intervals on by default; year_month/year_quarter ggplot2 scales
  10. 2y agotimeplyrRegression fixes after the 0.8.0 refactor
  11. 2y agotimeplyrC++ layer moved to cheapr; time_interval class introduced

Frequently asked questions

What is the difference between aniread and timeplyr?

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 timeplyr?

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 timeplyr?

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