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.

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

Add training configs to version control #613

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

dubslow
Copy link
Contributor

@dubslow dubslow commented May 16, 2018

So that we can track just what in the hell we were doing

@killerducky killerducky changed the base branch from master to next May 16, 2018 14:04
@dubslow
Copy link
Contributor Author

dubslow commented May 16, 2018

@Error323 I put old confs in by name, since we don't already have a version control history for them, but there's some discussion that this is kind of an ugly kludge. Is this okay with you, or should we stick to keeping only one live or current file? (And if the latter, how do we get the historical confs into git?)

@Error323
Copy link
Collaborator

Hi @dubslow sorry for keeping you waiting with this. I think the idea is good, but not in the main repo. Perhaps it would be better to create a log repo for this?

@dubslow
Copy link
Contributor Author

dubslow commented May 18, 2018

The training configs for the network should absolutely be in the main repo. Why shouldn't they be?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants