History Control: Difference between revisions

Line 18:

>>>HIST_GOCART<<< 'tavg2d_aer_x'

>>>HIST_GOCART<<< 'tavg3d_aer_p'

# 'geosgcm_iau'

# 'geosgcm_conv'

# 'goswim_catch'

# 'goswim_land'

# 'goswim_landice'

# 'geosgcm_lidar'

# 'geosgcm_parasol'

# 'geosgcm_modis'

# 'geosgcm_radar'

# 'geosgcm_isccp'

# 'geosgcm_misr'

::

Line 53:

Line 64:

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

It

Considerably more detail about GEOS GCM output streams and conventions, specifically related to the MERRA-2, can be found under: https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf and those related to the GMAO Forward Processing system for Instrument Teams (FPIT) can be found under:

@@ Line 18: / Line 18: @@
   >>>HIST_GOCART<<<     'tavg2d_aer_x'
   >>>HIST_GOCART<<<     'tavg3d_aer_p'
+ #             'geosgcm_iau'
+ #             'geosgcm_conv'
+ #             'goswim_catch'
+ #             'goswim_land'
+ #             'goswim_landice'
+ #             'geosgcm_lidar'
+ #             'geosgcm_parasol'
+ #             'geosgcm_modis'
+ #             'geosgcm_radar'
+ #             'geosgcm_isccp'
+ #             'geosgcm_misr'
                ::
@@ Line 53: / Line 64: @@
 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
+It
+Considerably more detail about GEOS GCM output streams and conventions, specifically related to the MERRA-2, can be found under: https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf and those related to the GMAO Forward Processing system for Instrument Teams (FPIT) can be found under: