-
Notifications
You must be signed in to change notification settings - Fork 4
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
Prev: in Rec #6
Comments
This is still missing. And this is a good question. I was thinking about it but I'm not really sure yet about the best way. It also has to be consistent to the naming logic (not only consistent, but we have to ensure that it will be always correct). Originally I was thinking about requiring all recurrent state as arguments to I'm thinking about some explicit mechanism like:
But I'm not sure if there is some better way. Also, I'm thinking about maybe requiring information about the shape. Sth like |
This is resolved now via |
What would be the proper way to access the previous timestep for the
Rec
class? Is there a logic for that already? Just using a functionget_special_layer
would not makes sense I think, due to this being a crucial feature of a RecUnit so making it part of the class would be good.The text was updated successfully, but these errors were encountered: