"ANSYS Mechanical APDL命令参考手册2021 R2"

需积分: 12 12 浏览量更新于2023-12-16 收藏 21.71MB PDF 举报

"Ansys_Mechanical_APDL_Command_Reference.pdf"是ANSYS中的一份帮助文件，它提供了关于APDL命令流的详细信息。该文件的发布版本为2021 R2，由ANSYS公司在2021年7月发布。 ANSYS, Inc.是一家总部位于美国宾夕法尼亚州Canonsburg市的公司，其地址为Southpointe2600 Ansys Drive，邮编15317。该公司还有一个在欧洲注册的分支机构Ansys Europe, Ltd.。可以通过ansysinfo@ansys.com联系到这两家公司。ANSYS, Inc.和Ansys Europe, Ltd.都是根据ISO 9001:2015注册的公司。该帮助文件的版权归ANSYS, Inc.所有。未经许可，禁止未经授权的使用、分发或复制该文件。在文件中提及的Ansys、Ansys Workbench、AUTODYN、CFX和FLUENT等品牌、产品、服务和特性的名称、商标和口号都是ANSYS, Inc.的注册商标。该文件的目的是为用户提供对APDL命令流的详细了解和使用指导。APDL（ANSYS Parametric Design Language）是ANSYS的一种命令流语言，通过以命令的形式输入各种操作和参数，实现对ANSYS软件的控制和定制。APDL命令流的灵活性和强大功能使得用户能够更好地利用ANSYS软件进行仿真和分析。在该帮助文件中，用户可以找到APDL命令流的完整命令列表和语法说明。这些命令涵盖了各种建模、分析、求解和后处理操作，包括几何体生成、材料属性定义、加载和边界条件设置、求解器选择和控制、结果输出和可视化等。文件中还提供了丰富的示例和使用案例，以帮助用户更好地理解和应用这些命令。除了命令列表和语法说明外，该帮助文件还提供了APDL命令流的相关概念和基本原理的介绍。用户可以了解到命令流的执行顺序、参数传递方式、循环和条件判断的使用方法等。这些知识对于编写和调试复杂的命令流非常重要，能够提高用户的操作效率和仿真结果的准确性。此外，该文件还包括对一些常见问题和故障的排除方法的介绍。如果用户在使用APDL命令流时遇到了错误或异常情况，可以通过参考这些排除方法来解决问题。文件中还提供了联系ANSYS技术支持团队的方式，用户可以通过电话或电子邮件与他们联系，获取进一步的帮助和支持。总之，"Ansys_Mechanical_APDL_Command_Reference.pdf"是一份非常有价值的帮助文件，对于使用ANSYS中的APDL命令流进行仿真和分析的用户来说，它提供了全面而详细的指导和参考。通过深入研读和实践，用户可以充分利用APDL命令流的优势，提高工作效率和结果准确性。

Data -- Data may be numeric (real or integer), alphabetic, or alphanumeric (containing letters and

numbers). Nonnumeric data should not contain special characters such as

! @ # $ % ^ & * ( ) _ - +

= | \ { } [ ] " ' / < > ~ `

Numeric data may be input in a variety of ways as described in Data Input (p. 5). Some commands

are switches of the form Commandname,Key where Key can be 0, NO or OFF to toggle the switch off;

or 1, YES or ON to toggle the switch on.

Degree of Freedom -- The degrees of freedom are the primary nodal unknowns determined by the

analysis. They may be displacements, rotations, temperatures, pressures, voltages, etc. A degree of

freedom is defined by a node number and a label, for example, 1 UX, 87 ROTZ, 4 TEMP, etc. Derived

results, such as stresses, heat flows, etc. are computed from the degree of freedom results and are

considered secondary unknowns.

Element types with unequal sets of degrees of freedom can be combined in a single structure. For ex-

ample, a 2-D structure composed of 2-D solid elements having two degrees of freedom (UX, UY) at each

node and a 2-D beam element having three degrees of freedom (UX, UY, ROTZ) at each node will have

the latter three degrees of freedom at the common nodes. Nodes which do not have a beam element

attached will have only two degrees of freedom with ROTZ eliminated from the solution printout.

Field -- The command name and data items entered on a command are separated into consecutive

fields. A field is assumed to be as "wide" as the number of characters specified. A comma is used to

end one field and begin the next.

Line -- A line of input is a physical record read by the computer. Input lines are limited to 640 characters

(including preceding blanks, commas, and any special characters). For file input, a line is represented

by one 640 column data record. For interactive input, a line is the string of characters (640 maximum)

entered before the RETURN key is pressed. Several commands may be put on one line as described in

Data Input (p. 5). Blank lines are permitted for clarity.

Command name -- Only the first four characters of any alphabetic (or alphanumeric) command name

are interpreted by the program (except as noted for certain commands, such as /POSTN, /AUXN. *EN-

DDO (p. 611), etc.). The remaining characters of the field are ignored. Names shown with fewer than

four characters are assumed to have blanks up through the fourth character as part of the name. For

example, this sample ET (p. 661) command may be input as ET (p. 661),1,42 or ET (p. 661) ,1,42 or ET (p. 661)

,1,42, but not as ETABCD,1,42. Names may not contain special characters (as described in Data In-

put (p. 5)). If the command name is omitted, the name defaults to the name of the previous command,

unless it was a slash (/) or star (*) command.

Postprocessing Phase -- The set of commands causing further processing of the solution output. These

commands consist of commands from the POST1 and POST26 processors. The postprocessing phase

may consist of input for several postprocessing sessions (in series).

Preprocessing Phase -- The set of commands related to defining the model. The preprocessing phase

consists of input from the PREP7 processor.

Program -- The collection of all processors (preprocessing, postprocessing, auxiliary, etc.) is called the

Ansys program.

Processor -- A group of related functions, such as model definition (PREP7) or results examination

(POST1).

of ANSYS, Inc. and its subsidiaries and affiliates.4

About This Reference

Run -- The collection of all commands between the system-level commands is called a run or session).

A session may also consist of several analyses in series (separated by a /CLEAR (p. 332) command).

Solution Phase -- The set of commands which apply boundary conditions to the model created in

preprocessing, then performs a solution for that set of boundary conditions. The solution phase may

consist of several solutions in series, such as a static solution, followed by a modal solution, etc.

1.3. Command Characteristics

The following characteristics apply to commands:

1.3.1. Data Input

1.3.2. Free-Format Input

1.3.3. Nonrestrictive Data Input

1.3.4. Condensed Data Input

1.3.5. Units

1.3.6. Command and Argument Defaults

1.3.7. File Names

1.3.8. Star and Slash Commands

1.3.1. Data Input

The data input for each command is described in this manual. Data should not be input in any un-

documented field, nor should other than documented values be input in any field. Also, the data input

described in this manual should not be used with any earlier version of the program. Some features

that allow easy input of data are free-format, nonrestrictive, and condensed input.

1.3.2. Free-Format Input

Free-format capability allows the user to input data in consecutive fields without having to space to

each field. The comma (,) character effectively ends the field so that the next character will be input

in the beginning of the next field. A blank field is skipped by having no data item between the

commas. Fields are assumed to be as wide as the number of characters specified. Input is converted

to formatted fields when coded files are written (of width large enough (16 characters maximum) to

minimize loss of accuracy).

Significant figures of output should not be expected to match that of input. Machine precision,

rounding of numbers when writing internal scratch files, etc., tend to lower the precision during the

analysis.

1.3.3. Nonrestrictive Data Input

Nonrestrictive data input allows the user to enter any form of data in a field and the Ansys program

will interpret it as required (integer, real, or alphabetic) or ignore it. Double precision is used

throughout the program for all real numbers. Alphabetic data may be entered in upper or lower case.

Lower case is internally converted to upper case within the program (except for case-sensitive applic-

ations, such as in comments, (text preceded by a !) titles, and file names.)

of ANSYS, Inc. and its subsidiaries and affiliates.

Command Characteristics

The following features are available with the nonrestrictive data input.

• No distinction is necessary between real and integer data.

• Data may be placed anywhere within the field.

• Real data input without a decimal point has the decimal point assumed after the right-most

digit.

• Real number values input to integer data fields will be rounded to the nearest integer. The

absolute value of integer data must fall between zero and 2,000,000,000.

• Element and node numbers (IDs) should be between 1 and 999,999,999. Element type, mater-

ial reference, real constant, section, and coordinate system IDs should be between 1 and

9,999,999. IDs larger than these may not be written out correctly in listings (xLIST commands),

CDWRITE (p. 285) files, LSWRITE (p. 1045) files, and other text-based output files.

• Exponents may be input in the field after the number. The E (or D) character must be used

(upper or lower case). The sign after the E character is assumed to be the sign associated with

the exponent (the absence of a sign is assumed to be +). The acceptable range of values for

real data is +/-1.0E+200 to +/-1.0E-200.

• A nonnumeric character in the numeric field (other than a valid convenience label, a parameter

name, or an E or D exponent character) will be ignored and will cause the remainder of the

field to be ignored. When the program can accept an alphanumeric label in a field, it will in-

terpret any alphanumeric input that matches a valid label as the appropriate label. In other

words, the program will not interpret a valid label as an identically named parameter. If you

truly want to use a parameter in place of a valid label, you can use forced parametric substitu-

tion (using % signs). A non-alphanumeric character in a label field is taken as part of the label.

Non-alphanumeric characters (such as CONTROL-characters, TAB-characters, and other terminal

editing characters) should be avoided since they may be used directly instead of being inter-

preted by the terminal.

1.3.4. Condensed Data Input

An option for condensing the data input is available with the $ character. This character effectively

ends a command and allows the next command to begin on the same line (at the next column). The

line must not extend beyond 640 characters (including all commas and $ signs). If a command cannot

be completed on the line, it should begin on the next line. Blank commands are ignored. The $

character should not be used following any command that causes a file switch to read additional

commands (such as the /INPUT (p. 909), *USE (p. 1985), CDREAD (p. 283), etc. commands, any "unknown

command" macro, or any do-loops or if-then-else constructs). The $ character should not be used

between a command and its required following format line (such as *VREAD (p. 2068), *VWRITE (p. 2089),

*MSG (p. 1139), etc.). The $ character should not be used after the ALLSEL (p. 107) command. Using

the $ character in interactive mode may result in unexpected output behavior.

1.3.5. Units

The Ansys program permits the use of any consistent set of units for length, force, time, temperature,

etc. Care must be taken to ensure that all input data are in the same set of units. The /UNITS (p. 1979)

command may be used to note the system of units being used. Temperatures may be absolute or

relative in most cases. For problems requiring absolute temperatures, such as those involving creep,

of ANSYS, Inc. and its subsidiaries and affiliates.6

About This Reference

swelling, or radiation, temperatures may be input as Celsius or Fahrenheit, for convenience, with a

temperature shift from absolute zero [TOFFST (p. 1934)].

1.3.6. Command and Argument Defaults

To minimize the amount of data input, most commands have defaults which apply both to the

command itself and to any arguments.

Command Defaults

A command default refers to the specification or behavior that is assumed when a command is not

issued. For example, if you do not issue the /FILNAME (p. 729) command, the jobname defaults to

FILE (or whatever jobname was specified when you entered the program).

Argument Defaults

An argument default is the value assumed for a command argument if the argument is not specified.

For example, if you issue the command N (p. 1161),10 (defining node 10 with the X, Y, Z coordinate

arguments left blank), the node is defined at the origin; that is, X, Y, and Z default to zero.

Values for numeric arguments (such as X, Y, Z) typically default to zero, although exceptions exist for

some commands, such as those with arguments specifying coefficients or tolerances. Such exceptions

are noted in the documentation for those commands.

When an argument has a nonzero default, entering a blank or a zero for that argument triggers the

nonzero default value. If an effective zero is desired for such an argument, input a very small number

(such as 1E-14) instead.

In cases where no default is indicated or obvious for an argument, enter the desired value. Such ar-

guments have no favored default value and require an explicit input value.

Some Command Defaults May Differ According to Product

The defaults for some commands and their arguments may differ depending on which product is

using the commands. The "Product Restrictions" section of the descriptions of the affected

commands clearly documents such cases.

If you intend to use your input file in more than one product, it is good practice to explicitly specify

commands and argument values, rather than letting them default. Otherwise, behavior in the other

product may differ from what you expect.

1.3.7. File Names

Various files are used during a session for reading, writing, and storing data. Program-generated files

are identified by a name, a system-dependent separator, and an extension (as in the form fname.ext).

The name is obtained from the Jobname (250 characters maximum, including the directory name)

as defined with the execution command. (Windows cannot create directory names longer than 245

characters.)

Unless otherwise specified, the Jobname defaults to a system-dependent name (usually FILE). The

extension is a two- to four-character identifier. (See Files that Ansys Writes in the Basic Analysis Guide.)

of ANSYS, Inc. and its subsidiaries and affiliates.

Command Characteristics

For example, the error message file (which has the identifier ERR) with a jobname of FILE and sep-

arator (.) would be generated as FILE.ERR. If the Jobname is JOB1, the file would be named

JOB1.ERR. The documentation generically refers to program-generated files as Jobname.identi-

fier, such as Jobname.ERR for the error message file. Unless otherwise indicated, files are written

in the current working directory.

Some commands (such as /INPUT (p. 909) and /OUTPUT (p. 1282)) allow you to specify a file name

other than Jobname, and an extension other than the default extension. Such user-written files use

a naming convention similar to the Ansys-generated files except that the name (248 characters

maximum, including the directory name) is user defined, and the extension (8 characters maximum)

is optional. The file name can include the directory path, but it is not necessary if you want to use

the default directory. File names containing directory paths must reference existing directories. File

and directory names may contain blank spaces, but strings containing blank spaces must be enclosed

in single quotes.

A system dependent separator is automatically written between file name and extension (if the exten-

sion exists) input on commands.

File name fields are usually restricted to 248 characters (including the directory name) in command

inputs. If you specify no directory path, the default path is your working directory, and you can use

all 248 characters for the file name.

To help ensure portability of input files across systems, the program has certain requirements for file

names. Avoid using special characters (+,-,*,/,$,!, etc.) in file names unless meaningful, and begin file

names with a letter. Some system-dependent special characters (such as ~) are not interpreted the

same as they are at the operating system level when used in path names. Parameter substitution can

be forced within the name, extension, or directory fields by enclosing the parameter within percent

(%) signs. For example, if I = 5, the name TEST%I% becomes TEST5.

Chinese and Japanese character file names are supported. The input file, output file, Jobname, and

working directory can include Chinese or Japanese characters in the file or folder name. These names

can be input at the command line, through the Mechanical APDL Launcher, or through commands

such as /FILNAME (p. 729), RESUME (p. 1541), and /ASSIGN (p. 192). Keep the following points in mind

when using Chinese or Japanese characters:

• The locale setting of the operating system must match that of the language being used for

naming.

• The file extensions must remain in standard English characters.

• Non-English characters are not supported by GUI operations. Specifically, the Open File button

on the Standard Toolbar does not accept Mechanical APDL files that are named with non-

English characters, and the GUI command input area does not accept commands that include

non-English characters.

1.3.8. Star and Slash Commands

The slash (/) and star ( *) commands are usually used for supplying general control instructions to

the program. For example, slash commands are used for entering a processor (/PREP7 (p. 1421),

/POST1 (p. 1404), etc.). Printout controls, display controls, and file controls are available within the slash

command set.

of ANSYS, Inc. and its subsidiaries and affiliates.8

About This Reference

剩余2127页未读，继续阅读

HHH@3h浩

粉丝: 14
资源: 3

"ANSYS Mechanical APDL命令参考手册2021 R2"

ANSYS Mechanical APDL Command Reference.pdf

ANSYS Mechanical APDL Programmers Reference.pdf

汉化ansys_mechanical_apdl_command_reference

ANSYS Mechanical APDL 命令参考手册

CS1231模拟输入前端详解：Ansys Mechanical APDL 命令参考

ansys mesh教程

数据库基础测验20241113.doc

微信小程序下拉选择组件

DICOM文件+DX放射平片-数字X射线图像DICOM测试文件

Jupyter Notebook《基于双流 Faster R-CNN 网络的 图像篡改检测》+项目源码+文档说明+代码注释

最新资源

Jupyter Notebook《基于双流 Faster R-CNN 网络的图像篡改检测》+项目源码+文档说明+代码注释