You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the new maintainer of Gym (I'm a PhD student at UMD, I have no formal affiliation with OpenAI). As you may know, Gym has been using MuJuCo for a long time in it's MuJuCo and Robotics environments, and was in the process of replacing these in full with Brax (originally PyBullet, but plans changed) due to MuJuCo's status as closed source and a host of massive maintenance issues with the MuJuCo environments and mujuco-py. Are you guys interested in Gym support, and if so would you be willing to reach out to me to set up a time to briefly chat about plans? My email is [email protected]
The text was updated successfully, but these errors were encountered:
Thanks for looking after this important resource for the community, and thanks for reaching out.
As a short term answer, you may be interested in the PR ikostrikov posted. As for supporting Gym long term, we should absolutely talk. We’ll reach out personally.
Once we’ve chatted and have a better idea of a plan, we’ll post it here.
@jkterry1 could you point to an announcement regarding mujoco_py no longer being maintained? There have been 3 commits since your last comment.
Finally, where can we learn more about your exchanges with the MuJoCo team and possible roadmap?
Hey,
I'm the new maintainer of Gym (I'm a PhD student at UMD, I have no formal affiliation with OpenAI). As you may know, Gym has been using MuJuCo for a long time in it's MuJuCo and Robotics environments, and was in the process of replacing these in full with Brax (originally PyBullet, but plans changed) due to MuJuCo's status as closed source and a host of massive maintenance issues with the MuJuCo environments and mujuco-py. Are you guys interested in Gym support, and if so would you be willing to reach out to me to set up a time to briefly chat about plans? My email is [email protected]
The text was updated successfully, but these errors were encountered: