fix: successor_liability task gets evaluated on balanced_accuracy instead of F1#44
Open
KensingtonOscupant wants to merge 1 commit intoHazyResearch:mainfrom
Open
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
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.
Hi there!
I was working on something and noticed that when using
evaluate()fromevaluation.py, thesuccessor_liabilitytask gets evaluated on balanced accuracy. I believe it is meant to be evaluated on F1, cf. section 5.1.3 of the paper.The evaluation mismatch happens because
successor_liabilityis an item in theEXACT_MATCH_BALANCED_ACClist inevaluation.py. This causes an unintended early return at the top of theevaluate()function:So in case of
successor_liability,return evaluate_successor_liability(generations, answers)is never reached.I hope this helps!