Competition

The HULKs visit various competitions regularly, such as the RoboCup German Open or the international RoboCup. During these events, good organization and communication are key to success, a good workflow and not too much stress.

Meetings

During periods of high activity, a daily Standup meeting is usually held to inform each other about the current status and to coordinate the next steps.

This meeting (as well as all other important events) is documented in the Nextcloud calendar. You should have access to it, if not, ask somebody from the team. Ideally, you should also have it synced to your phone.

Roles

To distribute tasks and responsibilities, different roles are assigned to the team members. Usually, the roles are assigned during the pregame meeting, only the role of the Head-of-Robots (HoR) is assigned for the whole competition.

Note

During the game, only the Team Captain, Deployer, and Logführer are allowed to stand next to the Game Controller.

Team Captain

Is usually one of the Dev-Leads, is responsible for the organization of the meetings and the overall schedule. Decides which code is deployed.

Deployer

Merge-squashes different branches and deploys the code to the robots.

Good to know

The deployer should have the necessary hardware or setup for fast deployment. I.e. a fast laptop or a working remote build setup using the HULKs infrastructure. Strong nerves are also a plus, as well as the ability to cope with sudden merge conflicts. This however can be learned and trained.

Logführer

Is responsible for observing the game and noting down important events and things that need to be improved.

Head-of-Robots (HoR)

Is responsible for the robots and the hardware, as well as all interactions with URG. Keeps the Roboboboard up to date and selects the robots for the game, as well as their number.

Important

This role is extremely important, as the hardware status (especially in the later games) is crucial for the performance. Also, having a good relationship with URG can be beneficial for the team.

Game Schedule

For games, a strict schedule is created, which looks like this:

• 90 minutes prior: Pregrame Meeting
  Here, the roles are assigned and last steps and important tasks before the game are discussed.
• 45 minutes prior: Code at deployer
  All branches are ready to be merged and deployed. Sometimes parameter changes are still made after this stage.
• 30 minutes prior: Golden Goal
  A kick-off against an empty field is performed. This is the final test before the game.

Game Rules

Every team member should be familiar with the SPL rules.

Generally speaking, one goal of the SPL is to stay as close to the official soccer rules as possible, however, there are some key differences.

Note

It's a good idea to read the rules before the competition, even if you are not refereeing yourself.