Closed FrancoisPorcher closed 10 months ago
@FrancoisPorcher Hi, thank you for your interest in our work.
Thank you for your answer! However I am still confused on which model I should download, is it the last one on this picture?
Yes, co_dino_5scale_lsj_swin_large_16e_o365tolvis.pth
is the model that achieves 64.5 box AP on LVIS.
Alright thanks!
And this model has been pre trained on O365 and fine-tuned on LVIS right? But it has never been trained on COCO? Because there are some images of COCO training set that are in LVIS validation set
And also why is the performance given on LVIS val? Isn't it LVIS test that matters? Or maybe the API was broken on the test set? (It has already happened for COCO0
I think the config file indicated for SOTA LVIS lsj is not the right one. The model name mentioned in the config file is different from the one in the google drive above. Would you know more info about that? Thanks!
Alright thanks!
And this model has been pre trained on O365 and fine-tuned on LVIS right? But it has never been trained on COCO? Because there are some images of COCO training set that are in LVIS validation set
Yes, it is only finetuned on LVIS. We also evaluate our model on the LVIS minival set, a subset of the LVIS val that excludes all COCO training images.
And also why is the performance given on LVIS val? Isn't it LVIS test that matters? Or maybe the API was broken on the test set? (It has already happened for COCO0
We just follow the evaluation settings of previous frameworks, such as EVA and ViTDet, to enable clear performance comparisons.
I think the config file indicated for SOTA LVIS lsj is not the right one. The model name mentioned in the config file is different from the one in the google drive above. Would you know more info about that? Thanks!
Sorry, it is the config of the Swin-L model (Co-DETR + SwinL + O365 pretraining + LVIS finetuning). I will correct the config filename.
Okay nice! I can change it myself for now before you release the change since it's just the model path. However is the "base" compatible? Or do we have to change it as well?
Also could you please give a little more information about the backbone? You mentioned a 304 M parameters backbone. Is it EVA02 directly or is it something else? And did you only use the images of O365 for SSL or the bound boxes as well? Thanks a lot!!
Okay nice! I can change it myself for now before you release the change since it's just the model path. However is the "base" compatible? Or do we have to change it as well?
It is compatible.
Also could you please give a little more information about the backbone? You mentioned a 304 M parameters backbone. Is it EVA02 directly or is it something else? And did you only use the images of O365 for SSL or the bound boxes as well? Thanks a lot!!
It is EVA-02. O365 is used for detection pretraining (image+box).
Hi CO-DETR team, thank you for your great work!
I am a little confused on which checkpoint should I use to reproduce the SOTA results on LVIS. In the link you provided it seems that there are different folders and in each folder several models. Could you please clarify this?
Thanks!