Skip to content

dnn onnx: support constaint inputs in einsum importer#24753

Merged
asmorkalov merged 2 commits intoopencv:4.xfrom
fengyuentau:einsum_importer
Dec 25, 2023
Merged

dnn onnx: support constaint inputs in einsum importer#24753
asmorkalov merged 2 commits intoopencv:4.xfrom
fengyuentau:einsum_importer

Conversation

@fengyuentau
Copy link
Copy Markdown
Member

Merge with opencv/opencv_extra#1132.

Resolves #24697

Credits to @LaurentBerger.


This is a workaround. I suggest to get input shapes and calculate the output shapes in getMemoryShapes so as to keep the best compatibility. It is not always robust getting shapes during the importer stage and we should avoid that as much as possible.

Pull Request Readiness Checklist

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

Copy link
Copy Markdown
Contributor

@Abdurrahheem Abdurrahheem left a comment

Choose a reason for hiding this comment

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

LGTM 👍🏻

@asmorkalov asmorkalov merged commit f978c99 into opencv:4.x Dec 25, 2023
@fengyuentau fengyuentau deleted the einsum_importer branch December 26, 2023 03:31
@asmorkalov asmorkalov mentioned this pull request Jan 19, 2024
thewoz pushed a commit to thewoz/opencv that referenced this pull request May 29, 2024
dnn onnx: support constaint inputs in einsum importer opencv#24753 

Merge with opencv/opencv_extra#1132.

Resolves opencv#24697

Credits to @LaurentBerger.

---

This is a workaround. I suggest to get input shapes and calculate the output shapes in `getMemoryShapes` so as to keep the best compatibility. It is not always robust getting shapes during the importer stage and we should avoid that as much as possible.

### 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.
- [x] The feature is well documented and sample code can be built with the project CMake
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug category: dnn (onnx) ONNX suport issues in DNN module category: dnn

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ERROR input shape not found in function 'cv::dnn::dnn4_v20230620::ONNXImporter::parseEinsum'

3 participants