Fix: Correct Bicubic Boundary Interpolation in CV-CUDA Resize (Tensor Path) #271
Conversation
This file contains hidden or 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
…Coord and adjusting iSrcCoord bounds
…lations and clamping bounds
Signed-off-by: Muhammed Sezer <74321576+sezer-muhammed@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR for the bicubic boundary interpolation fix for CV-CUDA’s
Resizeoperator.The tensor path now performs per-tap clamping on all 16 cubic samples, matching OpenCV’s behavior at image edges and eliminating the flattening artifacts seen in legacy kernels.
Image Comparison (Original → OpenCV → CvCuda → New CvCuda)
The new implementation reduces mean absolute error (compared to OpenCV) by an order of magnitude compared to the legacy kernel, spesifically at the images edges.
Note: I used OpenCV as colse to ground truth source for comparisons.