-
Notifications
You must be signed in to change notification settings - Fork 239
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
Bbox is 'Nan' when weights have 0 #44
Comments
The easiest solution is to remove predictions from ensemble you don't need to use (e. g. weight = 0). |
Yeah, that's right. |
I meant you can remove second set of boxes and set weights to weights=[1], then WBF will be applied to first set of boxes only. It's the equiualent to weights=[1, 0]. Looks like you have some of boxes intersected in the predictions of same model, so they fuse in process. |
Oh, thanks for your reply!
I will try it.
…---Original---
From: ***@***.***>
Date: Mon, Oct 11, 2021 21:51 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [ZFTurbo/Weighted-Boxes-Fusion] Bbox is 'Nan' when weights have 0 (#44)
I meant you can remove second set of boxes and set weights to weights=[1], then WBF will be applied to first set of boxes only. It's the equiualent to weights=[1, 0]. Looks like you have some of boxes intersected in the predictions of same model, so they fuse in process.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Hello, thanks for your nice work!
Recently, I used your method in my own project, and the mAP is improved indeed. However, When I check the JSON format result, most of the bounding boxes are Nan.
The below are the parameters:
iou_thr=0.5, skip_box_thr=0.01, weights=[1, 0]
when weights have 0, there will be warnings:
RuntimeWarning: invalid value encountered in true_divide box[4:] /= conf
But there are also 0 in the benchmark you have given.
Could you give me some suggestions?
Looking forward to your reply, Thanks!
The text was updated successfully, but these errors were encountered: