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

Add Thickness parameter in drawMatches function#20232

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
opencv-pushbot merged 1 commit intoopencv:3.4fromgasparitiago:drawMatches3.4
Jun 18, 2021

Conversation

@gasparitiago
Copy link
Contributor

@gasparitiagogasparitiago commentedJun 7, 2021
edited by alalek
Loading

This commit adds the feature of selecting the thickness
of the matches drawn by the drawMatches function.

In larger images, the default thickness of 1 pixel creates images
that are hard to visualize.

resolves#20095

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 other license that is incompatible with OpenCV
  • The PR is proposed to proper branch
  • There is reference to 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

This commit adds the feature of selecting the thicknessof the matches drawn by the drawMatches function.In larger images, the default thickness of 1 pixel creates imagesthat are hard to visualize.
Copy link
Member

@alalekalalek left a comment

Choose a reason for hiding this comment

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

Looks good to me 👍

There are some low priority questions about:

  • compatibility of Python bindings (we don't check them actually)
  • documentation of parameters

const std::vector<DMatch>& matches1to2, InputOutputArray outImg,
constint matchesThickness,const Scalar& matchColor=Scalar::all(-1),
const Scalar& singlePointColor=Scalar::all(-1),const std::vector<char>& matchesMask=std::vector<char>(),
int flags=DrawMatchesFlags::DEFAULT );
Copy link
Member

Choose a reason for hiding this comment

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

@vpisarev I believe we should define strategy about changes which should be migrated to OpenCV 5.0 major release

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Regarding Python bindings: I've tested the code provided by the author of#20095 and it's working fine.

Regarding the documentation: the new parameter should be documented when it's only used in an overloaded function? If so, I can take a look at it.
My first try was to include it as a parameter of the original function, but some errors happened due to the function names inside of binary files, that's why I've created a new function.

@opencv-pushbotopencv-pushbot merged commitc2263db intoopencv:3.4Jun 18, 2021
@alalekalalek mentioned this pull requestJun 19, 2021
@alalekalalek mentioned this pull requestOct 15, 2021
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@alalekalalekalalek approved these changes

Assignees

@alalekalalek

Projects

None yet

Milestone

3.4.15

Development

Successfully merging this pull request may close these issues.

3 participants

@gasparitiago@alalek@opencv-pushbot

[8]ページ先頭

©2009-2025 Movatter.jp