Fix handling of unencoded LMDB in Torch #478
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
Unencoded LMDB data are stored in BGR format so a channel swap is required to have a consistent representation of data across inputs, mean files, etc. close NVIDIA#477
gheinrich
force-pushed
the
dev/torch-unencoded-lmdb-3.0
branch
from
655af11
to
4eee8e3
Compare
|
NOTE: this is [nearly] a cherry-pick of the commit from #475 into the |
lukeyeager
added a commit
that referenced
this pull request
Dec 18, 2015
Fix handling of unencoded LMDB in Torch
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.
Unencoded LMDB data are stored in BGR format so a
channel swap is required to have a consistent
representation of data across inputs, mean files,
etc.
close #477