Repository navigation
Conversation
Contributor
There was a problem hiding this comment.
go2 replay realtime
Details
| Benchmark suite | Current: 1d029a8 | Previous: cdfaef0 | Ratio |
|---|---|---|---|
first frame wall |
9.3 s |
9.891 s |
0.94 |
first frame cpu |
18.938 s |
21.456 s |
0.88 |
run cpu |
29.88 s |
33.75 s |
0.89 |
run cpu (user) |
22.164 s |
26.257 s |
0.84 |
run cpu (system) |
7.715 s |
7.493 s |
1.03 |
peak memory |
2712.355 MB |
2699.734 MB |
1.00 |
peak threads |
404 threads |
394 threads |
1.03 |
disk read |
8.137 MB |
20.871 MB |
0.39 |
disk write |
11.137 MB |
11.098 MB |
1.00 |
network (transport) |
2713.989 MB |
2722.56 MB |
1.00 |
network (external rx) |
0.114 MB |
0.139 MB |
0.82 |
network (external tx) |
0.154 MB |
0.342 MB |
0.45 |
This comment was automatically generated by workflow using github-action-benchmark.
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Contributor
There was a problem hiding this comment.
go2 replay realtime (arm64)
Details
| Benchmark suite | Current: 55e5f9e | Previous: d793e80 | Ratio |
|---|---|---|---|
peak memory |
1740.984 MB |
1716.062 MB |
1.01 |
peak threads |
374 threads |
367 threads |
1.02 |
network (transport) |
2730.918 MB |
2724.058 MB |
1.00 |
disk write |
1.684 MB |
1.738 MB |
0.97 |
instructions |
137.561 G |
137.102 G |
1.00 |
This comment was automatically generated by workflow using github-action-benchmark.
1 task
TomCC7
force-pushed
the
cc/feat/webcam-capture-config
branch
from
October 28, 2026 04:52
b780b3a to
7468103
Compare
TomCC7
force-pushed
the
cc/feat/accepted-position-commands
branch
from
October 28, 2026 04:52
eea747e to
3bb478a
Compare
Consolidate reviewed layer changes from eea747e.
TomCC7
force-pushed
the
cc/feat/webcam-capture-config
branch
from
October 28, 2026 05:02
7468103 to
e79a972
Compare
TomCC7
force-pushed
the
cc/feat/accepted-position-commands
branch
from
October 28, 2026 05:02
3bb478a to
bff98d1
Compare
Preserve the existing PR history and inherit the updated parent layer.
…eview-stack-accepted-position-commands
Member
Author
|
I think we already have support for this in main? |
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.
What is this feature?
Publish applied_joint_position_command JointState events after successful POSITION/SERVO_POSITION hardware writes. Events contain only accepted joint targets and the control snapshot timestamp; publication occurs outside the hardware lock.
Why do we need this?
Dataset actions need accepted command history rather than measured state or commands that hardware rejected. This is a prerequisite of #4343, stacked after #4390 and immediately before the integration PR.
How to Test
97 control tests passed, including accepted/rejected writes and sparse target publication; commit hooks passed. Real hardware execution has not been verified.
Which issue(s) does this PR close?
None. This is a review slice of #4343, following the Manipulation SDK preview. It does not close or replace the integration PR.
Checklist
AI assistance: Codex assisted with the split, validation, and description.
Inherited review fixes
Inherit the #4395 complete-dataset publication and inspection fixes, and the #4396 recorder-local port declarations. Core Module and Blueprint definitions are unchanged, and the collection stack audit script is removed. This layer retains its existing control behavior and PR base.
The final assembled stack passed 278 host tests with two native-recorder tests excluded by the default marker filter. The LeRobot dataprep and MCAP suite passed 28 tests using cached LeRobot 0.6.0 and datasets 4.7.0; this is not a full locked-environment run. Scoped mypy passed for six scoped production files, and changed-file pre-commit passed. No dependencies were installed, no hardware was operated, and CI has not been checked.
Inherited training-key conversion
Inherit #4395's fixed LeRobot feature naming and MCAP-to-dataset E2E regression. Profiles retain their source declarations; conversion produces standard training-facing keys and records the mapping for inspection. No rename configuration is introduced. The final stack passed 278 host tests and 28 conversion/MCAP tests in the documented cached environment.
Rebased stack integration
Inherit #4395/#4396 rebased onto main, the recorder lifecycle fix, timestamp-boundary regression, and the Python-generated profile-to-dataset E2E. This layer keeps its original changes and existing history.
Current validation: 280 host tests passed with two pre-existing native-recorder tests excluded by the host marker filter. Thirty LeRobot conversion/E2E tests passed, including both Python-generated profile cases. Python tests used cached LeRobot 0.6.0 and datasets 4.7.0, not a complete locked isolated environment. The updated Python E2E passed scoped mypy; pre-commit passed. No physical hardware or policy training was used. CI has not been polled.