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

fail_eye_tracking isn't consistent with actual eye tracking data availability #127

Open
atombysx opened this issue Jul 13, 2021 · 1 comment

Comments

@atombysx
Copy link

Hi all,

Thanks for the toolbox! It's really helpful.

I'm performing analysis on eye tracking data. Even though fail_eye_tracking parameter has values 0, the experiments do not have eye tracking data available. Example IDs: 501574836, 501836392, 502368172, 508596945, 524848692, 531348161, etc.

I checked the NWB files and it doesn't contain the fail_eye_tracking parameter. I wonder how the fail_eye_tracking parameter is assigned to logical values?

Many thanks,
Adam.

@ehennestad
Copy link
Collaborator

ehennestad commented Dec 16, 2023

For the record:

This observation is correct. The NWB files for the mentioned sessions do not contain eye tracking data. The visual coding session table which is retrieved using the Allen Brain Observatory API does not have the correct value for for the fail_eye_tracking parameter. This seems to have been corrected in the session table which is available from the Visual Coding S3 Bucket.

Todo:

  • Get the session table from S3 bucket instead of API

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