SpikeInterface / SpikeInterface/spikeinterface

Question `commen_reference` for multi-shank probes:

Open
#3,865 3 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

I had a brief conversation with the CambridgeNeurotech about commen_reference today. It seems that since I am using a multi-shank probe, it would be great to take channels from one shank as a reference for channels from the other shank, and the other way round (instead of calculating the reference based on all channels). Has anyone tried this method before? In addition, I understand that current version of commen_reference can take dictionary as an input, which helps process data with multi-shank probes. In this case, how does the function work when those reference methods: "global" | "single" | "local" are called? I was wondering if the easiest way to take this concern into account when taking the reference would be giving local_radius and not splitting channels into dictionary, so that for every channels there would be an unique combination of channels set for calculating common reference (depending on the radius). Does it make sense?

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 inspecting the existing commen_reference implementation and how its global, single, and local methods handle dictionary inputs. Clarify the intended multi-shank behavior and whether local_radius should replace channel grouping; the issue needs a decided scope and explicit tests before completion can be assessed.

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.