[Good First Issue]: Align behavior of ONNX Frontend function ReduceL1-11, 13, 18 with original framework

[gkrivor]

Context

Neural networks are graphs consisting of nodes called operators. Each operator corresponds to a mathematical function, usually described in framework's documentation or an AI standard, such as ONNX.
OpenVINO ONNX Frontend is a component responsible for working with ONNX graphs and requires implementation of different ONNX operators in order to use ONNX models.
This task requires alignment between OpenVINO ONNX Frontend and original framework implementations of ReduceL1 for next list of opsets: opset 11, opset 13, opset 18
Necessary help will be provided by ONNX Fronted team.

What needs to be done?

First of all, please, take a look on ReduceMax PR for a reference.

Operator details can be found in ONNX Operators
More details can be found in ONNX Changelog: opset 11, opset 13, opset 18

1. Function already has a common implementation in OpenVINO. First of all, you need to review a documentation and prepare a table with differences between versions. It could be, for instance, a missing property, extended/reduced coverage of existing property, etc...
2. Copy existing implementation here to make it aligned with original framework (extend or reduce coverage of a common implementation). Copy of modified implementation should be in a defined opset, or in opset 1 in case it implements oldest implementation. Example of multi-opset operation.
3. Register the function in ops_bridge.cpp while keeping alphabetical order
4. Create test model(s) in ONNX models directory. OpenVINO test infrastructure then converts prototxt files to ONNX models - you will use those models later in tests
5. Add tests covering all use cases here
6. Check Python xfailed tests to find a test marked as a xfailed for added functionality. If any exist - remove corresponding lines and try to verify by using cmdline "python -m pytest -k name_of_test".
   More details in adding operators to ONNX Frontend guide

Example Pull Requests

No response

Resources

• Contribution guide - start here!
• What is OpenVINO?
• User documentation
• Guides on ONNX Frontend architecture and ONNX Frontend tests are also available
• You can also see a blog post on contributing to OpenVINO

Contact points

@gkrivor

Ticket

No response

[Gabriellgpc]

.take

[github-actions]

Thank you for looking into this issue! Please let us know if you have any questions or require any help.

[p-wysocki]

I am happy to announce that we have created a channel dedicated to Good First Issues support on our Intel DevHub Discord server! Join it to receive support, engage in discussions, ask questions and talk to OpenVINO developers.

[p-wysocki]

I'm reopening the issue due to current assignee's inactivity. If you with to repick the issue please let me know.

[RitikaxShakya]

.take

[github-actions]

Thank you for looking into this issue! Please let us know if you have any questions or require any help.

[RitikaxShakya]

@gkrivor Hello! I have created the table of differences and changes made on versions of ReduceL1

[gkrivor]

@RitikaxShakya awesome! I'll add link to a issue with similar discussion: #20553

Now I'm expecting to achieve something like https://github.com/openvinotoolkit/openvino/blob/master/src/frontends/onnx/frontend/src/op/softmax.cpp which will implement a found differences.

Also you will need to add a tests for exact implementations like here: #21825

I mean a prototxt file and corresponing unit test to verify a correctness.

[p-wysocki]

Hello @RitikaxShakya, are you still working on that issue?

[RitikaxShakya]

Yes, I am still working on it, I have made the changes so now working on running tests.

[gkrivor]

@RitikaxShakya hi, I had a chance take a look on set of Reduce*-18 operations. All of them could have issues with tests due to problems with a shape inference, because of newly added axes-input. I'll fix it soon.

[RitikaxShakya]

Thank you

[p-wysocki]

Helo @RitikaxShakya, are you still working on that issue?

[RitikaxShakya]

Yes I am working on it as the issues with tests due to problems with a shape inference, because of newly added axes-input is fixed.

[RitikaxShakya]

@gkrivor @p-wysocki Hello! I have completed all 6 steps mentioned in the issue description and here's the PR

[RitikaxShakya]

Hello, I would like if someone @gkrivor @p-wysocki can review my PR. I have updated it with new changes while taking ReduceMax as reference. Had some closed PRs (sorry about this) because i got into some issue while resolving merging conflicts so created another pr for this. Thank you!

[hub-bla]

Hey @mlukasze, @gkrivor, I think it can be closed due to #25909.