Don't force datum.label=0 in array_to_datum #3749
Merged
Conversation
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
Contributor
Author
|
Ping? I feel like the odds of breaking existing workflows should be pretty low. If they're not specifying a label, then I can't see why they would be reading it later. |
|
LGTM. |
Member
|
Looks good. Thanks for this and the IO care in general @lukeyeager, and thanks for signaling this @seanbell. |
fxbit
pushed a commit
to Yodigram/caffe
that referenced
this pull request
Sep 1, 2016
…ult-label Don't force datum.label=0 in array_to_datum
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.
datum.label=Noneis preferable todatum.label=0.