Repository navigation
lmg_deploy: /lowstate torso IMU, any observation layout, arm_ik arms, game-task goals - #41
Merged
Merged
Conversation
… game-task goals For the Locomanipulation_game exports from 2026-11-20 (pre-pose engage training, the torso IMU): - imu.source lowstate: the node takes LowState.imu_state's quaternion and accelerometer as reported and its gyroscope through the export's low-pass (timed by the LowState tick), untrimmed, without /livox/imu or FAST-LIO's attitude. Other exports keep the MID-360 path. - Observations: each actor's vector is built from the export's legs_obs_terms / arms_obs_terms, any of the controller's terms left out in its order (the new legs drop base_lin_acc, arm_goal and ee_targets: 79; ArmsOnly's arms drop the IMU, command and gait clock: 108). Unknown or reordered terms are refused. - arm_ik (mdp.IKPostureArmAction, LocoManip-ArmsOnly-v0 and -Marl-Direct-v0): seed from arm_seed_table.npz's nearest row, solved for the goal, once per goal; the synchronized trajectory from the target's own last value; the arms' gravity torque over kp; the pose-error integral; the integrated, freezing residual. Pinocchio gravity torques and seed solve in kinematics.py. Matches Locomanipulation_game's numpy reference (mujoco_sim) to 1.4e-8 rad with shared seeds; independently solved seeds differ by up to 5e-4 rad (training's float32 rotation error). - arm_goal_frame pelvis (goals ride on the pelvis, no odometry) and arm_goal_keeps_walking (the velocity command live through an arm goal), as LocoManip-Marl-Direct-v0 trains them; export.yaml's residual_cutoff_hz over the template's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015EG7pDM5uvsCpuEnXVWvMd
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
LegsEnergyDefault200k_s43 failed its first real engage on 2026-11-20. Locomanipulation_game's response (
main, ecaa375 and 16ec2c6) retrains every task: it engages from the real pre-pose range, reads the torso IMU as /lowstate reports it, and drops the accelerometer. This PR makes lmg_deploy run those exports. The policy shipped inpolicies/h12is unchanged and still loads; no new policy is shipped yet, since its training is still running.What changes
The /lowstate IMU. An export with
imu.source: lowstateis read fromLowState.imu_state:imu.gyro_lowpass_hz, sampled at every /lowstate and timed by itstick;imu_offset_*are ignored), and no wait for/livox/imuor FAST-LIO's attitude.The policy trained on the quaternion's measured bias, drawn per episode: pitch -3.6 to -2.0 deg, roll -0.6 to 0.4. Exports without
source: lowstatekeep the MID-360 path as before.Any observation layout. Each actor's vector is built from the export's
legs_obs_terms/arms_obs_terms. Any of the controller's terms may be left out, in its order; unknown or reordered terms are refused.base_lin_acc,arm_goaloree_targets(79 inputs).The arms' trajectory action (
arm_ik), ported frommdp.IKPostureArmActionfor LocoManip-ArmsOnly-v0 and the game task:arm_seed_table.npz's nearest row, solved for the goal, once per goal;Gravity torques and the seed solve use Pinocchio (
kinematics.py).reset()starts the target at the measured arm angles, as training's action term does.Game-task goals.
arm_goal_frame: pelviskeeps the goal on the pelvis (no SLAM odometry moves it).arm_goal_keeps_walking: truekeeps the velocity command live through an arm goal. Both match how LocoManip-Marl-Direct-v0 now trains.Residual cutoff.
export.yaml'sresidual_cutoff_hznow takes precedence over the template's.Checks
lmg_deploytests (golem_ros container)arm_ik, pelvis-frame goalsdeploy_parity.py: this controller vs the training env in Isaac, a LegsOnly torso-IMU export, 300 stepsarm_ikpath vs Locomanipulation_game's numpy reference (mujoco_sim.process_actions), a LocoManip-Marl-Direct-v0 export, 4 x 300 stepsIndependently solved seeds differ from training's by up to 5e-4 rad. Training's float32 rotation error zeroes errors below about 1e-3 rad, so this cannot match exactly. Through the integral, the worst target difference is 5.3e-3 rad.
Known limits
🤖 Generated with Claude Code
https://claude.ai/code/session_015EG7pDM5uvsCpuEnXVWvMd