-
Notifications
You must be signed in to change notification settings - Fork 42
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
In the case all class scores are lower than self.cls_threshold_to_reg. #9
Comments
If the parameter |
Yes, I have utilized the pre-trained model "fcos3d.pth" but I still meet the error. Can you train "sparse4d_r101_H1.py" without meeting any error? |
I wrote some code to prevent alerting the bug and print a warning text every time it meets this case. And find that even in the 24th epoch I can still meet this case. |
I did not encounter this problem. Is your batch_size not large enough? I used 8gpus*1sample_per_gpu. |
It shouldn’t be considered a bug if all of them are false. Some samples may not have valid object, as long as it does not affect the convergence of loss |
If you have concerns, just set this parameter to -1. It will not have a significant impact on the model effect |
Yes, you are right. The reason I open this issue is that when I am evaluating the model at the 24th epoch, the mAOE is weird, as shown below. So I'm just wondering if this case causes the weird result.
|
This phenomenon seems to be a problem with the annotation of yaw. It is recommended that you visualize the GT of the training data. |
OK, thank you for your timely reply. I will close this issue. |
hi,I meet the same
hi,I met the same problem at the 24th epoch,have you solved it? |
If you are using the code of sparse4dv1 or sparse4dv2, update the version of mmdet3d >= rc1.0.0. @bobyang7 |
Dear author @linxuewu ,
This is really a nice work! However, when training "sparse4d_r101_H1" I will always meet a bug at these lines of code.
Sparse4D/projects/mmdet3d_plugin/models/sparse4d_head.py
Lines 257 to 277 in 2154d91
Where, the resulting mask is all False, causing an empty "reg_target".
The text was updated successfully, but these errors were encountered: