-
Notifications
You must be signed in to change notification settings - Fork 21
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
Problems about the competition startkit #9
Comments
It looks like
Also, the script name is |
Hi
|
|
Meanwhile, it will be nice to try fresh by running |
Thanks, the following is all of the logs, it prints the following information, then it is blocked. : root@94d903ce99a4:/home/user/competition# xvfb-run -s "-ac -screen 0 1280x1024x24" ./new/evaluation_locally.sh --verbose Data directory is data Traceback (most recent call last): Usage: Try 'ps --help <simple|list|output|threads|misc|all>' For more details see ps(1). Data directory is data Traceback (most recent call last): |
I suggest that your team should give an example on how to use the startkit (You can use PPO, DQN or other baselines). I think it's not very clear. You can also claim the code format of every block. @skbly7 |
I don't know how to fix that bug@skbly7 |
When I use the docker_evaluation_locally.sh, there is still having bug. Here is the error log: Note: Gathering environment variables from environ.sh |
It can run in a docker envinment when I use
xvfb-run -s "-ac -screen 0 1280x1024x24" python train.py
But I get the following error when I use the script in competiton startkit repo, I use the bash
xvfb-run -s "-ac -screen 0 1280x1024x24" ./utility/evaluate_locally.sh
, it will get the following error:Traceback (most recent call last):
File "/root/anaconda3/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/root/anaconda3/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
File "/root/anaconda3/lib/python3.6/site-packages/minerl/env/malmo.py", line 896, in keep_alive_pyro
InstanceManager.add_keep_alive(os.getpid(), callback)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 275, in getattr
self._pyroGetMetadata()
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 615, in _pyroGetMetadata
self.__pyroCreateConnection()
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 588, in __pyroCreateConnection
uri = _resolve(self._pyroUri, self._pyroHmacKey)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 1911, in _resolve
return nameserver.lookup(uri.object)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 185, in call
return self.__send(self.__name, args, kwargs)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 476, in _pyroInvoke
raise data # if you see this in your traceback, you should probably inspect the remote traceback as well
Pyro4.errors.NamingError: unknown name: minerl.instance_manager
Traceback (most recent call last):
File "run.py", line 2, in
import train
File "/home/user/competition/train.py", line 14, in
from envs import diamond_env_creator
File "/home/user/competition/envs.py", line 10, in
from hack import minerl
File "/home/user/competition/hack.py", line 74, in
minerl.env.malmo.InstanceManager.get_instance = get_instance
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 291, in setattr
self._pyroGetMetadata()
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 615, in _pyroGetMetadata
self.__pyroCreateConnection()
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 588, in __pyroCreateConnection
uri = _resolve(self._pyroUri, self._pyroHmacKey)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 1911, in _resolve
return nameserver.lookup(uri.object)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 185, in call
return self.__send(self.__name, args, kwargs)
File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 476, in _pyroInvoke
raise data # if you see this in your traceback, you should probably inspect the remote traceback as well
Pyro4.errors.NamingError: unknown name: minerl.instance_manager
+--- This exception occured remotely (Pyro) - Remote traceback:
| Traceback (most recent call last):
| File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/naming.py", line 91, in lookup
| uri, metadata = self.storage[name]
| KeyError: 'minerl.instance_manager'
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/core.py", line 1421, in handleRequest
| data = method(*vargs, **kwargs) # this is the actual method call to the Pyro object
| File "/root/anaconda3/lib/python3.6/site-packages/Pyro4/naming.py", line 98, in lookup
| raise NamingError("unknown name: " + name)
| Pyro4.errors.NamingError: unknown name: minerl.instance_manager
The text was updated successfully, but these errors were encountered: