-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* first draft of fastest walk * first draft of kick leaderboard * first draft of passing leaderboard * first draft of ball control * initial glicko section * move leaderboards to seperate file * remove old leaderboard .tex * remove leaderboards from general challenges * address comments * clarify walk leaderboard starting positions and timing * simplify walk leaderboard start conditions * address comments * update passing challenge and GPF * address comments * move figures * Add leaderboard figure generator * address comments * new score calculation * rename challenge to leaderboard * allow later attempt registration --------- Co-authored-by: electr0n <[email protected]>
- Loading branch information
Showing
9 changed files
with
717 additions
and
1 deletion.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,3 +24,4 @@ | |
|
||
SPL-Rules.pdf | ||
SPL-Challenges.pdf | ||
SPL-Leaderboards.pdf |
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,131 @@ | ||
% !TeX spellcheck = en_US | ||
\documentclass[12pt]{article} | ||
|
||
\usepackage{times,fullpage,xspace,fancyhdr,url,color} | ||
\usepackage[pdftex]{graphicx} | ||
\usepackage[pdftex, | ||
colorlinks=true, | ||
urlcolor=black, | ||
linkcolor=black, | ||
citecolor=black, | ||
bookmarksopen=false, | ||
bookmarksnumbered=true, | ||
pdfstartview=FitH]{hyperref} | ||
|
||
\pdfcompresslevel=9 | ||
\newcommand{\leaguename}{RoboCup Standard Platform League (NAO) } | ||
\hypersetup{ | ||
pdftitle={\leaguename Challenge Leaderboards}, | ||
pdfauthor={Technical Committee SPL}, | ||
} | ||
\usepackage{microtype} | ||
\usepackage[utf8]{inputenc} | ||
\usepackage{amsmath} | ||
\usepackage{xargs} | ||
\usepackage[colorinlistoftodos,prependcaption,textsize=tiny]{todonotes} | ||
\usepackage{siunitx} | ||
\usepackage[capitalize,noabbrev]{cleveref} | ||
\usepackage[official]{eurosym} | ||
\usepackage[useregional]{datetime2} | ||
\usepackage{subcaption} | ||
\usepackage{enumitem} | ||
\usepackage{xcolor} | ||
\DTMlangsetup[en-GB]{ord=raise,monthyearsep={,\space}} | ||
|
||
\newcommandx{\unsure}[2][1=]{\todo[linecolor=red,backgroundcolor=red!25,bordercolor=red,#1]{#2}} | ||
\newcommandx{\change}[2][1=]{\todo[linecolor=blue,backgroundcolor=blue!25,bordercolor=blue,#1]{#2}} | ||
\newcommandx{\info}[2][1=]{\todo[linecolor=green,backgroundcolor=green!25,bordercolor=green,#1]{#2}} | ||
\newcommandx{\improvement}[2][1=]{\todo[linecolor=Plum,backgroundcolor=Plum!25,bordercolor=Plum,#1]{#2}} | ||
|
||
% comment 'disable' in to disable all the todo notes :) | ||
\usepackage | ||
[ | ||
%disable | ||
]{todonotes} | ||
|
||
\usepackage[theorems]{tcolorbox} | ||
\newtcbtheorem[number within=section]{hintbox}{}% | ||
{colback=red!10,colframe=red!45!black,fonttitle=\bfseries}{th} | ||
|
||
\include{common/spl_variables} | ||
\include{common/spl_dates} | ||
|
||
\sloppy | ||
\newcommand{\ie}{\mbox{i.\,e.}\xspace} | ||
\newcommand{\eg}{\mbox{e.\,g.}\xspace} | ||
%\newcommand{\cf}{\mbox{cf.}\xspace} | ||
\newcommand{\cf}{see\xspace} | ||
% \newcommand{\comment}[1]{\marginpar{\pdfannot width 4in height .5in depth 8pt {/Subtype /Text /Contents (#1)}}} | ||
\newcommand{\inparagraph}[1]{\paragraph{#1\hspace{-1em} }} | ||
|
||
|
||
% some colors | ||
\definecolor{orange}{rgb}{1,0.5,0} | ||
\definecolor{red}{rgb}{1,0,0} | ||
\definecolor{green}{rgb}{0,1,0} | ||
|
||
|
||
\title{\leaguename\\ Hall of Fame Leaderboards} | ||
\author{RoboCup Technical Committee} | ||
\date{(\RCYear leaderboard challenges, as of \today)} | ||
|
||
\setlength{\parindent}{0pt} | ||
\setlength{\parskip}{12pt plus 6pt minus 3 pt} | ||
\setcounter{tocdepth}{1} | ||
\widowpenalty=10000 | ||
\clubpenalty=10000 | ||
|
||
\pagestyle{fancy} | ||
\lhead{} | ||
\chead{} | ||
\rhead{} | ||
\lfoot{} | ||
\cfoot{} | ||
\rfoot{} | ||
|
||
\renewcommand{\headrulewidth}{0.4pt} | ||
\renewcommand{\footrulewidth}{0.4pt} | ||
|
||
% needed to align an image and text correctly side by side | ||
\newcommand{\imagebox}[1]{\raisebox{2ex}{\raisebox{-\height}{#1}}} | ||
|
||
\begin{document} | ||
|
||
\maketitle | ||
|
||
\begin{center} | ||
Questions or comments on the leaderboard rules should be submitted via \url{https://github.com/RoboCup-SPL/Rules/issues}, to the \texttt{\#rule-book} channel on the SPL Discord server, or by mail to \url{[email protected]}. | ||
\end{center} | ||
|
||
\newpage | ||
|
||
\tableofcontents | ||
\setcounter{tocdepth}{3} | ||
|
||
\thispagestyle{fancy} | ||
|
||
\clearpage | ||
|
||
\cfoot{\thepage} | ||
\setcounter{page}{1} | ||
|
||
\section{Introduction} | ||
Starting in 2025, several leaderboards will be introduced to track and compare team performances across key skills | ||
over multiple years. These leaderboards aim to motivate teams to improve in specific areas deemed valuable by the | ||
league and to compile a record of the top-performing components and skills. By highlighting these individual skills, | ||
the league encourages focused development in areas that contribute to overall team performance, and creates a showcase | ||
of the best technical abilities in the league. | ||
|
||
\subsection{Code Publication} | ||
Every team participating in a challenge must publish the corresponding code used in that competition according to Appendix A.7 of the SPL rule book, unless a specific challenge states otherwise. | ||
|
||
\subsection{Challenge Rules} | ||
Each year, teams can choose to make an attempt at specific leaderboard challenges. The Technical Committee and Organizing | ||
Committee will coordinate dedicated time slots at RoboCup for teams to complete three attempts at each leaderboard challenge. | ||
Metrics from each attempt will be recorded and added to the appropriate leaderboard. Each leaderboard will be based | ||
on unique metrics and procedures, detailed below. Teams should indicate their intention for a leaderboard attempt 2 weeks before | ||
the first competition day. Scheduling attempts after this deadline may not be possible. | ||
|
||
\include{leaderboards/leaderboard_challenges} | ||
|
||
\end{document} |
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
Binary file not shown.
Oops, something went wrong.