Closed agrosu1978 closed 1 year ago
As discussed through teams conversation, my first guess is that this is because the AgERA5 meteo collection for 2022 is not covering the entire year, which is a situation that is currently not supported in the code. Here we assume a full year, so if the actual data stops earlier, we run into an error.
Fastest temporary fix for the moment would be to regenerate 2022 meteo covering the full year. More longterm solution is a code patch that allows - if possible - to have less than a year of data. Downside is that gaps will not be detected because we assume a full year.
After a re-generation of AgERA5 meteo collection, the block processing was successfully completed. Still, a code patch that allow less than a year of data should be implemented for code maturity
fix with the delivery on the bucket of the full 2022 year
The behavior appears when processing Ukraine 2022 (102 tiles), summer1, for all tiles Please see in the attached file:
branch_0325_th7_20230120_103454_ip-192-168-15-221.eu-central-1.compute.internal.log