...

Page Properties
id Feature_PR
Info Overview table for the owner and an approver of this feature 1.Description General basal friction law for MALI 2.Owner Matt Hoffman 3.Created July 30, 2019 4.Equ 5.Ver 6.Perf 7.Val 8.Approver Stephen Price 9.Approved Date

...

• Weertman: 

  Mathblock
  anchor weertman
  \tau_d = C_q N^p u^{1/m}N |u|^{q-1} u

  
  

• Schoof

  Mathblock
  anchor schoof
  \tau_d = \mu N \left( \frac{|u|^{q-1}}{\left(|u| + \lambdaLambda A N^n} \right) ^{1/n}q}} u

  
  

• Plastic

  Mathblock
  anchor plastic
  \tau_d = \muC N

This can be accomplished with the Schoof form.  To use the Weertman form, set ....  To use the plastic form, set 

• |u|^{-1} u

  
  

Each requirement is to be listed under a ”section” heading, as there will be a one-to-one correspondence between requirements, design, proposed implementation and testing. Requirements should not discuss technical software issues, but rather focus on model capability. To the extent possible, requirements should be relatively independent of each other, thus allowing a clean design solution, implementation and testing plan.

Algorithmic Formulations

Design solution:

...

Basal friction law that can take the form of Weertman, Schoof, or plastic friction laws

Date last modified:

...

July 30, 2019
Contributors: Matt Hoffman

This can be accomplished with the Schoof form.  To use the Weertman form, set

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:

...

 Basal friction law that can take the form of Weertman, Schoof, or plastic friction laws

Date last modified

...

: July 30, 2019 
Contributors: Matt Hoffman

All the basal friction laws considered can take the form

\tau_d = \beta(|u|) u

where \beta is given by

• power law: 

  Mathblock
  anchor existing
  \beta(|u|) = C N |u|^{q-1}

  
  

• schoof law:

  Mathblock
  anchor existing
  \beta(|u|) = \mu N \frac{|u|^{q-1}}{\left(|u| + \Lambda A N^n \right)^{q}}

  
  

• Plastic:

  Mathblock
  anchor existing
  \beta(|u|) = C N |u|^{-1}

  
  

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:

...

  July 30, 2019
Contributors: 

...

Matt Hoffman

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:

...

 Basal friction law that can take the form of Weertman, Schoof, or plastic friction laws

Date last modified: July 30, 2019

Contributors: 

...

Matt Hoffman

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:

...

 Basal friction law that can take the form of Weertman, Schoof, or plastic friction laws

Date last modified: July 30, 2019
Contributors: 

...

Matt Hoffman

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?