SpikeInterface / SpikeInterface/spikeinterface

Getting spike amplitudes on each electrode of a tetrode for visual comparison between automatically and manually sorted clusters

Open
#2,553 0 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

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 spike distribution in six different electrode-electrode projection plots (spike amplitude on electrode 1 vs spike amplitude on electrode 2, spike amplitude on electrode 1 vs spike amplitude on electrode 3 ...), I was wondering if there is a function in Spikeinterface that can output spike amplitudes on each electrode of a tetrode for the automatically sorted units. It would be great to get the data and then plot to compare with manually sorted units.
Thanks!

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

No file, test, or entry point is named. Start by locating the SpikeInterface API for retrieving spike amplitudes from automatically sorted units, then check whether it exposes amplitudes per electrode for tetrode recordings. Done means obtaining data suitable for plotting electrode-pair amplitude comparisons against manually sorted clusters.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.