add sharded WorkUnit output for non-lazy input WorkUnits in reprojection #683
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.
resolves #678
allows us more flexibility in the reprojection workflow to choose between time and memory usage, i.e. instead of writing out an intermediary
WorkUnit
between the ic->wu generation and reprojection we can just pass in our already loadedWorkUnit
but have the output be a shardedWorkUnit
, using more memory but potentially saving time.write_output
flag inreproject_work_unit
to create write the output of reprojection instead of re-materializing as aWorkUnit
in memoryreproject_lazy_work_unit
function into the mainreproject_work_unit
function.