Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

tu-convnext_* with UNetPlusPlus throws runtime errors due to invalid weights with shape [0,x,y,y]#1054

tniranjan started this conversation inGeneral
Discussion options

I tried using any of the Timm convnext encoders with UNetPlusPlus, and always get the following runtime error: Given groups=1, expected weight to be at least 1 at dimension 0, but got weight of size [0,96,3,3] . (The 96 part changes depending on what size the encoder is). I believe this has to do with how theDecoderBlock out_channels are initialized. I poked around a bit and think this has to do with a difference in how encoder levels are generally initialized in backbones like ResNet/EffNet vstimm_encoder. If initialized with an encoder of depth 2, the problem disappears, but deeper Us have the problem.

You must be logged in to vote

Replies: 1 comment 1 reply

Comment options

Hey@tniranjan, thanks for opening discussion! At the moment Unet++ does not support transformers-like and convnext encoders, because feature map with H/2 resolution does no exist for them (the number of channels is 0).

Would appreciate a fix, in case you have bandwidth. The decoder should be adapted

You must be logged in to vote
1 reply
@tniranjan
Comment options

Thanks for the clarification. I am going to try.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
2 participants
@tniranjan@qubvel

[8]ページ先頭

©2009-2025 Movatter.jp