Lab Format & Logistics
Format
The Embodied AI Labs balance concepts, implementation, experimentation, and reflection.
Each repository provides a student-facing README.md for setup and commands and
an ASSIGNMENT.md for the required experiments, questions, deliverables, and
rubric.
-
Project setup Create a private group repository from the assigned public template and prepare the documented environment.
-
Implementation and checks Complete the assigned components and use the repository’s checks to validate the system incrementally.
-
Experimentation and evaluation Run the required scenarios, collect result artifacts, and compare timing, security, safety, or policy behavior.
-
Discussion and reflection Explain failure cases, safety boundaries, physical outcomes, and the limits of the evaluation.
Deliverables
The canonical deliverables and grading rubric are in the assigned repository’s
ASSIGNMENT.md. Typical deliverables include:
- concise written answers and result tables,
- completed source code and configuration,
- required experiment artifacts, and
- a submission archive generated by the repository’s submission script.
Logistics
The public repositories are templates. Create a private repository for your group, add only your project partners, and do not publish course work in a public repository.
Choose the environment documented for your assigned lab:
| Lab | Primary workflow | Model or simulation use |
|---|---|---|
| A: Agentic Driving Coach | ASU Sol; personal Linux is an alternative | CPU timing and replay exercises; GPU allocation for the documented live LLM runs |
| B: Embodied Agent Authentication | ASU Sol | Live VLM inference with ROS 2 and SST in a GPU allocation |
| C: Safe Agent Actuation | ASU Sol CPU allocation | Committed model capture, synthetic fixtures, real SST, and a recording actuator harness |
| D: Safe Multi-Embodied Agents | Native Ubuntu, native macOS, or ASU Sol CPU allocation | SUMO simulation and a message network; no live model or GPU |
Follow the allocation, container, and cleanup instructions for your specific project. Do not run compute-intensive work on a Sol login node. Environment checks confirm that tools are ready; they do not establish that unfinished student implementations are correct or that graded experiments are valid.
Each assignment has common CSE 494/598 work and an additional CSE 598 extension. Include the extension in the same group submission archive, using the repository’s section-specific packaging command where provided. Keep recorded model output, synthetic fixtures, live measurements, and offline diagnostics clearly identified in your answers.
The course LMS remains authoritative for deadlines, group assignments, and submission. Before uploading, inspect the generated archive and confirm that it contains the current code, answers, and required results.