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

GhostNet architecture #4

Closed
RudyChin opened this issue Feb 26, 2020 · 1 comment
Closed

GhostNet architecture #4

RudyChin opened this issue Feb 26, 2020 · 1 comment

Comments

@RudyChin
Copy link

Hi,

According to the paper, you follow MobileNetV3 and replace bottleneck with G-bottleneck.
However, from the code, I think GhostNet is architecturally different from MobileNetV3.

For example, there is a layer in GhostNet with 48 #exp and 24 #out, which I couldn't find in MobileNetV3. Also, for the last few layers, MobileNetV3 has two 960 #exp and 160 #out layers but GhostNet has four of them. Moreover, in MobileNetV3 there are two 120 #exp and 40 #out layers while GhostNet only has one.

Can you explain why is this the case? How do you come up with this final architecture?
Have you tried directly replacing all the bottlenecks in MobileNetV3 to Ghost module without altering the base architecture?

Thanks,
Rudy

@iamhankai
Copy link
Member

Hi Rudy,

We basically followed MobileNetV3 architecture and made a few changes to suit for better latency on hardware. For Ghost module, smaller input size are more efficient than larger ones. Directly replacing all the bottlenecks in MobileNetV3 to Ghost module with the same FLOPs is about 1 ms slower.

Best,
Kai

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