input template #2323
-
Hi, Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @Deba57, I see you have a question about setting up a METplus use case to loop over multiple forecast lead times. Looking at the filenames you provided as an example, it looks like the timestamps include the forecast valid time but make no mention of the model initialization or lead times. So I'll make the following assumptions...
The METplus Example wrapper is a really great tool for testing this sort of thing out. Here are my relevant settings for that:
With this sample DebaExample.conf.gz file, I ran:
And note the first and last files listed in the log output:
Note that you do need to pick a LOOP_BY option. Here I chose to loop by initialization time but setting Hope that helps clarify. |
Beta Was this translation helpful? Give feedback.
Hi @Deba57, I see you have a question about setting up a METplus use case to loop over multiple forecast lead times. Looking at the filenames you provided as an example, it looks like the timestamps include the forecast valid time but make no mention of the model initialization or lead times. So I'll make the following assumptions...
temp.instavg.20120102_0600z.nc
) corresponds to forecast hour 0. So the model was initialized at 20120102_06.temp.instavg.20120206_0000z.nc
) corresponds to the last forecast hour. If I'm doing my math correctly, that timestamp would be a whopping 834 hours later than the initialization.