SpikeInterface / SpikeInterface/spikeinterface

Whitening - computing the covariance matrix without spikes

Open
#2,017 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
847
Forks
280
Avg merge
3d 9h
Merged PRs (30d)
29

Description

In some implementations (KS, Spyking Circus) the spikes are removed before computing the covariance matrix used for whitening. In the whiten.py pre-processing module as far as I can tell the random chunks used for the whitening matrix computation contain spikes. Is it worth including an option to remove spikes using some absolute threshold?

It would be great to also here any thoughts / advice people have on the whitening step. My understanding it's primary uses include reducing the spatial extent of spikes across channels to improve separation of clusters. In which case, I guess it would make sense to include the spikes in the estimation of the covariance matrix. Otherwise if the purpose is to remove correlated noise, then not including the spikes (at least intuitively at least) makes sense.

In general I am quite interested in this so if anyone can recommend any readings it would be much appreciated!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading src/spikeinterface/preprocessing/whiten.py and tracing how random chunks are selected for the whitening matrix. Review the linked KS and Spyking Circus references, then clarify whether spike removal is needed and what an option should mean; done requires an agreed behavior and corresponding implementation or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.