Table 1 summarizes how the value written to the input file is determined for scalar discrete fields.
For prescribed conditions that have multiple degrees of freedom, such as displacements, prescribed condition discrete fields are used; and evaluating the discrete field becomes more complex. For prescribed conditions where you can activate the individual degrees of freedom, only the active degrees of freedom in the prescribed condition are considered; any degree of freedom that is not active in the prescribed condition will be ignored. The magnitudes specified for each degree of freedom in the prescribed condition are multiplied by either the magnitude specified in the discrete field or the default value for that degree of freedom in the discrete field. For example, if you define a displacement boundary condition, as shown in Figure 1, for Node-set-1 (containing nodes Part-2–1.10, Part-2–1.20, and Part-2–1.30) and a prescribed condition discrete field, as shown in Figure 2, the values that are submitted to the input file are shown in Table 2. Figure 1. Displacement boundary condition with two degrees of freedom
activated.
Figure 2. Prescribed condition discrete field used to define a spatially varying
displacement boundary condition.
Degrees of freedom for boundary conditions and predefined fields that result in a zero magnitude are written to the input file as such; however, degrees of freedom for loads that result in zero magnitudes are not written to the input file. When creating discrete fields that will be used with assembly-level and history objects, such as loads or interactions, you must specify the complete name of the node or element numbers, as described in Naming conventions. |