-
Notifications
You must be signed in to change notification settings - Fork 592
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
Problems about JS=1 & DC>1 #41
Comments
DC and JS give possible values when I change evaluation function to (eg. DC)
So basicly just change torch.max() to original array max, maybe there is something wrong here?
|
Seems the problem is solved, so I'd close this issue. Again, thank you for your contribution! |
Hi, @Yiyiyimu |
@Yiyiyimu |
First of all, thank you for your code where I do learned a lot from. I work on a dataset looks like isic2018 where only got one category and around 900 images for training.
But I occur to a problem that when training, JS would keep equal to 1 and DC would even keeps greater than 1. I can't find reason since normalization in data_loader has already make sure DC could not larger than 1. Do you have any ideas?
I noticed things would happens when I use R2Unet and when SR output is totally black(nothing is divided out), maybe that would be helpful to find out where got something wrong.
Another problem is it seems the model cannot learn things during epoches processing, the best model would come out in first 5 epoches when training for like 200 epoches. Is that because model would get better result on small set and when it generalized to more images the score would drop?
By the way, implementing only U-net would not get DC>1 and get some result.
Thank you in advance for your help~
Edit:
Just found out JS would also stuck on 1.0 and DC greater than 1 when training Attention U-net but this time it get some result. So it maybe just JS and DC calculation problem
No way this time same situation happens to U-net and I changed nothing...
The text was updated successfully, but these errors were encountered: