← Back to home
Comparison · Analytics

aniread vs intsurv

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

aniread vs intsurv: at a glance

Featureanireadintsurv
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesanimal tracking, file formats, pose estimation, data importsurvival-analysis, cure-models, censored-data, regularization
Last editorial update6h ago48m ago
WebsiteVisit →Visit →

What is aniread?

aniread keeps finding that every tracker lies about coordinates in its own way.

aniread is the reader package of the animovement suite, importing output from pose-estimation and centroid trackers into aniframe objects. The 0.4.0 release standardised something every reader had been getting differently — source data using an image top-left origin is now reflected into a conventional bottom-left origin, across eleven readers. Since then the work has been Octron and BORIS specifics, and 0.5.0 extended the package past tracking data into behavioural events.

Read the full aniread trajectory →

What is intsurv?

A Cox cure-rate model package woke up after four years to simplify its own interface.

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

Read the full intsurv trajectory →

aniread vs intsurv: editorial side-by-side

A
aniread
ANALYTICS
0.0

aniread keeps finding that every tracker lies about coordinates in its own way.

◆ Current state

aniread is the reader package of the animovement suite, importing output from pose-estimation and centroid trackers into aniframe objects. The 0.4.0 release standardised something every reader had been getting differently — source data using an image top-left origin is now reflected into a conventional bottom-left origin, across eleven readers. Since then the work has been Octron and BORIS specifics, and 0.5.0 extended the package past tracking data into behavioural events.

◆ Where it's heading

Each release reads as a catalogue of the ways a source format is imprecise: Octron omitting frames where nothing was detected, BORIS exports whose image index puts a STOP before its START, idtracker.ai renaming its leading column, Windows UNC shares reporting a false negative on read permission. The fixes share a posture of reconstructing what the format left implicit rather than passing the gap through — reinstating missing frames as all-NA rows, recovering a frame interval from time and FPS. Format support now tracks aniframe's class work closely, with 0.5.0 requiring aniframe 0.6.0 for the anievent class it produces.

◆ Prediction

get_supported_sources() was added so downstream packages can discover formats programmatically instead of hard-coding them, which suggests the next additions are more sources behind that registry rather than changes to the reader API.

I
intsurv
ANALYTICS
0.0

A Cox cure-rate model package woke up after four years to simplify its own interface.

◆ Current state

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

◆ Where it's heading

The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.

◆ Prediction

The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.

Alternatives to aniread and intsurv

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

See all aniread alternatives → · See all intsurv alternatives →

Recent activity from aniread and intsurv

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

  1. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  2. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  3. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  4. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  5. 10mo agointsurvModel configuration moves into dedicated control functions
  6. 5y agointsurvCross-validated model selection and offset terms added
  7. 6y agointsurvC++ headers relocated so other packages can link them
  8. 7y agointsurvCox cure models for uncertain event status arrive
  9. 7y agointsurvParameter initialization methods added to the alpha
  10. 7y agointsurvAlpha cut for paper submission and simulation reproducibility

Frequently asked questions

What is the difference between aniread and intsurv?

They serve adjacent needs but don't currently overlap on shipped themes. aniread and intsurv are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 intsurv?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniread and intsurv are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 intsurv?

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