- Timestamp:
- 2013-10-20T20:48:20+02:00 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2013/dev_r3987_UKMO4_OBS/DOC/TexFiles/Chapters/Chap_DIA.tex
r3976 r4081 362 362 \subsubsection{Use of Groups} 363 363 364 Groups can be used for 2 purposes. Firstly, the group can be used to define common attributes to be shared by the elements of the group through theinheritance. In the following example, we define a group of field that will share a common grid ''grid\_T\_2D''. Note that for the field ''toce'', we overwrite the grid definition inherited from the group by ''grid\_T\_3D''.364 Groups can be used for 2 purposes. Firstly, the group can be used to define common attributes to be shared by the elements of the group through inheritance. In the following example, we define a group of field that will share a common grid ''grid\_T\_2D''. Note that for the field ''toce'', we overwrite the grid definition inherited from the group by ''grid\_T\_3D''. 365 365 \vspace{-20pt} 366 366 \begin{alltt} {{\scriptsize … … 386 386 \end{verbatim} 387 387 }}\end{alltt} 388 that can be directly include in a file through the following syntax:388 that can be directly included in a file through the following syntax: 389 389 \vspace{-20pt} 390 390 \begin{alltt} {{\scriptsize … … 466 466 \end{verbatim} 467 467 }}\end{alltt} 468 However it is often very convienent to define the file name with the name of the experi ence, the output file frequency and the date of the beginning and the end of the simulation (which are informations stored either in the namelist or in the XML file). To do so, we added the following rule: if the id of the tag file is ''fileN''(where N = 1 to 99) or one of the predefined section or mooring(see next subsection), the following part of the name and the name\_suffix (that can be inherited) will be automatically replaced by:\\468 However it is often very convienent to define the file name with the name of the experiment, the output file frequency and the date of the beginning and the end of the simulation (which are informations stored either in the namelist or in the XML file). To do so, we added the following rule: if the id of the tag file is ''fileN''(where N = 1 to 99) or one of the predefined sections or moorings (see next subsection), the following part of the name and the name\_suffix (that can be inherited) will be automatically replaced by:\\ 469 469 \\ 470 470 \begin{tabular}{|p{4cm}|p{8cm}|} … … 474 474 \hline 475 475 \centering @expname@ & 476 the experi encename (from cn\_exp in the namelist) \\476 the experiment name (from cn\_exp in the namelist) \\ 477 477 \hline 478 478 \centering @freq@ & … … 590 590 file\_definition & 591 591 encapsulates the definition of all the files that will be outputted & 592 enabled, min\_digits, name, name\_suffix, output\_level, split\_f ormat, split\_freq, sync\_freq, type, src &592 enabled, min\_digits, name, name\_suffix, output\_level, split\_freq\_format, split\_freq, sync\_freq, type, src & 593 593 context & 594 594 file or file\_group \\ … … 596 596 file\_group & 597 597 encapsulates a group of files that will be outputted & 598 enabled, description, id, min\_digits, name, name\_suffix, output\_freq, output\_level, split\_f ormat, split\_freq, sync\_freq, type, src &598 enabled, description, id, min\_digits, name, name\_suffix, output\_freq, output\_level, split\_freq\_format, split\_freq, sync\_freq, type, src & 599 599 file\_definition, file\_group & 600 600 file or file\_group \\ … … 602 602 file & 603 603 define the contents of a file to be outputted & 604 enabled, description, id, min\_digits, name, name\_suffix, output\_freq, output\_level, split\_f ormat, split\_freq, sync\_freq, type, src &604 enabled, description, id, min\_digits, name, name\_suffix, output\_freq, output\_level, split\_freq\_format, split\_freq, sync\_freq, type, src & 605 605 file\_definition, file\_group & 606 606 field \\ … … 775 775 field family \\ 776 776 \hline 777 split\_f ormat&778 date format used in the name of splitted output files. can be spécified using the following syntaxe: \%y, \%mo, \%d, \%h \%mi and \%s&779 split\_f ormat= "\%yy\%mom\%dd" &777 split\_freq & 778 frequency at which to temporally split output files. Units can be ts (timestep), y, mo, d, h, mi, s. Useful for long runs to prevent over-sized output files.& 779 split\_freq="1mo" & 780 780 file family \\ 781 781 \hline 782 split\_freq & 783 split output files frequency. units can be ts (timestep), y, mo, d, h, mi, s. & 784 split\_freq="1mo" & 782 split\_freq\-\_format & 783 date format used in the name of temporally split output files. Can be specified 784 using the following syntaxes: \%y, \%mo, \%d, \%h \%mi and \%s & 785 split\_freq\_format= "\%y\%mo\%d" & 785 786 file family \\ 786 787 \hline … … 812 813 \hline 813 814 type (1)& 814 specify if the output files must be split(multiple\_file) or not (one\_file) &815 specify if the output files are to be split spatially (multiple\_file) or not (one\_file) & 815 816 type="multiple\_file" & 816 817 file familly \\
Note: See TracChangeset
for help on using the changeset viewer.
