-
Notifications
You must be signed in to change notification settings - Fork 674
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
[Feature]: Video logging with Gymnasium #4510
Comments
Hi @sdpkjc thanks so much for filing this, I have now created a feature request for our engineering team to support the integration of Gymnasium and we will reach out to you once this is implemented. I have also linked this ticket to the PR that will fix the compatibility issues with gym 0.26.0 and I will keep you posted once this is merged. Thanks once again, and have a great week! |
Hi, I'm one of the maintainers of Gymnasium. Have there been any updates on the progress of this? |
Hi @jkterry1 thank you for following up on this, I've asked internally the Growth team about this integration and they've confirmed it's under consideration for Q1. I hope this helps, and I will keep you posted here on any further progress updates. |
Hi @sdpkjc just an update on this, that a PR was just merged to support Hey @jkterry1 regarding I will close this ticket now as the original issue seems resolved, but please feel free to reopen this if you had any issues or further questions about it. |
Description
Gymnasium is a follow-up maintenance repository for the gym package.
Currently Wandb does not support video logging with Gymnasium. Gym0.26 needs to be supported in order to support Gymnasium. I see that there is a PR in progress to support Gym0.26. #4363
Suggested Solution
We may need to support both Gym and Gymnasium. After #4363 is completed, it seems that both Gym and gyms can continue to use Wandb log video. Because Gymnasium temporarily depends on Gym0.26.
We may need to support Gymnasium separately so that it can be updated later.
Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: