-
Notifications
You must be signed in to change notification settings - Fork 251
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
Is v0.4.3 nnom.py support sigmoid? #183
Comments
For sigmoid, please use Sigmoid layer instead of Activation("sigmoid") at the moment |
Sorry, I can't find how to use Sigmoid layer, but tf.keras.activations.sigmoid() which produce Lambda layer. Did I miss something? |
Is this the right fix, just to add sigmoid to is_shift_layer ? Or are there other complications? Btw, a workaround might be to use hard_sigmoid, it appears to be implemented |
sigmoid is already implemented, try replace act_hard_sigmoid() with act_sigmoid().
…---- Replied Message ----
| From | Jon ***@***.***> |
| Date | 03/30/2024 11:20 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [majianjia/nnom] Is v0.4.3 nnom.py support sigmoid? (Issue #183) |
Is this the right fix, just to add sigmoid to is_shift_layer ? Or are there other complications?
Btw, a workaround might be to use hard_sigmoid, it appears to be implemented
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
My model use sigmoid activation like:
activation = 'sigmoid'
output = Activation(activation)(input)
and I use generate_model() in nnom.py to convert model.
I think should add
('activation' in layer.name and layer.get_config()['activation'] == 'sigmoid')
to function is_shift_layer() .
The text was updated successfully, but these errors were encountered: