History Control: Difference between revisions

Line 51:

::

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).

Combined with the stream name, the template entry defines the filename, that is, at 060000 UTC on 1 April 2010 a file will be written out with the name: geosgcm_prog.20100401_0600z.nc4; the archive entry specifies a directory where the file will land; the format makes it complaint with the CFIO standard in GEOS; the frequency specifies how often a particular collection will be written out; the vertical units are defined in pressure, as opposed to model index levels; the levels entry specifies desired levels for the model output, and the fields entry allows for specification of a list of fields to be written. The variable grid_label defines the resolution of the output: here the use of the symbol "@", as in @HIST_IM and @HIST_JM, means that these are variables to 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 51: / Line 51: @@
                            ::
-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).
+Combined with the stream name, the template entry defines the filename, that is, at 060000 UTC on 1 April 2010 a file will be written out with the name: geosgcm_prog.20100401_0600z.nc4; the archive entry specifies a directory where the file will land; the format makes it complaint with the CFIO standard in GEOS; the frequency specifies how often a particular collection will be written out; the vertical units are defined in pressure, as opposed to model index levels; the levels entry specifies desired levels for the model output, and the fields entry allows for specification of a list of fields to be written. The variable grid_label defines the resolution of the output: here the use of the symbol "@", as in @HIST_IM and @HIST_JM, means that these are variables to 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