Fix: num_logits_to_keep
in composite models
#33168
Merged
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?
Fixes issue from #33164 (comment).
We cannot assume that the model will have
num_logits_to_keep
in its forward, because an LM can be used as backbone in composite models. So the current PR setsnum_logits_to_keep
to None by default and adds it as a kwarg only when it is explicitly set to an integer by usersPlus, updated VLMs accordingly with
num_logits_to_keep
. Other VLMs like BLIP don't need this arg because they delegate the whole generation process to the LM.cc @merveenoyan