-
Notifications
You must be signed in to change notification settings - Fork 27.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Token classification pipeline results different with tokenizers==0.11.6 vs tokenizers==0.12.0 #16520
Comments
This was referenced Mar 31, 2022
There's a proposed PR here : #16537 |
Tokenization tests were run before releasing |
5 tasks
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure if this is an issue with transformers, an issue with tokenizers or expected behavior. But when running the token classification pipeline with an aggregation_strategy="simple" the results are slightly different with tokenizers==0.12.0.
The following code produces different results (both examples use transformers==4.17.0).
With tokenizers==0.11.6:
With tokenizers==0.12.0:
The text was updated successfully, but these errors were encountered: