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.

Sign up for GitHub

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

Jump to bottom

[FT] More general approach than output_regex to model answer extraction #360

Open
sadra-barikbin opened this issue Oct 14, 2024 · 0 comments · May be fixed by #358
Open

[FT] More general approach than output_regex to model answer extraction #360

sadra-barikbin opened this issue Oct 14, 2024 · 0 comments · May be fixed by #358
Labels
feature request New feature/request

Comments

@sadra-barikbin
Copy link
Contributor

Hi there!

Currently, we can specify an output_regex in the task config to extract the model answer from its generated content. This config option is used in apply_generative_metrics.

We could replace output_regex with an answer extractor object that performs arbitary operations to extract the answer. For example, that of MMLU-Pro is as follows:

image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature/request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

A more general solution to model answer extraction instead of output_regex sadra-barikbin/lighteval
1 participant
@sadra-barikbin