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

.Save, .Restore for contrib.learn.DNNClassifier #3306

Closed
jah456 opened this Issue Jul 14, 2016 · 4 comments

Comments

Projects
None yet
5 participants
@jah456

jah456 commented Jul 14, 2016

The older functions like skflow.TensorFlowDNNClassifier had methods .save and .restore. These were supposedly migrated over to the contrib.learn functions, but there are no longer save and restore methods that I can find. Is there a new protocol for saving the graph and variables with the new contrib.learn package?

@jmchen-g

This comment has been minimized.

Show comment
Hide comment
@jmchen-g

jmchen-g Jul 14, 2016

Contributor

@ispirmustafa Could you take a look at this please?

Contributor

jmchen-g commented Jul 14, 2016

@ispirmustafa Could you take a look at this please?

@llealgt

This comment has been minimized.

Show comment
Hide comment
@llealgt

llealgt Jul 15, 2016

Hi, any news on this? , im having hard times trying to save a DNNClassifier , followed some examples using train.Saver() but it says (No variables to save)

llealgt commented Jul 15, 2016

Hi, any news on this? , im having hard times trying to save a DNNClassifier , followed some examples using train.Saver() but it says (No variables to save)

@michaelisard

This comment has been minimized.

Show comment
Hide comment
@michaelisard

michaelisard Jul 25, 2016

Member

@ispirmustafa any thoughts? Assigning @martinwicke since @ispirmustafa is not in the TensorFlow org.

Member

michaelisard commented Jul 25, 2016

@ispirmustafa any thoughts? Assigning @martinwicke since @ispirmustafa is not in the TensorFlow org.

@martinwicke

This comment has been minimized.

Show comment
Hide comment
@martinwicke

martinwicke Jul 25, 2016

Member

Checkpoints are saved automatically, and if you specify the same directory when you create another Estimator (of the same kind/same parameters), it will load the checkpoints and you can continue training.

There is currently a bug which prevents you from using the restored Estimator for inference without running at least one step of training.

I will close this issue -- for detailed questions, please ask on StackOverflow, we can track questions and answers better over there.

Member

martinwicke commented Jul 25, 2016

Checkpoints are saved automatically, and if you specify the same directory when you create another Estimator (of the same kind/same parameters), it will load the checkpoints and you can continue training.

There is currently a bug which prevents you from using the restored Estimator for inference without running at least one step of training.

I will close this issue -- for detailed questions, please ask on StackOverflow, we can track questions and answers better over there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment