Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@asmorkalov
Copy link
Contributor

@asmorkalov asmorkalov commented Apr 19, 2024

OpenCV Contrib: opencv/opencv_contrib#3723
OpenCV Extra: opencv/opencv_extra#1172

#25317 from junxnone:ipp_202110
#25354 from LaurentBerger:uiname
#25397 from asmorkalov:as/HAL_GaussianBlur_bit_exact
#25399 from asmorkalov:as/HAL_remap
#25402 from Linaname:4.x
#25414 from alexlyulkov:al/range-fixed
#25419 from vrabaud:ffmpeg
#25424 from mshabunin:fix-features2d-test
#25430 from asmorkalov:as/FaceDetectorYN_js
#25432 from vrabaud:webp_1.4.0
#25439 from mshabunin:cpp-contours-5-back
#25445 from Kumataro:fix25403
#25447 from vrabaud:tiff
#25454 from fengyuentau:fix_core_gemm_acc

Previous "Merge 4.x": #25422

alexlyulkov and others added 20 commits April 17, 2024 09:38
Fixed ONNX range layer opencv#25414

Partially address opencv#25363
Fixed ONNX range layer. It should support any input type.
Added tests (extra [PR](opencv/opencv_extra#1170))

### Pull Request Readiness Checklist

See details at https://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
- [ ] 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
Handle top and left border masked pixels correctly in inpaint method opencv#25402

Fixes opencv#25389

### Pull Request Readiness Checklist

See details at https://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
- [ ] 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
features2d: reduce accuracy test avg memory consumption opencv#25424

**Merge with contrib**: opencv/opencv_contrib#3722

I've observed high memory consumption in the `opencv_test_features2d` (x86_64, Ubuntu 22.04, Debug):

![image](https://github.com/opencv/opencv/assets/3304494/419d65d9-d727-4d1e-bdec-dbde6681c188)
It's always more than 180 MiB with peak at 535 MiB

This was caused by pointers to the algorithm object instances stored in the tests parameters. I've replaced them with factory functions/lambdas with the following result:

![image](https://github.com/opencv/opencv/assets/3304494/bd4ff0ea-3db4-4ab8-8e6d-192a3826e99c)
Now peak is at 355 MiB and permanent consumption level is ~ 1-2 MiB


**Note:** current peak is caused by KAZE features allocating 8x image size utility buffers. Not sure if we can or should do anything about it: https://github.com/opencv/opencv/blob/66fb5021e9253e3decab376d00322eaf2b279c89/modules/features2d/src/kaze/KAZEFeatures.cpp#L61-L68
…it_exact

Added HAL function for popular bit-exact branch of GaussianBlur with sigma=0
Fix race condition in InternalFFMpegRegister initialization. opencv#25419

initLogger_ does not check if the logger has been initizalized before and it might initialize it several times from different threads, racing with other threads that are logging.

### Pull Request Readiness Checklist

See details at https://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
imgproc: sync boundingRect function with 5.x
apps: createsamples: fix comment to remove last backslash opencv#25445

Close opencv#25403

### Pull Request Readiness Checklist

See details at https://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
- [ ] 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
core: fix `Core_GEMM.accuracy` failure on recent macOS
Fix for IPP 2021.10 with OneAPI 2024 opencv#25317

fixes opencv#25270

### Pull Request Readiness Checklist

See details at https://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
- [ ] 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
Remove unnecessary FIXIT section in grfmt_tiff.cpp opencv#25447

No int64/uint64 is used in the code anymore.

grfmt_tiff.hpp includes the tiff.h header inside of the tiff_dummy_namespace declaration. One implication of this is that all namespaced declarations made in tiff.h become qualified with tiff_dummy_namespace::.

Because tiff.h includes standard library headers, the std namespace declarations are converted to tiff_dummy_namespace::std declarations.

Subsequently, grfmt_tiff.hpp declares using namespace tiff_dummy_namespace;.

This can lead to an ambiguity error during the resolution of the std namespace.

### Pull Request Readiness Checklist

See details at https://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
Add cv::currentUIFramework opencv#25354

issue opencv#25329

### Pull Request Readiness Checklist

See details at https://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
- [ ] The PR is proposed to the proper branch
- [x] 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.
- [x] The feature is well documented and sample code can be built with the project CMake
@asmorkalov asmorkalov requested a review from alexlyulkov April 19, 2024 11:02
@asmorkalov asmorkalov changed the base branch from 4.x to 5.x April 19, 2024 11:02
@asmorkalov asmorkalov changed the title WIP: 5.x merge 4.x 5.x merge 4.x Apr 22, 2024

// Issue: https://github.com/opencv/opencv/issues/25363
// The issue was addressed in 4.x, but the solution does not fit 5.x design
TEST_P(Test_ONNX_layers, DISABLED_Range)
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe we should introduce policy to validate incoming DNN patches on both 4.x and 5.x branches to avoid cases like that.
Testing on both branches should improve proposed solutions.

@asmorkalov asmorkalov merged commit 43d243d into opencv:5.x Apr 22, 2024
@dkurt dkurt added this to the 5.0 milestone May 3, 2024
@asmorkalov asmorkalov mentioned this pull request Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.