Several parts of the op sec like the main op description, attributes, input and output descriptions become part of the binary that consumes ONNX e.g. onnxruntime causing an increase in its size due to strings that take no part in the execution of the model or its verification.

Setting __ONNX_NO_DOC_STRINGS doesn't really help here since (1) it's not used in the SetDoc(string) overload (s

To get started using this repo quickly using a Google Cloud Platform (GCP) Deep Learning Virtual Machine (VM) follow the instructions below. New GCP users are eligible for a $300 free credit offer. Other quickstart options for this repo include our [Google Colab Notebook](https://colab.research.google.com/github/ultralytics/yolov3/blob

Platform (like ubuntu 16.04/win10): Windows 10
Python version: 3.7.4, mmdnn==0.2.5

Running scripts: mmconvert -f caffe -df keras -om test

I know that this command is not supposed to run without passing an input file, but the error message is incorrect and should be improved:

mmconvert: error: argument --srcFramework/-f: invalid choice: 'None' (choose from 'caffe', 'caffe2', 'cn

The Keras logo shows COMING SOON.
We already have a demo for it. We should update the logo to remove the COMING SOON

https://github.com/microsoft/onnxruntime/blob/aefa466334f43a89c0821f74aef7f354f799e356/samples/c_cxx/imagenet/main.cc#L110

Shouldn't this be session_options not session_option?

The model zoo currently contains three models (Resnet50, SqueezeNet and VGG19) that each have two variants which is confusing to end consumers.

Ideally these should be de-duplicated. If that doesn't make sense then they should state their differences outside of origin framework and be organized in a way that places them all in the same sub-folder/path on the repo.

Following are pointers to t

I've been using rllib for a while and quite like the Trainable and Tune (hyperaram search) abstractions.
Does coach contain something similar?

I really like coach's documentation. Can someone provide a comparison between the two and when it is applicable to use each?
Thanks.

Changes made in #1874 to test/models/mxnet/1rnn_layer_3lstm.json reveal an error in the fusion of a sequence of LSTM cells into a single layer RNN for gpu.

The fused result should look like:

Instead, we currently see:
![rnn_fusion_issue](https://user-images.githubusercontent.com/48

@benbarsdell @yinghai For more detail see the issue originally posted in the tensorflow-onnx repo. Can you guys help look into this? I guess something is not quite right either in onnx-tensorrt parser or tensorflow-onnx conversion tool.

https://github.com/awslabs/mxnet-model-server/blob/master/plugins/endpoints/src/main/java/software/amazon/ai/mms/plugins/endpoint/ExecutionParameters.java#L26

'max_request_size' seems to refer to bytes, not mb.

The project README states:

We have joined force with Microsoft to co-develop ONNX Tensorflow frontend. For current onnx-tf frontend users, please migrate to use tf-onnx (https://github.com/onnx/tensorflow-onnx) where our code had been merged into.

Can we add more instructions on how to migrate to tensorflow-onnx? It looks like that package is doing TF -> ONNX only, not ONNX -> TF. What am

Describe the bug

Guide under Tensorflow.js heading needs an update, 'names' flag changed to 'name_policy ' according to latest commit?

Under supported layers heading, ConvTrsnpose2d==ConvTranspose2d?

Issue

In onnxmltools/convert/lightgbm/convert.py, inline comments indicate that only LGBMClassifiers, LGBMRegressor and Booster are supported:

This function produces an equivalent ONNX model of the given lightgbm model.
The supported lightgbm modules are 

Is your feature request related to a problem? Please describe.
N/A

Describe the solution you'd like
it could help to have functions to describe the expected shapes of input and output.
For example, in the case of image classification, the input's shape is related to the size of the picture. This could allow to easily use a pre-processing of the picture, without hardcoding it.

Gett

CI/CD on Google Cloud

Look over to Tensorflow Official Build Status.

We can have different badges for different mediums of deployment by using Google Cloud.