Changes between Initial Version and Version 1 of doc/app/spectra_parameters

Timestamp:

Sep 13, 2010 9:46:58 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/spectra_parameters

@@ +1 @@
+Standard table:\\
+||='''Parameter Name'''  =||='''Type'''  =||='''Default Value'''  =||='''Explanation'''  =||
+|----------------
+{{{#!td style="vertical-align:top; text-align:left;width: 150px"
+[=#averaging_interval_sp '''averaging_interval_sp''']
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
+R
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 100px"
+value of [#averaging_interval averaging_interval]
+}}}
+{{{#!td
+Averaging interval for spectra output to local file [#DATA_1D_SP_NETCDF DATA_1D_SP_NETCDF] and/or  [#PLOTSP_X_DATA PLOTSP_X_DATA] / [#PLOTSP_Y_DATA PLOTSP_Y_DATA] (in s). \\\\
+If this parameter is given a non-zero value, temporally averaged spectra data are output. By default, spectra data are not subject to temporal averaging. The interval length is limited by the parameter [#dt_dosp dt_dosp]. In any case '''averaging_interval_sp <= dt_dosp''' must hold. \\\\
+If an interval is defined, then by default the average is calculated from the data values of all timesteps lying within this interval. The number of time levels entering into the average can be reduced with the parameter [#dt_averaging_input_pr dt_averaging_input_pr]. \\\\
+If an averaging interval can not be completed at the end of a run, it will be finished at the beginning of the next restart run. Thus for restart runs, averaging intervals do not necessarily begin at the beginning of the run.
+}}}
+|----------------
+{{{#!td style="vertical-align:top; text-align:left;width: 150px"
+[=#comp_spectra_level '''comp_spectra_level''']
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
+I(100)
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 100px"
+no level
+}}}
+{{{#!td
+Vertical level for which horizontal spectra are to be calculated and output (gridpoints). \\\\
+Spectra can be calculated for up to 100 levels.
+}}}
+|----------------
+{{{#!td style="vertical-align:top; text-align:left;width: 150px"
+[=#data_output_sp '''data_output_sp''']
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
+C*10 (10)
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 100px"
+10 * ' '
+}}}
+{{{#!td
+Quantities for which horizontal spectra are to be calculated and output. \\\\
+Allowed standard values are: '''data_output_sp''' = '' 'u', 'v', 'w', 'pt', 'q' ''. The user may define further quantities '''!!!(see chapter 3.5.4 part 5)!!!'''. \\\\
+Spectra are calculated using the FFT-method defined by [#fft_method fft_method]. \\\\
+By default spectra data are output to the local file [#DATA_1D_SP_NETCDF DATA_1D_SP_NETCDF]. The file's format is NetCDF. Further details about processing NetCDF data are given in '''!!!chapter 4.5.1!!!'''. \\\\
+The temporal interval of the output times of profiles is assigned via the parameter [#dt_dosp dt_dosp]. \\\\
+The vertical levels for which spectra are to be computed and output must be given by parameter [#comp_spectra_level comp_spectra_level]. \\\\
+'''Note:''' \\
+Beside '''data_output_sp''', values '''must''' be given for each of the parameters,  [#comp_spectra_level comp_spectra_level], and [#spectra_direction spectra_direction], otherwise '''no''' output will be created! \\\\
+
+
+}}}
+|----------------