In use case up to this point, we have used (1) for GRIB files and (2) for NetCDF files. However, this is not what decides which to use. extended PDS GRIB files use (1), but not all GRIB files do, some use (2). Getting prob data via python embedding will use (2).
To handle this, we should create a new config variable(s) to determine if METplus should set the prob dictionary or use the prob boolean. We will need a separate variables for FCST and OBS, because although there are no probabilistic observations, MET can be configured to compare 2 probabilistic forecasts and the 2nd forecast info would go in the obs slot. Something like [FCST/OBS]_SET_PROB_DICTIONARY?
There are 2 ways to specify probabilistic data in the MET config files:
1) { name="PROB"; level="L0"; prob={ name="VAR_NAME"; thresh_lo=12.7; } cat_thresh=[==0.1]; }
2) { name="VAR_NAME_gt12.7"; level="L0"; prob=TRUE; }
In use case up to this point, we have used (1) for GRIB files and (2) for NetCDF files. However, this is not what decides which to use. extended PDS GRIB files use (1), but not all GRIB files do, some use (2). Getting prob data via python embedding will use (2).
To handle this, we should create a new config variable(s) to determine if METplus should set the prob dictionary or use the prob boolean. We will need a separate variables for FCST and OBS, because although there are no probabilistic observations, MET can be configured to compare 2 probabilistic forecasts and the 2nd forecast info would go in the obs slot. Something like [FCST/OBS]_SET_PROB_DICTIONARY?