Apply chunking of assets before indicator calculation #322
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 applies pre-chunking to assets. While adding overhead before indicator calculation begins, parallelization is more efficient because we now know in advance over how many items to iterate. This also means that we can get rid of the nested future topology, which is anyways really hard to reason about.
More specifically, chunking applies the following steps to all assets in a portfolio:
chunk_size
chunk_size
into a grid withcellsize
equal tochunk_size
assetid
, indicator results are then aggregated later based on its valuemapme.biodiversity/R/chunking.R
Lines 1 to 12 in 4318724