-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
12 changed files
with
324 additions
and
74 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| \section{Robot Inspection} | ||
| \label{sec:robot_inspection} | ||
| Safety is the most important issue when interacting with humans and operating in the same physical workspace. Because of this, all participating robots are inspected before participating in RoboCup@Home. Every team needs to get their robot(s) inspected and approved so that they can participate in the competition. | ||
|
|
||
| \begin{enumerate} | ||
| \item \textbf{Procedure:} The \RobotInspection{} is conducted like a regular test, namely it starts with opening of the arena door (see~\refsec{rule:start_signal}). One team after another (and one robot after another) has to enter the \Arena{} through a designated entrance door, move to the \textit{Inspection Point}, and leave the arena through the designated exit door. In between entering and leaving, the robot is inspected by the \TC. | ||
| \item \textbf{Checked aspects:} During the \RobotInspection{}, each robot is checked for compliance with the competition rules (see~\refsec{rule:robots}), in particular: | ||
| \begin{itemize} | ||
| \item emergency button(s) | ||
| \item collision avoidance (a TC member steps in front of the robot) | ||
| \item voice of the robot (it must be loud and clear) | ||
| \item custom containers (bowl, tray, etc.) | ||
| \item external devices (including wireless network), if any | ||
| \item Alternative human-robot interfaces (see~\refsec{rule:asrcontinue}). | ||
| \item \textbi{Standard Platform robots} | ||
| \begin{itemize} | ||
| \item no modifications have been made | ||
| \item specification of the \iaterm{Official Standard Laptop}{OSL} (if required) | ||
| \end{itemize} | ||
| \item \textbi{Open Platform robots} | ||
| \begin{itemize} | ||
| \item robot speed and dimension | ||
| \item start button (if the team requires it) | ||
| \item robot speaker system (plug for RF transmission) | ||
| \item other safety issues (duct tape, hanging cables, sharp edges etc.) | ||
| \end{itemize} | ||
| \end{itemize} | ||
| \item \textbf{Re-inspection:} If the robot is not approved in the inspection, it is the responsibility of the team to get the approval at a later point. Robots are not allowed to participate in any test before passing the \RobotInspection. | ||
| \item \textbf{Time limit:} The robot inspection is interrupted after three minutes (per robot). When told so by the TC --- in case of time interrupt or failure --- the team has to move the robot out of the \Arena{} through the designated exit door. | ||
| \item \textbf{Appearance Evaluation:} In addition to the inspection, the TC evaluates the appearance of the robots. Robots are expected to look nice (no duct tape, no cables hanging loose etc.). In case of objection, the TC may penalize the team with a penalty of maximum 50 points. | ||
| \item \textbf{Accompanying team member:} Each robot is accompanied by only one team member (the team leader is advised). | ||
| \item \textbf{OC instructions (at least two hours before the \RobotInspection):} | ||
| \begin{itemize} | ||
| \item Announce the entry and exit doors. | ||
| \item Announce the location of the \textit{Inspection Point} in the \Arena{}. | ||
| \item Specify and announce where and when the poster teaser and the poster presentation session take place. | ||
| \end{itemize} | ||
| \end{enumerate} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -11,7 +11,7 @@ \section{Infrastructure} | |
| \label{sec:introduction:mailinglist} | ||
| The official \AtHome{} mailing list can be found at\\ | ||
| \href{mailto:[email protected]}{\small\texttt{[email protected]}}. | ||
| You can subscribe to the mailing list at: {\small\url{http://lists.robocup.org/cgi-bin/mailman/listinfo/robocup-athome}} | ||
| You can subscribe to the mailing list at: {\small\url{https://lists.robocup.org/mm/lists/robocup-athome.lists.robocup.org/}} | ||
|
|
||
| \paragraph{RoboCup@Home Web Page} | ||
| \label{sec:introduction:webpage} | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,141 @@ | ||
| %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
| \section{Organization of the Competition} | ||
| \label{sec:procedure_during_competition} | ||
|
|
||
| \section{Stage System}\label{rule:stages} | ||
|
|
||
| The competition features a \iterm{stage system}, namely it is organized in two stages, each consisting of a number of specific tasks, and ends with a \FINAL. | ||
| \begin{enumerate} | ||
| \item \textbf{Robot Inspection:} For security, robots are inspected during the \SetupDays. | ||
| A robot must pass the \RobotInspection{} test (see~\refsec{sec:robot_inspection}) so that it is allowed to compete. | ||
|
|
||
| \item \textbf{\SONE:} The first days of the competition are called \SONE. | ||
| All qualified teams that have passed the \RobotInspection{} can participate in \SONE. | ||
|
|
||
|
|
||
| \item \textbf{\STWO:} The best \emph{50\% of teams} after \SONE{} advance to \STWO. If the total number of teams is less than 12, up to 6 teams may advance to \STWO. | ||
| In this stage, tasks require more complex abilities or combinations of abilities. | ||
|
|
||
| \item \textbf{\FINAL:} The best \emph{two teams} of each league, namely the ones with the highest score after \STWO, advance to the \FINAL. | ||
| The final round features only a single task integrating all tested abilities. | ||
|
|
||
| \end{enumerate} | ||
| In case of having no considerable score deviation between a team advancing to the next stage and a team dropping out, the TC may announce additional teams advancing to the next stage. | ||
|
|
||
|
|
||
| %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | ||
| \section{Schedule} | ||
| \label{rule:schedule} | ||
|
|
||
| \begin{enumerate} | ||
| \item \textbf{Test Blocks:} For each test one Test Block is scheduled during which each (qualified) team gets at least two Test Slots assigned. With the Restaurant test being the exception where only one Test Slot is assigned. | ||
|
|
||
| \item \textbf{Test Slots:} During a Test Slot a team has the amount of time specified for the test to attempt to solve it. | ||
|
|
||
| \item \textbf{Participation is default:} Teams have to inform the OC in advance if they are skipping a Test Block. Without such indication, they may receive a penalty when not attending (see~\refsec{rule:not_attending}). | ||
|
|
||
| \end{enumerate} | ||
|
|
||
| % Please add the following required packages to your document preamble: | ||
| % \usepackage[table,xcdraw]{xcolor} | ||
| % If you use beamer only pass "xcolor=table" option, i.e. \documentclass[xcolor=table]{beamer} | ||
| \begin{table}[h] | ||
| \centering\small | ||
| \newcommand{\teams}[2]{% | ||
| \tiny | ||
| \begin{tabular}{c}% | ||
| \textit{Test slot 1, team $#1$}\\ | ||
| \textit{Test slot 1, team $#2$}\\ | ||
| $\vdots$\\ | ||
| \textit{Test slot $n$, team $#1$}\\ | ||
| \textit{Test slot $n$, team $#2$}\\ | ||
| \end{tabular} | ||
| } | ||
| \newcommand{\wcell}[2]{% | ||
| \parbox[c]{2.5cm}{% | ||
| \vspace{#1}% | ||
| \centering% | ||
| #2% | ||
| \vspace{#1}% | ||
| }% | ||
| } | ||
| \newcommand{\cell}[1]{\wcell{0.2\baselineskip}{#1}} | ||
| % \newcommand{\mr}[1]{\multirow{2}{*}{#1}} | ||
|
|
||
|
|
||
| \begin{tabular}{ | ||
| >{\centering\arraybackslash}m{2.5cm}|% | ||
| >{\columncolor[HTML]{9AFF99}}c |% | ||
| >{\columncolor[HTML]{9AFF99}}c |% | ||
| >{\columncolor[HTML]{CBCEFB}}c |% | ||
| >{\columncolor[HTML]{FF8D27}}c % | ||
| } | ||
| \multicolumn{1}{ c }{} | ||
| & \multicolumn{1}{ c }{\cellcolor{white} Day 1 } | ||
| & \multicolumn{1}{ c }{\cellcolor{white} Day 2 } | ||
| & \multicolumn{1}{ c }{\cellcolor{white} Day 3 } | ||
| & \multicolumn{1}{ c }{\cellcolor{white} Day 4 } | ||
| \\\hhline{~---~} | ||
|
|
||
| \cell{Block 1\\\footnotesize(9:00--11:00)} | ||
| & \cell{Help Me Carry} | ||
| & \cell{Serve Breakfast} | ||
| & \cell{Restaurant} | ||
| & \cellcolor{white} | ||
| \\\hhline{~----} | ||
|
|
||
|
|
||
|
|
||
| \multicolumn{1}{ c }{} | ||
| & \multicolumn{3}{ c }{\wcell{0.5\baselineskip}{\color{gray}\----Break---\-}} | ||
| & \multicolumn{1}{|c|}{\cellcolor[HTML]{FF8D27}\cell{\textbf{Finals}}} | ||
| \\\hhline{~----} | ||
|
|
||
| \cell{Block 2\\\footnotesize(13:00--15:00)} | ||
| & \cell{Receptionist} | ||
| & \cell{GPSR} | ||
| & \cell{Stickler for the Rules} | ||
| & \cellcolor{white} | ||
| \\\hhline{~---} | ||
|
|
||
|
|
||
|
|
||
| \multicolumn{1}{ c }{} | ||
| & \multicolumn{1}{ c }{\wcell{0.5\baselineskip}{\color[HTML]{029734}}} | ||
| & \multicolumn{1}{ c }{\wcell{0.5\baselineskip}{\color[HTML]{6668e5}Stage 2}} | ||
| & \multicolumn{1}{ c }{\cellcolor{white}} | ||
| \\\hhline{~---} | ||
|
|
||
| \cell{Block 3\\\footnotesize(17:00--19:00)} | ||
| & \cell{Storing Groceries} | ||
| & \cellcolor[HTML]{CBCEFB}\cell{Clean the Table} | ||
| & \cell{EGPSR} | ||
| & \cellcolor{white} | ||
| \\\hhline{~---} | ||
| \end{tabular} | ||
|
|
||
| \caption{Example schedule. | ||
| Each team has at least two Test Slots assigned in every Test Block. | ||
| } | ||
| \label{tbl:schedule} | ||
| \end{table} | ||
|
|
||
| \noindent Note that the actual allocation of blocks will be announced by the OC during the \SetupDays{} (see Table \ref{tbl:schedule}). | ||
|
|
||
| \section{Scoring System} | ||
| \label{rule:score_system} | ||
|
|
||
| Each task has a main objective and a set of bonus scores. | ||
| To score in a test, a team must successfully accomplish the main objective of the task; bonuses are not awarded otherwise. | ||
|
|
||
| The scoring system has the following constrains: | ||
| \begin{enumerate} | ||
| \item \textbf{\FINAL:} The final score is normalized. | ||
| \item \textbf{Minimum score:} The minimum total score per test in \SONE{} and \STWO{} is \scoring{0 points}. | ||
| In principle, teams cannot receive negative points, except if they receive penalties. | ||
| In particular, both penalties for not attending (see~\refsec{rule:not_attending}) and extraordinary penalties (see~\refsec{rule:extraordinary_penalties}) can result in a total negative score. | ||
| \end{enumerate} | ||
|
|
||
| % Local Variables: | ||
| % TeX-master: "../Rulebook" | ||
| % End: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.