-
Notifications
You must be signed in to change notification settings - Fork 938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[jog_arm] SRDF velocity and acceleration limit enforcement #1863
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1863 +/- ##
==========================================
- Coverage 50.28% 50.21% -0.08%
==========================================
Files 313 313
Lines 24647 24692 +45
==========================================
+ Hits 12394 12398 +4
- Misses 12253 12294 +41
Continue to review full report at Codecov.
|
@AndyZe Please rebase |
@@ -142,7 +143,7 @@ class JogCalcs | |||
|
|||
robot_state::RobotStatePtr kinematic_state_; | |||
|
|||
sensor_msgs::JointState joint_state_, original_joint_state_; | |||
sensor_msgs::JointState incoming_joint_state_, internal_joint_state_, original_joint_state_; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the internal_joint_state_
correspond to a "current" joint state?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I mean is that it's used in calculations, it shouldn't be relied on to be accurate. Would there be a better way to say that?
I'm gonna try to get this list down to 2. It seems like incoming_joint_state_ and original_joint_state_ should be the same thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It turns out that original_joint_state_
is a little bit different from incoming_joint_state_
so I left a comment to explain it. incoming_joint_state_
has every joint, but passive joints might get dropped from original_joint_state_
Add a placeholder test for vel/accel limits
The test that was added (test_vel_accel_limits.py) will make more sense when I can check for specific error codes. For now, it's just a placeholder. PR #1915 adds the error codes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this and it works without any issues for me
* Loosen timing-based test tolerances * Rename and comment joint_state variables better * Add a placeholder test for vel/accel limits * Remove useless update of kinematic_state_ * Fix suddenHalt() * Improve Python integration tests
* Loosen timing-based test tolerances * Rename and comment joint_state variables better * Add a placeholder test for vel/accel limits * Remove useless update of kinematic_state_ * Fix suddenHalt() * Improve Python integration tests
* Loosen timing-based test tolerances * Rename and comment joint_state variables better * Add a placeholder test for vel/accel limits * Remove useless update of kinematic_state_ * Fix suddenHalt() * Improve Python integration tests
Read velocity and acceleration limits from the SRDF and enforce them