-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix] Switch order of reduce_zero_label
and applying label_map
in 1.x
#2517
[Fix] Switch order of reduce_zero_label
and applying label_map
in 1.x
#2517
Conversation
reduce_zero_label
and applying label_map
in 1.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we are still working on fixing ci. :(
we have fixed ci problem in #2519 and please rebase this modification on it |
…l-map-reduce-zero-order-1.x
Great! Merged the latest version of |
Codecov ReportBase: 83.39% // Head: 83.40% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #2517 +/- ##
===========================================
+ Coverage 83.39% 83.40% +0.01%
===========================================
Files 145 145
Lines 8510 8510
Branches 1274 1274
===========================================
+ Hits 7097 7098 +1
+ Misses 1198 1197 -1
Partials 215 215
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
* Sequential cpu offload: require accelerate 0.14.0. * Import is_accelerate_version * Missing copy.
… 1.x (open-mmlab#2517) This is an almost exact duplicate of open-mmlab#2500 (that was made to the `master` branch) now applied to the `1.x` branch. --- ## Motivation I want to fix a bug through this PR. The bug occurs when two options -- `reduce_zero_label=True`, and custom classes are used. `reduce_zero_label` remaps the GT seg labels by remapping the zero-class to 255 which is ignored. Conceptually, this should occur *before* the `label_map` is applied, which maps *already reduced labels*. However, currently, the `label_map` is applied before the zero label is reduced. ## Modification The modification is simple: - I've just interchanged the order of the two operations by moving a few lines from bottom to top. - I've added a test that passes when the fix is introduced, and fails on the original `master` branch. ## BC-breaking (Optional) I do not anticipate this change braking any backward-compatibility. ## Checklist - [x] Pre-commit or other linting tools are used to fix the potential lint issues. - _I've fixed all linting/pre-commit errors._ - [x] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness. - _I've added a unit test._ - [x] If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMDet3D. - _I don't think this change affects MMDet or MMDet3D._ - [x] The documentation has been modified accordingly, like docstring or example tutorials. - _This change fixes an existing bug and doesn't require modifying any documentation/docstring._
This is an almost exact duplicate of #2500 (that was made to the
master
branch) now applied to the1.x
branch.Motivation
I want to fix a bug through this PR. The bug occurs when two options --
reduce_zero_label=True
, and custom classes are used.reduce_zero_label
remaps the GT seg labels by remapping the zero-class to 255 which is ignored. Conceptually, this should occur before thelabel_map
is applied, which maps already reduced labels. However, currently, thelabel_map
is applied before the zero label is reduced.Modification
The modification is simple:
master
branch.BC-breaking (Optional)
I do not anticipate this change braking any backward-compatibility.
Checklist