Table of Contents - The Atmospheric Studies Group at TRC

Table of Contents - The Atmospheric Studies Group at TRC Table of Contents - The Atmospheric Studies Group at TRC

29.01.2015 Views

Section 7: Prognostic Meteorological Interfaces Table 7-13: CALETA Control File Inputs (CALETA.INP) Line Variable Type Description 1 TITLE character*80 Title for CALETA application 2 INFILE character*80 Path name of AWIPS input files 3 OUTFILE character*80 Output 3D.DAT file name 4 LOGFILE character*80 Output list file name 5 RLATMIN/ RLATMAX 6 RLONMIN/ RLONMAX 7 NZMIN/ NXMAX real real integer Southernmost and northernmost latitudes of the sub-domain to extract (positive in Northern hemisphere; in degrees) Westernmost and Easternmost longitude of the sub-domain to extract (negative in Western hemisphere; in degrees) Lowest and highest vertical levels of the sub-domain to extract 8 IDAWP integer AWIPS grid format (212, 218, 245-250) 9 IDATEB integer Beginning UTC date-hour of 3D.DAT 10 IDATEE integer Ending UTC date-hour of 3D.DAT 11 IHRRUN integer Hours between ETA runs (6 hours for AWIPS 212, 218; 24 hours for AWIPS 245- 247, 249; 12 hours for AWIPS 248,250) 12 IDFRMT integer Flag of file naming convention: 0 = original file name; 1 = renamed file name 13 IDRUN integer Flag of CALETA run mode: 0 = Forecast mode; 1= Hybrid mode. 14 IDWEB integer Flag of web site for AWIPS file downloading: 0 = NWS site; 1 = NCEP site 7-34

Section 7: Prognostic Meteorological Interfaces Users are responsible for choosing correct horizontal and vertical ranges and correct AWIPS grid format in Records 5-8, especially for the high-resolution WRF domains, although the code will check for consistency. Extracted horizontal and vertical ranges should be within corresponding AWIPS domains. Users should consult Figures 7-4 and 7-5 for geographical coverage. Vertical levels in current AWIPS files are listed in Table 7-10. Selected vertical range in Line 7 should be within these limits. Line 11 is the time interval in hours of initial ETA/NAM runs. The interval is 6 hours for AWIPS 212 and 218, 24 hours for AWIPS 245-247, 249, and 12 hours for AWIPS 248 and 250. Line 12 is the flag for file naming convention. It should be “1” if file names have been renamed following the rule in Table 7-11. It should be “0” if files keep their downloaded names; again users are reminded to put files in date-hour subdirectories in this case. Line 13 is the flag for run mode. The flag is “0” if running CALETA in the forecast mode, and it is “1” for the hybrid mode (see below). Line 14 is the flag for the web site, where AWIPS files are downloaded. This flag should be “1” if files are downloaded from the NCEP wet site, and it is “0” for files from the NWS web site. Since only AWIPS 212 files from the NWS web site can be used to create 3D.DAT file, this flag may be set to zero only for AWIPS 212 files. For all other AWIPS files, this flag must be set to “1”. CALETA can be applied in both forecast mode and historical mode (hybrid mode). In the forecast mode, CALETA uses AWIPS files from one run to create a 3D.DAT file. Table 7-14 gives an example for AWIPS 212 GRIB files used in a 24-hour 3D.DAT file in this mode. In the hybrid mode, CALETA uses the latest AWIPS files from multiple ETA/NAM runs to create a 3D.DAT file (Table 7-15). In this mode, if there are any missing files in the processing period, the latest existing files from previous runs will be used as substitutes within a 48-hour limit (Table 7-16). CALETA Output Files CALETA.LST The list file of CALETA records various information from processing, including user-specified input controls, configurations of AWIPS files, processed files etc. This file should be consulted if CALETA fails to produce a complete 3D.DAT. An example of list file is given in Table 7-17. 3D.DAT A sample 3D.DAT file is shown and described in section (7.7). 7-35

Section 7: Prognostic Meteorological Interfaces<br />

<strong>Table</strong> 7-13:<br />

CALETA Control File Inputs (CALETA.INP)<br />

Line Variable Type Description<br />

1 TITLE character*80 Title for CALETA applic<strong>at</strong>ion<br />

2 INFILE character*80 P<strong>at</strong>h name <strong>of</strong> AWIPS input files<br />

3 OUTFILE character*80 Output 3D.DAT file name<br />

4 LOGFILE character*80 Output list file name<br />

5 RLATMIN/<br />

RLATMAX<br />

6 RLONMIN/<br />

RLONMAX<br />

7 NZMIN/<br />

NXMAX<br />

real<br />

real<br />

integer<br />

Southernmost and northernmost l<strong>at</strong>itudes <strong>of</strong><br />

the sub-domain to extract (positive in<br />

Northern hemisphere; in degrees)<br />

Westernmost and Easternmost longitude <strong>of</strong><br />

the sub-domain to extract (neg<strong>at</strong>ive in<br />

Western hemisphere; in degrees)<br />

Lowest and highest vertical levels <strong>of</strong> the<br />

sub-domain to extract<br />

8 IDAWP integer AWIPS grid form<strong>at</strong> (212, 218, 245-250)<br />

9 IDATEB integer Beginning UTC d<strong>at</strong>e-hour <strong>of</strong> 3D.DAT<br />

10 IDATEE integer Ending UTC d<strong>at</strong>e-hour <strong>of</strong> 3D.DAT<br />

11 IHRRUN integer Hours between ETA runs (6 hours for<br />

AWIPS 212, 218; 24 hours for AWIPS 245-<br />

247, 249; 12 hours for AWIPS 248,250)<br />

12 IDFRMT integer Flag <strong>of</strong> file naming convention:<br />

0 = original file name; 1 = renamed file<br />

name<br />

13 IDRUN integer Flag <strong>of</strong> CALETA run mode:<br />

0 = Forecast mode; 1= Hybrid mode.<br />

14 IDWEB integer Flag <strong>of</strong> web site for AWIPS file<br />

downloading:<br />

0 = NWS site; 1 = NCEP site<br />

7-34

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!