Skip to content
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

Clarification request on pass@k metric #3

Open
kang-0909 opened this issue Mar 10, 2024 · 1 comment
Open

Clarification request on pass@k metric #3

kang-0909 opened this issue Mar 10, 2024 · 1 comment

Comments

@kang-0909
Copy link

kang-0909 commented Mar 10, 2024

Hi, I'm a little confused about the "pass@k" metric in the paper.

It appears that on APPS you reported test case average (unstrict accuracy), although you referred to the "proportion of problems successfully solved" as the pass@k metric, which is the widely recognized definition. However, the accuracies of CodeRL, WizardCoder in table 4,5 seem to be strict.

Could you clarify which metric is being used for evaluation? Your confirmation would be greatly appreciated. Thank you.

@JulietLJY
Copy link
Member

Thank you for bringing this to our attention. We have aligned the metrics and update the tables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants