SpikeInterface / SpikeInterface/spikeinterface
phy2 manual merging: cluster_info.tsv
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hi,
read_phy is failing for me. I manually curate with phy2. I noticed that the cluster_info.tsv has blank entries. For the original clusters (which were merged), the group is blank; and for the newly created clusters the clsuter_id is blank.
This causes phy (pandas) to fail. Is this normal ? Is my phy installation doing something silly ? If so, happy to close the issue. But I'd still be interested in whether others have experienced something similar.
Cheers
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 at the read_phy entry point and reproduce the phy2 manual-merge case using cluster_info.tsv. Inspect how blank group and cluster_id entries are handled before the pandas failure. Done means establishing whether the blanks are expected and, if not, identifying the needed correction or documenting the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- pandas, python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100