Inputs of some operators (requiring standard input shape) become non-standard after some optimization.
Open
@scxiao is already working on this.
Since Jan 17, 2022.
- Dominant language
- C++
- Stars
- 333
- Forks
- 150
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 54
Description
This issue begin to happen after we remove the requirement of some operators, e.g., transpose. The scenario is: When parsing a model, input shape to some operators (reshape, reduce_mean) that require standard input shape is standard, but after some optimization, the input becomes non-standard, then an exception is thrown.
This happens in the model in issue# 999. The models are gmixer_24_224, mixer_b16_224, mixer_b16_224_miil_in21k, mixer_b16_224_miil, mixer_l16_224_in21k, mixer_l16_224. It also happened in the model ssd_resnet I am working on.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.