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

OPTICAL_FLOW.flow_comp_m_(x/y) units to m/s #1189

Merged
merged 2 commits into from
Aug 8, 2019
Merged

Conversation

hamishwillee
Copy link
Collaborator

Fixes #1187

As stated by @jlecoeur the OPTICAL_FLOW.flow_comp_m_x and flow_comp_m_y must either be velocity units or an integration time unit is required so that flow can be determined from these. Given there is no such integration unit it is very likely that people are assuming m/s OR that it is not being used. Either way, the "best" fix is to clarify m/s.

Still waiting for confirmation on linked item from @auturgy.

Copy link
Collaborator

@julianoes julianoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know what's correct but the change itself seems fine.

@hamishwillee hamishwillee added the Dev Call Issues to be discussed during the Dev Call label Aug 5, 2019
@hamishwillee
Copy link
Collaborator Author

Discussed in dev call. Agreed that code for implementation of this message is velocity. Can be merged.

@julianoes julianoes merged commit c3700e9 into master Aug 8, 2019
@julianoes julianoes deleted the pr_OPTICAL_FLOW branch August 8, 2019 07:53
amilcarlucas pushed a commit to amilcarlucas/mavlink that referenced this pull request Sep 24, 2019
As stated by @jlecoeur the OPTICAL_FLOW.flow_comp_m_x and flow_comp_m_y must either be velocity units or an integration time unit is required so that flow can be determined from these. Given there is no such integration unit it is very likely that people are assuming m/s OR that it is not being used. Either way, the "best" fix is to clarify m/s.
tridge pushed a commit to ArduPilot/mavlink that referenced this pull request Oct 8, 2019
As stated by @jlecoeur the OPTICAL_FLOW.flow_comp_m_x and flow_comp_m_y must either be velocity units or an integration time unit is required so that flow can be determined from these. Given there is no such integration unit it is very likely that people are assuming m/s OR that it is not being used. Either way, the "best" fix is to clarify m/s.
CraftyJax pushed a commit to planckaero/mavlink that referenced this pull request Nov 19, 2020
As stated by @jlecoeur the OPTICAL_FLOW.flow_comp_m_x and flow_comp_m_y must either be velocity units or an integration time unit is required so that flow can be determined from these. Given there is no such integration unit it is very likely that people are assuming m/s OR that it is not being used. Either way, the "best" fix is to clarify m/s.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev Call Issues to be discussed during the Dev Call
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify units in OPTICAL_FLOW
3 participants