← Back to home
Comparison · Analytics

aniread vs hdnom

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

aniread vs hdnom: at a glance

Featureanireadhdnom
SectorAnalyticsAnalytics
Velocity score3.85.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importsurvival analysis, r, regularization, nomograms
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 hdnom?

hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to

hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.

Read the full hdnom trajectory →

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

H
hdnom
ANALYTICS
5.0

hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to

◆ Current state

hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.

◆ Where it's heading

The releases track two upstream pressures with no feature work of its own. glmnet is the larger one: its 4.1-9 change to how Cox cross-validation errors are normalized made lambda.1se select null models far more often, forcing hdnom to expose a rule argument and switch its examples to lambda.min. R-devel is the other, producing a steady trickle of strict-headers, deprecated-symbol and check-note fixes. The pattern is consistent — absorb the upstream change, default to whatever preserves existing behaviour, let users opt into the new one.

◆ Prediction

The cox.ties default is explicitly pinned to "breslow" to silence glmnet's migration warning, which is a deferral rather than a decision; expect a future release to flip that default to "efron" once glmnet completes the transition.

Alternatives to aniread and hdnom

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

See all aniread alternatives → · See all hdnom alternatives →

Recent activity from aniread and hdnom

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

  1. 19h agoanireadv0.6.0 — one entry point for every format
  2. 22d agohdnomhdnom 6.2.1
  3. 22d agohdnomhdnom 6.2.0 pins Cox tie handling ahead of glmnet's migration
  4. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  5. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  6. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  7. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  8. 1y agohdnomhdnom 6.1.0 exposes lambda selection after a glmnet normalization change
  9. 1y agohdnomhdnom 6.0.4
  10. 2y agohdnomhdnom 6.0.3
  11. 3y agohdnomhdnom 6.0.2

Frequently asked questions

What is the difference between aniread and hdnom?

They serve adjacent needs but don't currently overlap on shipped themes. hdnom is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is aniread better than hdnom?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hdnom is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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 hdnom?

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