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 tried depth anything v2 on vKitti2 in two different modes:
1- the general mode which outputs relative depth data
2- metric depth estimation fine-tuned on vKitti2
I got very strange depth for sky region for the "metric" one. Please see the attached image. Why is it the case? The network is fine-tuned on vKitti2, right? Then it should give us very good estimation for this dataset; however, the sky is quite off.
Q1- Have you excluded the sky region (or anything further than 80m) during fine-tuning?
Q2- Is it also the case for Depth AnyThing v1?
The text was updated successfully, but these errors were encountered:
I want to know whether the fine-tuning network you mentioned means retraining under the weights loaded in the demo, or freezing some network parameters
Hi @hgolestaniii, our metric depth model trained on VKITTI 2 can only estimate depth ranging from 0m to 80m, since we clip large depth values (> 80m) during training.
Hi,
I tried depth anything v2 on vKitti2 in two different modes:
1- the general mode which outputs relative depth data
2- metric depth estimation fine-tuned on vKitti2
I got very strange depth for sky region for the "metric" one. Please see the attached image. Why is it the case? The network is fine-tuned on vKitti2, right? Then it should give us very good estimation for this dataset; however, the sky is quite off.
Q1- Have you excluded the sky region (or anything further than 80m) during fine-tuning?
Q2- Is it also the case for Depth AnyThing v1?
The text was updated successfully, but these errors were encountered: