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

Extraction issue for feedback on error trials #249

Open
cskrasniak opened this issue Jul 21, 2021 · 0 comments
Open

Extraction issue for feedback on error trials #249

cskrasniak opened this issue Jul 21, 2021 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@cskrasniak
Copy link

cskrasniak commented Jul 21, 2021

for 8 sessions ( all ephys sessions for mouse zadorlab/CSH_ZAD_029, example eid 1ec23a70-b94b-4e9c-a0df-8c2151da3761) feedback times were not extracted on error trials. This arises from a known issue where the rig was miswired such that the sound pulses are 150hz TTLs instead of single pulses. It seems like a fix was implemented for go cues as those are correctly picked up, So if whatever go cue extraction fix was applied could also be applied to error tones that should work.
All effected eids:

1ec23a70-b94b-4e9c-a0df-8c2151da3761
5522ac4b-0e41-4c53-836a-aaa17e82b9eb
993c7024-0abc-4028-ad30-d397ad55b084
9a7e3a4b-8b68-4817-81f1-adb0f48088eb
c7bd79c9-c47e-4ea5-aea3-74dda991b48e
e349a2e7-50a3-47ca-bc45-20d1899854ec
fcd49e34-f07b-441c-b2ac-cb8c462ec5ac
fece187f-b47f-4870-a1d6-619afe942a7d

example image from taskQC viewer showing that go cues are correctly detected for this 150Hz sound TTL but error cue times are not:
image

@cskrasniak cskrasniak added the bug Something isn't working label Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants