Skip to content
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

Bad results on COCO dataset #10

Closed
zhangyuxuan321 opened this issue Sep 7, 2022 · 5 comments
Closed

Bad results on COCO dataset #10

zhangyuxuan321 opened this issue Sep 7, 2022 · 5 comments

Comments

@zhangyuxuan321
Copy link

Sorry to bother u, when I reproduct on Voc, it's the same results on Voc datasets you gave in your paper. But when I reproduct your methods on the CoCo dataset, using the exactly same hyperparameters, the results are much lower than those in the paper. I have tried a lot of time, but it always does. I can't figure out that problem, could you please give me some advice?
image
image
Above is the shell script of PIFS* running on the strict incremental few shot setting.

@fcdl94
Copy link
Owner

fcdl94 commented Sep 7, 2022

Hey! The first thing that comes to my mind is the dataset. Have you correctly pre-processed the data as written in the README?

@zhangyuxuan321
Copy link
Author

Hey! The first thing that comes to my mind is the dataset. Have you correctly pre-processed the data as written in the README?
I do pre-process the data according to the README, which is the make_annotation.py.
But I find there is two coco directories, one is COCO , another is COCO-stuff, I choose the COCO one
image
Is that a mistake? Thanks a lot for your quick reply and your great work!

@fcdl94
Copy link
Owner

fcdl94 commented Sep 7, 2022

It's hard to tell because it depends on how you named them while downloading and processing. Can you open an image and see if it has all the pixels belonging to stuff at class 0?

@fcdl94
Copy link
Owner

fcdl94 commented Sep 7, 2022

Anyway, yes, you need to use the file in the coco folder, not in coco stuff.

@zhangyuxuan321
Copy link
Author

Thanks a lot, I figure out that problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants