idyntree
idyntree copied to clipboard
Multibody Dynamics Library designed for Free Floating Robots
For example using the `WINDOWS_EXPORT_ALL_SYMBOLS` target option, see https://cmake.org/cmake/help/v3.4/variable/CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS.html#variable:CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS .
Hello iDyntree people, I think it would be beneficial to give users a simple example they can run so they have an idea of how much time each function cost...
In particular, `ENABLE_COMPATIBILITY_VARS` and `TARGETS_PROPERTY` should not be used anymore.
Currently in BERDY is using internally sensors defined as [`BerdySensorTypes`](https://github.com/robotology/idyntree/blob/devel/src/estimation/include/iDynTree/Estimation/BerdyHelper.h#L118). Those sensor types can be be: - copy of [`iDynTree::sensorsType`](https://github.com/robotology/idyntree/blob/devel/src/sensors/include/iDynTree/Sensors/Sensors.h#L35) ``` SIX_AXIS_FORCE_TORQUE_SENSOR = SIX_AXIS_FORCE_TORQUE, ACCELEROMETER_SENSOR = ACCELEROMETER, GYROSCOPE_SENSOR = GYROSCOPE,...
See related PR https://github.com/robotology/idyntree/pull/259 .
When using the floating type of joint in the URDF model iDyntree gives the following errors ``` [ERROR] JointElement :: setAttributes : Joint world_to_robot has type floating that is not...
For some reason, it seems that the `BerdyHelper::getDynamicVariablesOrdering()` method is not tested, and it may be bugged when berdyVariant is `BERDY_FLOATING_BASE` . The test present here: https://github.com/robotology/idyntree/blob/3fc1206dc5b8dfa5cd6b11f195ad5b7568ef771e/src/estimation/tests/BerdyHelperUnitTest.cpp#L158 should work fine...
This issue aims at adding a new COM_ACCELEROMETER_SENSOR berdy sensor to the berdy helper class. This sensor lets us add additional constraint on the estimation of dynamic variables. Additional details...
Any way we can have a demo on how to use/get/read/dostuff with the collision and visual elements ? _Originally posted by @ahoarau in https://github.com/robotology/idyntree/issues/496#issuecomment-524758603_
This was a functionality available in the old KDL-based iDynTree, but that was never ported to the new standalone iDynTree. Related issues and previous PRs: * https://github.com/robotology/idyntree/issues/161 * https://github.com/robotology/idyntree/pull/382