At the solution (SOLVE) stage of a cyclic symmetry analysis, the program applies the appropriate cyclic symmetry boundary conditions for each harmonic index solution requested (via the CYCOPT command) and solves. The program performs each harmonic index solution as a separate load step.
The following solution architecture topics are available for cyclic symmetry analysis:
The architecture of the cyclic symmetry solution process depends upon how the compatibility and equilibrium conditions of the cyclic sector are enforced in the matrix-solution process. The two most common solution methods are Duplicate Sector and Complex Hermitian. For faster performance, the program uses the Duplicate Sector method.
During the solution stage, the program generates a duplicate sector of elements at the same geometric location as the basic sector. (Duplicate sector creation occurs automatically and transparently.) The program applies all loading, boundary conditions, and coupling and constraint equations present on the basic sector to the duplicate sector.
The program enforces cyclic symmetry compatibility conditions for each harmonic index solution via coupling and/or constraint equations (CEs) connecting the nodes on the low- and high-edge components on the basic and duplicate sectors. The program deletes the coupling and/or constraint equations after each harmonic index solution, preserving any internal coupling and constraint equations that you may have defined on the basic sector for subsequent analyses. The constraint equations for edge-component nodes have the form shown in Equation 3–1.
Note: These internal CEs cannot be listed or viewed after a cyclic symmetry
solution, except by using the Option = CONV on the
CELIST command.
During the solution stage of a cyclic symmetry analysis, the program automatically rotates the nodal coordinate systems of all nodes on the low and high sector edges to be parallel with the cyclic coordinate system.
(3–1) |
where,
N / 2) when
N is even,
(0,1,2,…,(N-1) / 2) when
N is odd. (N is an
integer representing the number of sectors in 360°.) |
|
|
|
|
|
|
|
|
|
|
|
|
The equation is a function of harmonic index k
generating different sets of constraint equations for each harmonic index.
Therefore, for each harmonic index solution requested, the program creates the
appropriate constraint equations automatically, connects the edge-component nodes on
basic sector A and duplicate sector B, and solves.
Constraint equations that tie together the low and high edges of your model are generated from the low- and high-edge components, and nowhere else. You should verify that automatically detected components are in the correct locations and that you are able to account for all components; to do so, you can list (CMLIST) or plot (CMPLOT) the components.
Non-cyclic loading is applicable to static and full harmonic cyclic solutions. A load is non-cyclic when it varies between sectors and involves at least one harmonic index greater than zero. Support is available for cyclic analyses that have some combination of cyclic and non-cyclic loading.
The program considers the arbitrary forces acting on the full system as the sum of a finite number of spatial Fourier harmonics. The program analyzes the structure for each spatial harmonic index by applying constraint equations between the basic sector and duplicate sector. For each spatial Fourier harmonic, the program solves a corresponding equation, then expands and sums the calculated harmonics of the response to give the response for each substructure. For more information, see Cyclic Symmetry Transformations in the Mechanical APDL Theory Reference.
Table 3.1: Valid Non-Cyclically Symmetric Loads
| Non-Cyclic Load Type | Commands | Loads | Comments |
| Nodal Loads |
following the sector specifications
(CYCOPT,LDSECT, |
FX, FY, and FZ |
HFLOW is blocked for sector-restricted loading but can follow afterwards. All other nodal loads are not supported for non-cyclic loading. |
| Surface Loads |
following the sector specifications
(CYCOPT,LDSECT, |
PRES |
CONV is blocked for sector-restriced loading but can follow afterwards. All other surface loads are not supported for non-cyclic loading. |
| Inertia Loads |
Applies to all sectors. (Not affected by
CYCOPT,LDSECT, Default load in global X, Y, and Z on all sectors. |
May require harmonic index 0 and/or 1 only. |
This section is applicable to static and full harmonic cyclic analyses only. For cyclic mode-superposition harmonic analyses, non-cyclic loading is applied in a different manner. For more information, see Mode-Superposition Harmonic Cyclic Symmetry Analysis.
Specify non-cyclically symmetric loading via the LDSECT (load-on-sector) value on the CYCOPT command. A value greater than 0 (the default, indicating that the loads are identical on all sectors) restricts subsequently defined force loads and surface loads to the specified sector. The restriction remains in effect until you change or reset it. Non-cyclic loads are placed in a special *DIM table using SECTOR as its primary variable.
When non-cyclic loading applies, the program creates or modifies the required SECTOR tabular boundary condition (BC) data to apply on the appropriate sector. Therefore, it is not necessary to manipulate tables for situations where the applied BC is not a function of other tabular BC variables such as TIME, X, Y, Z, and so on.
If a SECTOR-varying table exists on an entity-BC combination (for example, node 17 FZ) and you enter another value for the same entity-BC combination (perhaps specifying a different sector on which to apply the load), the following conditions occur:
The program modifies the existing table to accommodate the new specification.
The table cannot reference any other independent variable (for example, TEMP). You must manually define any BC table requiring more than one independent variable.
If a table exists for an entity-BC combination and you enter another table for the same entity-BC combination, but the table does not reference SECTOR, the new table reference replaces the existing one.
During preprocessing, all tabular BC listings and plots referencing SECTOR will list the table names only. During solution or postprocessing, all tabular BC listings and plots referencing SECTOR will list the values per sector as they would be applied when solving (SOLVE).
Any tabular data X, Y, or Z variation applied to a cyclic model may not be applied in the same manner in which such a variation would occur for an equivalent full model (the exception being a variation in the axial direction). For example, if a tabular value of a nodal force is applied as function of the tabular variable Y, the program applies it to the designated cyclic sectors using values based upon the Y values of the basic sector only.
A given high-edge node is usually the same location in the structure as the corresponding low-edge node of the adjacent sector; therefore, it is necessary to apply constraints consistently. Note that inconsistent constraints are impossible to satisfy if the solution remains cyclic. The results can be unpredictable.
If a high (or low)-edge DOF has a constant (non-tabular) constraint, and the corresponding low (or high)-edge DOF is unconstrained, the program copies the constraint to the opposite edge. If a high (or low)-edge DOF has a tabular constraint, and the corresponding low (or high)-edge DOF is unconstrained, the program stops the solution with an error message. If a high-low corresponding pair of DOF are both constrained in any manner, the program assumes that you have specified constraints in a consistent manner.
One warning is issued the first time this is done for a given SOLVE operation.
Because edge nodes are rotated into the cyclic coordinate system during solution, any applied displacements or forces on sector edges will be in the cyclic coordinate system.
CYCOPT,LDSECT,1 ! LOADS ON SECTOR 1 ONLY SFL,ALL,PRES,10000
For DOF constraints, force loads, and body forces, any non-tabular load is cyclic. Any tabular load that does not reference the variable SECTOR is cyclic. The program assumes any tabular load referencing SECTOR to be non-cyclic (although it could be identical on all sectors).
*DIM,S1PRES,TABLE,5,1,1,SECTOR *SET,S1PRES(1,0,1),1,2,3,4,5 *SET,S1PRES(1,1,1),10000,0,0,0,0 ! PRESSURE ON SECTOR 1 ONLY SFL,ALL,PRES,%S1PRES%
When combined with other independent variables, SECTOR can be in positions 1, 2, or 3 only. Other independent variables operate as they do for non-cyclic data. (Think of X, Y, and Z as “ghost” coordinates, behaving as though all sectors have been modeled with actual nodes and elements.)
CYCOPT,LDSECT,3 F,10,UX,value! Apply a load (value) on node 10 at sector 3 ... FDELE,10,UX ! Delete the load on node 10 at sector 3
To delete a previously applied load on a specified sector, issue an FDELE command.
You can plot non-cyclic boundary conditions (BCs) on the sector on which the BC (F, D, SF) is applied. By expanding the cyclic sector model plot to the full 360 degrees (via the /CYCEXPAND command), you can view a BC on the sector on which it is applied.
Issue BC-listing commands FLIST, DLIST, and SFLIST to list non-cyclic BCs. The list indicates the value of the BC and the sector on which it is applied.
You can use graphical picking via the GUI to apply non-cyclic BCs on any sector. The graphical picking option is available after expanding the cyclic model (/CYCEXPAND). Applicable BCs are:
BCs applied by graphical picking ignore the current CYCOPT,LDSECT setting when cyclic expansion (/CYCEXPAND) is active. When cyclic expansion is not active, BCs are applied to the sector specified by CYCOPT,LDSECT (or all sectors if CYCOPT,LDSECT,ALL).
The mathematical characteristics of a cyclic symmetry solution require that displacement BCs (D, DK, DL, DA) apply to all sectors.