-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improved QuPath integration #39
Comments
Is there any chance something has changed on the Kiosk end that might have resulted in the errors shown in this issue: https://forum.image.sc/t/using-deepcell-with-qupath/60265/2?u=research_associate |
It sounds like the issue is a 400 error response. Browsing through the linked groovy script, I think that the |
That does bypass the original error, but it still seems the script might no longer work due to other changes. INFO: Waiting for 1 task(s) to complete ERROR: java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) |
Although the error message you posted has a specific shape on the x/y dims, I think what's actually causing the issue is the channels dimension, which in the image you provided is only a single channel. The model expects a two-channel image |
Ah, I was aiming for the simplest option. What text option do we use for nuclear segmentation only? Or is the expectation passing the DAPI channel twice? |
If you pass a nuclear and membrane channel, you'll get both nuclear and cell segmentation. You can then decide what you want to do with each segmentation. If you didn't acquire a membrane marker as part of your panel, then just pass a blank channel as the membrane marker. |
Pete put together the following script for improved QuPath usability: https://gist.github.com/petebankhead/db8548a0112bad089492061bf8046430
Once we figure out next steps for QuPath, we can decide what we want to do with this script.
The text was updated successfully, but these errors were encountered: