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

Problem of oaieval.py #243

Closed
JimmyfaQwQ opened this issue Mar 16, 2023 · 3 comments
Closed

Problem of oaieval.py #243

JimmyfaQwQ opened this issue Mar 16, 2023 · 3 comments

Comments

@JimmyfaQwQ
Copy link

The oaieval.py still preformed the very first version of the dataset after I updated the jsonl file as the program only execute one item while I have three in my dataset.
It looks like the first version had been cached, cause the content in log file created by record.py also didn't the match the dataset, but the content of the first version of my dataset (which means the log file contain content various from dataset).
How can I help with this?

@samclane
Copy link

samclane commented Mar 16, 2023

I'm currently having the same problem. I'm unsure of how to clear the cache to get it to "see" my new jsonl file. I've tried to change the name of the test to no avail

EDIT: After running with --debug, I found it was loading a pkl file from my /tmp folder. After deleting it I got it to run all my samples.

@aaronsmithtv
Copy link
Contributor

The behaviour is explained in custom-eval.md:

If you notice evals has cached your data and you need to clear that cache, you can do so with rm -rf /tmp/filecache.

This will be a difficult spot for people looking through custom-eval I think. I've also noticed that the flag --no-cache exists in the list of oaieval options. I'm not sure if this is intended to prevent .jsonl files from being cached (which would be a nice feature), but as far as I can tell the code associated with the arg isn't doing anything:

evals/evals/cli/oaieval.py

Lines 173 to 175 in 19bfdba

api_extra_options = {}
if not args.cache:
api_extra_options["cache_level"] = 0

Though of course @andrew-openai will know a lot more than I do!

@JimmyfaQwQ
Copy link
Author

Thanks, it helps.

The behaviour is explained in custom-eval.md:

If you notice evals has cached your data and you need to clear that cache, you can do so with rm -rf /tmp/filecache.

This will be a difficult spot for people looking through custom-eval I think. I've also noticed that the flag --no-cache exists in the list of oaieval options. I'm not sure if this is intended to prevent .jsonl files from being cached (which would be a nice feature), but as far as I can tell the code associated with the arg isn't doing anything:

evals/evals/cli/oaieval.py

Lines 173 to 175 in 19bfdba

api_extra_options = {}
if not args.cache:
api_extra_options["cache_level"] = 0

Though of course @andrew-openai will know a lot more than I do!

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

3 participants