Skip to content
reference implementation to use ONNX Runtime with Azure IoT Edge
Python
Branch: master
Clone or download
Latest commit 7834db1 Oct 14, 2019

README.md

page_type languages products
sample
python
azure-machine-learning-service
azure-iot-edge
azure-storage

ONNX Runtime with Azure IoT Edge for acceleration of AI on the edge

This tutorial is a reference implementation for executing ONNX models across different device platforms using the ONNX Runtime inference engine. ONNX Runtime is an open source inference engine for ONNX Models. ONNX Runtime Execution Providers (EPs) enables the execution of any ONNX model using a single set of inference APIs that provide access to the best hardware acceleration available.

In simple terms, developers no longer need to worry about the nuances of hardware specific custom libraries to accelerate their machine learning models. This tutorial demonstrates that by enabling the same code to run on different HW platforms using their respecitive AI acceleration libraries for optimized execution of the ONNX model.

ONNX Runtime with TensortRT on Jetson Nano is the tutorial example for deploying pre-trained ONNX models on the NVIDIA Jetson Nano using Azure IoT Edge.

ONNX Runtime with OpenVINO is the tutorial examle for dpeloying pre-trained ONNX models with ONNX Runtime using the OpenVINO SDK for acceleration of the model.

Contribution

This project was created with active contributions from Abhinav Ayalur, Angela Martin, Kaden Dippe, Kelly Lin, Lindsey Cleary and Priscilla Lui

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

You can’t perform that action at this time.