Skip to content

Latest commit

 

History

History
40 lines (29 loc) · 2.95 KB

soccerwindow2-debugger.md

File metadata and controls

40 lines (29 loc) · 2.95 KB
Raw

SoccerWindow2

SoccerWindow2 is a powerful monitor that can be used as a debugger even with a running match.

Open a terminal and run:

$ soccerwindow2 &

In the main menu, click on Monitor > Launcher Dialog or press Ctrl+X:

Set the path to the start.sh script (located in the src folder) for both teams with the arguments --debug --debug-server-connect.

The teams will appear in the field and the server will be started. Go to View > View preference. In player selection, select the side you want to see. The debug information shows up immediately on the screen. If needed, you can choose on which player you want to focus.

Go to Debug > View Preference or press Ctrl+V. In the Object tab, navigate to the section Player Selection and choose one of the following items:

  • Auto left: visualize information of all players of the left team (left side of the field)
  • Left number X: visualize information of a specific player t of the left team (left side of field).
  • Left coach: visualize information of the left team coach (left side of field).
  • Auto right: visualize information of all players of the right team (right side of the field)
  • Right number X: visualize information of a specific player t of the right team (right side of field).
  • Right coach: visualize information of the right team coach (right side of field).

The image below showsa match paused at cycle 2810 with the debugger active for all players of the iBots2D team:

Bigger image here

  • The blue circles represent the last known positions of the opponents viewed by the player number 7 (player with the ball possession).
  • The green circles represent the last known positions of the teammates viewed by the player number 7 (player with the ball possession).
  • The orange circle with a X on its center represents the position where the player number 7 tried to pass the ball.
  • The tracing red line represents the probable ball path.
  • The black line from the player number 6 to the player number 7 indicates that the player 7 received a message sent by the player 6.
  • On the left top corner right below the Helios_base team name, information about players communications are written. In this example, the player 7 has three actions to be taken: move (BasicMove78), turn its neck to scan the field (NeckScan) and do not attack (AttOff).

All this information can be selected using the main menu at Debug > Debug Message.

To view the debug information of a match replay, you need to add the flag --log-dir DIRECTORY in the start.sh script of your team and also add the flags --debug --debug-server-connect (where DIRECTORY is the folder where you want to save the match logs) é o diretório onde você deseja salvar os logs). When the match is over, you only need to open the match RCG file and the log files using the File menu.