Open bharvey-neuro opened 2 months ago
HI,
@yger can confirm, but I think that the template matching step has hardcoded chunk sizes
Yes, indeed, in spyking circus 2, there used to be a hardcoded limit for the find_peaks procedure (if not using wobble). Are you using the latest version from main ? Because not sure this is still in place. However, the reasons was that smaller chunks are faster for the template-matching step algorithm, despite counterintuitive. But this should not harm the results
Hello,
I am new to using spikeinterface, and am trying to sort spikes using spykingcircus2 for multiple-stereotrode data. I'm currently on version 100.8.
I have imported, band-passed, and common-referenced my Intan RHS file, and correctly saved it out prior to running spykingcircus.
To correct for using stereotrodes instead of a typical array- or shank-based probe, I've run the following block (region/coords list shortened for brevity):
This should, I believe, allow me to run the sorter using 'brain region' as a property to only run each stereotrode pair against one another.
The series of commands I'm currently using to then execute spykingcircus is:
So, all that said, my current issue is that when spykingcircus2 is extracting waveforms, the chunk_size of joblib is working correctly. However, when the "find spikes" operation is run, my chunk_size is limited to 3000.
Can anyone advice on how to change this chunk size to speed up this process? I'm trying to analyze chronic recordings so ease and speed of processing is important to me!
Thanks!