Conversation
…not float64 to decrease the size of stored .eye files In E2E files intensities are stored in a custom ufloat16 format this takes even less space. We actually read the data as uint16 and than map to the respective float which is converted to float32 to preserve precision. An option in future might be to store the intensities as uint16 as in E2E to further reduce file size.
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
1 participant
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.
…not float64 to decrease the size of stored .eye files
In E2E files intensities are stored in a custom ufloat16 format this takes even less space. We actually read the data as uint16 and than map to the respective float which is converted to float32 to preserve precision. An option in future might be to store the intensities as uint16 as in E2E to further reduce file size.