(Example of) support for multi-valued Box actions? about tensorforce

[michaelschaarschmidt]

Hi,

this seems more like an issue with the interface to gym, we will get on it, thanks for bringing it up!

[AlexKuhnle]

Hey, so after trying to run this, I first realized that there is a dependency to Box2D, which needs to be installed, but after doing so, it still does not work for me because of an exception from within Box2D:

File ".../gym/envs/box2d/__init__.py", line 1, in <module>
    from gym.envs.box2d.lunar_lander import LunarLander
  File ".../gym/envs/box2d/lunar_lander.py", line 4, in <module>
    import Box2D
  File ".../Box2D/__init__.py", line 20, in <module>
    from .Box2D import *
  File ".../Box2D/Box2D.py", line 435, in <module>
    _Box2D.RAND_LIMIT_swigconstant(_Box2D)
AttributeError: module '_Box2D' has no attribute 'RAND_LIMIT_swigconstant'

Hence I'm not even getting as far as you do, unfortunately.

[AlexKuhnle]

Nevertheless, you're right, we are not properly translating the Gym action interface in this case (and probably others), so thanks for pointing this out. In fact, our current setup requires that actions are all single-value, i.e. 0-dimensional. I realize now that this might not always be the most convenient way, so we will change this to allow action shapes. We should be able to fix this over the weekend, I'm pretty sure.

[sof]

Great, thanks for looking into this right away. Evaluating TRPO+GAE with multiple continuous actions is particularly interesting.

(openai/gym#100 covers the state of Box2D ; I had to compile pybox2d from sources to get something working.)

[AlexKuhnle]

Update: It turns out that a proper integration of action arrays requires quite some adaptations in various classes. Unfortunately, these changes aren't quite finished yet, but I think will be in the next 2-3 days. It will then be possible to define an action shape, e.g. dict(continuous=False, shape=(2, 3), num_actions=5), and the Gym environment should hopefully work.

[AlexKuhnle]

This should work now. I haven't tried it on the BipedalWalker environment (because of the box2d problems), but let me know if it does not work. I will close this issue for now, assuming that it does. Feel free to reopen it, if it still is not working.

[sof]

Can confirm that BipedalWalker-v2's Box(4) actions are now handled just fine; thanks.