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

Add RPM Debug with common scaling #277

Merged
merged 1 commit into from
Mar 1, 2019
Merged

Conversation

Cleric-K
Copy link
Contributor

Related to #196

It is useful to have the RPM traces on the same graph, because we can compare actual motor outputs when the same commands are given.

Curve scaling is implemented that calculates min/max over all four debug traces.

RPM debug traces' curve min/max are calculated over all four debug
fields. Thus when they are displayed on the same graph, they use
the same scale.
@mikeller mikeller added this to the 3.3.0 milestone Feb 28, 2019
@McGiverGim
Copy link
Member

The only problem here is that we calculate the min/max values four times, one for each debug, but I think we can live with it.

@Cleric-K
Copy link
Contributor Author

Cleric-K commented Mar 1, 2019

Yes, I was thinking of it also, but otherwise it would require some additional "caching" structures to see if the min max were already calculated, which I think would add more complexity to the code as a whole.

These scales are only calculated when changing graphs, so there's no practical performance penalty.

But if you think that such practice goes against the codelines of the project I can think of some caching mechanism.

@McGiverGim
Copy link
Member

No, It was only a comment. As it is, is good enough. I will not change nothing.

@mikeller mikeller merged commit bad27ec into betaflight:master Mar 1, 2019
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

Successfully merging this pull request may close these issues.

3 participants