Mechanical APDL Basic Analysis Guide - Ansys
Mechanical APDL Basic Analysis Guide - Ansys Mechanical APDL Basic Analysis Guide - Ansys
Chapter 8:The Time-History Postprocessor (POST26) You define the variable according to the result item in the results file. This means setting up pointers to the result item and creating labels for the areas where this data will be stored. For example, the following commands define time-history variables two, three and four: NSOL,2,358,U,X,UX_at_node_358 ESOL,3,219,47,EPEL,X, Elastic_Strain ANSOL,4,101,S,X ,Avtg_Stress_101 Variable two is a nodal result defined by the NSOL command. It is the UX displacement at node 358. Variable three is an element result defined by the ESOL command. It is the X component of elastic strain at node 47 for element 219. Variable four is an averaged element nodal result defined by the ANSOL command. It is the X-component of averaged element nodal stress at node 101. Any subsequent reference to these result items will be through the reference numbers or labels assigned to them. Defining a new variable with the same number as an existing variable overwrites the existing variable. The following commands are used to define variables: Commands used to define variables ANSOL GAPF EDREAD LAYERP26* SHELL* * Commands that define result location ESOL NSOL SOLU FORCE* RFORCE The second part is storing the variables (the STORE command). Storing means reading the data from the results file into the database. In addition to the STORE command, the program stores data automatically when you issue display commands (PLVAR and PRVAR) or time-history data operation commands (ADD, QUOT, etc.). An example of using the STORE command follows: /POST26 NSOL,2,23,U,Y ! Variable 2 = UY at node 23 SHELL,TOP ! Specify top of shell results ESOL,3,20,23,S,X ! Variable 3 = top SX at node 23 of element 20 PRVAR,2,3 ! Store and then print variables 2 and 3 SHELL,BOT ! Specify bottom of shell results ESOL,4,20,23,S,X ! Variable 4 = bottom SX at node 23 of element 20 STORE ! By command default, place variable 4 in memory with 2 and 3 PLVAR,2,3,4 ! Plot variables 2,3,4 In some situations, you will need to explicitly request storage using the STORE command (Main Menu> TimeHist Postpro> Store Data). These situations are explained below in the command descriptions. If you use the STORE command after issuing the TIMERANGE command or NSTORE command (the GUI equivalent for both commands is Main Menu> TimeHist Postpro> Settings> Data), then the default is STORE,NEW. Otherwise, it is STORE,MERGE as listed in the command description below. This change in command default is required since the TIMERANGE and NSTORE commands redefine time (or frequency) points and time increment for data storage. You have the following options for storing data: MERGE Adds newly defined variables to previously stored variables for the time points stored in memory. This is useful if you wish to store data using one specification (FORCE, SHELL, LAYERP26 commands) and store data using another specification; see the example above. NEW Replaces previously stored variables, erases previously calculated variables, and stores newly defined variables with current specifications. 194 Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
APPEND Appends data to previously stored variables. That is, if you think of each variable as a column of data, the APPEND option adds rows to each column. This is useful when you want to "concatenate" the same variable from two files, such as in a transient analysis with results on two separate files. Use the FILE command (Main Menu> TimeHist Postpro> Settings> File) to specify result file names. ALLOC,N Allocates space for N points (N rows) for a subsequent storage operation. Previously stored variables, if any, are zeroed. You normally do not need this option, because the program determines the number of points required automatically from the results file. Notes: • By default, batch mode allows you to define up to ten variables. Use the NUMVAR command to increase the number of variables up to the available 200. • Time or Frequency will always be variable 1 • By default, the force (or moment) values represent the total forces (sum of the static, damping, and inertial components). The FORCE command allows you to work with the individual components. Note The FORCE command only affects the output of element nodal forces. • By default, results data for shell elements and layered elements are assumed to be at the top surface of the shell or layer. The SHELL command allows you to specify the top, middle or bottom surface. For layered elements, use the LAYERP26 and SHELL commands to indicate layer number and surface location, respectively. • Other commands useful when defining variables are: – NSTORE - defines the number of time points or frequency points to be stored. – TIMERANGE - defines the time or frequency range in which data are to be stored. – TVAR - changes the meaning of variable 1 from time to cumulative iteration number. – VARNAM - assigns a name (32 character max.) to a variable. – RESET - removes all variables and resets all specifications to initial defaults. 8.4. Processing Your Variables to Develop Calculated Data Often, the specific analysis data you obtain in your results file can be processed to yield additional variable sets that provide valuable information. For example, by defining a displacement variable in a transient analysis, you can calculate the velocity and acceleration by taking derivatives with respect to time. Doing so will yield an entirely new variable that you may wish to analyze in conjunction with your other analysis data. 8.4.1. Interactive The variable viewer provides an intuitive calculator interface for performing calculations. All of the command capability can be accessed from the calculator area. The calculator can be displayed or hidden by clicking on the bar above the calculator area. Follow these steps to process your time history data using the variable viewer: Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates. 8.4.1. Interactive 195
- Page 159 and 160: 7.2.1.6. Particle Flow and Charged
- 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
- Page 209: 1. Click on the Add Data button. Re
- Page 213 and 214: !derivative of variable 2 with resp
- Page 215 and 216: The above command assumes that you
- Page 217 and 218: When plotting complex data such as
- Page 219 and 220: Sample Output from EXTREM time-hist
- Page 221 and 222: 5. Select the variables to be opera
- Page 223 and 224: RESP requires two previously define
- Page 225 and 226: Chapter 9: Selecting and Components
- Page 227 and 228: Note Crossover commands for selecti
- Page 229 and 230: would put UX and UZ constraints on
- Page 231 and 232: The Command Reference describes the
- Page 233 and 234: Chapter 10: Getting Started with Gr
- Page 235 and 236: Remote Network Access Hidden Line R
- Page 237 and 238: 10.4.1. Adjusting Input Focus To en
- Page 239 and 240: • If the environment variable SB_
- Page 241 and 242: 10.5.5. Erasing the Current Display
- Page 243 and 244: Chapter 11: General Graphics Specif
- Page 245 and 246: 11.3.1. Changing the Viewing Direct
- Page 247 and 248: 11.4. Controlling Miscellaneous Tex
- Page 249 and 250: 11.4.3. Controlling the Location of
- Page 251 and 252: Chapter 12: PowerGraphics Two metho
- Page 253 and 254: The subgrid approach affects both t
- Page 255 and 256: Chapter 13: Creating Geometry Displ
- Page 257 and 258: Figure 13.1 Element Plot of SOLID65
- Page 259 and 260: 13.2.1.12. Vector Versus Raster Mod
Chapter 8:The Time-History Postprocessor (POST26)<br />
You define the variable according to the result item in the results file. This means setting up pointers to the<br />
result item and creating labels for the areas where this data will be stored. For example, the following<br />
commands define time-history variables two, three and four:<br />
NSOL,2,358,U,X,UX_at_node_358<br />
ESOL,3,219,47,EPEL,X, Elastic_Strain<br />
ANSOL,4,101,S,X ,Avtg_Stress_101<br />
Variable two is a nodal result defined by the NSOL command. It is the UX displacement at node 358. Variable<br />
three is an element result defined by the ESOL command. It is the X component of elastic strain at node 47<br />
for element 219. Variable four is an averaged element nodal result defined by the ANSOL command. It is<br />
the X-component of averaged element nodal stress at node 101. Any subsequent reference to these result<br />
items will be through the reference numbers or labels assigned to them. Defining a new variable with the<br />
same number as an existing variable overwrites the existing variable. The following commands are used to<br />
define variables:<br />
Commands used to define variables<br />
ANSOL<br />
GAPF<br />
EDREAD<br />
LAYERP26*<br />
SHELL*<br />
* Commands that define result location<br />
ESOL<br />
NSOL<br />
SOLU<br />
FORCE*<br />
RFORCE<br />
The second part is storing the variables (the STORE command). Storing means reading the data from the<br />
results file into the database. In addition to the STORE command, the program stores data automatically<br />
when you issue display commands (PLVAR and PRVAR) or time-history data operation commands (ADD,<br />
QUOT, etc.).<br />
An example of using the STORE command follows:<br />
/POST26<br />
NSOL,2,23,U,Y ! Variable 2 = UY at node 23<br />
SHELL,TOP ! Specify top of shell results<br />
ESOL,3,20,23,S,X ! Variable 3 = top SX at node 23 of element 20<br />
PRVAR,2,3 ! Store and then print variables 2 and 3<br />
SHELL,BOT ! Specify bottom of shell results<br />
ESOL,4,20,23,S,X ! Variable 4 = bottom SX at node 23 of element 20<br />
STORE ! By command default, place variable 4 in memory with 2 and 3<br />
PLVAR,2,3,4 ! Plot variables 2,3,4<br />
In some situations, you will need to explicitly request storage using the STORE command (Main Menu><br />
TimeHist Postpro> Store Data). These situations are explained below in the command descriptions. If you<br />
use the STORE command after issuing the TIMERANGE command or NSTORE command (the GUI equivalent<br />
for both commands is Main Menu> TimeHist Postpro> Settings> Data), then the default is STORE,NEW.<br />
Otherwise, it is STORE,MERGE as listed in the command description below. This change in command default<br />
is required since the TIMERANGE and NSTORE commands redefine time (or frequency) points and time increment<br />
for data storage. You have the following options for storing data:<br />
MERGE<br />
Adds newly defined variables to previously stored variables for the time points stored in memory. This<br />
is useful if you wish to store data using one specification (FORCE, SHELL, LAYERP26 commands) and<br />
store data using another specification; see the example above.<br />
NEW<br />
Replaces previously stored variables, erases previously calculated variables, and stores newly defined<br />
variables with current specifications.<br />
194<br />
Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />
of ANSYS, Inc. and its subsidiaries and affiliates.