You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And my agent is always moving forward and never turn left or right.
It seems that if the env.step function takes in an int type, the env_action in env.step function can produce correct results like [0,0,0],[0,0,1],[0,1,0],[1,0,0]. However when the env.step function takes in a numpy.int64 type, the env_action will turn into [0,0,0],[1,1,1],[2,2,2],[3,3,3], which forces the agent to keep moving forward.
My way of solving this bug is to write another gym.Wrapper to overwrite the step function:
Hi @caozhenxiang-kouji, thank you very much for the report; this is indeed a serious bug! The fix will be merged soon, and a new patch release should be available on PyPI in a few hours.
There seems to be a serious bug with your VizdoomEnv.
When I use the following code to build a doom environment:
And I try to use the following code to step forward for the environment:
And my agent is always moving forward and never turn left or right.
It seems that if the
env.step
function takes in an int type, theenv_action
inenv.step
function can produce correct results like [0,0,0],[0,0,1],[0,1,0],[1,0,0]. However when theenv.step
function takes in a numpy.int64 type, theenv_action
will turn into [0,0,0],[1,1,1],[2,2,2],[3,3,3], which forces the agent to keep moving forward.My way of solving this bug is to write another gym.Wrapper to overwrite the step function:
It doesn't seem to be an elegant way since every time you make a environment you should wrap it again. But it works fine.
Hopes you can fix this bug soon!
The text was updated successfully, but these errors were encountered: