Part of a public week-one log of moving from ML/quant work into robotics: what was actually run, what it cost, and the honest next steps. The scripting was done with an AI coding agent; every number below was measured on one CPU-only Linux box (Python 3.12, MuJoCo 4.0.1, PyTorch 2.15 CPU wheels).
The robotics job market talks about VLA and foundation models, but the
interviews keep probing the layer underneath: state estimation, kinematics,
contact, and the discipline of measuring before claiming. MuJoCo is free, runs on
a laptop CPU, and every experiment below is checkable by a reader in under an
hour.
pip install --target + PYTHONPATH + CPU torch wheels. Cost: about an hour,
most of it reading error messages. The recipe is written down so it costs you
ten minutes.env.step() on HalfCheetah: ~50
microseconds. So the bottleneck is gradient steps, not physics: a SAC update at
batch 256 costs about 6 ms. Multiply before you commit.
Everything above ships with logs: eval.csv per run, a plot script, and a README
whose tables are generated. The claim is never "I know robotics"; the claim is
"here is a working baseline, here is what it cost, check it yourself".
Everything above is checkable: code, full training logs and the generated comparison table are MIT-licensed at sac-mujoco-repro. If you'd rather skip re-running the 1M-step training yourself, the packaged version — logs, learning curves, checkpoints, README — is on our store for $1. The price is there to collect first reviews, not to gate the free repo.