Add detector_eval_interval to train_from_coco - #3436
Open
juan-cobos wants to merge 1 commit into
Open
Conversation
…t of fixed eval_interval=10 for the detector as in base config
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Enable to select eval interval for the detector when running adaption_train inside train_from_coco. Currently, there is an eval_interval param which only applies to the pose estimation head. I patched it by adding a new parameter which allows to change eval interval for the detector too. Alternatively, you could standardize eval_interval for both, but I followed the current approach of "detector_" prefix params.