spikeinterface
spikeinterface copied to clipboard
A Python-based module for creating flexible and robust spike sorting pipelines.
Using the spikeinterface.extractors.read_neuralynx does not seem to work on headers created using Cheetah software 5.6.2. Works fine on header from Cheetah 6.4.1. Here is a link to google drive with...
For the hybrid project, make a function that can get Templates from any recording. To be discussed, as some features to play/interact with Templates are currently only written for WaveformExtactor...
Could such a solution work @samuelgarcia ? This is a patch to try to address #2001. The idea is that if we have a PeakSource node, and no peaks between...
Hi I encountered an issue that I lost the spike train for the merged units when I extract the waveform from the sliced sorting from a concatenated sorting I used...
Hi, I am still quite new to Spikeinterface and was thinking about a way to compare automatic and manual sorted clusters for tetrode recordings. Since manual clustering is based on...
After discussing with @alejoe91, we realized that it would be good to remove noise_levels from the function signatures, since now noise_levels can be saved as attributes of the recording. By...
As mentionned in #2387 this PR fixes the problem of return_scaled within the node pipeline. Now, everything will be handled with the scaling, and while it might be slightly slower...
`analyzer.compute("spike_amplitudes")` is really slow (90s in my case) even when the sorting contains a single unit with two spikes. Chunks of recording with no spikes should be skipped.
Extracting traces in parallel to speed up get_noise_levels (or any other traces related functions)
We can extent the pipeline machinery as explained in #2380 in order to get data chunks in parallel. The list of chunks passed to the ChunkRecordingExecutor can be customized accordingly,...