-
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
Rotation matrices in dataframes #21
Comments
I'm not sure I follow; do you want to allow passing in both a What I meant was more that we should keep the |
Okay so two main points:
Together this makes the overhead a little higher than I would like for understanding/working with the data structure I'm suggesting:
|
I'm not a big fan of Yet Another Euler Angles Convention to deal with, but I see your points. I love working with Rotations, but originally I thought that getting them in or out of dataframes would be less tedious, and it's not... So yeah, I think I'm ok with the change! |
sweet! will leave this open and update the spec when I can, cheers! |
Came up in discussion of #20 with @brisvag
I like the pattern used there of providing a utility function for generating the projection matrices rather than attempting to store them on the dataframe itself where they don't fit naturally
What do you think about using a similar pattern of using a utility function for generating the
Rotation
representation from a standard rep in the dataframe?We should still have the constructor take in a
Rotation
object and deal with unstacking, this would get rid of the need for people to understand quite so much about theRotation
API and more easily follow its docs which don't deal with 'how to shove this thing into a dataframe' at allThe text was updated successfully, but these errors were encountered: