Add load_templates_clusters parameter (kilosort/phy output)#4376
Add load_templates_clusters parameter (kilosort/phy output)#4376pas-calc wants to merge 2 commits intoSpikeInterface:mainfrom
Conversation
…refinement) Added a new parameter 'load_templates_clusters' to control loading of templates or clusters from Kilosort output. Updated logic to handle loading based on the parameter value.
for more information, see https://pre-commit.ci
|
Hi @pas-calc, thanks for this! It sounds like it's correct for the default to be "templates" since this always represents the "raw" outputs. This function is very new and hasn't been in a release version yet, so we don't need to be so careful about backward compatibility. Hence I would vote to make "templates" the default and remove the "auto" option. What do you think? Maybe we should also make it clear in the docstring that this function is only tested for data that has not been modified by Phy. EDIT: also, do you know if kilosort 2.5 also outputs both of these files? |
|
Basically I wrapped the original code inside the Kilosort2.5 outputs "spike_templates.npy" |
Added a new parameter 'load_templates_clusters' to control loading of templates or clusters from Kilosort output. Updated logic to handle loading based on the parameter value.
Have "auto" as default to ensure backward compatibility, as this was the previous implementation.
related:
#4373
We could also store a kwarg dict / attribute so that we later know from where we got the clusters, especially if "auto" was chosen.