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
This format only allows for a single, unnamed outcome, and while you can specify multiple outcome types in configs, there is no way to name them. We would like to support multiple named outcomes, with the parameter and outcome names being indicated by the config. For example, we could specify named outcomes in a config like so:
Currently tell messages have the following format:
This format only allows for a single, unnamed outcome, and while you can specify multiple outcome types in configs, there is no way to name them. We would like to support multiple named outcomes, with the parameter and outcome names being indicated by the config. For example, we could specify named outcomes in a config like so:
And specify named outcomes in tell messages like so:
(The server should check whether outcome is a dictionary or a list/scalar to determine if it should use the new or old functionality.)
This would require changes to
server.configure
,server.tell
, andserver._config_to_tensor
.The text was updated successfully, but these errors were encountered: