Difference between revisions of "Multi-mission Observation Operator (M2O2)"
Meemong Lee (Talk | contribs) (→Contact information) |
Meemong Lee (Talk | contribs) (→Distribution and Use) |
||
| Line 16: | Line 16: | ||
#Develop a mission-generic assimilation software library that can be easily integrated to atmospheric chemistry transport model (CTM) systems. | #Develop a mission-generic assimilation software library that can be easily integrated to atmospheric chemistry transport model (CTM) systems. | ||
| − | == | + | ==Distribution and Use== |
| − | + | Code for the GCA-M2O2 is distributed through GITLAB, a web interface connected to a GIT server located at ajdoint.colorado.edu. | |
| + | You can access GITLAB at http://adjoint.colorado.edu:8080 after your account is created. Please refer to the Quick guide to GIT described under GEOS-Chem Adjoint wiki page. | ||
| − | + | Even if your office mate has a copy of the code, the best way to obtain the model is to get an account for yourself and download a version from the repository. So please do not copy code directly from others or pass the code along to third parties. This vastly helps with tracking developments and keeping up with model updates. | |
| − | + | ||
| − | + | Use of the GCA-M2O2 code follows standard practice for GEOS-Chem-Adjoint. It is expected that any developments that come of individual applications based on this community model will eventually given back to the community by incorporation of new developments into the standard adjoint code. New development should be submitted to Daven Henze for inclusion in the standard adjoint model code. | |
| − | + | ||
| − | + | Using GIT gives the users the ability to change the code and commit their changes without affecting the main repository hosted at the adjoint.colorado.edu. Users can work with their tuned versions of the code and even create their own tags because GIT acts as a local repository. When ready to submit your update to the community just send Daven Henze your patch and we'll take case of the rest. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 17:55, 24 February 2014
Contact information
- PI : Meemong Lee / Jet Propulsion Laboratory, California Institute of Technology
- Co-Is : Kevin Bowman & Richard Weidner / Jet Propulsion Laboratory, Chris Lynnes /Goddard Space Flight Center, Daven Henze / University of Colorado, Boulder
Overview
The goal of the M2O2 is to create a streamlined interface mechanism between the atmospheric chemistry model developers and the atmospheric sounding mission data providers by infusing mission-generic observation integration technologies developed under the Advanced Information System Technology (AIST) program. The M2O2 addresses a major challenge in utilizing the space-based observations within the atmospheric chemistry modeling and assimilation community, which involves linking between the model analysis and the observed atmospheric state in the level 2 mission data products (L2 data). The state-of-the-practice is to develop an observation operator for each atmospheric component of an atmospheric sounding mission, which often involves laborious data preparation. A wide range of observation operators with its own ad-hoc way of handling L2 data greatly hinders integration of observations from multiple missions. A generic observation operator that provides the link between the model analysis and mission observations requires an automated “assimilation-purpose” data preparation service and representation coordinate transformation.
The scope of the M2O2 is limited to the “adjoint”-based global assimilations of three types of space-based observations, O3, CH4, and CO2 (xCO2) in 3D variational assimilation (3Dvar) and 4D variational assimilation (4D-var) processes. The 3D-var method updates the forecast by integrating the observations where the cost is computed for each assimilation time step over the entire atmospheric layers. The 4D-var method updates the initial condition by optimizing the cost integrated over the assimilation period and over the atmospheric layers. The global assimilation processes employs GEOS-Chem v9-01-01 as the forward model and GEOS-Chem Adjoint v33 as the adjoint model.
The technical objectives of M2O2 include :
- Derive assimilation-ready data products (L2# data) from level-2 mission data products.
- Create a ‘data-to-data’ web-service with configurable requests and mission-sensitive L2# data products.
- Develop a mission-generic assimilation software library that can be easily integrated to atmospheric chemistry transport model (CTM) systems.
Distribution and Use
Code for the GCA-M2O2 is distributed through GITLAB, a web interface connected to a GIT server located at ajdoint.colorado.edu. You can access GITLAB at http://adjoint.colorado.edu:8080 after your account is created. Please refer to the Quick guide to GIT described under GEOS-Chem Adjoint wiki page.
Even if your office mate has a copy of the code, the best way to obtain the model is to get an account for yourself and download a version from the repository. So please do not copy code directly from others or pass the code along to third parties. This vastly helps with tracking developments and keeping up with model updates.
Use of the GCA-M2O2 code follows standard practice for GEOS-Chem-Adjoint. It is expected that any developments that come of individual applications based on this community model will eventually given back to the community by incorporation of new developments into the standard adjoint code. New development should be submitted to Daven Henze for inclusion in the standard adjoint model code.
Using GIT gives the users the ability to change the code and commit their changes without affecting the main repository hosted at the adjoint.colorado.edu. Users can work with their tuned versions of the code and even create their own tags because GIT acts as a local repository. When ready to submit your update to the community just send Daven Henze your patch and we'll take case of the rest.
