1. 28 6月, 2023 2 次提交
  2. 25 6月, 2023 1 次提交
  3. 24 6月, 2023 5 次提交
  4. 23 6月, 2023 8 次提交
  5. 22 6月, 2023 6 次提交
    • A
      Merge pull request #23848 from AleksandrPanov:fix_detectDiamonds_api · affc69bf
      Alexander Panov 提交于
      Fix detect diamonds api #23848
      
      `detectDiamonds` cannot be called from python, reproducer:
      
      ```
      import numpy as np
      import cv2 as cv
      
      detector = cv.aruco.CharucoDetector(
          cv.aruco.CharucoBoard(
              (3, 3), 200.0, 100.0,
              cv.aruco.getPredefinedDictionary(cv.aruco.DICT_4X4_250)
          )
      )
      image = np.zeros((640, 480, 1), dtype=np.uint8)
      res = detector.detectDiamonds(image)
      print(res)
      ```
      
      The error in `detectDiamonds` API fixed by replacing `InputOutputArrayOfArrays markerIds` with `InputOutputArray markerIds`.
      
      
      ### 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
      - [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.
      - [ ] The feature is well documented and sample code can be built with the project CMake
      affc69bf
    • D
      Merge pull request #23702 from dkurt:py_rotated_rect · 22b747ea
      Dmitry Kurtaev 提交于
      Python binding for RotatedRect #23702
      
      ### Pull Request Readiness Checklist
      
      related: https://github.com/opencv/opencv/issues/23546#issuecomment-1562894602
      
      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
      - [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
      22b747ea
    • A
      FFmpeg/4.x: update FFmpeg wrapper 2023.6 · 426b0887
      Alexander Smorkalov 提交于
      426b0887
    • A
      Merge pull request #23843 from TolyaTalamanov:at/fix-missing-opaque-kind-for-kernel · 60848519
      Anatoliy Talamanov 提交于
      G-API: Fix incorrect OpaqueKind for Kernel outputs #23843
      
      ### Pull Request Readiness Checklist
      
      #### Overview
      The PR is going to fix several problems:
      1. Major: `GKernel` doesn't hold `kind` for its outputs. Since `GModelBuilder` traverse graph from outputs to inputs once it reaches any output of the operation it will use its `kind` to create  `Data` meta for all operation outputs. Since it essential for `python` to know `GTypeInfo` (which is `shape` and `kind`) it will be confused.
      
      Consider this operation:
      ```
       @cv.gapi.op('custom.square_mean', in_types=[cv.GArray.Int], out_types=[cv.GOpaque.Float, cv.GArray.Int])
          class GSquareMean:
              @staticmethod
              def outMeta(desc):
                  return cv.empty_gopaque_desc(), cv.empty_array_desc()
      ```
      Even though `GOpaque` is `Float`, corresponding metadata might have `Int` kind because it might be taken from `cv.GArray.Int`
      so it will be a problem if one of the outputs of these operation is graph output because python will cast it to the wrong type based on `Data` meta.
      
      2. Minor: Some of the OpenVINO `IR`'s doesn't any layout information for input. It's usually true only for `IRv10` but since `OpenVINO 2.0` need this information to correctly configure resize we need to put default layout if there no such assigned in `ov::Model`. 
      
      See details at https://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 another license that is incompatible with OpenCV
      - [ ] The PR is proposed to the proper branch
      - [ ] 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
      60848519
    • A
      Merge pull request #23540 from cudawarped:add_CAP_PROP_CODEC_FOURCC · 61d48dd0
      Alexander Smorkalov 提交于
      `VideoCapture`: change `CAP_PROP_FOURCC` to fix #22876
      61d48dd0
    • A
      Merge pull request #23842 from opencv-pushbot:gitee/alalek/fix_static_build_with_gapi_openvino · eba84509
      Alexander Smorkalov 提交于
      G-API: fix static build with OpenVINO
      eba84509
  6. 21 6月, 2023 9 次提交
  7. 20 6月, 2023 9 次提交