GAMAP v2–19 User Guide
Previous | Next | Printable View (no frames)
7. GAMAP input files
7.1 The gamap.defaults file
The gamap.defaults file contains the following user-definable default settings which are read the first time GAMAP is called, and then once thereafter each time the routine CTM_CLEANUP is called.
The gamap.defaults file that ships with GAMAP v2–19 is available by clicking HERE (file will open in a new browser window).
The switches that can be set in gamap.defaults are as follows:
String containing the default model name, grid resolution, and number of layers. GAMAP will use MODELNAME as the default model type when prompting the user to select a model. Valid entries for MODELNAME are "GISS_II_PRIME 4x5 (23L)", "GEOS1 2x2.5 (20L)", etc. Any number of spaces are allowed between the individual words.
Default filemask for input files. GAMAP will use FILEMASK when prompting the user to select a file via the dialog box. In order to tell GAMAP to read/write files to/from the current directory, you can set filemask to "./".
Flag for determining whether or not to create PostScript output. Valid entries for DO_POSTSCRIPT are 0 (never create PostScript output), 1 (always create PostScript output) or *QUERY (ask the user each time whether or not to create PostScript output) . Recommended value: *QUERY.
Default PostScript file name where output will be sent. Valid entries for PS_FILENAME are a file path (such as ~/IDL/myfile.ps) or *QUERY (which will prompt the user to supply a file name each time). If *QUERY is selected, then PS_FILENAME will have a default value of "idl.ps", which the user can change if so desired.
Flag for determining whether or not to place a timestamp on the PostScript output. Valid entries for TIMESTAMP are 0 (never), 1 (always), or *QUERY (ask the user each time). Recommended value: 0.
Flag for determining whether or not to save output to GIF files. Valid entries for DO_GIF are 0 (never), 1 (always), or *QUERY (ask the user each time). Recommended value: *QUERY
NOTE: the switches DO_JPEG, DO_BMP, DO_PNG, DO_PICT, DO_TIFF work in exactly the same way as DO_GIF.
Default GIF file name where output will be sent. Valid entries for GIF_FILENAME are a file path (such as ~/IDL/mygif.gif) or *QUERY (which will prompt the user to supply a file name each time). If *QUERY is selected, then GIF_FILENAME will have a default value of frame%NNN%, which the user can change if so desired. The token %NNN% will be replaced with a counting index, such as 001, 002, etc. Recommended value: *QUERY.
NOTE: the switches JPEG_FILENAME, BMP_FILENAME, PNG_FILENAME, PICT_FILENAME, and TIFF_FILENAME work in the same way as GIF_FILENAME.
ALSO NOTE: GIF file format support was removed in IDL version 5.4, but since has been restored in IDL versions 6.2 and higher. If you are using an older version of IDL we suggest that you upgrade to the most recent version so that you can take advantage of GIF file support.
7.2 The diaginfo.dat file
This file is where you list each different diagnostic category name and corresponding tracer offset. GAMAP assigns each diagnostic a different offset, which is specified in the line:
##### SPACING BETWEEN DIAGNOSTIC CATEGORY OFFSETS = 1000
These offsets are the same offsets listed in the tracerinfo.dat file (see Chapter 7.3).
Historically, GAMAP has used a diagnostic offset of 1000, which means that each diagnostic category could have a maximum of 1000 possible tracers. However, some diagnostic categories need to have more than 1000 tracers, either for "special chemistry" tracers or for quantities such as GMAO meteorological data fields. GAMAP v2–13 now allows you to specify the diagnostic offset within diaginfo.dat. For compatibility with older versions of GAMAP and GEOS–Chem, this offset is currently set to 1000. This offset value may be increased in a future version of GAMAP.
The diaginfo.dat file that ships with GAMAP v2–19 is available by clicking HERE (file will open in a new browser window). The # characters denote the start of comment lines, which will be ignored. If you have questions about how to modify this file, please contact Bob Yantosca (email: bmy at io dot harvard dot edu).
NOTE: you may not need to use the default diaginfo.datfile at all. GEOS–Chem can now create diaginfo.dat and tracerinfo.dat files that are customized to a given model simulation. If you keep these files in the same directory where the output files from the GEOS–Chem simulation are located and start GAMAP in that directory, then GAMAP will "customize" itself to the particular output files being read in.
7.3 The tracerinfo.dat files
This file is where you list each of the tracers that correspond to a given diagnostic category. You can also list the molecular weight, carbon number, default unit (and scale factor to multiply the original data by to convert to the default unit) for each tracer.
Click HERE to view the default tracerinfo.dat file that ships with GAMAP v2–19.
NOTE: You may not need to use the default tracerinfo.dat file at allse files at all. GEOS–Chem can now create customized versions of diaginfo.dat and tracerinfo.dat for each specific simulation type. However, if you want to read data that is not from a GEOS–Chem simulation, then you will have to modify the diaginfo.dat and tracerinfo.dat files to account for the data that you are trying to read.
Also, in the tracerinfo.dat files, # characters denote the start of comment lines, which will be ignored. You can modify the tracerinfo.dat files to suit your own purposes. If you have questions about how to modify these files, please contact the GEOS-Chem Support Team (email: geos-chem-supportg.harvard.edu).
Previous | Next | Printable View (no frames)