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, 
- competed, 
- in progress, 
- not done
Overview table for the owner and an approver of this feature
1.Description | Topographic downscaling, as implemented within the land component |
| 2.Owner | Ruby Leung |
| 3.Created | |
| 4.Equ | |
| 5.Ver | |
| 6.Perf | |
| 7.Val | |
| 8.Approver | Peter Thornton, William Riley (Unlicensed) |
| 9.Approved Date |
Title: Implement topographic downscaling within ACME Land Model, with connections to atmosphere effort through coupler
Requirements and Design
ACME Land Group
Date:
Summary
This task includes:
1) Testing two approaches to represent subgrid topography (elevation, slope, and aspect) and select an optimal approach to balance the ability to capture subgrid variability of topography with computational efficiency.
2) Discuss with the land and atmosphere team the selection of approaches to inform the design of model data structure and coupling method to support the implementation of subgrid topography in ALM and CAM.
3) Develop input datasets needed to implement subgrid topography in ALM and CAM. These include (a) delineation of watersheds at 1/8 degree resolution (for the original design), (b) fractional area, mean elevation, slope, and aspect of each subgrid topographic landunit within each model grid (which can be the 1/8 degree watershed or the CAM-SE grid), (c) dominant soil texture for each subgrid topographic landunit, (d) fractional area of each PFT within each subgrid topographic landunit, (e) elevation profile within each subgrid topographic landunit to support inundation modeling, and (f) information needed to map between the ALM and CAM subgrid topographic classes (not needed for the fallback plan in which CAM and ALM share the same grid and subgrid topographic landunits).
Requirements
Requirement: name-of-requirement-here
Date last modified: // date
Contributors: @ name (add your name to this list if it does not appear)
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:// date
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: // date
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?