Fix Jaco gripper force/torque sensor readings - #821
Open
Battleplus wants to merge 1 commit into
Open
Conversation
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.
Summary
palmchild to theright_grippermounting bodyWhy this placement
Attaching the sensors to
grip_sitemakes the default readings zero, but that site belongs to a massless visualization-onlyeefbody and does not measure the complete finger subtree. Moving the existingft_frameone level up measures the complete gripper at its mounting interface while preserving its pose.With MuJoCo 3.8.0 after
mj_resetData+mj_forward:force_eemax abs3.47e170.25torque_eemax abs3.42e150.141Testing
python -m pytest tests/test_grippers/test_jaco_sensors.py -q(1 passed)black --check tests/test_grippers/test_jaco_sensors.pygit diff --checkFixes #808