"Missing data" file boundary problem with CFS/GFS
Posted: April 3rd, 2013, 2:11 pm
I've encountered a problem with missing data warnings in converted 0.5deg CFS output. I used grib2arl since the output is on the same grid as some versions of GFS, and modified CFG_GRIB to match the necessary variables. Once I've converted multiple files, I can run both the trajectory and dispersion model on them, and the output appears to be reasonable for both forward and backward cases. However, I've noticed that in some cases I get "missing data" warnings in MESSAGE:
This only occurs on the boundary of the files (e.g., if I have pgbh06.gdas.20100516-20100520.bin and pgbh06.gdas.20100521-20100525.bin, the error will only show up when the model passes through 2010-05-21 00Z). Oddly, it still occurs at the original boundary if I concatenate the two files into one:
There are two main things that I can't figure out:
1) Why the file transition isn't handled correctly so that hysplit cannot find the data.
2) What does the model do in the absence of these data? I was surprised that it continued with the integration.
Could the problem be related to the fact that the CFS output is a sequence of 6-hour forecasts? Is hysplit expecting a single base time with a sequence of forecasts?
Any help greatly appreciated!
Code: Select all
NOTICE metpos: (mtime,ftime) - 58056480 58057200
WARNING metinp: missing data - HGTS
Time: 10 5 21 0 -1
Level: 1 Variable: 1
WARNING metinp: missing data - TEMP
Time: 10 5 21 0 -1
Level: 1 Variable: 2
WARNING metinp: missing data - UWND
Time: 10 5 21 0 -1
Level: 1 Variable: 3
WARNING metinp: missing data - VWND
Time: 10 5 21 0 -1
Level: 1 Variable: 4
WARNING metinp: missing data - WWND
Time: 10 5 21 0 -1
Level: 1 Variable: 5
...
Code: Select all
cat pgbh06.gdas.20100516-20100520.bin pgbh06.gdas.20100521-20100525.bin > bothfiles.bin
There are two main things that I can't figure out:
1) Why the file transition isn't handled correctly so that hysplit cannot find the data.
2) What does the model do in the absence of these data? I was surprised that it continued with the integration.
Could the problem be related to the fact that the CFS output is a sequence of 6-hour forecasts? Is hysplit expecting a single base time with a sequence of forecasts?
Any help greatly appreciated!