forked from ESCOMP/CMEPS
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathnamelist_definition_drv_flds.xml
200 lines (173 loc) · 7.46 KB
/
namelist_definition_drv_flds.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="http://www.cgd.ucar.edu/~cam/namelist/namelist_definition.xsl"?>
<entry_id version="2.0">
<!--
The following lists all of the namelist variables that can appear in the Buildconf/xxxconf/drv_flds_in
files, where xxx = [cam, clm, ...]. The driver buildnml treats all of these files as user_nl_cpl files
for generating the driver drv_flds_in file, which will appear in CaseDocs and in $RUNDIR.
-->
<!-- ======================================================================================== -->
<!-- MEGAN VOC emissions namelist options -->
<!-- ======================================================================================== -->
<entry id="megan_factors_file">
<type>char</type>
<input_pathname>abs</input_pathname>
<category>drv_flds_in</category>
<group>megan_emis_nl</group>
<desc>
File containing MEGAN emissions factors. Includes the list of MEGAN compounds that can be
used in the Comp_Name variable on the file.
</desc>
</entry>
<entry id="megan_specifier">
<type>char(100)</type>
<category>drv_flds_in</category>
<group>megan_emis_nl</group>
<desc>
MEGAN specifier. This is in the form of: Chem-compound = megan_compound(s)
where megan_compound(s) can be the sum of megan compounds with a "+" between them.
In each equation, the item to the left of the equal sign is a CAM chemistry compound, the
items to the right are compounds known to the MEGAN model (single or combinations).
For example: megan_specifier = 'ISOP = isoprene', 'C10H16 = pinene_a + carene_3 + thujene_a'
</desc>
</entry>
<entry id="megan_mapped_emisfctrs">
<type>logical</type>
<category>drv_flds_in</category>
<group>megan_emis_nl</group>
<desc>
MEGAN mapped isoprene emissions factors switch
If TRUE then use mapped MEGAN emissions factors for isoprene.
</desc>
</entry>
<entry id="megan_cmpds">
<type>char(150)</type>
<category>drv_flds_in</category>
<group>drv_physics</group>
<desc>
List of possible MEGAN compounds to use
(the list used by the simulation is on the megan_factors_file as the Comp_Name)
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- drydep Namelists -->
<!-- ======================================================================================== -->
<entry id="drydep_list">
<type>char(300)</type>
<category>dry-deposition</category>
<group>drydep_inparm</group>
<desc>
List of species that undergo dry deposition.
</desc>
</entry>
<entry id="dep_data_file">
<type>char</type>
<input_pathname>abs</input_pathname>
<category>drv_flds_in</category>
<group>drydep_inparm</group>
<desc>
Full pathname of file containing gas phase deposition data including effective
Henry's law coefficients.
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- Nitrogen deposition -->
<!-- ======================================================================================== -->
<entry id="ndep_list">
<type>char(2)</type>
<category>nitrogen deposition</category>
<group>ndep_inparm</group>
<desc>
List of nitrogen deposition fluxes to be sent from CAM to surfae models.
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- Fire emissions fluxes -->
<!-- ======================================================================================== -->
<entry id="fire_emis_factors_file">
<type>char</type>
<input_pathname>abs</input_pathname>
<category>Fire_emissions</category>
<group>fire_emis_nl</group>
<desc>
File containing fire emissions factors.
</desc>
</entry>
<entry id="fire_emis_specifier">
<type>char(100)</type>
<category>Fire_emissions</category>
<group>fire_emis_nl</group>
<desc>
Fire emissions specifier.
</desc>
</entry>
<entry id="fire_emis_elevated">
<type>logical</type>
<category>Fire_emissions</category>
<group>fire_emis_nl</group>
<desc>
If ture fire emissions are input into atmosphere as elevated forcings.
Otherwise they are treated as surface emissions.
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- CARMA fields -->
<!-- ======================================================================================== -->
<entry id="carma_fields">
<type>char</type>
<category>carma</category>
<group>carma_inparm</group>
<desc>
List of fluxes needed by the CARMA model, from CLM to CAM.
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- Dust emission fields -->
<!-- ======================================================================================== -->
<entry id="dust_emis_method">
<type>char*80</type>
<category>dust_emissions</category>
<group>dust_emis_inparm</group>
<valid_values>Zender_2003,Leung_2023</valid_values>
<desc>
Which dust emission method is going to be used. Either the Zender 2003 scheme or the Leung 2023
scheme.
</desc>
</entry>
<entry id="zender_soil_erod_source">
<type>char*80</type>
<category>dust_emissions</category>
<group>dust_emis_inparm</group>
<valid_values>none,lnd,atm</valid_values>
<desc>
Option only applying for the Zender_2003 method for whether the soil erodibility file is handled
in the active LAND model or in the ATM model.
(only used when dust_emis_method is Zender_2003)
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- Ozone control -->
<!-- ======================================================================================== -->
<entry id="atm_ozone_frequency">
<type>char</type>
<category>ozone_coupling</category>
<group>ozone_coupling_nl</group>
<desc>
Frequency of surface ozone field passed from CAM to surface components.
Surface ozone is passed every coupling interval, but this namelist flag
indicates whether the timestep-level values are interpolated from a
coarser temporal resolution.
</desc>
</entry>
<!-- ======================================================================================== -->
<!-- Lightning -->
<!-- ======================================================================================== -->
<entry id="atm_provides_lightning">
<type>logical</type>
<category>lightning_coupling</category>
<group>lightning_coupling_nl</group>
<desc>
If TRUE atmosphere model will provide prognosed lightning flash frequency (flashes per minute).
</desc>
</entry>
</entry_id>