-
Notifications
You must be signed in to change notification settings - Fork 48
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
why are the metrics divided by 1000 here? #6
Comments
Hi, the implementation of this function is adopted from GCA-Matting, which I suppose is based on the official Matlab evaluation code. You can evaluate the real-world portrait dataset using the "Whole Image" score, or you can modify to support the detail map in the real-world portrait dataset (e.g., detail_map[detail_map>0] = 128). Sorry for being busy these days, I will also update the code to give better support later. |
does evaluation on real-world portrait also use metrics divided by 1000? |
Yes, same metrics are used in real-world portrait dataset |
Hi, in this table. TrimapFG and Trimap refers to different types of inputs to our model. Since DIM dataset only provides trimap as guidance inputs, we use it to simulate a rough segmentation mask in two ways: TrimapFG: we only use the definite foreground region of the trimap; Trimap: we use a soft version of trrimap (i.e. trimap / 255.0). You can refer to our paper or code for more details :) |
thanks for updating, i will solve them with your code. But one more question, does self._noupdate_u_v() updating your network weight during evaluation?
|
ok, it does not change the weight after eval forward |
MGMatting/code-base/utils/evaluate.py
Line 102 in 671678d
and can the code evaluates real-world portrait dataset?
https://github.com/yucornetto/MGMatting/blob/main/code-base/evaluation.py
The text was updated successfully, but these errors were encountered: