dimensionalOS / dimensionalOS/dimos
Autoresearch for go2 blueprint cpu/sys footprint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
deploy go2 big office replay, measuring cpu/sys time
time uv run dimos --replay --viewer=none --replay-dir=unitree_go2_bigoffice run unitree-go2
ask autoresearch to optimize cpu/sys usage
make sure that replay has some self-validation, for example makes sure none of the messages in the LCM pipeline have changed (run a recorder for example, compare with original recording)
Synced from DIM-756 by summer
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running time uv run dimos --replay --viewer=none --replay-dir=unitree_go2_bigoffice run unitree-go2 to establish CPU and sys-time behavior. Use a recorder with the go2 big office replay and compare its output with the original recording, checking that messages in the LCM pipeline have not changed. Done means autoresearch improves CPU/sys usage while replay self-validation still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, robotics, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100