New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Why is LSTM final state's backward message (dloss/dfinalstate) 0? #6

Open

sunshineatnoon opened this issue Jul 11, 2016 · 0 comments

sunshineatnoon commented Jul 11, 2016

Thanks for this code, it's very clear. But I don't understand these two lines:

-- LSTM final state's backward message (dloss/dfinalstate) is 0, since it doesn't influence predictions
local dfinalstate_c = initstate_c:clone()
local dfinalstate_h = initstate_c:clone()

Why is LSTM final state's backward message (dloss/dfinalstate) 0?

The text was updated successfully, but these errors were encountered:

# for free to join this conversation on GitHub. Already have an account? # to comment