Skip to content
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

Error in arena cycling in play mode #33

Open
kozzy97 opened this issue Mar 18, 2024 · 7 comments
Open

Error in arena cycling in play mode #33

kozzy97 opened this issue Mar 18, 2024 · 7 comments
Assignees
Labels
bug fix A fix to a known bug

Comments

@kozzy97
Copy link
Member

kozzy97 commented Mar 18, 2024

When playing the following config with multiple arenas, I occasionally get an error where the arena skips to the next one several times in quick succession, until settling on one of the arenas. Each arena works individually, and the skipping doesn't seem to be dependent on the particular arena.

Steps to reproduce the behavior:

  1. Run the following config in play mode using a jupyter notebook, the latest AAI release and the latest PyPI release.
!ArenaConfig
showNotification: true
arenas:
  0: !Arena
    pass_mark: 1
    t: 500
    items:
    - !Item
      name: Agent
      positions:
      - !Vector3 {x: 20, y: 0, z: 1}
      rotations: [0]
    - !Item
      name: GoodGoal
      positions:
      - !Vector3 {x: 20, y: 0, z: 20}
      sizes:
      - !Vector3 {x: 2, y: 2, z: 2}
  1: !Arena
    pass_mark: 1
    t: 500
    items:
    - !Item
      name: Agent
      positions:
      - !Vector3 {x: 20, y: 0, z: 1}
      rotations: [0]
    - !Item
      name: GoodGoalMulti
      positions:
      - !Vector3 {x: 20, y: 0, z: 20}
      sizes:
      - !Vector3 {x: 2, y: 2, z: 2}
  2: !Arena
    pass_mark: 1
    t: 500
    items:
    - !Item
      name: Agent
      positions:
      - !Vector3 {x: 20, y: 0, z: 1}
      rotations: [0]
    - !Item
      name: BadGoal
      positions:
      - !Vector3 {x: 20, y: 0, z: 20}
      sizes:
      - !Vector3 {x: 2, y: 2, z: 2}
  3: !Arena
    pass_mark: 1
    t: 500
    items:
    - !Item
      name: Agent
      positions:
      - !Vector3 {x: 20, y: 0, z: 1}
      rotations: [0]
    - !Item
      name: DeathZone
      positions:
      - !Vector3 {x: 20, y: 0, z: 20}
      sizes:
      - !Vector3 {x: 10, y: 2, z: 2}
      rotations: [0]

Expected behavior
Arenas should cycle through and enable the player to play each episode unless they skip it.

Screenshots
Contact me for a screen capture of the problem.

Desktop (please complete the following information):

  • OS: Windows 11
@alhasacademy96 alhasacademy96 self-assigned this Mar 21, 2024
@alhasacademy96 alhasacademy96 added the bug fix A fix to a known bug label Mar 21, 2024
@alhasacademy96
Copy link
Contributor

alhasacademy96 commented Mar 21, 2024

Hi, @kozzy97, is this for PLAY or TRAINING mode?
Have you tried on both or either to reproduce the bug?

@kozzy97
Copy link
Member Author

kozzy97 commented Mar 21, 2024

@alhasacademy96 as stated in the issue title, the issue is in play mode. I have only noticed the bug in play mode.

@alhasacademy96
Copy link
Contributor

alhasacademy96 commented Mar 26, 2024

Hi @kozzy97, i wasn't able to reproduce the bug. I'm also using the latest build and python package. It could be as simple as memory overload on your computer, causing a bottleneck during play. I tried play and train mode and works fine. I had no other applications open/running when I pressed play.

I've tested on WIN11 and macOS.

I will continue debugging to see if any of the parameter values are the culprit.

Copy link

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

@github-actions github-actions bot added the stale label May 10, 2024
@alhasacademy96
Copy link
Contributor

Being actively worked on now.

@github-actions github-actions bot removed the stale label May 13, 2024
Copy link

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

@github-actions github-actions bot added the stale label Jun 27, 2024
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix A fix to a known bug
Projects
None yet
Development

No branches or pull requests

2 participants