Fei Xia

@jhpenger that's deprecated and using `env = SomeEnvClass(config = )` is the recommended way of creating environment. We didn't end up using `gym.make` because if we do that, we will...

@jhpenger It is because previous `depth_render` process is not killed properly (probably because the main process crashed) and is still hogging the socket port. You can see that by running...

@jhpenger If it requires rendering then GPU is needed. We use OpenGL rendering anyway so GPU is needed.

@jhpenger Depending on your resolution and quality settings, it will use one of the following from `gibson/assets`: `model_64.pth, model_128.pth, model_256.pth, model_512.pth, model_small_64.pth, model_small_128.pth, model_small_256.pth`.

@jhpenger You can set `mode: headless` and `display_ui: false` in the yaml config file.

GibsonEnv will use GPU even if in headless mode, headless means there is no display/X server needed, but GibsonEnv still uses OpenGL to render the frames and use pytorch to...

When running 256x256 resolution it uses about 1076MB + 163MB + 33MB GPU memory.

Yes, you can use the following code snippet to do this (`HuskyNavigateEnv` for example): ```python from gibson.envs.husky_env import HuskyNavigateEnv from gibson.utils.play import play import os config_file = os.path.join(os.path.dirname(os.path.realpath(__file__)), '..', 'configs',...

@HuYue-CS You would need to compile the source code with `./build.sh build_local`

@rainprob I observe similar issues when the `gibson/core/render/render_cuda_f.so` is not correctly compiled with nvcc. Can you check your `nvcc --version` is the same as `nvidia-smi` version?