-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Feature] Add with cp to mit and vit #1431
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1431 +/- ##
==========================================
+ Coverage 90.22% 90.34% +0.12%
==========================================
Files 136 139 +3
Lines 7946 8300 +354
Branches 1323 1393 +70
==========================================
+ Hits 7169 7499 +330
- Misses 552 564 +12
- Partials 225 237 +12
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@jiangyitong |
…into mit_vit_with_cp
Look Good To Me. I would make channel number, width and height of input and weight of model smaller in unit test to pass CI more quickly in the other pr. |
* add with cp to mit and vit * add test unit Co-authored-by: jiangyitong <jiangyitong1@sensetime.com>
* add with cp to mit and vit * add test unit Co-authored-by: jiangyitong <jiangyitong1@sensetime.com>
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
Support with cp for mit and vit backbone
Modification
add with_cp parameter and modify the transformerencoder
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)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist