-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Refactor] Refactor BEiT backbone and support v1/v2 inference #1144
Conversation
Codecov ReportBase: 0.02% // Head: 89.08% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #1144 +/- ##
============================================
+ Coverage 0.02% 89.08% +89.06%
============================================
Files 121 148 +27
Lines 8217 11384 +3167
Branches 1368 1812 +444
============================================
+ Hits 2 10142 +10140
+ Misses 8215 977 -7238
- Partials 0 265 +265
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. |
c7784a4
to
cae036c
Compare
6682914
to
bd05b79
Compare
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.
- please update API docs
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.
LGTM.
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
Related issue: #1097
Modification
BEiT v1
Official repo results


My results
BEiT v2
Official repo results


My results
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
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
Before PR:
After PR: