We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When reading data via the yarp::dev::IThreeAxisLinearAccelerometers and yarp::dev::IThreeAxisGyroscopes interfaces, we can directly use the getThreeAxisLinearAccelerometerFrameName and getThreeAxisGyroscopeFrameName methods to get the name of the frame in which sensors are expressed, we do not need anymore to manually mantain the imuFrameName parameter that is error prone (see icub-tech-iit/ergocub-software#221 (comment) and robotology/robots-configuration#614).
yarp::dev::IThreeAxisLinearAccelerometers
yarp::dev::IThreeAxisGyroscopes
getThreeAxisLinearAccelerometerFrameName
getThreeAxisGyroscopeFrameName
imuFrameName
The text was updated successfully, but these errors were encountered:
wholebodydynamics
No branches or pull requests
When reading data via the
yarp::dev::IThreeAxisLinearAccelerometersandyarp::dev::IThreeAxisGyroscopesinterfaces, we can directly use thegetThreeAxisLinearAccelerometerFrameNameandgetThreeAxisGyroscopeFrameNamemethods to get the name of the frame in which sensors are expressed, we do not need anymore to manually mantain theimuFrameNameparameter that is error prone (see icub-tech-iit/ergocub-software#221 (comment) and robotology/robots-configuration#614).The text was updated successfully, but these errors were encountered: