Compute padding when pad: 1 #17
Open
Conversation
This file contains 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
|
This is a major issue and should be included |
kevinkit
approved these changes
Jan 16, 2017
K-Du
approved these changes
Feb 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ReLUlayer typopad=1in Darknet .cfg files means that there is padding if necessary to maintain the same size output. Here it was taken directly as the number of pixels it pads by. From this answer.Padding always by 1 pixel changed the output size when converting to Caffe from Darknet in cases as 1x1 convolutions, which do not need any padding at all. Darknet19 with input size 224x224 gives now the correct size of 7x7 for the last feature map as in YOLO9000.