Skip to content
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

About SE layer in Fused-MBConv #5

Closed
Noir97 opened this issue Apr 21, 2021 · 4 comments
Closed

About SE layer in Fused-MBConv #5

Noir97 opened this issue Apr 21, 2021 · 4 comments

Comments

@Noir97
Copy link

Noir97 commented Apr 21, 2021

截屏2021-04-21 下午3 32 37

I understand that the SE layer might get removed in the original fusion attempt: https://ai.googleblog.com/2019/08/efficientnet-edgetpu-creating.html

But according to Fig2 in the paper, it seems like the SE layer is preserved in the Fused MBConv. So I am quite confused when I found the SE layer lacking in your implementation. Have you ever tried the implementation with SE layer, or am I missing something in the paper?

@Noir97
Copy link
Author

Noir97 commented Apr 21, 2021

OK...I guess the missing SE parameter in the architecture table implies that. Nevermind.

@Noir97 Noir97 closed this as completed Apr 21, 2021
@xiaoerlaigeid
Copy link

OK...I guess the missing SE parameter in the architecture table implies that. Nevermind.

I also notice this implementation lack of SE layer in Fused MBConv. Could further explain about this ?

@Noir97
Copy link
Author

Noir97 commented May 14, 2021

OK...I guess the missing SE parameter in the architecture table implies that. Nevermind.

I also notice this implementation lack of SE layer in Fused MBConv. Could further explain about this ?

截屏2021-05-14 下午12 44 19

In the architecture table, "SE" shows up but only with normal MBConv, I guess that means it is not used with Fused MBConv

@xiaoerlaigeid
Copy link

Oh thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants