Parameter Command: Difference between revisions
Jump to navigation
Jump to search
Foxchameleon (talk | contribs) No edit summary |
Foxchameleon (talk | contribs) No edit summary |
||
Line 9: | Line 9: | ||
---- | ---- | ||
{| | {| | ||
| style="width: | | style="width:250px" | '''$tag ''' || integer tag identifying the parameter. | ||
|- | |- | ||
| '''<specific object arguments>''' || depend on the object in the FE model encapsulating the desired parameters. | | '''<specific object arguments>''' || depend on the object in the FE model encapsulating the desired parameters. |
Revision as of 21:32, 11 January 2011
- Sensitivity_Command_Manual
- In DDM-based FE response sensitivity analysis, the sensitivity parameters can be material,
- geometry or discrete loading parameters. Each parameter should be defined as:
parameter $tag <specific object arguments> |
$tag | integer tag identifying the parameter. |
<specific object arguments> | depend on the object in the FE model encapsulating the desired parameters. |
Note: Each parameter must be unique in the FE domain, and all parameter tags must be numbered sequentially starting from 1.
- For example,
- To identify the elastic modulus, E, of the material 1 at section 3 of element 4, the <specific object arguments> string becomes
parameter 1 element 4 section 3 material 1 E
- To identify the elastic modulus, E, of elastic section 3 of element 4 (for elastic section, no specific material need to be
defined), the <specific object arguments> string becomes:
- parameter 1 element 4 section 3 E
- To parameterize E for element 4 with material 1 (no section need to be defined), the <specific object arguments> string
simplifies as:
- parameter 1 element 4 material 1 E
- Notice that the format of the <specific object arguments> is different for each considered element/section/material. The user is : referred to the corresponding section of this manual for the specific set of parameters and the relative <specific object
- arguments> format.