...
Weertman:
Mathblock anchor weertman \tau_d = C_q N |u|^{q-1} uSchoof
Mathblock anchor schoof \tau_d = \mu N \left( \frac{|u|^{q-1}}{left(|u| + \Lambda A N^n} \right) ^{q}} u
Plastic
Mathblock anchor plastic \tau_d = \muC N |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.
...
Date last modified: July 30, 2019
Contributors: Matt Hoffman
Because this All the basal friction law is nonlinear in the sliding velocity, it must be linearized. It thus takes the form:laws considered can take the form
| Mathblock | ||
|---|---|---|
| ||
\tau_d = \left[ \mu N \left(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?
...