Gyroscope Bias Estimation - Unnecessary Max Operation#462
Closed
alainschoebi wants to merge 1 commit into
Closed
Conversation
|
Thanks @alainschoebi for your pull request! Changes LGTM. I ticket has been created to test your changes and merge as soon as we're able to do it internally. |
Author
|
Hi, Thanks, @arilow. Do you have any updates on this? It appears that the merge has failed. Best regards, |
|
Your proposed changes have been already internally merged and will be included in the next release. Thanks for contributing to Cardboard! |
Member
|
This was merged in v1.26.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This pull request removes an unnecessary
std::maxoperation in the gyroscope bias estimation code. This improves code readability and efficiency without impacting the functionality of the algorithm.Description
The targeted code block checks if the gyroscope sample's norm exceeds a threshold (
kGyroscopeForBiasThreshold). If it does, the function exits early; otherwise, it computes an update weight.Here is the code block:
For the
std::maxoperation to pick0.0fover1.0f - gyroscope_sample_norm2 / kGyroscopeForBiasThreshold, we needwhich implies that
However, this cannot occur due to the previous if-statement
if (gyroscope_sample_norm2 >= kGyroscopeForBiasThreshold), which would exit the function before reaching this point.This suggests that the max operation is unnecessary here and can be omitted for code readability and efficiency.