You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
1.Support RMosaic
(PS: Corresponding codes in mmdetection shows Mosaic must be used with RandomAffine. But I find Resize is also working. )
BC-breaking (Optional)
Does the modification introduce changes that break the back-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.
Mosaic-transform outputs twice the input images. And resize-transform convert them to original sizes, which means all gt-boxes are half of inputs'. So I choose to set the min_box_size to 10, corresponding to min_box_size(5) of randomrotate.
From the view of visualizations, there seems no problem. But I got bad performance as:
Maybe mosaic should be used with randomcrop, and I'll try it.
Mosaic-transform outputs twice the input images. And resize-transform convert them to original sizes, which means all gt-boxes are half of inputs'. So I choose to set the min_box_size to 10, corresponding to min_box_size(5) of randomrotate.
From the view of visualizations, there seems no problem. But I got bad performance as:
Maybe mosaic should be used with randomcrop, and I'll try it.
For mosaic and mixup, it should revert to orginal dataset in last few epoch, such as yolox in mmdet, you can have a try. I'm working on rrandom affine, it will release in few days.
Thanks for your explaining @liuyanyi . I'll have a try.
does mosaic transform should combine with mixup? if that ,could you give a sample?
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
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
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
1.Support RMosaic
(PS: Corresponding codes in mmdetection shows Mosaic must be used with
RandomAffine. But I findResizeis also working. )BC-breaking (Optional)
Does the modification introduce changes that break the back-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)
Use the train_pipeline as belowing:
Visualization
Checklist