← Back to home
Comparison · Analytics

aniread vs treespace

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

aniread vs treespace: at a glance

Featureanireadtreespace
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importphylogenetics, transmission-trees, cran-compliance, maintenance-mode
Last editorial update10h 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 treespace?

treespace ships once every year or two, and only when CRAN or a user forces it.

treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.

Read the full treespace trajectory →

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

treespace ships once every year or two, and only when CRAN or a user forces it.

◆ Current state

treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.

◆ Where it's heading

The package is stable and lightly staffed rather than abandoned — bugs that affect correctness do get fixed, and CRAN deadlines are met. But the 2023 update is the telling one: rather than vendor or replace adephylo when it faced removal, the maintainers disabled two tree-vector methods and marked the loss as hopefully temporary. Two years on, nothing in the feed indicates they came back.

◆ Prediction

The next entry will most likely be another CRAN-compliance patch, on the pattern of four of the last five releases. Whether the Abouheif and sumDD methods ever return is not something these entries give any signal on.

Alternatives to aniread and treespace

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

See all aniread alternatives → · See all treespace alternatives →

Recent activity from aniread and treespace

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 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. 11mo agotreespacetreespace patches Rd cross-references for CRAN
  7. 2y agotreespacetreespace disables Abouheif and sumDD as adephylo exits CRAN
  8. 3y agotreespacetreespace fixes vignette build on NA tree names
  9. 5y agotreespacetreespace fixes dist indexing that broke its tests
  10. 5y agotreespacetreespace corrects tip label handling in transmission distances

Frequently asked questions

What is the difference between aniread and treespace?

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

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

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