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 10 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

Uncertainty quantification framework
2.OwnerKhachik Sargsyan, Daniel Ricciuto
3.Created 
4.Equ(warning)
5.Ver(error)
6.Perf(error)
7.Val(error)
8.ApproverPeter Thornton, William Riley (Unlicensed)
9.Approved Date
 Click here for Table of Contents ...

Table of Contents

 

 

 

Title: Uncertainty Quantification Framework

Requirements and Design

ACME Land  Group

Date:  

  

Summary

A set of Python scripts is being included in the ACME Land Model v1 (ALMv1) to perform basic forward uncertainty quantification tasks, such as surrogate model construction and variance-based sensitivity analysis. Besides pre- and post-processing steps, the scripts heavily utilize functionalities of Uncertainty Quantification Toolkit (UQTk) being developed at SNL-CA as a lightweight  C++/Python UQ library. Version 3.0 of UQTk will be available publicly in spring - any time before that the library is available upon request (see http://www.sandia.gov/uqtoolkit/). The general workflow consists of three steps (a) pre-processing: input parameter sampling, (b) ensemble simulation of ALM, (c) post-processing: for each output quantity of interest, build a polynomial surrogate and compute Sobol sensitivity indices.

Requirements


Requirement: Generate input parameter ensemble

Date last modified:     
Contributors: Khachik SargsyanDaniel Ricciuto

Add text here...

 

Requirement: Perform ALM ensemble simulations

Date last modified:     
Contributors:  Daniel Ricciuto

Add text here...

Requirement: Perform ALM ensemble simulations

Date last modified:     
Contributors: Daniel Ricciuto

Add text here...

 

Requirement: Polynomial Chaos surrogate model construction

Date last modified:     
Contributors: Khachik Sargsyan

Add text here...


Requirement: Variance-based uncertainty decomposition

Date last modified:     
Contributors: Khachik Sargsyan

Add text here...

Algorithmic Formulations


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: Generate input parameter ensemble

Date last modified:     
Contributors: Khachik SargsyanDaniel Ricciuto

Add text here...

 

Design solution: Perform ALM ensemble simulations

Date last modified:     
Contributors: Daniel Ricciuto

Add text here...

Design solution: Polynomial Chaos surrogate model construction

Date last modified:     
Contributors: Khachik Sargsyan

Add text here...

Design solution: Variance-based uncertainty decomposition

Date last modified:     
Contributors: Khachik Sargsyan

Add text here...

Design and Implementation

 

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?

Implementation: Generate input parameter ensemble

Date last modified:     
Contributors: Khachik SargsyanDaniel Ricciuto

Add text here...

 

Implementation: Perform ALM ensemble simulations

Date last modified:     
Contributors: Daniel Ricciuto

Add text here...

 

Implementation: Polynomial Chaos surrogate model construction

Date last modified:     
Contributors: Khachik Sargsyan

Add text here...


Implementation: Variance-based uncertainty decomposition

Date last modified:     
Contributors: Khachik Sargsyan

Add text here...

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