Closed prashanthr05 closed 4 years ago
I wouldn't go for that solution (2 yaml
option files) to avoid duplicating information while keeping things simple enough.
icub2_5/ICUB_2-5_plus_BB_SIM_MODEL.xml
model is not properly updated...We can add the parameters related to the FT-IMU via the CMakeLists.txt
as it was done through the cmake variables @XSENS_IMU_FRAME@
, @XSENS_IMU_SENSOR@
and using the condition tag GIVTWO_ICUB_PLUS
:
https://github.com/robotology/icub-model-generator/blob/bada6e53f0c874d80812a0b3cd146145d1ea85c9/simmechanics/CMakeLists.txt#L131-L142
icub2_5/ICUB_2-5_plus_BB_SIM_MODEL.xml
model update...The FT-IMU frames are useful when the FT sensors are equipped with the strain2 boards, but when the FT sensors still have the old strain boards, having those IMU frames in the model does not pose a problem. Anyway, this is independent from the additional features integrated in the cub2.5plus model (inclined soles, XSENS IMU sensor).
So icub2_5/ICUB_2-5_plus_BB_SIM_MODEL.xml
should be updated with those FT-IMU frames, unless we decide to drop that model all-together, which is another discussion.
CC @traversaro @fjandrad
As as side note, it is the same situation with the XSENS IMU sensor I would say. The frame SCSYS_ROOT_LINK_XSENS_IMU
should be present in both models icub2_5/ICUB_2-5_plus_BB_SIM_MODEL.xml
and icub2_5/ICUB_2-5_BB_SIM_MODEL.xml
so the later should be updated.
I think I accidentally deleted @XSENS_IMU_FRAME@
from the yaml file. I will add it.
I agree with @nunoguedelha suggestion to use custom params to avoid mantaining to .yml
files. Eventually if the 2.5+ model gets regenerate, we could probably avoid to have to deal with this additional parameter.
I agree with @nunoguedelha suggestion to use custom params to avoid mantaining to
.yml
files. Eventually if the 2.5+ model gets regenerate, we could probably avoid to have to deal with this additional parameter.
custom params added to CMakeLists.txt in https://github.com/robotology/icub-model-generator/pull/113.
Was this fixed by https://github.com/robotology/icub-model-generator/issues/114 @prashanthr05 @nunoguedelha ?
This was fixed by adding the custom @FT_IMU_SENSORS@
param to https://github.com/robotology/icub-model-generator/blob/9f6dbe7ab98c4a4762317e2c9aacb298ffe39c53/simmechanics/data/icub2_5/ICUB_2-5_BB_simmechanics_options.yaml.in#L923
which was set empty for ICUB_2-5_plus models
and set relevantly for ICUB_2-5 models https://github.com/robotology/icub-model-generator/blob/9f6dbe7ab98c4a4762317e2c9aacb298ffe39c53/simmechanics/CMakeLists.txt#L177
Ok, so we can close this issue?
I renamed the issue to be more meaningful. We can close it.
Thanks!
Just to complete the info:
The
ICUB_2-5_plus_BB_SIM_MODEL.xml
do not have the FT IMU frames generated. This causes errors while trying to add the FT IMU frames in theICUB_2-5_BB_simmechanics_options.yaml.in
fileWhile compiling, I get this error:
REASON
The IMU frames have not been generated in the
icub2_5/ICUB_2-5_plus_BB_SIM_MODEL.xml
and in the options fileicub2_5/ICUB_2-5_BB_simmechanics_options.yaml.in
, we are asking thefirstgen.py
parser to add the IMU sensors by accessing the relevant frame names in the generated sim mechanics file.WORKAROUND
To test if the changes in the PR are passing, I commented out the macro in
generate_icub_simmechanics
that uses theicub2_5/ICUB_2-5_plus_BB_SIM_MODEL.xml
. With this change, the compilation succeeds.Maybe a proper fix could be to maintain two yaml option files, one for
ICUB_2-5_plus_BB_SIM_MODEL.xml
and another forICUB_2-5_BB_SIM_MODEL.xml
.Any suggestions @nunoguedelha @fiorisi ?
Originally posted by @prashanthr05 in https://github.com/robotology/icub-model-generator/pull/113#issuecomment-519510998