ROBOTICS 101
robotics-101 · v1.0.0
ivyx✓
Lay out a robot cell in a simulator, have two arms make something, and prove it with numbers you can defend.
What this course is for
By the end of this course you can lay out a robot cell in the simulator, have one arm or two make something there, and prove it with numbers that say what they cover.
What you will be able to do
- Read a proof record and say what twenty trials do and do not show
- Tell a contact that counts from one a job means, and find the first bad one in a record
- Lay out a bench of your own and prove a job on it
- Write a goal as a structure and find the relation that failed
- Measure what two arms at once save, on the simulator's clock
- Say why a passing simulator proof is not a measurement of a real arm
Who it is for
Learners who can read Python and want to work with robots, with no robot and no robotics background needed, because every mission runs in the simulator inside the window.
Before you start
- PYTHON 101, or comfort with lists, dictionaries and functions
Lesson path
A record, its trials and the contacts in it
- 1The cell30 min
Open a proof record and say what each part of it holds
- 2One cube, one tray55 min
Prove a pick and place and say what twenty trials can and cannot show
- 3What a contact is55 min
Find the first bad contact in a record and say why a success can still be a failure
Other arms, other parts, a goal you write
- 4The same job, another arm50 min
Compare one job across arms and say what changed besides the number
- 5Your own bench50 min
Describe a bench as a list of parts and predict what stops a layout
- 6A structure is a goal55 min
Write a build as relations and find the one that failed
Time, intended contact, and shapes
- 7Two arms at once60 min
Measure what two arms at once save on the simulator's clock
- 8Intended contact55 min
Say which touches a push is allowed and read a press's stopping force
- 9Parts that are not cubes50 min
Compare grasps of different shapes from their records
The envelope and what a proof is not
- 10Off the simulator40 min
Read an envelope, predict what it refuses, and say what a proof does not measure
About this course
ROBOTICS 101: Prove it in the simulator
A robot arm runs in a simulator inside the window, so nothing here can break and you need no hardware. What runs through all ten lessons is one question: how do you know it works? Each lesson reads real proof records from the workbench, teaches one way of reading them, and ends with a mission you do yourself. The lesson marks that mission from your own proof, not from your code.
You leave able to lay out a robot cell, have one arm or two make something there, and report what happened in a sentence that says what it covers.
How this course teaches
Same tutor as the rest of the series: predict before you run, and a hint ladder that ends in an explanation rather than in pasted code. No cell passes by being run. A blank raises until you fill it, a broken cell raises until you fix it, and every challenge checks its own work.
A robot mission is a different kind of cell. It reads the proof on record for that mission, so it does not matter whether the assistant wrote the behavior, whether you built it in the graph, or whether you drove it from Python. Pressing Run before the mission is proven is not a wrong answer. It shows you the mission and opens the workbench.
The particular danger of this subject is a number that is right and a sentence that is not. Twenty out of twenty is not 100%. A pooled score can describe no arm at all. A proof in a simulator is not a measurement of an arm. The diagnose cells are built out of mistakes like these, and most of them were made for real.
What you will be able to do
- Read a proof record and say what twenty trials do and do not show
- Tell a contact that counts from one a job means, and find the first bad one in a record
- Lay out a bench of your own and prove a job on it
- Write a goal as a structure and find the relation that failed
- Measure what two arms at once save, on the simulator's clock
- Say why a passing simulator proof is not a measurement of a real arm
What you need
PYTHON 101, or comfort with lists, dictionaries and functions. The robotics extension, which the course lists as a requirement, and an AI core if you want the assistant to write behaviors. No robot, no robotics background and no graphics card.
The data in the lessons is real: every record was written by the workbench on the arm it names, shortened to what the lesson reads.