[rolling] image_publisher: add field of view parameter #985
Conversation
This file contains 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
Kotochleb
changed the title
Kotochleb
changed the title
ahcorde
requested changes
May 27, 2024
Co-authored-by: Alejandro Hernández Cordero <[email protected]>
Kotochleb
force-pushed
the
feature/image-publisher-add-fov
branch
from
c9cc228
to
4762cac
Compare
Kotochleb
changed the title
|
@ahcorde the changes were retargeted to |
ahcorde
requested changes
May 27, 2024
| camera_info_.k = {1, 0, static_cast<float>(camera_info_.width / 2), 0, 1, | ||
|
|
||
| // Based on https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/ | ||
| double f_approx = (camera_info_.width / 2) / std::tan((field_of_view_ * M_PI / 180) / 2); |
There was a problem hiding this comment.
is the default value 50 returning 1 ? as the current behavior ?
There was a problem hiding this comment.
It doesn't, and I forgot to account for breaking changes. I changed it now so when FOV is 0 or less, it disables the whole feature and uses 1.0 for focal length instead. The default vale is now zero as well, so now the whole thing is not breaking anything.
ahcorde
approved these changes
May 28, 2024
|
https://github.com/Mergifyio backport jazzy humble iron |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
May 28, 2024
Currently, the default value for focal length when no camera info is provided defaults to `1.0` rendering whole approximate intrinsics and projection matrices useless. Based on [this article](https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/), I propose a better approximation of the focal length based on the field of view of the camera. For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time. If there is some documentation to fill. please let me know. This PR should be straightforward to port it to `Humble`, `Iron` and `Jazzy`. --------- Co-authored-by: Alejandro Hernández Cordero <[email protected]> (cherry picked from commit 78d80f7)
mergify bot
pushed a commit
that referenced
this pull request
May 28, 2024
Currently, the default value for focal length when no camera info is provided defaults to `1.0` rendering whole approximate intrinsics and projection matrices useless. Based on [this article](https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/), I propose a better approximation of the focal length based on the field of view of the camera. For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time. If there is some documentation to fill. please let me know. This PR should be straightforward to port it to `Humble`, `Iron` and `Jazzy`. --------- Co-authored-by: Alejandro Hernández Cordero <[email protected]> (cherry picked from commit 78d80f7) # Conflicts: # image_publisher/doc/components.rst
mergify bot
pushed a commit
that referenced
this pull request
May 28, 2024
Currently, the default value for focal length when no camera info is provided defaults to `1.0` rendering whole approximate intrinsics and projection matrices useless. Based on [this article](https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/), I propose a better approximation of the focal length based on the field of view of the camera. For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time. If there is some documentation to fill. please let me know. This PR should be straightforward to port it to `Humble`, `Iron` and `Jazzy`. --------- Co-authored-by: Alejandro Hernández Cordero <[email protected]> (cherry picked from commit 78d80f7) # Conflicts: # image_publisher/doc/components.rst
This was referenced May 28, 2024
ahcorde
pushed a commit
that referenced
this pull request
May 28, 2024
Currently, the default value for focal length when no camera info is provided defaults to `1.0` rendering whole approximate intrinsics and projection matrices useless. Based on [this article](https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/), I propose a better approximation of the focal length based on the field of view of the camera. For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time. If there is some documentation to fill. please let me know. This PR should be straightforward to port it to `Humble`, `Iron` and `Jazzy`. <hr>This is an automatic backport of pull request #985 done by [Mergify](https://mergify.com). Co-authored-by: Krzysztof Wojciechowski <[email protected]>
ahcorde
pushed a commit
that referenced
this pull request
May 28, 2024
Currently, the default value for focal length when no camera info is provided defaults to `1.0` rendering whole approximate intrinsics and projection matrices useless. Based on [this article](https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/), I propose a better approximation of the focal length based on the field of view of the camera. For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time. If there is some documentation to fill. please let me know. This PR should be straightforward to port it to `Humble`, `Iron` and `Jazzy`. <hr>This is an automatic backport of pull request #985 done by [Mergify](https://mergify.com). Co-authored-by: Krzysztof Wojciechowski <[email protected]>
mikeferguson
pushed a commit
that referenced
this pull request
Jun 10, 2024
…992) Currently, the default value for focal length when no camera info is provided defaults to `1.0` rendering whole approximate intrinsics and projection matrices useless. Based on [this article](https://learnopencv.com/approximate-focal-length-for-webcams-and-cell-phone-cameras/), I propose a better approximation of the focal length based on the field of view of the camera. For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time. If there is some documentation to fill. please let me know. This PR should be straightforward to port it to `Humble`, `Iron` and `Jazzy`. <hr>This is an automatic backport of pull request #985 done by [Mergify](https://mergify.com). Co-authored-by: Krzysztof Wojciechowski <[email protected]>
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.
Currently, the default value for focal length when no camera info is provided defaults to
1.0rendering whole approximate intrinsics and projection matrices useless. Based on this article, I propose a better approximation of the focal length based on the field of view of the camera.For most of the use cases, users will either know the field of view of the camera the used, or they already calibrated it ahead of time.
If there is some documentation to fill. please let me know.
This PR should be straightforward to port it to
Humble,IronandJazzy.