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

Filename should only use Go run_properties$duration's #100

Open
nohelix opened this issue Mar 8, 2024 · 1 comment
Open

Filename should only use Go run_properties$duration's #100

nohelix opened this issue Mar 8, 2024 · 1 comment

Comments

@nohelix
Copy link
Collaborator

nohelix commented Mar 8, 2024

Issue

Naming scheme uses only Go trials to determine both frequency (kHz) and intensity (dB) ranges, but uses all (Go & No-Go) durations (ms).

Affected naming schemes

BBN, Gap, and possibly Tonal (not currently affect but could be)

Example problem file

Blue6_edge_BBN_60dB_1-2000ms_12s_BG_PKN_40dB_20240307-152003_BOX#006.zip

Results in errors:
Note you can ignore the edge_ at the beginning of the file name

Caution: mismatch in provided filename: edge_BBN_60dB_1-2000ms_12s_BG_PKN_40dB
calculated filename by contents: BBN_60dB_0-2000ms_12s_BG_PKN_40dB
ACTION REQUIRED: Was rat run on the wrong file?
ERROR: Filename -- BBN_60dB_0-2000ms_12s_BG_PKN_40dB -- does not match
Assignment -- edge_BBN_60dB_1-2000ms_12s_BG_PKN_40dB

Error results from a 0ms stim which is the No-Go (Type 0).

Solution

Similar to how go_kHz_range range is determined at the start of all the file names, go_ms_range needs to be calculated.

@nohelix
Copy link
Collaborator Author

nohelix commented Mar 8, 2024

After roll out of fix, I will need to remove files that have incorrectly generated names and reload them.

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

No branches or pull requests

1 participant