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

Robotics capstone: an autonomous robot task

9 weeks · 2 milestones

Build a robot (real or simulated) that does one task on its own, with a success test written first and a 20-trial log, then demo it live under a new condition and defend it. The last step of the Varsity Curriculum: Robotics, read by a blind review for Honors.

Part of: Robotics · Proves for: Engineers, Career, UG

Milestone map

Milestone map

2 milestones

Build the capstone: an autonomous robot task

6–8 weeks (12–15 hrs/week)

Pick one task your robot does on its own from start to finish (for example find and fetch an object, or follow a route and avoid people), using what you built in the earlier stages. Write the success test first, then build it and log at least 20 trials. Hardware or simulation-only: both count.

Proof required

Link the public repo (code, launch files, configs), the success test you wrote first, and the trial log with every result, failures included.

What gets checked

  • The success test was written before the build.
  • At least 20 trials are logged, with the success rate.
  • It uses perception, planning and control together.

Common mistakes

  • Changing the success test after seeing the results.
  • Logging only the good trials.

Powstik Guide

An autonomous robot task with a success test written first and a 20-trial log.

Steps

  1. Write the task and the success test.
  2. Build the smallest version that works end to end.
  3. Log every trial.
  4. Fix the biggest failure and log again.

Template

Capstone
Task:
Success test (written first):
System (perception, planning, control):
Trials (n, successes, failures):
Limits:

What gets sent back

  • No trial log.
  • Success test changed after the results.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Was the test written first?
  • Does the log match the repo and the recordings?
  • Is it the person's own work?

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

Demo it live and defend it

1–2 weeks

Show the task live to at least three people, in person or on a live call, on hardware or in simulation. They pick at least one new condition. Then defend your design choices and your failures for 15 minutes. This is what the Honors blind review reads, with the recording.

Proof required

Link the recording of the live demo and the defence, and name the people who watched.

What gets checked

  • It runs live under a condition the watchers chose.
  • The defence explains the design and the failures honestly.
  • The recording includes the questions.

Common mistakes

  • A pre-recorded run.
  • Avoiding the hard questions.

Powstik Guide

A recorded live demo with a new condition chosen by the watchers, and a 15-minute defence.

Steps

  1. Invite at least three people who know robotics.
  2. Let them choose a new condition.
  3. Run it live and record it.
  4. Defend the design and the failures.

Template

Defence plan
Task:
Design choices:
Failures and why:
What I would change:

What gets sent back

  • Not live.
  • No new condition.

Resources

What a verifier looks for

  • Did it run live under your new condition?
  • Were the failures explained honestly?
  • Does the demo match the trial log?

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

Part of