Version 34 (modified by Russo, 6 years ago) (diff) |
---|
Chemistry model parameters
TracNav
Core Parameters
Module Parameters
- Agent system
- Aerosol (Salsa)
- Biometeorology
- Bulk cloud physics
- Chemistry
- FASTv8
- Indoor climate
- Land surface
- Nesting
- Nesting (offline)
- Ocean
- Particles
- Plant canopy
- Radiation
- Spectra
- Surface output
- Synthetic turbulence
- Turbulent inflow
- Urban surface
- User-defined
- Virtual flights
- Virtual measurements
- Wind turbine
- Alphabetical list (outdated!)
Steering:
Chemistry namelist
Output steering in 'runtime_parameters'
Initialisation steering in 'initialization_parameters'
Since Version 5.0 a chemistry model is available in PALM which computes chemical conversion and tranport of reactive trace gases. In addition this module permits also the simulation of passive compounds in the gas phase and particulate matter.
All parts of code that are related to chemistry start with chem. The main routines and the driver of the chemistry module is included in chemistry_model_mod.f90. The main routines and the driver of the chemistry module is included in chemistry_model_mod.f90, subroutines are in chem_gasphase_mod.f90, chem_photolysis_mod.f90, and chem_emissions.f90.
The module chem_gasphase_mod.f90, where the gas phase chemistry rate equations are solved within PALM4U depends on the chosen chemical mechanism. chem_gasphase_mod.f90 is generated by a preprocessor that is based on the Kinetic Pre-Processor KPP (Damian et al., 2002, Sandu et al., 2006), Release 2.2.3 from November 2012 (http://people.cs.vt.edu/asandu/Software/Kpp/, kpp-2.2.3.tar.gz) and an adapted version of the KPP postprocessor KP4 (Jöckel et al, 2010, https://www.geosci-model-dev.net/3/717/2010/). This adapted Version of kp4 which converts the KPP-generated code to a PALM4U module is named kpp4palm.
The chemical preprocessor is located in the subdirectory UTIL/chemistry/gasphase_preproc.
Currently PALM-4U includes the following sample of chemistry mechanisms:
- CBM4: Carbon Bond Mechanism (Gery et al. 1989, 32 compounds, 81 reactions)
- SMOG: Photochemical smog mechanism (13 compounds, 12 reactions)
- SIMPLE: Simplified version of SMOG (9 compounds, 7 reactions)
- SIMPLEP: SIMPLE plus one tracer named PM10 (10 compounds, 7 real reactions plus one dummy 'reaction')
- PHSTAT: Photo-stationary state (3 compounds, 2 reactions)
Additionally 'mechanisms' are available that describes only the transport of one and two passive Tracers, respectively:
- PASSIVE1: Passive tracers (1 compound, 0 reactions)
- PASSIVE: Passive tracers (2 compounds, 0 reactions)
The list will be extended further.
Ready-to-use chem_gasphase_mod.f90 files for each of the mechanisms are supplied in the subdirectories Util/chemistry/gasphase_preproc/mechanisms/def_MECH, where 'MECH' stands for any of the available mechanisms. For using a different chemical mechanism than the one that comes with checkout of PALM4U (currently PASSIVE), copy your preferred mechanism into the SOURCEdirectory.
For details about preparing a chem_gasphase_mod.f90 from scratch see Readme_KPP4PALM.odt in the PALM4U subdirectory UTIL/chemistry/gasphase_preproc.
A main factor influencing atmospheric chemistry are the emissions of reactive compounds. In PALM4U emissions can be applied in three different ways:
- PARAMETERIZED: Traffic emissions are parameterized depending on the the values of street_type in the static file. Emission values for each street type and chemical compound must be supplied in the namelist as described beow. No other emissions are considered. street_type can be obtained from Openstreetmap.
- DEFAULT: Gridded yearly emissions must be supplied by the user as specified in the PIDS document (see sample emissions file). Typical temporal variations are apllied by PALM4U.
- PREPROCESSED: Preprocessed hourly (other temporal intervals will be possible in later versions) 3-d emission fields must be supplied by the user.
Chemistry is automatically activated when a chemistry_parameters namelist is set in the parameter file (_p3d).
A brief description of the chemistry model will follow here (see LSM description as an example).
NAMELIST group name: chemistry_parameters
Steering:
Parameter Name | FORTRAN Type | Default Value | Explanation |
---|---|---|---|
bc_cs_b | C*20 | 'dirichlet' | Bottom boundary condition of the chemical species (cs) concentration. Allowed values are 'dirichlet' (cs(k=0) = const. = cs_surface + cs_surface_initial_change; When a constant surface concentration flux is used (surface_cs_flux) or emissions are applied ('do_emis' = .T.), bc_cs_b = 'neumann' must be used. |
bc_cs_t | C*20 | 'initial_gradient' | Top boundary condition of the scalar concentration. Allowed are the values 'dirichlet' (cs(k=nz+1) does not change during the run), 'neumann' (cs(k=nz+1) = cs(k=nz)), and 'initial_gradient' . With the 'initial_gradient' boundary condition the value of the scalar concentration gradient at the top is calculated from the initial scalar concentration profile (see cs_surface, cs_vertical_gradient) by: bc_cs_t_val = (cs_init(k=nz) - ss_init(k=nz-1)) / dzu(nz). Using this value (assumed constant during the run) the concentration boundary values are calculated as cs(k=nz+1) = cs(k=nz) + bc_cs_t_val * dzu(nz+1) (up to k=nz the prognostic equation for the chemical species concentration is solved). When a constant cs flux is used at the top boundary (top_csflux), bc_cs_t = 'neumann' must be used, because otherwise the resolved scale may contribute to the top flux so that a constant value cannot be guaranteed. |
call_chem_at_all_substeps | L | .FALSE. | Switch whether chemistry is called at each substep of the Runge-Kutta scheme or just at each full dynamical time step 'dt'. The latter will do since the chemistry solvers are using their own timestep steering. |
chem_debug0 | L | .FALSE. | Extra print output of chemistry variables. |
chem_gasphase_on | L | .TRUE. | Switch for switching off the chemical reactions but still doing the transport for all chemical compounds. Useful for test purposes. |
cs_heights | R(99,100) | 9999999.9_wp |
Height levels above ground (in m) to go with cs_profile in order to define initial profiles of chemical species.
The first index refers to the chemical compound, the second to height level.
Example: |
cs_name | C*11(99) | 'novalue' |
Names of chemical species where surface concentrations or profiles are prescribed.
Example: |
cs_profile | R(99,100) | 9999999.9_wp |
Concentration values of chemical species (gases in ppm, particulate matter in kg m-3) at cs_heights.
Example: |
cs_surface | R | 0.0 | Concentration value for chemical species at the surface (gases in ppm, particulate matter in kg m-3). |
cs_surface_initial_change | XXX | YYY | Not required. Copied from passive scalar. We can use emissions instead, so no idea what it is still good for. |
cs_vertical_gradient | XXX | YYY | Not used, as we set initial values of cs by specifying values at given heights, not vertical gradients |
cs_vertical_gradient_level | dto | YYY | ZZZ |
daytype_mdh | XXX | C*80 | Type of weekday required for the MDH case of the DEFAULT mode of the emissions module. Possible values are: workday, weekend, holiday |
decycle_chem_lr | XXX | YYY | ZZZ |
decycle_chem_ns | L | .FALSE. | Cyclic boundary conditions for chemistry may result in accumluation of chemical compounds. If decycle_chem_ns is set to true, initial concentration values are fixed at the southern boundary. |
decycle_method | C*20(4) | 'dirichlet' |
Decycling method at horizontal boundaries (1=left, 2=right, 3=south, 4=north)
|
do_emis | XXX | YYY | ZZZ |
emiss_factor_main | XXX | YYY | ZZZ |
emiss_factor_side | XXX | YYY | ZZZ |
icntrl | I(20) | 0 | Selection and steering of the chemistry solver.
Note: For input parameters equal to zero the default values of the corresponding variables are used.
|
main_street_id | XXX | YYY | ZZZ |
max_street_id | XXX | YYY | ZZZ |
mode_emis | XXX | YYY | ZZZ |
my_steps | XXX | YYY | ZZZ |
nest_chemistry | XXX | YYY | ZZZ |
photolysis_scheme | XXX | YYY | ZZZ |
rcntrl | R(20) | 0.0 and see below | Steering of the chemistry solver. RCNTRL(1) -> Hmin,lower bound for the integration step size. It is strongly recommended to keep Hmin = ZERO RCNTRL(2) -> Hmax,upper bound for the integration step size RCNTRL(3) -> Hstart,starting value for the integration step size RCNTRL(4) -> FacMin?,lower bound on step decrease factor (default=0.2); RCNTRL(5) -> FacMax?,upper bound on step increase factor (default=6); RCNTRL(6) -> FacRej?,step decrease factor after multiple rejections RCNTRL(7) -> FacSafe?,by which the new step is slightly smaller than the predicted value (default=0.9) |
side_street_id | XXX | YYY | ZZZ |
surface_csflux | XXX | YYY | ZZZ |
surface_csflux_name | C*11(99) | 'novalue' |
Names of chemical species which are emitted. Required only for mode_emis = 'PARAMETERIZED',.
Example: |
time_fac_type | XXX | YYY | ZZZ |
top_csflux | XXX | YYY | ZZZ |
wall_csflux | XXX | YYY | ZZZ |
Output steering in runtime_parameters
Initialisation steering in initialization_parameters
Attachments (5)
-
chem_emissions_PALM4U.pdf
(112.9 KB) -
added by banzhafs 6 years ago.
PALM4U emission input documentation
-
Readme_KPP4PALM.pdf
(131.1 KB) -
added by forkel 6 years ago.
Information about kpp4palm
-
test_urban_chem_passive.tar
(6.5 MB) -
added by forkel 6 years ago.
test_urban with two passive compounds
-
INPUT_test_berlin_chem_smog.tar
(1.2 MB) -
added by forkel 6 years ago.
Test setup for Berlin with smog 'mechanism'
-
INPUT_test_berlin_chem_passive.tar
(1.2 MB) -
added by forkel 6 years ago.
Test setup for Berlin with 2 passive compounds