-
Notifications
You must be signed in to change notification settings - Fork 153
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
SPPF
will generate nodes with duplicate names
#234
Comments
Hi @SarBH , Thanks for reporting and providing this information!
The origin of this change is in upstream YOLOv5 ultralytics/yolov5#4420, the EDITED: A detailed test about the SPPF vs SPP - ultralytics/yolov5#4420 (comment) .
Actually, I don't quite understand the phenomenon that occurs here, could you provide me with more information, or a reproducible example? (I also have some interest in If the above change affects the use of downstream application, we can revert this change back or we can work together to find a better way to handle this scenario. |
Thanks for the follow up @zhiqwang, and for this awesome project! I investigated where exactly pruning is failing: the compressor.py file asserts that
The old hash’s model that doesnt fail prunning actually splits that ** Note: We are using an older version of nni package |
Got it, Thanks for the details informations, it is very useful. I agree with you, we will revert this substitution it this two days. |
Hi @SarBH , I revert the Please reinstall the pip install -U 'git+https://github.com/zhiqwang/yolov5-rt-stack.git' Thanks for the detailed information again, feel free to reopen this or create another ticket if you have more questions. |
Hello @SarBH , I encountered the same problem as you when using nni2.6. Considering the reason of sppf, I decided to use the yolov5 version 5, because the old version still uses the basic spp module, but the pruning process appeared new error, have you succeeded in pruning yolov5?
|
SPPF
will generate nodes with duplicate names
Hi, @zhiqwang @syswyl |
🐛 Describe the bug
Somewhere between these two commits there was a model backbone change: 06022fd...e3e18f2. The three MaxPool2d at
backbone.body.8.m.0, backbone.body.8.m.1, backbone.body.8.m.2
go from being parallel to being serialized in the later hash into justbackbone.body.8.m
with three outputs. (I'm usingnni==2.4
to prune the model, and a node with three outputs is a problem for that)For example, the SMALL model.
On the left: commit hash 06022fd, default upstream_version = r4.0
On the right: commit hash e3e18f2, default value for upstream_version changed with the addition of
r6.0
, so I set theupstream_version=r4.0
explicitly.I see the same behavior for
'yolov5s', 'yolov5m', 'yolov5l'
All else in the models remained the same, therefore I wondered if this was accidental.
Versions
The text was updated successfully, but these errors were encountered: