Changes between Version 47 and Version 48 of doc/app/chemistry_parameters

Timestamp:

Oct 15, 2018 11:45:19 AM (6 years ago)

Author:

forkel

Comment:

--

doc/app/chemistry_parameters

@@ -3 +3 @@
 
 
-'''Steering:'''
+'''[#Steering Steering]:'''
  '''[#chempar Chemistry namelist]'''\\
  '''[#output Output steering in 'runtime_parameters']'''\\
@@ -50 +50 @@
 A brief description of the chemistry model will follow here (see [wiki:doc/app/lsmpar#LandSurfaceParameters LSM description] as an example).
 
-\\\\
-NAMELIST group name: [=#chempar '''chemistry_parameters''']\\
-
 
 ----
 \\\\
 [=#steering '''Steering:]\\
+
+
+\\\\
+NAMELIST group name: [=#chempar '''chemistry_parameters''']
+
 ||='''Parameter Name'''  =||='''[[../fortrantypes|FORTRAN]]\\[[../fortrantypes|Type]]'''  =||='''Default\\Value'''  =||='''Explanation'''  =||
 |----------------
@@ -162 +164 @@
 }}}
 {{{#!td
-Names of chemical species where surface concentrations or profiles are prescribed. 
+Names of chemical species where surface concentrations or concentration profiles ([#cs_profile cs_profile]) are prescribed. 
 Example:\\
 cs_name                    = 'O3',  'NO', 'NO2',  'CO', 'RCHO', 'PM10', 'PM25',\\
@@ -183 +185 @@
 cs_profile(1,:)            =  0.020, 0.023, 0.026, 0.029, 0.032, 0.035, 0.038, 0.041, 0.044, 0.047, 0.050,    !Values for initial profile of first species\\
 cs_profile(2,:)            =  0.080, 0.073, 0.064, 0.057, 0.050, 0.043, 0.036, 0.029, 0.022, 0.015, 0.007,    !Values for initial profile of second species\\ 
-The individual chemical species are identified using [#cs_name cs_name]
+The individual chemical species are identified using [#cs_name cs_name]. These initial profiles become only effective when = 'inifor {{{set_constant_profiles}}} is set for [#init initializing_actions]. 
 }}}
 |----------------
@@ -201 +203 @@
 |----------------
 {{{#!td style="vertical-align:top; width: 150px"
-[=#cs_surface_initial_change '''cs_surface_initial_change''']
-}}}
-{{{#!td style="vertical-align:top; width: 50px"
-XXX
+[=#cs_vertical_gradient_level '''cs_vertical_gradient_level''']
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+dto
 }}}
 {{{#!td style="vertical-align:top; width: 75px"
@@ -210 +212 @@
 }}}
 {{{#!td
-Not required. Copied from passive scalar. We can use emissions instead, so no idea what it is still good for.
-}}}
-|----------------
-{{{#!td style="vertical-align:top; width: 150px"
-[=#cs_vertical_gradient '''cs_vertical_gradient''']
-}}}
-{{{#!td style="vertical-align:top; width: 50px"
-XXX
-}}}
-{{{#!td style="vertical-align:top; width: 75px"
-YYY
-}}}
-{{{#!td
-Not used, as we set initial values of cs by specifying values at given heights, not vertical gradients
-}}}
-|----------------
-{{{#!td style="vertical-align:top; width: 150px"
-[=#cs_vertical_gradient_level '''cs_vertical_gradient_level''']
-}}}
-{{{#!td style="vertical-align:top; width: 50px"
-dto
-}}}
-{{{#!td style="vertical-align:top; width: 75px"
-YYY
-}}}
-{{{#!td
 ZZZ
 }}}
@@ -249 +225 @@
 }}}
 {{{#!td
-Type of weekday required for the MDH case of the DEFAULT mode of the emissions module.
+Type of weekday required for the MDH (MonthDayHour)case of the DEFAULT mode of the emissions module.
 Possible values are: workday, weekend, holiday
 }}}
@@ -331 +307 @@
 }}}
 {{{#!td
-Constant emission scaling factor for SIDE (secondary) street types, used in the PARAMETERIZED mode of chem_emission module. The number and the order of the values has to correspond to the names of the emission species provided for [#surface_csflux_name surface_csflux_name].
+Constant emission scaling factor for SIDE (secondary) street types, used in the PARAMETERIZED [#mode_emis mode] of chem_emission module. The number and the order of the values has to correspond to the names of the emission species provided for [#surface_csflux_name surface_csflux_name].
 
 }}}
@@ -461 +437 @@
 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)
+ 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)
 
 See http://people.cs.vt.edu/asandu/Software/Kpp/
@@ -570 +546 @@
 |----------------
 
- [=#output Output steering in `runtime_parameters`]
-
- [=#init Initialisation steering in `initialization_parameters`]
-
+\\
+
+'''[=#output Output steering in `runtime_parameters`]'''
+
+
+
+\\
+'''[=#init Initialisation steering in `initialization_parameters`]'''
+
+If large-scale forcings (inifor) are used only for meteorology, then user defined initial concentration and initial vertical profiles can be activated by adding 'set_constant_profiles' with inifor separated by a spaces only. For example 
+
+{{{initializing_actions = 'inifor set_constant_profiles', }}}
+