Add validation_interval to TrainConfig. Run validation and stats-logging every validation_interval. #452
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Closes: #449
Add
args.validation_intervaltoTrainConfig.During the training session, make evaluate() calls and stats-logging every
args.validation_interval.Setting
args.validation_intervalto a large value (e.g. equal to theargs.epochs + 1) essentially means we will not run theevaluate()operation throughout the training.Related:
#416
Type of change
How has this change been tested, please provide a testcase or example of how you tested the change?
Trained locally on
basketball-player-detection-2.v13i.coco.zipdataset using the a script.Test 1:
Train for 5 epochs with validation_interval=2.
Expected behaviour:
args.checkpoint_interval.Test 2:
Train for 5 epochs without any validation. Set validation_interval=6.
Expected behaviour:
args.checkpoint_interval.args.run_test === True, ascheckpoint_best_total.pthdoesn't exist.Any specific deployment considerations
None
Docs
None