Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Training starts from epoch 0 when using a run recovery object. #206

Closed
Shruthi42 opened this issue Sep 8, 2020 · 1 comment
Closed

Training starts from epoch 0 when using a run recovery object. #206

Shruthi42 opened this issue Sep 8, 2020 · 1 comment
Labels
bug Something isn't working
Projects

Comments

@Shruthi42
Copy link
Contributor

When continuing to train from a recovered run, the training run starts again from epoch 0. This has the side effect of causing the the inference run to use the run recovery object instead of the weights from the last epoch on the validation and test datasets.

@Shruthi42 Shruthi42 added the bug Something isn't working label Sep 8, 2020
@ant0nsc ant0nsc added this to To do in InnerEye Sep 10, 2020
@ant0nsc ant0nsc moved this from Backlog to Current Sprint in InnerEye Sep 22, 2020
@ant0nsc
Copy link
Contributor

ant0nsc commented Sep 28, 2020

Without supplying an additional --start_epoch=... argument, training will start from epoch 0. Documentation says that start_epoch must be supplied as well.

@ant0nsc ant0nsc closed this as completed Sep 28, 2020
InnerEye automation moved this from Current Sprint to Done Sep 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
No open projects
InnerEye
  
Done
Development

No branches or pull requests

2 participants