Making perplexity calculations consistent across sample length - #27
Open
mcleish7 wants to merge 1 commit into
Open
Making perplexity calculations consistent across sample length#27mcleish7 wants to merge 1 commit into
mcleish7 wants to merge 1 commit into
Conversation
|
|
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
2 participants
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.
When calculating perplexity, on lines 110 and 115 the code currently divides by
len(token_probs)which is twice the length oftoken_probs[mid_index:]asmid_index = len(token_probs) // 2but then on line 120, for the whole sequence, the code still divides bylen(token_probs).This means the is a slight inconsistency in the perplexity calculation.
I have corrected this by using a single function cases, also removing the repeated code.