Regression in INTER_NEAREST remap (Bug #2428)
Description
Command to reproduce:
run.py --perf_min_samples=1 --perf_force_samples=1 -t imgproc --gtest_filter=*Remap.Remap*
Failed tests:
[ FAILED ] TestRemap_Remap.Remap/8, where GetParam() = (640x480, 16UC1, 32FC2, INTER_NEAREST) [ FAILED ] TestRemap_Remap.Remap/20, where GetParam() = (640x480, 16SC1, 32FC2, INTER_NEAREST) [ FAILED ] TestRemap_Remap.Remap/32, where GetParam() = (640x480, 32FC1, 32FC2, INTER_NEAREST) [ FAILED ] TestRemap_Remap.Remap/44, where GetParam() = (1920x1080, 16UC1, 32FC2, INTER_NEAREST) [ FAILED ] TestRemap_Remap.Remap/56, where GetParam() = (1920x1080, 16SC1, 32FC2, INTER_NEAREST) [ FAILED ] TestRemap_Remap.Remap/68, where GetParam() = (1920x1080, 32FC1, 32FC2, INTER_NEAREST)
Associated revisions
Update sanity data for remap (issue #2428)
Merge pull request #2428 from alalek:ocl_copyMakeBorder_3channels
History
Updated by Andrey Kamaev over 12 years ago
- Target version deleted ()
Updated by Vadim Pisarevsky over 12 years ago
About at the same time as the threading was added to remap, we fixed the following bug in remap, nearest neighbor interpolation mode: http://code.opencv.org/issues/2314
In short, remap with this interpolation type worked incorrectly. Now, the reference results in the performance tests need to be regenerated.
- Status changed from Open to Cancelled
Updated by Andrey Kamaev over 12 years ago
Reference data is updated.
Updated by Andrey Kamaev about 12 years ago
- Target version set to 2.4.3