Milestone map
Milestone map
2 milestones
Build a ROS 2 robot in simulation
2–4 weeks (about 8 hrs/week, est)
Build a ROS 2 package with at least three nodes (a sensor publisher, a controller and a teleoperation or goal node) driving a robot in Gazebo, Webots or MuJoCo. Keep it in one public repo and commit as you go. No hardware needed: this milestone is done in simulation.
Proof required
Link the public repo with the ROS 2 package, a launch file that starts it, and a screen recording of the simulated robot responding to commands.
What gets checked
- It builds and launches from the README.
- Nodes talk through topics or services you designed.
- The robot in the simulator responds to commands.
Common mistakes
- One big upload with no commit history.
- Results the repo cannot reproduce.
Powstik Guide
A public repo with a ROS 2 package with at least three nodes (a sensor publisher, a controller and a teleoperation or goal node) driving a robot in Gazebo, Webots or MuJoCo.
Steps
- Make a public repo.
- Set up the simulator from its free docs.
- Build the smallest version that works, then measure it.
- Write a README: what it is, how to launch it, what the numbers show.
- Ask someone who knows robotics to check it.
Template
README Stage 3: Robot software What is here: How to launch it: Results: Limits:
What gets sent back
- No measurements.
- Code that does not work from the README.
- Copied code with no history.
Resources
Foundationstart here
What a verifier looks for
- It builds and launches from the README.
- Nodes talk through topics or services you designed.
- The robot in the simulator responds to commands.
- Open the repo: does the code produce what the recording shows?
You'll sign in first, then come straight back here.
Show it working to a person
1 week (about 4 hrs, est)
Show the robot (simulated, or real if you have one) following commands given live by someone else. Do it in person or on a live video call. Simulation-only route: if you have no hardware, a live run in the simulator counts.
Proof required
Name the person who watched and add the recording or your notes of what happened, including anything that failed.
What gets checked
- Commands come from the other person.
- The node graph is shown and explained.
- One failure is shown and handled.
Common mistakes
- A pre-recorded run passed off as live.
- Cutting the failures.
Powstik Guide
A live demo to one person who knows robotics, with notes or a recording.
Steps
- Agree the test with the person first.
- Let them choose the conditions.
- Show it live and record what happened.
- Write down what failed and why.
Template
Demo notes Who watched: What they asked for: What happened: What failed:
What gets sent back
- The person did not see it live.
- No notes or recording.
Resources
What a verifier looks for
- Commands come from the other person.
- The node graph is shown and explained.
- One failure is shown and handled.
- Did you watch it happen live?
You'll sign in first, then come straight back here.
Part of