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

The problem of image shape #25

Open
xiewende opened this issue Dec 14, 2021 · 4 comments
Open

The problem of image shape #25

xiewende opened this issue Dec 14, 2021 · 4 comments

Comments

@xiewende
Copy link

when use "python3 train.py --config configs/voc_cac_deeplabv3+_resnet50_1over8_datalist0.json" with two GPUS to run , i find that one GPUS imput image size is (1,3,335,500) while another is (1,3,366,500) . in this case ,i can run to end.
but ,when i run with only one GPU,the problem of diffrent size is occr.
how is go ???

@X-Lai
Copy link
Collaborator

X-Lai commented Dec 24, 2021

Thanks for your interest in our work. I don't really understand your problem. Can you clarify your question more clearly?

@xiewende
Copy link
Author

run with only one Gpu , a problem of diffrent input image size
run with two Gpus , one GPUS input image size = (1,3,335,500) while another GPUS input image size = (1,3,366,500),but in this case,i can run
what happen? why the input image size is different

@X-Lai
Copy link
Collaborator

X-Lai commented Dec 24, 2021

Do you meet the problem only in validation? If yes, I recommend you to adjust the batch_size in val_loader to be the same as n_gpu. Since during validation, the size of images are different.

@xiewende
Copy link
Author

xiewende commented Jan 4, 2022

ok!thank to your answer!however,how i train with my own datasets,and what mean under dataloaders TXT file ,is there any py_file to generate these txt_file?

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

2 participants