Phy is running very slow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 430
- Forks
- 187
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 2
Description
Hi all,
I apologize for the vague issue, but this is the main problem: phy is running unusably slowly for us. It takes at least 10-20 seconds when switching between clusters in the clusterview, during which the program freezes when we try to curate a ~2h neuropixel recording clustered with Kilosort4.
I have tried to point params.py to recording.dat, temp_wh.dat, or the raw open ephys data, but the results are the same.
This is the case on one of our regular desptops (win 11, 16GB RAM, no GPU) and on the PC we use for clustering (also win 11, 96GB RAM, Nvidia RTX4000 Quadro GPU). We have Phy 2.1.0 and run it via Anaconda/Python 3.12.
I have no idea what's going on and would love some tips.
Susan
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 with params.py and reproduce the 10–20 second delay when switching clusters in clusterview using recording.dat, temp_wh.dat, and the raw Open Ephys data. Compare the behavior on the two Windows systems described; done should mean identifying the cause of the freeze and making cluster switching responsive for the reported Kilosort4 recording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- anaconda, python
- Domain
- data, desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100