Standardize qa dataset naming and structure #876
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR addresses the issue of lengthy and unintuitive dataset names, such as "datasetname-test," "datasetname-test-tiny," "datasetname-dev," and "datasetname-dev-tiny." The proposed changes aim to adopt a more concise and informative naming format for better clarity.
To ensure consistency and clarity, this PR suggests standardizing key parameters, including datasource, split, and subset in dataset names. This standardization will make it easier for users to understand and work with the datasets.
Type of change
Please delete options that are not relevant.
Usage
Checklist:
pydanticfor typing when/where necessary.Screenshots (if appropriate):