You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using a ResNet-18 backbone (ResNetEncoder), I do not undestand why the decoder achieved using a UNet or FPN architecture is not symetrical ... I attach the summary of a UNetDecoder which only consists of 3M parameters, instead of the 11M related to the encoder. Where is the problem? How can I made the decoder completely symmetrical?
The input of the decoder should be the 8x8x512 feature maps ... but I receive the original image as input 256x256x3. Why?
The text was updated successfully, but these errors were encountered:
bobetocalo
changed the title
My encoder-decoder shows asymmetrical architectures
My encoder-decoder shows asymmetrical architectures (using torchinfo package)
Oct 8, 2024
Hi! It's not an original Unet implementation. Orignal one uses VGG encoder as far as I remember, however, newer encoders provide much better results. You can increase the number of channels in decoder to increase the number of parameters with decoder_channels=(...), see https://smp.readthedocs.io/en/latest/models.html#unet
Using a ResNet-18 backbone (ResNetEncoder), I do not undestand why the decoder achieved using a UNet or FPN architecture is not symetrical ... I attach the summary of a UNetDecoder which only consists of 3M parameters, instead of the 11M related to the encoder. Where is the problem? How can I made the decoder completely symmetrical?
The input of the decoder should be the 8x8x512 feature maps ... but I receive the original image as input 256x256x3. Why?
The text was updated successfully, but these errors were encountered: