Output Module (last updated 8/27/2015)

Transcription

1 Output Module (last updated 8/27/2015) Goals: Provide a common output format and content from all modeling groups for Tier 2 files. Provide a data file that is compatible with the GFDL Vortex Tracker program and contains sufficient information to fully evaluate the various models. Data Requirements: Gridded model data must be on a non-staggered, uniform-spaced, latitudelongitude grid, with specified fields and levels, in a GRIB1 file. Each modeling group will be responsible for developing the front-end portion of the postprocessing routine necessary to produce the specified output fields on a nonstaggered, uniform-spaced, latitude-longitude grid for the specified levels. The Output Module provides the code that collects fields and grid information and writes a GRIB1file in the correct format for evaluation. Overview: The Output Module is a set of Fortran routines that produces a GRIB1 file. The input to this module is the specified meteorological fields on a non-staggered, uniform-spaced, latitude-longitude grid (see Table A). the latitude-longitude grid definition parameters (see Table B). The data file specifications are defined in Table C. Compile/Run Instructions: Code needed for generating the necessary output files is provided in a tar file via attachment (OutputModule.tar.gz). First unzip and untar this file - tar xvf OutputModule_v2.2.tar.gz This tar file has the following contents: makefile: use to compile and link the Output Module code to the GRIB1 library, with a command-line option to select either linux or ibm w3lib directory: code for building the GRIB1 library OutputModule directory o makefile o DRIVER.f : a template/sample driver routine which calls gribbing routines o *.f : additional routines to prepare the data for gribbing o *.comm and *.tbl : common blocks and tables to prepare the data for gribbing o fort.14: namelist that determines GRIB1 fields to output 1

2 To implement the code, the first step is to edit DRIVER.f and insert your customized code to: Loop over all forecast times at 6-h intervals. o Read in the model dataset. o If necessary, de-stagger and interpolate required data fields to a uniform-spaced, latitude-longitude grid and appropriate vertical levels. o Order the arrays from West to East (first index) and North to South (second index). o Assign data fields to the arrays required by the Output Module, including vorticity if available (see Table A). If vorticity is not available, fill the vorticity arrays with (signifies missing data). Accumulated precipitation at the initial time should be filled with (signifies missing data). o Define grid and date parameters, including date/time/forecast/model_id in common data elements required by the Output Module (see Table B). o Call routines READCNTRL and PROCESS to pack/write the GRIB file (will append to existing/open file). Close the output file Once DRIVER.f has been customized, compile and link using the makefile in top-level directory: make linux <or> make ibm o supplied makefiles assume PGI compilers for linux and xlf compilers for IBM if you have different compilers, you will need to edit the toplevel makefile. It is not necessary to manually change the makefile in the w3lib or OutputModule subdirectories. Information for running driver.exe: Environment variables used: none. Run-time parameters/files needed: o Input: fort.14: a parameter file containing GRIB field codes. Do not modify this file! o Output: fort.70 will be opened and appended with each time-step. After the run, fort.70 should be renamed using the requested file naming convention, listed below. Optionally, you may open unit=70 in the Fortran code with the appropriate filename. 2

3 File naming convention: Global <mdl>_<h,d><vvvv>_<yyyymmddhh>.grb Regional <mdl>_<h,d><vvvv>_<yyyymmddhh>_<basin><cyclone number><yyyy>.grb where, <mdl> = assigned model ATCF ID <h,d> = use h to designate historical or retrospective forecasts and d for demo or quasi-real-time forecasts <vvvv> = use this 4-letter identifier to indicate the version of your model used to generate the forecast. This identifier can be as simple as the year in which you generated the forecast or a more sophisticated identifier that is directly connected to your group s method for tracking model versions. Please provide information on how to translate this identifier. <yyyymmddhh> = date/time of forecast initialization. <basin> = ocean basin abbreviation corresponding to location of the storm al = North Atlantic basin, north of the Equator sl = South Atlantic basin, south of the Equator ep = North East Pacific basin, eastward of 140 W cp = North Central Pacific basin, between the dateline and 140 W wp = North West Pacific basin, westward of the dateline io = North Indian Ocean basin, north of the Equator, between 40 E and 100 E sh = South Pacific Ocean basin and South Indian Ocean basin <cyclone number> = 01 49, training/test, invests <YYYY> = year portion of the full ATCF id for the storm year of the hurricane (e.g., 2010) Files should be deposited on either the jet (NOAA/GSD) or bluefire (NCAR). You will need an account on one of these systems; please contact the following data manager if you need assistance in setting up an account: Christopher Williams cwill@ucar.edu

4 Delivery to jet (preferred): Jet is the preferred system for data delivery to TCMT. If you need to open an account on this system, download the application form from Fax the completed application to , attention Lee Cohen and ask to be added to the tcmt project group. Once your user ID has been enabled and you are a member of the tcmt group, you will need to transfer secure ssh keys that you generate on the system currently holding your Tier 2 data files to jetscp, a file-transfer frontend system for jet. To generate your secure ssh keys perform the following on the system currently holding your Tier 2 data files: a) on your chosen host (where your Tier 2 data currently resides): ssh-keygen -t dsa cat ~/.ssh/*dsa* b) copy & paste the output of cat into an and send it to hpcshelp.fsl@noaa.gov, requesting installation into jetscp Once the key installation is complete you can scp files to a location under the tcmt project directory specified by your TCMT data manager via jetscp by executing (locally) a command similar to: scp some_file jetscp.rdhpcs.noaa.gov:/lfs2/projects/tcmt/<h,d><yyyy> where, <h,d> = use h to designate historical or retrospective forecasts and d for demo or quasi-real-time forecasts <yyyy> = year of project Delivery to bluefire: Please deposit the files in a directory of your choosing. Once the files are on bluefire, please inform your data manager of the path to the directory where the data is located. 4

5 Table A: Meteorological fields to be included in Tier 2 data files, as well as the corresponding array name for this field in the Output Module Meteorological Field (units) Level Output array name Sea Surface Temperature (K) Surface SST Mean Sea Level Pressure (Pa) Surface PSFC 6-h accumulated precipitation Surface ACPREC (mm) Vertically integrated water Surface VW condensate (kg m -2 ) Total precipitable water (mm) Surface PW U component of the wind (m s -1 ) 10-m AGL U10 U component of the wind (m s -1 ) 850 hpa U(*,*,1) U component of the wind (m s -1 ) 700 hpa U(*,*,2) U component of the wind (m s -1 ) 500 hpa U(*,*,3) U component of the wind (m s -1 ) 300 hpa U(*,*,4) U component of the wind (m s -1 ) 200 hpa U(*,*,5) V component of the wind (m s -1 ) 10-m AGL V10 V component of the wind (m s -1 ) 850 hpa V(*,*,1) V component of the wind (m s -1 ) 700 hpa V(*,*,2) V component of the wind (m s -1 ) 500 hpa V(*,*,3) V component of the wind (m s -1 ) 300 hpa V(*,*,4) V component of the wind (m s -1 ) 200 hpa V(*,*,5) Temperature (K) 2-m AGL TSFC Temperature (K) 850 hpa T(*,*,1) Temperature (K) 700 hpa T(*,*,2) Temperature (K) 500 hpa T(*,*,3) Temperature (K) 300 hpa T(*,*,4) Temperature (K) 200 hpa T(*,*,5) Relative Humidity (%) 2-m AGL RHSFC Relative Humidity (%) 850 hpa RH(*,*,1) Relative Humidity (%) 700 hpa RH(*,*,2) Relative Humidity (%) 500 hpa RH(*,*,3) Relative Humidity (%) 300 hpa RH(*,*,4) Relative Humidity (%) 200 hpa RH(*,*,5) Geopotential Height (m) 850 hpa Z(*,*,1) Geopotential Height (m) 700 hpa Z(*,*,2) Geopotential Height (m) 500 hpa Z(*,*,3) Geopotential Height (m) 300 hpa Z(*,*,4) Geopotential Height (m) 200 hpa Z(*,*,5) Absolute Vorticity (s -1 ) 850 hpa AVORT (*,*,1) Absolute Vorticity (s -1 ) 700 hpa AVORT (*,*,2) 5

6 Table B: List of grid and date parameters to include in Tier 2 data files. Grid Parameter Variable LATSTART Northernmost latitude (range -90 to +90 ) LONSTART Westernmost longitude (range -180 to +180 ) LATLAST Southernmost latitude (range -90 to +90 ) LONLAST Easternmost longitude (range -180 to +180 ) DXVAL West-east grid spacing ( ) DYVAL North-south grid spacing ( ) SDAT(1) Month of model initialization SDAT(2) Day of model initialization SDAT(3) Year of model initialization (4 digits) IHRST Hour of model initialization (UTC) IMIN Minute of model initialization IFHR Forecast hour IFMIN Forecast minute IMDLTY Assigned model ATCF ID 6

7 Table C: Tier 2 data file specifications Format GRIB1 You may use the HFIP Output Module to convert your files to GRIB1 format. Projection Temporal resolution Forecast length Unstaggered, uniform-spacing, latitude-longitude 6 h Global 7 days Regional 5 days Spatial Resolution Global: 0.50 Regional: 0.10 Domain Global: global domain Regional: 20 x 20 deg domain centered on the storm. Models run on nested grids smaller than 20 x 20 are requested to send a single 20 x20 grid created by blending data from the appropriate nested domains. Data delivery Modeling groups will only provide gridded data files for forecasts for which a storm is present. Please deposit on either bluefire or the jet system. 7