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
Currently when pad_spaces is set, action spaces are padded out to be the same size across all agents. However, this is done by simply appending enough [Padding] Sleep() actions to the end of the action space.
This results in an action space that is the correct size, however the larger action space is not aligned across the smaller and larger agents. The problem is each action type (e.g. Analyse, Remove, etc) has e.g. 16 entries in the small agents and 48 entries in the large agents and the action space is sorted by Action type.
For example, when padding spaces, the first 4 small agents (Blue Agent 0-3) all have a Monitor action as action 16, however Blue Agent 4 has another Analyse action.
Instead of just extending the action space when applying padding, the appropriate number of padding should be inserted after each action type. This would ensure that the action numbers across padded environments have the same semantic meaning, e.g. Action 49 is Remove for all Agents when pad_spaces = True.
The text was updated successfully, but these errors were encountered:
Description
Currently when
pad_spaces
is set, action spaces are padded out to be the same size across all agents. However, this is done by simply appending enough[Padding] Sleep()
actions to the end of the action space.cage-challenge-4/CybORG/Agents/Wrappers/BlueFixedActionWrapper.py
Lines 316 to 317 in 313bf33
This results in an action space that is the correct size, however the larger action space is not aligned across the smaller and larger agents. The problem is each action type (e.g.
Analyse
,Remove
, etc) has e.g. 16 entries in the small agents and 48 entries in the large agents and the action space is sorted by Action type.For example, when padding spaces, the first 4 small agents (Blue Agent 0-3) all have a
Monitor
action as action 16, however Blue Agent 4 has anotherAnalyse
action.Steps to Reproduce
Expected behavior
Instead of just extending the action space when applying padding, the appropriate number of padding should be inserted after each action type. This would ensure that the action numbers across padded environments have the same semantic meaning, e.g. Action 49 is Remove for all Agents when
pad_spaces = True
.The text was updated successfully, but these errors were encountered: