-
Notifications
You must be signed in to change notification settings - Fork 532
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
Small question about Xnet vs Nestnet difference #31
Comments
I think xnet is the real UNet++. nestnet doesn't connect current layer to all previous layers . Therefore,the accuracy of the nestnet is not as high as xnet. And I think there is also something wrong with xnet,even if I'm not sure. |
Hey @zsk-tech thank you for your input. I agree that the connections are different.. What we can say is it makes a difference in the number of trainable parameters.
I was also confused by the filters of the additional decoder skip connections. Where did you see the author using [32 64 128 256 16] number of filters?
But maybe you looked into what actually happens in |
Thank you for your explanation. Q: Where did you see the author using [32 64 128 256 16] number of filters? A: I derived it from the code in build_xnet.But it is also possible that my understanding of the code is incorrect. |
Okay that makes sense, I'll try to look at it when I find the time and report back! The |
OKay |
The only architectural difference between the two seems to be this:
skip=interm[(n_upsample_blocks+1)*i+j]
skip=interm[(n_upsample_blocks+1)*i: (n_upsample_blocks+1)*i+j+1]
in the
upblock
parameters.can someone confirm this and maybe quickly explain how this affects the model?
would they both count as Unet++ architecture according to the paper but with different skip connections?
The text was updated successfully, but these errors were encountered: