PA0= PALM error messages = The following list displays the error messages reported by PALM. Each error message is identified by a unique message identifier which is composed of two letters and a four digit number. The second column contains the error message as reported in the job protocol (see here?). The third column explains the error and possible reasons in more detail, and also gives suggestions how to solve the problem.

PA****	Identifier for messages in the PALM standard code
UI****	Identifier for messages in ''user_'' routines
NC****	Identifier for messages from the netCDF library

To be continued.

Message identifier	Error message	Explanation
PA0001	manual restart settings requires file activation string "restart"	Values for parameters dt_restart or/and restart_time have been given in the &runtime_parameters-NAMELIST. This also requires to give the file activation string "restart" with palmbuild-option -a, because otherwise the restart files wouldn't be generated at the end of the PALM run. Repeat the run with -a ".... restart" or remove parameters dt_restart or/and restart_time from your NAMELIST-file.
PA0002	illegal coupling mode: ...	This message is related to the atmosphere-ocean coupling or pure vertical nesting implemented in PALM. Internally, the variable coupling_mode defines the coupling setup used for the current respective model run. It may have one of the values "atmosphere_to_ocean" (atmospheric part of a coupled run), "ocean_to_atmosphere" (ocean part of a coupled run), "precursor_atmos" (a precursor atmosphere run), "precursor_ocean" (a precursor ocean run), "vnested_crse", (the coarse simulation of a vertical nesting run) "vnested_fine" (the fine simulation of a vertical nesting run) or "uncoupled" (atmosphere or ocean run without any intended coupling). This error message means that the initialization of the coupling did fail because coupling_mode has a value different from the ones mentioned before. Possible reasons might be trying a coupling between two atmosphere runs (or two ocean runs), or problems with the palmrun script.
PA0003	dt_coupling is not set but required for coupling mode "..."	This error appears if the temporal interval for the data exchange dt_coupling is not explicitly set in case of runs with coupled models (e.g. atmosphere - ocean).
PA0004	coupling mode "...": dt_coupling = ... is not equal to dt_coupling_remote = ...	For coupled runs the temporal interval for the data exchange dt_coupling must be explicitly set and must have the same value in both models (dt_coupling has to be set in PARIN and PARIN_O). See also coupled runs.
PA0005	coupling mode "...": dt_coupling <= 0.0 is not allowed and is reset to MAX(dt_max(A,O)) = ...	This error occurs if an invalid value for dt_coupling is used in the parameter file. dt_coupling must be > 0.0 and equal in both models (dt_coupling has to be set in PARIN and PARIN_O). The letter A in the error message on the left refers to Atmosphere and the letter O to ocean. See also coupled runs.
PA0006	coupling mode "...": restart_time = ... is not equal to restart_time_remote = ...	restart_time has not been set properly (equal) in the atmosphere and ocean parameter file. See also coupled runs.
PA0007	coupling mode "...": dt_restart = ... is not equal to dt_restart_remote = ...	dt_restart has not been set properly (equal) in the atmosphere and ocean parameter file. See also coupled runs.
PA0008	coupling mode "...": time_to_be_simulated_from_reference_point = ... is not equal to time_to_be_simulated_from_reference_point_remote = ...	The simulated time from the reference point is stored internally in the variable time_to_be_simulated_from_reference_point. In coupled mode both times must be equal. This error might occur when precursor runs are used with different startup times and the coupling is initiated inappropiately. See coupled runs for a detailed description of the setup for precursor runs.
PA0009	dx in atmosphere is not larger or equal than dx in ocean	Coupled runs allow to use different grid resolutions in atmosphere and ocean. It is, however, not allowed to use a finer grid resolution in the atmosphere than in the ocean.
PA0010	Domain size in x-direction is not equal in ocean and atmosphere	Coupled runs are only possible, if the horizontal model domain size is equal in both, atmosphere and ocean. Check the settings for dx, dy, nx and ny to avoid this error.
PA0011	dy in atmosphere is not larger or equal than dy in ocean	Coupled runs allow to use different grid resolutions in atmosphere and ocean. It is, however, not allowed to use a finer grid resolution in the atmosphere than in the ocean.
PA0012	Domain size in y-direction is not equal in ocean and atmosphere	Coupled runs are only possible, if the horizontal model domain size is equal in both, atmosphere and ocean. Have a look at the settings for dx, dy, nx and ny to avoid this error.
PA0013	illegal value given for loop_optimization: "..."	See parameter loop_optimization for allowed values, and check your parameter file.
PA0014	a non-flat topography does not allow ...	There are several features which do not work together with a non-flat topography. See parameter topography for possible restrictions and appropriately modify your parameter file. For a complete list of not allowed parameter settings due to a non-flat topography see check_parameters.f90.
PA0015	Using synthetic turbulence generator requires initializing_actions = "set_constant_profiles" or "read_restart_data"	When switching on the synthetic turbulence generator by setting use_synthetic_turbulence_generator = .TRUE., PALM has to be initialized using either constant profiles (initializing_actions = "set_constant_profiles") or loading data from a previous run (initializing_actions = "read_restart_data"). Other initialization actions do not support the synthetic turbulence generator.
PA0016	unknown solver for perturbation pressure: psolver = "..."	See parameter psolver for allowed values, and correct your parameter file.
PA0017	output of more than 300 profiles requested	The total sum of output profiles given via parameters data_output_pr and data_output_pr_user is greater than 300. You may either reduce the number of output profiles, or ask the PALM group (via the trouble-ticket system) to extend the bounds of PALM internal arrays to allow for more than 300 profiles.
PA0018	illegal value for data_output_masks or data_output_masks_user: ...	Possible reasons are: (a) a typo in the parameter file related to masked data output, (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 here). For possible output quantities see data_output_masks.
PA0019	unknown surface type: surface_type = "..."	See parameter surface_type for allowed values, and appropriately correct your parameter file.
PA0020	unknown multigrid cycle: cycle_mg = "..."	See parameter cycle_mg for allowed values, and appropriately correct your parameter file.
PA0021	unknown fft-algorithm: fft_method = "..."	See parameter fft_method for allowed values, and appropriately correct your parameter file.
PA0022	unknown advection scheme: momentum_advec = "..."	See parameter momentum_advec for allowed values, and appropriately correct your parameter file.
PA0023	momentum_advec or scalar_advec = "..." is not allowed with timestep_scheme = "..."	The 5th order advection scheme is conditional unstable in conjunction with euler or runge-kutta-2 integration. Instead, use timestep_scheme = runge-kutta-3.
PA0024	unknown advection scheme: scalar_advec = "..."	See parameter scalar_advec for allowed values, and appropriately correct your parameter file.
PA0025	use_upstream_for_tke is set to .TRUE. because use_sgs_for_particles = .TRUE. and scalar_advec /= 'ws-scheme'	This is just a warning telling you that the simple upstream discretization is used for the advection term of the TKE equation instead of the one that you have set with parameter scalar_advec. This is required in case of using SGS velocity components for particle transport, because non-diffusiv advection schemes may cause large artificial vertical gradients near the surface, which create numerical instabilities in the particle transport. You can avoid output of this warning by explicitly setting parameter use_upstream_for_tke in the parameter file (initialization_parameters-NAMELIST).
PA0026	advection_scheme scalar_advec = "bc-scheme" not implemented for loop_optimization = "cache"	For the Bott-Chlond scheme loop_optimization = "vector" must to be set.
PA0027	unknown timestep scheme: timestep_scheme = "..."	See parameter timestep_scheme for allowed values, and appropriately correct your parameter file.
PA0028	negative weighting factor	A negative weighting factor might occur if the timestep is too long. Try to adjust dt.
PA0029	momentum advection scheme "..." does not work with timestep_scheme "..."	For timestep_scheme = 'runge-kutta-3' only momentum_advec = 'ws-scheme' or 'pw-scheme' gives a numerically stable solution.
PA0030	initializing_actions = "..." unkown or not allowed	See parameter initializing_actions for allowed values in initial runs (of a job chain). For a restart run, please set initializing_actions = 'read_restart_data' .
PA0031	initializing_actions = "set_constant_profiles" and "set_1d-model_profiles" are not allowed simultaneously	Set either initializing_actions = 'set_constant_profiles' in your parameter file, if the 3d-model shall be initialized with constant profiles, or set initializing_actions = 'set_1d-model_profiles' if the 3d-model shall be initialized with profiles of the (stationary) solution of the 1d-model.
PA0032	initializing_actions = "set_constant_profiles" and "by_user" are not allowed simultaneously	Set either initializing_actions = 'set_constant_profiles' in your parameter file, if the 3d-model shall be initialized with constant profiles, or set initializing_actions = 'by_user' , if the 3d-model shall be initialized with profiles to be provided by the user in routine user_init_3d_model of the user-interface.
PA0033	initializing_actions = "by_user" and "set_1d-model_profiles" are not allowed simultaneously	Set either initializing_actions = 'by_user' in your parameter file, if the 3d-model shall be initialized with profiles to be provided by the user in routine user_init_3d_model of the user-interface, or set initializing_actions = 'set_1d-model_profiles' , if the 3d-model shall be initialized with profiles of the (stationary) solution of the 1d-model.
PA0034	bulk_cloud_model = .T. is not allowed with humidity = .F.	It is necessary to turn on humidity for the use of cloud physics.
PA0035	Using synthetic turbulence generator requires bc_lr = "dirichlet/radiation"	The synthetic turbulence generator requires a non-cyclic boundary condition along x direction with an inflow at the left domain boundary.
PA0036	humidity = .TRUE. and sloping_surface = .TRUE. are not allowed simultaneously	If alpha_surface is set to a non-zero value in order to use an inclined surface, the parameter sloping_surface is internally set .TRUE.. I.e., in the case of alpha_surface /= 0.0 the simultaneous use of humidity = .TRUE. is not allowed.
PA0037	Using synthetic turbulence generator requires bc_ns = "cyclic"	The synthetic turbulence generator only supports non-cyclic boundary conditions at the left/right boundary. In north/south direction, cyclic boundary conditions must be set.
PA0038	turbulent_outflow = .T. requires bc_lr = "dirichlet/radiation"	When using the turbulent outflow method, non-cyclic boundary condition along the x direction must be used. See also turbulent_outflow.
PA0039	Using synthetic turbulence generator in combination with turbulent_inflow = .T. is not allowed	A turbulent inflow can only be generated by either the synthetic turbulence generator or the turbulence recycling method. Using both at the same time is impossible.
PA0040	LWC is not conserved during collision! LWC after condensation: ... LWC after collision: ...	LWC means liquid water content. This should not happen. Please write a ​ticket.
PA0041	plant_canopy = .TRUE. requires a non-zero drag coefficient, given value is canopy_drag_coeff = 0.0	When simulating a plant canopy, a non-zero canopy_drag_coeff must be set in the parameter file under NAMELIST &plant_canopy_parameters. The canopy model in PALM adds an additional sink/source terms to the momentum equations, the prognostic equation for temperature, and the subgrid scale turbulent kinetic energy equation. In case of humidity = .TRUE. or passive_scalar = .TRUE., an additional source/sink term is added to the prognostic equation of the respective scalar. If canopy_drag_coeff = 0.0, the additional terms equal zero and there would be no effect on the flow.
PA0042	use_top_fluxes must be .TRUE. in ocean mode	In ocean mode, fluxes at the water surface must be prescribed as driving boundary conditions. In atmosphere-ocean coupled runs, these fluxes are provided by the atmosphere run.
PA0043	ABS( alpha_surface = ... ) must be< 90.0	Upright surfaces are not allowed in case of sloping surfaces.
PA0044	dt = ... <= 0.0	The parameter dt (time step for the 3d-model) must not be set to a value <= 0.0.
PA0045	cfl_factor = ... out of range 0.0 < cfl_factor <= 1.0 is required	The Courant-Friedrichs-Levy factor used in the timestep condition must be within the given limits. See also cfl_factor .
PA0046	baroclinity (ug) not allowed simultaneously with galilei transformation	The Galilei coordinate transformation (see galilei_transformation) is not allowed under baroclinic conditions (where the geostrophic wind varies with height). Modify either ug_surface or galilei_transformation, or set use_ug_for_galilei_tr = .FALSE. appropriately in the parameter file.
PA0047	baroclinity (vg) not allowed simultaneously with galilei transformation	The Galilei coordinate transformation (see galilei_transformation) is not allowed under baroclinic conditions (where the geostrophic wind varies with height). Modify either vg_surface, or galilei_transformation appropriately, or set use_ug_for_galilei_tr = .FALSE. in the parameter file.
PA0048	variable translation speed used for Galilei-transformation, which may cause instabilities in stably stratified regions	You have set both galilei_transformation = .TRUE. and use_ug_for_galilei_tr = .FALSE., which means that the translation velocity to be used in the Galilei transformation will be newly calculated after every timestep. From past experiences, this may cause numerical flow instabilities within stably stratified, non-turbulent regions.
PA0049	unknown boundary condition: bc_lr = "..."	See parameter bc_lr for allowed values, and appropriately correct your parameter file.
PA0050	unknown boundary condition: bc_ns = "..."	See parameter bs_ns for allowed values, and appropriately correct your parameter file.
PA0051	non-cyclic lateral boundaries do not allow psolver = "..."	Using non-cyclic lateral boundary conditions requires the multigrid method for solving the Poisson equation for the perturbation pressure. You can choose this method by setting the parameter psolver = 'multigrid' or 'multigrid_noopt' .
PA0052	non-cyclic lateral boundaries do not allow momentum_advec = "..."	Using non-cyclic lateral boundary conditions requires to use either the Wicker-Skamarock or the Piacsek-Williams advection scheme for momentum. You can choose one of these methods by setting the parameter momentum_advec.
PA0053	non-cyclic lateral boundaries do not allow scalar_advec = "..."	Using non-cyclic lateral boundary conditions requires to use either the Wicker-Skamarock or Piacsek-Williams advection scheme for scalar quantities. You can choose one of these methods by setting the parameter scalar_advec.
PA0054	non-cyclic lateral boundaries do not allow galilei_transformation = .T.	The Galilei coordinate transformation can only be used with cyclic horizontal boundary conditions. Either use bc_lr = bc_ns = 'cyclic' , or set galilei_transformation = .FALSE. in the parameter file.
PA0055	turbulent_inflow = .T. requires initializing_actions = 'cyclic_fill' or initializing_actions = 'read_restart_data'	Using a turbulent inflow requires that the 3d arrays have to be initialized by cyclically repeated data from a prerun or by restart data. Set parameter initializing_actions appropriately and follow the instructions at turbulent inflow.
PA0056	illegal value for reference_state: "..."	See parameter reference_state for allowed values, and appropriately correct your parameter file.
PA0057	boundary condition bc_e_b changed to "..."	You have set both bc_e_b = (u*)**+neumann, and constant_flux_layer = .FALSE., which is in conflict, since this type of boundary condition requires a constant flux layer. bc_e_b has been set to 'neumann' instead.
PA0058	unknown boundary condition: bc_e_b = "..."	See parameter bc_e_b for allowed values, and appropriately correct your parameter file.
PA0059	unknown boundary condition: bc_p_b = "..."	See parameter bc_p_b for allowed values, and appropriately correct your parameter file.
PA0060	Output at every timestep is wanted ("dt_..." = 0.0). The output interval is set to the fixed timestep dt = "..."s.	Occurs only when netcdf_data_format > 4 and dt /= -1 as an informative message. When using parallel NetCDF the output time interval must be >0. Using dt_do = 0.0 (output at every time step) is equal to setting the output interval to dt.
PA0061	unknown boundary condition: bc_p_t = "..."	See parameter bc_p_t for allowed values, and appropriately correct your parameter file.
PA0062	unknown boundary condition: bc_pt_b = "..."	See parameter bc_pt_b for allowed values, and appropriately correct your parameter file.
PA0063	unknown boundary condition: bc_pt_t = "..."	See parameter bc_pt_t for allowed values, and appropriately correct your parameter file.
PA0064	both, top_momentumflux_u AND top_momentumflux_v must be set	If you want to give a momentum flux as top boundary condition, you have to give both components top_momentumflux_u and top_momentumflux_v at the same time.
PA0065	boundary_condition: bc_pt_b = "..." is not allowed with constant_heatflux = .TRUE.	You have tried to set both, a Dirichlet surface boundary condition for temperature (with bc_pt_b = 'dirichlet' ), and a surface sensible heatflux (with surface_heatflux /= 0.0). Please decide, if you like to give either the surface temperature or the surface heatflux as boundary condition, and omit one of the two parameters in the parameter file.
PA0066	constant_heatflux = .TRUE. is not allowed with pt_surface_initial_change (/=0) = ...	If you give the sensible heatflux as surface boundary condition (using parameter surface_heatflux), you must not specify anything about the surface temperature at the same time (e.g. with parameter pt_surface_initial_change).
PA0067	boundary_condition: bc_pt_t = "..." is not allowed with constant_top_heatflux = .TRUE.	You have tried to set both, a Dirichlet boundary condition for temperature at the top (with bc_pt_t = 'dirichlet' ), and a sensible heatflux at the top (with top_heatflux /= 0.0). Please decide, if you like to give either the temperature or the heatflux as boundary condition at the top, and omit one of the two parameters in the parameter file.
PA0068	unknown boundary condition: bc_sa_t = "..."	See parameter bc_sa_t for allowed values, and appropriately correct your parameter file.
PA0069	boundary condition: bc_sa_t = "..." requires to set top_salinityflux	You have chosen a Neumann boundary condition for salinity at the top (by setting bc_sa_t = 'neumann' ), but you did not provide a salinity flux at the top. Please provide parameter top_salinityflux in the parameter file.
PA0070	boundary condition: bc_sa_t = "..." is not allowed with top_salinityflux /= 0.0'	You have tried to set both, a Dirichlet boundary condition for salinity at the top (with bc_sa_t = 'dirichlet' ), and a salinity flux at the top (with top_salinityflux /= 0.0). Please decide, if you like to give either the salinity or the salinity flux as top boundary condition, and omit one of the two parameters in the parameter file.
PA0071	unknown boundary condition: bc_..._b ="..."	See the respective parameter description in the documentation, and appropriately correct your parameter file.
PA0072	unknown boundary condition: bc_..._t ="..."	See the respective parameter description in the documentation, and appropriately correct your parameter file.
PA0073	boundary condition: bc_..._b = "..." is not allowed with prescribed surface flux	You have tried to set both, a Dirichlet surface boundary condition for humidity / passive scalar (with bc_q_b / bc_s_b = 'dirichlet' ), and a surface latent heatflux / scalar flux (with surface_waterflux / surface_scalarflux /= 0.0). Please decide, if you like to give either the surface humidity / scalar or the surface latent heatflux / scalar flux as boundary condition, and omit one of the two parameters in the parameter file.
PA0074	a prescribed surface flux is not allowed with ..._surface_initial_change (/=0) = ...	If you give the latent heatflux / scalar flux as surface boundary condition (using parameter surface_waterflux / surface_scalarflux), you must not specify anything about the surface humidity / scalar at the same time (e.g. with parameter q_surface_initial_change / s_surface_initial_change).
PA0075	boundary condition: bc_uv_b = "..." is not allowed with constant_flux_layer = .TRUE.	You have tried to set both, a Neumann surface boundary condition for horizontal velocity (with bc_uv_b = 'neumann' ), and a constant flux layer between the surface and the first vertical grid point (with constant_flux_layer = .TRUE.), which are contradicting conditions. Either set constant_flux_layer = .FALSE. or bc_uv_b = 'dirichlet' in the parameter file.
PA0076	unknown boundary condition: bc_uv_b = "..."	See parameter bc_uv_b for allowed values, and appropriately correct your parameter file.
PA0077	unknown boundary condition: bc_uv_t = "..."	See parameter bc_uv_t for allowed values, and appropriately correct your parameter file.
PA0078	rayleigh_damping_factor = ... out of range [0.0,1.0]	Adjust the value of rayleigh_damping_factor in your parameter file to the allowed range.
PA0079	rayleigh_damping_height = ... out of range [0.0, ...]	Adjust the value of rayleigh_damping_height in your parameter file to the allowed range. This error may appear if you have reduced the domain height in your current run (e.g. by reducing the number of vertical grid points) without adjusting the height at which Rayleigh damping shall start.
PA0080	preprocessor switch for fftw is missing	You have set 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 (i.e. call palmbuild.
PA0081	"..." = 0.0 while using a variable timestep and parallel netCDF4 is not allowed.	When using parallel NetCDF output (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 dt.
PA0082	number of statistic_regions = ... is not allowed	Adjust parameter statistic_regions in your parameter file to a value >= 0.
PA0083	normalizing_region = ... must be >= 0 and <= ... (value of statistic_regions)	The region number given by normalizing_region must be within the range [0, statistic_regions ]. Adjust normalizing_region appropriately in your parameter file.
PA0084	urban surface model requires ...	When using the USM it is required to use a constant_flux_layer and the radiation model.
PA0085	averaging_interval = ... must be <= dt_data_output_av = ...	The averaging_interval for averaged output data must be smaller or equal to the output interval given by dt_data_output or dt_data_output_av. Adjust settings of these variables appropriately in the parameter file.
PA0086	averaging_interval_pr = ... must be <= dt_dopr = ...	The averaging_interval_pr for profile output data must be smaller or equal to the output interval given by dt_dopr. Adjust settings of these variables appropriately in the parameter file.
PA0087	averaging_interval_sp = ... must be <= dt_dosp = ...	The averaging_interval_sp for spectra output data must be smaller or equal to the output interval given by dt_dosp. Adjust settings of these variables appropriately in the parameter file.
PA0088	dt_averaging_input = ... must be <= averaging_interval = ...	The sampling interval (set by dt_averaging_input) for averaging data must be less or equal to the averaging interval (set by averaging_interval). Adjust settings of these variables appropriately in the parameter file.
PA0089	dt_averaging_input_pr = ... must be <= averaging_interval_pr = ...	The sampling interval (set by dt_averaging_input_pr) for averaging profile data must be less or equal to the averaging interval (set by averaging_interval_pr). Adjust settings of these variables appropriately in the parameter file.
PA0090	precipitation_amount_interval = ... must not be larger than dt_do2d_xy = ...	Choose a value for precipitation_amount_interval smaller than or equal to dt_do2d_xy. Adjust the settings of precipitation_amount_interval appropriately in the parameter file.
PA0091	wrong component of Stokes force: ...	Only the two Cartesian components 2 and 3 are allowed for the Stokes force in ocean mode.
PA0092	data_output_pr = ... is not implemented for humidity = .FALSE.	The listed entries in the parameter file under data_output_pr are only available for humidity= .T.. There could also be a typo in data_output_pr (an output variable was used that does not exist in PALM).
PA0093	data_output_pr = ... is not implemented for passive_scalar = .FALSE.	The listed entries in the parameter file under data_output_pr are only available for passive_scalar= .T.. There could also be a typo in data_output_pr (an output variable was used that does not exist in PALM).
PA0094	data_output_pr = ... is not implemented for bulk_cloud_model = .FALSE.	The listed entries in the parameter file under data_output_pr are only available for bulk_cloud_model= .T.. There could also be a typo in data_output_pr (an output variable was used that does not exist in PALM).
PA0095	data_output_pr = ... is not implemented for bulk_cloud_model = .FALSE. and humidity = .FALSE.	The listed entries in the parameter file under data_output_pr are only available for bulk_cloud_model= .T. or bulk_cloud_model= .F. and humidity=.T.. There could also be a typo in data_output_pr (an output variable was used that does not exist in PALM).
PA0096	data_output_pr = ... is not implemented for bulk_cloud_model = .FALSE. and cloud_droplets = .FALSE.	The listed entries in the parameter file under data_output_pr are only available for cloud_droplets= .T. or bulk_cloud_model=.T.. There could also be a typo in data_output_pr (an output variable was used that does not exist in PALM).
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 here).
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).
PA0099	netCDF: netCDF4 parallel output requested but no cpp-directive __netcdf4_parallel given, switch back to netCDF4 non-parallel output	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 (%compiler_options) and load (%linker_options) options of the configuration file appropriately. Job will be continued with netcdf_data_format = netcdf_data_format - 2.
PA0100	momentum_advec of the restart run differs from momentum_advec of the initial run	The advection scheme for the momentum equations 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.
PA0101	scalar_advec of the restart run differs from scalar_advec of the initial run	The advection scheme for scalar quantities scalar_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.
PA0102	number of output quantities given by data_output and data_output_user exceeds the limit of 500	The total number of output quantities listed in data_output and data_output_user exceeds the maximum of 500. To increase this limit, the standard PALM code has to be modified. In case you have little experience with the PALM code use a trouble ticket for a query to increase the maximum output number.
PA0103	output of "e" requires constant_diffusion = .FALSE.	Output of the subgrid TKE e listed in the parameter file under data_output or data_output_masks is only available for constant diffusion= .F..
PA0104	output of "..." requires a "particles_par"-NAMELIST in the parameter file (PARIN)	Output of the particle concentration pc and/or particle radius pr listed in the parameter file under data_output or data_output_masks is only available in case the particle_parameters namelist is set in the parameter file
PA0105	output of "..." requires humidity = .TRUE.	Output of humidity (q and/or vpt) listed in the parameter file under data_output or data_output_masks is only available for humidity= .T..
PA0106	output of "ql" requires bulk_cloud_model = .TRUE. or cloud_droplets = .TRUE.	Output of liquid water content ql listed in the parameter file under data_output or data_output_masks is only available for bulk_cloud_model= .T. or cloud_droplets= .T..
PA0107	output of "..." requires cloud_droplets = .TRUE.	The quantities ql_c, ql_v, ql_vp are only calculated in case of cloud_droplets = .T..
PA0108	output of "..." requires bulk_cloud_model = .TRUE.	For the output of some quantities related to clouds and humidity bulk_cloud_model= .T. must be set. For example, the water vapor mixing ratio qv requires bulk_cloud_model= .T.. Also, humidity = .T. must be set. If you want to simulate the humidity without condensation/evaporation processes, use only humidity = .T. and choose output quantity q for output of the water vapor mixing ratio.
PA0109	output of "..." requires ocean mode	The quantities rho_ocean and sa are only calculated in case that ocean mode has been activated by giving the &ocean_parameters namelist.
PA0110	output of "s" requires passive_scalar = .TRUE.	The output of the passive scalar s is only available if the prognostic equation for a passive scalar is solved by setting passive_scalar = .T..
PA0111	illegal value for data_output: "..." only 2d-horizontal cross sections are allowed for this value	The listed quantities are pure two-dimensional xy-cross-sections. They are not available as 3d data or xz/yz cross-sections. Note that these quantities are always marked by an asterisk as last character. See also data_output.
PA0112	output of "..." requires cloud_scheme = kessler or seifert_beheng	The quantities pra* and prr* are only calculated if cloud_scheme = kessler or cloud_scheme = seifert_beheng.
PA0113	temporal averaging of precipitation amount "pra*" is not possible	The quantity precipitation_amount pra* listed in data_output contains already the summed precipitation of the last precipitation_amount_interval. Therefore, remove the substring _av of pra*.
PA0114	illegal value for data_output or data_output_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 here).
PA0115	illegal value for data_output = "..."	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). For possible output quantities see data_output.
PA0116	to_netcdf = .True. requires parallel NetCDF	surface output with NetCDF requires parallel NetCDF
PA0117	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).
PA0118	using the beta function for the construction of the leaf area density profile requires both alpha_lad and beta_lad to be /= 9999999.9	If the lad (leaf area density) profile of a vegetation canopy is to be constructed using a beta distribution, parameters alpha_lad, beta_lad must be set and lai_beta must be given a non-zero value.
PA0119	using the beta function for the construction of the leaf area density profile requires a non-zero lai_beta, but given value is lai_beta = 0.0	If the lad (leaf area density) profile of a vegetation canopy is to be constructed using a beta distribution, parameters alpha_lad, beta_lad must be set and lai_beta must be given a non-zero value.
PA0120	simultaneous setting of alpha_lad /= 9999999.9 combined with beta_lad /= 9999999.9 and lad_surface /= 0.0 is not possible, use either vertical gradients or the beta function for the construction of the leaf area density profile	The lad (leaf area density) profile of a vegetation canopy can be either constructed with a beta function by prescribing parameters alpha_lad, beta_lad and lai_beta; or from piecewise linear segments by prescribing lad_surface, lad_vertical_gradient and lad_vertical_gradient_level.
PA0121	km_constant = ... < 0.0	The eddy-diffusivity km has to be positive definite. Change the value of km_constant accordingly.
PA0122	prandtl_number = ... < 0.0	The Prandtl number Pr has to be positive definite. Change the value of prandtl_number accordingly.
PA0123	constant_flux_layer is not allowed with fixed value of km	For laminar flows with a constant eddy diffusivity km_constant= ..., the constant flux layer has to be switched off via constant_flux_layer=.F..
PA0124	pt_damping_width out of range	In case of non-cyclic lateral boundary conditions, the parameter pt_damping_width should not be lesser than zero or greater than the model domain length in the respective direction. In case of bc_lr /= 'cyclic', pt_damping_width must satisfy: and in case of bc_ns /= 'cyclic': (nx+1), (ny+1) are the total number of grid points and dx, dy the grid lengths in the x-, y-direction, respectively.
PA0125	zeta_min = ... must be less than zeta_max = ...	The stability parameter zeta=z_mo/L (z_mo: height of the constant flux layer, L: Obukhov length) that is calculated interactively in PALM can be limited to prevent reaching unrealistic values under certain circumstances. Make sure that zeta_min is smaller than zeta_max.
PA0126	disturbance_level_b = ... must be >= ... (zu(3))	Due to technical reasons the lower disturbance level given by disturbance_level_b has to be larger than or equal zu(3).
PA0127	disturbance_level_b = ... must be <= ... (zu(nzt-2))	Due to technical reasons the lower disturbance level given by disturbance_level_b has to be smaller than or equal zu(nzt-2).
PA0128	disturbance_level_t = ... must be <= ... (zu(nzt-2))	Due to technical reasons the upper disturbance level given by disturbance_level_t has to be smaller than or equal zu(nzt-2).
PA0129	disturbance_level_t = ... must be >= disturbance_level_b = ...	Ensure that disturbance_level_t is larger than or equal disturbance_level_b to obtain at least one layer where disturbances are added.
PA0130	disturbance_level_ind_t =... must be >= disturbance_level_ind_b = ...	This error may occur when the lower and upper disturbance levels disturbance_level_b and disturbance_level_t are calculated automatically and there are two few grid points in the vertical direction. There have to be at least seven vertical levels.
PA0131	inflow_disturbance_begin out of range	The parameter inflow_disturbance_begin gives the number of grid points (counted horizontally from the inflow) from which on perturbations are imposed on the horizontal velocity field. This value must not be smaller than zero or larger than nx (in case of non-cyclic lateral boundary conditions along the x-direction) or ny (in case of non-cyclic lateral boundary conditions along the y-direction).
PA0132	inflow_disturbance_end out of range	The parameter inflow_disturbance_end gives the number of grid points (counted horizontally from the inflow) up to which perturbations are imposed on the horizontal velocity field. This value must not be smaller than zero or larger than nx (in case of non-cyclic lateral boundary conditions along the x-direction) or ny (in case of non-cyclic lateral boundary conditions along the y-direction).
PA0133	turbulent_inflow = .T. requires a Dirichlet condition at the inflow boundary	In case of turbulent inflow the turbulence signal is added to a time-constant horizontal mean wind profile at the left inflow boundary at each timestep. The use of a time-constant mean wind profile requires a Dirichlet boundary condition at the left inflow boundary. For further information please see: nonclyclic boundary conditions as well as turbulent inflow.
PA0134	illegal value for recycling_width: ...	See parameter recycling_width for allowed values, and appropriately correct your parameter file.
PA0135	unknown random generator: random_generator = "..."	See parameter random_generator for allowed values, and appropriately correct your parameter file.
PA0136	damp_level_1d = ... must be >= 0.0 and <= ... (zu(nzt+1))	The value of damp_level_1d must be within the range [0, zu(nzt+1)]
PA0137	mixing_length_1d = "..." is unknown	See parameter mixing_length_1d for allowed values, and appropriately correct your parameter file.
PA0138	dissipation_1d = "..." is unknown	See parameter dissipation_1d for allowed values, and appropriately correct your parameter file.
PA0139	'pavement_type = 0 (user_defined) requires setting of pavement_heat_conduct /= 9999999.9	In case of a user-defined pavement type, the heat conductivity of the pavement must be given
PA0140	invalid soil layer configuration found (dz_soil_center(k) <= 0.0)	By setting zs (the center of the soil layers), the depths of the individual layers is calculated by PALM itself. This errors points towards a misconfiguration because a soil level is set within an already established soil layer. Check dz_soil.
PA0141	coupling requires PALM to be compiled with cpp-option "-D_parallel"	Coupling is only allowed in parallel and not in serial mode. You have to compile PALM with the preprocessor option "-D_parallel". Add this option to the %cpp_options line in your configuration file .palm.config....
PA0142	absolute temperature < 0.0 at zu(...) = ...	Within the PALM code (in bcm_init), the hydrostatic pressure profile is calculated for a neutrally stratified temperature profile t(z) = t_surface-g/c_p*z(k). If the height of the model domain is too large, the absolute temperature will become negative, which is not allowed. This error usually appears when both grid stretching is switched on and too many grid points along z are used. Try to reduce the number of grid points (nz), switch on the grid stretching at larger heights (see dz_stretch_level) or reduce the grid stretching factor (dz_stretch_factor).
PA0143	k=... j=... i=... ql_c=... part(...)%wf=... delta_r=...	This error occurs due to a spurious interaction of the production and depletion of supersaturations if the applied time step is too large. Please re-run the simulation with a shorter time step.
PA0144	#1 k=... j=... i=... e_s=... e_a=... t_int=... delta_r=... particle_radius=...	This error occurs if the droplet radius becomes negative. This might be related to a too long time step or an (artificial?) accumulation of super-droplets in one grid cell.
PA0145	illegal value for outflow_source_plane:...	The position of the source plane for the turbulent outflow method is not given or outside the model domain. Assign a value inside the model domain: dx <= outflow_source_plane <= nx*dx
PA0146	unknown splitting mode = "..."	See parameter splitting_mode for allowed values, and appropriately correct your parameter file.
PA0147	unknown splitting function = "..."	See parameter splitting_function for allowed values, and appropriately correct your parameter file.
PA0148	particle too fast. n = ...	Particle has moved further than the length of one PE subdomain within on timestep. This is not allowed, since particles can only be transferred from one subdomain to the neighboring subdomain. Please check if subdomains are too small or velocities are unrealistically high.
PA0149	no value specified for initializing_actions	You must specify a value for initializing_actions.
PA0150	Both dp_external and conserve_volume_flow are .TRUE., but one of them must be .FALSE.	Simultaneous use of an external pressure gradient forcing (dp_external = .TRUE.) and conserve_volume_flow is not allowed. Please correct your parameter file appropriately.
PA0151	dp_level_b = ... is out of range [zu(nzb), zu(nzt)]	dp_level_b is outside of the vertical bounds of the model domain. Please check the prescribed value for dp_level_b in your parameter file.
PA0152	dp_external is .TRUE. but dpdxy is zero, i.e. the external pressure gradient will not be applied	If the flow forcing shall be accomplished by an external pressure gradient, i.e. dp_external is .TRUE., dpdxy must be set to a non-zero value in your parameter file.
PA0153	dpdxy is nonzero but dp_external is .FALSE., i.e. the external pressure gradient will not be applied	If the flow forcing shall be accomplished by an external pressure gradient, i.e. dpdxy is set to a non-zero value, dp_external = .TRUE. must be set in your parameter file.
PA0154	unknown conserve_volume_flow_mode: ...	See parameter conserve_volume_flow_mode for allowed values, and appropriately correct your parameter file.
PA0155	noncyclic boundary conditions require conserve_volume_flow_mode = "initial_profiles"	See parameter conserve_volume_flow_mode for allowed values. conserve_volume_flow_mode = 'bulk_velocity' is not allowed when you are using non-cyclic boundary conditions.
PA0156	The number of values for dz = ... has to be the same than the number of values for dz_stretch_level_end + 1 = ...	Self-explanatory. Please add/remove values for dz or for dz_stretch_level_end appropriately.
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 conserve_volume_flow = .T. and conserve_volume_flow_mode = "bulk_velocity".
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 trouble ticket.
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 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 trouble ticket.
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 data_output_sp.
PA0161	sorry, calculation of spectra in non parallel mode is still not realized	Calculation of spectra in non-parallel mode is not implemented.
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 data_output_sp.
PA0163	run will be terminated because it is running out of job cpu limit remaining time: ... s termination time needed: ... s	In case that 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 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 Initialization and restart runs for further information.
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 restart_time and/or dt_restart and the new restart time is calculated. Have a look at Initialization and restart runs for further information.
PA0165	re-open of unit 14 is not verified. Please check results!	The file with unit number 14 contains the binaries BINOUT. It was opened at least a second time by user specific settings. This is not verified, so check the results carefully.
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 I/O-files.
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	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 I/O-files and choose an unused file-id.
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 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	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	netCDF: netCDF4 format requested but no cpp-directive __netcdf4 given switch back to 64-bit offset 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 (%compiler_options) and load (%linker_options) options of the configuration file appropriately.
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	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	wrong argument expected: ... given:	Internal code error in routine cpu_log which can measure the CPU-time of a specific code segment. This error occurs when cpu_log is used again with the same id for a specific code segment (first input parameter) but with a different name describing this segment (second input parameter). When you did not change the source code by yourself please inform the PALM developers.
PA0175	Tunnel width too small	tunnel_width_x - 2.0*tunnel_wall_depth must be > 2*dx
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	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	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".
PA0179	unknown modus of time measurement: ...	Possible options for cpu_log are "start", "pause", "continue" and "stop". Please refer to the description in the header of cpulog_mod.f90.
PA0180	unknown cross-section: ...	Cross sections are only possible for xy-, xz- or yz-sections. Please check your variable list in your data_output and data_output_user parameter for correct spelling.
PA0181	no output provided for: ...	There is no 2D data output available for the selected variable. Please check your variable list in your data_output and data_output_user parameter for correct spelling.
PA0182	no output provided for: ...	There is no 3D data output available for the selected variable. Please check your variable list in your data_output and data_output_user parameter for correct spelling.
PA0183	end_time of the simulation exceeds the time dimension in the dynamic input file	time dimension in dynamic input file must cover the entire simulation time.
PA0184	unknown recycling method for thermodynamic quantities	Allowed input for recycling_method_for_thermodynamic_quantities is 'turbulent_fluctuation' or 'absolute_value'.
PA0185	data_output_pr = s*2 is not implemented for passive_scalar = .FALSE.	The listed entry s*2 in the parameter file under data_output_pr is only available for passive_scalar= .T..
PA0186	no spectra data available	This message occurs if the data_output_spectra routine is called but no spectra data was calculated through the routine calc_spectra. Check your spectra settings in the parameter file.
PA0187	fft method "system-specific" currently does not work on NEC	Usage of system-specific fft has been switched on with parameter fft_method, but the relevant part of the PALM code where the NEC-fft-library calls (e.g. DZFFT or DZFFTM) are used contains bugs which still require to be solved. You may submit a trouble ticket and ask for help.
PA0188	no system-specific fft-call available	You have set fft_method = system-specific. In this case you additionally have to set the cpp-preprocessor switches -D__ibm or -D__nec to specify the fft-library that you like to use. Calls to IBM/NEC-libraries are the only one implemented so far in the PALM code. Probably you forgot to set such a switch. Set the switch and do not forget to recompile the code.
PA0189	fft method "..." not available	See fft_method for the availabe methods that are implemented in PALM and modify the initialization-parameter fft_method in your NAMELIST file appropriately.
PA0190	flow_statistics is called two times within one timestep	Routine flow_statistics computes average profiles and further average flow quantities. It is only allowed to call this routine once during a time step (one timestep consists of several intermediate steps due to the selected time integration scheme). Please submit a trouble ticket if you have run into this error.
PA0191	unknown action(s): ...	The initializing action given by initializing_actions in your parameter file is unknown. Please check for correct spelling.
PA0192	timestep has exceeded the lower limit dt_1d = ... s simulation stopped!	The time step of the 1D model is determined according to the diffusion criterion to assure a stable numerical solution. This error message means that the required minimum time step is several orders of magnitude smaller than dt_max_1d. The error message may indicate for unrealistic settings of e.g. boundary conditions or other NAMELIST parameters. Please also check if this error appears if you run without USERCODE. To compile and run the PALM and USERCODE with DEBUG-options might also give sometimes valuable hints.
PA0193	unknown initializing problem	This should not happen during the initialization of the model variables in the routine init_3d_model. Please submit a trouble ticket if you have run into this error.
PA0194	number of time series quantities exceeds its maximum of dots_max = ... Please increase dots_max in modules.f90.	In case that the output of user defined timeseries is done and the number of the user defined timeseries exceeds the maximum number, the maximum number dots_max, which is currently set to 100, has to be increased. Please increase dots_max in modules.f90​ according to your needs.
PA0195	In case of external radiation forcing both, rad_sw_in and rad_lw_in are required.
PA0196	In case of external radiation forcing dimension time_rad is required.
PA0197	External radiation forcing: rad_sw_in must not contain any fill values.
PA0198	External radiation forcing: rad_lw_in must not contain any fill values.
PA0199	External radiation forcing: rad_sw_in_dif must not contain any fill values.
PA0200	missing dz	No value for dz was given in the parameter file.
PA0201	dz=... <= 0.0	The value given for dz must be greater than 0.0.
PA0202	grid anisotropy exceeds threshold given by only local horizontal reduction of near_wall mixing length l_wall starting from height level k = ... .	The grid-dependent mixing length l_grid ( = Δ = (Δx Δy Δz)1/3 ) becomes larger than 2.7 * dx or 2.7 * dy starting from the reported height level k. Although PALM will not abort due to this warning, the chosen grid setup might lead to untrustworthy results. The reason for this is an unfavourable choise of grid anisotropy. To avoid this, make sure that the values of dx, dy, and dz do not differ too much from each other. In case of grid stretching, the settings of dz_stretch_level and/or dz_stretch_factor should be changed to ensure a smaller difference between dz(k) and dx and dy at the reported height level.
PA0203	inconsistent building parameters: index_left_bwall=... index_right_bwall=... index_south_bwall=... index_north_bwall=... nx=... ny=...	The setup of the single building (topography = 'single_building' ) yields a too narrow building or the building walls are positioned outside of the model domain. Please check the building parameters in your parameter file.
PA0204	no street canyon width given	If topography = 'single_street_canyon' is given, also a canyon width must be given by either specifying canyon_width_x or canyon_width_y in the parameter file.
PA0205	inconsistent canyon parameters: index_left_cwall=... index_right_cwall=... ngp_cx=... ch=... nx=... ny=...	Due to canyon_width_x the setup of the single street canyon (topography = 'single_street_canyon' ) yields a too narrow canyon or the canyon walls are outside of the model domain. Please check the canyon parameters in your parameter file.
PA0206	inconsistent canyon parameters:... cys=... cyn=... cwy=... ch=... nx=... ny=...	Due to canyon_width_y the setup of the single street canyon (topography = 'single_street_canyon' ) yields a too narrow canyon or the canyon walls are outside of the model domain. Please check the canyon parameters in your parameter file.
PA0207	inconsistent canyon parameters: street canyon can only be oriented either in x- or in y-direction	Please do not specify canyon_width_x and canyon_width_y in the parameter file at the same time.
PA0208	file TOPOGRAPHY_DATA does not exist	Make sure that the topography data is available in the job directory (JOBS/<job-name>/INPUT/) and named correctly (<job-name>_topo). For remote jobs it might be possible that the automatic transfer of the topography file to the host computer did not work. In this case the topography file must be transfered manually to the host. Carefully check the messages in the terminal output / job protocol file that follows line *** providing INPUT-files:, If there is no line like >>> INPUT: /... to TOPOGRAPHY_DATA, the topography file hasn't been provided.
PA0209	error reading line ... of file TOPOGRAPHY_DATA	File contains illegal characters. Check the respective line given by the error message.
PA0210	nzb_local values are outside the model domain MINVAL( nzb_local ) = ... MAXVAL( nzb_local ) = ...	This error occurs during grid consistency checks of the index arrays when using non-flat topography with regard to the vertical dimension. Please submit a trouble ticket if you have run into this error because this should not happen.
PA0211	The number of values for dz = ... has to be the same as or one more than the number of values for dz_stretch_level_start = ...	Self-explanatory. Please add/remove values for dz or for dz_stretch_level_start appropriately.
PA0212	Overhanging topography do not work with particles	When you have defined an overhanging structure in your topography data the simultaneous use of the Lagrangian particle model could be dangerous because reflection boundary conditions (as well as subgrid-scale velocities) are not realized for downward-facing walls so far.
PA0213	max_number_of_particle_groups = ... number_of_particle_groups reset to reset to ...	If the number_of_particle_groups > 10 then is reset to the maximum number of particle groups (at maximum 10 are allowed)
PA0214	version mismatch concerning data from prior run version on file = ... version in program = ...	This error occurs when particle data from the restart file is read and the precursor run was carried out with a different particle binary version than the main run. Repeat the precurser with the current version or carry out the main run with the same version as the precursor. You can check the particle binary version number which is required for the main run in lpm_read_restart_file.f90.
PA0215	particle group # ... has a density ratio /= 0 but radius = 0	Particles with mass but without radius are not allowed. Please appropriately correct radius or density_ratio
PA0216	The number of values for dz_stretch_level_start = ... has to be the same or one more than the number of values for dz_stretch_level_end = ...	Self-explanatory. Please add/remove values for dz_stretch_level_start or for dz_stretch_level_end appropriately.
PA0217	unknown boundary condition bc_par_b = "..."	See parameter bc_par_b for allowed values, and appropriately correct your parameter file.
PA0218	unknown boundary condition bc_par_t = "..."	See parameter bc_par_t for allowed values, and appropriately correct your parameter file.
PA0219	unknown boundary condition bc_par_lr = "..."	See parameter bc_par_lr for allowed values, and appropriately correct your parameter file.
PA0220	unknown boundary condition bc_par_ns = "..."	See parameter bc_par_ns for allowed values, and appropriately correct your parameter file.
PA0221	number of PEs of the prescribed topology (...) does not match the number of PEs available to the job (...)	In case that the number of PEs along the x- and y-direction of the virtual processor grid is set via npex and npey, the product npey*npex has to match exactly the total number of processors which is assigned by the palmrun-option -X.
PA0222	if the processor topology is prescribed by the user, both values of "npex" and "npey" must be given in the NAMELIST-parameter file	In case that only one number of processors along x- or y- direction npex or npey is set in the &runtime_parameters-Namelist, the remaining, so far not assigned, number of processors has to be set, too.
PA0223	errors in \$nesting_parameters	An unvalid variable name or value has been given in the nestpar-NAMELIST. Carefully check your nestpar-NAMELIST and compare with the parameters given and explained in the Nesting-section of the model steering parameters.
PA0224	Each dz_stretch_level_end has to be ... than its corresponding value for dz_stretch_level_start ... 4*MAX(dz(n),dz(n+1)) to allow for smooth grid stretching	To allow for a smooth stretching, the distance between dz_stretch_level_start and dz_stretch_level_end has to be large enough. Please increase the stretching region appropriately.
PA0225	x-direction: gridpoint number (...) is not an integral multiple of the number of processors (...)	The division of the number of grid points along the x-direction given by nx+1 by the number of processors along the x-direction has a rest and is therefore not an integral multiple of the number of processors. To solve this problem you must ensure that the aforementioned division is without rest for example by setting the number of PEs in x-direction manually (see npex) or by changing nx. It might also be the case that you did not think about that nx+1 is the total number of gridpoints along the x-direction instead of nx.
PA0226	Each dz_stretch_level_start has to be ... than ...	The stretching region has to be defined above the first two grid points (Prandtl-layer). In case of ocean mode the stretching region muss below the two highest grid points (surface). Please adjust dz_stretch_level_start accordingly.
PA0227	y-direction: gridpoint number (...) is not an integral multiple of the number of processors (...)	The division of the number of grid points along the y-direction given by ny+1 by the number of processors along the y-direction has a rest and is therefore not an integral multiple of the number of processors. To solve this problem you must ensure that the aforementioned division is without rest for example by setting the number of PEs in y-direction manually (see npey) or by changing ny. It might also be the case that you did not think about that ny+1 is the total number of gridpoints along the y-direction instead of ny.
PA0228	Two adjacent values of dz must be different	It is necessary to specify different values for dz if they are adjacent.
PA0229	nesting-setup requires different number of MPI procs (...) than provided (...)	This message appears for nested runs, if the total number of MPI processes for all nested domains given in the nestpar-NAMELIST is larger than the number of MPI processes which has been allowed for the run, e.g. with palmrun-option -X. (Attention: For hybrid OpenMP/MPI-runs the number of MPI processes allowed for the run is the number given by -X divided by the number of threads per MPI-task, as given with palmrun-option -O.) You either have to provide the run more resources (i.e. more cores) or you have to decrease the number of MPI processes in $nestpar.
PA0230	transposition z --> x: nz=... is not an integral multiple of pdims(1)= ...	Due to restrictions in data transposition, the division of nz by the number of processors in x-direction has to be without rest. Please ensure this by changing nz or setting the number of gridpoints in x-direction (pdims(1)) manually by npex.
PA0231	transposition x --> y: nx+1=... is not an integral multiple of pdims(2)= ...	Due to restrictions in data transposition, the division of nx+1 by the number of processors in y-direction has to be without rest. Please ensure this by changing nx or setting the number of gridpoints in y-direction (pdims(2)) manually by npex.
PA0232	transposition y --> z: ny+1=... is not an integral multiple of pdims(1)=...	Due to restrictions in data transposition, the division of ny+1 by the number of processors in x-direction has to be without rest. Please ensure this by changing ny or setting the number of gridpoints in x-direction (pdims(1)) manually by npex.
PA0233	transposition x --> y: ny+1=... is not an integral multiple of pdims(1)=...	Due to restrictions in data transposition, the division of ny+1 by the number of processors in x-direction has to be without rest. Please ensure this by changing ny or setting the number of gridpoints in x-direction (pdims(1)) manually by npex.
PA0234	direct transposition z --> y (needed for spectra): nz=... is not an integral multiple of pdims(2)=...	Due to restrictions in data transposition, the division of nz by the number of processors in y-direction has to be without rest. Please ensure this by changing nz or setting the number of gridpoints in y-direction (pdims(2)) manually by npey.
PA0235	mg_switch_to_pe0_level out of range and reset to 0	mg_switch_to_pe0_level was manually set out of range. It was reset to 0, so that the gathering level is determined automatically and displayed in file RUN_CONTROL. See mg_switch_to_pe0_level for details.
PA0236	grid coarsening on subdomain level cannot be performed	The multigrid pressure solver halfs the number of grid points in each direction to get coarser grid levels. This is done for the subdomains on each PE until one of the directions cannot be divided by 2 without rest. If this is the case, the coarsest grid level of each subdomain are gathered on each PE for further coarsening. Before gathering, the coarsening must be done for the subdomain at least one time. You get this error messages for example with the following combination: nx = 60, ny = 60, nz = 60, npex = 4, npey = 2. With this combination, the subdomain on each PE has the size: nx = 15, ny = 30, nz = 60. The number of grid points in the x-direction of the subdomain cannot be divided by 2 and no coarsening is possible for the subdomains in this example. To avoid this error ensure that the number of grid points in each direction can be divided by 2 without rest on the subdomain of an PE at least one time. Therefor vary the number of grid points for the direction which does not fit by changing nx , ny or nz or adjust the number of processors by modifying the parameters npex or npey in order to get other subdomain sizes. In the example given above, you can avoid the error by changing nx or npex. For example setting nx = 64 leads to a subdomain of nx = 16, ny = 30, nz = 60. All numbers are now divisible by 2 without rest and the first coarser grid on the subdomain is then: nx = 8, ny = 15, nz = 30.
PA0237	multigrid gather/scatter impossible in non parallel mode	You are using the multigrid-solver and are running PALM in non-parallel mode (i.e. on a single processor core), but you have set a multigrid level (using parameter mg_switch_to_pe0_level) from where on data shall be collected on core 0 in order to allow for a further coarsening of the grid. Obviously, this does not make sense if only one core is used. Remove this parameter from your NAMELIST-file or set it to value -1 to switch of collection.
PA0238	more than 10 multigrid levels	You have selected the multigrid Poisson-solver (psolver = "multigrid") and a numerical grid which allows for more than 10 coarsening levels. This may happen for very large grids where the grid point numbers along x,y,z are given by 2n with n>10. The smallest grid which may cause this error would have 20483 points. However, depending on the chosen domain decomposition, much larger grids might be possible. Choose a different number of grid points to circumvent this problem.
PA0239	The value for "topography_grid_convention" is not set. Its default value is only valid for "topography" = "single_building", "tunnel" "single_street_canyon" or "read_from_file" Choose "cell_edge" or "cell_center".	See topography_grid_convention for details.
PA0240	The value for "topography_grid_convention" is not recognized. Choose "cell_edge" or "cell_center".	See topography_grid_convention for details.
PA0241	netcdf_precision must contain a "_" netcdf_precision(...)="..."	Output types can be assigned a NETCDF precision. For that, the output type has to be connected with the precision via "_". See netcdf_precision for details.
PA0242	illegal netcdf precision: netcdf_precision( ...)="..."	See PA0241. Allowed NETCDF precisions are 'NF90_REAL4' (single precision) or 'NF90_REAL8' (double precision) .
PA0243	unknown variable in initialization_parameters assignment: netcdf_precision(...)="..."	See PA0241. Allowed outputs are 'xy', 'xz', 'yz', '2d', '3d', 'pr', 'ts', 'sp', 'prt' or 'all'.
PA0244	no grid defined for variable ...	All output quantities need a grid on which they are then output. See user-defined output documentation for a detailed description on how to output your own quantities. If you did not define your own output quantities and if you did not change the code please submit a trouble ticket.
PA0245	netCDF file for volume data ... from previous run found, but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its 3d variables do not match the ones of the current run. Therefore a new file is created instead.
PA0246	netCDF file for volume data ... from previous run found, but this file cannot be extended due to mismatch in number of vertical grid points (nz_do3d). New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, the number of vertical grid points of the 3d variables do not match the one of the current run. Therefore a new file is created instead.
PA0247	netCDF file for volume data ... from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0248	netCDF file for volume data ... from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0249	netCDF file for cross-sections ... from previous run found, but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its 2D variables do not match the ones of the current run. Therefore a new file is created instead.
PA0250	netCDF file for cross-sections ... from previous run found, but this file cannot be extended due to mismatch in number of cross sections. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, the number of cross sections do not match the one of the current run. Therefore a new file is created instead.
PA0251	netCDF file for cross-sections ... from previous run found but this file cannot be extended due to mismatch in cross section levels. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, the specified cross section levels which shall be outputted do not match the ones of the current run. Therefore a new file is created instead.
PA0252	netCDF file for cross sections ... from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0253	netCDF file for cross-sections ... from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0254	netCDF file for vertical profiles from previous run found, but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its 1D variables do not match the ones of the current run. Therefore a new file is created instead.
PA0255	netCDF file for vertical profiles from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0256	netCDF file for vertical profiles from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0257	netCDF file for (flight) time series from previous run found but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its time dependent variables do not match the ones of the current run. Therefore a new file is created instead.
PA0258	netCDF file for (flight) time series from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0259	netCDF file for (flight) time series from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0260	netCDF file for spectra from previous run found, but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its variables do not match the ones of the current run. Therefore a new file is created instead.
PA0261	netCDF file for spectra from previous run found, but this file cannot be extended due to mismatch in number of vertical levels. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, the number of vertical levels which shall be outputted do not match the ones of the current run. Therefore a new file is created instead.
PA0262	netCDF file for spectra from previous run found, but this file cannot be extended due to mismatch in heights of vertical levels. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, the specified vertical levels (heights) which shall be outputted do not match the ones of the current run. Therefore a new file is created instead.
PA0263	netCDF file for spectra from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0264	netCDF file for spectra from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0265	netCDF file for particles from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0266	netCDF file for particles from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0267	netCDF file for particle time series from previuos run found, but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its time dependent particle data do not match the data of the current run. Therefore a new file is created instead.
PA0268	netCDF file for particle time series from previous run found, but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0269	netCDF file for particle time series from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0270	mode "..." not supported	The mode which steers the netcdf output can not be processed in netcdf_interface_mod.f90​). Possible modes are 3d, ma (mask), xy, xz, yz, pr (profiles), ps (particle timeseries), fl (flight data), ts (timeseries), sp (spectra). In addition, the extension (_ext) and the creation of netcdf files is possible. If you run into this error please submit a trouble ticket.
PA0271	Error(s) in namelist <parameter_list> Reading fails on line <line_number> at <line>	There is an error in your INPUT file in the given line. Most likely this is a typo or outdated steering parameter. NOTE: According to the Fortran Standard, the line on which reading stops in case of an error is not clearly defined. To our knowledge the current implementation works, but it is not guaranteed to do so. If you encounter this error message and you are sure that the given line is correct, please submit a trouble ticket.
PA0272	no &initialization_parameters-namelist found	Your parameter file must contain an &initialization_parameters-namelist. Parameters given in this namelist are required for model steering. Please take a look at our beginners' simulation examples and appropriately correct your parameter file. One possible error might be a typo in the NAMELIST name, e.g. inialization_parameters instead of initialization_parameters.
PA0273	no value or wrong value given for nx: nx=...	See parameter nx for allowed values, and check the &initialization_parameters-namelist in your parameter file.
PA0274	no value or wrong value given for ny: ny=...	See parameter ny for allowed values, and check the &initialization_parameters-namelist in your parameter file.
PA0275	no value or wrong value given for nz: nz=...	See parameter nz for allowed values, and check the &initialization_parameters-namelist in your parameter file.
PA0276	local file ENVPAR not found, some variables for steering may not be properly set	Some model steering parameters are passed to PALM through a namelist &envpar which is stored in local file ENVPAR. This file is created by the script palmrun​ which can be used to start model runs. This message appears, if ENVPAR could not be found because it was not created by palmrun. Check if you changed anything in the script.
PA0277	errors in local file ENVPAR some variables for steering may not be properly set	The namelist &envpar expects certain model steering parameters (see parin.f90​). Some of these parameters have not been properly set or are missing entirely. This should only happen if (1) you didn't use palmrun to start your run, (2) you used an old version of palmrun that is not compatible with your model version anymore (then please update) or (3) you changed palmrun manually and set some parameters of the &envpar namelist incorrectly. (Also see PA0276)
PA0278	no envpar-NAMELIST found in local file ENVPAR or some variables for steering may not be properly set	Some model steering parameters are passed to PALM through a namelist &envpar which is stored in local file ENVPAR. This file is created by the script palmrun​ which can be used to start model runs. The &envpar namelist was not found. This is possible if you (1) did not use palmrun to start your run or (2) changed palmrun manually so that the namelist is not properly created.
PA0279	wrong component: ...	This message is produced by the procedure pcm_tendency of the plant canopy model. It calculates drag for velocity components and scalar quantities. The calculated components are: u, v, w, pt, q, e, s (1-7). The subroutine is only called for these 7 quantities. If this error occured, you called the routine from your own code for a component that is out of range. If you wish to do this, you must adjust procedures pcm_tendency and pcm_tendency_ij in file plant_canopy_model_mod.f90​ accordingly.
PA0280	No tunnel width is given.	This error occurs if you have set topography= 'tunnel' in you parameter file but you did not specify tunnel_width_x or tunnel_width_y
PA0281	Inconsistent tunnel parameters: tunnel can only be oriented either in x- or in y-direction.	Please do not specify tunnel_width_x and tunnel_width_y in the parameter file at the same time.
PA0282	Tunnel width too large	tunnel_width_x must be <= (nx+1)*dx
PA0283	no sufficient convergence within 1000 cycles	Still after 1000 cycles of the multigrid-solver the divergence residual is larger than the residual limit given by residual_limit. Try to increase the residual limit, or fix the number of multigrid cycles (see mg_cycles). In any case, carefully check if the divergence of the velocity field is sufficiently reduced by the multigrid solver. This can be done by comparing the divergence before and after the call of the multigrid solver which is printed in the RUN_CONTROL file. If this error appears during the initial phase of a run (before the first timestep), the number of subdomain gridpoints along x/y/z probably do not allow sufficient coarsening of the grid. The number of gridpoints should allow for a division by two (without rest) at least 2-3 times.
PA0284	data from subdomain of previous run mapped more than 1000 times	The model domain of the precursor run was much smaller than that of the main run. It was reused more than 1000 times in one direction. Try a smaller main run domain or a larger precursor.
PA0285	number of PEs or virtual PE-grid changed in restart run. Set debug_output =.T. to get a list of files from which the single PEs will read respectively	Either the model domain of the precursor run is smaller than that of the main run and has been copied one or multiple times or the number of processors has been changed during restart runs. This informative message is only printed out for PE0 but is also valid for the other processors. Set runtime parameter debug_output = .T. to see from which files the respective PEs will read.
PA0286	version mismatch concerning binary_version_local: version on file = "..." version in program = "..."	The precursor run was carried out with a different version than the main run. Repeat the precurser with the current version or carry out the main run with the same version as the precursor.
PA0287	problem with index bound nxl on restart file "..." nxl = ... but it should be = ... from the index bound information array	The processor grid was changed between this and the previous run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0288	problem with index bound nxr on restart file "..." nxr = ... but it should be = ... from the index bound information array	The processor grid was changed between this and the previous run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0289	problem with index bound nys on restart file "..." nys = ... but it should be = ... from the index bound information array	The processor grid was changed between this and the previous run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0290	problem with index bound nyn on restart file "..." nyn = ... but it should be = ... from the index bound information array	The processor grid was changed between this and the previous run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0291	mismatch between actual data and data from prior run on PE ... nzb on file = ... nzb = ...	The vertical extent of the model domain must be the same in precursor and main run. In this case, there is a mismatch in the respective topography. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0292	mismatch between actual data and data from prior run on PE ... nzt on file = ... nzt = ...	The vertical extent of the model domain must be the same in precursor and main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0293	data_output_pr = ... is not implemented for air_chemistry = .FALSE.
PA0294	vegetation_type = 1 (bare soil) requires vegetation_coverage = 0	Self-explanatory. Change the value of vegetation_type or vegetation_coverage.
PA0295	complex_terrain requires topography = 'read_from_file'	Self-explanatory. See complex_terrain and topography.
PA0296	version mismatch concerning binary_version_global: version on file = "..." version on program = "..."	The precursor run was carried out with a different version than the main run. Repeat the precurser with the current version or carry out the main run with the same version as the precursor.
PA0297	numprocs not found in data from prior run on PE ...	Number of processors are not written out or read in correctly during restarts. Please submit a trouble ticket.
PA0298	hor_index_bounds not found in data from prior run on PE ...	Field that stores the horizontal index bounds of each processor are not written out or read in correctly during restarts. Please submit a trouble ticket.
PA0299	nz not found in data from prior run on PE ...	Vertical number of gridpoints are not written out or read in correctly during restarts. Please submit a trouble ticket.
PA0300	max_pr_user not found in data from prior run on PE ...	Number of user-defined profiles (must not change within a job chain) are not written out or read in correctly during restarts. Please submit a trouble ticket.
PA0301	statistic_regions not found in data from prior run on PE ...	Number of statistic regions are not written out or read in correctly during restarts. Please submit a trouble ticket.
PA0302	unknown variable named "..." found in ... data from prior run on PE ...	During the initial run, a variable was written to BINOUT, that is not recognized during read-in of the restart run. Note that user variables have to be written in user_write_restart_data_mod (not in write_restart_data_mod​ where standard output is written). It has to be read accordingly in user_read_restart_data_mod. Also see: user output.
PA0303	nz not found in restart data file	nz is necessary for the main run to continue. This will happen if the initialization parameter list was altered between precursor and main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs. Also check if you altered nz between precursor and main run.
PA0304	mismatch concerning number of gridpoints along z: nz on file = "..." nz from run = "..."	The main run must have the same number of grid points in z-direction as the precursor run. x- and y-directions may differ. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0305	max_pr_user not found in restart data file	max_pr_user is necessary for the main run to continue. This will happen if the initialization parameter list was altered between precursor and main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs. Also check if you altered data_output_pr_user between precursor and main run.
PA0306	number of user profiles on restart data file differs from the current run: max_pr_user on file = "..." max_pr_user from run = "..."	This message is informative, the run will continue nonetheless. This will only happen in case the number of user profiles was changed from precursor to main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0307	statistic_regions not found in restart data file	statistic_regions are necessary for the main run to continue. This will happen if the initialization parameter list was altered between precursor and main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0308	statistic regions on restart data file differ from the current run: statistic regions on file = "..." statistic regions from run = "..." statistic data may be lost!	This message is a warning, the run will continue nonetheless. This will only happen in case the statistic regions were changed from precursor to main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
PA0309	inflow profiles not temporally averaged. Averaging will be done now using ... samples.	The tubulent inflow method needs time averaged inflow profiles. This warning occurs if the output of time averaged profiles (skip_time_dopr + dt_dopr) is not an integral divisor of the end_time which is specified for the precursor run or if skip_time_dopr + dt_dopr is larger than this end_time.
PA0310	remote model "..." terminated with terminate_coupled_remote = ... local model "..." has terminate_coupled = ...	The remote model in a coupled run has been terminated. The reason for the termination is provided by terminate_coupled. Termination reasons: 1 model was terminated (unknown reason) 2 time step has reached minimum limit (see PA0312) 3 run will be terminated because it is running out of job cpu limit remaining time (see PA0163) 4 run will be terminated due to user settings of dt_restart (see PA0164) 5 run will be terminated due to user settings of restart_time (see PA0164) 6 unscheduled termination was forced by the user (see PA0398)
PA0311	number of gridpoints along x or/and y contain illegal factors only factors 2, 3, 5 are allowed	In case that fft_method='temperton-algorithm', the number of horizontal grid points (nx+1, ny+1) must be composed of prime factors 2,3 and 5. Higher prime factors such as 7 are not allowed. Please ensure that these restrictions are fulfilled or use 'singleton-algorithm' as fft_method.
PA0312	Time step has reached minimum limit. dt = ... s Simulation is terminated. old_dt = ... s dt_u = ... s dt_v = ... s dt_w = ... s dt_diff = ... s u_max = ... m/s k=... j=... i=... v_max = ... m/s k=... j=... i=... w_max = ... m/s k=... j=... i=...	The time step is determined according to the CFL criterion to assure a stable numerical solution. This error message means that the required minimum time step, determined from the three velocity components, is several orders of magnitude smaller than dt_max, or, in other words, that at least one of the velocity components got too large. Due to the large number of complex reasons it should be noted that this list is not complete, but it is intended to give general hints how to proceed in case of this error message. First, check for a unrealistic value of dt_max in the NAMELIST file. Moreover, this error message may indicate for unrealistic settings of e.g. boundary conditions or other NAMELIST parameters. For very small vertical grid spacing dz this error might also occur if roughness_length >= dz. Please also check if this error appears if you run without USERCODE. To compile and run the PALM and USERCODE with DEBUG-options might also give sometimes valuable hints.
PA0313	Resolved plant-canopy is defined on top of an artificially created building grid point (emerged from the filering) - LAD profile is omitted at this grid point	Due to numerical reasons one-grid point cavities in topography are filtered, so that building geometries might be changed on this scale. In case tall canopy is directly adjacent to the building before, it may happen that building and plant canopy overlap after the filtering. In order to avoid that LAD is mistakenly mapped on top of buildings, which may significantly affect the downstream flow and radiation properties, LAD profiles are ommitted at these artificially-created building grid points.
PA0314	External radiation forcing does not cover the entire simulation time.
PA0315	In case of external radiation forcing a dynamic input file is required. If no dynamic input for the child domain(s) is provided, at least one for the root domain is needed.
PA0316	pavement-surfaces are not allowed in combination with a non-default setting of dz_soil
PA0317	ocean mode does not allow coupling_char = ... set by palmrun-option "-y"	The palmrun option "-y" must not be used for atmosphere runs. The option is only required for ocean precursor runs, which are followed by atmosphere-ocean coupled restart runs.
PA0318	inflow_damping_height must be explicitly specified because the inversion height calculated by the prerun is zero	See inflow_damping_height.
PA0319	section_xy must be <= nz + 1 = ...	You specified a height through the grid index that is larger than the vertical model domain. Adjust section_xy.
PA0320	section_xz must be <= ny + 1 = ...	You specified a y position through the grid index that is larger than the horizontal model domain. Adjust section_xz.
PA0321	section_yz must be <= nx + 1 = ...	You specified a x position through the grid index that is larger than the horizontal model domain. Adjust section_yz.
PA0322	output of qsws* requires humidity=.TRUE.	Variables connected with humidity, e.g. the surface latent heatflux qsws*, can only be output if the moist version of PALM is used, i.e. if humidity = .TRUE.
PA0323	output of averaged quantity "..." requires to set a non-zero averaging interval	If 2d or 3d data shall be output as a time average over a certain time interval, the parameter averaging_interval must be set to a non-zero value. The default is averaging_interval = 0.0, i.e. by default no averaging is applied to the output variables.
PA0324	applying large scale vertical motion is not allowed for ocean mode	Large scale subsidence is only reasonable and implemented for atmospheric runs. The setting of subs_vertical_gradient and subs_vertical_gradient_level is not available for the ocean mode.
PA0325	illegal value: masks must be >= 0 and <= "..."(=max_masks)	If more than max_masks are needed, the value for max_maskes can be changed in modules.f90​. See documentation of the user interface and data_output_masks.
PA0326	illegal value: mask_scale_x, mask_scale_y and mask_scale_z must be > 0.0	mask_scale_x (or y or z)
PA0327	no masked output available for: "..."	See data_output_masks for allowed variables. If you want to have user-defined masked output check also user_data_output_mask.f90​ and add the respective CASE.
PA0328	netCDF file formats 5 and 6 (with parallel I/O support) are currently not supported.	Parallel mask output not yet supported. Choose another value for netcdf_data_format.
PA0329	number of output quantitities given by data_output_mask and data_output_mask_user exceeds the limit of 100	Check data_output_masks and data_output_masks_user and reduced the quantities you want to output Otherwise you have to change the limit of 100 in the code.
PA0330	illegal value for data_output_masks: "..."	This error is most likely related to a typo in the parameter file (a output variable was used that does not exist in PALM). For possible output quantities see data_output_masks
PA0331	"..." in mask "..." along dimension "..." exceeds "..." = "..."	Your masked output exeeds the model domain in x-, y- or z- direction. Check the documentation of masked output and mask_x (or y or z)
PA0332	mask_loop(...,...,1)=... and/or mask_loop(...,...,2)=... exceed (...+1)*.../mask_scale(...)=...	Your looped output mask exeeds the model domain in x- or y-direction. Check mask_x_loop (or y) and mask_scale_x (or y).
PA0333	mask_loop(...,...,1)=... and/or mask_loop(...,...,2)="..." exceed zu(nz+1)/mask_scale(...)=...	Your looped output mask exeeds the model domain in z-direction. Check mask_z_loop and mask_scale_z.
PA0334	mask_loop(...,3,2)=... exceeds dz_stretch_level=... or dz_stretch_level_ground=.... Vertical mask locations will not match the desired heights within the stretching region.	Recommendation: use mask instead of mask_loop.
PA0335	netCDF file for "..." data for mask "..." from previous run found but this file cannot be extended due to variable mismatch. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its masked variables do not match the ones of the current run. Therefore a new file is created instead.
PA0336	netCDF file for "..." data for mask "..." from previous run found but this file cannot be extended due to mismatch in number of vertical grid points. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, the number of vertical grid points of the masked variables do not match the one of the current run. Therefore a new file is created instead.
PA0337	netCDF file for "..." data for mask "..." from previous run found but this file cannot be extended because the current output time is less or equal than the last output time on this file. New file is created instead.	This is a warning. A netCDF file from a previous run exist which is tried to be opened for extension. However, its last output time is greater than the first output time of the current run. Therefore a new file is created instead.
PA0338	netCDF file for "..." data for mask "..." from previous run found. This file will be extended.	This is just an informative message and self-explanatory.
PA0339	coupling mode "...": nx+1 in ocean is not divisible by nx+1 in atmosphere without remainder	For coupling of atmosphere and ocean, a smaller grid length in the y-direction can be chosen for the ocean, so that the ocean has more grid points in the y-direction than the atmosphere. In this case, the information must be interpolated for the data exchange between atmosphere and ocean. It must therefore be ensured that each interpolation interval has the same number of gridpoints. This is ensured if the following holds: with the number of grid points in the y-direction for the ocean and atmosphere model, respectively. To avoid this error ensure that the above equation is fulfilled.
PA0340	coupling mode "...": ny+1 in ocean is not divisible by ny+1 in atmosphere without remainder	For coupling of atmosphere and ocean, a smaller grid length in the y-direction can be chosen for the ocean, so that the ocean has more grid points in the y-direction than the atmosphere. In this case, the information must be interpolated for the data exchange between atmosphere and ocean. It must therefore be ensured that each interpolation interval has the same number of gridpoints. This is ensured if the following holds: with the number of grid points in the y-direction for the ocean and atmosphere model, respectively. To avoid this error ensure that the above equation is fulfilled.
PA0341	non-default setting of dz_soil does not allow to use pavement_type /= 0)	Currently it is not possible to assign a user-defined number of soil layers when using pavement_type /= 0 as the individual depths of the pavements are fixed values.
PA0342	pavement_type = 0 (user_defined) requires setting of pavement_heat_conduct /= 9999999.9	In case of a user-defined pavement type, the heat conductivity of the pavement must be given
PA0343	initializing_actions = 'initialize_vortex' is not allowed with conserve_volume_flow = .T.	Self-explanatory. Check conserve_volume_flow and/or initializing_actions for different values.
PA0344	psolver must be called at each RK3 substep when 'ws-scheme' is used for momentum_advec.	The use of 5th-order advection scheme for the momentum equations requires a sufficiently large reduction of flow divergence to minimize numerical errors. Set call_psolver_at_all_substeps to true.
PA0345	uv_heights(1) must be 0.0	See uv_heights for further instructions.
PA0346	u_profile(1) and v_profile(1) must be 0.0	See u_profile and v_profile for further instructions.
PA0347	Coriolis force is switched on (omega /= 0.0) and initial profiles u_profile and v_profile are prescribed	Per default the initial wind profile (u- and v-profile) is set to the geostrophic wind profile. However, the initial wind profile can also be set to a different profile with the initialization parameters u_profile and v_profile. An initial wind profile that deviates too much from the geostrophic wind profile will cause strong inertia oscillations and thus the mean flow will take a long time to become steady state. The strength of the inertia oscillation can be significantly reduced, when the initial wind profile is set to the steady-state wind profile that might be obtained by a low-cost precursor simulation with a small domain and coarser grid spacing.
PA0348	radiation_interactions_on is set to .FALSE. although vertical surfaces and/or trees exist. The model will run without RTM (no shadows, no radiation reflections)	This is just a warning (self-explanatory). Maybe you should change the namelist parameter radiation_interactions_on to TRUE to get more realistic results.
PA0349	Incorrect type of plant canopy. Allowed values 0 <= pctype <= 10, but pctype is ...	Description will follow.
PA0350	unknown collision kernel: collision_kernel = "..."	see package parameter collision_kernel for allowed values.
PA0351	heatflux must not be set for pure neutral flow	Initialization parameter neutral = .TRUE. has been set, but non-zero values for parameters surface_heatflux and / or top_heatflux are given at the same time. This is not allowed for simulating a flow with pure neutral stratification where the temperature equation is switched off. Check your parameter file.
PA0352	pavement_type = 0 (user_defined) requires setting of z0_pavement /= 9999999.9	In case of a user-defined pavement type, the roughness length for momentum must be given by the user.
PA0353	pavement_type = 0 (user_defined) requires setting of z0h_pavement /= 9999999.9	In case of a user-defined pavement type, the roughness length for heat must be given by the user.
PA0354	It is not allowed to arrange more than 100 profiles with cross_profiles. Apart from that, all profiles are saved to the netCDF file.	This is just an informative message. All profiles are written to the netCDF file. Only the first 100 profiles will be plotted by palmplot pr with var=cross_profiles (default). To see all profiles, add the parameter var=all to palmplot pr.
PA0355	netcdf_deflate out of range given value: ..., allowed range: 0-9	Set runtime-parameter netcdf_deflate to a value within the allowed range
PA0356	netcdf_deflate reset to 0	You have set netcdf_data_format /= 3 and netcdf_deflate > 0 in the runtime_parameters-NAMELIST. However, data compression only works for the NetCDF4/HDF5 non-parallel format (netcdf_data_format = 3).
PA0357	unknown cloud microphysics scheme cloud_scheme = "..."	Unknown cloud microphysics scheme. Allowed cloud microphysics schemes are "saturation_adjust", "kessler", "seifert_beheng" or "morrison".
PA0358	data_output_pr = '...' is not implemented for cloud_scheme /= ...	Output of profiles of rain drop number density (nr) or rain water mixing ratio (qr) is only allowed for cloud_scheme = "seifert_beheng". Output of profiles of cloud drop number density (nc) is only allowed for cloud_scheme = "morrison".
PA0359	output of "..." requires cloud_scheme = seifert_beheng	Output of 3d-data, cross-sections or masked data of rain drop number concentration (nr) or rain water content (qr) is only allowed for cloud_scheme = "seifert_beheng". Output of cloud drop number density (nc) is only allowed for cloud_scheme = "morrison".
PA0360	plant_canopy = .TRUE. requires cloud_scheme /= seifert_beheng	It is not allowed to use plant_canopy with the cloud_scheme = "seifert_beheng".
PA0361	output of ssws* requires passive_scalar=.TRUE.	Variables connected with passive_scalar, e.g. like the resolved-scale turbulent scalar flux w*s*, can only be output if passive_scalar = .TRUE.
PA0362	nz >= 14 is required	Due to an internal restriction, PALM currently requires more than 13 vertical grid levels. Increase the number of vertical grid levels in the initialization_parameters namelist (parameter nz).
PA0363	No time dependent surface variables in LSF_DATA for end of run found	PALM detected an end-of-file condition for the surface values in LSF_DATA and aborts. Possible reasons could be that no or too less time dependent surface variables are provided in the large scale forcing file.
PA0364	zu(k) = ... m is higher than the maximum height in NUDING_DATA which is ...m. Interpolation on PALM grid is not possible.	NUDGING_DATA has a maximum vertical height that is smaller than the vertical extent of the grid used in PALM. Hence, interpolation of the NUDGING_DATA onto the PALM grid is not possible. Reduce either the vertical extent of the PALM modeling domain or enlarge the NUDING_DATA file correspondingly. Note: it is also possible that your file NUDGING_DATA is not formatted correctly and that there has been an error while reading it.
PA0365	file NUDGING_DATA does not exist	Make sure that the file basename_nudge containing the nudging profiles as described in NUDGING_DATA is provided in the INPUT folder of the respective run on the host where the job is running.
PA0366	errors in file NUDGING_DATA	PALM has problems reading the file basename_nudge. Possible reasons could be that the format described in NUDGING_DATA is not followed closely.
PA0367	unknown prognostic variable ...	The tendency due to nudging can only be applied to the prognostic variable u, v, pt and q. Make sure that one of the variables is used.
PA0368	file LSF_DATA does not exist	Make sure that the file basename_lsf containing surface fluxes, surface temperature, humidity and pressure as well as profiles of the geostrophic wind components and large scale subsidence described in LSF_DATA is provided in the INPUT folder of the respective run on the host where the job is running.
PA0369	errors in file LSF_DATA	PALM has problems reading the file basename_lsf. Possible reasons could be that the format described in LSF_DATA is not followed closely.
PA0370	Initial profiles of u, v, pt and q from NUDGING_DATA are used.	Informative message that initial profiles from the nudging file are used.
PA0371	Time dependent surface variables in LSF_DATA set in after end of simulation - lsf_surf is set to FALSE	This messages appears in the case that the first time step of the surface values read in from LSF_DATA is larger than the end time of the simulation. In this case the surface heat and water fluxes prescribed in LSF_DATA cannot be used.
PA0372	No time dependent vertical profiles in LSF_DATA for end of run found	PALM detected an end-of-file condition for the profile data in LSF_DATA and aborts. Possible reasons could be that no time dependent profile data is provided in the large scale forcing file.
PA0373	Time dependent large scale profile forcing from LSF_DATA sets in after end of simulation - lsf_vert is set to FALSE	This messages appears in the case that the first time step of the profile data read in from LSF_DATA is larger than the end time of the simulation. In this case the geostrophic wind profiles and large scale subsidence profile prescribed in LSF_DATA cannot be used.
PA0374	Nudging requires large_scale_forcing = .T.. Surface fluxes and geostrophic wind should be prescribed in file LSF_DATA	In order to use nudging it is required to use large_scale_forcing = .T., too. The surface values and profiles needed in LSF_DATA should correspond to the data provided in NUDGING_DATA.
PA0375	Non-cyclic lateral boundaries do not allow for the usage of large scale forcing from external file.	Large scale forcing (and also nudging) are not implemented/tested for non-cyclic boundary conditions so far.
PA0376	The usage of large scale forcing from external file LSF_DATA requires humidity = .T..	If you want to use large_scale_forcing (and also nudging) from an external file, you need to run PALM with humidity.
PA0377	The usage of large scale forcing from external file LSF_DATA is not implemented for non-flat topography	Please use topography = 'flat' or refrain from using large scale forcing.
PA0378	The usage of large scale forcing from external file LSF_DATA is not implemented for ocean runs	Please use ocean = .F. or refrain from using large scale forcing.
PA0379	water_type = 0 (user_defined) requires setting of water_temperature /= 9999999.9	When the water_type is set to be user-defined, a water temperature must be prescribed.
PA0380	There is no default large scale vertical velocity profile set. Specify the subsidence velocity profile via subs_vertical_gradient and subs_vertical_gradient_level.	With large_scale_subsidence = .T. but without large_scale_forcing a profile for the subsidence velocity w_subs has to be prescribed. See subs_vertical_gradient_level.
PA0381	Enable usage of large scale subsidence by setting large_scale_subsidence = .T..	subs_vertical_gradient_level requires large_scale_subsidence = .T..
PA0382	data_output_pr = w_subs is not implemented for large_scale_subsidence = .FALSE.	w_subs can only be part of the profile output if large_scale_subsidence = .T..
PA0383	netCDF file formats 5 (parallel netCDF 4) and 6 (parallel netCDF 4 Classic model) are currently not supported (not yet tested) for masked data. Using respective non-parallel output for masked data.	So far, parallel NetCDF output is not available for masked data. If the user is setting the parameter netcdf_data_format to five or six for getting parallel output, netcdf_data_format is set internally to three or four for masked data.
PA0384	Output of xy cross-sections is not given at t='...' because the maximum number of output time levels is exceeded.	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do2d_xy and dt_do2d_xy can be set by the user. If this limit is exceeded, this warning is given and an output of xy-sections is not done anymore. This could be the case if the simulated time exceeds the given end time by the length of the given output interval. In this case, the user can start a restart run and give an output at the beginning.
PA0385	Output of xz cross-sections is not given at t='...' because the maximum number of output time levels is exceeded.	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do2d_xz and dt_do2d_xz can be set by the user. If this limit is exceeded, this warning is given and an output of xz-sections is not done anymore. This could be the case if the simulated time exceeds the given end time by the length of the given output interval. In this case, the user can start a restart run and give an output at the beginning.
PA0386	Output of yz cross-sections is not given at t='...' because the maximum number of output time levels is exceeded.	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do2d_yz and dt_do2d_yz can be set by the user. If this limit is exceeded, this warning is given and an output of yz-sections is not done anymore. This could be the case if the simulated time exceeds the given end time by the length of the given output interval. In this case, the user can start a restart run and give an output at the beginning.
PA0387	Output of 3d data is not given at t='...' because the maximum number of output time levels is exceeded.	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do3d and dt_do3d can be set by the user. If this limit is exceeded, this warning is given and an output of 3d data is not done anymore. This could be the case if the simulated time exceeds the given end time by the length of the given output interval. In this case, the user can start a restart run and give an output at the beginning.
PA0388	netCDF file for volume data "..." from previous run found, but this file cannot be extended because the number of output time levels has been increased compared to the previous simulation. New file is created instead.'	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do3d and dt_do3d can be set by the user. If the calculated number of maximum time levels between the initial run and a restart run changed by modifing on of the parameters above, a new output file is created.
PA0389	netCDF file for cross sections "..." from previous run found, but this file cannot be extended because the number of output time levels has been increased compared to the previous simulation. New file is created instead.'	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do2d_xy and dt_do2d_xy can be set by the user. If the calculated number of maximum time levels between the initial run and a restart run changed by modifying on of the parameters above, a new output file is created.
PA0390	netCDF file for cross sections "..." from previous run found, but this file cannot be extended because the number of output time levels has been increased compared to the previous simulation. New file is created instead.'	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do2d_xz and dt_do2d_xz can be set by the user. If the calculated number of maximum time levels between the initial run and a restart run changed by modifing on of the parameters above, a new output file is created.
PA0391	netCDF file for cross sections "..." from previous run found, but this file cannot be extended because the number of output time levels has been increased compared to the previous simulation. New file is created instead.'	In case of parallel NetCDF output, the time dimension is limited for increasing the performance. The number of time levels is calculated at the beginning of the simulation by the formula: The parameters end_time, skip_time_do2d_yz and dt_do2d_yz can be set by the user. If the calculated number of maximum time levels between the initial run and a restart run changed by modifing on of the parameters above, a new output file is created.
PA0392	water_type = 0 (user_defined) requires setting of z0h_water /= 9999999.9'	If the water_type is set to be user-specific, it is essential to prescribe a roughness length for heat (in m) for water surface types.
PA0393	data_output_pr = ... is not implemented for large_scale_forcing = .FALSE.	The listed entries in the parameter file under data_output_pr are only avialable for large_scale_forcing = .T..
PA0394	data_output_pr = ... is not implemented for nudging = .FALSE.	The listed entries in the parameter file under data_output_pr are only avialable for nudging = .T..
PA0395	zu(...) = ... m is higher than the maximum height in LSF_DATA which is ...m. Interpolation on PALM grid is not possible.	LSF_DATA has a maximum vertical height that is smaller than the vertical extent of the grid used in PALM. Hence, interpolation of the LSF_DATA onto the PALM grid is not possible. Reduce either the vertical extent of the PALM modeling domain or enlarge the LSF_DATA file correspondingly. Note: it is also possible that your file LSF_DATA is not formatted correctly and that there has been an error while reading it.
PA0396	The usage of use_subsidence_tendencies requires large_scale_subsidence = .T..	If use_subsidence_tendencies is used, subsidence tendencies for temperature and humidity are read in from the external file LSF_DATA. However, these tendencies can only be applied to the prognostic variables if large_scale_subsidence = .T..
PA0397	The usage of use_subsidence_tendencies requires large_scale_forcing = .T..	If use_subsidence_tendencies is used, subsidence tendencies for temperature and humidity are read in from the external file LSF_DATA. This requires large_scale_forcing = .T..
PA0398	run will be terminated because user forced a job finialization using a flag file: DO_STOP_NOW: "..." DO_RESTART_NOW: "..."	The user can force an unscheduled termination/restart of the running job by creating one of the flag files DO_STOP_NOW or DO_RESTART_NOW in the temporary directory of the job.
PA0399	lsm requires setting of bc_pt_b = "dirichlet" and bc_q_b = "dirichlet"	In case the land surface model (LSM) is used, the surface fluxes have to be calculated by means of surface values of potential temperature and humidity (that are provided by the LSM), which reflects setting dirichlet boundary conditions.
PA0400	lsm requires ...	When using the LSM it is required to use a constant_flux_layer and the radiation model.
PA0401	vegetation_type = 0 (user defined) requires setting of ...	In case a user-defined vegetation is used, all LSM parameters must be explicitly set by the user. See vegetation_type
PA0402	data_output_pr = ... is not implemented for land_surface = .FALSE.	The chosen quantity is related to the LSM, but the LSM was not activated.
PA0403	soil_type = 0 (user_defined) requires setting of ...	In case a user-defined soil type is used, all soil parameters must be explicitly set by the user. See soil_type
PA0404	output of ... requires land_surface = .TRUE. (or urban_surface = .TRUE.)	The requested output quantity is only available when using the LSM (or USM).
PA0405	unknown radiation_scheme = ...	For a list of available radiation schemes, see radiation_scheme.
PA0406	output of ... requires radiation = .TRUE. and radiation_scheme = "rrtmg"	The requested output quantity is only available when using the RRTMG radiation_scheme.
PA0407	radiation_scheme = "rrtmg" requires compilation of PALM with pre-processor directive -D_rrtmg	In order to use RRTMG, the radiation code must be installed as external (shared or static) library and PALM must be compiled with -D__rrtmg listed in the %cpp_options. For further details, see here
PA0408	data_output_pr = ... is not available for radiation = .FALSE. or radiation_scheme = "constant"	The desired output (here radiation fluxes) is only available for radiation_scheme = "clear-sky" or "rrtmg".
PA0409	output of ... requires radiation = .TRUE. and radiation_scheme = "rrtmg"	The desired output (here: surface albedos) is only available when using radiation_scheme = "rrtmg"
PA0410	radiation_scheme = "clear-sky" in combination with albedo_type = 0 requires setting of albedo /= 9999999.9'	The choice of a user-defined albedo requires manual setting of the albedo as there is no default value set. See radiation_scheme
PA0411	radiation_scheme = "rrtmg" in combination with albedo_type = 0 requires setting of albedo_lw_dif /= 9999999.9, albedo_lw_dir /= 9999999.9, albedo_sw_dif /= 9999999.9 and albedo_sw_dir /= 9999999.9	The choice of a user-defined albedo requires manual setting of all four albedos for direct/diffuse longwave/shortwave radiation as there is no default value set. See radiation_scheme
PA0412	radiation_scheme = "rrtmg" requires the use of NetCDF (preprocessor directive -D_netcdf'	The RRTMG library reads atmospheric profiles unsing NetCDF by default. Therefore NetCDf must be activated when using RRTMG.
PA0413	data_output_pr = "..." is not avalable for radiation = .FALSE. or radiation_scheme /= "rrtmg"	Radiative heating rates are only available when using the full RRTMG radiation scheme.
PA0414	nested child domain lower left corner [and upper right corner and height] must match its parent grid lines	nested child domain lower left corner (x,y) [and upper right corner (x,y) and top (z)] coordinates must match the parent grid lines, i.e. they must be integer divisible by the parent grid spacings in the respective coordinate direction
PA0415	water_type = 0 (user_defined) requires setting of z0_water /= 9999999.9'	If the water_type is set to be user-specific, it is essential to prescribe a roughness length for momentum (in m) for water surface types.
PA0416	nesting grid-spacing ratio ( parent dx / child dx [or dy or dz, respectively] ) must have an integer value [for each z-level]	Parent / child grid spacing ratios in each coordinate direction must be integer valued. This also implies that vertical grid stretching is not allowed in nested runs except in the root domain above the top level of the highest nest-domain
PA0417	illegal nesting mode: ...	Allowed values for nesting_mode are 'one-way', 'two-way' or 'vertical'.
PA0418	illegal nesting datatransfer mode: ...	Allowed values for nesting_datatransfer_mode are 'cascade', 'mixed' or 'overlap'.
PA0419	mismatch between root model and child settings: <parameter name>(root) = ... <parameter name>(child) = ... child value is set to root value	The displayed parameter has been assigned different values for the root domain and a child domain (the id of the child domain is listed in the first line of the message) but it must have the same value for all domains. PALM automatically adjusts the child domain value to the one given for the root domain. In order to get rid of this warning message, adjust the parameter in the respective NAMELIST-parameter file of the child (or root) domain.
PA0420	Number of agents exceeds agent dimension. Starting at time_since_reference_point = <time_since_reference_point> s, data may be missing. Number of agents: <out_noa> Agent dimension size: <dim_size_agtnum>	This is a result of the user manually setting either dim_size_agtnum_manual or dim_size_factor_agtnum or both, resulting in the agent-number dimension of DATA_AGT_NETCDF becoming smaller than the number of agents the MAS tries to ouput. Please adjust the parameters accordingly.
PA0421	Using synthetic turbulence generator requires random_generator = random-parallel.
PA0422	data_output_pr = ... is not available for cloud_scheme = saturation_adjust	If the output is not necessary, delete the variable from the namelist. If it is necessary, use cloud_scheme = kessler, seifert_beheng or morrison.
PA0423	output of "..." is not available for cloud_scheme = saturation_adjust	If the output is not necessary, delete the variable from the namelist. If it is necessary, use cloud_scheme = kessler or seifert_beheng.
PA0424	roughness_length must be smaller than dz/2	The roughness length has to be smaller than the constant flux layer, which is dz/2.
PA0425	nested child domain does not fit into its parent domain	A nest domain does not completely fit in its parent domain, or in case of vertical nesting mode, the horizontal boundaries of a nest domain do not exactly match the horizontal boundaries of its parent domain. In 3D-nesting mode, the vertical extent of the child must be smaller than that of the parent domain.
PA0426	nested parallel child domains overlap	Two or more parallel nest domains overlap each other in space. Parallel nest domains must never overlap.
PA0427	at least one dimension of lower left corner of one domain is not 0. All lower left corners were set to (0, 0)	In case of vertical nesting mode all domains must have lower left corner at x=0, y=0. If defined otherwise in PARIN, palm will reset it.
PA0428	bc_lr and bc_ns were set to cyclic for vertical nesting	In case of vertical nesting mode bc_lr and bc_ns must be cyclic for all domains. If defined otherwise in PARIN_*, palm will reset them.
PA0429	parent buffer too small ...	Error happens in PALM model coupler for the parent domain (palm/trunk/SOURCE/pmc_parent_mod.f90​): parent buffer too small. This should not happen. Please submit a trouble ticket.
PA0430	hole(s) resolved by only one grid point were filled	Topography was filtered, i.e. holes resolved by only one grid point are filled. These holes are suspected to possibly lead to a velocity blow-up. Moreover, continuity equation cannot be fulfilled in such holes on a discrete grid.
PA0431	Start x position is outside the model domain	Start position for virtual flight must be within the model domain.
PA0432	Start y position is outside the model domain	Start position for virtual flight must be within the model domain.
PA0433	Cyclic flight leg does not match lateral boundary condition	Virtual flights can only be in cyclic-mode if lateral model boundary are cyclic.
PA0434	Flight leg or parts of it are outside the model domain	End position must be within the model domain in case of return-legs.
PA0435	Unknown flight mode	leg_mode can either be 'cyclic' or 'return'.
PA0436	surface element at grid point (j,i) = ( ... ) is not a vegetation surface, so that information given in vegetation_pars is neglected.
PA0437	If topography information is provided (via Netcdf or ASCII input) topography = "read_from_file" is required.
PA0438	Flight level is outside the model domain	Flight level is above domain top or below 0.
PA0439	netcdf_data_format must be > 2	Data output for virtual flights has 4 unlimited dimensions - time, x-, y-, and z-position. Unfortunately, assignment of more than one unlimited dimension per NC file is only possible with NetCDF4 / HDF5. Adjust netcdf_data_format appropriately
PA0440	The usage of large scale forcing from external file LSF_DATA is not implemented for passive scalars	So far, large-scale forcing for passive scalars is not implemented.
PA0441	boundary condition: bc_s_t = "..." is not allowed with top_scalarflux /= 0.0'	You have tried to set both, a Dirichlet boundary condition for scalar at the top (with bc_s_t = 'dirichlet' ), or an initial-gradient boundary condition, and a scalar flux at the top (with top_scalarflux /= 0.0).
PA0442	bulk_cloud_model = .TRUE. is not allowed with cloud_droplets = .TRUE.	Either second-order moment adjustment scheme or Lagrangian cloud physics can be applied, not both at the same time
PA0443	wall_heatflux additionally requires setting of surface_heatflux	As wall_heatflux only describes the kinematic flux at topography walls at non-zero height levels, additional setting of surface_heatflux is required for the kinematic flux at the surface.
PA0444	wall_humidityflux additionally requires setting of surface_waterflux	As wall_humidityflux only describes the kinematic flux at topography walls at non-zero height levels, additional setting of surface_waterflux is required for the kinematic flux at the surface.
PA0445	wall_scalarflux additionally requires setting of surface_scalarflux	As wall_scalarflux only describes the kinematic flux at topography walls at non-zero height levels, additional setting of surface_scalarflux is required for the kinematic flux at the surface.
PA0446	unknown approximation: approximation = ...	This error message appears if the parameter approximation is not set to one of the allowed values 'boussinesq' or 'anelastic'.
PA0447	Anelastic approximation requires momentum_advec = "ws-scheme	The anelastic approximation requires: momentum_advec = 'ws-scheme'. Currently no other advection scheme is allowed with approximation = 'anelastic'.
PA0448	Anelastic approximation currently only supports: psolver = "poisfft", psolver = "sor" and psolver = "multigrid_noopt"	The anelastic approximation requires: psolver to be set to one of 'poisfft', 'sor' or 'multigrid_noopt'. Currently no other pressure solver is allowed with approximation = 'anelastic'.
PA0449	Anelastic approximation is not allowed with conserve_volume_flow = .TRUE.	The anelastic approximation is not allowed with: conserve_volume_flow = .TRUE.
PA0450	unknown flux input mode: flux_input_mode = ...	This error message appears if the parameter flux_input_mode is not set to one of the allowed values 'dynamic', 'kinematic' or 'approximation-specific'.
PA0451	unknown flux output mode: flux_output_mode = ...	This error message appears if the parameter flux_output_mode is not set to one of the allowed values 'dynamic', 'kinematic' or 'approximation-specific'.
PA0452	Soil type is out of the valid range	between 1 and 6
PA0453	incompatible integer arithmetic: ...	This error message appears if the compiler integer arithmetic is not compatible with the assumptions made for the parallel random number generator. If this is the case the internal checks that the kind value isp is in fact a 32-bit integer with the usual properties that we expect it to have (under negation and wrap-around addition) fail.
PA0454	problem in attempt to allocate memory	This error message appears if the parallel random number generator is not able to allocate sufficient memory.
PA0455	Tunnel width too small	tunnel_width_y - 2.0*tunnel_wall_depth must be > 2*dy
PA0456	Tunnel width too large	tunnel_width_y must be <= (ny+1)*dy
PA0457	The maximumn number of agents durin this run was <maximum_number_of_agents>. Consider adjusting the INPUT parameter dim_size_agtnum_manual accordingly for the next run.	This informative message is given at the end of every job that uses the Multi Agent System. In order to avoid unnecessarily large files, try to set dim_size_agtnum_manual as close to the maximum number of agents during the simulation.
PA0458	soil_moisture must not exceed its saturation value	This error can occur when the soil moisture is higher than the saturation moisture for the given vegetation type. Check and may adjust parameters saturation_moisture or soil_moisture.
PA0459	unknown aerosol type 'aero_type = ...'	Chose an appropriate value for aero_type.
PA0460	wrong settings for stokes_wavelength and/or stokes_waveheight	If you set parameters stokes_wavelength and stokes_waveheight to switch on the Stokes force in ocean mode, they must both be set > 0.0. Values < 0.0 are not allowed.
PA0461	pitch_control = .TRUE. requires speed_control = .TRUE.	Self-explanatory. See pitch_control and speed_control.
PA0462	omega_rot < 0.0, Please set omega_rot to a value larger than or equal to zero	Self-explanatory. See omega_rot.
PA0463	rcx, rcy, rcz have to be given for each turbine.	The position of each turbine has to be specified. See rcx, rcy and rcz.
PA0464	file WTM_DATA does not exist	Make sure that the file WTM_DATA containing physical characteristics of the blades, as described in example_wtm.txt, is provided in the INPUT folder of the respective run on the host where the job is running.
PA0465	surface_type = netcdf requires static input file.	Either provide the file PIDS_STATIC or change the value of surface_type to a value different than netcdf.
PA0466	wrong component of wave breaking: ...	Only the two Cartesian components 1 and 2 are allowed for adding wave breaking effects in ocean mode.
PA0467	y_shift /= 0 is only allowed for cyclic boundary conditions in both directions	y_shift defines a shift in the cyclic boundary conditions. It can therefore only be used with cyclic boundary conditions. See y_shift.
PA0468	y_shift /= 0 is only allowed for multigrid pressure solvers	y_shift defines a shift in the cyclic boundary conditions. The data then becomes not truly cyclic anymore. Therefore, the fft pressure solver is no longer viable. See y_shift.
PA0469	unknown aerosol species for bulk microphysics	aerosol species must be set to a known type. See aerosol_bulk.
PA0470	unknown aerosol species for lagrangian cloud microphysics	aerosol species must be set to a known type. See aero_species.
PA0471	number of soil layers (...) does not match to the number of layers specified in soil_temperature (...)	For each soil layer an initial soil temperature must be prescribed (see soil_temperature). The number of soil layers is defined by dz_soil.
PA0472	deep_soil_temperature is not set but must be /= 9999999.9	Since r2729 the deep_soil_temperature is no longer part of the soil_temperature array and must be specific separately. The deep soil temperature serves as bottom boundary condition for heat diffusion in the soil model. Note that there is no analogous value for soil moisture as the bottom of the soil can either be set to bedrock (water accumulates) or free drainage (water is lost).
PA0473	Vertical grid stretching is not allowed for complex_terrain = .T.	Self-explanatory. See complex_terrain and dz_stretch_level.
PA0474	pavement_type = 0 (user_defined) requires setting of pavement_depth_level /= 0	When a user-defined pavement is prescribed, a depth must be asigned that determines how deep the pavement extends into the ground. The pavement heat capacity and pavement heat conductivty are then asigned to all those levels.
PA0475	Particle violated CFL-criterion: particle with id ... will be deleted!	This is a warning that some of your particles moves too fast. Therefore they will be deleted.
PA0476	Humidity has to be set to .T. in the _p3d file for coupled runs between ocean and atmosphere.	Set humidity = .T. in the _p3d.
PA0477	In Child model: bc_par_t is automatically set to nested	This is a warning that bc_par_t is automatically set to nested although a different boundary condition was specified. Set bc_par_t = 'nested' in the child _p3d_NXX.
PA0478	In Child model: bc_par_lr is automatically set to nested	This is a warning that bc_par_lr is automatically set to nested although a different boundary condition was specified.. Set bc_par_lr = 'nested' in the child _p3d_NXX.
PA0479	In Child model: bc_par_ns is automatically set to nested	This is a warning that bc_par_ns is automatically set to nested although a different boundary condition was specified. Set bc_par_ns = 'nested' in the child _p3d_NXX.
PA0480	RMA window too small on child	If particles pass the borders between the child and parent domain they will be exchanged using MPI windows (MPI window = memory that is made accessible to accesses by remote processes for one sided communication). Within this process it could happen that the size of the windows is too small due to a very large number of particles that need to be transferred between the domains. Either choose a smaller amount of particles or change the internal limit of max_nr_particle_in_rma_win from 100000 to a higher value.
PA0481	RMA window too small on parent	If particles pass the borders between the child and parent domain they will be exchanged using MPI windows (MPI window = memory that is made accessible to accesses by remote processes for one sided communication). Within this process it could happen that the size of the windows is too small due to a very large number of particles that need to be transferred between the domains. Either choose a smaller amount of particles or change the internal limit of max_nr_particle_in_rma_win from 100000 to a higher value.
PA0482	Version of binary SVF file "..." does not match the version of model "..."	This error occurs when radiation data from the file SVFIN is read and the precursor run was carried out with a different svf binary version than the main run. Repeat the precurser with the current version or carry out the main run with the same version as the precursor. You can check the svf binary version number which is required for the main run in radiation_model_mod.f90​.
PA0483	Wrong number of SVF or CSF	This error can happen if svf data is read from file SVFIN (e.g. during manual restarts). The local number of sky view factors and canopy sink factors for calculating surface reflection of radiation has to be the same between the precursor run and the main run. Be sure that you create the svf binary data with the same version as the version of the main run.
PA0484	The lowest level where vertical stretching is applied have to be greater than ...	The wind turbine model implemented in PALM does not consider a stretched grid. Therefore grid stretching should only be applied well above the region where the wind turbine model is active. Please adjust dz_stretch_level_start accordingly.
PA0485	dissipation_1d = "as_in_3d_model" requires mixing_length_1d = "as_in_3d_model"	The dissipation rate in the TKE equation of the 1d-model can be calculated the same way as in the 3D model only if the mixing_length is also calculated as in the 3D model.
PA0486	Usage of radiation module is only allowed if land-surface and/or urban-surface model is applied.	Either the namelist &land_surface_parameters has to be set in the _p3d file or &urban_surface_parameters (or both) to avoid this error.
PA0487	data_output_pr = ... is currently not implemented. Please output resolved- and subgrid-scale fluxes individually to obtain the total flux.
PA0488	ERROR: the surface type ... is not supported for calculating SVF	Allowed surface types are 0, 2, 3, 4, 5, 6, 7, 8, 9, 10. Their meaning can be identified in radiation_model_mod.f90​. This error should not occur. Please submit a trouble ticket.
PA0489	In case of nesting, spinup_time and dt_spinup must be identical in all parent and child domains.	In case of spinup and nested run, the spinup end time must be identical in order to have synchronously running simulations. Adjust spinup_time and/or dt_spinup in your steering files appropriately.
PA0490	nsurfl from SVF file does not match calculated nsurfl from radiation_interaction_init.	Number of all local surface elements in sky-view factor file (SVFIN) does not match the calculated number of local surface elements. Be sure that you created the svf binary data with the same version as the version of the main run and that you did not introduce further surfaces in the meantime. Otherwise submit a trouble ticket.
PA0491	A different number of processors between the run that has written the svf data and the one that will read it is not allowed.	Self-explanatory.
PA0492	initializing_actions = "..." has been changed to 'set_constant_profiles' in child domain.	This is an informative message. In a nested run, only 'read_restart_data' (in case of a restart) or 'set_constant_profiles' are allowed for initializing_actions in child domain even though the constant-profiles initializations for the prognostic variables will be overwritten by pmci_child_initialize and pmci_parent_initialize. This is, however, important e.g. to make sure that diagnostic variables are set properly. An exception is made in case of restart runs and if user decides to do everything by its own.
PA0493	npcbl from SVF file does not match calculated npcbl from radiation_interaction_init	The number of the local plant canopy gridboxes in SVFIN does not match the one which is calculated during model initialization. Be sure that you created the svf binary data with the same version as the version of the main run. Otherwise submit a trouble ticket.
PA0494	ndsidir from SVF file does not match calculated ndsidir from radiation_presimulate_solar_pos	The number of apparent solar directions in SVFIN does not match the one which is calculated during model initialization. Be sure that you created the svf binary data with the same version as the version of the main run. Otherwise submit a trouble ticket.
PA0495	optimized multigrid method requires nz to be even	You are using the optimized multigrid method, which requires nz to have an even value. Change nz in your parameter file, or choose psolver = 'multigrid_noopt' (but be aware that with an uneven value of nz the multigrid solver can only use one grid level, so you will have no multi grid levels at all and hence convergence will be very low!).
PA0496	The lowest level where vertical stretching is applied have to be greater than ...	The radiation model does not consider a stretched grid. The assumption of a uniform grid is necessary in parts below the top layer of urban surface (index height nzut). Please adjust dz_stretch_level_start accordingly.
PA0497	constant_heatflux = .TRUE. is not allowed with pt_surface_heating_rate (/=0) = ...
PA0498	bc_lr and/or bc_ns in the prerun was set /= "cyclic"	In case of initializing_actions = 'cyclic_fill', the prerun must use cyclic boundary conditions along x and y. Check settings of bc_lr / bc_ns in your prerun parameter file.
PA0500	Unknown turbulence closure: ...	The variable turbulence_closure has an unknown value.
PA0501	turbulent inflow/outflow is not yet implemented for RANS mode	Setting turbulent_inflow or turbulent_outflow is not allowed in RANS mode (see namelist parameter turbulence_closure to switch between LES/RANS mode).
PA0502
PA0503	z0 exceeds surface-layer height at horizontal/vertical natural/urban surface and is decreased appropriately	In PALM, Monin-Obukhov similarity is assumed between the surface and the first computational grid point normal to the surface. Because of the staggered grid, the distance between these two points is half of the grid spacing in the respective direction, i.e. dz/2 in vertical direction. The height z = dz/2 defines the top of the (analytical) logarithmic layer zs, which is called the surface layer height here. Now functions like ln(zs/z0), where z0 is the roughness length, are used to calculate characteristic surface layer variables like u* or theta*. This mathematically requires that zs > z0, or in other words, that z0 < dz/2. In case you have run into this error, you either need to reduce the roughness length z0 or increase the grid spacing dz. Attention: This message is given only once (for the first grid point where the exceedance has been detected). Be aware that there might be more grid points where z0 exceeds the surface-layer height.
PA0504	A mixture of different LOD for the provided boundary data is not possible.	In case of mesoscale nesting (see nesting_offline) the boundary data can be provided as level-of-detail (LOD) 1 or as LOD 2. However, a mixture of both in one simulation is not possible.
PA0505	unknown boundary condition: bc_cs_l "..."	See parameter bc_cs_l for allowed values, and appropriately correct your parameter file.
PA0506	illegal Rosenbrock-solver type	See chemistry parameter icntrl . The value of icntrl(3) must be in range 0 < inctrl(3) < 7. Please correct your parameter file appropriately.
PA0507	z0h exceeds surface-layer height at horizontal/vertical natural/urban surface and is decreased appropriately	See error PA0503 for detailed explanation.
PA0508	z0 exceeds surface-layer height at sea surface and is decreased appropriately	See error PA0503 for detailed explanation.
PA0509	salinityflux must not be set for ocean run without salinity	You have set parameters top_salinityflux or/and bottom_salinityflux to a non-zero value, and simulataneously switched off the salinity equation. Remove either the flux settings from your parameter file, or set salinity = .TRUE.
PA0510	ocean mode not allowed for nesting	Nesting is not available for the ocean mode.
PA0511	ocean mode does not allow cyclic-fill initialization	Main runs with initializing_actions = 'cyclic_fill' cannot use ocean mode so far.
PA0512	output of "..." requires uv_exposure = .TRUE. in namelist "biometeorology_parameters"	To output the requested variable, the UV exposure calculation must be switched on which is part of the biometeorology module. See the UVEM documentation for more details.
PA0513	uv_exposure = .TRUE. but input file "PIDS_UVEM" is not present. Calculating UV exposure impossible.	The UV exposure calculation requires an additional input file which is not given. See the UVEM documentation for more details.
PA0514	uv_exposure = .TRUE. but one or more required input varaibles are not present in file "PIDS_UVEM". Calculating UV exposure impossible.	The UV exposure calculation requires special input variables given in the input file PIDS_UVEM. See the UVEM documentation for more details.
PA0515	consider_obstructions = .TRUE. but varaible "obstruction" is not present in file "PIDS_UVEM". Calculating UV exposure impossible.	To consider obstruction, e.g. by buildings, for UV exposure, the obstruction must be pre-calculated for each grid point and be provided within the input file PIDS_UVEM. See the UVEM documentation for more details.
PA0516	Required input file "<filename>" does not exist!	A required netCDF file is not available. Either this file is not given in your INPUT folder or has a wrong name (check the .palm.iofiles file for the correct naming).
PA0517	Chemical reactions: ON/OFF
PA0518	Sub-time-steps are skipped for chemistry time-steps
PA0519	If building_type is provided, also building_id is required
PA0520	Synthetic turbulence generator is required if offline nesting is applied and PALM operates in LES mode.	In order to trigger turbulence, synthetic turbulence need to be imposed at the lateral boundaries, else very larger adjustment zones in the order of O(10 km) are required.
PA0522	Chemistry is calculated at all meteorology time-step
PA0523	Incorrect photolysis scheme selected, please check spelling
PA0524	Synthetic turbulence generator is required when nesting is applied and parent operates in RANS-mode but current child in LES mode.
PA0526	Vegetation type is out of the valid range	between 1 and 18
PA0527	Pavement type is out of the valid range	between 1 and 15
PA0528	Water type is out of the valid range	between 1 and 5
PA0529	Building type is out of the valid range	between 1 and 7
PA0531	error opening file PLANT_CANOPY_DATA_3D	ASCII file for reading plant-canopy information is not available. This message is triggered if canopy_mode = 'read_from_file' is switched-on. With this setting, PALM searches for canopy information in the static input file first. If this is not available, PALM tries to open an ASCII file for plant-canopy information. This file has not been provided in the respective INPUT folder.
PA0531	error reading file PLANT_CANOPY_DATA_3D	Mis-configured ASCII file
PA0533	If virtual measurements are taken, a setup input file is required
PA0534	If virtual measurements are taken, a static input file is required
PA0535	Attribue featureType = ... is not allowed.	only 'timeseries', 'timeseriesProfile', or 'trajectory' is allowed.
PA0536	averaging_interval_surf must be <= dt_dosurf_av
PA0537	Variable is not yet implemented in the surface output
PA0538	Variable is not part of the surface output
PA0539	Output of surface data is not given at t= ' ' because the maximum number of output time levels is exceeded.	see e.g. PA0384 for more explanation on this
PA0540	NetCDF attribute lod is not set properly for buildings_2d.	only LoD = 1 possible
PA0541	NetCDF attribute lod is not set properly for buildings_2d.	only LoD = 2 possible
PA0542	If building heigths are prescribed in static input file, also an ID is required.
PA0543	Number of inifor vertical grid points does not match the number of numeric grid points.	Dimensions in dynamic input file must match the dimension of prognostic grid points for the respective variable.
PA0544	Missing initial data for ...	Data is missing in dynamic input file.
PA0545	NetCDF input for ... must not contain any _FillValues	Data is dynamic input file must not contain any _FillValues.
PA0546	nesting_offline = .TRUE. requires dynamic input file
PA0547	initializing_actions = 'inifor' requires dynamic requires dynamic input file
PA0548	Static input file: horizontal dimension in x- and/or y-direction do not match the respective model dimension
PA0549	Static input file: horizontal grid spacing in x- and/or y-direction do not match the respective model dimension
PA0550	NetCDF variable zt is not allowed to have missing data
PA0551	Incorrect chemistry mechanism selected, check spelling in namelist and/or chem_gasphase_mod
PA0552	Reading 3D building data - too much data points along the vertical coordinate
PA0553	Reading 3D building data - vertical coordinate do not match numeric grid	The z-dimension in the static input file needs to match with the vertical numerical grid of the scalar grid points (center of the grid volume). The vertical grid for 3D buildings starts at the surface, i.e. at z=0.
PA0554	Minimum requirement for surface classification is not fulfilled. At least vegetation_type, pavement_type, soil_type and water_type are required. If urban-surface model is applied, also building_type ist required
PA0555	If vegetation_type = 0 at any location, vegetation_pars is required
PA0556	If vegetation_type = 0 at any location, root_area_dens_s is required
PA0557	If soil_type = 0 at any location, soil_pars is required
PA0558	If building_type = 0 at any location, building_pars is required
PA0559	If albedo_type = 0 at any location, albedo_pars is required
PA0560	If pavement_type = 0 at any location, pavement_pars is required
PA0561	If pavement_type = 0 at any location, pavement_subsurface_pars is required
PA0562	If water_type = 0 at any location, water_pars is required
PA0563	At least one of the parameters vegetation_type, pavement_type, building_type, or water_type must be set to a non-missing value. Grid point:	If the land-surface and building-surface model is employed at least one of the "_type" must be set to classify the surfaces accordingly.
PA0564	soil_type is required for each location (y,x) where vegetation_type or pavement_type is a non-missing value
PA0565	More than one surface type (vegetation, pavement, water) is given at a location. Please note, this is not possible at the moment as no tile approach has been yet implemented. (i,j) =
PA0566	The sum of all land-surface fractions must equal 1.
PA0567	Mismatch in setting of surface_fraction. Vegetation-, pavement-, or water surface is given at (i,j) = ( , ), but surface fraction is 0 for the given type
PA0568	Mismatch in setting of surface_fraction. Vegetation-, pavement-, or water surface is not given at (i,j) = ( , ), but surface fraction is not 0 for the given type.
PA0569	If vegetation_type(y,x) = 0, all parameters of vegetation_pars at this location must be set
PA0570	If vegetation_type(y,x) = 0, all levels of root_area_dens_s must be set at this location
PA0571	If soil_type(y,x) = 0, all levels of soil_pars at this location must be set
PA0572	If building_type(y,x) = 0, all parameters of building_pars at this location must be set
PA0573	Each location where a building is set requires a type ( and vice versa ) in case the urban-surface model is applied. i, j = ( , )
PA0574	Each location where a building is set requires an ID ( and vice versa ). i, j = ( , )
PA0575	Each building grid point requires an ID.
PA0576	If albedo_type(y,x) = 0, all parameters of albedo_pars at this location must be set
PA0577	If pavement_type(y,x) = 0, all parameters of pavement_pars at this location must be set
PA0578	If pavement_type(y,x) = 0, all parameters of pavement_subsurface_pars at this location must be set
PA0579	If water_type(y,x) = 0, all parameters of water_pars at this location must be set
PA0580	nsurface_fraction must not be larger than 3.
PA0581	If buildings are provided, also building_type is required.
PA0582	If buildings are provided, also building_id is required.
PA0585	The number of cores has been changed between restart runs. This is not allowed when surface data output is used.
PA0586	For chemistry variables only LOD=1 is allowed.	Initialization of chemistry via dynamic input file is only allowed with profiles (LOD=1).
PA0587	Child subdomain width in x[or y]-direction must not be smaller than its parent grid dx[or dy]. Change the PE-grid setting (npex, npey) to satisfy this requirement.	In nested runs child domain decomposition must be such that the subdomain size is never smaller than the parent grid-spacing in the respective direction.
PA0589	bc_lr = "..." and bc_ns = "..." are not allowed to be set at the same time	Dirichlet/radiation boundary conditions are only allowed to be set along x or along y. Cyclic conditions must be set along the respective other direction. If you like to set non-cyclic conditions along x and y you need to use the offline-nesting feature.
PA0560	In case of radiation scheme ='rrtmg' and the use of cloud droplets average radiation is not implemented
PA0591	dt_radiation must be > 0.0
PA0593	unknown boundary condition: bc_cs_b = "..."
PA0594	salsa = .T. is not allowed with humidity = .F.	Applying the salsa module requires running PALM in humid mode. See parameter humidity.
PA0595	unknown boundary condition: bc_aer_b = "..."	See parameter bc_aer_b for allowed values, and appropriately correct your parameter file.
PA0596	unknown boundary condition: bc_aer_t = "..."	See parameter bc_aer_t for allowed values, and appropriately correct your parameter file.
PA0597	unknown nj3 (must be 1-3)	See parameter nj3 for allowed values, and appropriately correct your parameter file.
PA0598	salsa_emission_mode /= "no_emission" for requires bc_aer_b = "Neumann"	If aerosol surface emissions are given, a Neumann boundary condition should be set at the bottom. See parameter bc_aer_b for allowed values, and appropriately correct your parameter file.
PA0599	SALSA is run together with chemistry but not all gaseous components are provided by kpp (H2SO4, HNO3, NH3, OCNV, OCSC).	Some gaseous compound(s) needed in the aerosol module SALSA are missing from the chemical mechanism applied. Check the chem_gashase_mod.f90.
PA0600	Unknown aerosol species/component(s) given in the initialization	Unknown chemical components included in the parameter file. See parameter listspec for allowed components.
PA0601	Number of inifor horizontal grid points does not match the number of numeric grid points.	Dimensions in dynamic input file must match the dimension of prognostic grid points for the respective variable.
PA0602	None of the aerosol chemical components in PIDS_DYNAMIC... correspond to ones applied in SALSA.	If the initial aerosol concentrations are read from the dynamic input file (parameter isdtyp = 1), the chemical composition must include at least one chemical component applied in the model.
PA0603	Currently only lod=1 accepted for init_atmosphere_aerosol	Initialization of the aerosol module via dynamic input file is only allowed with profiles (LOD=1).
PA0604	The number of size bins in init_atmosphere_aerosol does not match with that applied in the model set-up	The number of aerosol size bins in the dynamic input file does not correspond to the size distribution information given in the parameter file. See parameters nbin and reglim, and appropriately correct the discrepancy.
PA0605	Mean diameters of the aerosol size bins in PIDS_DYNAMIC... do not match with the sectional representation of the model.	The mean diameters of the aerosol size bins in the dynamic input file does not correspond to the size distribution information given in the parameter file. See parameters [wik:doc/app/salsa_parameters#nbin nbin] and reglim, and appropriately correct the discrepancy.
PA0606	Error in initialising mass fractions of chemical components. Check that all chemical components are included in parameter file!	The chemical composition in the dynamic input file does not overlap with the one applied in the model. See parameter listspec for allowed components.
PA0607	Input file PIDS_DYNAMIC... for SALSA missing!	The initial aerosol size distribution is set to be read from the dynamic input file (parameter isdtyp = 1) but the file <run_identifier>_dynamic is missing.
PA0608	isdtyp = 1 but preprocessor directive netcdf is not used in complicing!	You have set isdtyp = 1, but netcdf-code has not been activated by the corresponding cpp-preprocessor switch. Add '-D__netcdf' to the %cpp_options line in the configuration file and re-compile (i.e. call palmbuild.
PA0609	Number of inifor horizontal grid points does not match the number of numeric grid points.	Dimensions in dynamic input file must match the dimension of prognostic grid points for the respective variable.
PA0610	Input file PIDS_DYNAMIC... for SALSA missing!	The initial aerosol size distribution is set to be read from the dynamic input file (parameter isdtyp = 1) but the file <run_identifier>_dynamic is missing.
PA0611	igctyp = 1 but preprocessor directive netcdf is not used in complicing!	You have set igctyp = 1, but netcdf-code has not been activated by the corresponding cpp-preprocessor switch. Add '-D__netcdf' to the %cpp_options line in the configuration file and re-compile (i.e. call palmbuild.
PA0612	Either OC or SO4 must be active for aerosol region 1a!	Either organic carbon (OC) or sulphates (SO4) have to be included as aerosol chemical components in parameter listspec. Correct your parameter file.
PA0613	depo_pcm_type not set correctly.	See depo_pcm_type. Correct your parameter file.
PA0614	No vegetation type defined.	The land surface model is applied, but vegetation type needed for the dry deposition is not defined. Check the static input file.
PA0615	No pavement type defined.	The land surface model is applied, but pavement type needed for the dry deposition is not defined. Check the static input file.
PA0616	No water type defined.	The land surface model is applied, but water type needed for the dry deposition is not defined. Check the static input file.
PA0617	Subrange 1: no convergence!	The solution of the equilibrium subroutine does not converge for the subrange 1. This might be due to some error in initialising the aerosol mass concentrations.
PA0618	Subrange 2: no convergence!	The solution of the equilibrium subroutine does not converge for the subrange 2. This might be due to some error in initialising the aerosol mass concentrations.
PA0619	Horizontal / Vertical surface element at grid point i, j = ..., is neither a vegetation, pavement, nor a water surface.	The respective surface element is not correctly initialized, indicating inconsistencies in the static input file
PA0620	Using synthetic turbulence generator is not allowed in LES-LES nesting.
PA0621	Using synthetic turbulence generator is not allowed in RANS-RANS nesting
PA0622	Offline nesting is only applicable in root model
PA0623	Invalid output value: nucleation rate > 106 1/cm3s	Calculated nucleation rate in the subroutine for ternary nucleation (ternucl) exceeds 1e6 cm-3s-1.
PA0624	error: zvfrac < 0	When updating the aerosol size distribution after aerosol processes, the volume fraction of aerosols to be moved to the larger bin has gone negative.
PA0625	Error: Aerosol bin update not converged	When updating the aerosol size distribution after aerosol processes, the solution does not converge.
PA0626	unknown boundary condition: bc_aer_l "..."	See parameter [wik:doc/app/salsa_parameters#bc_aer_l bc_aer_l] for allowed values, and appropriately correct your parameter file.
PA0627	unknown boundary condition: bc_aer_r "..."	See parameter bc_aer_r for allowed values, and appropriately correct your parameter file.
PA0628	Error in itype!	The input parameter in bin_mixrat is falsely set. Review the code.
PA0629	Input file PIDS_SALSA... missing!	Emission information for the aerosol particles is set to be read from a NetCDF input file (salsa_emission_mode == 'read_from_file'), but the file <run_identifier>_salsa is missing.
PA0630	None of the aerosol chemical components in PIDS_SALSA... correspond to ones applied in SALSA.	If the aerosol emissions are read from <run_identifier>_salsa (parameter salsa_emission_mode == 'read_from_file'), the chemical composition must include at least one chemical component applied in the model.
PA0631	unknown unit for aerosol emissions: ... (lod1)	Aerosol emission values given in the NetCDF input file <run_identifier>_salsa are incorrect when lod=1 is applied. Aerosol emissions are given as total particulate mass concentrations per emission category and should be given in units: kg/m2/yr or g/m2/yr.
PA0632	None of the emission categories in PIDS_SALSA... match with the ones in the model.	Emission categories in <run_identifier>_salsa do not match with ones applied in the model ('traffic exhaust', 'road dust', 'wood combustion', 'other').
PA0633	emission_time_factors should be given for each nhoursyear OR nmonthdayhour	Emission time factors for aerosol emissions (LOD=1) are not given or they are not correctly named in <run_identifier>_salsa.
PA0634	unknown unit for aerosol emissions: ...	Aerosol emission values given in the NetCDF input file <run_identifier>_salsa are incorrect when lod=2 is applied. Aerosol emissions are given as number emission per aersol size bin and should be given in units: #/m2/s.
PA0635	The number of size bins in aerosol input data does not match with that applied in the model set-up	The number of aerosol size bins in <run_identifier>_salsa does not correspond to the size distribution information given in the parameter file. See parameters nbin and reglim, and appropriately correct the discrepancy.
PA0636	Mean diameters of the aerosol size bins in PIDS_SALSA... do not mmatch with the ones in the model.	The mean diameters of the aerosol size bins in <run_identifier>_salsa does not correspond to the size distribution information given in the parameter file. See parameters nbin and reglim, and appropriately correct the discrepancy.
PA0637	Unknown lod for aerosol_emission_values.	The level of detail (LOD) for aerosol_emission_values in <run_identifier>_salsa should be either 1 or 2.
PA0638	salsa_emission_mode = "read_from_file", but preprocessor directive netcdf is not used in compiling!	You have set salsa_emission_mode = "read_from_file", but netcdf-code has not been activated by the corresponding cpp-preprocessor switch. Add '-D__netcdf' to the %cpp_options line in the configuration file and re-compile (i.e. call palmbuild.
PA0639	unknown salsa_emission_mode: ...	The parameter salsa_emission_mode is not correctly set.
PA0640	Input file PIDS_CHEM... missing!	Emission information for SALSA is set to be read from a NetCDF input file (salsa_emission_mode == 'read_from_file'), but the file <run_identifier>_chemistry is missing. The chemistry module is not applied and therefore gaseous emissions are read in within salsa_mod.f90.
PA0641	emission_time_factors should be given for each nhoursyear OR nmonthdayhour	Emission time factors for gaseous emissions (LOD=1) are not given or they are not correctly named in <run_identifier>_chemistry.
PA0642	Unknown lod for emission_values.	The level of detail (LOD) for emission_values (gaseous emissions) in <run_identifier>_chemistry should be either 1 or 2.
PA0643	salsa_emission_mode = "read_from_file", but preprocessor directive netcdf is not used in compiling!	You have set salsa_emission_mode = "read_from_file", but netcdf-code has not been activated by the corresponding cpp-preprocessor switch. Add '-D__netcdf' to the %cpp_options line in the configuration file and re-compile (i.e. call palmbuild.
PA0644	unknown unit for gaseous emissions: ...	Unknown units applied for the gaseous emissions in the NetCDF input file <run_identifier>_chemistry. Units should be: #/m2/s or g/m2/s or ppm/m2/s or mumol/m2/s or kg/m2/yr or g/m2/yr Note that gases are not imported to SALSA from the chemistry module since the chemistry module is not applied!
PA0645	surface element at grid point (j,i) = ( ... ) is not a water surface, so that information given in water_pars is neglected.
PA0646	rad_sw_in / rad_lw_in / rad_sw_in_dif has no valid lod attribute
PA0647	surface element at grid point (j,i) = ( ... ) is not a pavement surface, so that information given in pavement_pars is neglected.
PA0648	No grid coarsening possible, multigrid approach effectively reduces to a Gauss-Seidel scheme.	The convergence of the pressure solver might be insufficient and the simulation can become unstable. You should try to adjust the number of subdomain grid points in a way that each of (nx+1)/npex, (ny+1)/npey, and nz contain power-of-two (2n) factors with at least n = 2 or larger. Be aware that you can change both, the total number of gridpoints of the total domain, and/or the number of PEs. Alternatively, in case that you cannot change your grid or virtual processor grid, you may try to increase the number of Gauss-Seidel iterations (ngsrb) to improve convergence, but this approach is very limited.
PA0649	Invalid input value: prh	Relative humidity given to the subroutine for ternary nucleation (ternucl) is not within the allowed humidity range of 5-95 %.
PA0650	Invalid input value: pc_sa	Number concentration of gaseous sulphuric acid given to the subroutine for ternary nucleation (ternucl) is not within the allowed range of 1e4-1e9 cm-3.
PA0651	Invalid input value: pc_nh3	Mixing ratio of gaseous ammonia given to the subroutine for ternary nucleation (ternucl) is not within the allowed range of 0.1-100 ppt.
PA0652	Child domain too narrow [or shallow] for anterpolation in x- [or y- or z-]direction	In case of nesting_mode = 'two-way', the child domain must cover a sufficient number of parent-grid cells in all directions. Otherwise anterpolation is not possible. The absolute minimum number of parent-grid cells covered in x- and y-directions is 3 + 2*anterpolation_buffer_width, and 2 + anterpolation_buffer_width in z-direction. However, it is recommended that child domains cover much larger number of parent-grid cells. This error message is only given if nesting_mode = 'two-way'.
PA0653	Anterpolation_buffer_width value too high, reset to 0	In case of a marginally small child domain (see PA0652 above), the user is warned and anterpolation_buffer_width is set to 0 (the default value is 2) so that the minimum criteria (see PA0652 above) for the child domain size in terms of the number of parent-grid cells covered are satisfied. However, it is recommended that child domains cover much larger number of parent-grid cells. This warning is only given if nesting_mode = 'two-way'.
PA0654	Anterpolation_buffer_width value too high, reset to the default value 2	In case of too wide anterpolation buffer, the user is informed and anterpolation_buffer_width is reset to its default value 2 so that the minimum criteria (see PA0652 above) for the child domain size in terms of the number of parent-grid cells covered are satisfied. However, it is recommended that child domains cover much larger number of parent-grid cells. This informative message is only given if nesting_mode = 'two-way'.
PA0655	Multiple calls to palm_date_time_set detected. date and time must be set only once.	Routine palm_date_time_set was called multiple times. Please remove any additional calls to this routine from your user code.
PA0656	Date and time are not set yet. Reset not possible.	palm_date_time_reset was called before palm_date_time_set which is not allowed.
PA0657	Date and time are not set yet. Returning date/time information not possible.	palm_date_time_get was called before palm_date_time_set which is not allowed.
PA0658	Date given in wrong format: "..." = ... is invalid! Check format of date_init. Format must be "YYYY-MM-DD hh:mm:ss (+-)hh".	An invalid date and/or time was detected. Please check the value and format of date_init.
PA0659	subrgrid scale velocities in combination with simple interpolation method is not implemented for passive particles	Set use_sgs_for_particles to FALSE or if you want to keep it set particle_interpolation to 'trilinear'
PA0661	namelist file "PARIN" or "PARIN_O" not found! Please have a look at the online description of the error message for further hints.	The origin of this error can have several reasons. Most likely, the activation string of the palmrun command was incorrect. You have to assure that the correct activation string is set so that the parameter namelist is recognised by palmrun (per default, this is 'd3#' for normal runs or 'd3r' for restarts). If you use several strings within the list of activation strings, make sure that each string is separated by a blank, i.e. do not write 'd3#restart' but 'd3# restart'. If you used a modified version of .palm.iofiles, there is probably an incorrect linkage between the PARIN file and the actual file inside the INPUT directory. Please refer to the documentation of palm_iofiles for how to correctly configure this file.
PA0662	no output file type selected for surface-data output! Set at least either "to_vtk" or "to_netcdf" to .TRUE.	Surface-data output was requested without specifying a file type to store the data in. When requesting surface-data output, either 'to_vtk' or 'to_netcdf' or both must be set to true.
PA0663	The maxima of the standard deviation remain at the open edges of the model	The maxima of the standard deviation of u, v, w, pt or q remain at the open edges of the model (look vdi_internal_controls.f90).
PA0664	The maxima of the standard deviation travel from the open edges into the interior of the domain with increasing simulation time	The maxima of the standard deviation of u, v, w, pt or q travel into the interior of the domain. Run does not fulfill VDI 3783 Part 9.
PA0665	Monotonic decrease or increase with increasing simulation time for u/v/w/pt/q	The mean of u, v, w, pt or q decrease or increase in the last 90 % of time in the simulation. Maybe your simulation time is too short or there is a physical cause for this.
PA0666	The mass is not conserved	conservation of mass is not fulfilled (look vdi_internal_controls)
PA0667	A wind component have a magnitude greater than ten times the maximum wind velocity at the approach flow profile	The u, v or w component of the wind exceed a specified limit (vdi_internal_controls).
PA0668	The potential temperature does not lie between 220 K and 330 K.	pt exceed a specified limit (vdi_internal_controls).
PA0669	2-delta t waves are generated	The u component at a control grid point or the means of the meteorological variables exhibit 2 delta t waves (vdi_internal_controls).
PA0670	External radiation with lod = 2 is currently not possible with average_radiation = .T..
PA0671	For non-pavement surfaces the combination of lai = 0.0 and c_veg = 1.0 is not allowed.
PA0672	Wind turbine model output requires NetCDF version 4. No output file will be created.	Data output for the wind turbine model is realized only for NetCDF version 4. As a consequence the model output is deactivated if version 3 is used.
PA0673	External radiation input should have the same lod.
PA0674
PA0675	unknown boundary condition: bc_c_t = "..."
PA0676	surface_fraction is given for more than one type. Please note, this is not possible at the moment as no tile approach has yet been implemented. (i, j) =
PA0677	No reference date-time defined. Returning date-time information is not possible. Either specify reference_date_time_str or set a reference via set_reference_date_time.	Routine get_date_time is either called without specifying any reference time (neither in the call itself nor via set_reference_date_time). Please check your user code for any calls to get_date_time. If you did not use any user code, please report this error via the ticket system.
PA0678	Error while converting date-time string. Please check format of date-time string: "...". Format must be "YYYY-MM-DD hh:mm:ss ZZZ".	The date-time information given in origin_date_time is given in a wrong format. Please check the format of the string.
PA0679	Date-time values out of bounds: "..." is out of bounds. Please check date-time string: "...". Format must be "YYYY-MM-DD hh:mm:ss ZZZ".	The date-time information given in origin_date_time has invalid values for the specified date or time component. Please check the setting of origin_date_time
PA0680	Multiple calls to set_reference_date_time detected. The reference date-time must be set only once.	Routine set_reference_date_time can only be called once per program execution. Please check your user code for any additional calls to this routine and remove it. If you did not use any user code, please report the appearance of the error in the ticket system.
PA0681	section_xy/xz/yz not defined for requested xy/xz/yz-cross section output. At least one cross section must be given.	If you specified any data-output quantity for a xy-, xz-, or yz-cross section via data_output, then you need to also specify the location of at least one corresponding cross section via section_xy, section_xz, or section_yz.
PA0684	Found building surface on non-building coordinates (xs, ys, zenith, azimuth): "xs, ys, zenith, azimuth"	If the variable building_surface_pars has been specified within a static driver, the coordinates xs/ys/zs define the location of a horizontal/vertical buildings surface, while zenith/azimuth define the orientantion of the surface (upward-, northward-, southward-, eastward-, westward-facing). In case this error message appears, the coordinates xs, ys, zs, zenith, and azimuth describing a surface element do not match with the location of a building. Even if xs, ys, zs, are prescribed correctly, mismatches in zenith and azimuth may cause this error. In such a case, please check carefully your pre-processor code that you used to create the static driver. Further information about the data input for surface elements can be found here.
PA0686	The relative material fractions do not sum-up to one at horizotal/vertical surface. (i,j) = ...	If building_pars is specified within a static input file, all parameters indicating the relative fraction of wall / window / green surfaces must be given.
PA0688	surface fractions at grid point (j,i) = ( ) are all zero.
PA0689	Invalid input value: ptemp	Air temperature given to the subroutine for ternary nucleation (ternucl) is not within the allowed temperature range of 240-300 K.
PA0690	end_time of the simulation exceeds the time dimension in the dynamic input file.	Time dimension in <run_identifier>_dynamic must cover the entire simulation time.
PA0691	Offline nesting: time dimension must start at time_utc_init.	Time dimension in <run_identifier>_dynamic must start at the start of the simulation in time utc. For example, for a simulation starting at 7 am in UTC+3 time, this is 14400.
PA0692	end_time of the simulation exceeds the time dimension in the salsa input file.	Time dimension in <run_identifier>_salsa must cover the entire simulation time.
PA0693	None of the aerosol chemical components in <run_identifier>_dynamic correspond to ones applied in SALSA.	None of the chemical components given in composition_name in <run_identifier>_dynamic correspond to the ones applied in SALSA. Please check the file and spelling.
PA0694	Missing emission_mass_fracs in <run_identifier>_salsa	Variable emission_mass_fracs missing from <run_identifier>_salsa.
PA0695	salsa_emission_mode = "parameterized", but the street_type data is missing.	When salsa_emission_mode = "parameterized", the variable street_type must be provided in <run_identifier>_static.
PA0697	The mixing ratio exceeds the saturation mixing ratio	The mixing ratio must not exceed its saturation mixing ratio by more than 2 percent. Higher values are physically unrealistic and will not be observed in the atmosphere. In case cloud physics are considered, oversaturation would create strong convection leading to unpredictable model behavior. Further, oversaturated mixing ratios have implications in the land-surface model, where moisture might condense immediately at the surface, creating very high surface fluxes. Note, an error message is given in the initial run, while only a warning is given when moisture exceeds its saturation value in a restart run.
PA0698	Unclassified surface element at grid point (k,j,i) =	Input data is not defined consistently. Please contact the Palm support.
PA0699	Bottom and top boundary are treated equal	This is just an informative message. It tells you that the regions close to the bottom and top boundaries are treated physically and numerically equal. This is not necessarily the case for normal atmospheric runs.
PA0700	dz should be equal close to the boundaries due to symmetrical problem	To get realistic results of a closed channel flow, it is necessary to treat bottom and top boudary region the same. This includes the grid spacing.
PA0701	A constant flux layer is not allowed if a closed channel shall be used	So far, the constant flux layer approach is only implemented for the bottom boundary but bottom and top boundary shall be treated equal for closed channel flows. Therefore, it is not allowed.
PA0702	The ocean mode is not allowed if a closed channel shall be used	self-explanatory
PA0703	A closed channel requires the upwind scheme of Wicker and Skamarock as the advection scheme	Only the the upwind scheme of Wicker and Skamarock is realized and tested for a symmetric degradation of the advection scheme (from 5th, to 3rd to 1st order) close to the bottom and top boundary.
PA0704	End of line or file detected for file TOPOGRAPHY_DATA at line ...	File does not contain enough data. Check the respective line given in the error message. a) The number of columns (ncols) is less than nx+1. b) The number of rows (nrows) is less than ny+1. Solution: Make sure that ncols matches nx+1 and that nrows matches ny+1.
PA0705	If virtual measurements are taken, the number of surrounding grid points must not be larger than the number of ghost points - 1	When virtual measurements are taken, data is sampled at given station grid coordinates. It is possible that also the adjoining grid points can be sampled, however, the number of grid points additionally sampled in each direction must not be larger than the number of ghost points - 1 to avoid any segmentations faults. In the future we will improve this to allow a more flexible number of offset grid points.
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.
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.
PA0708	If virtual measurements are taken, parallel NetCDF is required.	The PALM code need to be compiled with a parallel NetCDF library.
PA0709	unknown boundary condition: bc_aer_n "..."	See parameter [wik:doc/app/salsa_parameters#bc_aer_n bc_aer_n] for allowed values, and appropriately correct your parameter file.
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.
PA0711	unknown boundary condition: bc_aer_s "..."	See parameter bc_aer_s for allowed values, and appropriately correct your parameter file.
PA0712	boundary conditions bc_aer_l and bc_aer_r must both be cyclic or non-cyclic.	See parameter descriptions under bc_aer_l and bc_aer_r, and appropriately correct your parameter file.
PA0713	boundary conditions bc_aer_n and bc_aer_s must both be cyclic or non-cyclic.	See parameter descriptions under bc_aer_n and bc_aer_s, and appropriately correct your parameter file.
PA0714	boundary conditions bc_cs_n and bc_cs_s must both be cyclic or non-cyclic
PA0715	Unused/incorrect input for initial surface value: ...
PA0716	Unused/incorrect input of chemical species for surface emission fluxes: ...
PA0717	The surface value of cs_heights must be 0.0
PA0718	boundary conditions bc_cs_n and bc_cs_s must both be cyclic or non-cyclic.	See parameter descriptions under bc_cs_n and bc_cs_s, and appropriately correct your parameter file.
PA0719	ql must be larger than zero.	values smaller than zero can occur if the time-stpe is not appropiate.
PA0720	illegal action "..." for opening restart files	Only actions "read" or "write" are allowed. This is a PALM internall conding problem. Please contact the PALM developers / submit a trouble ticket.
PA0721	error opening restart file for posix I/O.	A serial run (on one core) was unable to open the restart file for reading or writing. In case of reading check your job log if the restart file has been copied to the temporary working directory before execution of PALM.
PA0722	CHARACTER/INTEGER/REAL variable/array "..." not found in restart file.	The indicated variable was not found in the restart file. If you are doing restart I/O in your user-interface, please check that input- and output variables exactly match.
PA0723	2d-INTEGER array "..." to be read from restart file is defined with illegal dimensions in the PALM code.	This problem may appear in your user-interface, if you try to write/read 2d-INTEGER arrays with ghost boundaries to/from the restart file. 2d-INTEGER arrays in restart files are not allowed to have ghost boundaries so far.
PA0724	illegal restart data format "..."	See parameter description under restart_data_format for allowed values and correct your parameter file appropriately.
PA0725	illegal restart input data format "..."	See parameter description under restart_data_format_input for allowed values and correct your parameter file appropriately.
PA0726	illegal restart output data format "..."	See parameter description under restart_data_format_output for allowed values and correct your parameter file appropriately.
PA0727	error opening restart file "..." for reading with MPI-IO	Check if you provided the activation string d3r with palmrun option -a.
PA0728	error opening restart file "..." for writing with MPI-IO	There might be a problem with the directory that you have set in the configuration file (.palm.config...) via %fast_io_catalog.
PA0729	prerun data is not allowed to contain soil information	In case of initializing_actions = 'cyclic_fill', it is not allowed to use the land surface model within the prerun. Change your prerun parameter file appropriately.
PA0730	number of chem spcs exceeding the limit
PA0731	Incorrect mode_emiss option select. Please check spelling
PA0732	Invalid value for emiss_lod (0, 1, or 2)
PA0733	Synchronizing mode_emis to defined emiss_lod. NOTE - mode_emis will be depreciated in future releases please use emiss_lod to define emission mode
PA0734	emiss_lod undefined. Using existing mod_emiss setting. NOTE - mode_emis will be depreciated in future releases please use emiss_lod to define emission mode
PA0735	Legacy emission read mode activated. All emissions data will be loaded prior to start of simulation
PA0736	New emission read mode currently unavailable for LODs 0 and 1. Reverting to legacy emission read mode
PA0737	New emission read mode activated LOD 2 emissions will be updated on-demand according to indicated timestamps
PA0738	No lsm- ... type defined. Please define ... type to enable deposition calculation
PA0739	No pavement type defined. Please define pavement type to enable deposition calculation
PA0740	Component ... not supported
PA0741	nwet can only be 0 or 1
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	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'
UI0003	unused
UI0004	unused
UI0005	topography "..." not available yet	There was no usable user-defined topography found.
UI0006	unknown topography "..."	This error message appears if the parameter topography is not set to one of the allowed values 'flat', 'single_building', 'single_street_canyon', 'tunnel' or to a user defined value. This can happen if the parameter topography contains a wrong character string that is neither recognized in init_grid nor in user_init_grid.
UI0007	canopy_mode "..." not available yet	There was no usable user-defined plant canopy found.
UI0008	unknown canopy_mode "..."	The requested identifier for the canopy mode was not found in the user interface palm/trunk/SOURCE/user_init_plant_canopy.f90​. Check if the spelling in your input file matches the defined canopy mode.
UI0009	the number of user-defined profiles given in data_output_pr (...) does not match the one found in the restart file (...)	This will only happen in case the number of user profiles was changed from precursor to main run. See documentation of tubulent inflow for detailed information on the use of restart data for precursor runs.
UI0010	Spectra of ... can not be calculated	No CASE statement defined for '...' in user_spectra.f90​.
UI0011	Spectra of ... are not defined	No CASE statement defined for '...' in user_spectra.f90​.
NC****	**** contains numbers in the range from 1-521	Internally, PALM calls the netCDF function NF90_STRERROR which returns an error message string provided by netCDF. Hence, no exact assignment between PALM error number and netCDF error string can be given. Most of the netCDF errors should never appear if the default code is used. The following list gives errors which may be caused by wrong steering or errors due to problems in the user interface.
NC0079	String match to name in use	A netCDF variable name has been used twice. Possible reasons: a variable in the parameter file has been listed twice (e.g. in data_output) or a variable name that has been defined in the user interface is already used by PALM.
NC0253	Name contains illegal characters	netCDF variable names consist of arbitrary sequences of alphanumeric characters. These names are e.g. assigned by the user in the user-interface to variables dots_label or dopr_label. Due to the netCDF convention, they must not start with a digit. Also, usage of / as special character is not allowed. Older netCDF versions (before 3.6.3) have further restrictions on special characters. Please check if your string settings in the user-interface follow the above rules.