Versions Compared

Old Version 4

changes.mady.by.user Renata McCoy

Saved on

compared with

New Version 5

changes.mady.by.user Qi Tang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Properties
idFeature_PR


Info

Overview table for the owner and an approver of this feature

1.Description

This is a descriptive long titleOzone (O3v2) with tropospheric loss in the lowermost a few layers
2.OwnerQi Tang
3.Created
4.Equ(error)
5.Ver(error)
6.Perf(error)
7.Val(error)
8.Approver
9.Approved Date
V2.0



...

Expand
titleClick here for Table of Contents ...


Panel

Table of Contents

Table of Contents





Title:

...

 Improved ozone (O3v2) with tropospheric loss in the lowermost a few layers

Requirements and Design

E3SM Watercycle Group

Date:

...

   

Summary

The purpose of this section is to summarize what capability is to be added to the ACME Ocean and Ice system through this design process. It should be clear what new code will do that the current code does not. Summarizing the primary challenges with respect to software design and implementation is also appropriate for this section. Finally, this statement should contain general statement with regard to what is “success.”

Requirements

Requirement: name-of-requirement-here

Date last modified: // date  
Contributors: @ name  (add your name to this list if it does not appear)redesigned ozone (O3v2) and algorithms are compatible with and expect the addition of fully interactive tropospheric chemistry that is planned for E3SM V3. It adds the tropospheric ozone loss in the lowermost a few layers (currently set to 4) and removes the resetting to ozone climatology in the troposphere. This changes enables more realistic tropopause changes for simulations such as 4x CO2 and future projections. It also allows us to diagnose the stratosphere troposphere exchange of ozone fluxes, which provide important information about the quality of stratospheric simulations.

Requirements

Requirement: minor changes in the Linoz module and some related physics code

Date last modified:  
Contributors: Qi Tang, Juno Hsu (Unlicensed), Michael J Prather


Each requirement is to be listed under a ”section” heading, as there will be a one-to-one correspondence between requirements, design, proposed imple- mentation and testing. Requirements should not discuss technical software issues, but rather focus on model capability. To the extent possible, require- ments should be relatively independent of each other, thus allowing a clean design solution, implementation and testing plan.


Algorithmic Formulations

Design solution:

short-description-of-proposed-solution-here

Add the ozone e-folding decay to 30 ppb with a 2-day e-folding time. Turn off the resetting to climatology ozone in the troposphere and ozone dry deposition.

Date last modified:

// date

  
Contributors: Qi Tang, 

(add your name to this list if it does not appear)

Juno Hsu (Unlicensed), Michael J Prather


For each requirement, there is a design solution that is intended to meet that requirement. Design solutions can include detailed technical discussions of PDEs, algorithms, solvers and similar, as well as technical discussion of performance issues. In general, this section should steer away from a detailed discussion of low-level software issues such as variable declarations, interfaces and sequencing.


Design and Implementation

Implementation

: short-desciption-of-implementation-here

: Pull requests implemented O3v2 (https://github.com/E3SM-Project/E3SM/pull/3047)

Date last modified: 

// date

 
Contributors: Qi Tang, 

(add your name to this list if it does not appear)

Juno Hsu (Unlicensed), Michael J Prather


This section should detail the plan for implementing the design solution for requirement XXX. In general, this section is software-centric with a focus on software implementation. Pseudo code is appropriate in this section. Links to actual source code are appropriate. Project management items, such as svn branches, timelines and staffing are also appropriate. How do we typeset pseudo code?


Planned Verification and Unit Testing 

Verification and Unit Testing:

short

5-

desciption-of-testing-here

year and 20-year tests

Date last modified:

  How will XXX be tested? i.e. how will be we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?

  
Contributors: Qi Tang, 

(add your name to this list if it does not appear)

Juno Hsu (Unlicensed), Michael J Prather


A 5-year test with O3v2 was done and compared with the 5-year control run with the ozone in E3SMv1. The climate of these two runs are very similar. The O3v2 tropospheric loss looks reasonable and shows signs of approaching a stable state. An extended 20-year test confirmed that the O3v2 was implemented correctly and produced expected results.

Planned Validation Testing 

Validation Testing:

short-desciption-of-testing-here

20-year test and 4x CO2 simulation

Date last modified:  
Contributors: 

(add your name to this list if it does not appear)How will XXX be tested? What observational or other dataset will be used?  i.e. how will be we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?

Qi Tang


The 20-year simulation was complete (as mentioned above). It verifies that the code is implemented correctly and the results are reasonable. A 4x CO2 is planned to verify the O3v2 with larger perturbations and examine the climate sensitivity changes.

Planned Performance Testing 

Performance Testing: short-desciption-of-testing-here

Date last modified:
Contributors: (add your name to this list if it does not appear)


How will XXX be tested? i.e. how will be we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?


...