-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messages not parsed in edf file #15
Comments
What is in your samples table?
If you indeed have data in there you probably need to set a trial_marker parameter. For example:
When I need to determine a useful trial marker I use the SR tool edf2asc to dump the edf out as ascii, then parse the lines beginning with MSG until I find a suitable indicator of the start of a message for a given trial. .gs |
Side note - the above seems to not be necessary with data that I have from a Duo. I'm not 100% sure why. Could be how the capture was run and messages injected but not sure. |
Hello, We are having the same issue with our EDF files coming from an Eyelink 1000 Plus. As in the first comment, the following code (the EDF file is attached)
gives
Using filter =‘all’ yields the same result. Now, if I do
as suggested, it parses the messages. However, I am interested in a more general application of the tool where users would be able to parse all the messages without specifying trial markers in one call of edf.pread. Is that something that is possible? Thank you for any help! |
Try this: |
This works, thank you! |
The "messages" from our edf files generated from our EyeLink 1000 Plus are not parsed by pyedfread (see attachment for an example edf file). We'd be greatful for an hint on what's going on.
The following code
prints
Our pyedfread version is the latest from GitHub.
blub.zip
The text was updated successfully, but these errors were encountered: