Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Consistent train / dev split #15

Open
pokey opened this issue Oct 9, 2022 · 1 comment
Open

Consistent train / dev split #15

pokey opened this issue Oct 9, 2022 · 1 comment

Comments

@pokey
Copy link
Contributor

pokey commented Oct 9, 2022

It would be nice to have a consistent train / dev split between training runs, to make it less likely to inadvertently leak data between train / dev sets
@pokey pokey mentioned this issue Dec 23, 2022
Closed
@pokey
Copy link
Contributor Author

pokey commented Jan 17, 2023

See #29 for some discussion on how we'd like to split the data amongst members of the ensemble

@pokey pokey mentioned this issue Jan 17, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clean up data loading and randomization; add scheduler pokey/parrot.py
1 participant
@pokey