Repository navigation
Enable detokenizing special tokens - #1596
Merged
Merged
Conversation
Contributor
Author
|
Hey @abetlen , when you get a chance, would you give this a review? |
Owner
|
Hey @benniekiss thank you for the contribution! I reverted the changes to |
Contributor
Author
|
That's perfect! Thank you for taking the time to review |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed that it was not possible to detokenize special tokens, such as the EOS token, when using Phi-3(.1). This PR makes sure that the
specialflag can be passed to thedetokenize()method of both theLlamaTokenizerand theLlamaHFTokenizerI also noticed that
prev_tokenswas not being used in the detokenize method ofLlamaTokenizer, so this PR also adds that functionality based onLlamaHFTokenizer