Versions Compared

Key

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

...

The purpose of this task is to create a regionally-refined test case for the ACME model.  The refined area covers the continental United States (CONUS) and has the same resolution as the target resolution of the ACME model, 1/4-degree or ne120.   The low resolution area covers the remainder of the globe and is 1-degree, or ne30.  This configuration will enable developers wishing to see how their parameterization performs in high-resolution without having to run at global high-resolution.   This configuration can be used when set-up as a new case by the user.  See How to run the regionally refined model (RRM) for information on how to run with this configuration.   Verification, performance testing, and validation are in progress.
 

Requirements


Requirement: RRM CONUS case configuration

Date last modified:  
Contributors: Erika Roesler Mark TaylorQi TangMark TaylorWuyin Lin Steve Klein

Grid, initial condition, and boundary condition files were uploaded to ACME data repository.  A new case was developed on a feature branch and merged to master.

 

Requirement: RRM CONUS case configuration

Date last modified:  
Contributors:  (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.

 

Requirement: RRM CONUS case configuration

Date last modified:  
Contributors:  (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: 
Contributors: Erika Roesler Mark Taylor, Steve Klein

Grid file was generated and approved by ACME Atmos group.  From this grid file the initial and boundary condition files were generated.   The new case was then configured. 

 

Design and Implementation

Implementation: short-desciption-of-implementation-here

 

Date last modified:  
Contributors:

 (add your name to this list if it does not appear)

Erika Roesler , Wuyin Lin, Qi Tang, Mark Taylor

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: Test CONUS case on other ACME-supported machines

Date last modified:   
Contributors: Erika Roesler , Qi Tang, Wuyin Lin

Members of this group downloaded the feature branch and tested the case on their institutional clusters.  If the case ran for the specified time, then this test and requirement was considered successful.   A unit test for the RRM CONUS case in under consideration. 

 

Planned Validation Testing 

Validation Testing:

short-desciption-of-testing-here

Climatology analysis

Date last modified:  
Contributors: Erika Roesler Mark Taylor Qi TangMark TaylorWuyin Lin Steve Klein

Analysis of the climatology of the CONUS grid is underway. 

(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?

Comparisons will be made with the global uniform resolutions of the ne30 and ne120 (AMIP, v.03) simulations. 

Validation Testing: CAPT testing

Date last modified:  
Contributors: Wuyin Lin, Qi Tang

CAPT tests will be performed as an application of this tool to understand model behavior at high resolution.

Validation Testing: Nudging

Date last modified:  
Contributors: Wuyin Lin, Qi Tang

Nudging tests will be performed as an application of this tool to understand model behavior at high resolution.  See this page for more info on nudging: 

How to perform nudging simulations with the regional refined model (RRM)


Planned Performance Testing 

Performance Testing:

short-desciption-of-testing-here

RRM-CONUS performance testing

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?

Erika Roesler , Qi Tang, Wuyin Lin, Mark Taylor

 

Initial performance tests were performed on institutional clusters to compare the RRM case with global low or global high resolution cases.   The performance of implementing nudging was also investigated here:  /wiki/spaces/ATM/pages/24478405