-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Improve the precision of our integration tests #914
Comments
I'm going to start work on this right now |
@patrickvonplaten after some research I think I understand the issue. The images are currently stored in a low-precision format (e.g. png) which prevents us from testing with any greater precision than What we need to do is store a numpy representation of the image, say somewhere inside The way we could do this is by generating the test output, saving that output as a numpy image and uploading it. This is what I plan to do tomorrow. This stack overflow thread was very helpful in understanding the issue. |
Hey @Lewington-pitsos, That's a very good observation - we came to the same conclusion here: #937 :-) |
Hey, yes I am currently working on this in fact! |
@patrickvonplaten I made a PR adding the files: https://huggingface.co/datasets/hf-internal-testing/diffusers-images/discussions/2 |
Thanks a mille @Lewington-pitsos for making this very important improvement-of-life PR! Leaving this issue open as we still need to apply the same changes to: |
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
…ingface#914) * [SD] Modify the flags to use --iree-preprocessing-pass-pipeline * Fix flags in sd_annotation
* Revert "[SD] Modify the flags to use --iree-preprocessing-pass-pipeline (huggingface#914)" This reverts commit a783c08. * Revert "Fix iree flags due to the change in shark-runtime (huggingface#944)" This reverts commit 1d38d49.
We currently have a rather low precision when testing our pipeline due to due reasons.
.max() < 1e-2
. IMO we should test for.max() < 1e-4
with the numpy arrays. In my experiements across multiple devices I have not seen differences bigger than.max() < 1e-4
when using full precision.IMO this could have also prevented: #902
The text was updated successfully, but these errors were encountered: