Skip to content
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

Use of MTRX #56

Closed
dchannin opened this issue Apr 20, 2019 · 2 comments
Closed

Use of MTRX #56

dchannin opened this issue Apr 20, 2019 · 2 comments

Comments

@dchannin
Copy link

Hello,

Am I correct that when MTRX is present, it should be used as a 3x3 matrix to re-orient the ACCL data?

Thank you,
Dave

@dnewman-gpsw
Copy link
Collaborator

Yes, optionally. The plan is to have the GPMF_ScaledData() call apply all the SCAL and MTRX manipulations automatically (only only does scale currently.) MTRX, ORIN and ORIO all can be used. MRTX might eventually carry the calibration for the orientation, that is why it is an array of floats, but it doesn't today. ORIN - describes the stored (input) orientation, ORIO is the recommended output orientation (which will match HERO5 for consistency.) In HERO7 we have:
"ORIN": "YxZ",
"ORIO": "ZXY",

lower case indicates a sign reversal.
The above means:
outACCL[0] = inACCL[2];
outACCL[1] = -inACCL[1];
outACCL[2] = inACCL[0];

@dchannin
Copy link
Author

Thank you. I am running my own Python code so I do the SCAL and MTRX myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants