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 SpatialInertia::shift() method does not work correctly for a SpatialInertia with a non-zero COM offset. This method is used in calcCompositeBodyInertias() and related methods so those are also wrong. Neither of these is commonly used.
The problem was reported for Simbody 3.5.1 by Gordon Deane in this forum post.
There was a regression test for this but it had a zero COM offset so didn't detect the bug; that should be changed.
The text was updated successfully, but these errors were encountered:
…so broke composite body inertias.
Added a regression test for SpatialInertia.
Improved composite body inertia regression to use non-zero COM offset.
Added comments clarifying that the ArticulatedInertia::shift() method actually shifts by the *negative* of the given vector.
…so broke composite body inertias.
Added a regression test for SpatialInertia.
Improved composite body inertia regression to use non-zero COM offset.
Added comments clarifying that the ArticulatedInertia::shift() method actually shifts by the *negative* of the given vector.
(cherry picked from commit 934cbc7)
…so broke composite body inertias.
Added a regression test for SpatialInertia.
Improved composite body inertia regression to use non-zero COM offset.
Added comments clarifying that the ArticulatedInertia::shift() method actually shifts by the *negative* of the given vector.
(cherry picked from commit 934cbc7)
The
SpatialInertia::shift()
method does not work correctly for aSpatialInertia
with a non-zero COM offset. This method is used incalcCompositeBodyInertias()
and related methods so those are also wrong. Neither of these is commonly used.The problem was reported for Simbody 3.5.1 by Gordon Deane in this forum post.
There was a regression test for this but it had a zero COM offset so didn't detect the bug; that should be changed.
The text was updated successfully, but these errors were encountered: