-
Notifications
You must be signed in to change notification settings - Fork 813
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
OSx #36
Comments
I use Mujoco 1.3.1 frequently under OSX. Can you be more specific about how it doesn't work? |
Ah. Perhaps nobody at OpenAI has an NVMe disk. Supporting 1.5 is likely to be a big project, since it will change the semantics of all the mujoco envs and make new results incompatible with previous results. I wonder if there's a workaround by linking |
OK will try |
Unable to workaround this and I am unable to run the Roboschool also |
Using OSX 10.12.4, I got "ERROR: Could not open disk". This source states: "The license manager in MuJoCo Pro 1.40 and earlier does not work with newer Macs that have NVMe disks. This was fixed in MuJoCo 1.50." |
yes thank you I was able to solve it by updating the models |
What do you mean by "updating the models"? |
The issue was I had trouble running the OpenAI models in mujoco for which Emo replied saying I have to update mujoco models to 1.5 version , the current OpenAI models only support Mujoco 1.3 version |
I also had a hard time using mujoco-py because my laptop is MacBook Pro 2016. Hope to see someone coming up a fix. |
So there is no workaround except waiting for openai to support 1.5? |
Aha they have now released support for 1.5 version but some problems in installing the same |
This is resolved with 1.50.1.0 -- Python 3.6 support is tracked in #52. |
@tlbtlbtlb Trevor, your suggestion was worth a try... I tried copying both ~/.mujoco and the working dir to a non-NVMe USB drive... unfortunately mujoco gives the same "Could not open disk" error. A little bit cleaner way to do the dtruss is to cd into mjpro131/bin and do
I don't know how it figures out there is an NVME drive. Looks like it is accessing paths like /System and /etc which are hard to copy over. I think I'm not up for setting up an entire USB boot disk for my mac this evening... :-) And after all that, maybe mujoco wouldn't like a USB drive either. I have just tried asking Mujoco to fix the NVMe disk problem in a patch from 131 to 132... then one could just link to that and OpenAI wouldn't have to change anything. http://www.mujoco.org/forum/index.php?threads/error-could-not-open-disk.3441/ P.S. Here is the dtruss output... by the time it opens MUJOCO_LOG.TXT below, I think the error has already occurred, because it also writes "ERROR: Could not open disk" to that file.
|
Only Mujoco 1.5 works in OSx so could you guys release support for 1.5 instead of 1.31 version of Mujoco
The text was updated successfully, but these errors were encountered: