-
Notifications
You must be signed in to change notification settings - Fork 34
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
config for num_classes #25
Comments
Of course when I fintune it, I set num_classes as right the num of classes. And all is right. |
When I set num_classes = num of classes plus 1, so many boxes are predicted to be background, but AP and Recall increases while FNR decreases, which means the model is like to find the minority class better in my example. |
According to the logic of the code, it should be set to plus 1, but it is strange to have a complete lack of focus on most classes |
I found what happened! 80 object categories for coco. But I haven't find the document of them to check whether the category id is begin with 0 or 1.
|
I found it! The id of the object the author used is from 0 to 79, not 1 to 90 as I thought before. So just set num_classes as the num of your dataset, but check your annotation. |
Did you find why it does do +1? I have a dataset that has 1 class but it doesn't work when I set cum_classes to 1. It only works when I set it to 2 |
I am confused that do we need to set the background as a class. Cause most models for object detection like YOLO and DETR set num_classes to the original number of classes plus 1. Does DEIM also need plus 1?
Moreover, the question is, why is the num_classes configuration for COCO 80? Shouldn't it be 90 (+1)?
The text was updated successfully, but these errors were encountered: