Drop make_averaged_dataset from hindcast automation #133
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.
The 15-18
reshapr extract
jobs that this generated per optimum hindcast run seems to be too much for the dask cluster on salish, resulting in an unacceptably high job failure rate of ~20%.Tests of day-by-day processing (3 concurrent reshapr jobs) as will happen when we add make_averaged_dataset to automation for nowcast-green.202111 showed nearly 100% reliability. So, processing of hindcast will be handled outside of automation.