problems with trace view
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 430
- Forks
- 187
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 2
Description
Hello! I was wondering if someone could help me and explain how does phy know which probe in trace view to color when there is a recorded spike? In this picture you can see that phy has colored an event across all of the channels, instead of the single channel it was sorted on? I am trying to figure how to correct this. 
Additionally, as can be seen in the picture, I have a number of short vertical lines that get drawn below the waveforms on a channel? Why is this happening, and how can I get rid of them? Finally, Even though I have chosen the cluster group color scheme, there are seemingly random patches of light green painted at numerous points? Does anyone know what this represents? Cluster view shows only 2 clusters for this channel? Thank you for any help!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior in phy's trace view using the screenshot and the described recording and cluster-group color settings. Inspect how spike events, short vertical channel marks, and light-green patches are rendered. Done means determining whether each visual element is expected or correcting the trace view so coloring matches the selected channel and cluster scheme.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100