Skip to content
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

Implementation of threshold_binary and threshold_truncate #313

Merged
merged 2 commits into from Jun 18, 2019

Conversation

@miralshah365
Copy link
Contributor

miralshah365 commented Jun 18, 2019

Description

Two variant of Binary threshold Implemented

  1. Simple Binary Threshold
    If the pixel value is more than the threshold then the pixel value is set to maximum or else to 0
  2. Inverse Binary Threshold
    If the pixel value is more than the threshold then the pixel value is set to 0 or else to maximum

Two Truncation threshold Implemented

  1. Threshold Truncate
    If the pixel value is more than the threshold then it is truncated if the direction specified is regular. If the direction is in inverse then values below the thresholds are truncated.
  2. Truncation to zero
    If the pixel value is less than the threshold then it is set to zero if the direction specified is regular. If the direction is in inverse then values above the thresholds are set to zero.

References

Tasklist

  • Add test case(s)
  • Ensure all CI builds pass
  • Review and approve
Add public functions threshold_binary and threshold_truncate.
Add tests and example.
Closes #310
@mloskot mloskot self-requested a review Jun 18, 2019
Copy link
Member

mloskot left a comment

This work is ready for approval.

It has been already reviewed as PR at BoostGSoC19#1 and this PR is just a copy following the decision and agreement to work from Miral's private fork and submit against upstream repo.

@mloskot mloskot marked this pull request as ready for review Jun 18, 2019
@mloskot mloskot added the cat/feature label Jun 18, 2019
@mloskot mloskot merged commit 716fe9a into boostorg:develop Jun 18, 2019
9 checks passed
9 checks passed
boostorg.gil Build #20190618.2 succeeded
Details
boostorg.gil (macos1013_xcode91_cmake) macos1013_xcode91_cmake succeeded
Details
boostorg.gil (ubuntu1604_gcc5_cxx11_cmake) ubuntu1604_gcc5_cxx11_cmake succeeded
Details
boostorg.gil (ubuntu1604_gcc8_cxx14_cmake) ubuntu1604_gcc8_cxx14_cmake succeeded
Details
boostorg.gil (win2012_vs2015_cmake) win2012_vs2015_cmake succeeded
Details
boostorg.gil (win2016_vs2017_cxx14_cmake) win2016_vs2017_cxx14_cmake succeeded
Details
boostorg.gil (win2016_vs2017_cxx17_cmake) win2016_vs2017_cxx17_cmake succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
[gsoc2019] Image Processing Algorithms automation moved this from In progress to Done Jun 18, 2019
@mloskot mloskot added this to the Boost 1.71 milestone Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.