Question on COCORAHS precip verification #2080
-
Asking a question that we didn't quite get to in the Monday METplus User's Discussion with EMC/DTC. Printing it out verbatim from the notes of that meeting (3/6): We spoke about the COCORAHS precip verification several weeks ago. I just wanted to check in for the correct settings that we need for precip verification valid at 12Z, because the notes didn’t quite make clear what the correct settings should be. I have the following: VALID_BEG = {ENV[VDATE]}12 ASCII2NC_FILE_WINDOW_BEGIN = 0 FCST_PCP_COMBINE_COMMAND = -sum 00000000_000000 1 {ENV[VDATE]}_120000 24 {FCST_PCP_COMBINE_OUTPUT_DIR}/{FCST_PCP_COMBINE_OUTPUT_TEMPLATE} -pcpdir {FCST_PCP_COMBINE_INPUT_DIR}/{FCST_PCP_COMBINE_INPUT_TEMPLATE} OBS_POINT_STAT_WINDOW_BEGIN = -82400 Please define the first 00000000_000000, what this represents and the 1 following that. George: See 8. Re-Formatting of Gridded Fields — MET 11.0.1 documentation I have set {ENV[VDATE]}_120000 24 to be the valid date of the end of the summing period, and the 24 is the hours to be summed. Somewhere, I want to be sure I have the past 24 hours of valid analysis data to be able to sum that. Where specifically do I define that. I put that in the OBS_POINT_STAT_WINDOW variables, but are there PCP_COMBINE window variables, which I believe should be there? Thanks for any assistance you can provide. Perry |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
Hi Perry: I wasn't part of the discussion Monday. However, when using the sum command, the required input arguments are init_time, in_accum in hours, valid_time, and out_accum in hours. For observations (rather than model), the init_time should be specified as 00000000_000000, since there isn't a model initialization. It looks like you have specified your valid_time as {ENV[VDATE]}_120000, in_accum as 1, and out_accum as 24. With the configurations listed, MET will take the {ENV{VDATE}}_120000 as the end of the 24 hour period, and look for the 24 one hour precip files leading up to that date, in the directory given after pcpdir. However, it looks like you are running pcp_combine on forecast data. In this case, you probably want to specify the model initialization as something other than 00000000_000000, so that MET will know which initialization to use for these these 24 one hour files. If you are not running on forecast data, then you will want to change your PCP_COMBINE variable names to say OBS_PCP_COMBINE rather than FCST_PCP_COMBINE. Pcp combine does have a sum option, which can make setting up these types of runs easier. It looks like you are using the USER_DEFINED option. Does this help? Christina |
Beta Was this translation helpful? Give feedback.
-
Hi Perry: Were you able to get this working as expected? Thanks, |
Beta Was this translation helpful? Give feedback.
Hi Perry:
I wasn't part of the discussion Monday. However, when using the sum command, the required input arguments are init_time, in_accum in hours, valid_time, and out_accum in hours. For observations (rather than model), the init_time should be specified as 00000000_000000, since there isn't a model initialization. It looks like you have specified your valid_time as {ENV[VDATE]}_120000, in_accum as 1, and out_accum as 24.
With the configurations listed, MET will take the {ENV{VDATE}}_120000 as the end of the 24 hour period, and look for the 24 one hour precip files leading up to that date, in the directory given after pcpdir. However, it looks like you are running pcp_combine on foreca…