-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Performance Discrepancy Between SAM Model Demo and GitHub Code #762
Comments
I have the same question. |
same problem |
Same issue. |
The online and library versions are probably using different hyperparamters. Checkout this notebook: https://github.com/facebookresearch/segment-anything/blob/main/notebooks/automatic_mask_generator_example.ipynb |
What exactly to check in the notebook? |
Cell 24 indicates the config options. The parameter names are mostly self
explanatory.
El mar, 17 de sept de 2024, 15:36, Ted Wong ***@***.***>
escribió:
… What exactly to check in the notebook?
—
Reply to this email directly, view it on GitHub
<#762 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMA6BZXPR7CVK7JPAT2Z6DZXBZD3AVCNFSM6AAAAABJPURO5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGYZTKMBWGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
same question. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I am working on segmenting car bodies in images using the Meta SAM model. I am facing a significant difference in performance between the UI demo on the official website and the code provided on the GitHub repository. UI demo performed remarkably well with just 1-2 clicks, however, when I attempted to use the code, results are very different and bad. Despite of providing multiple points, the results were not up to the mark as compared to the demo.
Using SAM Model Version:- "vit_h"
Used predictor_example file:- notebooks/predictor_example.ipynb
Examples:
Image 1:
Original Image:
UI Demo Segmentation: - Performed well with 4 foreground points and 3 background points.
My Code Segmentation: - Poor results with the same point placement.
Image 2:
Original Image:
UI Demo Segmentation: - Good results with 4 foreground points and 4 background points.
My Code Segmentation: - Poor results with the same point placement.
I would appreciate any insights into why this discrepancy is happening.
Could it be related to hidden hyperparameter settings, optimizers, or learning rates used in the UI demo that aren't included in the GitHub code?
If this is the case, would it be possible to provide some guidance.
The text was updated successfully, but these errors were encountered: