Cleaner workaround for max pool#103
Merged
drnikolaev merged 1 commit intoNVIDIA:caffe-0.14from Jan 20, 2016
Merged
Conversation
drnikolaev
added a commit
that referenced
this pull request
Jan 20, 2016
Cleaner workaround for max pool
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.
Only switch pooling engine on maxpool. Other cases should be okay. The source of the issue is how indexes are tracked to deal with handling multiple maxes (e.g. ties). Caffe makes cuDNN do this in place which can corrupt the indecies leading to arbitrary tie breaking. Until we can review, switch default engine in the case of max pool.