History Control: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
The output of GEOS GCM is subset in files, referred to as COLLECTIONS. An example of a COLLECTION table is provided below: | The output of GEOS GCM is subset in files, referred to as COLLECTIONS. An example of a COLLECTION table is provided below: | ||
COLLECTIONS: 'geosgcm_prog' | COLLECTIONS: 'geosgcm_prog' | ||
'geosgcm_surf' | 'geosgcm_surf' | ||
| Line 19: | Line 19: | ||
>>>HIST_GOCART<<< 'tavg3d_aer_p' | >>>HIST_GOCART<<< 'tavg3d_aer_p' | ||
\# 'geosgcm_iau' | \# 'geosgcm_iau' | ||
# 'geosgcm_conv' | \# 'geosgcm_conv' | ||
# 'goswim_catch' | \# 'goswim_catch' | ||
# 'goswim_land' | \# 'goswim_land' | ||
# 'goswim_landice' | \# 'goswim_landice' | ||
# 'geosgcm_lidar | \# 'geosgcm_lidar' | ||
:: | :: | ||
The table follows MAPL's (and MPEU's) convention of starting with a name (COLLECTION) and editing with two colons (::). The particular example above would be found in a file with the extension "tmpl' to indicate it is a template file (meaning, it has entries in a format >>>ENTRY<<< which get replaced by something meaningful at runtime. | The table follows MAPL's (and MPEU's) convention of starting with a name (COLLECTION) and editing with two colons (::). The particular example above would be found in a file with the extension "tmpl' to indicate it is a template file (meaning, it has entries in a format >>>ENTRY<<< which get replaced by something meaningful at runtime. | ||