← Back to home
Comparison · Analytics

aniread vs dcurves

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

aniread vs dcurves: at a glance

Featureanireaddcurves
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importclinical-prediction, decision-analysis, net-benefit, biostatistics
Last editorial update13h ago2d 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 dcurves?

Decision curve analysis, settled since 2022 and now moving only when its neighbours do

dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.

Read the full dcurves trajectory →

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

Decision curve analysis, settled since 2022 and now moving only when its neighbours do

◆ Current state

dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.

◆ Where it's heading

The package reached its intended scope quickly and then stopped. Its 2022 releases did the substantive work: adding threshold-level diagnostic accuracy, tightening argument validation, and taking one breaking change to make net-interventions-avoided plots show the treat-all and treat-none reference lines by default. Since then it has moved only as a dependent of the wider tidy-modelling documentation ecosystem it plugs into.

◆ Prediction

Nothing in these entries points to method or API work; expect the next release to be another compatibility or CRAN documentation patch.

Alternatives to aniread and dcurves

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

See all aniread alternatives → · See all dcurves alternatives →

Recent activity from aniread and dcurves

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

  1. 1d 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. 9mo agodcurvesHTML5 documentation rebuild for CRAN
  7. 2y agodcurvesbroom.helpers added to Suggests for gtsummary 2.0
  8. 3y agodcurvesNet interventions plots now show treat-all and treat-none by default
  9. 4y agodcurvestest_consequences() reports accuracy across thresholds

Frequently asked questions

What is the difference between aniread and dcurves?

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

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

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