← Back to home
Comparison · Analytics

aniread vs deeptime

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

aniread vs deeptime: at a glance

Featureanireaddeeptime
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importggplot2-extension, geology, phylogenetics, deprecation
Last editorial update8h 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 deeptime?

A geologic-time plotting layer that outgrew time axes and became a geology rendering toolkit.

deeptime extends ggplot2 with geological time scales, radial deep-time coordinates and phylogeny-aware geoms, and since 2.0.0 it also renders standardized FGDC/USGS geologic patterns as ggplot2 fills. The current 2.4.0 release adds geom_text_clade() for labeling clades on radial phylogenies and repairs long-standing coord_trans_xy() and scale-placement edge cases.

Read the full deeptime trajectory →

aniread vs deeptime: 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.

D
deeptime
ANALYTICS
0.0

A geologic-time plotting layer that outgrew time axes and became a geology rendering toolkit.

◆ Current state

deeptime extends ggplot2 with geological time scales, radial deep-time coordinates and phylogeny-aware geoms, and since 2.0.0 it also renders standardized FGDC/USGS geologic patterns as ggplot2 fills. The current 2.4.0 release adds geom_text_clade() for labeling clades on radial phylogenies and repairs long-standing coord_trans_xy() and scale-placement edge cases.

◆ Where it's heading

The package is converging on two jobs: being the canonical R renderer for stratigraphic drawing conventions, and keeping pace with ggplot2's own churn. A sustained deprecation program — gggeo_scale(), coord_geo_polar(), getScaleData(), now disparity_through_time() — is trimming the surface down to coord_geo(), coord_geo_radial() and the pattern functions. Roughly half of each recent release is ggplot2 4.0 compatibility work.

◆ Prediction

Expect disparity_through_time() and coord_geo_polar() to be removed outright in the next major version, and further geoms aimed at annotating radial phylogenies.

Alternatives to aniread and deeptime

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

See all aniread alternatives → · See all deeptime alternatives →

Recent activity from aniread and deeptime

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

  1. 19h agoanireadv0.6.0 — one entry point for every format
  2. 1mo agodeeptimegeom_text_clade() labels clades on radial phylogenies
  3. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  4. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  5. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  6. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  7. 8mo agodeeptimeArgument renames for ggplot2 4.0 parity
  8. 9mo agodeeptimePattern code dictionary and time-scale theming
  9. 1y agodeeptimegeom_text_phylo() arrives with ggplot2 4 compatibility
  10. 1y agodeeptimeContrast-aware label colors across the built-in scales
  11. 1y agodeeptimeFGDC geologic patterns become ggplot2 fills

Frequently asked questions

What is the difference between aniread and deeptime?

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

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

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