History Control: Difference between revisions

Todling (talk | contribs)
No edit summary
Todling (talk | contribs)
No edit summary
Line 4: Line 4:




'COLLECTIONS: 'geosgcm_prog'
COLLECTIONS: 'geosgcm_prog'
             'geosgcm_surf'
             'geosgcm_surf'
             'geosgcm_moist'
             'geosgcm_moist'
Line 18: Line 18:
>>>HIST_GOCART<<<    'tavg2d_aer_x'
>>>HIST_GOCART<<<    'tavg2d_aer_x'
>>>HIST_GOCART<<<    'tavg3d_aer_p'
>>>HIST_GOCART<<<    'tavg3d_aer_p'
::'
::




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.


Users can control the 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.
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.