...
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
...
| Expand | |||
|---|---|---|---|
| |||
|
Title:
...
E3SM Water management and flood inundation
Requirements and Design
E3SM Watercycle Group
Date:
...
Summary
The purpose of this section is to summarize what capability is to be added to the ACME Ocean and Ice system through this design process. It should be clear what new code will do that the current code does not. Summarizing the primary challenges with respect to software design and implementation is also appropriate for this section. Finally, this statement should contain general statement with regard to what is “success.”Date last modified: // date
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.Date last modified:// date
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 This document summarizes the new water management and inundation features to be added to the MOSART component of E3SM. The development of the two new features were led by Nathalie Voisin (Unlicensed) (for WM) and Xiangyu Luo (for inundation) and were merged to one single branch by Anthony Craig when they were coupled with E3SM. It is very hard to separate the two features so they are bundled together as one PR by Tian Zhou. The water management capability (WM) regulates the river streamflow through the representation of spatially distributed water extractions for irrigation as well as flow regulations at dams. Each dam’s operating rules are determined based on historical long-term mean monthly inflow simulated by the models, reservoir characteristics, and reservoir purposes. The flood inundation capability creates a floodplain along the river channel which represents the flood processes when the river water exceeds the capacity of the channel.Requirements
Requirement 1: Implement the water management (WM) capability to MOSART
Date last modified:
Contributors: Nathalie Voisin (Unlicensed) Hongyi Li Tian Zhou Anthony Craig Ruby Leung
Requirement 2: Implement the inundation capability to MOSART
Date last modified:
Contributors: Xiangyu Luo Hongyi Li Tian Zhou Anthony Craig Ruby Leung
Algorithmic Formulations
Requirment 1: In MOSART-WM, water will be extracted from the river channel and upstream reservoir storage to fulfill the water demand calculated by ELM or provided by an external demand term. The location of the reservoirs and the dependency of the water allocation to each reservoir are mapped on the river network. The dam operation follows a generic rule which is determined based on historical long-term mean monthly inflow , reservoir characteristics, and reservoir purposes (flood control, irrigation, combination of flood control and irrigation, and other). For detailed description of the algorithm, see Voisin et. al. 2013.
Voisin, N., Li, H. Y., Ward, D., Huang, M., Wigmosta, M., & Leung, L. R. (2013). On an improved sub-regional water resources management representation for integration into earth system models. Hydrology and Earth System Sciences, 17, 3605-3622. doi:10.5194/hess-17-3605-2013
Date last modified:
Contributors: (Nathalie Voisin (Unlicensed), Ruby Leung )
Requirment 2: In MOSART-inundation, water will enter the floodplain when the water storage exceeds the channel storage defined by the channel geometry. The fraction of the inundation of each gridcell depends on the area-elevation relationship defined by an elevation profile of the gridcell. For detailed description of the algorithm, see Luo et. al. 2017.
Luo, X., Li, H. Y., Ruby Leung, L., Tesfa, T. K., Getirana, A., Papa, F., & Hess, L. L. (2017). Modeling surface water dynamics in the Amazon Basin using MOSART-Inundation v1.0: Impacts of geomorphological parameters and river flow representation. Geoscientific Model Development, 10, 1233-1259. doi:10.5194/gmd-10-1233-2017
Date last modified:
Contributors: (Xiangyu Luo, Ruby Leung )
Design and Implementation
Implementation:
The source code of both features are located in the MOSART component directory.
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?
...