Skip to content

Increase cartesian planning timeout to accommodate slower machines#9

Closed
nikkijhart wants to merge 2 commits intohumble-develfrom
humble-feature/cartesian-fix
Closed

Increase cartesian planning timeout to accommodate slower machines#9
nikkijhart wants to merge 2 commits intohumble-develfrom
humble-feature/cartesian-fix

Conversation

@nikkijhart
Copy link
Collaborator

Fix for NASA-JSC-Robotics/clr_sim_demos#2. Hopefully this doesn't impact those with faster machines--in theory, this should be the upper limit, not the time required to plan. Maybe @eholum-nasa can test and verify?

ur_manipulator:
kinematics_solver: trac_ik_kinematics_plugin/TRAC_IKKinematicsPlugin
kinematics_solver_timeout: 0.005
kinematics_solver_timeout: 0.05
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that Trac IK in distance mode will use the full time allotment for each solve - you can follow the param down to here (I am not 100% sure so would ask you to confirm that):

https://bitbucket.org/traclabs/trac_ik/src/56136bbdbab3f323dcf7fe2bb30e31ed4502cba8/trac_ik_lib/src/nlopt_ik.cpp#lines-591

So I am a bit loathe to up this across the board... But maybe it would be worth it to change these to speed?

@nikkijhart
Copy link
Collaborator Author

@eholum-nasa Updated timeout based on further testing

@eholum-nasa
Copy link
Member

Updated specifically for that one demo, here:

NASA-JSC-Robotics/clr_sim_demos#7

I think this is good to close.

@eholum-nasa eholum-nasa closed this Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants