init_model_from argument has no effect on where driver starts
EricZeiberg opened this issue · comments
It seems like, even when a checkpoint file is passed into --init_model_from argument, it starts from epoch 0.00 and acts like the initial model was never even passed in.
it's init_from, not resume_from. it loads in the weights but it doesnt actually resume the optimization exactly at the epoch it did before. instead it starts the counter at scratch. i decided that it would be slightly tricky and didn't have time to do it.
Oh alright