facebookresearch / facebookresearch/segment-anything

Reproducing segmentation results shown in the demo

Open
#230 6 comments 20 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
54.9k
Forks
6.4k
PR merge metrics
No merged PRs in 30d

Description

Here are the segmentation results obtained by using the auto-segmentation button provided on the official website (https://segment-anything.com/demo)

![image](https://user-images.githubusercontent.com/41274618/232478670-9a70ef72-d228-43a3-9eb7-a48658007125.png)
![image](https://user-images.githubusercontent.com/41274618/232478726-4df561ee-d555-433b-9962-fb28b01f7805.png)

These are the segmentation results generated using the released code. Specifically, I used the ViT-H model with all hyperparameters set to their default values.
![image](https://user-images.githubusercontent.com/41274618/232478912-a81ae90c-5a0b-4eba-8d0c-8372fccd4674.png)
![image](https://user-images.githubusercontent.com/41274618/232479009-9311087a-a188-4742-9c25-96afa0a440bd.png)

The results generated by the released code are obviously poorer than those obtained from the official website. Why is this the case, and what model is used in the website version?

Contributor guide

Open the contributing guide

Research direction

Start by comparing the official website demo with the released code using the ViT-H model and its default hyperparameters. Determine why the segmentation results differ and identify which model the website version uses; done means providing a clear explanation of the discrepancy.

Written by the indexing model from the issue text.

Assessment

Domain
computer-vision, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.