You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: competitions/f1tenth-sim-racing-rules/index.html
+8-3Lines changed: 8 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -794,6 +794,11 @@ <h2 id="3-submission-guidelines">3. Submission Guidelines<a class="headerlink" h
794
794
Each team is expected to submit a containerized version of their autonomous racing software stack. Submissions for each phase of the competition will be done separately.
795
795
</p>
796
796
797
+
<divclass="admonition note">
798
+
<pclass="admonition-title">Note</p>
799
+
<p>We expect that upon running your submitted container, all the necessary nodes should start up (the <code>autodrive_devkit</code> API we have included as well as your team's racing stack). Once we hit the <code>Connection Button</code> on the <code>Menu Panel</code> of AutoDRIVE Simulator, the simulated vehicle should start running. Please refer to the <ahref="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules">competition rules</a>, where it talks about the <ahref="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules/#31-submission-requirements">submission requirements</a> and <ahref="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules/#32-submission-process">submission process</a>.</p>
800
+
</div>
801
+
<p>Please make sure that you include all the necessary commands (for sourcing workspaces, setting environment variables, launching nodes, etc.) within the <code>entrypoint</code> script (<code>autodrive_devkit.sh</code> file) provided within the <code>autodrive_f1tenth_api</code> container. Please do <strong>NOT</strong> use <code>~/.bashrc</code> or other means to automate the algorithm execution! Competition organizers should be able to start additional bash session(s) within your submitted container (without your codebase executing every time a new bash session is initialized) for data recording and inspection purposes.</p>
<p>Teams can test their algorithms locally before containerizing them. However, don't forget to test the containerized approach before submitting!</p>
817
+
<p>Teams can test their algorithms locally before containerizing them. However, don't forget to test your containers before pushing them upstream and submitting them!</p>
<li>Teams will <b>containerize</b> their autonomous racing software stack using <ahref="https://www.docker.com">Docker</a>.</li>
821
-
<li>Teams will <b>push</b> their Docker container image to <ahref="https://hub.docker.com">DockerHub</a>.</li>
826
+
<li>Teams will <b>push</b> their self-sustainable Docker container image to <ahref="https://hub.docker.com">DockerHub</a>.</li>
822
827
<li>Teams will <b>share</b> the link of the upstream repository with the organizers via a secure submission form (separate forms for each stage of the competition).</li>
0 commit comments