Created methods that return the size of different features to the user #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While reading the code to understand what the observation vector is composed of, I found the opportunity to implement methods inside the StarCraft2Env class to expose how much of the observation is composed of agent movement features, enemy features, ally features and agent features. This may help other users interpret or separate the observation vector in its smaller components, in case they deem it necessary.
The methods I created also removed redundant code in situations where the size of the observation vector was calculated in different parts of the code (e.g. inside
get_obs()
andget_obs_size()
).Lastly, I took the opportunity to briefly describe in the docstring what the observation vector is composed of.