diff --git a/CMakeLists.txt b/CMakeLists.txt index 3a4f883b21..16885f458f 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -3,7 +3,7 @@ cmake_minimum_required(VERSION 3.16) -project(iDynTree VERSION 14.0.1 +project(iDynTree VERSION 14.0.2 LANGUAGES C CXX) # Disable in source build, unless Eclipse is used diff --git a/doc/model_loading.md b/doc/model_loading.md index 83277ea8ee..12f217a7c3 100644 --- a/doc/model_loading.md +++ b/doc/model_loading.md @@ -17,14 +17,16 @@ Furthermore, we also use some extension to the URDF specs, as defined in the fol ### Spherical joints -The `URDF` specification do not support Spherical Joints, that instead iDynTree support. To allow to easily load and export URDF models that contain spherical joints, by default iDynTree URDF parser detect if the model contains three consecutive `revolute` or `continuous` joints with this conditions: +The `URDF` specification do not support Spherical Joints, that instead iDynTree support. To allow to easily load and export URDF models that contain spherical joints, iDynTree URDF parser exposes an option `ModelParserOptions::convertThreeRevoluteJointsToSphericalJoint` that is off by default, but if enable can detect if the model contains three consecutive `revolute` or `continuous` joints with this conditions: * The three joint axis intersect at a single point * The three joint axis are each one orthogonal to each other * The two internal links have zero mass If all these conditions are respected, the three revolute joints in the URDF model are substituted with a single iDynTree's SphericalJoint. Similarly, when a `iDynTree::Model` is exported, any `iDynTree::SphericalJoint` contained in it is exported as a three revolute joints that respect the aforementioned conditions. -To disable this behaviour that by default is enabled you can set the `ModelParserOptions::convertThreeRevoluteJointsToSphericalJoint` and `ModelExporterOptions::exportSphericalJointsAsThreeRevoluteJoints` options to `false`. +To enable this behaviour that by default is disable you can set the `ModelParserOptions::convertThreeRevoluteJointsToSphericalJoint` to true. + +The equivalent option for the URDF export, i.e. `ModelExporterOptions::exportSphericalJointsAsThreeRevoluteJoints` is by default `true`, and can be set to `false` to ensure that trying to export a `SphericalJoint` to a URDF results in a clear error. Note that this way of supporting spherical joints in URDF is compatible with the [`onshape-to-robot`'s `ball_to_euler` processor](https://onshape-to-robot.readthedocs.io/en/latest/processor_ball_to_euler.html). diff --git a/src/model_io/codecs/src/ModelLoader.cpp b/src/model_io/codecs/src/ModelLoader.cpp index f5be04f378..40c9ac1004 100644 --- a/src/model_io/codecs/src/ModelLoader.cpp +++ b/src/model_io/codecs/src/ModelLoader.cpp @@ -17,7 +17,7 @@ namespace iDynTree ModelParserOptions::ModelParserOptions() : addSensorFramesAsAdditionalFrames(true) , originalFilename("") - , convertThreeRevoluteJointsToSphericalJoint(true) + , convertThreeRevoluteJointsToSphericalJoint(false) , sphericalJointZeroMassTolerance(1e-6) , sphericalJointOrthogonalityTolerance(1e-6) , sphericalJointIntersectionTolerance(1e-6) {}