Jake Pennington

Thanks. I still didn't see any memory problems, it never used more than about 2GB of video memory at any one time. I know it's annoying, but did you try...

Okay. I'll look into that, but you should be able to get around it by just typing or copy-pasting the file location into the text area instead of clicking on...

The warning isn't meaningful, it's something we're aware of. However, we did suppress that warning a few versions ago around the same time that we implemented some bug fixes that...

Hello, That error is raised if the file you selected doesn't have an appropriate file extension. What does the full path to the file look like?

Correct, a `.cbin` file would not work. There is a way to pass array objects directly to `run_kilosort` through the API, which I can explain if needed, but looking briefly...

Please let us know if you have any more questions about this, I'm closing this for now.

Thanks, that's helpful.

This is fixed now with the latest code changes, I'll have it added to pip soon.

Which version of Kilosort4 was this? Also, just to clarify, you're saying there were spike times that were past the end of the recording?

Great, glad that fixed it! For future reference, `conda list kilosort` should give more detailed version information (if you're using conda as your environment manager).