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.
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
Distortion normalization improvement + fix "folding" on large distortions #3009
Distortion normalization improvement + fix "folding" on large distortions #3009
Changes from 18 commits
9a3e7f8
ed7a417
ba51bac
8a95b8d
eb4df36
77bb479
4a6781f
bc4fd70
519e6b4
f230f56
774bab3
4fe9c4b
406b65e
b70d927
0d4980d
861f8eb
5de3259
b0b627b
fa809d5
4fa5f30
d291950
1c821cb
fd01e14
c31c97e
3caa105
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this logic block looks new. should we add
&& !this->dataPtr->legacyMode
to the if statement? or we could reverse it:if not, then we should clarify that this is a bug fix that applies in all cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be considered a bug fix, since there will be the wrapping behavior shown in #3009 (comment) on very large barrel distortions with the legacy method.
I'm not sure what would be the best place to mention this. I can alter the PR to mention the bug fix and add a comment in this part of the code. Anywhere else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a comment in the code (below) and modified the PR title and description. https://github.com/osrf/gazebo/blob/406b65e634b3ee6d45ffbd6f77d136caa048ca3a/gazebo/rendering/Distortion.cc#L240-L243
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this breaks ABI?
ABI checker didn't show any issue here but I'm not sure if that's because it's not testing the
ServerFixture
library.Also add
\param[in]
for_horizontalFov
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering the same thing, but we only distribute
ServerFixture
in a static library, and I believe ABI is only a concern for dynamically loaded libraries