-
Notifications
You must be signed in to change notification settings - Fork 753
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
Llama-3 offset-mapping needs fixing #1553
Comments
@ArthurZucker Is it possible to fix this in |
Yep, you are right, I'll dive a bit to see why we have this! |
Awesome thank you! |
@ArthurZucker Is there a workaround in the meantime? |
sorry not yet! I am fixing bunch of stuff, maybe #1568 ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Opening a new issue for the previously opened issue here -- #1517
Here we can see that the desired behavior for
return_offsets_mapping
from Mistral gives character indices corresponding to tokens:But for Llama-3 they are not correct
We can also see Llama-2 and GPT-2 working the same as Mistral, so Llama-3 is definitely the one performing behavior that is unexpected
The text was updated successfully, but these errors were encountered: