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

incorrect metadata values for stim trial structures #129

Closed
jihyunbak opened this issue Feb 19, 2022 · 4 comments · Fixed by #130
Closed

incorrect metadata values for stim trial structures #129

jihyunbak opened this issue Feb 19, 2022 · 4 comments · Fixed by #130

Comments

@jihyunbak
Copy link
Member

Current stimulus metadata are incorrect in many places. Working on a fix.

Here's a teaser:
https://github.com/BouchardLab/pyraat/blob/main/notebooks/auditory_stimuli_check.ipynb

@jihyunbak
Copy link
Member Author

jihyunbak commented Feb 19, 2022

fixing this would also resolve these issues:

(EDIT: maybe not #127. Looks like a block-specific problem)

@jthermiz
Copy link
Member

Thanks for going through all the stimuli and optimizing the parsing @jihyunbak ! It looks like you've solved all of the mark finding issues.

@jthermiz
Copy link
Member

I just realized that the signals you are analyzing are the .wav signals but you will eventually want to analyze the marker signal as recorded by the neural acquisition system (in this case TDT) and optimize detection of those markers. The sampling rates are different for these signals (Audio: 96k? vs TDT: ~12k or ~25k) and when the stimulus is played is variable (depends on when human presses play on DVD player) wrt to the start of the neural recording. Does that make sense?

@jihyunbak jihyunbak mentioned this issue Feb 22, 2022
4 tasks
@jihyunbak
Copy link
Member Author

@jthermiz You were right - I did the analysis on the recorded marks instead. It required a different solution for the missing wn2 marks (the first mark was much lower than all others), which is now part of PR #130

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

Successfully merging a pull request may close this issue.

2 participants