AndyZe
AndyZe
> Since most projects just use one controller per set of joints, it's probably acceptable to replace the TEM's controller search logic with some simple condition, like picking the first...
Found some info [here](https://community.atlassian.com/t5/Pipelines-articles/Pipelines-runtime-v2-rollout-updates-amp-known-issues/ba-p/2865254). Apparently this is due to a bitbucket upgrade. > The docker run --init command is currently not supported. If you attempt to use this parameter with...
I'd say that either the sign on your gains is incorrect, for example `/servo_server/x_proportional_gain` should be -1.5, or one of the frames is incorrect.
Try increasing these 2 parameters: ``` lower_singularity_threshold: 17 # Start decelerating when the condition number hits this (close to singularity) hard_stop_singularity_threshold: 30 ```
I took care of srdfdom: https://github.com/ros-planning/srdfdom/pull/108
I'm moderately opposed to the move because I think it's too early to declare MTC as the right solution for task-planning-like things (I know it's not really a task planner)....
I don't have merge power here
Well, there's nothing to do yet. This is a reminder for later.
Can't you fill the `displacements` field in the JointJog message? https://github.com/ros-controls/control_msgs/blob/master/control_msgs/msg/JointJog.msg The tutorial mentions this, except the tutorial fills the `velocities` field rather than `displacements`. https://moveit.picknik.ai/main/doc/examples/realtime_servo/realtime_servo_tutorial.html
Sorry, I think @ChrisThrasher is already working on it :/