Physical AI Lab 01
When does feedback matter?
Compare a scheduled pick-and-place with a feedback-guarded controller. Same physics. Measured outcomes.
What you will learnDistinguish commanded motion from verified load support; test a one-factor repair.
What runs herePhysX 5.6.1 contacts; designed waypoint controller with optional feedback guards. No learned policy.
Completion criteriaMeasured baseline, diagnostic evidence, controlled repair comparison, then four frozen transfer cases.
Choose a task preset, then run. Checkmarks come from recorded physical evidence, not clicking through.
Interactive workcell
Pick. Place. Verify.
- 01Observe
- 02Plan
- 03Act
- 04Verify
Measured state
Updated from the simulation- Physics engine
- Loading
- Experiment time
- 0.00 s
- Center height
- —
- Object speed
- —
- Gripper gap
- —
- Contact state
- Waiting
Measured at 120 physics steps/s; graph sampled at 10 Hz. No generated or predicted outcomes.
Saved on this device only.
Experiment log
- Choose a task and controller.
Open: u(t) = waypoint(schedule, t)
Closed: same u(t); advance only if guard(state)
contact ≥ 8 frames → lift y ≥ 0.85 m → retain
place: |x−xb|,|z−zb| < .27 m; |y−ys| < .055 m
settle: speed < .08 m/s, spin < .2 rad/s for .5 sOne 15 mm closure retry; then abort. μΣN ≳ mg is intuition, not the solver or a success oracle. All bodies remain native PhysX contacts. Occupancy is a user-set safety flag, not person detection.
Download controller sourceRun a matched pair for comparable evidence.