diode-devkit

diode-devkit copied to clipboard

How to handle invalid depths

1

From the paper, it seems that there are some invalid depths that were shown as black pixels in the depth map. I'm wondering if there is any way to handle...

awsaf49

thanks for your great work，but I have a question that how can I train with the dataset while there are many zeros in the depth map, in NYUv2 dataset, there...

erzhu222

name format for each file

3

Hi, Thanks for the work, in our research, we need to recover the extrinsic of the virtual parameter. I wonder how the name corresponding to the rotation of elevation angles...

pengwangucla

How to change the format depth.npy to depth.png

3

genera0

The readme mentions a test set: > We have released the train and validation splits of DIODE depth and DIODE normal, including RGB images, depth maps, depth validity masks and...

alexbarnett12

im_fname = osp.join(self.data_root, '{}.png'.format(im)) de_fname = osp.join(self.data_root, '{}_depth.npy'.format(im)) de_mask_fname = osp.join(self.data_root, '{}_depth_mask.npy'.format(im)) im = np.array(Image.open(osp.join(self.data_root, im_fname))) on the last line the im_fname is joined twice with self.data_root

jisonZ

Thanks for a great work and dataset, Can you please give details of normalization of the ground truth depth

Bayrambai

As #3 mentioned, depth around edges are noisy. Which is a common case in depth estimation and could have been solved. As is known, depth sensor return invalid value around...

emojilearning

Hello, nice work. I noticed that the depth map is stored in .npy format, I want to know what is the bit-depth of the raw depth images?

MEYE66

I believe that this `osp.join()` is a bug as `im_fname` already contains `self.data_root` prefix from [line 111](https://github.com/diode-dataset/diode-devkit/blob/master/diode.py#L111)

vejbomar