-
Notifications
You must be signed in to change notification settings - Fork 199
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
Pr 190 merge resolved #207
Conversation
…ntroller (ros-controls#190) (cherry picked from commit f43fa8a) # Conflicts: # README.md # ros2_control_demo_bringup/launch/rrbot.launch.py # ros2_control_demo_bringup/launch/rrbot_base.launch.py
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.
Thanks! We should do a switch here. Can you do that?
@@ -32,8 +32,8 @@ def generate_launch_description(): | |||
[ | |||
Node( | |||
package="ros2_control_test_nodes", | |||
executable="publisher_joint_trajectory_controller", | |||
name="publisher_joint_trajectory_controller", | |||
executable="publisher_joint_trajectory_position_controller", |
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.
We should here switch to ros2_controllers_test_nodes
from ros2_controllers repository. Can you do that, please?
I am not sure if I would continue with this change. Personally, find a very nice and descriptive example that the controller name is different than the type. The controller name should be rather descriptive and not correspond to its type. |
After merging #232 this is obsolete. |
Hello,
this MR resolved the mergify conflicts from #198
Best,
Haider