Home

Context Navigation

errmsg

Timestamp:: Jun 8, 2017 12:49:31 PM (8 years ago)
Author:: Giersch
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/errmsg

-                      v401
+                      v402
 ||[=#PA0156 PA0156]   ||noncyclic boundary conditions require conserve_volume_flow_mode = "inflow_profile"   || [[span(style=color: #FF0000, Micha)]] ||
 ||[=#PA0157 PA0157]   ||nonzero bulk velocity requires conserve_volume_flow = .T. and conserve_volume_flow_mode = "bulk_velocity"   || The bulk velocity is used to prescribe a volume flow which then should be conserved. This, however, requires [../inipar#conserve_volume_flow conserve_volume_flow] = .T. and [../inipar#conserve_volume_flow_mode conserve_volume_flow_mode] = "bulk_velocity". ||
 ||[=#PA0158 PA0158]   ||no vertical boundary condition for variable "..."   || Routine advec_s_bc was called for a variable, which does not have a specific boundary condition implemented. ||
 ||[=#PA0159 PA0159]   ||no term for component "..."   || Routine buoyancy was called for the u/w-component while an inclined surface was used. In case of an inclined surface (see [../inipar#alpha_surface alpha_surface]) the buoyancy term appears in the equation of motion of the w-component and u-component. There is no buoyancy term implemented for the v-component as the surface can only be inclined in x-direction and no buoyancy term is required for the v-component. ||
+||[=#PA0158 PA0158]   ||no vertical boundary condition for variable "..."   || Routine {{{advec_s_bc}}} was called for a variable, which does not have a specific boundary condition implemented. ||
+||[=#PA0159 PA0159]   ||no term for component "..."   || Routine {{{buoyancy}}} was called for the u/w-component while an inclined surface was used. In case of an inclined surface (see [../inipar#alpha_surface alpha_surface]) the buoyancy term appears in the equation of motion of the w-component and u-component. There is no buoyancy term implemented for the v-component as the surface can only be inclined in x-direction and no buoyancy term is required for the v-component. ||
 ||[=#PA0160 PA0160]   ||non-cyclic lateral boundaries along x do not allow calculation of spectra along x       || In case of non-cyclic conditions spectra would be largely affected by the non-cyclic lateral boundaries since this conflicts with the basic assumption used for the FFT that the spatial extention in the x and y-direction are infinitely large. See also  [../sppar#data_output_sp data_output_sp]. ||
 ||[=#PA0161 PA0161]   ||sorry, calculation of spectra in non parallel mode is still not realized       || Calculation of spectra in non-parallel mode is not implemented. ||
 …
 ||[=#PA0164 PA0164]   ||run will be terminated due to user settings of restart_time / dt_restart new restart time is: ... s   ||A restart run is established by PALM due to the setting of  [../d3par#restart_time restart_time] and/or [../d3par#dt_restart dt_restart] and the new restart time is calculated. Have a look at [../runs Initialization and restart runs] for further information.  ||
 ||[=#PA0165 PA0165]   ||re-open of unit 14 is not verified. Please check results!   ||The file with unit number 14 contains the binaries  [../iofiles#BINOUT BINOUT]. It was opened at least a second time by user specific settings. This is not verified, so check the results carefully.  ||
 ||[=#PA0166 PA0166]   ||re-opening of file-id ... is not allowed   || It was tried to re-open a file, which had already been opened once during the simulation. Only certain files are allowed to be re-opened to prevent errors. If you are sure that the file can be re-opened without causing any errors, you may add the file-id to the list in routine check_open. See also the list of [../iofiles I/O-files]. ||
+||[=#PA0166 PA0166]   ||re-opening of file-id ... is not allowed   || It was tried to re-open a file, which had already been opened once during the simulation. Only certain files are allowed to be re-opened to prevent errors. If you are sure that the file can be re-opened without causing any errors, you may add the file-id to the list in routine {{{check_open}}}. See also the list of [../iofiles I/O-files]. ||
 ||[=#PA0167 PA0167]   ||opening file-id ... not allowed for PE ...   || Certain files are only allowed to be opened on a certain PE (in most cases only on PE0). Please check if your file can be opened on this PE and choose a different file-id. ||
 ||[=#PA0168 PA0168]   ||opening file-id ... is not allowed since it is used otherwise   || Certain file-ids are reserved for files used temporarily outside of the main program. Please refer to the list of [../iofiles I/O-files] and choose an unused file-id. ||
 ||[=#PA0169 PA0169]   ||current user-interface revision "..." does not match the required revision r.... ||You are using a user-interface which does not match the installed PALM revision. One reason might be that the default user-interface of the newest PALM revision has been changed by the PALM developers (e.g. because some parameters have been added to parameter-lists of subroutine calls). Please carefully read the [wiki:doc/tec/changelog source code change log], where these kind of changes are announced, and where also hints will be given for how to adjust existing user-interfaces. ||
 ||[=#PA0170 PA0170]   ||pointer for array ".." can't be associated   ||This is an internal error message from the pmc (PALM model coupler) which is responsible for data exchange in nested runs. Please submit a trouble ticket if you are sure that you did not modify the source code of the model coupler (routine names is ''pmc_interface_mod.f90'').  ||
+||[=#PA0170 PA0170]   ||pointer for array ".." can't be associated   ||This is an internal error message from the pmc (PALM model coupler) which is responsible for data exchange in nested runs. Please submit a trouble ticket if you are sure that you did not modify the source code of the model coupler ({{{pmc_interface_mod.f90}}}).  ||
 ||[=#PA0171 PA0171]   ||netCDF: netCDF4 format requested but no cpp-directive !__netcdf4 given switch back to 64-bit offset format  ||[../d3par#netcdf_data_format  netcdf_data_format ] > 2 has been set. This requires netCDF4 features, which have to be activated by setting the cpp-directive {{{__netcdf4}}} in the configuration file ({{{%cpp_options}}}). It also requires a netCDF4 library. Set {{{-I}}}, {{{-L}}} and {{{-l}}} options in compile ({{{%copts}}}) and load ({{{%lopts}}}) options of the configuration file appropriately.  ||
 ||[=#PA0172 PA0172]   ||no OPEN-statement for file-id ...   || Routine check_open was called with an unknown file-id. Please check the file-id for a typo or open the file manually using an OPEN(...) statement. ||
 ||[=#PA0173 PA0173]   ||wrong component: ...   || Routine coriolis can only be called for component 1, 2 and 3, which correspond to the wind speed components u, v and w. Other components do not exist. ||
 ||[=#PA0174 PA0174]   ||wrong argument expected: ... given:   ||Internal code error. Please inform the PALM developers. ||
+||[=#PA0172 PA0172]   ||no OPEN-statement for file-id ...   || Routine {{{check_open}}} was called with an unknown file-id. Please check the file-id for a typo or open the file manually using an OPEN(...) statement. ||
+||[=#PA0173 PA0173]   ||wrong component: ...   || Routine {{{coriolis}}} can only be called for component 1, 2 and 3, which correspond to the wind speed components u, v and w. Other components do not exist. ||
+||[=#PA0174 PA0174]   ||wrong argument expected: ... given:   ||Internal code error in routine {{{cpu_log}}}. Please inform the PALM developers. ||
 ||[=#PA0175 PA0175]   ||   ||message number is unused  ||
 ||[=#PA0176 PA0176]   ||negative time interval occured PE ... L=PAUSE "..." new=... last=...   || The time measurement via cpu_log gave a negative time interval. This error could be caused when cpu_log was called with option "pause" before the corresponding cpu_log was initialised with option "start". ||
+||[=#PA0176 PA0176]   ||negative time interval occured PE ... L=PAUSE "..." new=... last=...   || The time measurement via routine {{{cpu_log}}} gave a negative time interval. This error could be caused when {{{cpu_log}}} was called with option "pause" before the corresponding {{{cpu_log}}} was initialised with option "start". ||
 ||[=#PA0177 PA0177]   ||negative time interval occured PE ... L=STOP "..." new=... last=... isum=...   || The time measurement via cpu_log gave a negative time interval. This error could be caused when cpu_log was called with option "stop" before the corresponding cpu_log was initialised with option "start" or before it was continued with option "continue". ||
 ||[=#PA0178 PA0178]   ||negative time interval occured PE ... L=STOP "..." sum=... mtime=...   || The time measurement via cpu_log gave a negative time interval. This error could be caused when cpu_log was called with option "stop" before the corresponding cpu_log was initialised with option "start" or before it was continued with option "continue". ||