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

in jupyter notebook any way to set model.fit() output error frequency? #4676

Closed
pswpswpsw opened this issue Dec 11, 2016 · 2 comments
Closed

Comments

@pswpswpsw
Copy link

model.fit() with verbose = 1 can output error status, however, sometimes it is too fast that the webpage is getting slow..remember jupyter notebook is still a webpage.. is there anyway to get around with his?

@patyork
Copy link
Contributor

patyork commented Dec 11, 2016

You can set verbose to either 0 or 2, use the RemoteMonitor callback (or a variant of it that also posts data on batch_end), and write your own web service to display the data. If you are using TensorFlow, TensorBoard might work. But barring those two ideas, right now, there is no other option other than TensorBoard for TensorFlow, or just logging less data.

Jupyter does not handle the screen clears correctly, and accrues the output, making the notebook larger and larger. If you look at a saved notebook (the raw file) after the .fit method, you'll see stuff like this:

[=>...................]
[==>..................]
[===>.................]
[====>................]

which quickly gets to be a lot of data; one line for each minibatch.

@pswpswpsw
Copy link
Author

Thanks for the response. Actually I use tensorboard to monitor my work on workstation. The workstation works on a dropbox file folder so I can see what's going on by just tensorboard at this dropbox.

Another option I just find is that, use command line rather than ipython notebook..which is much faster for output to screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants