leakyRelu feature as a part of Relu layer. #323
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svlandeg
added
enhancement
|
Thanks for the PR. I'm thinking about the best way to do this: I'm trying to decide whether we should have the parameter in the op or not. I think I'd probably prefer a different op for the leaky vs non-leaky relu, instead of a parameter. This also makes the naming easier. |
|
I do think I'd prefer to have this as a separate operation, instead of a parameter, so I'll close this. I'm sure your implementation will be helpful in adding a leaky relu op though, thanks again 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is in line with #322. Have implemented Leaky Relu as a parameterized option inbuilt within Relu. Use the optional parameter "alphaLeaky" to use it.