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

How should the measurement field names be in comparison with state field names? #67

Open
tugrul512bit opened this issue Jun 15, 2023 · 0 comments

Comments

@tugrul512bit
Copy link

For example, when there is a single measurement of orientation (a quaternion) and if states to be handled by the library are quaternion (as pan, tilt, roll), velocity of quaternion (as velocity of pan, tilt, roll), acceleration of quaternion, then should the fields be named like:

  • measurement: MyQuaternion
  • state: MyQuaternion, MyQuaternionVel, MyQuaternionAcc

or different than measurement:

  • state: MyQuaternionState, MyQuaternionVel, ...

How does library connect the updates between measurement and states? Does naming become an issue?

Does it have tools to differentiate a quaternion to compute velocity / acceleration or user has to compute it?

Is there a minimal example to use for such a scenario?

Thank you for your time.

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

1 participant