-
Notifications
You must be signed in to change notification settings - Fork 46
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
micro_sam.automatic_segmentation error #773
Comments
Hi @aloboa, Can you try installing |
After installing opncv, I still get:
The same command works without the |
Hi @aloboa, Can you share with me the CLI script you use? (that will help me reproduce the issue from my side) |
It is just a command typed on the linux terminal: It nicely works in 1'30'' without the |
Thanks for sharing the details @aloboa. We figured out the issue and should be fixed by #780. Can you pull the latest commits in our Let us know if the issue is fixed. |
I do:
And then:
|
Big problem: micro_sam.automatic_segmentation was working with my gpu using the former version if the
Should I go back to |
Hi @aloboa, Can you try running in the code via terminal in the activated
|
It is FALSE, but I remember it was TRUE before the upgrade. |
Hi @aloboa , |
I do not understand. Why was the GPU working with the previous version of micro-sam? This problem raises after I do the |
That is indeed quite weird. In this case, I would suggest to install a new environment via |
Also, I get error even if selecting 'cpu':
|
This is because you are trying to cache embeddings, but the embedding file exists already and the embeddings were computed for a different image. Removing the file |
Same error with a simpler command:
|
This is a different error, but it points to an issue in our recent change. We will get back to you about this ASAP. cc @anwai98 : it looks like the current logic for choosing AMG vs. segmentation decoder does not work correctly. We should fix it and add a test for this so that we can ensure its functionality in the future. |
Hi @aloboa, Thanks for spotting the issue. I've added a PR where this should be fixed. We will ping you here once it's merged. @constantinpape I overlooked a minor detail in our heuristic which led to the issue. I've added some more CLI-level tests now. |
Thanks, but I still wonder why my GPU was working with the previous version (I actually checked with the same python command) and not now. |
I would recommend following the instructions suggested by @constantinpape (also highlighted in the quoted text below) to make a fresh installation from source (it's often hard to back-trace the source issue over multiple hot fixes).
|
Many thanks for your help.
cuda is back to work but
|
Hi @aloboa, You need to provide the device as |
I apologize for the typo...
|
Ahha yes. This PR has not been merged yet (there's some super minor detail I still need to take care of). We'll ping you here once the PR is merged. |
Hi @aloboa, The issue you faced should be fixed now (you need to pull the latest state, and things should work as expected). Let us know if you come across any other issues. I'll go ahead and close this as the aforementioned issue is fixed. |
I confirm |
If I do:
(sam) alobo2@alobo-ws:~$ micro_sam.automatic_segmentation -i "/media/alobo2/SP PHD U3/Islandia/Alteration/Cristina_nDann/DI17_2/DI17_2.tif" -o "/media/alobo2/SP PHD U3/Islandia/Alteration/microsam/DI17_2labelsout.tif" -e /home/alobo2/embeddings -m vit_b --tile_shape 1024 1024 --halo 256 256 -d 'cpu' --pred_iou_thresh 0.7 --stability_score_thresh 0.5 --box_nms_thresh 0.5 --min_mask_region_area 10
I get:
The text was updated successfully, but these errors were encountered: