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

Decide how to handle 'Local Variable' #4

Open
sj6077 opened this issue Jul 25, 2018 · 0 comments
Open

Decide how to handle 'Local Variable' #4

sj6077 opened this issue Jul 25, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@sj6077
Copy link
Contributor

sj6077 commented Jul 25, 2018

Things to Change

To implement RNN models, a user can represent the RNN hidden state with Variable to correctly pass it between multiple session runs.
However, current parallax just places it in PS, and it is not replicated into workers even the developer specified that the variable is 'local variable' which should not be replicated. It leads to the incomplete convergence of the model.
Furthermore, the fact that it is the user's responsibility to specify which variable should be replicated(GLOBAL_VARIABLE) and which should not (LOCAL_VARIABLE) also seems to be a problem, since parallax aims to support 'automatic parallelization'.

Current Behavior

Users have to distinguish between local and global variables by themselves.

Expected Behavior

Parallax automatically detects a local variable or helps a user with a warning

Failure Information (for bugs)

Failure Logs

How to Reproduce

Related Issues

@sj6077 sj6077 added the enhancement New feature or request label Jul 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant