Comments (14)
I use Mujoco 1.3.1 frequently under OSX. Can you be more specific about how it doesn't work?
from mujoco-py.
Ok checkout this screenshot of the chat with Emo, 1.31 doesn't work with OSx so asking for help
from mujoco-py.
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 $HOME/.mujoco
to a temporary disk or something. My superficial examination of `dtruss python -c 'import gym; env=gym.make("Hopper-v1")' doesn't show any obviously non-portable things it does in order to read the key file.
from mujoco-py.
OK will try
from mujoco-py.
Unable to workaround this and I am unable to run the Roboschool also
from mujoco-py.
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."
from mujoco-py.
yes thank you I was able to solve it by updating the models
from mujoco-py.
What do you mean by "updating the models"?
from mujoco-py.
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
from mujoco-py.
I also had a hard time using mujoco-py because my laptop is MacBook Pro 2016. Hope to see someone coming up a fix.
from mujoco-py.
So there is no workaround except waiting for openai to support 1.5?
from mujoco-py.
Aha they have now released support for 1.5 version but some problems in installing the same
from mujoco-py.
This is resolved with 1.50.1.0 -- Python 3.6 support is tracked in #52.
from mujoco-py.
@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
sudo dtruss ./simulate
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.
$ sudo dtruss ./simulate
dtrace: system integrity protection is on, some features will not be available
SYSCALL(args) = return
MuJoCo Pro library version 1.31
ERROR: Could not open disk
Press Enter to exit ...open("/dev/dtracehelper\0", 0x2, 0x7FFF5F61E6B0) = 3 0
ioctl(0x3, 0x80086804, 0x7FFF5F61E638) = 0 0
close(0x3) = 0 0
thread_selfid(0x3, 0x80086804, 0x7FFF5F61E638) = 894851 0
bsdthread_register(0x7FFFA8AC8080, 0x7FFFA8AC8070, 0x2000) = 1073741919 0
mprotect(0x1040CD000, 0x88, 0x1) = 0 0
mprotect(0x1042AA000, 0x1000, 0x0) = 0 0
mprotect(0x1042C0000, 0x1000, 0x0) = 0 0
mprotect(0x1042C1000, 0x1000, 0x0) = 0 0
mprotect(0x1042D7000, 0x1000, 0x0) = 0 0
mprotect(0x1040CF000, 0x1000, 0x1) = 0 0
mprotect(0x1040CD000, 0x88, 0x3) = 0 0
mprotect(0x1040CD000, 0x88, 0x1) = 0 0
ulock_wake(0x1, 0x7FFF5F61C54C, 0x0) = -1 Err#2
issetugid(0x1, 0x7FFF5F61C54C, 0x0) = 0 0
getpid(0x1, 0x7FFF5F61C54C, 0x0) = 88439 0
stat64("/AppleInternal/XBS/.isChrooted\0", 0x7FFF5F61C408, 0x0) = -1 Err#2
stat64("/AppleInternal\0", 0x7FFF5F61C4A0, 0x0) = -1 Err#2
csops(0x15977, 0x7, 0x7FFF5F61BF30) = -1 Err#22
dtrace: error on enabled probe ID 2158 (ID 561: syscall::sysctl:return): invalid kernel access in action #10 at DIF offset 40
ulock_wake(0x1, 0x7FFF5F61C4B0, 0x0) = -1 Err#2
csops(0x15977, 0x7, 0x7FFF5F61B810) = -1 Err#22
getuid(0x15977, 0x7, 0x7FFF5F61B810) = 0 0
getuid(0x15977, 0x7, 0x7FFF5F61B810) = 0 0
stat64("/System/Library/PrivateFrameworks/Heimdal.framework/Heimdal\0", 0x7FFF5F61B918, 0x7FFF5F61B810) = 0 0
stat64("/System/Library/Frameworks/GSS.framework/GSS\0", 0x7FFF5F61B918, 0x7FFF5F61B810) = 0 0
mprotect(0x104288000, 0x88, 0x1) = 0 0
mprotect(0x1042D8000, 0x1000, 0x0) = 0 0
mprotect(0x1042EE000, 0x1000, 0x0) = 0 0
mprotect(0x1042EF000, 0x1000, 0x0) = 0 0
mprotect(0x104305000, 0x1000, 0x0) = 0 0
mprotect(0x1040CF000, 0x1000, 0x3) = 0 0
mprotect(0x1040CF000, 0x1000, 0x1) = 0 0
mprotect(0x104288000, 0x88, 0x3) = 0 0
mprotect(0x104288000, 0x88, 0x1) = 0 0
access("/System/Library/taggedstringsoff\0", 0x4, 0x1) = -1 Err#2
getrlimit(0x1008, 0x7FFF5F61F5B8, 0x1) = 0 0
fstat64(0x1, 0x7FFF5F61F5D8, 0x1) = 0 0
ioctl(0x1, 0x4004667A, 0x7FFF5F61F61C) = 0 0
dtrace: error on enabled probe ID 2133 (ID 951: syscall::write_nocancel:return): invalid kernel access in action #12 at DIF offset 92
dtrace: error on enabled probe ID 2133 (ID 951: syscall::write_nocancel:return): invalid kernel access in action #12 at DIF offset 92
access("/etc/localtime\0", 0x4, 0x1) = 0 0
open_nocancel("/etc/localtime\0", 0x0, 0x0) = 3 0
fstat64(0x3, 0x7FFF5F61C580, 0x0) = 0 0
dtrace: error on enabled probe ID 2135 (ID 949: syscall::read_nocancel:return): invalid kernel access in action #12 at DIF offset 92
close_nocancel(0x3) = 0 0
shm_open(0x7FFFA8ABBDE7, 0x0, 0x0) = 3 0
mmap(0x0, 0x1000, 0x1, 0x1, 0x3, 0x0) = 0x10428A000 0
close_nocancel(0x3) = 0 0
open_nocancel("mjkey.txt\0", 0x0, 0x1B6) = 3 0
fstat64(0x3, 0x7FFF5F61F3A8, 0x1B6) = 0 0
dtrace: error on enabled probe ID 2135 (ID 949: syscall::read_nocancel:return): invalid kernel access in action #12 at DIF offset 92
dtrace: error on enabled probe ID 2135 (ID 949: syscall::read_nocancel:return): invalid kernel access in action #12 at DIF offset 92
close_nocancel(0x3) = 0 0
open_nocancel("MUJOCO_LOG.TXT\0", 0x20A, 0x1B6) = 3 0
lseek(0x3, 0x0, 0x2) = 767 0
fstat64(0x3, 0x7FFF5F61F418, 0x2) = 0 0
dtrace: error on enabled probe ID 2133 (ID 951: syscall::write_nocancel:return): invalid kernel access in action #12 at DIF offset 92
close_nocancel(0x3) = 0 0
dtrace: error on enabled probe ID 2133 (ID 951: syscall::write_nocancel:return): invalid kernel access in action #12 at DIF offset 92
dtrace: error on enabled probe ID 2133 (ID 951: syscall::write_nocancel:return): invalid kernel access in action #12 at DIF offset 92
fstat64(0x0, 0x7FFF5F61F618, 0x1) = 0 0
ioctl(0x0, 0x4004667A, 0x7FFF5F61F65C) = 0 0
dtrace: error on enabled probe ID 2133 (ID 951: syscall::write_nocancel:return): invalid kernel access in action #12 at DIF offset 92
from mujoco-py.
Related Issues (20)
- Installing mujoco someplace other than the /home directory
- Mujoco can't find files when placed in a non-home directory: /opt/mujoco-py/mujoco_py/cymj.c:798:10: fatal error: mjmodel.h: No such file or directory
- after installing mujoco_py I get this cython error HOT 4
- Cython.Compiler.Errors.CompileError: D:\Anaconda\Anaconda3\envs\py310torch2.1\lib\site-packages\mujoco_py-2.0.2.1-py3.10.egg\mujoco_py\cymj.pyx HOT 3
- mujoco-py is not available now? HOT 3
- failure to enable energy computation
- Fail to import mujoco_py HOT 1
- Could not build wheels for mujoco-py HOT 3
- Segmentation fault (core dumped) from using PID controller plugin and keyframes simultaneously
- Mujoco rendering produces black image for every MjModel instance called after the first HOT 6
- Cannot change site position programmatically when pos is set to zero in XML
- unable to define a good camera perspective
- I am unable to import mujoco_py HOT 2
- Discrepancies in Mass Matrix Values Between Pinocchio and MuJoCo HOT 1
- gcc: error: unrecognized command line option ‘-R’ HOT 1
- Issue when importing mujoco_py (crypt.h: No such file or directory)
- when run "python setup.up build", and "import mujoco-py", some mistakes happen on my win10 computer.
- Excessive Duplicate Vertices in Imported Mesh in MuJoCo
- Mujoco lglewegl missing, command '/usr/bin/gcc' failed with exit code 1 HOT 1
- raise error.MujocoDependencyError('Found your MuJoCo license key but not binaries. Please put your binaries into ~/.mujoco/mjpro131 or set MUJOCO_PY_MJPRO_PATH. Follow the instructions on https://github.com/openai/mujoco-py for setup.')
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mujoco-py.