You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those links added to the urdfs are no longer necessary after #254.
In fact, for example, the ergoCub model was added and tested (#340) by using directly the original model by adding all the required fixed transforms to the configuration file (see
). Since the ergoCub model should basically have same (or similar) link definition as the iCub3 (and iCub2.5) models, starting from those transforms we should be able to get rid of the teleoperation models.
Since the ergoCub model should basically have same (or similar) link definition as the iCub3 (and iCub2.5) models, starting from those transforms we should be able to get rid of the teleoperation models.
I remember that with @GiulioRomualdi we had some issues in understanding the frame wrt which the offset was defined (the rotation part was clearer). When using the offsets of iCub3 (
The objective is to get rid of the teleoperation models found in https://github.com/robotology/human-dynamics-estimation/tree/master/conf/urdfs which are copies of the original robot urdf files (contained in https://github.com/robotology/icub-models) with the addition of fake links originally added to replicate the orientation of the sensors data.
Those links added to the urdfs are no longer necessary after #254.
In fact, for example, the
ergoCub
model was added and tested (#340) by using directly the original model by adding all the required fixed transforms to the configuration file (seehuman-dynamics-estimation/conf/xml/RobotStateProvider_ergoCub_openxr_ifeel.xml
Lines 104 to 137 in 11ad67f
ergoCub
model should basically have same (or similar) link definition as theiCub3
(andiCub2.5
) models, starting from those transforms we should be able to get rid of the teleoperation models.cc @mebbaid @S-Dafarra
The text was updated successfully, but these errors were encountered: