microsoft / microsoft/onnxruntime
When will onnxruntime make it available to get nodeunit inputs correctly for QLinearConcat
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 21.9k
- Forks
- 4.2k
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 184
Description
Describe the issue
May I ask when will onnxruntime support for setting inputs for the QLinearConcat operator in node unit structure be available? I saw a ‘todo’ note in the code, but there has been no progress for the past two years.”
To reproduce
File path:node_unit.cc. I found that onnxruntime does not handle the inputs of the QLinearConcat's node_unit in the same way as it does with other QLinear operators, that is, by binding each actual input with its quantization information into a single input.
Urgency
No response
Platform
Linux
OS Version
Ubuntu 22.04.2 LTS
ONNX Runtime Installation
Built from Source
ONNX Runtime Version or Commit ID
main
ONNX Runtime API
C++
Architecture
X86
Execution Provider
Default CPU, NNAPI, Other / Unknown
Execution Provider Library Version
No response
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.
Research direction
Start at onnxruntime/core/framework/node_unit.cc around line 287 and compare QLinearConcat handling with the other QLinear operators. Use the issue’s reproduction details to verify the expected node_unit input representation. Done means each actual QLinearConcat input is bound together with its quantization information consistently with the other QLinear operators.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100