Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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. 

...

Page Properties
idFeature_PR


Info

Overview table for the owner and an approver of this feature

1.Description

River water temperature module of MOSART
2.OwnerHongyi Li
3.Created 
4.Equ(tick)
5.Ver(warning)(tick)
6.Perf(warning)(tick)
7.Val(tick)
8.ApproverKatherine Calvin (Unlicensed)
9.Approved Date 
V2.0




Expand
titleClick here for Table of Contents ...


Panel

Table of Contents

Table of Contents


...

Requirement: Evaluation of MOSART-heat. 

Date last modified: 30 Jun 2019

 
Contributors: Hongyi LiRuby LeungTeklu Tesfa

MOSART-heat has been successfully evaluated over the contiguous U.S. against the observed daily stream temperature at over 320 USGS gauges. For details please refer to Li et al. (2015)

...

Algorithmic Formulations

Design solution: Riverine heat processes

Date last modified: 30 Jun 2019


Contributors: Hongyi LiRuby Leung

This is a completely new capacity added into E3SM/MOSART. All the heat processes are described in a physically-based way. The advective heat fluxes are estimated based on the advective water fluxes including the surface and subsurface runoff from hillslopes into the sub-network channel, from sub-network channel to main channel, and between upstrean/downstream main channels. The temperature of surface runoff is assumed to be equal to the average soil temperature (simulated by ELM) over the top 10cm soil layers. The temperature of subsurface runoff is assumed to be equal to the average soil temperature of those soil layers below the ground water table (simulated by ELM). The temperature of sub-network and main channel water is estimated based on the heat balance, including long-wave and short-wave solar radiation, sensible heat, latent heat and advective heat fluxes etc.


Design and Implementation

Implementation: Implementing riverine heat processes

Date last modified: 30 Jun 2019

 
Contributors: Ruby LeungHongyi LiAnthony Craig


The implementation of MOSART-heat within E3SM largely follows the software engineering protocols used in E3SMv2 of MOSART, One major difference comparing to the version in Li et al. (2015) is that now MOSART is established NOT as part of ELM or CLM anymore, but a E3SM component parallel to ELM. As such,  the coupling between MOSART-heat and ELM and EAM is achieved through the flux coupler directly.   


Planned Verification and Unit Testing 

Verification and Unit Testing: Verifying MOSART-heat

Date last modified:  

30 Jun

03 Sep 2019


Contributors: Hongyi LiTian Zhou


Verification is performed by checking the fields that are passed from ELM and EAM to MOSART-heat through the flux coupler. MOSART-heat has been tested on Constance and Compy and passed the E3SM_developer tests on Compy.

Planned Validation Testing 

Validation Testing: Validating MOSART-heat

Date last modified: 

30 Jun

03 Sep 2019


Contributors: Hongyi LiRuby Leung


Validation is performed by comparing the MOSART-heat simulated has been validated over the U.S. domain against the observed stream temperature with observations data from multiple river gaugesUSGS gauges (see Li et al., 2015). The global validation against the observations also shows satisfactory results.

Li, H.-Y.*, L. Ruby Leung, T. Tesfa, N. Voisin, M. Hejazi, L. Liu, Y. Liu, J. Rice, H. Wu, and X. Yang (2015), Modeling stream temperature in the Anthropocene: An earth system modeling approach, J. Adv. Model. Earth Syst., 7, doi:10.1002/2015MS000471.

Planned Performance Testing 

Performance Testing: MOSART-heat performance

Date last modified:

30 Jun

03 Sep 2019
Contributors: Hongyi Li

Tian ZhouPerformance will be evaluated using different number of processors on Compy.


ELM-MOSART-heat has been run globally w/o water management option on Constance using 144 cores during a historical period 1972-2004. The total running time is ~47 hours with the water management option, and is ~45 hours without it.