Closed Penguuuuin closed 1 year ago
This seems like a bug introduced after v1.1. There was a big change in the computation pipeline and probably some variables needed to compute the angular momentum are not computed. I'll push a fix to this soon
Thanks for you prompt reply! So do I calculate angular momentum right?
Yes, that looks correct. The angular momentum function is unit-tested (but only after the massMatrix call)
I need to calculate the angular momentum of a walking humanoid robot and find out the function getAngularMomentum(), but it seems doesn't get a reasonable result when I directly call it like this: and the pic of angular momentum data gathered like this. The value of the data fluctuates and increases and it's impossible for a stable walking robot.
Then I find that if calls getMassMatrix() before getAngularMomentum(), the gathered data become reasonable.
Why it happens? Is getMassMatrix() calls other function to update any internal value? Or if I need to call any other functions such as updateMassInfo() to manually update something?