...
ACME will be one of the first climate models to include a fully coupled, dynamic ice sheet component. Meshes appropriate for use with the MPAS-LI model, the ice sheet model component in ACME, will need to be added to ACME for: 1) testing purposes, 2) use in configurations where the ice sheet may be dynamically inactive but coupled thermodynamically to the ocean component, and 3) use in configurations with a fully coupled and active ice sheet model component.
Accurate simulation of marine ice sheet dynamics - e.g., retreat and advance of ice sheet grounding lines - requires extremely high spatial grid resolution (>=1km) in limited portions of the computational domain covered by the ice sheet. Use of a 3d, higher-order ice sheet model on a sub-km, uniform resolution mesh of Antarctica is not a computationally efficient approach. As such, the MPAS-Land Ice model allows for the use of variable resolution meshes, to focus spatial resolution and computational power in select regions while simultaneously allowing for low spatial resolution in places of low dynamic complexity. ACME simulations targeting a better understanding of future mass loss from the Antarctic ice sheet will thus require the use of high quality, variable resolutions meshes.
Requirements
Requirement: Coarse, uniform resolution meshes for testing
Date last modified: 2015-9-23
Contributors: Matt Hoffman, Stephen Price
Testing of the new ice sheet and climate model coupling in ACME will require inexpensive, coarse, uniform resolution meshes for the land ice model component.
Requirement: Variable resolution meshes for static ice sheet configurations
Date last modified: 2015-9-23
Contributors: Matt Hoffman, Stephen Price
Some ACME simulations may choose to have an inactive ice sheet component. In this case, we can still allow for thermodynamic coupling between the ocean and ice sheet (e.g., so that the ocean can circulate under static ice shelves and exchange heat and fresh water fluxes with the ice sheet). This will require variable resolution meshes with intermediate spatial dimensions.
Requirement: Variable resolution meshes for active ice sheet configurations
Date last modified: 2015-9-23
Contributors: Matt Hoffman, Stephen Price
Accurate simulation of marine ice sheet dynamics - e.g., retreat and advance of ice sheet grounding lines - requires extremely high spatial grid resolution (>=1km) in limited portions of the computational domain covered by the ice sheet. Use of a 3d, higher-order ice sheet model on a sub-km, uniform resolution mesh of Antarctica is not a computationally efficient approach. As such, the MPAS-Land Ice model allows for the use of variable resolution meshes, to focus spatial resolution and computational power in select regions while simultaneously allowing for low spatial resolution in places of low dynamic complexity. ACME simulations targeting a better understanding of future mass loss from the Antarctic ice sheet will thus require the use of high quality, variable resolutions meshesACME simulations with an active ice sheet component will require variable resolution meshes that allow for this localized high resolution in order to insure accurate simulations of marine ice sheet evolution.
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
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?
...