Add Multiple Cameras for Observation During Training

[alhasacademy96]

I think by trying to fix the bug of arenas not cycling properly during training, I realized that it would be very beneficial to be able to view the arena with all three camera perspectives, as overlays. The agent would not be susceptible to this change during training but would really help for debugging and potentially more insightful research as currently the camera is fixed at the perspective of the agent and this makes it harder to test for certain purposes and situations.

This setting could also be toggled on/off by the user via the yaml file or even the command line, such as:

class AAIOptions():
"""The options used by the animalai environment"""
arenaConfig: str = attr.ib() #The path of a valid arena config yaml file
useCamera: bool = attr.ib() #If true, then camera observations are returned
resolution: int = attr.ib() #The (square) resolution of camera observations (if useCamera is true)
grayscale: bool = attr.ib() #If the camera observations are grayscale or RGB
useRayCasts: bool = attr.ib() #If true, then raycast observations are returned
raysPerSide: int = attr.ib() #The number of rays on each side of the central ray (see observations doc)
rayMaxDegrees: int = attr.ib() #The number of degrees between the central ray and furthest ray in each direction.
enableMultiObs: bool = attr.ib() # if true, display all cameras on the UI for complete observation during training. False by default.

Open to discussion
[Mid-to-high priority]

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale. Please open a new issue for related bugs.

[github-actions]

This issue is stale because it has been open for 45 days with no activity.

[github-actions]

This issue is stale because it has been open for 45 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 120 days since being marked as stale. Please open a new issue for related bugs.

[github-actions]

This issue is stale because it has been open for 60 days with no activity.