You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that those files contained a [VELOCITY_CONTROL] group that will stop working in gazebo-yarp-plugins 4 once the velocityControlImplementationType parameter, introduced in gazebo-yarp-plugins v3.5.1 https://github.com/robotology/gazebo-yarp-plugins/blob/master/CHANGELOG.md#351---2020-10-05 , will be made compulsory instead of automatically use the default value direct_velocity_pid. If those files are not mantained, why we don't just tag a release that contains them, and then remove them from the master branch of the repo?
The text was updated successfully, but these errors were encountered:
@MarcoCaianiello is currently working on those files. Indeed rather then deprecating them, we could revive it by pushing the updated, and working, configuration.
I noticed that those files contained a
[VELOCITY_CONTROL]
group that will stop working in gazebo-yarp-plugins 4 once thevelocityControlImplementationType
parameter, introduced in gazebo-yarp-plugins v3.5.1 https://github.com/robotology/gazebo-yarp-plugins/blob/master/CHANGELOG.md#351---2020-10-05 , will be made compulsory instead of automatically use the default valuedirect_velocity_pid
. If those files are not mantained, why we don't just tag a release that contains them, and then remove them from the master branch of the repo?The text was updated successfully, but these errors were encountered: