Skip to content

Conversation

@NielsRogge
Copy link
Contributor

@NielsRogge NielsRogge commented Jan 4, 2023

What does this PR do?

A user reported at timojl/clipseg#18 that CLIPSeg uses the ImageNet mean + std instead of the [-1, 1] range for normalization. This PR updates the integration test as repos on the hub were fixed.

@NielsRogge NielsRogge requested a review from ydshieh January 4, 2023 11:59
@HuggingFaceDocBuilderDev
Copy link

HuggingFaceDocBuilderDev commented Jan 4, 2023

The documentation is not available anymore as the PR was closed or merged.

Copy link
Collaborator

@ydshieh ydshieh left a comment

Choose a reason for hiding this comment

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

Thanks for the fix. LGTM, but I am wondering one thing: ClipSeg has (only) CLIPSegProcessor which include ViTImageProcessor, which itself has default values IMAGENET_STANDARD_MEAN and IMAGENET_STANDARD_STD.

So the image processor used for ClipSeg is just ViTImageProcessor with different settings?

@NielsRogge
Copy link
Contributor Author

Yes, it uses ViTImageProcessor with different settings.

@NielsRogge NielsRogge merged commit 4f1c9d1 into huggingface:main Jan 5, 2023
silverriver pushed a commit to silverriver/transformers that referenced this pull request Jan 6, 2023
Fix integration test

Co-authored-by: Niels Rogge <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants