Mechanical APDL Basic Analysis Guide - Ansys
Mechanical APDL Basic Analysis Guide - Ansys Mechanical APDL Basic Analysis Guide - Ansys
Chapter 7:The General Postprocessor (POST1) Figure 7.7 PLVECT Vector Plot of Magnetic Field Intensity You can also create your own vector quantity by specifying two or three components on the PLVECT command. 7.2.1.4. Path Plots These are graphs that show the variation of a quantity along a predefined path through the model. To produce a path plot, you need to perform these tasks: 1. Define path attributes using the PATH command (Main Menu> General Postproc> Path Operations> Define Path> Path Status> Defined Paths). 2. Define the points of the path using the PPATH command (Main Menu> General Postproc> Path Operation> Define Path> Modify Path). 3. Map the desired quantity on to the path using the PDEF command (Main Menu> General Postproc> Path Operations> Map onto Path) 4. Use the PLPATH and PLPAGM commands (Main Menu> General Postproc> Path Operations> Plot Path Items) to display the results. More details on this appear later in Mapping Results onto a Path (p. 155). 7.2.1.5. Reaction Force Displays These are similar to boundary condition displays and are activated using the labels RFOR or RMOM on the /PBC command. Any subsequent display (produced by commands such as NPLOT, EPLOT, or PLDISP) will include reaction force symbols at points where DOF constraints were specified. The sum of nodal forces for a DOF belonging to a constraint equation does not include the force passing through that equation. See the Theory Reference for the Mechanical APDL and Mechanical Applications. Like reactions, you can also display nodal forces using labels NFOR or NMOM on the /PBC command (Utility Menu> PlotCtrls> Symbols). These are forces exerted by an element on its node. The sum of these forces at each node is usually zero except at constrained nodes or at nodes where loads were applied. By default, the force (or moment) values that are printed and plotted represent the total forces (sum of the static, damping, and inertial components). The FORCE command (Main Menu> General Postproc> Options for Outp) allows you to separate the total force into individual components. 142 Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
7.2.1.6. Particle Flow and Charged Particle Traces A particle flow trace is a special form of graphics display that shows how a particle travels in a flowing fluid. A charged particle trace is a graphics display that shows how a charged particle travels in an electric or magnetic field. See Creating Geometric Results Displays (p. 249) for more information on graphic displays and see Animation (p. 267) for information on particle trace animation. See the Theory Reference for the Mechanical APDL and Mechanical Applications for simplifying assumptions on electromagnetic particle tracing. A particle flow or charged particle trace requires two functions: 1. The TRPOIN command (Main Menu> General Postproc> Plot Results> Flow Trace> Defi Trace Pt). Either defines a point on the path trajectory (starting point, ending point, or anywhere in between). 2. The PLTRAC command (Main Menu> General Postproc> Plot Results> Flow Trace> Plot Flow Tra). Either produces the flow trace on an element display. Up to 50 points can be defined and plotted simultaneously. A sample PLTRAC plot is shown below. Figure 7.8 A Sample Particle Flow Trace The Item and Comp fields on PLTRAC allow you to see the variation of a specified item (such as velocity, pressure, and temperature for a particle flow trace or electric potential for a charged particle trace). The variation of the item is displayed along the path trajectory as a color-contoured ribbon. Figure 7.9 A Sample Charge Particle Trace in Electric and/or Magnetic Fields Tracing a particle moving in a pure magnetic field might look like this: The path of that particle moving through a pure electric field might look like this: Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates. Notes 143
- Page 107 and 108: applies an equal stress of SX = 100
- Page 109 and 110: 4.7.2. Example: Initial Stress Prob
- Page 111 and 112: inis,defi,all,all,all,all,0.1,,, in
- Page 113 and 114: Chapter 5: Solution In the solution
- Page 115 and 116: Solver Typical Applications * In to
- Page 117 and 118: used. Running the distributed spars
- Page 119 and 120: With all iterative solvers, be part
- Page 121 and 122: 5.3.3. Disk Space (I/O) and Postpro
- Page 123 and 124: If your analysis is either static o
- Page 125 and 126: Note Whether you make changes to on
- Page 127 and 128: Figure 5.2 PGR File Options From th
- Page 129 and 130: GUI: Main Menu> Solution> Current L
- Page 131 and 132: Figure 5.3 Examples of Time-Varying
- Page 133 and 134: Requirements for Performing an Anal
- Page 135 and 136: *dim,temtbl,table,4,1,,time ! Defin
- Page 137 and 138: 5.9.1.1.1. Multiframe Restart Limit
- Page 139 and 140: prnsol finish 5.9.2. VT Accelerator
- Page 141 and 142: 5.12. Stopping Solution After Matri
- Page 143 and 144: Chapter 6: An Overview of Postproce
- Page 145 and 146: each element. Derived data are also
- Page 147 and 148: Chapter 7: The General Postprocesso
- Page 149 and 150: Although not required for postproce
- Page 151 and 152: The ETABLE command documentation li
- Page 153 and 154: • Path plots • Reaction force d
- Page 155 and 156: The PLETAB command contours data st
- Page 157: PLDISP,1 ! Deformed shape superimpo
- Page 161 and 162: • Particle flow traces occasional
- Page 163 and 164: The surfaces you create fall into t
- Page 165 and 166: You can opt to archive all defined
- Page 167 and 168: 19 41.811 51.777 .00000E+00 -66.760
- Page 169 and 170: Sample PRETAB and SSUM Output *****
- Page 171 and 172: 7.2.5. Mapping Results onto a Path
- Page 173 and 174: Command(s): PDEF GUI: Main Menu> Ge
- Page 175 and 176: To retrieve path information from a
- Page 177 and 178: 7.2.6. Estimating Solution Error On
- Page 179 and 180: Write Results - You can use the dat
- Page 181 and 182: NOTE: When you append data to your
- Page 183 and 184: EMF - Windows Enhanced Metafile For
- Page 185 and 186: Figure 7.20 The PGR File Options Di
- Page 187 and 188: 7.4.8. Comparing Nodal Solutions Fr
- Page 189 and 190: the effect of the rigid body rotati
- Page 191 and 192: The SADD command (Main Menu> Genera
- Page 193 and 194: To view correct mid-surface results
- Page 195 and 196: To get usable results combine the r
- Page 197 and 198: 7.4.4. Mapping Results onto a Diffe
- Page 199 and 200: • EMF (Main Menu> General Postpro
- Page 201 and 202: 7.4.8.1. Matching the Nodes The Mec
- Page 203 and 204: 7.4.8. Comparing Nodal Solutions Fr
- Page 205 and 206: Chapter 8: The Time-History Postpro
- Page 207 and 208: enables the alternate selections sh
Chapter 7:The General Postprocessor (POST1)<br />
Figure 7.7 PLVECT Vector Plot of Magnetic Field Intensity<br />
You can also create your own vector quantity by specifying two or three components on the PLVECT command.<br />
7.2.1.4. Path Plots<br />
These are graphs that show the variation of a quantity along a predefined path through the model. To<br />
produce a path plot, you need to perform these tasks:<br />
1. Define path attributes using the PATH command (Main Menu> General Postproc> Path Operations><br />
Define Path> Path Status> Defined Paths).<br />
2. Define the points of the path using the PPATH command (Main Menu> General Postproc> Path<br />
Operation> Define Path> Modify Path).<br />
3. Map the desired quantity on to the path using the PDEF command (Main Menu> General Postproc><br />
Path Operations> Map onto Path)<br />
4. Use the PLPATH and PLPAGM commands (Main Menu> General Postproc> Path Operations> Plot<br />
Path Items) to display the results.<br />
More details on this appear later in Mapping Results onto a Path (p. 155).<br />
7.2.1.5. Reaction Force Displays<br />
These are similar to boundary condition displays and are activated using the labels RFOR or RMOM on the<br />
/PBC command. Any subsequent display (produced by commands such as NPLOT, EPLOT, or PLDISP) will<br />
include reaction force symbols at points where DOF constraints were specified. The sum of nodal forces for<br />
a DOF belonging to a constraint equation does not include the force passing through that equation. See<br />
the Theory Reference for the <strong>Mechanical</strong> <strong>APDL</strong> and <strong>Mechanical</strong> Applications.<br />
Like reactions, you can also display nodal forces using labels NFOR or NMOM on the /PBC command (Utility<br />
Menu> PlotCtrls> Symbols). These are forces exerted by an element on its node. The sum of these forces<br />
at each node is usually zero except at constrained nodes or at nodes where loads were applied.<br />
By default, the force (or moment) values that are printed and plotted represent the total forces (sum of the<br />
static, damping, and inertial components). The FORCE command (Main Menu> General Postproc> Options<br />
for Outp) allows you to separate the total force into individual components.<br />
142<br />
Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />
of ANSYS, Inc. and its subsidiaries and affiliates.
Change language