tulpa
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
Comparison · Analytics
aniread vs sftime
A side-by-side editorial comparison of aniread and sftime — release velocity, themes, recent moves, and the top alternatives to consider.
aniread vs sftime: at a glance
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.
What is sftime?
The spatiotemporal companion to sf, moving at the pace of the packages around it.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
aniread vs sftime: editorial side-by-side
aniread
3.8ANALYTICS
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.
sftime
0.0ANALYTICS
The spatiotemporal companion to sf, moving at the pace of the packages around it.
◆ Current state
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
◆ Where it's heading
The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.
◆ Prediction
Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.
Alternatives to aniread and sftime
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 sftime.
AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
NocoDB
Interfaces gets the permissions layer it needed, one release after launching.
ManageEngine RecoveryManager Plus
RecoveryManager Plus keeps widening its backup coverage across the Microsoft identity estate.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
silx
silx settles into maintenance a release after its PySide6 migration
See all aniread alternatives → · See all sftime alternatives →
Recent activity from aniread and sftime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoanireadv0.6.0 — one entry point for every format ⚡
- 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
- 1mo agoanireadread_boris() imports behavioural events as anievent objects
- 3mo agosftimeExamples switched to the native R pipe
- 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
- 3mo agoaniready-origin standardised to bottom-left across eleven readers ⚡
- 0y agosftimeFixes the cubble namespace version check
- 1y agosftimeConverts from spatstat, sftrack and cubble objects
Frequently asked questions
What is the difference between aniread and sftime?
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 sftime?
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 sftime?
Top sftime alternatives in Analytics are ranked by recent ship velocity. Browse the "sftime alternatives" section above for the current picks, or visit /alternatives/sftime for the full list with editorial commentary on each.