Getting inertia tensor of the human in a different basis

[chrisdembia]

-We talked about how nice it would be to have an inertia(about=None, in_frame=None) method where the user can get the inertia dyadic about some other frame etc.

-We also want the user to be able to transform the inertia tensor in the GUI, so the user provides a point and a rotation matrix used to transform the inertia tensor in the GUI.

-There's a separate issue of using the current visualization in one's other visualization. So combining yeadon library draw_mayavi() as part of some other code. We could either AVOID modifying yeadon at all, and just set transformations in mayavi itself, but then what does the inertia tensor represent? How do we know its rotation?

[chrisdembia]

Get rid of existing transform/translate/rotate methods. Worry about what this means for rendering for later releases.

[moorepants]

Can we leave the methods in place for 1.0? And depreciate them later. This is mainly because I use them in the BicycleParameters package and would like that not to break with the 1.0 release unless we have some alternative.

[chrisdembia]

That sounds fine.

On Sun, Jun 16, 2013 at 11:13 PM, Jason Moore [email protected]:

Can we leave the methods in place for 1.0? And depreciate them later. This
is mainly because I use them in the BicycleParameters package and would
like that not to break with the 1.0 release unless we have some alternative.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-19527758
.

[chrisdembia]

Okay just need to finish the test for this now.

[chrisdembia]

Tested in d65191a

[chrisdembia]

Okay it's still an issue, but we did what we wanted for the 1.0 milestone.

[moorepants]

Should this be closed with the inertia_transformed method being introduced?

[chrisdembia]

Perhaps we need to clarify the further work we want to do with transforming inertia. There should still be issues for:

• getting rid of old transform methods that are currently hidden?
• transforming the global reference frame, for visualization purposes (visualizing with a bike, for example)

unless we no longer want that functionality.

[moorepants]

We can use some deprecation warnings for the old methods. And I'm not sure we need the other functionality. I added a bike just fine in the example notebook. You just have to draw everything in the Yeadon coordinate system. I don't think that is that big of a deal. But maybe adding some feature to rotate the global axes could be useful. Doesn't seem like a necessity though.