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
The "real" iCub robot are typically launched with a yarprobotinterface that spawns, beside the YARP device that communicate with the internal robot fieldbus and the YARP network wrapper server device to expose their functionality over the network, also the device cartesiancontrollerserver and soon for supported robots also the wholebodydynamics device.
To reduce the simulation to reality gap, we could consider offering simulated models that do the same, or at least documentation on how to build such models. This was not easy in the past, but it has been enabled by the creation of the gazebo_yarp_robotinterface plugin in robotology/gazebo-yarp-plugins#532 .
Things to consider:
Such models would have more runtime dependencies then the existing ones. The existing models just depend on gazebo-yarp-plugins, the new models may depend on ICUB and whole-body-estimators, that are the repo that provide such devices. For this reason, it could make sense to make this option opt-in, rather then enabling it for all the models.
The "real" iCub robot are typically launched with a
yarprobotinterface
that spawns, beside the YARP device that communicate with the internal robot fieldbus and the YARP network wrapper server device to expose their functionality over the network, also the devicecartesiancontrollerserver
and soon for supported robots also thewholebodydynamics
device.To reduce the simulation to reality gap, we could consider offering simulated models that do the same, or at least documentation on how to build such models. This was not easy in the past, but it has been enabled by the creation of the gazebo_yarp_robotinterface plugin in robotology/gazebo-yarp-plugins#532 .
Things to consider:
gazebo_yarp_imu
andgazebo_yarp_forcetorque
as described in Ensure that all device created by plugins can specify their YARP device instance name to be used by gazebo_yarp_robotinterface gazebo-yarp-plugins#535The text was updated successfully, but these errors were encountered: