You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, thanks for your work! It is truly a great project!
Quick question on the KeywordsStoppingCriteriaimplementation. I see that it is a custom stopping criteria appended to other forms like EOSTokenCriteria,MaxLengthCriteria etc..
As far as I understood, The EOSTokenCriteria used here looks if the predicted token is an EOS token which is 151645 which I believe is the same as the KeywordsStoppingCriteria functionality where the ['<|im_end|>'] is tokenized as 151645. I feel they do the same thing. Return True if the predicted token is 151645.
I tried passing None to stopping_criteriahere and it did not change the behavior. Is there a reason we need both?
The text was updated successfully, but these errors were encountered:
Hello Team,
First off, thanks for your work! It is truly a great project!
Quick question on the
KeywordsStoppingCriteria
implementation. I see that it is a custom stopping criteria appended to other forms like EOSTokenCriteria,MaxLengthCriteria etc..As far as I understood, The
EOSTokenCriteria
used here looks if the predicted token is an EOS token which is151645
which I believe is the same as theKeywordsStoppingCriteria
functionality where the['<|im_end|>']
is tokenized as151645
. I feel they do the same thing. ReturnTrue
if the predicted token is151645
.I tried passing
None
tostopping_criteria
here and it did not change the behavior. Is there a reason we need both?The text was updated successfully, but these errors were encountered: