onnx / onnx/models

[Announce] Move existing models (< opset_version 13) to models/legacy

Open
#616 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

announce enhancement
Dominant language
Jupyter Notebook
Stars
9.8k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Feature Request

What is the problem that this feature solves?

All of existing ONNX Model Zoo models use opset_version<13, which is a quite old version (opset 12 released on May 8, 2020 in ONNX 1.7.0). Please see similar discussion in https://github.com/onnx/models/issues/472. While we will bring more new models with higher opset_version (i.e., 18): https://github.com/onnx/models/issues/617, move existing old models to models/legacy for better awareness. Also the upload requirements/model storage structure will be changed.

Describe the feature

Why is this feature necessary? What does it accomplish?

  • Move existing models (< opset_version 13) to models/legacy
  • ONNX Hub will continue to support download these old models, but please note that the location of these models will be changed. (Moved to models legacy)
  • In the future, once ONNX Model Zoo has sufficient new models, we will remove the legacy directory entirely and please go ahead to use higher opset_version instead.
Relevant Model Zoo feature areas

Which area in the Model Zoo infrastructure does this impact?
Feature Area (e.g. CI, file organization, model storage, other):
CI, file organization

Notes

Any additional information
If anyone has any question/concern, feel free to raise in this thread. Thank you for the contribution!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inventorying the existing models and their opset versions, then review the models/legacy location and the ONNX Hub download references described in the issue. Done means models with opset_version below 13 are moved to models/legacy, while CI, file organization, and downloads continue to account for the new location.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, machine-learning
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.