There are occasional references throughout the neuroscope helper functions to data contained within the .clu and .res files.
This information has already been accessed, retrieved, and stored within the SortingExtractor object prior to running the conversion, and these helper functions should therefore utilize this rather than re-accessing the files again since this access can only be done via readtxt (not lazily).
One exception to this may be waveforms in the .spk.%i files as SpikeEventSeries whose indexing corresponds to the per-shank (not per-unit) .res files; of course, once the future version of waveforms as jagged array unit columns is implemented, we can just include that in SpikeInterface and would become a non-issue for that.
There are occasional references throughout the
neuroscope
helper functions to data contained within the.clu
and.res
files.This information has already been accessed, retrieved, and stored within the SortingExtractor object prior to running the conversion, and these helper functions should therefore utilize this rather than re-accessing the files again since this access can only be done via
readtxt
(not lazily)..spk.%i
files as SpikeEventSeries whose indexing corresponds to the per-shank (not per-unit).res
files; of course, once the future version of waveforms as jagged array unit columns is implemented, we can just include that in SpikeInterface and would become a non-issue for that.