Added a way to configure the decompressed file dtype #380
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
… negative differences. Also added functionality to cast the decompressed output to a differemt dtype
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.
I was using the MNIST dataset and the original file was a uint8, but the output decompressed file was in float32, so it was much larger.
I've added a way to specify the data type of the decompressed file, a bonus is that by limiting the maximum and minimum values of this image, it also slightly increases performance. This is done by adding c.dtype = "foo" to the config file, where np.foo is a valid data type. If nothing is added then it will work as previously.