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
Need to check if all distortion coefficients are zero, not just first one #180
Comments
lucasw
added a commit
to lucasw/vimjay
that referenced
this issue
Feb 29, 2016
…ausing rectification to not be done ros-perception/image_pipeline#180
I can provide a pull request in a day or two. |
Thx, please do. And please include a test. |
A corresponding change is needed in vision_opencv to make a fix here work:
|
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 1, 2016
… a test next. Currently testing manually with vimjay image_rect.launch (which brings up an rqt gui and camera info distortion coefficients can be dynamically reconfigured.
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 1, 2016
…all_of), collapse this commit with above later.
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 6, 2016
… debug it because I can't talk to rostest master on 22422. Don't push this, rebase when solution is found
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 6, 2016
… just spinOnce.
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 6, 2016
…camera info parameters are still changing the image
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 6, 2016
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 6, 2016
Test with: rostest --reuse-master --text image_proc test_rectify.xml Can also test interactively with vimjay image_rect.launch, which brings up an rqt gui and camera info distortion coefficients can be dynamically reconfigured.
lucasw
added a commit
to lucasw/image_pipeline
that referenced
this issue
Mar 6, 2016
Test with: rostest --reuse-master --text image_proc test_rectify.xml Can also test interactively with vimjay image_rect.launch, which brings up an rqt gui and camera info distortion coefficients can be dynamically reconfigured.
greatly fixed in #117 |
wkentaro
pushed a commit
to wkentaro/image_pipeline
that referenced
this issue
May 24, 2016
Test with: rostest --reuse-master --text image_proc test_rectify.xml Can also test interactively with vimjay image_rect.launch, which brings up an rqt gui and camera info distortion coefficients can be dynamically reconfigured.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/ros-perception/image_pipeline/blob/indigo/image_proc/src/nodelets/rectify.cpp#L125
That check ought to test every element of info_msg->D to see if they are all 0.0. This check probably always works with real camera calibrations, but synthetic ones (which could be used in tests or simulations) can have an exactly zero first coefficient and non-zero other coefficients.
The text was updated successfully, but these errors were encountered: