← Back to home
Comparison · Analytics

aniread vs pedprobr

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

aniread vs pedprobr: at a glance

Featureanireadpedprobr
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importpedigree analysis, likelihood computation, peeling algorithm, allele lumping
Last editorial update13h 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 pedprobr?

pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.

pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.

Read the full pedprobr trajectory →

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

P
pedprobr
ANALYTICS
0.0

pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.

◆ Current state

pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.

◆ Where it's heading

Every significant release here removes a class of computation that used to be infeasible, either by making a marker lumpable or by making a loop breakable. The rest is steady peeling-algorithm optimization, which has been reducing memory footprint release after release since 0.9.2. The newly added .diagnostics option suggests the peeling internals are now complex enough that the maintainer needs to inspect them.

◆ Prediction

Since special lumping is documented as covering only some cases so far, expect further lumping situations to be implemented as pedmut adds them.

Alternatives to aniread and pedprobr

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

See all aniread alternatives → · See all pedprobr alternatives →

Recent activity from aniread and pedprobr

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

  1. 23h 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. 1mo agopedprobrLoop handling updated for pedtools' new loop breakers
  5. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  6. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  7. 1y agopedprobrCRAN example rounding fix
  8. 1y agopedprobrSpecial lumping for previously un-lumpable mutation models
  9. 1y agopedprobrGenotype distributions gain sparse and table output
  10. 2y agopedprobrPeeling order bug fix
  11. 2y agopedprobrPartial genotype fix for singletons

Frequently asked questions

What is the difference between aniread and pedprobr?

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

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

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