Correctly update num_select during seg model finetuning
#399
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
When fine-tuning seg-preview model,
num_selectseems to be set to 200, but it is set to 300 like other detection models.It is due to that this parameter isn't set in
SegmentationTrainConfig, so it isn't updated correctly.With this fix,
num_selectis correctly updated to 200.Namespace(..., num_select=300, ...)Namespace(..., num_select=200, ...)Type of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
As adding
num_selectparameter inSegmentationTrainConfig, the argument inNamespaceis correctly updated like above.Any specific deployment considerations
NA
Docs