sigs
sigs copied to clipboard
Maintaining versioning for ONNX models
In the model zoo, a contributor normally submits a model and also maintains opset versions of each model.
Because of difference in contribution levels between contributors, some models have a lot more models at different versions than others.
- Can we take advantage of the version converters to automate this process?
- What role should the Model Zoo SIG play in the maintenance of these models for new ONNX / ONNX Runtime releases?