History Control: Difference between revisions

Line 25:

Users can control freely the collections (or output streams) they want by simply commenting or uncommenting existing collections --- a "#" sign is a comment, which the reading software ignores.

Each collection defines its own meta-information.

Each collection defines its own meta-information. For example, the output stream <<geosgcm_prog>> in the COLLECTION table above is associated with the following entries in the HISTORY resource file:

Line 50:

'O3' , 'CHEMISTRY' ,

::

Combined with the stream name, the template entry defines the filename, that is, on 010000 UTC of 01April2010 the file will be written out with the name: geosgcm_prog.20100401_0100z.nc4; the archive entry specifies a directory where the files will land; the format makes it complaint with the CFIO standard in GEOS; the frequency specifies how often this stream will be written out; the vertical units are defined in pressure, as opposed to model index levels; the levels specifies desired levels for the model output, and fields gives a list of fields to be written. The variable grid_label defines the resolution of the output: the notation @HIST_IM and @HIST_JM means that these entries will be defined at setup time (as opposed to runtime).

Considerable more detail about GEOS GCM output stream and conventions can be found under: https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf

@@ Line 25: / Line 25: @@
 Users can control freely the collections (or output streams) they want by simply commenting or uncommenting existing collections --- a "#" sign is a comment, which the reading software ignores.
-Each collection defines its own meta-information.
+Each collection defines its own meta-information. For example, the output stream <<geosgcm_prog>> in the COLLECTION table above is associated with the following entries in the HISTORY resource file:
@@ Line 50: / Line 50: @@
                            'O3'       , 'CHEMISTRY'    ,
                            ::
+Combined with the stream name, the template entry defines the filename, that is, on 010000 UTC of 01April2010 the file will be written out with the name: geosgcm_prog.20100401_0100z.nc4; the archive entry specifies a directory where the files will land; the format makes it complaint with the CFIO standard in GEOS; the frequency specifies how often this stream will be written out; the vertical units are defined in pressure, as opposed to model index levels; the levels specifies desired levels for the model output, and fields gives a list of fields to be written. The variable grid_label defines the resolution of the output: the notation @HIST_IM and @HIST_JM means that these entries will be defined at setup time (as opposed to runtime).
 Considerable more detail about GEOS GCM output stream and conventions can be found under: https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf