Changes between Version 264 and Version 265 of doc/app/errmsg

Timestamp:

Aug 12, 2016 1:55:15 PM (8 years ago)

Author:

suehring

Comment:

--

doc/app/errmsg

@@ -93 +93 @@
 ||[=#PA0068 PA0068]   ||unknown boundary condition: bc_sa_t = "..."   ||See parameter [../inipar#bc_sa_t bc_sa_t] for allowed values, and appropriately correct your parameter file.  ||
 ||[=#PA0069 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 [../inipar#bc_sa_t bc_sa_t] = '' 'neumann' ''), but you did not provide a salinity flux at the top. Please provide parameter [../inipar#top_salinityflux top_salinityflux] in the parameter file. ||
-||[=#PA0070 PA0070]   ||boundary condition: bc_sa_t = "..." is not allowed with constant_top_salinityflux = .TRUE.'   ||You have tried to set both, a Dirichlet boundary condition for salinity at the top (with [../inipar#bc_sa_t bc_sa_t] = '' 'dirichlet' ''), and a salinity flux at the top (with [../inipar#top_salinityflux 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. ||
+||[=#PA0070 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 [../inipar#bc_sa_t bc_sa_t] = '' 'dirichlet' ''), and a salinity flux at the top (with [../inipar#top_salinityflux 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 PA0071]   ||unknown boundary condition: bc_..._b ="..."   ||See the respective parameter description in the documentation, and appropriately correct your parameter file. ||
 ||[=#PA0072 PA0072]   ||unknown boundary condition: bc_..._t ="..."   ||See the respective parameter description in the documentation, and appropriately correct your parameter file. ||
@@ -667 +667 @@
 ||[=#PA0439 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.  ||
 ||[=#PA0440 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 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 [../inipar#bc_s_t bc_s_t] = '' 'dirichlet' ''), or an initial-gradient boundary condition, and a scalar flux at the top (with [../inipar#top_scalarflux top_scalarflux] /= ''0.0''). ||
 ||[=#UI0001 UI0001]   ||unknown location "..."   ||The location has to be either 'time_int' or 'nudging'.  ||
 ||[=#UI0002 UI0002]   ||location "..." is not allowed to be called with parameters "i" and "j"   ||  ||