Error Evaluate your docker container locally
See original GitHub issueI’m on the last step of setting everything in my docker container and test it out. But when I run
./test_locally_objectnav_rgbd.sh --docker-name objectnav_submission
I get the following error:
Traceback (most recent call last):
File "agent.py", line 41, in <module>
main()
File "agent.py", line 33, in main
challenge = habitat.Challenge(eval_remote=False)
File "/habitat-lab/habitat/core/challenge.py", line 16, in __init__
super().__init__(config_paths, eval_remote=eval_remote)
File "/habitat-lab/habitat/core/benchmark.py", line 38, in __init__
self._env = Env(config=config_env)
File "/habitat-lab/habitat/core/env.py", line 108, in __init__
id_sim=self._config.SIMULATOR.TYPE, config=self._config.SIMULATOR
File "/habitat-lab/habitat/sims/registration.py", line 19, in make_sim
return _sim(**kwargs)
File "/habitat-lab/habitat/sims/habitat_simulator/habitat_simulator.py", line 271, in __init__
super().__init__(self.sim_config)
File "<attrs generated init habitat_sim.simulator.Simulator>", line 11, in __init__
File "/opt/conda/envs/habitat/lib/python3.7/site-packages/habitat_sim/simulator.py", line 122, in __attrs_post_init__
self.__set_from_config(self.config)
File "/opt/conda/envs/habitat/lib/python3.7/site-packages/habitat_sim/simulator.py", line 260, in __set_from_config
self._config_backend(config)
File "/opt/conda/envs/habitat/lib/python3.7/site-packages/habitat_sim/simulator.py", line 204, in _config_backend
super().__init__(config.sim_cfg, config.metadata_mediator)
AssertionError: ESP_CHECK failed: Missing (at least) one of scene dataset attributes, stage attributes, or dataset scene attributes for scene 'habitat-challenge-data/data/scene_datasets/hm3d/val/00802-wcojb4TFT35/wcojb4TFT35.basis.glb'. Likely an invalid scene name.
I’m not sure how to solve this. Could anyone help to get the project running?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to Fix and Debug Docker Containers Like a Superhero
Container errors are tricky to diagnose, but some investigative magic works wonders. Read along to learn how to debug Docker containers.
Read more >How to Debug and Fix Common Docker Issues - DigitalOcean
In this troubleshooting guide aimed at people new to Docker, you'll troubleshoot problems when building Docker images, resolve naming collisions ...
Read more >Troubleshooting errors with Docker commands when using ...
Check that your local disk has enough remaining free space to store the Docker image you are pulling. You can also delete old...
Read more >Debug pipelines locally with Docker | Bitbucket Cloud Cloud KB
You can test your Bitbucket Pipelines build locally with Docker. This can be helpful to check whether your Docker image is suitable, or...
Read more >GitLab Docker images
Local location, Container location, Usage ... This error occurs when using Docker Toolbox with VirtualBox on Windows or Mac, and making use of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @hychen-naza ,
This is exactly the output I see on my end as well. The SPL is 0.0 because the agent is just taking random action.
If you want to get better numbers, you should test the ddppo agent, which we detail in point 8 here
I suspect that your
habitat-challenge-data/data/scene_datasets/hm3d
folder is symlinked to an incorrect path. Can you check ifdataDownload/scene_datasets/hm3d
folder exists in your machine? It is possible to create symlinks to non-existent files or folders which I believe is the case here (see this issue for more details).