Data split depending on eval params #169
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
…ls in one single step
… to fit user conditions if needed
NathanHB
reviewed
Apr 30, 2024
NathanHB
reviewed
Apr 30, 2024
NathanHB
reviewed
Apr 30, 2024
Co-authored-by: Nathan Habib <[email protected]>
Co-authored-by: Nathan Habib <[email protected]>
|
TODO: check this again after the merge |
NathanHB
reviewed
Jul 10, 2024
NathanHB
reviewed
Jul 10, 2024
NathanHB
reviewed
Jul 10, 2024
NathanHB
reviewed
Jul 10, 2024
clefourrier
commented
Jul 10, 2024
clefourrier
commented
Jul 10, 2024
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.
This PR needs #158 to be merged first.
The main problem is that splits are no longer by size, but they are however now making sure that all batched generative evals are launched with similar evals (same sampling, same eos tokens)