Changes between Version 509 and Version 510 of doc/app/errmsg

Timestamp:

May 22, 2018 1:25:57 PM (7 years ago)

Author:

Giersch

Comment:

--

doc/app/errmsg

@@ -105 +105 @@
 ||[=#PA0080 PA0080]   ||preprocessor switch for fftw is missing ||You have set [../inipar#fft_method fft_method] = '' 'fftw' '', but the fftw-code has not been activated by the corresponding cpp-preprocessor switch. Add '' {{{'-D__fftw'}}} '' to the {{{%cpp_options}}} line in the configuration file, touch file {{{fft_xy.f90}}} (e.g. by executing command {{{"touch trunk/SOURCE/fft_xy.f90"}}} and re-compile. ||
 ||[=#PA0081 PA0081]   || "..." = 0.0 while using a variable timestep and parallel netCDF4 is not allowed. || When using parallel NetCDF output ([../d3par#netcdf_data_format netcdf_data_format]>4) the number of output time levels must be calculated in the beginning of the simulation (see e.g. [#PA0384]). With a variable time step it is not possible to determine how many output time levels are needed to do an output at every time step. Therefore you have to set a fixed time step [../inipar#dt dt]. ||
-||[=#PA0082 PA0082]   ||number of statistic_regions = ... are not allowed ||Adjust parameter [../inipar#statistic_regions statistic_regions] in your parameter file to a value >= ''0''.  ||
+||[=#PA0082 PA0082]   ||number of statistic_regions = ... is not allowed ||Adjust parameter [../inipar#statistic_regions statistic_regions] in your parameter file to a value >= ''0''.  ||
 ||[=#PA0083 PA0083]   ||normalizing_region = ... must be >= 0 and <= ... (value of statistic_regions)  ||The region number given by [../d3par#normalizing_region normalizing_region] must be within the range [0, [../inipar#statistic_regions statistic_regions] ]. Adjust [../d3par#normalizing_region normalizing_region] appropriately in your parameter file. ||
-||[=#PA0084 PA0084]   ||dt_sort_particles is reset to 0.0 because of cloud_droplets = .TRUE. ||Using particles as cloud droplets ([../inipar#cloud_droplets cloud_droplets] = ''.TRUE.'') requires sorting of the particle array after each timestep. This warning means, that the respective steering parameter ([../parpar#dt_sort_particles dt_sort_particles]) for the resort-interval has been automatically reset to 0.0, in order to force a resort after each timestep. '''Not available from release 4.0 on.'''||
-||[=#PA0085 PA0085]   ||averaging_interval = ... must be <= dt_data_output = ... ||The [../d3par#averaging_interval averaging_interval] for output data must be smaller or equal to the output interval given by [../d3par#dt_data_output dt_data_output]. Adjust settings of these variables appropriately in the parameter file. ||
+||[=#PA0084 PA0084]   || ||message number is unused ||
+||[=#PA0085 PA0085]   ||averaging_interval = ... must be <= dt_data_output_av = ... ||The [../d3par#averaging_interval averaging_interval] for averaged output data must be smaller or equal to the output interval given by [../d3par#dt_data_output dt_data_output] or [../d3par#dt_data_output_av dt_data_output_av]. Adjust settings of these variables appropriately in the parameter file. ||
 ||[=#PA0086 PA0086]   ||averaging_interval_pr = ... must be <= dt_dopr = ... ||The [../d3par#averaging_interval_pr averaging_interval_pr] for profile output data must be smaller or equal to the output interval given by [../d3par#dt_dopr dt_dopr]. Adjust settings of these variables appropriately in the parameter file. ||
 ||[=#PA0087 PA0087]   ||averaging_interval_sp = ... must be <= dt_dosp = ... ||The [../sppar#averaging_interval_sp averaging_interval_sp] for spectra output data must be smaller or equal to the output interval given by [../sppar#dt_dosp dt_dosp]. Adjust settings of these variables appropriately in the parameter file. ||
@@ -119 +119 @@
 ||[=#PA0094 PA0094]   ||data_output_pr = ... is not implemented for cloud_physics = .FALSE.  ||The listed entries in the parameter file under  [../d3par#data_output_pr data_output_pr] are only available for [../inipar#cloud_physics cloud_physics]= .T.. There could also be a typo in [../d3par#data_output_pr data_output_pr] (an output variable was used that does not exist in PALM). ||
 ||[=#PA0095 PA0095]   ||data_output_pr = ... is not implemented for cloud_physics = .FALSE. and humidity = .FALSE.   ||The listed entries in the parameter file under  [../d3par#data_output_pr data_output_pr] are only available for [../inipar#cloud_physics cloud_physics]= .T. or [../inipar#cloud_physics cloud_physics]= .F. and [../inipar#humidity humidity]=.T.. There could also be a typo in [../d3par#data_output_pr data_output_pr] (an output variable was used that does not exist in PALM).||
-||[=#PA0096 PA0096]   ||data_output_pr = ... is not implemented for cloud_physics = .FALSE. or cloud_droplets = .FALSE.   ||The listed entries in the parameter file under  [../d3par#data_output_pr data_output_pr] are only available for [../inipar#cloud_droplets cloud_droplets]= .T. or [../inipar#cloud_physics cloud_physics]=.T.. There could also be a typo in [../d3par#data_output_pr data_output_pr] (an output variable was used that does not exist in PALM). ||
+||[=#PA0096 PA0096]   ||data_output_pr = ... is not implemented for cloud_physics = .FALSE. and cloud_droplets = .FALSE.   ||The listed entries in the parameter file under  [../d3par#data_output_pr data_output_pr] are only available for [../inipar#cloud_droplets cloud_droplets]= .T. or [../inipar#cloud_physics cloud_physics]=.T.. There could also be a typo in [../d3par#data_output_pr data_output_pr] (an output variable was used that does not exist in PALM). ||
 ||[=#PA0097 PA0097]   ||illegal value for data_output_pr or data_output_pr_user = "..."   ||No matching variable was found for the given identifier in the parameter file. Possible reasons are: (a) a typo in the parameter file, (b) a user-defined variable has not been defined in {{{user_check_data_output.f90}}}, (c) the string length of the user-defined variable exceeds the current limits (see [../userint/output here]).  ||
-||[=#PA0098 PA0098]   ||illegal value for data_output_pr = "..."   ||No matching variable was found for the given identifier in the parameter file. This error is most likely related to a typo in the parameter file (a output variable was used that does not exist in PALM. ||
+||[=#PA0098 PA0098]   ||illegal value for data_output_pr = "..."   ||No matching variable was found for the given identifier in the parameter file. This error is most likely related to a typo in the parameter file (a output variable was used that does not exist in PALM). ||
 ||[=#PA0100 PA0099]   ||netCDF: netCDF4 parallel output requested but no cpp-directive !__netcdf4_parallel given switch back to netCDF4 non-parallel output ||[../d3par#netcdf_data_format  netcdf_data_format ] > 4 has been set. This requires netCDF4 features including parallel file support, which have to be activated by setting the cpp-switches {{{-D__netcdf4}}} '''and''' {{{-D__netcdf4_parallel}}} in the configuration file ({{{%cpp_options}}}). It also requires a netCDF4 library which supports parallel I/O. Set {{{-I}}}, {{{-L}}} and {{{-l}}} options in compile ({{{%fopts}}}) and load ({{{%lopts}}}) options of the configuration file appropriately. \\\\ Job will be continued with {{{netcdf_data_format = netcdf_data_format - 2}}}. ||
 ||[=#PA0100 PA0100]   ||momentum_advec of the restart run differs from momentum_advec of the initial run   ||The advection scheme for the momentum equations [../inipar#momentum_advec momentum_advec] used in the restart run differs from the advection scheme used in the corresponding initial run. The advection scheme that is used in a restart run must be the same as the one that was used in the initial run.  ||