The cThe 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.
...
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-hereTesting and comparison of subgrid classification schemes
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-hereRuby Leung; Teklu Tesfa
Two subgrid classifcation schemes, global and local, were implemented over the Columbia River Basin based on the HydroShed DEM data at 90m resolution. The global method used fixed intervals for the subgrid elevation classes, while the local method defines class intervals by percentile areas using elevation profiles. We also compared two types of subgrid structures: geolocated (subbasins/grids divided into contiguous units) and non-geolocated (subbasins/grid divided into spatially non-contiguous units - i.e., percentage areas). Several metrics were used to evaluate the effectiveness of the two methods in capturing the subgrid variability of surface elevation while balancing computational requirements needed to model processes in each subgrid class. The local and non-geolocated approach was selected based on the metrics.
Requirement: Discuss approaches with the atmosphere and land teams
Date last modified: // date
Contributors: Ruby Leung; Teklu Tesfa
Prepared presentations to discuss the approaches and results.
Requirement: Development of input datasets for the subgrid classification schemes
Date last modified: // date
Contributors: Ruby Leung; Teklu Tesfa
First a global DEM dataset was developed by patching together the HydroSHED DEM with DEM data for the high latitude regions, Arctic, and Antarctic, while ensuring smooth transition across data boundaries.
The TauDEM software was extended for use to implement the local and non-geolocated subgrid classification approach.
Scripts were developed to automate the process.
The scripts were applied to generate input data by continents. The first set of input data was developed for the same ALM and CAM grids based on the CAM-SE grid at 1-degree resolution.
Algorithmic Formulations
Design solution: Algorithm to determine subgrid topographic landunits
Date last modified:// date
Contributors: Teklu Tesfa; Ruby Leung
Design solution: Algorithm to calculate metrics to evaluate the subgrid classification schemes
Date last modified:// date
Contributors:
Teklu Tesfa; Ruby Leung
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 solution: Algorithm to define soil texture and PFT classes for each subgrid topographic landunit
Date last modified:// date
Contributors: Teklu Tesfa; Ruby Leung
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-hereVerify subgrid topographic landunits
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:
(add your name to this list if it does not appear)Teklu Tesfa; Ruby Leung
Plot the subgrid topographic landunits over selected continents to visually check for accuracy.
Calculate various statistical measures as a sanity check and to compare the methods.
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?
...