Feature #896: Extend Elan backend
Support proper temporal intervals in Elan backend
|Assignee:||J. Moringen||% Done:|
|Target version:||Robotics Service Bus - rsb-0.18|
Currently, only the
create timestamp is used when writing events to an Elan file.
We have to specify how an additional end-point of an event can be specified. The current idea is to use a user-defined timestamp to specify this.
#1 Updated by D. Klotz over 10 years ago
Using a second user-defined timestamp in the same event to define the extent in time will not be possible in all cases. Think of logging live events in a real-time (study, experiment...) setting. There, the end of the timespan will not be known in advance when the event "starts". Two events (maybe related by a cause vector) would probably work better in that case (and maybe even in general).
Would also be interesting how the "content" of the event would be specified, i.e. what data type would actually be logged and how does that relate to the annotation content in Elan.