Changes between Version 679 and Version 680 of doc/app/errmsg


Ignore:
Timestamp:
Feb 28, 2020 8:08:19 AM (5 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v679 v680  
    901901||[=#PA0706 PA0706]  || dt_virtual_measurement must be > 0.0 ||This parameter is used to estimate the number of output timesteps in the output NetCDF files. With zero-valued numbers this is not possible. ||
    902902||[=#PA0707 PA0707]  || Run will be terminated because virtual measurement times index exceeds its maximum value in the output files. A restart run is forced. ||Please see comment under PA0706. ||
    903 ||[=#PA0708 PA0708]  || If virtual measurements are taken, parallel NetCDF is required.||The PALM code need to be compiled with a parallel NetCDF library. ||
     903||[=#PA0708 PA0708]  || If virtual measurements are taken, parallel NetCDF is required. ||The PALM code need to be compiled with a parallel NetCDF library. ||
     904||[=#PA0710 PA0710]  || raytrace_mpi_rma = .T. not allowed in serial mode. ||You have compiled the PALM code for serial mode, i.e. without setting the preprocessor switch {{{-D __parallel}}} in the configuration file. Radiation calculations for the urban environment with ray tracing using one-sided MPI communication only works for the parallel mode. Either set the switch {{{-D __parallel}}} in your config file, or set raytrace_mpi_rma = .F. in your NAMELIST file. ||
    904905||[=#UI0001 UI0001]   ||unknown location "..."   ||The location of the CALL of user_actions has to be one of 'before_timestep', 'after_integration', 'after_timestep', 'u_tendency' 'v_tendency', 'w_tendency', 'pt_tendency', 'sa_tendency', 'e_tendency', 'q_tendency', 's_tendency'. The location of the CALL of user_actions_ij has to be one of 'u_tendency' 'v_tendency', 'w_tendency', 'pt_tendency', 'sa_tendency', 'e_tendency', 'q_tendency', 's_tendency'.   ||
    905906||[=#UI0002 UI0002]   ||location "..." is not allowed to be called with parameters "i" and "j"   || The location of the CALL of user_actions_ij must not be 'before_timestep', 'after_integration', 'after_timestep' ||