HRRR 72 hour back trajectory gives 52 hours
Posted: August 31st, 2021, 1:16 pm
When using HRRR through the server, a backward 72h trajectory cannot cover 72 hours unless it starts at the end of the day. To illustrate the problem, I am posting the top lines of a tdump output file.
Note that the trajectories start at 3Z on May 10th, but the MET files cover through the end of May 10th. That means that 3 of the 12 met files are not used. Because of the 12 file limit, there are only 48 previous hours plus the few at the beginning of May 10th.
In the web interface, I selected the HRRR data covering 20200510_00-05_hrrr. Is it possible to update the web interface to select MET files based on the trajectory hour options? Or based on the MET file selected by the user?
Note that the trajectories start at 3Z on May 10th, but the MET files cover through the end of May 10th. That means that 3 of the 12 met files are not used. Because of the 12 file limit, there are only 48 previous hours plus the few at the beginning of May 10th.
Code: Select all
12 1
HRRR 20 5 8 0 1
HRRR 20 5 8 6 1
HRRR 20 5 8 12 1
HRRR 20 5 8 18 1
HRRR 20 5 9 0 1
HRRR 20 5 9 6 1
HRRR 20 5 9 12 1
HRRR 20 5 9 18 1
HRRR 20 5 10 0 1
HRRR 20 5 10 6 1
HRRR 20 5 10 12 1
HRRR 20 5 10 18 1
9 BACKWARD OMEGA
20 5 10 3 36.138 -115.258 500.0
20 5 10 2 36.138 -115.258 500.0
20 5 10 1 36.138 -115.258 500.0
20 5 10 0 36.138 -115.258 500.0
20 5 9 23 36.138 -115.258 500.0
20 5 9 22 36.138 -115.258 500.0
20 5 9 21 36.138 -115.258 500.0
20 5 9 20 36.138 -115.258 500.0
20 5 9 19 36.138 -115.258 500.0