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

Dropout in ConvLSTM Cell #20063

Closed
dryglicki opened this issue Jul 30, 2024 · 5 comments · Fixed by #20089
Closed

Dropout in ConvLSTM Cell #20063

dryglicki opened this issue Jul 30, 2024 · 5 comments · Fixed by #20089
Assignees
Labels

Comments

@dryglicki
Copy link

Really quick question here.

In the ConvLSTMCell here, the dropout code has been commented out. recurrent_dropout also doesn't seem to do anything, except it is used in the DropoutRNNCell mixin.

Is this a bug or am I missing something?

@sachinprasadhs
Copy link
Collaborator

This code snippet was commented in the fix here 2cae421 to fix Conv LSTM correctness

@dryglicki
Copy link
Author

Hi @sachinprasadhs, can you be a little more clear with this explanation? What does "correctness" mean here, exactly?

I've been looking at the base RNN layer here: https://github.com/keras-team/keras/blob/master/keras/src/layers/rnn/rnn.py. Is the dropout now done under the hood?

In the Dropout Test here (https://github.com/keras-team/keras/blob/master/keras/src/layers/rnn/dropout_rnn_cell_test.py), those two calls aren't commented out.

@sachinprasadhs sachinprasadhs added the keras-team-review-pending Pending review by a Keras team member. label Jul 31, 2024
@hertschuh hertschuh self-assigned this Aug 5, 2024
@hertschuh hertschuh removed the keras-team-review-pending Pending review by a Keras team member. label Aug 5, 2024
hertschuh added a commit to hertschuh/keras that referenced this issue Aug 5, 2024
Implemented dropout and recurrent dropout in `ConvLSTMCell` with the same approach as in Keras 2.

Fixes keras-team#20063
Copy link

Are you satisfied with the resolution of your issue?
Yes
No

1 similar comment
Copy link

Are you satisfied with the resolution of your issue?
Yes
No

@hertschuh
Copy link
Contributor

@dryglicki ,

Thank you for the report. This was an oversight. It is now fixed.

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

Successfully merging a pull request may close this issue.

3 participants