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.
...
In the table below, 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation, 
- completed, 
- in progress, 
- not done
| HTML Comment |
|---|
|
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
| Expand | |||
|---|---|---|---|
| |||
|
Title: New Improvements to Aerosols and Clouds
...
- Improved treatment of aerosol resuspension from drop evaporation. (RESUSP_TO_COARSE)
- Improved treatment of H2SO4 vapor fro new particle formation. (H2SO4_TIME_SPLIT)
- New treatment of trace gas removal and SO2 solubility. (GAS_WET_REMVOEREMOVE)
- New treatment of sub-grid vertical velocity for ice nucleation (WSUB)
- Parameterization of the impact of pre-existing ice crystals on ice nucleation in cirrus clouds (PREICE)
- Classical-nucleation-theory based parameterization for mixed-phase clouds (CNT)
- New treatment of ice crystal to snow conversion (DCS)
Requirements
- The RESUSP_TO_COARSE: the aerosol wet-scavenging modules are revised to use a more physically-based treatment in which all aerosol material is released to the coarse mode as relatively large particles. This requires a modest increase in the number of transported aerosol species (i.e., coarse-mode BC, POA and SOA)
Modify the H2SO4_TIME_SPLIT: modify the MAM treatment of H2SO4 vapor production and loss to use a parallel time-split approach, instead of a serial time-split approach.
- Implement GAS_WET_REMOVE: Implement a new treatment of trace gas removal
- Implement WSUB: implement a new sub-grid parameterization of the characteristic updraft velocity, assuming a Gaussian distribution for the sub-grid variation of vertical velocities.
- Modify PREICE: modify the ice nucleation scheme to consider the impact of pre-existing ice crystals
- Add CNT: add a classical-nucleation-theory based parameterization for mixed-phase clouds
- Add DCS: add a temperature dependent threshold size for auto conversion of cloud ice to snow
Date last modified:
13 Sep
Contributors: Hailong Wang, Richard Easter (Unlicensed), Kai Zhang, Balwinder Singh
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
- For RESUSP_TO_COARSE, to be documented.
- For H2SO4_TIME_SPLIT, seeto be documented.
- For GAS_WET_REMOVE, to be documentedsee Neu and Prather (2012)
- For PREICE, see Shi et al. (2015)
- For CNT, see Wang et al. (2014)
- For WSUB, to be documented see this page.
- For DCS, to be documented see this page.
Date last modified:
Contributors: Hailong Wang,
(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.
Richard Easter (Unlicensed), Kai Zhang, Balwinder Singh
Design and Implementation
Implementation:
short-desciption-of-implementation-hereCode design/implementation for all the sub-tasks, except for GAS_WET_REMOVE that will follow an initial implementation to CESM, has been done in separate ACME branches. Closely related implementations will be grouped together for testing and pull request.
Date last modified:
Contributors: Hailong Wang,
(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?
Richard Easter (Unlicensed), Kai Zhang, Balwinder Singh
Planned Verification and Unit Testing
Verification and Unit Testing:
short-desciption-of-testing-hereWe will run tests to verify that the B4B with default model is maintained and results of the new implementation is consistent with our expectations based on the physics and/or with those in the published studies (see references above).
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?
Hailong Wang, Richard Easter (Unlicensed), Kai Zhang, Balwinder Singh
Planned Validation Testing
Validation Testing:
short-desciption-of-testing-hereResults of the ACME model with the new implementations will be validated against those in the published studies (see references above). As documented in our progress reports, for some of the sub-tasks results have been evaluated against in-situ measurements at fixed stations and/or in field campaigns, as well as satellite and ground-based remote sensing data.
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?
Date last modified:
Contributors:
(add your name to this list if it does not appear)Hailong Wang, Richard Easter (Unlicensed), Kai Zhang, Balwinder Singh
Planned Performance Testing
Performance Testing:
short-desciption-of-testing-hereExcept for the RESUSP_TO_COARSE sub-task, in which three additional tracers will increase computational cost by less than 10%, the new implementations are not expected to have significant impact on the computational performance, but we will work with the performance team to get the new implementations in ACME fully tested.
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?