...
- We currently produce climate files for each reforecast run date, so in total 8*12-1 = 95 dates in a calendar year with 1/5/9/13/17/21/25/29 of each month, excluding 29 Feb.
- For each of these climate dates, there will be climate files for each possible daily lead time of the sub-seasonal range. Here not only calendar weeks are considered, but all possible 7-day lead times, starting from days1-7, then days2-8, .., out to days 40-46. This way, the weekly mean climatology for all possible lead times will be available, and so for each real time forecast the right climatology can be used, with the correct lead time in days, depending on which day of the week the real time forecast run (i.e. which corresponding climate lead time of climate to choose in order to get to the calendar weeks).
...
EFAS/GloFAS are both handled in the same way, by the same structure and same scripts. The only differences are the source name variable in the suite and the copydis_seasonal.sms script, which has slightly different retrieval options for both EFAS/GloFAS, depending on the source variable setting. And also the slight difference is in the weekly averaging, as the steps are set according whether 24-hourly (GloFAS) or 6-hourly (EFAS) data is processed.
...