MOVEDepth icon indicating copy to clipboard operation
MOVEDepth copied to clipboard

Missing the evaluation for fused depth

Open xjixzz opened this issue 2 years ago • 10 comments

Hi,

Thank you for sharing your project! It is really amazing.

It seems that the evaluate_depth.py provides the evaluation for mono depth and mvs depth, and upper bound results, but lacks the evaluation for fused depth. I tried to add the evaluation code for fused depth only to find that fused depth is worse than mvs depth with my evaluation code. The test results with your pretrained weights are as follows:

mono results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.113 & 0.823 & 4.724 & 0.190 & 0.879 & 0.960 & 0.981 \

mvs results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.094 & 0.704 & 4.389 & 0.175 & 0.902 & 0.965 & 0.983 \

fuse results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.112 & 0.818 & 4.709 & 0.190 & 0.879 & 0.960 & 0.982 \

upbound results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.082 & 0.618 & 4.135 & 0.162 & 0.915 & 0.969 & 0.985 \

I also tested my own trained model, the results are as follows: mono results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.116 & 0.920 & 4.868 & 0.193 & 0.874 & 0.959 & 0.981 \

mvs results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.097 & 0.785 & 4.512 & 0.177 & 0.899 & 0.963 & 0.982 \

fuse results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.098 & 0.788 & 4.518 & 0.177 & 0.899 & 0.963 & 0.982 \

upbound results: abs_rel | sq_rel | rmse | rmse_log | a1 | a2 | a3 | & 0.086 & 0.698 & 4.269 & 0.165 & 0.911 & 0.968 & 0.984 \

I think there must be something wrong with my modification of the evaluation code. Could you please update the evaluation code to test fused depth?

xjixzz avatar Sep 26 '22 02:09 xjixzz

I also encountered the same problem. Is this problem solved?

youtufan avatar Feb 01 '23 05:02 youtufan

Not yet

xjixzz avatar Feb 01 '23 08:02 xjixzz

I have the same question. It seems that the mask for fused depth did not work on the evaluation. And the fused depth is always worse than the mvs depth.

RuijieZhu94 avatar Feb 21 '23 05:02 RuijieZhu94

Is this operation even reasonable? If I can conduct tests in this manner, I could churn out ten top-tier conference papers in a year LOL.

Adam-Zha avatar Feb 24 '23 02:02 Adam-Zha

I have the same problem. Since there is no reply by author from Sep 26, 2022 to now, I guess that something is wrong in paper or in codes.

logicred avatar Feb 24 '23 02:02 logicred

Hi @xjixzz , could you please provide the revised version of evaluate_depth.py? I encountered the same problem with you. But sadly I did not managed to reproduce the same "fuse results" with yours. Thanks a lot!

CydKnocking avatar Mar 02 '23 14:03 CydKnocking

Here is my revised evaluate_depth.py @CydKnocking

xjixzz avatar Mar 03 '23 02:03 xjixzz

@xjixzz Thank you for your code! I got similar results with yours when tested on my own trained model.

CydKnocking avatar Mar 03 '23 07:03 CydKnocking

Has anyone solved the problem on fused results?

fanrz avatar Nov 17 '23 14:11 fanrz

The author mentioned in the article that the trust mask seems to have no effect. In the training logs, it's observable that the MVS depth map and the fused depth map are identical, suggesting there might be some issues within the program.

lhx0416 avatar Dec 21 '23 12:12 lhx0416