Changes between Version 514 and Version 515 of doc/app/errmsg


Ignore:
Timestamp:
May 23, 2018 7:34:04 AM (7 years ago)
Author:
Giersch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v514 v515  
    199199||[=#PA0156 PA0156]   ||   ||   message number is unused. ||
    200200||[=#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". ||
    201 ||[=#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. ||
    202 ||[=#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. ||
     201||[=#PA0158 PA0158]   ||no vertical boundary condition for variable "..."   || Routine {{{advec_s_bc}}} which calculates the advection term for scalar quantities using the Bott-Chlond scheme was called for a variable, which does not have a specific boundary condition implemented (Adding top and bottom boundaries according to the relevant boundary conditions is not possible). This should not happen. Please submit a [/newticket trouble ticket]. ||
     202||[=#PA0159 PA0159]   ||no term for component "..."   || Routine {{{buoyancy}}} was called for a different wind component than 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. This should not happen. Please submit a [/newticket trouble ticket]. ||
    203203||[=#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]. ||
    204204||[=#PA0161 PA0161]   ||sorry, calculation of spectra in non parallel mode is still not realized       || Calculation of spectra in non-parallel mode is not implemented. ||
    205205||[=#PA0162 PA0162]   ||non-cyclic lateral boundaries along y do not allow calculation of spectra along y       || 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]. ||
    206206||[=#PA0163 PA0163]   ||run will be terminated because it is running out of job cpu limit remaining time: ... s termination time needed: ... s   ||In case that [../d3par#restart_time restart_time] has not been set manually, PALM determines internally when a new restart run has to be carried out depending on the setting of [../d3par#termination_time_needed termination_time_needed]. Within the remaining time PALM will, for example, copy binary files for restart runs, archive or transfer result data. Have a look at [../runs Initialization and restart runs] for further information. ||
    207 ||[=#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.  ||
     207||[=#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.  ||
    208208||[=#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.  ||
    209209||[=#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]. ||