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
[WARNING] wholeBodyDynamics: estimateVelocityAccelerationOptionName bool parameter missing, please specify it.";
[WARNING] wholeBodyDynamics: setting estimateVelocityAccelerationOptionName to the default value of true, but this is a deprecated behaviour that will be removed in the future.";
that was surprising for me, as I based the test introduced in robotology/whole-body-estimators#177 on the configurations of ergoCubSN00* . Indeed, by looking in the configuration files for ergoCubSN00*, I noticed that the estimateJointVelocityAcceleration option is never set (the error refers to a different name, but it is a typo).
This means that for ergoCubSN00 torque estimation we never used the velocity estimated at low level, but always the velocity estimated at high level with a kalman filter.*
I guess we should get rid of this warning by explicitly setting estimateJointVelocityAcceleration (as done for iCub3 in
While working on robotology/whole-body-estimators#194 , I noticed that the test was printing a warning:
that was surprising for me, as I based the test introduced in robotology/whole-body-estimators#177 on the configurations of ergoCubSN00* . Indeed, by looking in the configuration files for ergoCubSN00*, I noticed that the
estimateJointVelocityAcceleration
option is never set (the error refers to a different name, but it is a typo).This means that for ergoCubSN00 torque estimation we never used the velocity estimated at low level, but always the velocity estimated at high level with a kalman filter.*
I guess we should get rid of this warning by explicitly setting
estimateJointVelocityAcceleration
(as done for iCub3 inrobots-configuration/robots-icebox/iCubGenova09/estimators/wholebodydynamics.xml
Line 23 in 8883a01
fyi @GiulioRomualdi @isorrentino @LoreMoretti
The text was updated successfully, but these errors were encountered: