...
| Page Properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|
...
Title: UNICON convection
Requirements and Design
ACME Atmosphere Group
Group
Date:
Summary
Requirements
Requirement: name-of-requirement-here
Contributors: (add your name to this list if it does not appeartask to implement and evaluate a new convective parameterization scheme - UNified CONvection scheme by Sungsu Park (Unlicensed) at NCAR in ACME. There are noticeable improvements using UNICON in terms of mean climate, climate variabilities including Madden Julian Oscillation (MJO) and diurnal cycle of precipitation, and so on. We want to implement this new scheme into the ACME master and do series of evaluations.
Requirements
Requirement 1: Fast track implementation and evaluation were done successfully. We found a couple of implementation errors and fixed. Also, we found an issue with new tracers in UNICON and SE dycore. A fix was implemented.
Date last modified:
Contributors: Jin-Ho Yoon (Unlicensed), Sungsu Park (Unlicensed), Hailong Wang, Po-Lun Ma, Mark Taylor, Phil Rasch (pnl.gov)
Requirement 2: Slow track implementation is discussed.
Date last modified:
Contributors: Jin-Ho Yoon (Unlicensed), Sungsu Park (Unlicensed), Hailong Wang, Po-Lun Ma, Mark Taylor, Phil Rasch (pnl.gov)
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
Date last modified:
Contributors: (add your name to this list if it does not appear)
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
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?
...