Replace custom multiprocessing pipeline with sentinelhub multithreading #43
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
|
This pull request introduces 1 alert when merging a7a9f4b into 6b139d1 - view on LGTM.com new alerts:
|
AdrienWehrle
deleted the
37-replace-custom-multiprocessing-pipeline-with-sentinelhubdownloadclient-multithreading
branch
AdrienWehrle
restored the
37-replace-custom-multiprocessing-pipeline-with-sentinelhubdownloadclient-multithreading
branch
AdrienWehrle
deleted the
37-replace-custom-multiprocessing-pipeline-with-sentinelhubdownloadclient-multithreading
branch
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.
I initially implemented a multiprocessing pipeline with a multiprocessing strategy depending on the number of days and split boxes to process (if only a couple of days to process but many split boxes, it makes more sense to distribute jobs over the different split boxes than over days). The Sentinel Hub services already offer multithreading capabilities, so let's use this instead to make the tool more simple and probably more stable!
On a simple test over Ilulissat in Greenland downloading 2017-05-01 to 2017-09-01 of Sentinel-1 EW data no significant improvement in download efficiency have been observed.