-
Notifications
You must be signed in to change notification settings - Fork 544
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 autoanchor
for YOLO series
#654
base: dev
Are you sure you want to change the base?
Conversation
configs/yolov5/autoanchor/yolov5_s-v61_syncbn_8xb16-300e_coco_aa.py
Outdated
Show resolved
Hide resolved
autoanchor
for YOLO series (with bug)
autoanchor
for YOLO series (with bug)autoanchor
for YOLO series
|
||
priority = 48 | ||
|
||
# YOLOAutoAnchorHook takes priority over EMAHook. |
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.
既然有这个要求,那么在这个hook初始化时候一定要记得打印下,说明这个hook优先级必须高于 emahook,提供更多信息
model = model.module | ||
|
||
device = next(model.parameters()).device | ||
anchors = torch.tensor( |
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.
这个地方应该用 model 内部属性比较好,而不是用配置。而且要写的鲁棒点
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.
直接用model.bbox_head.prior_generator.base_sizes 这样可以嘛?
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 for 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