Difference between revisions of "Sandbox"

From Geos-chem
Jump to: navigation, search
(Emission directories by version)
 
Line 1: Line 1:
On this page we describe the directory tree from which the [[HEMCO|HEMCO emissions component]] can read emissions inventories and other atmospheric data sets.
+
== Instructions for adding tracers to GEOS-Chem ==
  
== Overview ==
+
'''''By [mailto:mpayer@seas.harvard.edu Melissa Payer]'''''
  
The [[HEMCO|HEMCO emissions component]] can read several types of emission inventories, as well as other types atmospheric data sets, such as production and loss rates, or concentration dataWe have collated all of this data into a comprehensive directory tree structure. Each folder of the HEMCO data directory tree represents a particular emissions inventory or other data set.
+
These instructions describe how to add advected tracers to GEOS-ChemAdvected tracers are carried in the <tt>STT</tt> array (which is declared in <tt>GeosCore/tracer_mod.F</tt>), and are transported by the winds.
  
At present, the HEMCO data directory tree resides on the Compute Canada and AWS s3://gcgrid bucket.  We have created a package that will let you download this directory tree to your local disk storage space.  For more information, please see the [[#Downloading_the_HEMCO_data_directories|''Downloading the HEMCO data directories'']] section below.
+
NOTE: Some advected tracers are also chemical species, which comprise GEOS-Chem's NOx-Ox-HC-aerosol chemistry mechanism.
  
== Data directories by GEOS-Chem version ==
+
#<p>Add tracers to input.geos under Tracer Menu</p>
 +
##<p>Increase “Number of tracers” accordingly</p>
 +
##<p>Add tracer number, name, molecular weight, and emitted species to end of tracer list</p>
 +
#<p>Add tracer(s) to restart file – see separate instructions</p>
 +
#<p>Modify the following source code routines:</p>
 +
##<p><tt>Headers/CMN_SIZE_mod.F</tt></p>
 +
###<p>Increase <tt>NNPAR</tt> by number of tracers being added</p>
 +
###<p>If the species have anthropogenic emissions, increase NEMPARA accordingly</p>
 +
###<p>If the species have biogenic emissions, increase NEMPARB accordingly</p>
 +
###<p>If the species have biomass burning emissions, increase NBIOMAX accordingly</p>
 +
##<p><tt>GeosCore/tracerid_mod.F</tt></p>
 +
###<p>Increase <tt>NNNTRID</tt> by the number of tracers being added NOTE: <tt>NNNTRID</tt> must be equal to <tt>NNPAR</tt> in <tt>CMN_SIZE_mod.F</tt></p>
 +
###<p>Define tracer IDs as needed:</p>
 +
####<p>IDxxxx – ID for SMVGEAR species</p>
 +
####<p>IDTxxxx – GEOS-Chem tracer ID</p>
 +
####<p>IDExxxx – GEOS-Chem emission ID</p>
 +
####<p>IDBFxxxx – GEOS-Chem biofuel ID</p>
 +
####<p>IDBxxxx – GEOS-Chem biomass ID</p>
 +
###<p>In subroutine <tt>TRACERID</tt>,</p>
 +
####<p>Under “Assign tracer, biomass, biofuel, and anthro emission ID’s,” add case for added tracers to initialize IDTxxxx, IDBFxxxx, IDBxxxx</p>
 +
####<p>Under “Initialize the IDExxx flags,” add IF statement for added tracer IDs and initialize IDExxxx</p>
 +
####<p>Under “Fill IDEMS with appropriate tracer ID #’s,” add IF statement for added tracers</p>
 +
####<p>Under “Print additional information,” add WRITE statements for added tracers</p>
 +
###<p>In subroutine SETTRACE  (NOTE: Only do the following if species is included in SMVGEAR chemical mechanism<p>
 +
####<p>Add IF statement, to initialize IDxxxx</p>
 +
####<p>In subroutine INIT_TRACERID,</p>
 +
####<p>Zero all IDs added (IDxxxx, IDTxxxx, IDExxxx, etc.)</p>
 +
##<p>Other modules that may need to be updated include:</p>
 +
###<p>wetscav_mod.F</p>
 +
###<p>drydep_mod.F</p>
 +
###<p>emissions_mod.F</p>
 +
###<p>biomass_mod.F</p>
 +
###<p>biofuel_mod.F</p> etc.
  
Our [https://github.com/geoschem/input-data-catalogs/Github repository named '''input-data-catalogs'''] contains lists of input files needed to run GEOS-Chem simulations.  These are contained in the comma-separated files <tt>ChemistryInputs.csv</tt>, <tt>EmissionInputs.csv</tt> and <tt>InitialConditions.csv</tt>.  Passing these files to the [https://github.com/LiamBindle/bashdatacatalog <tt>bashdatacatalog</tt>] utility will download the data to your local disk storage].
 
  
{| border=1 cellspacing=0 cellpadding=5
 
|-bgcolor="#CCCCCC"
 
!width="150px"|Version
 
!width="200px"|Chemistry Inputs
 
!width="200px"|Emissions Inputs
 
!width="200px"|Initial Conditions
 
  
|-valign="top" halign="center"
+
Instructions for adding species to GEOS-Chem
|[[GEOS-Chem 13.4.0]]
+
|
+
|
+
|
+
  
|-valign="top" halign="center"
+
Modify run directory files
|[[GEOS-Chem 13.3.0]]
+
|
+
|
+
|
+
  
|-valign="top" halign="center"
+
1) Add tracers to input.geos under Tracer Menu
|[[GEOS-Chem 13.2.0]]
+
c) Increase “Number of tracers” accordingly
|
+
d) Add tracer number, name, molecular weight, and emitted species to end of tracer list
|
+
|
+
  
|-valign="top" halign="center"
+
2) Add tracer(s) to restart file – see separate instructions
|[[GEOS-Chem 13.1.0]]
+
|
+
|
+
|
+
  
|-valign="top"
+
3) Modify globchem.dat to include additional species, kinetic reactions (including emissions and drydep), or photolysis reactions
|[[GEOS-Chem 13.0.0]]
+
NOTE: If you modify globchem.dat and plan to run GEOS-Chem using the KPP chemical solver, you will need to generate new gckpp*.F90 files. For more information see the following wiki pages:
|[https://github.com/geoschem/input-data-catalogs/blob/7a53a0c19b5972611486a91a4c45433da97ba7c9/ChemistryInputs.csv <tt>ChemistryInputs.csv</tt>]
+
http://wiki.seas.harvard.edu/geos-chem/index.php/KPP_solvers_FAQ#What_are_the_cons_of_using_KPP.3F
|[https://github.com/geoschem/input-data-catalogs/blob/7a53a0c19b5972611486a91a4c45433da97ba7c9/EmissionsInputs.csv <tt>EmissionInputs.csv</tt>]
+
http://wiki.seas.harvard.edu/geos-chem/index.php/Interfacing_GEOS-Chem_with_KPP#Generating_KPP_input_files_from_GEOS-Chem_globchem.dat
|[https://github.com/geoschem/input-data-catalogs/blob/7a53a0c19b5972611486a91a4c45433da97ba7c9/InitialConditions.csv  <tt>InitialConditions.csv</tt>]
+
  
|}
+
4) If necessary, modify:
 +
a) ratj.d – contains species names and branching ratios for FAST–JX photolysis species
 +
For more information: http://acmg.seas.harvard.edu/geos/doc/man/chapter_5.html#5.4.1
 +
b) jv_spec.dat – contains cross-sections and quantum yields for FAST–JX photolysis species
 +
For more information: http://acmg.seas.harvard.edu/geos/doc/man/chapter_5.html#5.4.3

Latest revision as of 21:25, 10 May 2023

Instructions for adding tracers to GEOS-Chem

By Melissa Payer

These instructions describe how to add advected tracers to GEOS-Chem. Advected tracers are carried in the STT array (which is declared in GeosCore/tracer_mod.F), and are transported by the winds.

NOTE: Some advected tracers are also chemical species, which comprise GEOS-Chem's NOx-Ox-HC-aerosol chemistry mechanism.

  1. Add tracers to input.geos under Tracer Menu

    1. Increase “Number of tracers” accordingly

    2. Add tracer number, name, molecular weight, and emitted species to end of tracer list

  2. Add tracer(s) to restart file – see separate instructions

  3. Modify the following source code routines:

    1. Headers/CMN_SIZE_mod.F

      1. Increase NNPAR by number of tracers being added

      2. If the species have anthropogenic emissions, increase NEMPARA accordingly

      3. If the species have biogenic emissions, increase NEMPARB accordingly

      4. If the species have biomass burning emissions, increase NBIOMAX accordingly

    2. GeosCore/tracerid_mod.F

      1. Increase NNNTRID by the number of tracers being added NOTE: NNNTRID must be equal to NNPAR in CMN_SIZE_mod.F

      2. Define tracer IDs as needed:

        1. IDxxxx – ID for SMVGEAR species

        2. IDTxxxx – GEOS-Chem tracer ID

        3. IDExxxx – GEOS-Chem emission ID

        4. IDBFxxxx – GEOS-Chem biofuel ID

        5. IDBxxxx – GEOS-Chem biomass ID

      3. In subroutine TRACERID,

        1. Under “Assign tracer, biomass, biofuel, and anthro emission ID’s,” add case for added tracers to initialize IDTxxxx, IDBFxxxx, IDBxxxx

        2. Under “Initialize the IDExxx flags,” add IF statement for added tracer IDs and initialize IDExxxx

        3. Under “Fill IDEMS with appropriate tracer ID #’s,” add IF statement for added tracers

        4. Under “Print additional information,” add WRITE statements for added tracers

      4. In subroutine SETTRACE (NOTE: Only do the following if species is included in SMVGEAR chemical mechanism<p>

        1. <p>Add IF statement, to initialize IDxxxx

        2. In subroutine INIT_TRACERID,

        3. Zero all IDs added (IDxxxx, IDTxxxx, IDExxxx, etc.)

    3. Other modules that may need to be updated include:

      1. wetscav_mod.F

      2. drydep_mod.F

      3. emissions_mod.F

      4. biomass_mod.F

      5. biofuel_mod.F

        etc.


Instructions for adding species to GEOS-Chem

Modify run directory files

1) Add tracers to input.geos under Tracer Menu c) Increase “Number of tracers” accordingly d) Add tracer number, name, molecular weight, and emitted species to end of tracer list

2) Add tracer(s) to restart file – see separate instructions

3) Modify globchem.dat to include additional species, kinetic reactions (including emissions and drydep), or photolysis reactions NOTE: If you modify globchem.dat and plan to run GEOS-Chem using the KPP chemical solver, you will need to generate new gckpp*.F90 files. For more information see the following wiki pages: http://wiki.seas.harvard.edu/geos-chem/index.php/KPP_solvers_FAQ#What_are_the_cons_of_using_KPP.3F http://wiki.seas.harvard.edu/geos-chem/index.php/Interfacing_GEOS-Chem_with_KPP#Generating_KPP_input_files_from_GEOS-Chem_globchem.dat

4) If necessary, modify: a) ratj.d – contains species names and branching ratios for FAST–JX photolysis species For more information: http://acmg.seas.harvard.edu/geos/doc/man/chapter_5.html#5.4.1 b) jv_spec.dat – contains cross-sections and quantum yields for FAST–JX photolysis species For more information: http://acmg.seas.harvard.edu/geos/doc/man/chapter_5.html#5.4.3