leela-chess
leela-chess copied to clipboard
Add training configs to version control
So that we can track just what in the hell we were doing
@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?)
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?
The training configs for the network should absolutely be in the main repo. Why shouldn't they be?