[SegGPT] Fix loss calculation #30421
Merged
+89
−16
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?
This PR fixes #30419 and ensures that the loss is being correctly calculated.
While working on this PR I not only noticed that
SegGptLoss
was broken, but it was being incorrectly calculated (shame onSegGpt
contributor 😞). Proposed solution include:labels
toSegGptModel
to correctly perform theforward
pass when training inIn-Context Painting
styleSegGptLoss
forward
method and its docstrings accordingly so that the output is the same as the one obtained in the original implementation.Note
While running
test_modeling_seggpt
withis_training = True
I found thatgradient_checkpointing
is also not working due totype_token_semantic
parameter that is not used in the forward pass and is controlled by theembedding_type
the model'sforward
and by default we use thetype_token_instance
just like the original implementation. Hence, we could probably move theembedding_type
to config to allowgradient_checkpointing
or remove it entirely as in the original implementation is not clear what is the use case fortype_token_semantic
c.c. @amyeroberts