TrOCR decoder_start_token should be eos
instead of cls
.
#362
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.
Using the pretrained model, when I pass
cls
orbos
as the initial decoder token, the output (first decoded token) rarely get correct. But once I try to useeos
, the output is correct, or at least similar with the output returned bymodel.generate()
.In the official code from Microsoft, they will fallback to
eos
if the token is not specified https://github.com/microsoft/unilm/blob/6f60612e7cc86a2a1ae85c47231507a587ab4e01/trocr/generator.py#L84Code excerpt to manually see the first decoded token:
Switch
eos_token_id
tobos_token_id
then observe the different output.