Skip to content
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

Feature request: More silent reading of EDF files #5

Open
alexholcombe opened this issue Oct 10, 2024 · 3 comments
Open

Feature request: More silent reading of EDF files #5

alexholcombe opened this issue Oct 10, 2024 · 3 comments

Comments

@alexholcombe
Copy link
Contributor

alexholcombe commented Oct 10, 2024

Would be good to have a way to suppress the messages that for me always seem to occur when reading an EDF file, such as:

loadEvents = 1
setTrial End:  TRIAL_RESULT
loadEvents = 0

I confess I don't know exactly what these mean but they seem to reflect expected events, so it confuses users to see them printed out, especially in the context of code reading in a lot of EDFs, where these messages could drown out more informativ messages.

I don't understand the Eyelinks EDFAPI, but I'm wondering whether a silent=TRUE parameter could be optionally passed to e.g. extract_saccades, just as it is passed to extract_display_coords?

Maybe I could work on this if so. Thank you again for the package!

@alexholcombe alexholcombe changed the title Feature request: Feature request: More silent reading of EDF files Oct 10, 2024
@alexander-pastukhov
Copy link
Owner

@alexholcombe I'll take a look. This is not my code but rather EDF API messages. I will try to figure out whether it is possible to suppress them. Just to be sure: This happens when you call read_edf(), correct?

@alexholcombe
Copy link
Contributor Author

@alexander-pastukhov yes, but it's only a minor thing; there are probably higher priorities for the package, but point me to the associated call if you find it; I don't understand how the C bindings work.

@alexander-pastukhov
Copy link
Owner

@alexholcombe I've reached out to SR-Research and apparently these are debugging messages accidentally left over. They promised to turn them off in the upcoming release of the DevKit. I'll close the issue once it is no longer an issue (just to remind myself not to forget to check it).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants