cortex-lab / cortex-lab/phy

Regarding the issue of drawing 2D probes.

Open
#1,276 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: visualization type: enhancement
Dominant language
Python
Stars
430
Forks
187
Avg merge
2h 31m
Merged PRs (30d)
2

Description

Hi, I wish to display a 2D probe array in certain views, such as the clusterscatter view. I want the x-axis and y-axis to represent the physical coordinates of the probes, but currently, both x and y can only be set to depth. I have checked the available properties, and it seems that there is only one property, depth, and there is no property such as length. However, my probes are set up with x and y coordinates.

These are the properties of my clusters.
{'id': 140, 'ch': '258', 'sh': 0, 'depth': 1785.0, 'fr': 0.6933564452148405, 'amp': 58.766525, 'n_spikes': 208, 'amplitude_cutoff': None, 'channel_group': 0, 'group': 'unsorted', 'isi_violations_count': 0.0, 'isi_violations_ratio':
0.0, 'presence_ratio': 1.0, 'si_unit_id': 140, 'snr': 5.327821730321634, 'is_masked': False}

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 with the clusterscatter view and inspect how its x- and y-axis properties are selected from cluster data. Trace how probe coordinates are represented and mapped into view axes. Done means a 2D probe array can use its physical x and y coordinates rather than depth for the two axes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-visualization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.