-
Notifications
You must be signed in to change notification settings - Fork 44
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
Exact accuracies on miniF2F be presented more clearly? #123
Comments
|
Hi Brando! By exact accuracy you means the accuracy breaking down to each statement, or the sota accuracy like the paper you mentioned here? |
yes, like the examples ones I provided. Let me know if you have other thoughts. Thanks!
…-----
Brando Miranda
Ph.D. Student
Computer Science, Stanford University
EDGE Scholar, Stanford University
***@***.******@***.***>
website: https://brando90.github.io/brandomiranda/home.html
On Nov 1, 2022, at 6:01 PM, Kunhao ZHENG ***@***.******@***.***>> wrote:
Hi Brando! By exact accuracy you means the accuracy breaking down to each statement, or the sota
accuracy?
—
Reply to this email directly, view it on GitHub<#123 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAOE6LXIQKDB2QX2WURWRWLWGG4P5ANCNFSM6AAAAAARTXNYWE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I can provide several paper that I know reporting accuracies on miniF2F, more or less in chronological order. The list may be incomplete and any fix welcome!
As the accuracies (pass-rate) are usually subject to the computation budget and the language. I only put the number on test split here, for the number of validation split it worth taking a look at the details in these paper. |
No description provided.
The text was updated successfully, but these errors were encountered: