← Back to home
Comparison · Analytics

aniread vs teal.modules.clinical

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

aniread vs teal.modules.clinical: at a glance

Featureanireadteal.modules.clinical
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importclinical-trials, shiny-modules, teal, decorators
Last editorial update13h ago5d 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 teal.modules.clinical?

Roche's clinical teal modules have settled into slow, decorator-driven maintenance.

The module library took its architectural break in 0.9.0, when every module moved to teal_data objects and dropped data_extract_spec inputs. Work since then is narrower: formatting arguments, decorator plumbing, and per-module bug fixes. The 0.13.0 candidates cut in July 2026 are a two-tag same-day release where the first tag carries all the notes.

Read the full teal.modules.clinical trajectory →

aniread vs teal.modules.clinical: 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.

T0.0

Roche's clinical teal modules have settled into slow, decorator-driven maintenance.

◆ Current state

The module library took its architectural break in 0.9.0, when every module moved to teal_data objects and dropped data_extract_spec inputs. Work since then is narrower: formatting arguments, decorator plumbing, and per-module bug fixes. The 0.13.0 candidates cut in July 2026 are a two-tag same-day release where the first tag carries all the notes.

◆ Where it's heading

Development has shifted from reshaping the module API to making outputs configurable — numeric formatting in tm_t_summary, several decorators applied to one output object, categorical statistics in summary_by. Changes arrive from a wide bench of Roche engineers with occasional outside contributors, and releases go through candidates rather than straight to final.

◆ Prediction

A 0.13.0 final should follow the candidates with little beyond a dependency bump; the decorator work ported from teal.modules.general is the most likely source of the next batch of changes.

Alternatives to aniread and teal.modules.clinical

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 teal.modules.clinical.

See all aniread alternatives → · See all teal.modules.clinical alternatives →

Recent activity from aniread and teal.modules.clinical

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

  1. 1d agoanireadv0.6.0 — one entry point for every format
  2. 1mo agoteal.modules.clinicalNumeric formatting control and multi-decorator outputs
  3. 1mo agoteal.modules.clinicalteal.transform dependency bump
  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. 2y agoteal.modules.clinicalForest and Kaplan-Meier plots move to ggplot objects
  9. 2y agoteal.modules.clinicalEvery clinical module migrates to teal_data objects

Frequently asked questions

What is the difference between aniread and teal.modules.clinical?

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 teal.modules.clinical?

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 teal.modules.clinical?

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