Changes between Version 841 and Version 842 of doc/app/errmsg

Timestamp:

Jan 12, 2023 4:42:36 PM (22 months ago)

Author:

raasch

Comment:

--

doc/app/errmsg

@@ -1041 +1041 @@
 ||[=#PA0846 PA0846]   ||Dimension "time_inflow" in dynamic input file contains fill values. || Fill values are not allowed in the time dimension. ||
 ||[=#PA0847 PA0847]   || input_block_size must be smaller or equal than 2 x the subdomain size in x-direction, which is: nxr - nxl + 1, and larger or equal than 2. || In the read-from-file inflow method, the input block size of the boundary data can be customized, in order to allow input of multiple timesteps at once to avoid NetCDF IO every timestep. In order to contrain the input size to avoid any memory exceedance, the size of input boundary data is limited to maximum two three-dimensional arrays. Please check the domain decomposition in the RUN_CONTROL or HEADER file and decrease input_block_size accordingly. Alternatively, the domain-decomposition along the x-dimension can be changed via the namelist parameter [../runtime_parameters#npex npex]. ||
+||[=#PA0848 PA0848]   ||Sampling coordinates of site: ... do not lie within the PALM domain.  ||Check the coordinates in your virtual measurement input file, or extend the model domain. ||
+||[=#PA0849 PA0849]   ||fft_method = "fftw" is not available for loop_optimization = "vector"   ||Choose a different fft-method, e.g. the temperton-algorithm, or switch to scalar loop optimization. ||
 ||[=#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'.   ||
 ||[=#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' ||