Closed piojanu closed 5 years ago
Thanks! Yes, a PR would be welcome.
Hi @piojanu, I've looked into this more and decided to extend the functionality a bit to also support isolating environments into processes. This helps avoid OpenGL errors on some system configurations. I've already incorporated those changes and pushed them to Github, so I'm closing your PR. By the way, the external process wrapper was only used once as it should since it was disabled in simulate.py. Thanks again for bringing this to my attention!
Hi!
Environment gets wrapped in
ExternalProcess
in its constructor intasks.py
(the last but one line):and in
simulate.py
again if we have multiple env processes defined:Fix: At first I wanted to remove wrapping from task constructor in
tasks.py
as it shouldn't be needed in case when we execute environments in sequence (BatchEnv
meet API requirements when it calls environments). However, it introduces some seg. faults. Strange and certainly not good, I have no idea why is that.So the other way is to simplify code in
simulate.py
to:Locally it works when I run training with debug config. @danijar should I create PR?