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
Saver / tf.train.latest_checkpoint doesn't work very well with relative paths #571
Comments
Fixed by: |
We abandoned the gerrit one -- if #573 looks good, we can merge |
polm
referenced
this issue
in hardmaru/sketch-rnn
Mar 20, 2016
Relative path handling seems to have changed at some point since this was released; see issues #571 and 751. -POLM
This issue persists when you change the name of the run folder. It seems that the checkpoints/checkpoint file only keep the old path and tf fails when latest_checkpoint is used over this new folder. |
darkbuck
pushed a commit
to darkbuck/tensorflow
that referenced
this issue
Jan 23, 2020
…pstream-zyin-merge-conv-algo-picker [XLA:GPU] Refactor cudnn & miopen conv algorithm picker for find mode
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example, if model is saved into a folder
test
by doingsaver.save(session, '/path/to/test')
- will result in the havingcheckpoints
andmodel-0
files. Wherecheckpoints
file will have something like this:Which if you call now
tf.train.latest_checkpoint('test')
from the same directory, will result in theNone
.This is due to
os.path.join(checkpoint_dir, ckpt.model_checkpoint_path)
which for relative path like above will result in thetest/test/model-0
.The text was updated successfully, but these errors were encountered: