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

way to calculate F score #31

Open
fujenchu opened this issue Jun 12, 2018 · 6 comments
Open

way to calculate F score #31

fujenchu opened this issue Jun 12, 2018 · 6 comments

Comments

@fujenchu
Copy link

Hi Dr. Nguyen,

It is a really nice work! Thank you.
Would you mind to provide script to compute the F score in the paper? I would like to evaluate the performance for my own dataset set. Or it is in the repo and I overlooked it? It would be great if I could borrow the code from you.

Thank you very much.

@nqanh
Copy link
Owner

nqanh commented Jun 13, 2018

@fujenchu
Copy link
Author

Cool! Thanks for your reply. I just got it working.

@fujenchu fujenchu reopened this Aug 22, 2018
@fujenchu
Copy link
Author

Hi Dr. Nguyen,

I just realized that previous works evaluated their approaches by first cropping images with ground truth mask for bounding boxes. I am wondering if you follow the same procedure (cropping the region of interest) or you pass the whole images for F score to get the results described in the paper? Thank you very much.

@nqanh
Copy link
Owner

nqanh commented Aug 23, 2018

We pass the whole image and evaluate F score. Please see paper for more details.

@fujenchu
Copy link
Author

I see. Thank you very much!
I've read the paper and we are wondering how many epochs you have trained on UMD dataset for getting the results? It seems the hyperparameters in the repo are for IIT. Would you mind to provide the hyperparameters for UMD if possible? It seems stepsize of 150k in solver.prototxt is large for UMD given the dataset size. Thank you in advance!

@nqanh
Copy link
Owner

nqanh commented Aug 23, 2018

You can just train then stop when the lost doesn't decrease anymore :)

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