Academia.eduAcademia.edu

Figure 5 – uploaded by Zulham Mochtar

See full PDFdownloadDownload figure
The parameter NTEMP could be an array of temperatures at selected nodes; NTEMP(1) = -47.6 could be the temperature at node 27, NTEMP(2) = -5.2 could be the temperature at node 43, and so on. Similarly, EVOLUM could be an array of element volumes, and COMPSTRS could be an array of nodal component stresses, with each column representing a particular direction (X, Y, Z, XY, YZ, XZ, for example).

Figure 5 The parameter NTEMP could be an array of temperatures at selected nodes; NTEMP(1) = -47.6 could be the temperature at node 27, NTEMP(2) = -5.2 could be the temperature at node 43, and so on. Similarly, EVOLUM could be an array of element volumes, and COMPSTRS could be an array of nodal component stresses, with each column representing a particular direction (X, Y, Z, XY, YZ, XZ, for example).

Related Figures (36)

The following is a complete list of APDL operators:
The following is a complete list of APDL operators:
Figure 3.4: A Graphical Representation of a Table Array As shown in the above example, when configuring a table array you must set
Figure 3.4: A Graphical Representation of a Table Array As shown in the above example, when configuring a table array you must set
Figure 3.5: An Example *VEDIT Dialog Box for an ARRAY
Figure 3.5: An Example *VEDIT Dialog Box for an ARRAY
3.10.5.4. Filling an Array From a Data File Using *VREAD Figure 3.6: An Example *VEDIT Dialog Box for a TABLE You can fill an array from a data file using the *VREAD command (Utility Menu> Parameters> Array Parameters> Read from File). The command reads information from an ASCII data file and begins writing it into the array, starting with the index location that you specify. You can control the format of the inform- ation read from the file through data descriptors. The data descriptors must be enclosed in parenthesis and placed on the line following the *VREAD command. See Vector Operations (p. 35) for more information about data descriptors. The data descriptors control the number of fields to be read from each record, the width of the data fields, and the position of the decimal point in the field.
3.10.5.4. Filling an Array From a Data File Using *VREAD Figure 3.6: An Example *VEDIT Dialog Box for a TABLE You can fill an array from a data file using the *VREAD command (Utility Menu> Parameters> Array Parameters> Read from File). The command reads information from an ASCII data file and begins writing it into the array, starting with the index location that you specify. You can control the format of the inform- ation read from the file through data descriptors. The data descriptors must be enclosed in parenthesis and placed on the line following the *VREAD command. See Vector Operations (p. 35) for more information about data descriptors. The data descriptors control the number of fields to be read from each record, the width of the data fields, and the position of the decimal point in the field.
In ANSYS, you define a TABLE parameter "Ttx" using the *DIM command (Utility Menu> Parameters> Arra Parameters> Define/Edit). Specify 4 rows, 5 columns, 1 plane, row label of TIME, and column label of X- COORD. Note that the data table you created has four rows and five columns of data, plus the row and column index values. Then read in the file as described earlier, specifying 2 skipped lines. The TABLE array in ANSYS would look like this: For this example, create (in a spreadsheet application, a text editor, etc.) a 2-D table named "T2data" con- taining temperature data as a function of time and x-coordinate and read it into a TABLE array parameter called "Ttx." The table, in its ASCII form, would look like this:
In ANSYS, you define a TABLE parameter "Ttx" using the *DIM command (Utility Menu> Parameters> Arra Parameters> Define/Edit). Specify 4 rows, 5 columns, 1 plane, row label of TIME, and column label of X- COORD. Note that the data table you created has four rows and five columns of data, plus the row and column index values. Then read in the file as described earlier, specifying 2 skipped lines. The TABLE array in ANSYS would look like this: For this example, create (in a spreadsheet application, a text editor, etc.) a 2-D table named "T2data" con- taining temperature data as a function of time and x-coordinate and read it into a TABLE array parameter called "Ttx." The table, in its ASCII form, would look like this:
This same example, done via command input, would look like the following:
This same example, done via command input, would look like the following:
In ANSYS, you define a TABLE parameter "Ttxy" using the *DIM command (Utility Menu> Parameters> Array Parameters> Define/Edit). In the case of a 3-D table, the table is dimensioned according to the number of rows, columns, and planes of data. The first column (TIME) is the row index values and the first row is the column index values. Specify 4 rows, 5 columns, 2 planes, row label of TIME, column label of X- COORD, and plane label of Y-COORD. Note that the data table you created has four rows and five columns
In ANSYS, you define a TABLE parameter "Ttxy" using the *DIM command (Utility Menu> Parameters> Array Parameters> Define/Edit). In the case of a 3-D table, the table is dimensioned according to the number of rows, columns, and planes of data. The first column (TIME) is the row index values and the first row is the column index values. Specify 4 rows, 5 columns, 2 planes, row label of TIME, column label of X- COORD, and plane label of Y-COORD. Note that the data table you created has four rows and five columns
Figure 3.8: A Sample 2-D TABLE Array Dialog Box This same example, done via command input, would look like the following:
Figure 3.8: A Sample 2-D TABLE Array Dialog Box This same example, done via command input, would look like the following:
Figure 3.9: A Sample 3-D TABLE Array Dialog Box
Figure 3.9: A Sample 3-D TABLE Array Dialog Box
Figure 3.10: Time-History Forcing Function
Figure 3.10: Time-History Forcing Function
In the following example, the result array is first dimensioned (Z1). The *VOPER command then adds columr 2 of X to column 1 of Y, both starting at row 1, and then places the result into Z1. Notice that the starting location (the row and column index numbers) must be specified for all array parameters. The operation ther progresses sequentially down the specified vector. The examples below illustrate the use of some of these commands. Refer to the Command Reference for syntactical information about these commands. For all of the following examples, the array parameters (of type ARRAY) X, Y, and THETA have been dimensioned and defined.
In the following example, the result array is first dimensioned (Z1). The *VOPER command then adds columr 2 of X to column 1 of Y, both starting at row 1, and then places the result into Z1. Notice that the starting location (the row and column index numbers) must be specified for all array parameters. The operation ther progresses sequentially down the specified vector. The examples below illustrate the use of some of these commands. Refer to the Command Reference for syntactical information about these commands. For all of the following examples, the array parameters (of type ARRAY) X, Y, and THETA have been dimensioned and defined.
The following table lists the various specification commands and the vector and matrix array commands that they affect. In the following, the results array (CMPR) is dimensioned. The two *VFUN commands, in conjunction with the preceding *VMASK and *VLEN commands, then compress selected data and write them to specified locations in CMPR. The complement to the COMP operation is the EXPA operation on the *VFUN command.
The following table lists the various specification commands and the vector and matrix array commands that they affect. In the following, the results array (CMPR) is dimensioned. The two *VFUN commands, in conjunction with the preceding *VMASK and *VLEN commands, then compress selected data and write them to specified locations in CMPR. The complement to the COMP operation is the EXPA operation on the *VFUN command.
Figure 3.11: Sample Plot Using *VPLOT, ,arrayval(1,1) ,2 Figure 3.12: Sample Plot Using *VPLOT, , tableval (1,1) , 2 The following are example *VPLOT commands and their resulting plots. Note that since ARRAY data is un ordered it is plotted as a histogram; TABLE data is ordered and is therefore plotted as a curve.
Figure 3.11: Sample Plot Using *VPLOT, ,arrayval(1,1) ,2 Figure 3.12: Sample Plot Using *VPLOT, , tableval (1,1) , 2 The following are example *VPLOT commands and their resulting plots. Note that since ARRAY data is un ordered it is plotted as a histogram; TABLE data is ordered and is therefore plotted as a curve.
Figure 3.14: Sample Plot Using *VPLOT, tableval(1,0),tableval(1,1) ,2 Figure 3.13: Sample Plot Using *VPLOT , table2(1),tableval(1,1) ,2
Figure 3.14: Sample Plot Using *VPLOT, tableval(1,0),tableval(1,1) ,2 Figure 3.13: Sample Plot Using *VPLOT , table2(1),tableval(1,1) ,2
3.10.9. Modifying Curve Labels When you use *VPLOT to create your curves, default labels are assigned. Normally, the label for curve 1 is “COL 17 the label for curve 2 is “COL 2” and so on; the column number is the field containing the dependent variables for that particular curve. You can use the /GCOLUMN command to apply your own labels to the curves (any string of up to eight characters).
3.10.9. Modifying Curve Labels When you use *VPLOT to create your curves, default labels are assigned. Normally, the label for curve 1 is “COL 17 the label for curve 2 is “COL 2” and so on; the column number is the field containing the dependent variables for that particular curve. You can use the /GCOLUMN command to apply your own labels to the curves (any string of up to eight characters).
Figure 3.15: Sample Plot With User-specified Labels
Figure 3.15: Sample Plot With User-specified Labels
As with the *CREATE command, parameters are not evaluated but are written verbatim into the macro file. Note that you do not make the last line a *END command.
As with the *CREATE command, parameters are not evaluated but are written verbatim into the macro file. Note that you do not make the last line a *END command.
4.1.5. Using Macro Library Files As a convenience, ANSYS allows you to place a set of macros in a single file, called a macro library file. You can create these either through the *CREATE command or through a text editor. Given that macro librarie tend to be longer than single macros, using a text editor normally provides the best approach.
4.1.5. Using Macro Library Files As a convenience, ANSYS allows you to place a set of macros in a single file, called a macro library file. You can create these either through the *CREATE command or through a text editor. Given that macro librarie tend to be longer than single macros, using a text editor normally provides the best approach.
Table 4.1 _RETURN Values
Table 4.1 _RETURN Values
4.6. Using the STATUS and _RETURN Parameters in Macros
4.6. Using the STATUS and _RETURN Parameters in Macros
*ask,parml, ‘username (enclose the username in single quotes) |
*ask,parml, ‘username (enclose the username in single quotes) |
Figure 5.2: A Typical Multiple-Prompt Dialog Box
Figure 5.2: A Typical Multiple-Prompt Dialog Box
Additional *get commands for a new entity=PRODUCT
Additional *get commands for a new entity=PRODUCT
Check for Ansys gateway commands/feature RPR4
Check for Ansys gateway commands/feature RPR4
Related topics:
Naval EngineeringNaval ArchitectureFinite Element MethodsMarine EngineeringOffshore StructuresFinite Element Analysis (FEA)Finite AutomataOffshore EngineeringNaval Architecture and Engineering
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved