-
Notifications
You must be signed in to change notification settings - Fork 39
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
[BUG] Cellfinder 2D viewer not working on windows #26
Comments
Thanks to @FedeClaudi, this seems to be related to napari/napari#733. Should be an easy workaround. |
As per the issue above: Calling |
Thanks.
|
Alternatively, just pass the "theoretical" max from |
N.B. If this issue persists, it will need fixing for the curation interface too. |
Can confirm that the same problem comes up with curation interface. |
Fixed in a627661. Not sure if this should be made smarter though. Currently it just takes 2x max of the middle slice. |
@FedeClaudi @adamltyson I'm trying to chase down and eliminate any remaining contrast limit estimation bugs so that if users don't explicitly pass |
This is now the approach napari employs - see https://github.com/napari/napari/blob/dec5b9965d4a3fcea2d8314064465af14a97fec7/napari/layers/layer_utils.py#L25-L65 - it would be good to know if we are failing still |
@sofroniewn I couldn't replicate this issue, @FedeClaudi is this something you can test? Perhaps by loading raw data into the amap viewer (assuming you can actually access your data currently)? I'd like to remove my hacky fix and rely on napari dealing with this more gracefully if possible. |
Looks to be working (eda3c10), but I could never fully reproduce this. |
Describe the bug
The 2D viewer to inspect the results of cellfinder doesn't start on windows [gets stuck while loading the data].
The text was updated successfully, but these errors were encountered: