[Feature Request] Classify Contributed Ops
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- machine-learning
Research direction
Start with docs/ContribOperators.md and review the listed contributed Ops, including BeamSearch, GreedySearch, and CropAndResize, against the proposed NLP and vision namespaces. Done means defining the categorization scope and consistently representing applicable Ops under com.microsoft.nlp, com.microsoft.vision, com.microsoft.audio, or the general com.microsoft namespace.
Written by the indexing model from the issue text.
Description
Describe the feature request
Currently there is no categorization of contributed Ops into e.g. NLP, Vision, and Audio
All are under ONE same namespace: com.microsoft
The suggestion is to split these Ops into the following categories
e.g.
- com.microsoft.nlp
- com.microsoft.vision
- com.microsoft.audio
For those Ops that are non-specific to any one of the above categories, they stay with
- com.microsoft
Describe scenario use case
To democratize the use of these ops, especially for new users, for users interested on e.g. NLP, they could look into the following namespeace
nlp
com.microsoft.nlp
vision
com.microsoft.vision
- Dominant language
- C++
- Stars
- 21.9k
- Forks
- 4.2k
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 179
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/onnxruntime
-
ep:MIGraphX
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/onnxruntime#32352 · 1 comment ·
-
`optimization.disable_specified_optimizers` is documented as comma-separated but is parsed on `;` Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
microsoft/onnxruntime#32211 ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/onnxruntime#29750 · 3 comments ·
-
ep:WebGPU platform:web stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/onnxruntime#28976 · 3 comments ·
-
[Documentation] Python tutorial missing PyTorch export guidance and external data file handling Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/onnxruntime#28763 · 5 comments ·
All issues in microsoft/onnxruntime
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·