AutoRef - Autonomous Referee System

From Control Systems Technology Group
Jump to navigation Jump to search

Note: This page is being actively modified.

AutoRef logo

The AutoRef system is a proposed autonomous referee for RoboCop Middle Size League (MSL) robot soccer under development at Eindhoven University of Technology (TU/e). It is intended to accomplish all refereeing duties of human referees in MSL.

Development towards system architecture and implementation began in 2016 by TU/e PDEng trainees in the 2015–2017 cohort of the Mechatronic Systems Design (MSD) program as their Block II in-house project. Since then, each MSD cohort team has contributed to AutoRef's continuation in their respective Block II in-house projects. In TU/e's 2019–2020 academic year, a team of students in the Honors program High Tech Systems realized the control of drones as part of AutoRef's implementation, with continued efforts in drone control by these students leading to the Firefly-project.

Team contributions to AutoRef from 2016 through 2020 saw multiple iterations of its project definition, consequently leading to relatively poor overall project progress. Earlier MSD cohorts emphasized a fully autonomous referee, while later years scoped the project towards an assistive, supplementary system for human referees. In 2021, to prevent further repetitive efforts in the design of AutoRef, the 2020–2022 MSD cohort project team (AutoRef PDEng MSD 2020 or simply MSD 2020) was specifically tasked with ensuring continuity for future work.

As a result of MSD 2020's team contribution, the AutoRef's system architecture and implementation pages describe the current state of the project "as-is" without the voice of any specific team's contribution. Team contributions prior to MSD 2020 (i.e., MSD 2015–2019 and Honors 2019) are generally provided as isolated technical reports which provide details of their respective work but do not meet the concern for continuity of AutoRef. Contributions from MSD 2020 onwards are integrated into the AutoRef's pages for continuity, with each team's respective contribution page providing summaries of what was done to help supervisors understand and evaluate a team's work. An archive initiated by MSD 2020 provides an overview of all team contributions (past and present) https://teams.microsoft.com/l/file/EA8BF37F-3469-4424-9010-BEADD8E96EE9?tenantId=cc7df247-60ce-4a0f-9d75-704cf60efc64&fileType=xlsx&objectUrl=https%3A%2F%2Ftuenl.sharepoint.com%2Fsites%2FMCS_Drone_Referee_project_Team%2FShared%20Documents%2FGeneral%2FAutoRef%20Project%202020%20Final%20Deliverables%2FDocumentation%20%26%20Archive%2FArchive%20of%20past%20year's%20work.xlsx&baseUrl=https%3A%2F%2Ftuenl.sharepoint.com%2Fsites%2FMCS_Drone_Referee_project_Team&serviceName=teams&threadId=19:67b92555afdd4fdbbc40f984fb35696c@thread.tacv2&groupId=1efe2c69-ea31-43f1-9b96-c1c8cfa600e6.

Background

This section's tone or style may not reflect the encyclopedic tone as used in articles such as those on Wikipedia. See Wikipedia's guide to writing better articles for suggestions.

RoboCup

RoboCup is an international initiative to promote and advance research in robotics and artificial intelligence. Founded in 1997, its main goal is to ‘develop a team of fully autonomous humanoid robot soccer players that is able to win against the winner of the most recent World Cup, complying with the official rules of FIFA, by the middle of the 21st century’.

Middle Size League (MSL)

In RoboCup's Middle Size League (MSL), two teams of five autonomous robots play a soccer match on an artificial field. These robots are able to drive around while using several on-board camera's to position themselves on the field. Moreover, they can determine the position of the ball, opponents and team mates. Through radio signals they can communicate with each other and decide upon a strategy. With a ball-handling system the ball can be captured and controlled and a shooting mechanism is able to shoot a ball over the ground or through the air.

As discussed in this tutorial, a standard RoboCup field measures 18 by 12 meters. During a match, there are two teams consisting of five robots on this field, driving around with velocities up to 5 m/s and possibly even higher. These robots are all competing for the same thing: scoring goals. This means that getting possession of the ball is a primary goal. When several robots are competing for the ball, collisions, pushing and scrummages are nearly inevitable.

Human refereeing

To ensure each MSL match is played fairly, a human referee observes events on the field from the sideline. This human referee is supported by an auxiliary referee who stands on the opposite side, next to the field. Both referees can stop the game in response to a committed foul, a scored goal, a ball out of bounds, and other game events as specified in the MSL rules. The MSL rules are based on the official FIFA rules, but adapted to robot soccer rules were necessary. However, the large set of rules and the interpretation thereof can often lead to situations where a referee might decide to continue the game, while another might decide to interrupt. This can and will often lead to frustrations in the aggrieved team. Moreover, a decision made by a referee can affect the outcome of a game and even an entire championship.

RoboCup 2016 Leipzig: MSL final match

The outcome-affecting nature of refereeing was evident in the final match of the RoboCup world championship 2016 in Leipzig, Germany (full match; match highlights). The final was played between team Tech United from the Netherlands and team WATER from China. The winner of this would become world champion robot soccer in the MSL. At the end of the match, the scoreboard showed 2-2. Per MSL rules (as is in FIFA rules), a tied score results in extra time to decide on the winner. During the match, team WATER faced issues with ball handling, preventing the ball from rotating in a ‘natural’ way over the field. When it happens that the ball does not rotate in the direction it is being moved, this is considered clamping and regarded as a foul in favor of the other team. In the last couple of minutes the score was 3-3 when WATER turned towards the Tech United goal, shot and scored the winning goal. While the Chinese team was already celebrating their victory, the auxiliary referee decided that the scoring robot was clamping the ball before scoring the goal. After a discussion with the main referee, it was decided to declare the goal invalid. Since the extra time also ended in a draw, penalties were needed to decide who would become the new world champion. After all penalties of the Chinese team were stopped by the Dutch keeper, the first shot of the Tech United robot went into the net. The Dutch team won the penalty series with 1-0 and thus Tech United became the world champion of 2016.

Tumbnail test video.png

AutoRef motivation

The events of the 2016 final match between the Dutch and Chinese MSL teams show how the decisions of human referees can affect the outcome of a match or even a tournament. Rules are always prone to interpretation, and a team which is disadvantaged by this will always complain. Referees have little means to justify their decisions other than their own observations and interpretations of the rules.

Referees in human soccer already use technology to support their decisions. Nowadays, several stadiums are already equipped with goal line technology and referees can be assisted by a Video Assistant Referee (VAR). If the use of technology keeps increasing, a human referee for might one day become entirely obsolete. The proceedings of a match could be measured and evaluated by some system of sensors. With enough (correct) data, this system would be able to recognize certain events and make decisions based on these event.

Robot soccer in RoboCup MSL can likewise benefit from such an autonomous refereeing system — an AutoRef — to ensure matches are played fairly.

Development history

Development of the AutoRef system architecture and implementation began in 2016 by TU/e PDEng trainees in the 2015–2017 cohort of the Mechatronic Systems Design (MSD) program as their Block II in-house project. Since then, each MSD cohort has contributed to AutoRef's continuation in their respective Block II in-house projects. In TU/e's 2019–2020 academic year, a team of students in the Honors program High Tech Systems realized the control of drones as part of AutoRef's implementation, with continued efforts in drone control by these students leading to the Firefly-project.

Team contributions in AutoRef's development history are divided by a paradigm shift starting with the 2020–2022 MSD cohort project team (AutoRef PDEng MSD 2020 or simply MSD 2020) contribution in 2021. Unlike the teams which came before it, MSD 2020 eliminated the requirement of quadcopter drones as the basis for the autonomous refereeing system and emphasized continuity as a key stakeholder concern in system architecture. As such, the history of AutoRef is presented across:

  1. the 2015–2020 system based on various quadcopter drones; and
  2. the 2021–present system.

2016–2020 (drone-based system)

See also: Team contributions

From 2016 through 2020 AutoRef's development was based on camera-equipped quadcopter drones in autonomously refereeing RoboCop Middle Size League (MSL) robot soccer matches. Most of the 2016–2020 projects introduced their own systems engineering and implementation approaches. This repetitive work combined with the relatively short two-month duration available to these teams prevented the entire V-model from being realized for AutoRef and therefore causing relatively poor overall project progress across different teams.

Repetitions of the project definition (i.e., the left-hand side of the V-model) are specifically evident across the 2016–2020 team documentation. Earlier MSD cohorts emphasized a fully autonomous referee, while later years scoped the project towards an assistive, supplementary system for human referees. All teams from 2016–2020 specify the requirement that the AutoRef system be based on quadcopter drones. However, nearly each team used a different type of drone model in their implementation. This discontinuity in drone hardware between teams (among other hardware differences) further contributed to the slow progress AutoRef's development. To summarize the AutoRef 2016–2020 team contributions in terms of the underlying drone hardware:

Illustration by Peter van Dooren, BSc student at Mechanical Engineering, TU Eindhoven, November 2016.

2021–present

See also: Team contributions

In 2021, to prevent further repetitive efforts and slowed progress in the development of AutoRef, the MSD 2020 team was tasked with ensuring continuity in their contribution to the project. AutoRef's technical specification resumed that of an autonomous refereeing system as to fully replace human refereeing in MSL. The drone-based specification for AutoRef featured in previous team systems — that is, the requirement that AutoRef use drones — was also eliminated by MSD 2020.

As of MSD 2020, AutoRef's system architecture and implementation pages now describe the current state of the project "as-is" without the voice or perspective of any specific team's contribution. Whereas pre-MSD 2020 team contribution pages provide standalone descriptions of their respective architecture and implemention, pages for MSD 2020 onwards only summarize their contributions, keeping the detailed documentation on AutoRef's pages. An archive was also initiated by MSD 2020 to satisfy their stakeholder requirement for an overview of all team contributions, past and present https://teams.microsoft.com/l/file/EA8BF37F-3469-4424-9010-BEADD8E96EE9?tenantId=cc7df247-60ce-4a0f-9d75-704cf60efc64&fileType=xlsx&objectUrl=https%3A%2F%2Ftuenl.sharepoint.com%2Fsites%2FMCS_Drone_Referee_project_Team%2FShared%20Documents%2FGeneral%2FAutoRef%20Project%202020%20Final%20Deliverables%2FDocumentation%20%26%20Archive%2FArchive%20of%20past%20year's%20work.xlsx&baseUrl=https%3A%2F%2Ftuenl.sharepoint.com%2Fsites%2FMCS_Drone_Referee_project_Team&serviceName=teams&threadId=19:67b92555afdd4fdbbc40f984fb35696c@thread.tacv2&groupId=1efe2c69-ea31-43f1-9b96-c1c8cfa600e6.

System architecture

Main article: AutoRef system architecture

Implementation

Main article: AutoRef implementation

Team contributions

Note: This chapter is being actively modified.

Whereas pre-MSD 2020 team contribution pages provide standalone descriptions of their respective architecture and implemention, pages for MSD 2020 onwards only summarize their contributions, keeping the detailed documentation on AutoRef's pages. An archive was also initiated by MSD 2020 to satisfy their stakeholder requirement for an overview of all team contributions, past and present https://teams.microsoft.com/l/file/EA8BF37F-3469-4424-9010-BEADD8E96EE9?tenantId=cc7df247-60ce-4a0f-9d75-704cf60efc64&fileType=xlsx&objectUrl=https%3A%2F%2Ftuenl.sharepoint.com%2Fsites%2FMCS_Drone_Referee_project_Team%2FShared%20Documents%2FGeneral%2FAutoRef%20Project%202020%20Final%20Deliverables%2FDocumentation%20%26%20Archive%2FArchive%20of%20past%20year's%20work.xlsx&baseUrl=https%3A%2F%2Ftuenl.sharepoint.com%2Fsites%2FMCS_Drone_Referee_project_Team&serviceName=teams&threadId=19:67b92555afdd4fdbbc40f984fb35696c@thread.tacv2&groupId=1efe2c69-ea31-43f1-9b96-c1c8cfa600e6.

2016–2020 (drone-based system)

PDEng

High Tech Systems (HTS)

2021–present

PDEng

Archive

Link to archive needed (spreadsheet only accessible by TU/e entities)

Retrieved from "https://dsdwiki.wtb.tue.nl/index.php?title=AutoRef_-_Autonomous_Referee_System&oldid=112110"