Skip to content

Commit

Permalink
deploy: e06470d
Browse files Browse the repository at this point in the history
  • Loading branch information
ChristianH99 committed Nov 1, 2024
1 parent 037296d commit 7afeb47
Show file tree
Hide file tree
Showing 2 changed files with 54 additions and 35 deletions.
89 changes: 54 additions & 35 deletions 2025-draft/onstage_rules.html
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="generator" content="Asciidoctor 2.0.23">
<meta name="author" content="2024-10-11">
<title>RoboCupJunior OnStage Rules 2025 - DRAFT</title>
<meta name="author" content="2024-11-01">
<title>RoboCupJunior OnStage Rules 2025</title>
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700">
<style>
/*! Asciidoctor default stylesheet | MIT License | https://asciidoctor.org */
Expand Down Expand Up @@ -437,9 +437,9 @@
</head>
<body class="article toc2 toc-left">
<div id="header">
<h1>RoboCupJunior OnStage Rules 2025 - DRAFT</h1>
<h1>RoboCupJunior OnStage Rules 2025</h1>
<div class="details">
<span id="author" class="author">2024-10-11</span><br>
<span id="author" class="author">2024-11-01</span><br>
</div>
<div id="toc" class="toc2">
<div id="toctitle">Table of Contents</div>
Expand Down Expand Up @@ -538,6 +538,10 @@ <h2 id="_robocupjunior_forum" class="discrete">RoboCupJunior Forum</h2>
<div class="paragraph">
<p>For inquiries and questions about the rules or competition updates, the <strong>Official RoboCupJunior forum</strong> (<a href="https://junior.forum.robocup.org/" class="bare">https://junior.forum.robocup.org/</a>) can be used to contact the OnStage League Committee. All official communication from the committee will be published here before and during the competition season.</p>
</div>
<h2 id="_robocupjunior_onstage_community_website" class="discrete">RoboCupJunior OnStage Community Website</h2>
<div class="paragraph">
<p>Ressources for participating in the OnStage league can be found on the OnStage community website: <a href="https://robocup-junior.github.io/onstage" class="bare">https://robocup-junior.github.io/onstage</a></p>
</div>
<h2 id="_robocupjunior_onstage_youtube_channel" class="discrete">RoboCupJunior OnStage YouTube channel</h2>
<div class="paragraph">
<p>Examples of good performances and documentation can be found on the <strong>Official RoboCupJunior OnStage YouTube channel</strong> (<a href="https://www.youtube.com/@rcjonstage" class="bare">https://www.youtube.com/@rcjonstage</a>).</p>
Expand All @@ -553,7 +557,7 @@ <h2 id="_overview" class="discrete">Overview</h2>
<p>An OnStage Performance must showcase the implementation and integration of robotic features in ways that visually enhance or add value and contribute to the theme or story being portrayed. More information about the selection of the features can be found in <a href="#judging-overview">Section 1, &#8220;Judging Overview&#8221;</a>.</p>
</div>
<div class="paragraph">
<p>During the International RoboCupJunior OnStage Competition, teams also take part in a SuperTeam Challenge. The SuperTeam Challenge is a robotic performance created by a group of two or more cooperating teams from different regions. The SuperTeams spend a short period of time for the collaborative performance creation. More details will be released before the International RoboCupJunior competition .</p>
<p>During the International RoboCupJunior OnStage Competition, teams also take part in a SuperTeam Challenge. The SuperTeam Challenge is a robotic performance created by a group of two or more cooperating teams from different regions. The SuperTeams spend a short period of time for the collaborative performance creation. More details will be released before the International RoboCupJunior competition.</p>
</div>
<div class="paragraph">
<p>From 2021 onwards, there will be no sub-leagues in RoboCupJunior OnStage.</p>
Expand All @@ -570,13 +574,17 @@ <h2 id="_overview" class="discrete">Overview</h2>
</tr>
</tbody>
</table>
<h2 id="_general_rules" class="discrete">General rules</h2>
<div id="addition-1" class="paragraph">
<p><strong><span class="red">Refer to the general RoboCupJunior rules (<a href="https://junior.robocup.org/robocupjunior-general-rules/" class="bare">https://junior.robocup.org/robocupjunior-general-rules/</a>) for additional restrictions and requirements.</span></strong></p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="judging-overview"><a class="anchor" href="#judging-overview"></a><a class="link" href="#judging-overview">1. Judging Overview</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>All teams are judged in the following areas: Technical Description Poster, Technical Demonstration Video, Technical Interview and the OnStage Performance. Teams must highlight four of their robot(s) <strong>features</strong> in the work they present to the judges. Ask the following question - “What do we believe are our best system/sensor integration, electromechanical design, interaction, or software solutions implemented on our robot(s)? <a id="addition-1"></a>
<p>All teams are judged in the following areas: Technical Description Poster, Technical Demonstration Video, Technical Interview and the OnStage Performance. Teams must highlight four of their robot(s) <strong>features</strong> in the work they present to the judges. Ask the following question - “What do we believe are our best system/sensor integration, electromechanical design, interaction, or software solutions implemented on our robot(s)? <a id="addition-2"></a>
<strong><span class="red">Why/how does our project stand out from other teams’ projects?</span></strong>” The aim should be to present how the chosen features are integrated to enhance the quality of the performance in unique and innovative ways. Examples of features include, but are not limited to:</p>
</div>
<div class="ulist compact">
Expand Down Expand Up @@ -604,7 +612,7 @@ <h2 id="judging-overview"><a class="anchor" href="#judging-overview"></a><a clas
<div class="paragraph">
<p>Teams should describe and provide reasoning for their four chosen features in the Technical Description Poster and during their Technical Demonstration Video, before being judged on the implementation of these features during the Performance. In addition, teams should demonstrate their understanding of their systems in the Technical Interview.</p>
</div>
<div id="addition-2" class="paragraph">
<div id="addition-3" class="paragraph">
<p><strong><span class="red">More information on the selection of features can be found in the Article</span></strong> <strong>How to Decide on Your OnStage Robotic Features</strong> (<a href="https://robocup-junior.github.io/onstage/resources/teams/how_to_features.html" class="bare">https://robocup-junior.github.io/onstage/resources/teams/how_to_features.html</a>).</p>
</div>
<div class="paragraph">
Expand Down Expand Up @@ -695,10 +703,10 @@ <h3 id="restarts"><a class="anchor" href="#restarts"></a><a class="link" href="#
<p>Teams can restart their routine if necessary, at the discretion of the judges. There is no limit on the number of restarts allowed within the stage-time. <a id="deletion-1"></a>
<sup class="footnote">[<a id="_footnoteref_1" class="footnote" href="#_footnotedef_1" title="View footnote.">1</a>]</sup></p>
</div>
<div id="addition-3" class="paragraph">
<div id="addition-4" class="paragraph">
<p><strong><span class="red">The team can restart without reentering the stage and with a clear countdown (3-2-1) to the judges.</span></strong></p>
</div>
<div id="addition-4" class="paragraph">
<div id="addition-5" class="paragraph">
<p><strong><span class="red">Scores and deductions are reset to 0 after the team has requested a restart. Deductions for every restart will be applied at the end of the performance according to the scoresheet.</span></strong></p>
</div>
<div class="paragraph">
Expand Down Expand Up @@ -763,16 +771,17 @@ <h3 id="robots"><a class="anchor" href="#robots"></a><a class="link" href="#robo
<div class="sect2">
<h3 id="communication-and-localization"><a class="anchor" href="#communication-and-localization"></a><a class="link" href="#communication-and-localization">3.6. Communication and Localization</a></h3>
<div class="paragraph">
<p>Teams are encouraged to design their robots to interact with a communication function. Robots are encouraged to communicate with each other during the performance. Suggested and allowed communication protocols are infrared (IR), Bluetooth (LE and classic), ZigBee, RFID or other localization platforms.</p>
<p>Teams are encouraged to design their robots to interact with a communication function. Robots are encouraged to communicate with each other during the performance. Suggested <a id="deletion-2"></a>
<sup class="footnote">[<a id="_footnoteref_2" class="footnote" href="#_footnotedef_2" title="View footnote.">2</a>]</sup> communication protocols are infrared (IR), Bluetooth (LE and classic), ZigBee, RFID or other localization platforms.</p>
</div>
<div class="paragraph">
<p>There must be no communication between off-stage and on-stage devices.</p>
</div>
<div class="paragraph">
<p>It is the team’s responsibility to make sure that their communication function does not interfere with other teams' robots when practicing or performing.</p>
</div>
<div class="paragraph">
<p>No team is permitted to use other radio frequency (RF) signals (like Wi-Fi or Z waves) as this may interfere with robots in other RoboCup leagues. If you are unsure, please check with the OnStage League Committee before your performance.</p>
<div id="deletion-3" class="paragraph">
<p><sup class="footnote">[<a id="_footnoteref_3" class="footnote" href="#_footnotedef_3" title="View footnote.">3</a>]</sup></p>
</div>
<div class="paragraph">
<p>Teams should prepare for disruptions in communication protocols and unavailability of Wifi (as outlined in the general rules) before and during the setup and stage time.</p>
Expand All @@ -792,7 +801,7 @@ <h3 id="scenery"><a class="anchor" href="#scenery"></a><a class="link" href="#sc
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Props that interact with robots via sensors <a id="addition-5"></a>
<p>Props that interact with robots via sensors <a id="addition-6"></a>
<strong><span class="red">(mounted either on the robot or the props)</span></strong></p>
</li>
<li>
Expand Down Expand Up @@ -843,8 +852,10 @@ <h3 id="humans-on-stage"><a class="anchor" href="#humans-on-stage"></a><a class=
<div class="sect2">
<h3 id="deductions"><a class="anchor" href="#deductions"></a><a class="link" href="#deductions">3.10. Deductions</a></h3>
<div class="paragraph">
<p>Refer to the scoresheet for the list of deductions.
All robot movements or interactions that happen outside the performance area will not be considered for the scoring, but will not lead to deductions.</p>
<p>Refer to the scoresheet for the list of deductions.</p>
</div>
<div class="paragraph">
<p>All robot movements or interactions that happen outside the performance area will not be considered for the scoring, but will not lead to deductions.</p>
</div>
<div class="paragraph">
<p>Teams are reminded that humans triggering the progress of the performance via touch-based sensors will be considered remote-controlled interaction and therefore will be considered an unplanned human interaction.</p>
Expand Down Expand Up @@ -885,16 +896,15 @@ <h3 id="content"><a class="anchor" href="#content"></a><a class="link" href="#co
</div>
<div class="sect2">
<h3 id="saftety-and-power-considerations"><a class="anchor" href="#saftety-and-power-considerations"></a><a class="link" href="#saftety-and-power-considerations">3.14. Safety and Power Considerations</a></h3>
<div class="paragraph">
<p>Under no circumstances can <strong>mains electricity</strong> be used during the performance. <a id="deletion-2"></a>
<sup class="footnote">[<a id="_footnoteref_2" class="footnote" href="#_footnotedef_2" title="View footnote.">2</a>]</sup></p>
<div id="deletion-4" class="paragraph">
<p><sup class="footnote">[<a id="_footnoteref_4" class="footnote" href="#_footnotedef_4" title="View footnote.">4</a>]</sup></p>
</div>
<div id="deletion-3" class="paragraph">
<p><sup class="footnote">[<a id="_footnoteref_3" class="footnote" href="#_footnotedef_3" title="View footnote.">3</a>]</sup></p>
<div id="deletion-5" class="paragraph">
<p><sup class="footnote">[<a id="_footnoteref_5" class="footnote" href="#_footnotedef_5" title="View footnote.">5</a>]</sup></p>
</div>
<div class="paragraph">
<p>Teams should be aware of the proper handling of <a id="deletion-4"></a>
<sup class="footnote">[<a id="_footnoteref_4" class="footnote" href="#_footnotedef_4" title="View footnote.">4</a>]</sup> batteries to ensure safety.</p>
<p>Teams should be aware of the proper handling of <a id="deletion-6"></a>
<sup class="footnote">[<a id="_footnoteref_6" class="footnote" href="#_footnotedef_6" title="View footnote.">6</a>]</sup> batteries to ensure safety.</p>
</div>
<div class="paragraph">
<p>Lithium batteries must be transported or moved in safety bags.</p>
Expand Down Expand Up @@ -939,7 +949,7 @@ <h3 id="interview-procedure"><a class="anchor" href="#interview-procedure"></a><
<p>All teams will have up to 20 minutes of technical interview judging during the competition. Which will take place as an in-person meeting with the judges in a separate room at the venue.</p>
</div>
<div class="paragraph">
<p>Interviews will be judged by at least two RoboCupJunior officials <a id="addition-6"></a>
<p>Interviews will be judged by at least two RoboCupJunior officials <a id="addition-7"></a>
<strong><span class="red">who have also scored the teams poster beforehand</span></strong>.</p>
</div>
<div class="paragraph">
Expand Down Expand Up @@ -993,9 +1003,9 @@ <h3 id="technical-demonstration-video"><a class="anchor" href="#technical-demons
<div class="paragraph">
<p>The maximum length of the video is <a id="substitution-1"></a>
<strong><span class="red">6</span></strong>
<sup class="footnote">[<a id="_footnoteref_5" class="footnote" href="#_footnotedef_5" title="View footnote.">5</a>]</sup> minutes. If it is longer than <a id="substitution-2"></a>
<sup class="footnote">[<a id="_footnoteref_7" class="footnote" href="#_footnotedef_7" title="View footnote.">7</a>]</sup> minutes. If it is longer than <a id="substitution-2"></a>
<strong><span class="red">6</span></strong>
<sup class="footnote">[<a id="_footnoteref_6" class="footnote" href="#_footnotedef_6" title="View footnote.">6</a>]</sup> minutes, it will be cut to that time for judging.</p>
<sup class="footnote">[<a id="_footnoteref_8" class="footnote" href="#_footnotedef_8" title="View footnote.">8</a>]</sup> minutes, it will be cut to that time for judging.</p>
</div>
<div class="paragraph">
<p>Robots should be presented without their costumes and key features of the technologies used should be visible to the audience.</p>
Expand Down Expand Up @@ -1027,8 +1037,8 @@ <h3 id="technical-description-poster"><a class="anchor" href="#technical-descrip
<div class="paragraph">
<p>Teams must submit a digital copy of their poster in PDF format (≤ 10 MB).</p>
</div>
<div class="paragraph">
<p>The size of the poster should be no larger than A1 (60 x 84 cm).</p>
<div id="deletion-7" class="paragraph">
<p><sup class="footnote">[<a id="_footnoteref_9" class="footnote" href="#_footnotedef_9" title="View footnote.">9</a>]</sup></p>
</div>
<div class="paragraph">
<p>Areas that are useful to be included in the poster are:</p>
Expand All @@ -1048,11 +1058,11 @@ <h3 id="technical-description-poster"><a class="anchor" href="#technical-descrip
<p>system diagrams of the systems and robot(s) under development at various stages</p>
</li>
<li>
<p><a id="addition-7"></a>
<p><a id="addition-8"></a>
<strong><span class="red">interconnection of robots (examples could include: network connection diagram, exploded views of robots, &#8230;&#8203;)</span></strong></p>
</li>
<li>
<p><a id="addition-8"></a>
<p><a id="addition-9"></a>
<strong><span class="red">flowchart of performance (Robot A triggers Robot B, Robot B communicates to Robot C)</span></strong></p>
</li>
<li>
Expand Down Expand Up @@ -1307,24 +1317,33 @@ <h2 id="appendix-b" class="discrete">Appendix B - Ressources to be released duri
<a href="#_footnoteref_1">1</a>. In previous version this said "Penalty marks will be deducted from the score."
</div>
<div class="footnote" id="_footnotedef_2">
<a href="#_footnoteref_2">2</a>. In previous version this said "Every robot should be equipped with some sort of battery power, with a maximum of 15 volts."
<a href="#_footnoteref_2">2</a>. In previous version this said "and allowed"
</div>
<div class="footnote" id="_footnotedef_3">
<a href="#_footnoteref_3">3</a>. In previous version this said "Lead-acid batteries are not considered appropriate unless the team has gained permission from the OnStage League Committee <strong>before</strong> attending the competition for a specific reason. Failure to declare batteries may result in disciplinary actions, including deductions."
<a href="#_footnoteref_3">3</a>. In previous version this said "No team is permitted to use other radio frequency (RF) signals (like Wi-Fi or Z waves) as this may interfere with robots in other RoboCup leagues. If you are unsure, please check with the OnStage League Committee before your performance."
</div>
<div class="footnote" id="_footnotedef_4">
<a href="#_footnoteref_4">4</a>. In previous version this said "lithium"
<a href="#_footnoteref_4">4</a>. In previous version this said "Under no circumstances can <strong>mains electricity</strong> be used during the performance. Every robot should be equipped with some sort of battery power, with a maximum of 15 volts."
</div>
<div class="footnote" id="_footnotedef_5">
<a href="#_footnoteref_5">5</a>. In previous version this said "5"
<a href="#_footnoteref_5">5</a>. In previous version this said "Lead-acid batteries are not considered appropriate unless the team has gained permission from the OnStage League Committee <strong>before</strong> attending the competition for a specific reason. Failure to declare batteries may result in disciplinary actions, including deductions."
</div>
<div class="footnote" id="_footnotedef_6">
<a href="#_footnoteref_6">6</a>. In previous version this said "5"
<a href="#_footnoteref_6">6</a>. In previous version this said "lithium"
</div>
<div class="footnote" id="_footnotedef_7">
<a href="#_footnoteref_7">7</a>. In previous version this said "5"
</div>
<div class="footnote" id="_footnotedef_8">
<a href="#_footnoteref_8">8</a>. In previous version this said "5"
</div>
<div class="footnote" id="_footnotedef_9">
<a href="#_footnoteref_9">9</a>. In previous version this said "The size of the poster should be no larger than A1 (60 x 84 cm)."
</div>
</div>
<div id="footer">
<div id="footer-text">
Last updated 2024-10-11 15:21:14 UTC
Last updated 2024-11-01 15:45:14 UTC
</div>
</div>
</body>
Expand Down
Binary file modified 2025-draft/onstage_rules.pdf
Binary file not shown.

0 comments on commit 7afeb47

Please sign in to comment.