...
In the table below, 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation, 
- competedcompleted, 
- in progress, 
- not done
| HTML Comment |
|---|
|
...
completed, |
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
| Expand | |||
|---|---|---|---|
| |||
|
...
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, Shaocheng Xie, Wuyin Lin, Balwinder Singh, 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.
Requirement 3: Slow track implementation.
Date last modified:
Contributors: Jin-Ho Yoon (Unlicensed), Sungsu Park (Unlicensed), Hailong Wang, Po-Lun Ma, Shaocheng Xie, Wuyin Lin, Balwinder Singh, Phil Rasch (pnl.gov)
Algorithmic Formulations
Design solution: UNICON design is well documented in Sungsu Park (Unlicensed)'s papers.
Date last modified:
Contributors: Jin-Ho Yoon (Unlicensed), Sungsu Park (Unlicensed)
Design and Implementation
Implementation:
short-desciption-of-implementation-hereFast track implementation
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?
Jin-Ho Yoon (Unlicensed)
Planned Verification and Unit Testing
Verification and Unit Testing: short-desciption-of-testing-hereVerify against UNICON's implementation in CESM1 code base and its behavior.
Verify/Test its compatibility with Polar mods
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:
(add your name to this list if it does not appear)Jin-Ho Yoon (Unlicensed), Hailong Wang, Po-Lun Ma,
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?
Jin-Ho Yoon (Unlicensed), Sungsu Park (Unlicensed), Phil Rasch (pnl.gov), Mark Taylor, Hailong Wang, Po-Lun Ma, Hui Wan, Kai Zhang
The initial implementation has been tested for without considering B4B capability with default ACME, because we are taking a fast track approach for quick evaluation. However, we know how to maintain B4B with default ACME. On the other hand, we rigorously tested for consistencies with NCAR simulation in terms of FV and SE dycores. An earlier issue in SE dycore has been fixed. 10 year fixed SST simulation has been done for UNICON in CESM1 branch with FV dycore (used as a guideline), UNICON in ACME with FV dycore, and UNICON in ACME with SE dycore to ensure all the features are preserved.
Planned Performance Testing
Performance Testing: short-desciption-of-testing-here
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?
Date last modified:
Contributors: Jin-Ho Yoon (Unlicensed),
(add your name to this list if it does not appear)Phil Rasch (pnl.gov), Po-Lun Ma, Hailong Wang, Balwinder Singh
Early results show that UNICON improves simulations of the mean climate, tropical variability, diurnal precipitation, and cloud properties. An early test with UNICON on high vertical resolution shows much less sensitivity, meaning good scale adaptivity and easier tuning. UNICON costs extra 40-50%. We'll work with the performance team to evaluate/improve performance.