Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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

 Click here for instructions to fill up the table below ......

The first table in Design Document gives overview of this document, from this info the Design Documents Overview page is automatically created.

In the overview table below 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation

  • Equations: Document the equations that are being solved and describe algorithms
  • Verification Plans: Define tests that will be run to show that implementation is correct and robust. Involve unit tests to cover range of inputs as well as benchmarks.
  • Performance expectations: Explain the expected performance impact from this development
  • Validation Plans: Document what process-based, stand-alone component, and coupled model runs will be performed, and with what metrics will be used to assess validity

Use the symbols below (copy and paste) to indicate if the section is in progress or done or not started.

In the table below 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation,   (tick) - competed, (warning) - in progress, (error) - not done


Overview table for the owner and an approver of this feature

1.Description

This is a descriptive long title
2.OwnerHongyi Li
3.Created 
4.Equ(error)
5.Ver(error)
6.Perf(error)
7.Val(error)
8.Approver
9.Approved Date
V2.0
 Click here for Table of Contents ...

Table of Contents




Title: Mosart Sediment

Requirements and Design

E3SM BGC Group

Date:    

Summary

The riverine suspended sediment capacity is added to the E3SM BGC system. The new code simulates the suspended sediment fluxes from hillslopes into small rivers then through the river systems to the coasts. It also simulates the riverine sediment transport, erosion and deposition processes as function of hydraulic conditions simulated by MOSART-water. The success of the code would be satisfactory performance evaluated against the observed sediment discharges over multiple river gauges in different river systems. 

Requirements

Requirement: Implementing riverine sediment process description on top of ELM soil erosion (Zeli Tan), MOSART-water and water management.

Date last modified: Jun 30 2019
Contributors: Hongyi LiZeli TanTian ZhouRuby Leung


MOSART-sediment has been developed and tested offline in a data-land mode based on the apcraig/mosart/add-inundation branch which was based off the E3SM v1 master branch a while ago. I will create a new MOSART-sediment branch based on the merger of two new branches tizhou/mosart/add-wm-inundation and tanzeli/lnd/elm-erosion-master. The former is based off the latest E3SM v2 master branch and includes the newest code of MOSART-water and water management. The latter is also based off the latest E3SM v2 master branch and includes the newest code of soil erosion. 


Requirement: Validating MOSART-sediment

Date last modified: Jun 30 2019
Contributors: Hongyi LiZeli TanTian ZhouRuby Leung

MOSART-sediment simulations will be validated against the observed sediment data from multiple USGS gauges. 


Algorithmic Formulations

Design solution: Riverine sediment processes

Date last modified: Jun 30 2019
Contributors: Hongyi LiZeli TanTian ZhouRuby 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 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?



  • No labels