← Back to home
Comparison · Analytics

aniread vs broman

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

aniread vs broman: at a glance

Featureanireadbroman
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importstatistics, base-graphics, utilities, r-package
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 broman?

A statistician's personal toolbox, growing one plotting utility at a time

broman is Karl Broman's collection of personal R utilities — base-graphics plotting helpers such as grayplot, dotplot and timeplot, running-window summaries, and assorted conveniences. Recent releases alternate between small additions, like runningratio2() with an adaptive window sized to hit a target denominator, and narrow bug fixes in crayons() and jiggle(). Version 0.92 removes an include that had begun warning on CRAN.

Read the full broman trajectory →

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

B
broman
ANALYTICS
0.0

A statistician's personal toolbox, growing one plotting utility at a time

◆ Current state

broman is Karl Broman's collection of personal R utilities — base-graphics plotting helpers such as grayplot, dotplot and timeplot, running-window summaries, and assorted conveniences. Recent releases alternate between small additions, like runningratio2() with an adaptive window sized to hit a target denominator, and narrow bug fixes in crayons() and jiggle(). Version 0.92 removes an include that had begun warning on CRAN.

◆ Where it's heading

The additions cluster around two themes: time-axis plotting and running-window summaries, both of which have been extended across several releases. Nothing here is planned in the usual sense — functions appear when the author needs them and bugs are fixed when they surface downstream, as jiggle() did through dotplot(). The C-level cleanup in 0.92 matches the same change made to R/qtl the same week, which is what maintaining a set of packages under one author looks like.

◆ Prediction

Both recent function additions extend existing families rather than starting new ones, so the next release is most likely another variant in the running-window or time-plotting group, or a fix surfaced by one of the author's other packages.

Alternatives to aniread and broman

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

See all aniread alternatives → · See all broman alternatives →

Recent activity from aniread and broman

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. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  5. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  6. 8mo agobromanRemove R_ext/PrtUtil.h include flagged by CRAN
  7. 10mo agobromanFix exact-name matching in crayons()
  8. 11mo agobromanFix jiggle() with factors missing levels
  9. 1y agobromanrunningratio2() uses an adaptive window
  10. 2y agobromantimeplot() added; running functions accept NAs
  11. 2y agobromantime_axis() added for date-time axis labels

Frequently asked questions

What is the difference between aniread and broman?

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

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

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