- Timestamp:
- 2013-07-24T11:48:35+02:00 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Chap_DIA.tex
r3764 r3989 1 1 % ================================================================ 2 % Chapter ÑI/O & Diagnostics2 % Chapter � I/O & Diagnostics 3 3 % ================================================================ 4 4 \chapter{Ouput and Diagnostics (IOM, DIA, TRD, FLO)} … … 609 609 set via an equivalent and identically named namelist to \textit{namnc4} 610 610 in \np{xmlio\_server.def}. Typically this namelist serves the mean files 611 whilst the \n p{ namnc4} in the main namelist file continues to serve the611 whilst the \ngn{ namnc4} in the main namelist file continues to serve the 612 612 restart files. This duplication is unfortunate but appropriate since, if 613 613 using io\_servers, the domain sizes of the individual files produced by the … … 631 631 trend of the dynamics and/or temperature and salinity time evolution equations 632 632 is stored in three-dimensional arrays just after their computation ($i.e.$ at the end 633 of each $dyn\cdots.F90$ and/or $tra\cdots.F90$ routines). These trends are then 633 of each $dyn\cdots.F90$ and/or $tra\cdots.F90$ routines). Options are defined by 634 \ngn{namtrd} namelist variables. These trends are then 634 635 used in \mdl{trdmod} (see TRD directory) every \textit{nn\_trd } time-steps. 635 636 … … 675 676 The on-line computation of floats advected either by the three dimensional velocity 676 677 field or constraint to remain at a given depth ($w = 0$ in the computation) have been 677 introduced in the system during the CLIPPER project. The algorithm used is based 678 introduced in the system during the CLIPPER project. Options are defined by \ngn{namflo} 679 namelis variables. The algorithm used is based 678 680 either on the work of \cite{Blanke_Raynaud_JPO97} (default option), or on a $4^th$ 679 681 Runge-Hutta algorithm (\np{ln\_flork4}=true). Note that the \cite{Blanke_Raynaud_JPO97} … … 687 689 688 690 689 In case of Ariane convention, input filename is \np{ "init\_float\_ariane"}. Its format is:691 In case of Ariane convention, input filename is \np{init\_float\_ariane}. Its format is: 690 692 691 693 \texttt{ I J K nisobfl itrash itrash } … … 709 711 710 712 711 In the other case ( longitude and latitude ), input filename is \np{"init\_float"}. Its format is:713 In the other case ( longitude and latitude ), input filename is init\_float. Its format is: 712 714 713 715 \texttt{ Long Lat depth nisobfl ngrpfl itrash} … … 732 734 733 735 \np{jpnfl} is the total number of floats during the run. 734 When initial positions are read in a restart file ( \np{ln\_rstflo = .TRUE.}), \np{jpnflnewflo}736 When initial positions are read in a restart file ( \np{ln\_rstflo}= .TRUE. ), \np{jpnflnewflo} 735 737 can be added in the initialization file. 736 738 … … 740 742 is the frequency of creation of the float restart file. 741 743 742 Output data can be written in ascii files (\np{ln\_flo\_ascii = .TRUE.}). In that case,743 output filename is \np{is trajec\_float}.744 745 Another possiblity of writing format is Netcdf (\np{ln\_flo\_ascii = .FALSE.}). There are 2 possibilities:746 747 - if (\key{iomput}) is used, outputs are selected in \np{iodef.xml}. Here it is an example of specification744 Output data can be written in ascii files (\np{ln\_flo\_ascii} = .TRUE. ). In that case, 745 output filename is trajec\_float. 746 747 Another possiblity of writing format is Netcdf (\np{ln\_flo\_ascii} = .FALSE. ). There are 2 possibilities: 748 749 - if (\key{iomput}) is used, outputs are selected in iodef.xml. Here it is an example of specification 748 750 to put in files description section: 749 751 … … 768 770 769 771 770 - if (\key{iomput}) is not used, a file called \np{trajec\_float.nc}will be created by IOIPSL library.772 - if (\key{iomput}) is not used, a file called trajec\_float.nc will be created by IOIPSL library. 771 773 772 774 … … 789 791 %---------------------------------------------------------------------------------------------------------- 790 792 791 Concerning the on-line Harmonic analysis, some parameters are available in namelist: 793 Concerning the on-line Harmonic analysis, some parameters are available in namelist 794 \ngn{namdia\_harm} : 792 795 793 796 - \texttt{nit000\_han} is the first time step used for harmonic analysis … … 841 844 842 845 843 Namelist parameters control how frequently the flows are summed and the time scales over which844 they are averaged, as well as the level of output for debugging:846 Namelist variables in \ngn{namdct} control how frequently the flows are summed 847 and the time scales over which they are averaged, as well as the level of output for debugging: 845 848 846 849 %------------------------------------------namdct---------------------------------------------------- … … 992 995 993 996 The poleward heat and salt transports, their advective and diffusive component, and 994 the meriodional stream function can be computed on-line in \mdl{diaptr} by setting995 \np{ln\_diaptr} to true (see the \textit{ namptr} namelist below).997 the meriodional stream function can be computed on-line in \mdl{diaptr} 998 \np{ln\_diaptr} to true (see the \textit{\ngn{namptr} } namelist below). 996 999 When \np{ln\_subbas}~=~true, transports and stream function are computed 997 1000 for the Atlantic, Indian, Pacific and Indo-Pacific Oceans (defined north of 30\deg S)
Note: See TracChangeset
for help on using the changeset viewer.