/mss/fsl/frd/lapb/ihop_reruns/{MODEL} where MODEL is one of MM512, WRF12, MM504, WRF04
{CYCLE}_grb.tar: De-staggered isobaric and surface data in GRIB format using FSL/LAPB GRIB Table
{CYCLE}_raw.tgz: Raw netCDF-format WRF input, namelist, and output files on native vertical coordinate, staggered grid
{CYCLE}_fsf.tgz: Surface/2D fields in LAPS netCDF format
{CYCLE}_fua.tgz: 3D isobaric fields in LAPS netCDF format
{CYCLE}.v5d: 3D isobaric and 2D surface fields in Vis5D format
CYCLE=YYYYMMDDHH in UTC for model initialization time. For example, the 1200 UTC run for 2 June 2002 would have CYCLE=2002060212
The “hopper” file server contains extracted versions of the post-processed data stored on the MSS. To access these data sets, you need to either obtain an account on hopper or have the /mr/mr1 file system exported and mounted on the system on which you will run your diagnostic tools. Contact Gary Fisher or Scott Buennemeyer for assistance. The following data formats are available on hopper:
/mr/mr1/ihop_reruns/VIS5D/{MODEL}
The Vis5D files are good for a “quick look” capability if you have access to a system that has Vis5D installed and can reasonably handle the load.
/mr/mr1/ihop_reruns/GRIB/{MODEL}
GRIB files are named using the convention: YYjjjHHMMffff.grib
YY = 2-digit year of model initialization time (UTC)
jjj = 3-digit day-of-year for model initial time
HHMM = hour/minute UTC of initial time
ffff = Forecast hour for the data in the file (i.e., add this many hours to the initial time to get the valid time)
GRIB data uses a different table than the operational NCEP table, and this custom table can be found here. The GRIB files are useful for display on AWIPS, use within GEMPAK or NCL, etc.
12km: /mr/mr1/ihop_reruns/LAPS-NETCDF/laps12/lapsprd/fsf/{model} where model is either “mm5” or “wrf”
4km: /mr/mr1/ihop_reruns/LAPS-NETCDF/laps04/lapsrd/fsf/{model}
The fsf files use a similar file name as the GRIB convention, except that the “ffff” portion of the file name is used for hours and minutes in the fsf names (i.e., a 27 hour forecast would be 2700 for fsf, whereas for the GRIB files it would be 0027). Since these files are in netCDF, they can be read using a variety of tools (IDL, NCL). Furthermore, they are stored in an appropriate directory structure to allow the use of the lapsplot.exe program.
12km: /mr/mr1/ihop_reruns/LAPS-NETCDF/laps12/lapsprd/fua/{model} where model is either “mm5” or “wrf”
4km: /mr/mr1/ihop_reruns/LAPS-NETCDF/laps04/lapsrd/fua/{model}
The fua files are only going to be place on hopper on a case-by-case basis to save space.
Since the data is created on ijet, it resides there for a period of time before being moved to hopper and/or MSS. Check in the following directories:
/exchange/tmp/ihoplaps/CASES/MM512
/exchange/tmp/ihoplaps/CASES/WRF12
These two directories contain everything being put to MSS, using the same file names.