spiketimes exceeds recording duration

[lepmik]

When converting time stamps from loadSpikes in OpenEphys.py by dividing by the sample rate I get spike times that are larger than the recording duration e.g.

Spike time 1011.3367666666667 s exceeds duration 983.1765333333333 s

Am I converting time stamps wrongly?

[jsiegle]

Are you taking into account the recording start time (found in the messages.events file)? That will shift the continuous timestamps by a constant value (the spike and event times should already be shifted).

[lepmik]

We are saving with the binary lib, with t start = 0, that means I have to shift spikes and events back to 0? 2017-04-25 18:53 GMT+02:00 Josh Siegle <[email protected]>:

…

Are you taking into account the recording start time (found in the messages.events file)? That will shift the continuous timestamps by a constant value (the spike and event times should already be shifted). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADQn8H_MJVPQutssUpIqIH8FJy-hcJ_8ks5rziUAgaJpZM4NHXdA> .

-- Mikkel Elle Lepperød <http://cinpla.org/people/> Centre for Integrative Neuroplasticity (CINPLA <http://cinpla.org>) University of Oslo (UiO <http://uio.no>) Kristine Bonnevies hus, room 2513

[aacuevas]

There should be a messages.events file with a line like
XXX Processor: Rhythm FPGA Id: 100 start time: XXX@20000Hz
Substract the XXX to the raw timestamp value for spikes and events to align them to the 0-aligned timestamps of the continuous data.

Since the .dat file does not contain timestamps itself, it is always aligned to 0, but the events and spikes timestamps are stored in its raw format, with the hardware timestamps.