Skip to content
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

Set controller names in Demo pick and place task #582

Closed
wants to merge 5 commits into from

Conversation

MarqRazz
Copy link

@MarqRazz MarqRazz commented Jun 3, 2024

To remove the following warnings when running the Demo Pick and Place task we need to specify the controllers the task should use.

[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.106751682]: The trajectory of stage '4' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.106813314]: The trajectory of stage '5' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.106851123]: The trajectory of stage '7' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.106876960]: The trajectory of stage '11' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.106931256]: The trajectory of stage '14' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.106975585]: The trajectory of stage '16' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.107018325]: The trajectory of stage '18' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.107050142]: The trajectory of stage '21' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.107091647]: The trajectory of stage '24' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.
[move_group-4] [moveit_task_constructor_visualization.execute_task_solution 1717427532.107175876]: The trajectory of stage '25' from task '' does not have any controllers specified for trajectory execution. This might lead to unexpected controller selection.

rhaschke and others added 5 commits May 26, 2024 12:55
Looks like Rolling's MoveIt uses a more relaxed goal constraint threshold than Humble.
For this reason, all end states reached by Connect solutions of pick+place demo are rejected.
This commit relaxes the max_distance threshold of Connect accordingly.
- Unify move_to.launch.py and test_task_model.launch.py
- Rename them to test.launch.py as they are independent of the executable
- Move Node creation to the fixture constructor
- Replace Task::setRobotModel(loadModel()) with Task::loadRobotModel()
Using quick_exit instead of return/exit avoids calling all cleanup functions,
which fail due to a bug in rmw_fastrtps_cpp.
@rhaschke
Copy link
Contributor

rhaschke commented Jun 4, 2024

This warning was not introduced by me and I think it is not well-motivated. Your PR looks good to fix those. However, please target the ros2 branch.

@MarqRazz
Copy link
Author

MarqRazz commented Jun 4, 2024

If the joints of motion can be executed by multiple controllers (i.e. position, position with compliance, torque) how do you tell MoveIt which one it should use to execute?

@rhaschke
Copy link
Contributor

rhaschke commented Jun 5, 2024

Often, there is only one controller applicable. Also, we have defaults as far as I remember. The warning should actually only trigger when there is ambiguity.

@MarqRazz MarqRazz force-pushed the set_traj_exec_info branch from 12fd10f to edf2605 Compare June 5, 2024 12:45
@MarqRazz
Copy link
Author

MarqRazz commented Jun 5, 2024

Sorry that rebase didn't go as expected.

I'll get this cleaned up and tested the ros2 branch. Is that targeting ROLLING?

@MarqRazz MarqRazz closed this Jun 5, 2024
@MarqRazz MarqRazz deleted the set_traj_exec_info branch June 5, 2024 13:03
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.

3 participants