dimensionalOS / dimensionalOS/dimos
Investigate potential GO2 Performance issues
Open
Nobody has claimed this yet.
bug
go2
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
run time dimos --replay --viewer=none run unitree-go2
on current dev, on dev 2 months ago, on dev 4 months ago, my feeling is that performance got much worse
log cpu time, system time
Synced from DIM-728 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 dimos --replay --viewer=none run unitree-go2 on current dev and the dev revisions from two and four months ago. Record CPU time and system time for each run, then compare the results to determine whether performance regressed and document the findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100