Commit 6b5e011
committed
ENH: Read and store "START" and "END" events from EDF file
These events indicate when the Eyetracking started and stopped recording, respectively. There can be multiple of these events, meaning that the eyetracker started and paused (e.g. during a calibration sequence or between trials).
The pyeparse authors appeared to know about "START" and "END events in EDF files, but they just used python's `pass` to skip handling these events.
I adjusted our event handlers to give both start and end events an entry in `EDF["discrete"].
It's important to store this info because for some recordings (read: users) there is a time gap between an end event and the subsequent start event. In other words, there is a pause/gap in the recording that the user might want to know about.1 parent 1d57c07 commit 6b5e011
1 file changed
+18
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
151 | 151 | | |
152 | 152 | | |
153 | 153 | | |
| 154 | + | |
| 155 | + | |
154 | 156 | | |
155 | 157 | | |
156 | 158 | | |
| |||
209 | 211 | | |
210 | 212 | | |
211 | 213 | | |
212 | | - | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
213 | 224 | | |
214 | 225 | | |
215 | 226 | | |
| |||
541 | 552 | | |
542 | 553 | | |
543 | 554 | | |
| 555 | + | |
| 556 | + | |
| 557 | + | |
| 558 | + | |
544 | 559 | | |
545 | 560 | | |
546 | 561 | | |
| |||
592 | 607 | | |
593 | 608 | | |
594 | 609 | | |
595 | | - | |
596 | | - | |
| 610 | + | |
| 611 | + | |
597 | 612 | | |
598 | 613 | | |
0 commit comments