fcst and hcst dates and other parameters in the seasonal recipe
Hi @allabres @nmilders @cchou,
I have been tweaking some things in the recipe. We discussed a few weeks ago that you felt that the Time section was not very clear. What do you think of this format:
Time:
sdate: '1101' # Mandatory, int: Start date, 'MMDD'
fcst_year: '2020' # Optional, int: Forecast year 'YYYY'
hcst_start: '1993' # Mandatory, int: Hindcast start year 'YYYY'
hcst_end: '2016' # Mandatory, int: Hindcast end year 'YYYY'
ftime_min: 1 # Mandatory, int: First leadtime time step in months
ftime_max: 2 # Mandatory, int: Last leadtime time step in months
Instead of the previous one:
Time:
sdate:
fcst_syear: '2020' # Optional, int: Forecast year 'YYYY'
fcst_sday: '1101' # Mandatory, int: Start date, 'MMDD'
hcst_start: '1993' # Mandatory, int: Hindcast start year 'YYYY'
hcst_end: '2016' # Mandatory, int: Hindcast end year 'YYYY'
ftime_min: 0 # Mandatory, int: First leadtime time step in months
ftime_max: 1 # Mandatory, int: Last leadtime time step in months
The people working on decadal said that they would prefer for ftime to begin at 1 instead of 0. I'm guessing this would work for you all as well?
Finally, we will also be including a parameter to request the computation of percentiles and probability categories, within the Skill module. (Note @allabres: this is not the same as what we were discussing the other day about requesting specific thresholds for RPSS). My initial idea was something like this:
Skill:
metric: RPS RPSS FRPSS BSS10 BSS90 EnsCorr Corr
prob: [[1/3, 2/3], [1/10, 9/10]]
But I think it might be confusing. So I welcome any suggestions from you on where the parameter should go and what the name should be.
Thank you very much,
Victòria