You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm currently trying to sort a recording with a file size of 264GB. In the GUI the data looks absolutely fine.
When I just sort the first 100s, everything runs through smoothly. But when I try to sort the whole thing I get an error somewhere between batch 2601-2701.
Interesting enough the drift trace plot also looks rather suspicious. It has a few huge outliers
The biggest outlier happens to be 2670. So right in the batch of batches, where the error occurs.
So I was wondering whether such a huge outlier would maybe pose a problem to Kilosort? Not sure though how it should be really connected to CUDA. But on the other side, such a coincident seems rather unlikely.
I don't exactly know how KS3 works, but if batch sizes are always the same, than batch 2670 should occur around 5744 seconds into the recording. Inspecting the data at this point didn't show anything suspicious.
The text was updated successfully, but these errors were encountered:
Hi,
I'm currently trying to sort a recording with a file size of 264GB. In the GUI the data looks absolutely fine.
When I just sort the first 100s, everything runs through smoothly. But when I try to sort the whole thing I get an error somewhere between batch 2601-2701.
This is the console output of matlab
Interesting enough the drift trace plot also looks rather suspicious. It has a few huge outliers
![batch_outliers](https://user-images.githubusercontent.com/42135900/152203737-0488e8be-9af5-4324-82e6-ef5897fbc554.png)
The biggest outlier happens to be 2670. So right in the batch of batches, where the error occurs.
So I was wondering whether such a huge outlier would maybe pose a problem to Kilosort? Not sure though how it should be really connected to CUDA. But on the other side, such a coincident seems rather unlikely.
I don't exactly know how KS3 works, but if batch sizes are always the same, than batch 2670 should occur around 5744 seconds into the recording. Inspecting the data at this point didn't show anything suspicious.
![KSscreenshot](https://user-images.githubusercontent.com/42135900/152204687-16b75877-e7ec-4cc4-82e5-775cb163d2ae.png)
The text was updated successfully, but these errors were encountered: