You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I compute the rmse in the same way for the method "NeWCRFs", and got the right rmse of 0.333. However, when I tried zoedepth, I got the rmse of 0.375. As you can see in my annotation, I have tried to crop the black border of RGB the same as Zoedepth, changed the mode of 'inter' into 'eval', and also tried to save the npy file to avoid round-off error, but none of them work. An interesting thing is that when I directly run the evaluate.py by the author, I got the right rmse of 0.27.
Directly utilize "mde_array = zoe.infer_pil(rgb_pil, output_type="numpy")" is so convenient to save depth map, but what makes the metrics down?
The text was updated successfully, but these errors were encountered:
suzdl
changed the title
save imgs first and validate metrics on NYUv2, got rmse of 0.375, but rmse in paper is 0.27
save depth maps first, and then validate metrics on NYUv2, got rmse of 0.375, but rmse in paper is 0.27
Mar 28, 2024
I load the model "ZoeD_M12_N.pt", and run the general following code with little modification
, to save metrics depth map first.
in this way, I will get the output metric depth in mm, and I test it by the following code, got bad rmse of 0.375 by the following code:
I compute the rmse in the same way for the method "NeWCRFs", and got the right rmse of 0.333. However, when I tried zoedepth, I got the rmse of 0.375. As you can see in my annotation, I have tried to crop the black border of RGB the same as Zoedepth, changed the mode of 'inter' into 'eval', and also tried to save the npy file to avoid round-off error, but none of them work. An interesting thing is that when I directly run the evaluate.py by the author, I got the right rmse of 0.27.
Directly utilize "mde_array = zoe.infer_pil(rgb_pil, output_type="numpy")" is so convenient to save depth map, but what makes the metrics down?
The text was updated successfully, but these errors were encountered: