Add dataset support for .tsv
files
#637
Merged
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.
This PR contains:
What is the current behavior? (You can also link to an open issue here)
.tsv
files properly.csv
and.tsv
files without a headerMGSM dataset uses tab-separated file format without a header.
See simple-evals/mgsm_eval.py
This functionality would help add MGSM to
inspect_eval
(see UKGovernmentBEIS/inspect_evals#3 )What is the new behavior?
fieldnames
is added tocsv_dataset
. By default it is None, which preserves backward compatibility. This parameter is passed directly into csv.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking changes.
Other information:
This is how I currently use
csv_dataset
:I am not very familiar with the codebase. Tests are passing, but not 100% that this will not break anything.