dimensionalOS / dimensionalOS/dimos
Add ClockSyncConfigurator for Unitree WebRTC clock synchronization
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Problem
Unitree WebRTC connections require clock sync within 100ms between the control computer and the robot. Currently there's no automated check — if clocks drift, our video and odom look bad in replay
Solution
Utilize Blueprint.requirements() and SystemConfigurator to implement automatic clock sync checks
Wire into unitree_go2_basic and unitree_g1_basic blueprints via .requirements().
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 locating Blueprint.requirements(), SystemConfigurator, and the unitree_go2_basic and unitree_g1_basic blueprints. Trace how requirements are declared and checked before defining the ClockSyncConfigurator behavior. Done means both blueprints invoke the configurator and connections automatically check that the control computer and robot clocks are within 100ms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100