Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

The Design Document page provides a description of the algorithms, implementation and planned testing including unit, verification, validation and performance testing. Please read  Step 1.3 Performance Expectations that explains feature documentation requirements from the performance group point of view. 

Design Document

 Click here for instructions to fill up the table below ......

The first table in Design Document gives overview of this document, from this info the Design Documents Overview page is automatically created.

In the table below, 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation

  • Equations: Document the equations that are being solved and describe algorithms
  • Verification Plans: Define tests that will be run to show that implementation is correct and robust. Involve unit tests to cover range of inputs as well as benchmarks.
  • Performance expectations: Explain the expected performance impact from this development
  • Validation Plans: Document what process-based, stand-alone component, and coupled model runs will be performed, and with what metrics will be used to assess validity

Use the symbols below (copy and paste) to indicate if the section is in progress or done or not started.

In the table below, 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation,   (tick) - competed, (warning) - in progress, (error) - not done

 

Overview table for the owner and an approver of this feature

1.Description

Ozone-hole-Linoz-v2: Interactive stratospheric ozone and ozone hole

2.OwnerPhilip Cameron-Smith (Unlicensed)
3.Created 
4.Equ(error)
5.Ver(error)
6.Perf(error)
7.Val(error)
8.ApproverShaocheng XiePhil Rasch (pnl.gov)
9.Approved Date
 Click here for Table of Contents ...

Table of Contents

 

 

 

Title: cameronsmith1/atm/Ozone-hole-Linoz-v2: Interactive stratospheric ozone and ozone hole 

Requirements and Design

ACME Atmosphere Group

Date: 2015-9-4 

Summary

The Antarctic ozone hole changes the solar heating in the atmosphere, and it is fairly well established that this impacts the Southern Annular Mode winds (SAM) and hence surface stress on the ocean and thereby ocean currents that may have implications for sea-ice and ice-sheet melting (ACME v1 cryosphere science driver). 

The interannual variability of the Antarctic ozone hole is quite large, so this variability may impact the probability of warm water reaching the base of the ice-sheets and triggering rapid melting.  

To implement an Antarctic ozone hole that is consistent with the ACME model state and provides variability in the future requires an interactive stratospheric ozone capability.  Specifying stratospheric ozone with monthly-mean data files (the current ACME default) will not provide ozone that is consistent with the model state, and it is not clear how to provide the variability in the future. 

Many stratospheric ozone and ozone-hole capabilities have been developed, but most of them are far too computationally expensive to even consider for the high-resolution ACME v1 cryosphere simulations.  However, there is one scheme (Linoz) which is well tested and computationally fast: it only requires the computational cost of a single advected tracer.

Linoz was developed by Michael Prather's group at UC Irvine, and Linoz-v2 was implemented into CAM in 2008 for the LLNL_super_fast chemical mechanism by Philip Cameron-Smith (Unlicensed) and Daniel Bergmann, and subsequently incorporated into the NCAR trop_mozart mechanism too. 

The goal of this task is to implement Linoz for ACME-v1, and tune it to reproduce the statistics of the historical Antarctic ozone hole. 

Requirements

Requirement: Combine Linoz-v2 and MAM3 in a new chemical mechanism.

Date last modified:    Contributors: Philip Cameron-Smith (Unlicensed) (add your name to this list if it does not appear)

Create a new chemistry mechanism that adds Linoz-v2 to MAM3.

 

Requirement: Implement Linoz-v2 into the default MAM4 chemistry configuration.

Date last modified:    Contributors: Philip Cameron-Smith (Unlicensed) (add your name to this list if it does not appear)

Create a new chemistry mechanism that adds Linoz-v2 to MAM3.   Make this the default for ACME v1 simulations.

 

Requirement: name-of-requirement-here

Date last modified:    Contributors: Philip Cameron-Smith (Unlicensed) (add your name to this list if it does not appear)

Tune simulation to reproduce statistics of Antarctic ozone hole and stratospheric ozone hole (trends and variability).

Algorithmic Formulations

Design solution: short-description-of-proposed-solution-here

Date last modified: 
Contributors: Philip Cameron-Smith (Unlicensed) (add your name to this list if it does not appear)

Linoz-v2 is documented in Hsu and Prather, JGR, 2009 <http://onlinelibrary.wiley.com/doi/10.1029/2008JD010942/abstract>.

Linoz-v1 is documented in McLinden et al., JGR 2000 <http://onlinelibrary.wiley.com/doi/10.1029/2000JD900124/abstract>

The key equation (from Hsu and Prather) is:

f = ozone concentration.

T = local temperature.

c = overhead ozone column.

(P-L) = Net chemical tendency due to production minus loss.

o = Climatological tendency or sensitivity at the model climatological equilibrium point (for the UC-Irvine CTM).

Note: Only a single tracer is needed (f), since c is calculated by integrating f above each grid-point.

 

Design and Implementation

Implementation: short-desciption-of-implementation-here

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

 

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-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?

Planned Validation Testing 

Validation 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? 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?

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?

 


  • No labels