Concat falls back to copy when there is only a single bottom blob#570
Conversation
Contributor
|
Huh? What's the use case for this? |
Contributor
|
There was Check to avoid that. We don't need concat with only one blob, On Monday, June 30, 2014, Jeff Donahue notifications@github.com wrote:
Sergio |
Contributor
Author
|
In #560, when there is only a single pyramid level, the concat layer receives vectors with such bottom blobs. I didn't want to deal with the single and multiple pyramid levels differently. |
Contributor
Author
|
I should handle the special case directly. |
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
3 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.
No description provided.