Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FR]: Make vitis-ai quantization compatible with ORT 1.16.0+ #382

Closed
1 of 7 tasks
jambayk opened this issue Jun 27, 2023 · 2 comments
Closed
1 of 7 tasks

[FR]: Make vitis-ai quantization compatible with ORT 1.16.0+ #382

jambayk opened this issue Jun 27, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@jambayk
Copy link
Contributor

jambayk commented Jun 27, 2023

Proposal Summary

Vitis ai code uses some functions that are not available in ORT 1.16.0 is currently in development. Refer to #380 for more details.

What component(s) does this request affect?

  • OliveModels
  • OliveSystems
  • OliveEvaluator
  • Metrics
  • Engine
  • Passes
  • Other
@jambayk jambayk added the enhancement New feature or request label Jun 27, 2023
@jambayk jambayk assigned jambayk and unassigned jambayk Jun 27, 2023
@jambayk
Copy link
Contributor Author

jambayk commented Jun 27, 2023

@sheng-xiao FYI

@jambayk jambayk mentioned this issue Jun 27, 2023
Merged
5 tasks
@sheng-xiao sheng-xiao mentioned this issue Jun 28, 2023
Merged
5 tasks
@sheng-xiao
Copy link
Contributor

@jambayk See #385 for the fix, thanks.

guotuofeng pushed a commit that referenced this issue Jun 29, 2023
@sheng-xiao
Vitis ai (#385)
ef15fea 
## Describe your changes
Update vitis_ai link in passes/onnx.md and make Vitis AI compatible with
ORT 1.16.0 (nightly)
1. Stop using clone_model_with_shape_infer in ORT 1.16.
2. Set optimize_model=False by default.
3. Use load_model_with_shape_infer in ORT 1.16.
4. Convert string-type model_input to Path object.
5. Update some codes to be aligned with onnxruntime.quantization.

## Checklist before requesting a review
- [ ] Add unit tests for this change.
- [ ] Make sure all tests can pass.
- [ ] Update documents if necessary.
- [ ] Format your code by running `pre-commit run --all-files`
- [ ] Is this a user-facing change? If yes, give a description of this
change to be included in the release notes.

## (Optional) Issue link
#382
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@guotuofeng @sheng-xiao @jambayk