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

Suppress output for python bindings #2504

Closed
wants to merge 1 commit into from

Conversation

lukeyeager
Copy link
Contributor

I'm tired of pycaffe printing hundreds of lines to stderr. See #789, #858 and #872 for discussions on why this was done by default for C++.

Is suppressing the output when using python a bad idea for any reason? Is there a better way to suppress the output than this (it's kinda hacky)? GLOG flags explained here.

@lukeyeager
Copy link
Contributor Author

Edited to allow ERROR and FATAL messages to propagate through.

Only allow output for errors
@lukeyeager
Copy link
Contributor Author

Based on comments in this thread, it seems like people still want to see the output during training. That makes sense - I've never used pycaffe for training, only for working with trained models.

Can anyone who uses pycaffe for training comment on whether any version of this PR could be useful? Does the solver store the training updates somewhere, or is the log the only way to access that data?

@lukeyeager lukeyeager closed this Aug 3, 2015
@lukeyeager lukeyeager deleted the suppress-output branch May 27, 2016 19:41
@PapaMadeleine2022
Copy link

see here.

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

Successfully merging this pull request may close these issues.

2 participants