Difference between revisions of "Sandbox"

From Geos-chem
Jump to: navigation, search
(→‎feel free to experiment here)
(→‎Emission directories by version)
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
==feel free to experiment here ==
+
On this page we describe the directory tree from which the [[HEMCO|HEMCO emissions component]] can read emissions inventories and other atmospheric data sets.
  
−
{| border=1 bordercolor="#000000" cellpadding="5" cellspacing="0"
+
== Overview ==
−
|-valign="top"
+
−
|Yuan_XLAI
+
−
|DEFAULT
+
−
|[[Leaf area indices in GEOS-Chem#Yuan processed MODIS LAI|Yuan processed MODIS LAI data]]
+
−
*cf Yuan et al 2011, doi:10.1016/j.rse.2011.01.001
+
  
−
This data has been processed into 73 netCDF variables (one corresponding to each Olson land type), which facilitates regridding by HEMCO.
+
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 data. We 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.
−
|[ftp://ftp.as.harvard.edu/gcgrid/data/ExtData/HEMCO/Yuan_XLAI/v2019-03/ <tt>HEMCO/Yuan_XLAI/v2019-03</tt>]
+
  
−
|}
+
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.
  
 +
== Data directories by GEOS-Chem version ==
  
 +
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].
  
−
=== Quick fix to use Yuan-processed MODIS LAI in GEOS-Chem Classic ===
+
{| border=1 cellspacing=0 cellpadding=5
 +
|-bgcolor="#CCCCCC"
 +
!width="150px"|Version
 +
!width="200px"|Chemistry Inputs
 +
!width="200px"|Emissions Inputs
 +
!width="200px"|Initial Conditions
  
−
Bob Yantosca discovered an error when using the Yuan-processed MODIS LAI data in GEOS-Chem "Classic" simulations. HEMCO cannot locate the proper bounding timestamps for the interpolation.
+
|-valign="top" halign="center"
 +
|[[GEOS-Chem 13.4.0]]
 +
|
 +
|
 +
|
  
−
<blockquote>Example: HEMCO should have detected that simulation date '''20160701''' was bounded by data timestamps '''20160624''' and '''20160704''', and should have interpolated accordingly. Instead, HEMCO was detecting that simulation data '''20160701''' was bounded by data timestamps '''20160602''' and '''20160610'''. This is clearly wrong.</blockquote>
+
|-valign="top" halign="center"
 +
|[[GEOS-Chem 13.3.0]]
 +
|
 +
|
 +
|
  
−
Christoph Keller traced this error to routine <tt>GET_TIMEIDX</tt> in module <tt>HEMCO/Core/hcoio_read_std_mod.F90</tt>, which is only used for GEOS-Chem "Classic" simulations. The search algorithm was continuing to look for timestamps further back in time than was necessary.
+
|-valign="top" halign="center"
 +
|[[GEOS-Chem 13.2.0]]
 +
|
 +
|
 +
|
  
−
If you need to run GEOS-Chem simulations with the Yuan-processed MODIS LAI data, Christoph Keller has submitted a quick fix.  Add the IF statement in  <span style="color:green">GREEN</span> to this code in <tt>hcoio_read_std_mod.F90</tt>. This will force the timestamp search algorithm to terminate before it goes too far back in time.
+
|-valign="top" halign="center"
 +
|[[GEOS-Chem 13.1.0]]
 +
|
 +
|
 +
|
  
−
        ! -------------------------------------------------------------
+
|-valign="top"
−
        ! Check if we need to continue search. Even if the call above
+
|[[GEOS-Chem 13.0.0]]
−
        ! returned a time slice, it may be possible to continue looking
+
|[https://github.com/geoschem/input-data-catalogs/blob/7a53a0c19b5972611486a91a4c45433da97ba7c9/ChemistryInputs.csv <tt>ChemistryInputs.csv</tt>]
−
        ! for a better suited time stamp. This is only the case if
+
|[https://github.com/geoschem/input-data-catalogs/blob/7a53a0c19b5972611486a91a4c45433da97ba7c9/EmissionsInputs.csv <tt>EmissionInputs.csv</tt>]
−
        ! there are discontinuities in the time stamps, e.g. if a file
+
|[https://github.com/geoschem/input-data-catalogs/blob/7a53a0c19b5972611486a91a4c45433da97ba7c9/InitialConditions.csv  <tt>InitialConditions.csv</tt>]
−
        ! contains monthly data for 2005 and 2020. In that case, the
+
−
        ! call above would return the index for Dec 2005 for any
+
−
        ! simulation date between 2005 and 2010 (e.g. July 2010),
+
−
        ! whereas it makes more sense to use July 2005 (and eventually
+
−
        ! interpolate between the July 2005 and July 2020 data).
+
−
        ! The IsClosest command checks if there are any netCDF time
+
−
        ! stamps (prior to the selected one) that are closer to each
+
−
        ! other than the difference between the preferred time stamp
+
−
        ! prefYMDhm and the currently selected time stamp
+
−
        ! availYMDhm(tidx1a). In that case, it continues the search by
+
−
        ! updating prefYMDhm so that it falls within the range of the
+
−
        ! 'high-frequency' interval.
+
−
        ! -------------------------------------------------------------
+
−
        ExitSearch = .FALSE.
+
−
        IF ( Lct%Dct%Dta%CycleFlag == HCO_CFLAG_EXACT ) THEN
+
−
          ExitSearch = .TRUE.
+
−
        ELSE IF ( tidx1a > 0 ) THEN
+
−
          ExitSearch = IsClosest( prefYMDhm, availYMDhm, nTime, tidx1a )
+
−
        ENDIF
+
−
        <span style="color:green">!### for testing, only apply to containers with “XLAI” in the name
+
−
        IF ( INDEX( Lct%Dct%Cname, 'XLAI' ) > 0 ) THEN
+
−
          ExitSearch = .true.
+
−
        ENDIF</span>
+
  
−
We will try to add a more robust fix for this issue in the near future.  We did not want to add a fix that was contingent on a HEMCO container name to the standard code.
+
|}
−
 
+
−
NOTE: GCHP is unaffected by this issue, as it uses the MAPL ExtData functionality to read data from disk.  We have verified that GCHP reads in the Yuan-processed MODIS LAI data properly.
+
−
 
+
−
--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 19:23, 7 June 2019 (UTC)
+

Revision as of 14:25, 20 May 2022

On this page we describe the directory tree from which the HEMCO emissions component can read emissions inventories and other atmospheric data sets.

Overview

The 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 data. We 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.

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 section below.

Data directories by GEOS-Chem version

Our repository named input-data-catalogs contains lists of input files needed to run GEOS-Chem simulations. These are contained in the comma-separated files ChemistryInputs.csv, EmissionInputs.csv and InitialConditions.csv. Passing these files to the bashdatacatalog utility will download the data to your local disk storage].

Version Chemistry Inputs Emissions Inputs Initial Conditions
GEOS-Chem 13.4.0
GEOS-Chem 13.3.0
GEOS-Chem 13.2.0
GEOS-Chem 13.1.0
GEOS-Chem 13.0.0 ChemistryInputs.csv EmissionInputs.csv InitialConditions.csv
Retrieved from "https://wiki.seas.harvard.edu/geos-chem/index.php?title=Sandbox&oldid=50836"