GitLab

Using groovy to debug issues in jenkins file

Fixing new line and names

Do the following

- Split build_and_test.sh into build_and_install.sh and test_onnxrt_unit_test.py
- Add parity tests to test_onnxrt_parity_tests.sh
- Parallelize unit and parity tests for MIGraphX-Onnxruntime integration in jenkins
- Add changes to dockerfile for additional run scripts.

Idea here is that unit tests take a while, and in the meantime if we perform
a wheel build of onnxruntime library and then run the appropriate parity tests
we should be able to catch any odd changes in parity that are missed by the unit tests
which would also appear in additional testing.

Run the three parity checks that are used for onnxruntime as part of CI

can be expanded later if needed

Example of using the C++ API to run an ONNX model with dynamic batch

Co-authored-by: Chris Austen <causten@users.noreply.github.com>

Updated each source file in the repo with the existing license.

* restructring examples

* modifications to titles/paths

* cleanup
Co-authored-by: root <root@rocm-framework-3.amd.com>

* Added initial examples

* Added python example from wiki

* Edited readme

* Added cpp interface files

* Made changes to readmes

* Added jupyter notebook for tf2 ex, added readme for tf1 ex

* Added dockerfile

* Re-structured driver example

* Removed unnecessary files

* Changed include path

* Removed cpp_interface to rewrite

* Added example of parsing, loading, saving with C++ API

* Updated readme

* Small code change, altered docker invocation, formatiing

* Formatting

* Added newline to end of dockerfile

* Formatting

* Formatting

* Added C++ API inference example program

* Formatting

* Added README to cpp inference example

* DeepCode suggested changed

* DeepCode suggested change

* Redesign python inference example

* Address review comments

* Address review comments

* Address review comments