MiDaS icon indicating copy to clipboard operation
MiDaS copied to clipboard

Code for robust monocular depth estimation described in "Ranftl et. al., Towards Robust Monocular Depth Estimation: Mixing Datasets for Zero-shot Cross-dataset Transfer, TPAMI 2022"

Results 160 MiDaS issues
Sort by recently updated
recently updated
newest added

I have a few doubts, if you could kindly clear them 1. Could you clarify the number of layers in the depth map produced by the MiDaS model and how...

If a copy is made of a Midas model loaded through torch hub, the forward call on the copy will throw an error related to missing keys in parts of...

1. Add a `pyproject.toml` that allows for `pip install` 2. Restructure code so that the source code lives inside `src` 3. Replace relative imports with absolute (`from .backbones` -> `from...

I'm using a Raspberry Pi 5 with the latest Raspberry Pi OS Lite (headless). I have a simple script taken from the Google Collab example: https://colab.research.google.com/github/pytorch/pytorch.github.io/blob/master/assets/hub/intelisl_midas_v2.ipynb ``` #!/usr/bin/env python3 import...

Thank you for your work. I am trying to quantize the MiDaS DPT_Large model into INT 8 quantization. I have searched through github and googled, and asked bing if there...

Hi, I want to retrain the model using ConvNeXtV2 as the backbone, but I don't find the loss func for this project. can you share the loss function? I read...

When will MiDaS 3.1 be supported for conversion into ONNX?

Hi, I ran the code today and found that it reported the following error, the following error was reported, in utils.py line 195 in the code out = cv2.applyColorMap(np.uint8(out), cv2.COLORMAP_INFERNO)...

The error occurs when the F.interpolate function was called with new_height and new_width as arguments for the size parameter. These variables were of type numpy.intc, while F.interpolate expected arguments of...

Hi there, I tried to load the pretrained model but met an error "Unexpected key(s) in state_dict: "pretrained.model.blocks.0.attn.relative_position_index", ....". I found that this error only happened with timm=0.9.7 and would...