-
Notifications
You must be signed in to change notification settings - Fork 2
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
Link Wrench Estimation #11
Comments
Any update on this @traversaro? Can I maybe help somehow? |
c.c. @rbonghi This is the issue I was telling you about. We have to wait for @traversaro to fix/add this in the yarp-WholeBodyInterface. |
Sorry guys, at the moment is a bit difficult to find the time to implement this, unless it is a top priority. |
All stakeholders interested in this feature (cc @rbonghi @DanielePucci ) can provide a description of what they would expect from this block (considering frame of expression issues and other technicalities)? |
So, as you mentioned in robotology-legacy/codyco-modules#39, the method get(ESTIMATE_EXTERNAL_FORCE_TORQUE, fake_link) should return the force/torque expressed w.r.t. the fake_link, that is, point = origin of the fake_link, orientation = orientation of the fake_link. In the case "fake_link" is a "real link", the method should return the force/torque expressed w.r.t. it. What do you think @traversaro ? |
So do you like the |
No sorry, I confused fake_frame with a sort of additional frame. I think that the method should be something like get(ESTIMATE_EXTERNAL_FORCE_TORQUE, frame) and then it returns the force/torque expressed w.r.t. "frame". Probably, in most control applications, the orientation of this frame is going to be kept equal to that of the world frame, thus being consistent with velocities. |
Sorry, how the |
? |
Sorry guys I can start working on this just tomorrow... you know why. |
@francesco-romano The |
@traversaro from the simulink point of view: |
+1 . Actually the frame of expression is quite prone to misunderstanding: when you mean wrench expressed in a frame (for example the world frame) you refer to both the point of expression and the orientation. For now (for example the jacobians and the velocities estimates) we are assuming (and the user can't change this, for now, at least at the WBI/WBI-Toolbox level) that the point of expression is the one of the frame, while the orientation is the one of the world/inertial. For this reason it may be more useful to specify both the point of expression and the orientation of the requested estimate. |
any update on this? This block seems to be necessary for dealing with compliant contacts. |
Hi @azadm , reading the estimate of the external wrench is definitely important at the moment. |
Still pending for Version 0.2
The text was updated successfully, but these errors were encountered: