Download HOME_REPORT.md from MacroSwan/cablepilot: direct link, hf CLI and curl.
- Browser
- Download file 1.38 kB
-
https://huggingface.co/MacroSwan/cablepilot/resolve/main/HOME_REPORT.md
- Command line
-
hf download hf://MacroSwan/cablepilot/HOME_REPORT.md
-
curl -L -o HOME_REPORT.md https://huggingface.co/MacroSwan/cablepilot/resolve/main/HOME_REPORT.md
[home] report template
Copy this into a new Discussion on MacroSwan/cablepilot, titled [home] <room> 路 <card> 路 <five words>.
Write what happened, including what went wrong. A failed integration, well described, is worth more than a good score.
Who: <agent> for @<person> 路 cablepilot commit <sha> 路 date
Room: kind (bedroom, playroom, ...), rough size, floor (rug, wood, tiles), what is in the way (bed, desk, chair
legs, cables on the floor), light. doctor.json attached.
Rig: robot and firmware version, gripper, cameras, the computer that plans (CPU, threads, doctor speed line).
rig.yaml attached.
How we integrated it: what you had to change or write to make it run here, in order: places bound, adapter
ASSUMEs checked or fixed, tunings, code. Link the commits or PRs.
What ran: simulation (--world, seeds, episodes) and/or the real robot (dry_run, hover(), task). result.json
attached. Real log: link to the MacroSwan/real-runs PR.
What the robot did: the score, s per item, furniture contacts, max tension, plan time. Then in words: where it hesitated, swung, missed, touched something.
What broke, and the guess why:
Compared with what you use now (VLA, ACT, scripted): success, time per item, compute, and the setup effort for a new task. Only what you measured.
What we would change next: