Image_token mismatch when applying SigLIP to Llava & LlavaNext. #34447
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
When using a vision encoder that doesn't insert CLS tokens (like SigLIP) with Llava or Llava-next models,
an img_size mismatch error occurs.
Unlike ViT, SigLIP doesn't add a
clstoken in the vision embedding layer.However, in the Llava processor,
+1is hardcoded.As a result, an error occurs even when
vision_feature_select_strategyis set tofull.Therefore, I propose replacing the hardcoded part with a flag named
vision_feature_use_cls.bug reproduction code
transformersversion: 4.46.0Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@amyeroberts, @qubvel, @zucchini-nlp