Jake Pennington

Thanks for submitting this. We're not going to merge the changes at this time. The changes are more involved than expected, and we don't have a way to test this...

Hello, You can see example code for this here, in the "Plot the results" section: https://kilosort.readthedocs.io/en/latest/tutorials/basic_example.html ``` import numpy as np import pandas as pd from pathlib import Path results_dir...

Hello @LiorDor1 Most of this is already done in that snippet I shared, you just have to combine the variables into a table if that's what you want. This will...

We're already planning to make these kinds of changes, it just hasn't happened yet. I have to coordinate with @marius10p when deciding on new naming conventions, so it's likely we'll...

That's what comments/documentation are intended to accomplish, we're just behind on updating that. I will note, however, that most of the variables you list are in fact documented in `kilosort.run_kilosort`....

It looks like this is happening when KS4 tries to allocate space for the new file when saving the preprocessed data. That file will be the same size as your...

Yes, `temp_wh.dat` will always be int16 regardless of the input data type. Some normalization happens during preprocessing, so I'm not sure how that will translate to visualizing in real units....

Correct, Kilosort4 does not support z-axis information. The first thing I would try is simply duplicating the contact positions but shifted over by the shank width (60um) on the x-axis....

Closing this for now, please feel free to re-open it later when you have an update.

We don't support Apple's Metal chips. Our recommendation is to use a different machine with an Nvidia GPU. If you're determined to use the M4 chip, you'll have to figure...