Skip to content

Commit cfbde5f

Browse files
authored
Update f1tenth-sim-racing-guide.md
1 parent dc87999 commit cfbde5f

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/competitions/f1tenth-sim-racing-guide.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -605,6 +605,10 @@ Please make a note of the data streams mentioned above (along with their access
605605

606606
### 3.5. Container Submission
607607

608+
!!! note
609+
We expect that upon running your submitted container, all the necessary nodes should start up (the `autodrive_devkit` API we have included as well as your team's racing stack). Once we hit the `Connection Button` on the `Menu Panel` of AutoDRIVE Simulator, the simulated vehicle should start running. Please refer to the [competition rules](https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules), where it talks about the [submission requirements](https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules/#31-submission-requirements) and [submission process](https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-rules/#32-submission-process).
610+
Please make sure that you include all the necessary commands (for sourcing workspaces, setting environment variables, launching nodes, etc.) within the `entrypoint` script (`autodrive_devkit.sh` file) provided within the `autodrive_f1tenth_api` container. Please do **NOT** use `~/.bashrc` 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.
611+
608612
1. Run the image you created in the previous step inside a container:
609613
```bash
610614
xhost local:root

0 commit comments

Comments
 (0)