AutoRef implementation: Difference between revisions
20204919@TUE (talk | contribs) |
20204919@TUE (talk | contribs) |
||
| Line 21: | Line 21: | ||
===Motivation=== | ===Motivation=== | ||
This objective was chosen due to several reasons: | |||
- Past projects analysis has shown that this functionality has never been designed before | |||
- Stakeholder interviews (the MSL referees) have led to the conclusion that this kind of rules are hard to control for a human being | |||
- Proof of concept for the developed functional specification was desirable | |||
- Learning goals of the team members correspond to the technical solutions necessary for the functionality development | |||
===Scope of work=== | ===Scope of work=== | ||
Revision as of 14:19, 31 March 2021
The implementation for the AutoRef autonomous referee for RoboCup Middle Size League (MSL) robot soccer is the proposed design of the AutoRef system.
In 2021 contributions by MSD 2020 focused on detecting ball-to-player distance violations.
Introduction
Objective statement
The main objective of the implementation part of the project was to detect violations of the rules related to the distance between the ball and players during the following game states:
- Free kick
- Kick-off
- Corner kick
- Goal kick
- Throw-in
- Dropped-ball
- Penalty kick
These rules are described in Laws number 8, 10, 13, 14, and 15 of the MSL Rulebook.
Motivation
This objective was chosen due to several reasons:
- Past projects analysis has shown that this functionality has never been designed before
- Stakeholder interviews (the MSL referees) have led to the conclusion that this kind of rules are hard to control for a human being
- Proof of concept for the developed functional specification was desirable
- Learning goals of the team members correspond to the technical solutions necessary for the functionality development