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

Why the non-linearity in the last layer? #245

Closed
marcelodiaz558 opened this issue Nov 8, 2020 · 0 comments
Closed

Why the non-linearity in the last layer? #245

marcelodiaz558 opened this issue Nov 8, 2020 · 0 comments

Comments

@marcelodiaz558
Copy link

Hi,
I don't understand why developers decided to include a swish non-linearity in the architecture right after the fully connected classifier layer, I don't think that it's good choice for an image classification task since swish will throw out some information that might be important, just like ReLU does with negative values. Most likely I'm wrong and there's some good reason to do this, can anyone please explain this to me?

This is how the network forward propagation ends:

(_fc): Linear(in_features=1280, out_features=1000, bias=True) (_swish): MemoryEfficientSwish()

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

1 participant