-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cellprofiler 4.0.7 and CellPose 3.0.7 - RunCellpose is out of date #252
Comments
And the available switches for CellPose 3.0.7:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Firstly, my versioning information:
I am using the Cuda SDK v12.4, and torch version 2.4.0
I am using a conda environment with both CellProfiler and Cellpose running in it. I have installed the GUI version of CellPose, and it runs well with CUDA/GPU processing enabled.
However, there are issues with the RunCellpose plugin in CellProfiler. runcellpose.py was pulled via git clone today, 8th August 2024.
Issues:
In the CellProfiler project pipeline, the RunCellpose items are crossed ❌ with the "Value not in decimal format" notification. With the workaround I have, that issue doesn't affect the processing.
The models in the Cellpose 2.x are now mostly removed, but are referenced by the current runcellpose.py.
net_avg
used by the plugin is no longer used by CellPose 3.0.7, so the plugin throws an error and exits.If I comment out
net_avg
lines 536, 551, and 610. The plugin works, but with CPU only (see next).core.use_gpu
on line 717 in the script fails, because there's no reference tocore
:****Worker 0: TORCH CUDA version installed and working. ****
:So in summary, there are a few major issues with runcellpose.py and CellPose 3.0.7. My current edits to remove net_avg, make it work, but only via CPU. I am using custom trained models generated in CellPose 3.0.7.
I hope these issues can be resolved. It would be good to get GPU processing working. I'll continue to look at the python script to see what I can do.
The text was updated successfully, but these errors were encountered: