Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Stereo Calibration: Return rotation and transformation vectors for each calibration object#22519

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@stefan-spiss
Copy link
Contributor

Motivation for feature

Extension of stereoCalibrate function for both, pinhole and fisheye model, to return the translation and rotation vectors between each calibration object and the coordinate system of the first camera of the stereo pair. This feature is helpful to evaluate the individual image pairs used for calibration. This feature is in particular interesting for the fisheye model since its stereoCalibrate function has not provided a parameter to obtain the reprojection errors per stereo image pair. With these per-view transformations available, it is now possible to calculate these reprojection errors. In addition, for the pinhole model, it is also interesting to not only get the per-view rms errors, but also statistics within one view.
For the implementation, the single camera calibration methods were used as example and all previous available function calls should still work.

Pull Request Readiness Checklist

See details athttps://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request

  • I agree to contribute to the project under Apache 2 License.
  • To the best of my knowledge, the proposed patch is not based on a code under GPL or another license that is incompatible with OpenCV
  • The PR is proposed to the proper branch
  • There is a reference to the original bug report and related work
  • There is accuracy test, performance test and test data in opencv_extra repository, if applicable
    Patch to opencv_extra has the same branch name.
  • The feature is well documented and sample code can be built with the project CMake

asmorkalov reacted with rocket emoji
…w rotation and translation vectors between the calibration object coordinate space and the coordinate space of the first camera of the stereo pair. Added overloaded versions of the function for downward compatibility.
…w rotation and translation vectors between the calibration object coordinate space and the coordinate space of the first camera of the stereo pair. Added overloaded versions of the function for downward compatibility.
@asmorkalov
Copy link
Contributor

/cc@ivashmak

Copy link
Contributor

@savuorsavuor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

These changes should also be ported to 5.x (taking into account all the recent refactoring)

@asmorkalovasmorkalov added the port to 5.x is neededLabel for maintainers. Authors of PR can ignore this labelSep 16, 2022
@asmorkalov
Copy link
Contributor

/cc@vpisarev

@asmorkalovasmorkalov merged commitfcf9f11 intoopencv:4.xSep 19, 2022
@alalek
Copy link
Member

@savuor@asmorkalov There is still no port of this patch to "5.x" branch.
Automatic merge is not possible due to manual memory management here - logic must be significantly refactored first.

rvecs.create(3,1, CV_64F, i,true);
tvecs.create(3,1, CV_64F, i,true);
memcpy(rvecs.getMat(i).ptr(), rvecs1[i].val,sizeof(Vec3d));
memcpy(tvecs.getMat(i).ptr(), tvecs1[i].val,sizeof(Vec3d));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

rvecs.getMat(i).ptr()

There is no guarantee (and no checks) of contiguous memory layout.

@alalekalalek mentioned this pull requestJan 8, 2023
@asmorkalov
Copy link
Contributor

@savuor Please port the patch to 5.x manually.

savuor added a commit to savuor/opencv that referenced this pull requestJan 19, 2023
asmorkalov pushed a commit that referenced this pull requestFeb 2, 2023
### Changes* Port of#22519 to 5.x* Distortion coefficients were not copied properly, fixed* Minor coding style chages### Pull Request Readiness ChecklistSee details athttps://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request- [x] I agree to contribute to the project under Apache 2 License.- [x] To the best of my knowledge, the proposed patch is not based on a code under GPL or another license that is incompatible with OpenCV- [x] The PR is proposed to the proper branch- [x] There is a reference to the original bug report and related work- [x] There is accuracy test, performance test and test data in opencv_extra repository, if applicable      Patch to opencv_extra has the same branch name.- [x] The feature is well documented and sample code can be built with the project CMake
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@alalekalalekalalek left review comments

@savuorsavuorsavuor approved these changes

Assignees

@savuorsavuor

Labels

category: calib3dfeatureport to 5.x is neededLabel for maintainers. Authors of PR can ignore this

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@stefan-spiss@asmorkalov@alalek@savuor

[8]ページ先頭

©2009-2025 Movatter.jp