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
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
Overview table for the owner and an approver of this feature
1.Name | New Improvements to Aerosols and Clouds |
| 2.Owner | Hailong Wang |
| 3.Created | |
| 4.Equ | |
| 5.Ver | |
| 6.Perf | |
| 7.Val | |
| 8.Approver | Shaocheng Xie |
| 9.Approved Date |
Title: New Improvements to Aerosols and Clouds
Requirements and Design
ACME Atmosphere Group
Date:
Summary
- 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_REMVOE)
- 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 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 MAM treatment of H2SO4 vapor production and loss to use a parallel time-split approach, instead of a serial time-split approach.
- Implement a new treatment of trace gas removal
- Implement a new sub-grid parameterization of the characteristic updraft velocity, assuming a Gaussian distribution for the sub-grid variation of vertical velocities.
- Modify the ice nucleation scheme to consider the impact of pre-existing ice crystals
- Add a classical-nucleation-theory based parameterization for mixed-phase clouds
- Add a temperature dependent threshold size for auto conversion of cloud ice to snow
Date last modified:
Contributors: Hailong Wang, Richard Easter (Unlicensed), Kai Zhang
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, see
- For GAS_WET_REMOVE, to be documented
- For PREICE, see Shi et al. (2015)
- For CNT, see Wang et al. (2014)
- For WSUB, to be documented
- For DCS, to be documented
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?