improve net config and shape mismatch error messages #2927
Merged
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
jeffdonahue
force-pushed
the
improve-net-init-error-msgs
branch
7 times, most recently
from
e80ddb8
to
2201a94
Compare
jeffdonahue
force-pushed
the
improve-net-init-error-msgs
branch
from
2201a94
to
7f4ffcd
Compare
|
These messages should help spell out issues! Thanks Jeff. |
shelhamer
added a commit
that referenced
this pull request
Aug 25, 2015
improve net config and shape mismatch error messages
|
👍 |
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.
This PR tries to improve a few unclear error messages that can be triggered from
Net::Init(many of which were my fault to begin with, sorry about that). In particular many questions on caffe-users are about the error messageCheck failed: ShapeEquals(proto) shape mismatch (reshape not set)which occurs in the call toFromProtoinCopyTrainedLayersFrom; this new message which displays the layer name and the shape of both blobs (and suggests renaming the layer if you didn't want to finetune) will hopefully help clear up some of that confusion.