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
In many cases it may happen that some FT sensors can be offset-calibrated, while other no, and it would be convenient to just calibrate them. For example, when a humanoid robot is standing on its leg, the FT sensors on the legs cannot be offset-calibrated, while the one on the arms yes (assuming no force is excerted on the arms).
For a specific application, I implemented an hardcoded implementation of this in ac0cd22 . However, it would be good to have a model agnostic implementation. Possible way of implementing this:
O1: Define in the config file "groups" of FT sensors, and then this groups can be used as the calib_code in the RPC calls to calib*** RPC calls (see
O2: Define new calib** functions (or at least for calib, as all other calibration methods are not really relevant for the arms use case) in which the list of sensors to calibrate is explicitly passed when the RPC function is called.
In general I would prefer O1, even if it has the downside to put even more complexity in the configuration files that it is definetly something not desirable, so from that point of view O2 has the advantage that we would not need to put more complexity in the config files.
The text was updated successfully, but these errors were encountered:
In many cases it may happen that some FT sensors can be offset-calibrated, while other no, and it would be convenient to just calibrate them. For example, when a humanoid robot is standing on its leg, the FT sensors on the legs cannot be offset-calibrated, while the one on the arms yes (assuming no force is excerted on the arms).
For a specific application, I implemented an hardcoded implementation of this in ac0cd22 . However, it would be good to have a model agnostic implementation. Possible way of implementing this:
calib_code
in the RPC calls tocalib***
RPC calls (seewhole-body-estimators/idl/wholeBodyDynamics_IDLServer/wholeBodyDynamics_IDLServer.thrift
Line 18 in c46c185
calib**
functions (or at least forcalib
, as all other calibration methods are not really relevant for the arms use case) in which the list of sensors to calibrate is explicitly passed when the RPC function is called.In general I would prefer O1, even if it has the downside to put even more complexity in the configuration files that it is definetly something not desirable, so from that point of view O2 has the advantage that we would not need to put more complexity in the config files.
The text was updated successfully, but these errors were encountered: