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

How to choose the best checkpoint? #110

Closed
hajlyx opened this issue Dec 19, 2019 · 4 comments
Closed

How to choose the best checkpoint? #110

hajlyx opened this issue Dec 19, 2019 · 4 comments

Comments

@hajlyx
Copy link

hajlyx commented Dec 19, 2019

Choose final checkpoint or checkpoint with lowest val loss, which is better?

Assume the val set has 20 patients.

Best.

@FabianIsensee
Copy link
Member

There is no hard rule to that. You will never really know because you need to pick one and then evaluate on the test set only once. If I were you I would look at the plot. If the evaluation metric goes up and then back down again I would use the best. If not I would use final.
Best,
Fabian

@hajlyx
Copy link
Author

hajlyx commented Jan 2, 2020

There is no hard rule to that. You will never really know because you need to pick one and then evaluate on the test set only once. If I were you I would look at the plot. If the evaluation metric goes up and then back down again I would use the best. If not I would use final.
Best,
Fabian

Thanks for reply.

Another question is about ensemble strategy. It seems that in nnUNet we just use the mean value of outputs from five fold trained model. Is there a more robust and elegant ensemble strategy?

Best.
Wayen.

@FabianIsensee
Copy link
Member

There are certainly better ways to do it. Here I just average and it works well enough. You can choose to do this differently
Best,
Fabian

@hajlyx
Copy link
Author

hajlyx commented Jan 7, 2020

Thanks.

I'm going to look for different ways.

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