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
README: Faster RCNN fp16 config link fix #9366
Conversation
README: Faster RCNN fp16 config link fix
Hi @apatsekin , |
Codecov ReportBase: 64.19% // Head: 64.17% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev #9366 +/- ##
==========================================
- Coverage 64.19% 64.17% -0.03%
==========================================
Files 361 361
Lines 29544 29583 +39
Branches 5023 5033 +10
==========================================
+ Hits 18966 18984 +18
- Misses 9570 9590 +20
- Partials 1008 1009 +1
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. |
* README: Faster RCNN fp16 config link fix README: Faster RCNN fp16 config link fix * Update README.md * Update README.md Co-authored-by: Yue Zhou <592267829@qq.com>
README: Faster RCNN fp16 config link fix
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
Please briefly describe what modification is made in this PR.
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