Add support for memory mapping Tiff files #51
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
Codecov Report
@@ Coverage Diff @@
## master #51 +/- ##
==========================================
- Coverage 94.29% 93.77% -0.53%
==========================================
Files 5 6 +1
Lines 263 289 +26
==========================================
+ Hits 248 271 +23
- Misses 15 18 +3
Continue to review full report at Codecov.
|
tlnagy
changed the title
[ci skip]
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 adds support for memory-mapping OMETIFF files, i.e. lazy-loading, virtual stacks, etc. The current version is a read-only variant while I work out the details for writing to disk, which will likely need some coordination with #30.
This PR also resolves some ambiguity related slow downs in filestreams.
Fixes #3