possible bug

[denkorzh]

mixedillWB/src/gridnet.py

Line 150 in aeee3b8

x_latent = res_blck(latent_x)

You seem to use the same latent_x for all columns of the decoder part. I suggest this is a bug in your implementation of GridNet.

[mahmoudnafifi]

Thanks for your comment. At first res block, x_latent is returned "if j == 0: x_latent = res_blck(latent_x)", then for next blocks I use x_latent. It is bad naming i agree, but it looks not an implementation bug to me.

[denkorzh]

the line I pointed to is NOT under if j == 0

[denkorzh]

As far as I understand, for j>0 you do not process the *processed*, you process *the same* encoder output `latent_x`with a new residual block. Thefore, the output of the previous residual block in the decoder row is just unemployed. ср, 16 мар. 2022 г., 20:04 Mahmoud Afifi ***@***.***>:

…

yes I understand your point. Res_blocks are arranged horizontally. Each row received the processed latent from encoder and process it sequentially. If we are at the beginning of the row, then we retrieve the encoder latent of this row once and process it, otherwise we process the processed latent in this row: if j == 0: latent_x = latent_forward[k] x_latent = res_blck(latent_x) Makes sense? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACV4QJMW4L66KY26TG37UJDVAIIBDANCNFSM5Q332ESA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[mahmoudnafifi]

I checked the code carefully and yes you are right. It should be x_latent. It means the current implementation practically has a single decoder column. I will not change it to make trained models work as trained. But let's keep this issue open to help people find out.

[mahmoudnafifi]

Updated readme and referred to this issue. Thanks @denkorzh!

[denkorzh]

You're welcome!