You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, while I can't comment on whether this is true for all cases, the header is not exposed when loading events. Importantly, the sample rate is nowhere to be found in the recording object. As an example, let data_dir be a path pointing to a directory with .continuous and .events files.
At this point, it seems the user should be able to determine the sample rate information, as this information is contained within the header for the .events file, however it is apparently discarded:
Certainly, the header information from this events file should be accessible through a recording object. I am unsure what the best way to address is, or if it is already being worked on, but I thought I would bring attention to the problem.
EDIT: I have temporarily solved this for my personal requirements by simply storing the header dict returned by load in self.header.
The text was updated successfully, but these errors were encountered:
Hi Kyle, thanks for bringing this up. We definitely want this info to be accessible in the Session object, but I'm not sure about the best place to put it.
Would it make sense to add a top-level metadata property that stores general information about the recording (e.g., start time), as well as info about individual processors? For example, the sample rate for each processor could be accessed via:
Hi, while I can't comment on whether this is true for all cases, the header is not exposed when loading events. Importantly, the sample rate is nowhere to be found in the recording object. As an example, let
data_dir
be a path pointing to a directory with .continuous and .events files.At this point, it seems the user should be able to determine the sample rate information, as this information is contained within the header for the
.events
file, however it is apparently discarded:open-ephys-python-tools/open_ephys/analysis/formats/OpenEphysRecording.py
Lines 130 to 140 in 5b4750f
Certainly, the header information from this events file should be accessible through a recording object. I am unsure what the best way to address is, or if it is already being worked on, but I thought I would bring attention to the problem.
EDIT: I have temporarily solved this for my personal requirements by simply storing the
header
dict returned byload
inself.header
.The text was updated successfully, but these errors were encountered: