Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataloader problem #7

Open
vivek1527 opened this issue Oct 14, 2021 · 4 comments
Open

Dataloader problem #7

vivek1527 opened this issue Oct 14, 2021 · 4 comments

Comments

@vivek1527
Copy link

Screenshot from 2021-10-14 22-40-19
Hi,

I was trying to run the training from scratch and I am encountering this error. Do you know any particular reasons for this error.
I am using batch_size of 1 and GPU of 4GB

@VivekRamayanam19
Copy link

image

Hi, Can you please let me know the root cause of this error as I have tried many ways to resolve it but it reappears again and again

@qianqianwang68
Copy link
Owner

Sorry I don't recall this error. Can you check if the dataset is complete, and the path to your dataset is correct? Can you print the filename to see which sample caused the error?

@aruba01
Copy link

aruba01 commented Apr 11, 2022

Screenshot from 2021-10-14 22-40-19 Hi,

I was trying to run the training from scratch and I am encountering this error. Do you know any particular reasons for this error. I am using batch_size of 1 and GPU of 4GB

I encounter the same situation. In megadepth.py the function __getitem__, normally it will return a dict with 9 elements. But sometimes it will return None, which cause the error. The open-source code uses batchsize=6, and this datasets cannot happen the situation that 6 pairs return None at the same time, so it can't recall this error.

@qianqianwang68
Copy link
Owner

thank you so much @aruba01! That makes a lot of sense. I think an easy fix to this issue could be that whenever the batch is None, we reset it to be a dummy batch, and in the training loop, we simply skip dummy batches whenever we detect them. I think this will resolve this issue and I will try to push an update soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants