Closed kabilar closed 2 years ago
Hi @Alvalunasan, would this be possible for sessid
758539? If there are more cases, I will have to think about a smarter way for the element
to handle this situation. Thanks.
I think we can enforce to have kilosort results in a subdirectory. I will talk with ephys team about it.
![Uploading Screen Shot 2021-10-21 at 9.10.59 AM.png…]()
Only instances of session directory containing kilosort results that are not in a subdirectory:
Session 751666 possibly does not have an issue because there is also other directory with some kilosort results for that subject and date: Thomas/T219/T219_2019_12_05/spikesort_2019_12_09_01_01_01_ks2jrc_thomas
Hi Kabi, Adrian agreed to correct these sessions (by creating a SORT_ID) subfolder. Also, the SORT_ID subfolder should be enforced in the future
Great. Thank you.
Hi @Alvalunasan, I was going to transfer this Issue
to the new public vathes fork, and privately archive the current detached repository. Is there any information in this Issue
that we would not want to be in the public repository? If so, I can delete those comments and then transfer the issue. Thank you.
Hi @kabilar no I think it is fine to let all the Issues you find on the public repo. Thanks for doing this.
Ephys pipeline in brodylab is not used at all so I will close this issue.
element-array-ephys
the Kilosort results should be in a subdirectory of the session directory.acquisition.AcquisitionSessions
?