Repository navigation
Conversation
Contributor
There was a problem hiding this comment.
go2 replay realtime (arm64)
Details
| Benchmark suite | Current: 1461538 | Previous: c3f0add | Ratio |
|---|---|---|---|
peak memory |
1827.445 MB |
1762.234 MB |
1.04 |
peak threads |
372 threads |
359 threads |
1.04 |
network (transport) |
2730.966 MB |
2735.794 MB |
1.00 |
disk write |
1.711 MB |
1.699 MB |
1.01 |
instructions |
137.526 G |
137.654 G |
1.00 |
This comment was automatically generated by workflow using github-action-benchmark.
❌ 5 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
# Conflicts: # dimos/robot/unitree/g1/blueprints/basic/unitree_g1_sonic_wbc.py
# Conflicts: # dimos/robot/unitree/g1/blueprints/basic/unitree_g1_sonic_wbc.py
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why do we need this?
Use the enterprise Pico browser's full-body tracking to drive G1 SONIC, without the native Pico/XRoboToolkit workaround and without a second controller owning the motors.
What is this feature?
Stack: #4304 -> #4305 -> #3557 -> #4783 -> #4784.
Controller UI companion: jeff-hykin/dim-controller#1.
Layer 5, based on #4783. 17 files, +1500/-60 relative to that base. Builds on Tom's WebXR/SMPL retargeting work in #3721 (
cc/feat/pico-teleop-sonic), adapted to the standalone SONIC controller.unitree-g1-sonic-webxr-teleopby composing the existing SONIC stack. One policy controller, one motor-command owner.No APK, PC Service, gRPC, native video, sim2 dependency or ControlCoordinator task. Unsupported browsers fail rather than falling back to head/wrist-only poses.
How to manually run this
On macOS or a CUDA-enabled Linux host with SONIC dependencies installed. On a Mac, first run
uv sync --extra control --extra sim; the blueprint selects CPU inference automatically. Real hardware still requires CUDA:Open
https://<simulation-host>:8443/teleopin the enterprise Pico browser using a trusted host certificate and enter the immersive session. The existing WebXR HTTPS setup applies.In simulation, check walking, A+X pose entry, asymmetric arm motion, return to walking, recenter, headset/controller disconnect and reconnect, Desktop Stop motion, and the four-button damping stop. Tracking recovery must not automatically re-enter pose mode. Inspect
status().webxrplus planner/decoder timing.Controls and acceptance checks.
Verification
On the final branch:
Unit tests use synthetic tracking and fake model/motor IO. Separately, native Mac CPU tests ran the actual models with both full blueprints in MuJoCo, with Rerun disabled: walking, stopping and staying upright without a policy fault. The WebXR HTTPS server started successfully. Legacy shared-memory resource-tracker cleanup warnings remain. A later repeat under severe host load (load average 150.8; 18.5 GB swap in use) hit the existing planner timeout and latched damping. The CPU path is functional, not a hard-real-time guarantee; no watchdog threshold was relaxed. Enterprise-Pico tracking and physical-robot acceptance remain pending; this PR stays draft. No robot deployment or actuation was performed.
Which issue(s) does this PR close?
Follow-up to #3557 and browser retargeting work from #3721; no separate issue closed.
Checklist