Its public code is organized around evaluation, with policy-serving infrastructure separated from the benchmark itself. Simulation uses Isaac Sim, while physical evaluation requires its prescribed hardware and resets.
RoboDojo research team · Publication date not disclosed · Source accessed 2026-09-28
Reading results
The repository records observation and asset fixes during September 2026. A reported score therefore needs the environment revision and observation pipeline, especially when comparing runs made before and after those fixes.
robodojo-benchmark · Publication date not disclosed · Source accessed 2026-09-28
Official README inspected live. Repository code terms do not automatically cover model weights, data, or third-party assets.
Reported benchmark results
Context before scores. Results from different benchmarks are not directly comparable. A simulation result does not establish real-world reliability, safety or commercial availability.
No result meets our complete revision and methodology requirements for this record yet. Inspect the original benchmark documentation before comparing published scores.
What this evidence does not establish
Physical and simulated tracks must be displayed separately. A mixed benchmark identity does not make each result a physical experiment.
Related reading is an editorial crosslink. Sourced connections describe relationships reported in the cited material. A link to a versioned profile does not establish compatibility with that version unless the connection note explicitly identifies it.