[Feature] add -with-labels arg to inferencer for visualization without labels #3466
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.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
It is difficult to visualize without "labels" when using the inferencer.
MMSegInferencer
, the visualized prediction contains labels on the mask, but it is difficult to passwithLabels=False
without rewriting the config (which is harder to do when you initialize the inferencer with a model name rather than the config).withLabels=False
toinferencer.__call__()
since you can also passopacity
and other parameters anyway.Modification
Please briefly describe what modification is made in this PR.
with_labels
tovisualize_kwargs
insideMMSegInferencer
.visualize()
function.-with-labels
args toimage_demo.py
andimage_demo_with_inferencer.py
scripts.BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
Checklist