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

Performance of the demo varies dramatically with the CUDA device #8

Closed
Junyi42 opened this issue Apr 6, 2023 · 2 comments
Closed

Comments

@Junyi42
Copy link

Junyi42 commented Apr 6, 2023

Hi, and thank you for your fantastic work! I have encountered a minor issue that I'd like to bring to your attention. I found that when I change the line model.to(cfg.train.device) to model.to("cuda:1") (or any other device) in the demo.ipynb, there is a significant difference in the generated segmentation map compared to the original (please see the attached image below).

output

The original code runs perfectly fine and produces results consistent with those in the paper. However, when I make this modification, I don't encounter any specific warnings or errors, so I'm uncertain where the issue lies (I suspect that perhaps some modules are not loaded correctly). I'd greatly appreciate your help with this issue. Thank you!

@Junyi42 Junyi42 changed the title Performance of the Demo Varies Dramatically with the CUDA Device Performance of the demo varies dramatically with the CUDA device Apr 6, 2023
@xvjiarui
Copy link
Contributor

Hi @Junyi42
Sorry for the late reply. How about using CUDA_VISIBLE_DEVICES?

@Junyi42
Copy link
Author

Junyi42 commented Apr 21, 2023

Thanks for the reply, and that solves this issue! btw, I think the issue may lie in the loading of the decoder since I found the extracted features from the backbone unchanged in this case.

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