[DAR-6557][Internal] Use np.uint8 as datatype for output nifti volumes to reduce allocations #1064
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.
Problem
Export to nifti volumes has a large memory footprint. We encountered out of memory errors during export.
Solution
Each exported nifti volume is casted to int16 to be written to disk, moreover, each volume we export has just one mask. Thus we can use
np.uint8datatype for volumes during export processing to save space.Changelog
Use np.uint8 as datatype for output nifti volumes to reduce allocations