-
Notifications
You must be signed in to change notification settings - Fork 3
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
MAE computation is different from Ref-NeRF #7
Comments
Thanks for bringing this to my attention. I will recalculate the values and update the paper. New values: I'll also fix the NVDiffRec and NVDiffRecMC values. |
I have updated the arxiv paper. |
This is probably caused by the incorrect mixing mode. Can you check the output config.yaml to see if the diffuse mixing mode is set to "fresnel"? diffuse_mixing_mode: "fresnel" If it isn't you can set this by passing model.arch.model.diffuse_mixing_mode="fresnel" |
Thanks for the help! I have made this the default. |
Hi, I have been running experiments on Shiny Blender recently, and I want to compare my results with yours. But I find that your MAE computation is different from Ref-NeRF.
Ref-NeRF averages MAE weighted on alpha*acc:
https://github.com/google-research/multinerf/blob/5b4d4f64608ec8077222c52fdf814d40acc10bc1/internal/ref_utils.py#L45-L50
https://github.com/google-research/multinerf/blob/5b4d4f64608ec8077222c52fdf814d40acc10bc1/eval.py#L156-L163
But you average MAE on all pixels.
nmf/renderer.py
Lines 375 to 376 in 3eb6039
Since transparent pixels' MAE is 0, final results would be much smaller than Ref-NeRF's.
The text was updated successfully, but these errors were encountered: