-
Notifications
You must be signed in to change notification settings - Fork 728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
only single action supported #112
Comments
You need to define a network that can support multiple Actions, you can use CriticNetwork as an example. |
Well for example with td3 agent, I define Critic Network as follows, and the action spec defined with 2 actions, and I get such error. The only agent that worked was PPOAgent. _critic_net_input_specs = (tf_env.time_step_spec().observation,
|
Right, I see in ddpg that critic_network can only handle 1 observation. |
SAC only limited to 1 observation, it appears. |
So would need to write your own ActorNetwork and your own CriticNetwork classes that can handle multiple observations and multiple actions. |
ok I may try it. I'm not sure why the PPO Agent is written so that it can accept arbitrary number of actions/observations but the CriticNetwork is written differently. |
I am also struggling with the same issue, @sguada, if you could give me some pointers as to how to create custom ActorDistributionNetworks, I would really appreciate it! |
Getting this error...is this my mistake or do some agents only support a single action?
ValueError: Only a single action is supported by this network
In call to configurable 'CriticNetwork' (<function _NetworkMeta.new..capture_init at 0x00000203ED9DEEA0>)
In call to configurable 'train_eval' (<function train_eval at 0x00000203EE878BF8>)
The text was updated successfully, but these errors were encountered: