-
Notifications
You must be signed in to change notification settings - Fork 40
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
Getting "RuntimeError: Cannot find cuda device suitable for rendering cuda:0" when training an RL agent #142
Comments
Did you set |
I set |
Given the current information, it is very hard to understand what is causing the error. |
Hi, I meet the same error. Is there any possible solution / related issue to this issue? Thanks. |
I meet the same error. Any solution will be highly appreciated....🧎🧎🧎 |
what version of sapien are you using? And are you testing this via ManiSkill? |
Hi, I met with this error too. I am using sapien version of 2.2.2. Tried with NVIDIA A40 and A5000. I was testing it via ManiSkill, but the error occurs even if I run:
Any help would be highly appreciated. |
@srye2 can you install sapien==3.0.0b1 and run sapien info --all If it doesn't work please follow https://maniskill.readthedocs.io/en/latest/user_guide/getting_started/installation.html#troubleshooting, |
Upgrading worked, thank you so much! |
System:
Describe the bug
I have used sapien to render camera pictures as observations in a gym environment. However, the following error occured during training.
The agent had already interacted with the gym environment before the above error occured, and the memory for the corresponding gpu is sufficient. The agent model is on cuda:2 device. I want to know why the error could occur and how to fix it.
Expected behavior
Successfully obtain a renderer and set it to the sapien engine.
Additional context
Also in the beginning I run the code without
device="cuda:0"
, and another error occuredI guess it was because the renderer and the agent used the same gpu, and this is the reason I chose to specify the device of the renderer.
The text was updated successfully, but these errors were encountered: