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

cuda is not compatible #4

Open
JDesperado opened this issue Sep 2, 2024 · 3 comments
Open

cuda is not compatible #4

JDesperado opened this issue Sep 2, 2024 · 3 comments

Comments

@JDesperado
Copy link

Hello, author. What version of cuda and Nvidia driver are you using? tensorflow1.14.0 officially supports cuda 10.0, torch1.11.0 officially supports cuda 10.2, but the 10.2 version does not support tesnsorflow1.14.0, and these issues also lead to driver incompatibility. May I ask how to solve this problem? I run this project under ubuntu18 system,I need your help.Looking forward to your reply,thank you!

@Tviskaron
Copy link

Hi, I’m not the author of this repo, but I’ll try to help.

First of all, the core network of SCRIMP is implemented in pytorch, so tensorflow is a redundant dependency. As a working example, I recommend the docker setup from the POGEMA benchmark. Here is the link: POGEMA Benchmark Dockerfile. If Docker isn’t an option, consider using cuda 11.6 with torch<2.0,>=1.9, which worked for our case.

@JDesperado
Copy link
Author

Hi, I’m not the author of this repo, but I’ll try to help.

First of all, the core network of SCRIMP is implemented in pytorch, so tensorflow is a redundant dependency. As a working example, I recommend the docker setup from the POGEMA benchmark. Here is the link: POGEMA Benchmark Dockerfile. If Docker isn’t an option, consider using cuda 11.6 with torch<2.0,>=1.9, which worked for our case.

Thank you for your reply. I have taken your suggestion, but now I have encountered a new problem. As shown in the picture, I hope to get your help!
2024-09-03 10-22-17 的屏幕截图

@Tviskaron
Copy link

I haven't encountered such an error. It seems that there might be an issue with the initialization of self.PROB, which should default to OBSTACLE_PROB = (0.0, 0.5)

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