← Back to home
Comparison · Analytics

aniread vs epidemics

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

aniread vs epidemics: at a glance

Featureanireadepidemics
SectorAnalyticsAnalytics
Velocity score3.83.8
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importepiverse-trace, compartmental-models, odin, breaking-changes
Last editorial update11h 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 epidemics?

epidemics swapped its C++ engine for odin — and quietly inverted how contact matrices must be passed.

epidemics ships composable compartmental model structures — default SEIR-V, Vacamole, diphtheria and Ebola — with classes for populations, interventions and vaccination campaigns. After more than two years without a release, 0.5.0 landed in July 2026 carrying both an engine migration and a breaking input-convention change. Maintainership moved to a new lead back in 0.4.0.

Read the full epidemics trajectory →

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

E
epidemics
ANALYTICS
3.8

epidemics swapped its C++ engine for odin — and quietly inverted how contact matrices must be passed.

◆ Current state

epidemics ships composable compartmental model structures — default SEIR-V, Vacamole, diphtheria and Ebola — with classes for populations, interventions and vaccination campaigns. After more than two years without a release, 0.5.0 landed in July 2026 carrying both an engine migration and a breaking input-convention change. Maintainership moved to a new lead back in 0.4.0.

◆ Where it's heading

The package's history is a sequence of deliberate breaking releases: 0.2.0 renamed every model function and vectorised the ODE models, 0.3.0 restructured the Ebola model into two levels and made replicates the default, and 0.5.0 rewrites the compiled core. The direction is toward a smaller, more declarative model definition layer with the numerical work delegated to a dedicated tool.

◆ Prediction

With the default, Vacamole and diphtheria systems now declared in odin, the Ebola model is the obvious remaining candidate for the same treatment.

Alternatives to aniread and epidemics

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

See all aniread alternatives → · See all epidemics alternatives →

Recent activity from aniread and epidemics

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

  1. 21h agoanireadv0.6.0 — one entry point for every format
  2. 1mo agoepidemicsODE models migrate to odin; contact matrices must no longer be transposed
  3. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  4. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  5. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  6. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  7. 2y agoepidemicsPeak timing and scenario comparison helpers; negative-susceptible bug fixed
  8. 2y agoepidemicsEbola model accepts vector inputs and defaults to 100 replicates
  9. 2y agoepidemicsODE models vectorised; every model function renamed
  10. 2y agoepidemicsFirst release: four composable compartmental model structures

Frequently asked questions

What is the difference between aniread and epidemics?

They serve adjacent needs but don't currently overlap on shipped themes. aniread and epidemics are shipping at a similar cadence (velocity 3.8 vs 3.8, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is aniread better than epidemics?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniread and epidemics are shipping at a similar cadence (velocity 3.8 vs 3.8, both within Sparkpulse's "active" band). 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 epidemics?

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