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

Question on fluid.layers.dynamic_lstm #12845

Closed
jczaja opened this issue Aug 21, 2018 · 2 comments
Closed

Question on fluid.layers.dynamic_lstm #12845

jczaja opened this issue Aug 21, 2018 · 2 comments
Assignees

Comments

@jczaja
Copy link
Contributor

jczaja commented Aug 21, 2018

Hi,

I have question of returned values of fluid.layers.dynamic_lstm. According to :
http://paddlepaddle.org/documentation/api/en/0.14.0/layers.html#dynamic-lstm

dynamic_lstm does return hidden state as well as cell state. My questions are:

  1. what is the intention of returning cell state by dynamic_lstm?
  2. In what situation it can be useful for a model to have an access to cell state when using dynamic_lstm?
  3. Can you point me fluid model that is actively(not ignoring) using cell state as returned by dynamic_lstm ?

Best Regards,

@luotao1
Copy link
Contributor

luotao1 commented Aug 22, 2018

Discussed with @qingqing01 :

what is the intention of returning cell state by dynamic_lstm

  1. In what situation it can be useful for a model to have an access to cell state when using dynamic_lstm?
  2. Can you point me fluid model that is actively(not ignoring) using cell state as returned by dynamic_lstm?

There is no fluid model using cell state now.

@jczaja
Copy link
Contributor Author

jczaja commented Aug 22, 2018

Thanks @luotao1,

Meantime I found an additional argument after having cell state returned via python interface which is
that if sequence is to long to have it processed at once via dynamic_lstm then it could be split into multiple execution of dynamic_lstm's and returning cell_state as well as providing input c0 will allow this scenario to happen.

@jczaja jczaja closed this as completed Aug 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants