Skip to content

Commit

Permalink
documentation changes to go with changes to percentiles and data_type
Browse files Browse the repository at this point in the history
  • Loading branch information
davidalbo committed Jan 2, 2024
1 parent ce7943a commit 992f8cd
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions docs/Users_Guide/mode.rst
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,28 @@ The **multivar_intensity_compare_fcst** and **multivar_intensity_compare_obs** c

When regridding to the FCST or OBS field (e.g. to_grid = FCST), the first field of the field array is used from the forecast and observation field dictionaries, respectively. All regridding is then done to that grid. Other regrid options described in :ref:`regrid` can also be used as normal.

"file_type" can be set independently for each input in multivariate mode. If not set for an input, MET uses file names and file content to determine the type.

When setting a threshold to a percentile, some choices require both an observation input and a forecast input. When this is the case, it's assumed the indices match, so for example if forecast input 1 has such a percentile setting, then observation input 1 will be used to compute the percentile. Percentiles in which this will happen are:

* SFP in an observation input
* The matching forecast input will be used to determine the threshold.
e.g. ">SFP33.3" in the 2nd observation input means greater than 33.3-rd percentile of the 2nd forecast input will be used as the threshold for that observation input.
* SOP in a forecast input
* The matching observation input will be used to determine the threshold.
e.g. ">SOP33.3" in the 2nd forecast input means greater than 33.3-rd percentile of the 2nd observation input will be used as the threshold for that forecast input.

* "==FBIAS" in an observation input.
* e.g. "==FBIAS1" in an observation input to automatically de-bias the data, using a simple threshold in the matching forecast input. For example,
when observation input 3 has "==FBIAS1", and forecast input 3 has ">5.0", MET applies the >5.0 threshold to the forecast and then chooses an
observation threshold which results in a frequency bias of 1. The frequency bias can be any float value > 0.0.

* "==FBIAS" in a forecast input.
* e.g. "==FBIAS1" in a forecast input to automatically de-bias the data, using a simple threshold in the matching observation input. For example,
when forecast input 2 has "==FBIAS1", and observation input 2 has ">5.0", MET applies the >5.0 threshold to the observation and then chooses a
forecast threshold which results in a frequency bias of 1. The frequency bias can be any float value > 0.0.


Practical Information
=====================

Expand Down

0 comments on commit 992f8cd

Please sign in to comment.