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.
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
Improved random seed configuration for Lhotse dataloaders with docs #9001
Improved random seed configuration for Lhotse dataloaders with docs #9001
Changes from 4 commits
7b03d3b
08d8a84
250266b
45ab785
7add45b
9905eda
ad895d6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the recommended practice on managing the "seed" on large data setup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally every time you resume, you'd provide a different value to
model.train_ds.seed=<val>
. A true-enough random seed can be obtained on most systems by reading /dev/urandom, e.g. uint32 seed:RSEED=$(od -An -N4 -tu4 < /dev/urandom | tr -d ' ')
. If you have some sort of "launcher script" that queues multiple jobs, this would be the right place to use this. Let me update the docs with this example.Ideally we'd be able to automate this seed management thing by keeping some state in the checkpoints, but at this point it'd be a scope creep.