Change FT sensors names for compatibility with icub-models >= 2.0.0 and robots-configuration >= 2.5.0 (take two) #172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revised version of #171 after reviews from @HosameldinMohamed .
Fix robotology/icub-models-generator#242 .
icub-models 2.0.0 changed the name of the FT sensors in the URDF from being named
<identifier>_ft_sensor
(likel_arm_ft_sensor
,l_leg_ft_sensor
, ...) to<identifier>_ft
(likel_arm_ft
,l_leg_ft
, ...).However, the yarprobotinterface configuration files continued to refer to the sensors as
<identifier>_ft_sensor
, creating errors for software that was trying to match sensors find in URDF and sensors as exposed by the YARP's multipleanalogsensorsserver device.This PR changes all the instances of iCub configuration files to
<identifier>_ft
, restoring compatibility with icub-models 2.0.0, robots-configuration releases >= 2.5.0 and ergocub-software >= 0.3.4, see robotology/robots-configuration#562 .Note that the name of the joint to which the sensor is attached remained
<identifier>_ft_sensor
, both before and after icub-models 2.0.0 release.