Skip to content

[quant][executorch] Support inception_v4 in examples #108382

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.

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

Closed
wants to merge 1 commit into from

Conversation

jerryzh168
Copy link
Contributor

Summary: Verified that pt2e quant flow matches the fx flow with executorch backend config

Test Plan:
with-proxy buck2 run executorch/examples/quantization:example -- -m=ic4 --verify

[INFO 2023-08-31 16:08:06,923 example.py:77] prepare sqnr: inf
[INFO 2023-08-31 16:08:06,932 example.py:81] quant diff max: 0.0
[INFO 2023-08-31 16:08:06,936 example.py:85] quant sqnr: inf

full output: https://www.internalfb.com/intern/paste/P818520579/

Differential Revision: D48889075

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 31, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/108382

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ You can merge normally! (2 Unrelated Failures)

As of commit 6b9446e with merge base 30a33b7 (image):

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48889075

Copy link
Contributor

@kimishpatel kimishpatel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Accepting for now, but it would be good to add test for this.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48889075

@jerryzh168
Copy link
Contributor Author

Looks good. Accepting for now, but it would be good to add test for this.

sure I can add a test after refactoring test code, right now it is tested in executorch

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48889075

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48889075

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48889075

Summary:
X-link: pytorch/executorch#203


Verified that pt2e quant flow matches the fx flow with executorch backend config

Test Plan:
with-proxy buck2 run executorch/examples/quantization:example -- -m=ic4 --verify

```
[INFO 2023-08-31 16:08:06,923 example.py:77] prepare sqnr: inf
[INFO 2023-08-31 16:08:06,932 example.py:81] quant diff max: 0.0
[INFO 2023-08-31 16:08:06,936 example.py:85] quant sqnr: inf
```

full output: https://www.internalfb.com/intern/paste/P818520579/

Reviewed By: kimishpatel

Differential Revision: D48889075
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48889075

facebook-github-bot pushed a commit to pytorch/executorch that referenced this pull request Sep 8, 2023
Summary:
Pull Request resolved: #203

X-link: pytorch/pytorch#108382

Verified that pt2e quant flow matches the fx flow with executorch backend config

bypass-github-export-checks

Reviewed By: kimishpatel

Differential Revision: D48889075

fbshipit-source-id: 40bcad1f32354131cf8d1194dca31b9d13dd6011
@facebook-github-bot
Copy link
Contributor

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants