Die on NaN loss#2363
Closed
jeffdonahue wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
(Of course, this adds to the existing list of annoyances associated with Caffe's checks -- e.g. in PyCaffe -- but that's kind of a separate issue... Nonetheless I can see how it probably shouldn't be merged until those things are resolved.) |
Contributor
|
Makes sense. Yes, it might be a bad idea to crash pycaffe in this normal situation. See also #1349. |
Contributor
Author
Contributor
Author
|
Closing this as it's a duplicate and no longer mergable. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This will make training die on a NaN loss, unless turned off by setting
SolverParameter.die_on_nan == false. It's been saving the GPUs I've been using many pointless cycles...