Repository navigation
Separate dataset seeding from training seeding - #110
Merged
Merged
Conversation
michaelmckinsey1
force-pushed
the
dataset-seed
branch
from
October 1, 2026 18:37
cbba552 to
73f6315
Compare
ndryden
approved these changes
Oct 3, 2026
This file contains hidden or 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.
PR92 Enabled forced creating seeded datasets, but no way to separate the dataset seed and training seed. Using different dataset seeds creates datasets that vary in difficulty. For scaling data stability, I am enabling setting the dataset seed separately from the training seed, which reduces variability between seeds by ~5x.
Users can still vary the dataset seed and training seed together if they wish.
before (3 different dataset seeds and training seeds)
after (1 dataset seed, 3 training seeds)