powstik
Prove
LiveProof-of-Work · Oct–Nov: every verified proof counts. 28 days leftAll outcomes
Skills

Robotics 5: Planning & control

6 weeks · 2 milestones

PID, path and motion planning, and picking things up. Stage 5 of the Varsity Curriculum: Robotics. A simulation-only route counts at every step; free resources only.

Part of: Robotics · Proves for: Engineers, UG

Milestone map

Milestone map

2 milestones

Plan, control and grasp in simulation

3–5 weeks (about 8 hrs/week, est)

Build a tuned PID controller, a path planner (for example A* or RRT) around obstacles, and a simple pick-and-place with a simulated arm. 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 controller, planner and grasp code, step-response plots for the controller, planning results on at least five maps, and a screen recording of the pick-and-place.

What gets checked

  • Step responses show overshoot and settling time.
  • The planner is tested on at least five maps, including one with no path.
  • Pick-and-place succeeds on most of at least ten trials, with the rate reported.

Common mistakes

  • One big upload with no commit history.
  • Results the repo cannot reproduce.

Powstik Guide

A public repo with a tuned PID controller, a path planner (for example A* or RRT) around obstacles, and a simple pick-and-place with a simulated arm.

Steps

  1. Make a public repo.
  2. Set up the simulator from its free docs.
  3. Build the smallest version that works, then measure it.
  4. Write a README: what it is, how to launch it, what the numbers show.
  5. Ask someone who knows robotics to check it.

Template

README
Stage 5: Planning & control
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

  • Step responses show overshoot and settling time.
  • The planner is tested on at least five maps, including one with no path.
  • Pick-and-place succeeds on most of at least ten trials, with the rate reported.
  • Open the repo: does the code produce what the recording shows?

You'll sign in first, then come straight back here.

Handle a goal someone else sets

1 week (about 4 hrs, est)

Show the robot reaching a goal and moving an object someone else chooses, on hardware or in simulation. 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

  • The goal and object are chosen by the other person.
  • Success or failure is recorded honestly.
  • The controller is explained.

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

  1. Agree the test with the person first.
  2. Let them choose the conditions.
  3. Show it live and record what happened.
  4. 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

  • The goal and object are chosen by the other person.
  • Success or failure is recorded honestly.
  • The controller is explained.
  • Did you watch it happen live?

You'll sign in first, then come straight back here.

Part of