-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
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
Skip ungenerated FT IMU frames in the simmechanics model for 2-5_plus models #114
Comments
I wouldn't go for that solution (2 While the
|
As as side note, it is the same situation with the XSENS IMU sensor I would say. The frame |
I think I accidentally deleted |
I agree with @nunoguedelha suggestion to use custom params to avoid mantaining to |
custom params added to CMakeLists.txt in #113. |
Was this fixed by #114 @prashanthr05 @nunoguedelha ? |
This was fixed by adding the custom which was set empty for ICUB_2-5_plus models and set relevantly for ICUB_2-5 models |
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 #113 (comment)
The text was updated successfully, but these errors were encountered: