Loading ...
Global Do...
News & Politics
34
0
Try Now
Log In
Pricing
UTOMATIC YNAMIC NCREMENTAL ONLINEAR NALYSIS ADINA User Interface Command Reference Manual Volume III: ADINA CFD Model Definition Report ARD 08-4 February 2008 ADINA R&D, Inc. ADINA User Interface Command Reference Manual Volume III: ADINA CFD Model Definition Report ARD 08-4 February 2008 for the ADINA System version 8.5 ADINA R & D, Inc. 71 Elton Avenue Watertown, MA 02472 USA tel. (617) 926-5199 telefax (617) 926-0238 www.adina.com Notices ADINA R & D, Inc. owns both this software program system and its documentation. Both the program system and the documentation are copyrighted with all rights reserved by ADINA R & D, Inc. The information contained in this document is subject to change without notice. ADINA R & D, Inc. makes no warranty whatsoever, expressed or implied that the Program and its documentation including any modifications and updates are free from errors and defects. In no event shall ADINA R & D, Inc. become liable to the User or any party for any loss, including but not limited to, loss of time, money or goodwill, which may arise from the use of the Program and its documentation including any modifications and updates. Trademarks ADINA is a registered trademark of K. J. Bathe / ADINA R & D, Inc. All other product names are trademarks or registered trademarks of their respective owners. Copyright Notice © ADINA R & D, Inc. 1994 - 2008 February 2008 Printing Printed in the USA ADINA R & D, Inc. v Table of contents Table of contents Chapter 1 Introduction .......................................................................................................... 1-1 1.1 Program execution ................................................................................................ 1-3 1.2 Command syntax ................................................................................................... 1-3 1.3 Input details .......................................................................................................... 1-6 1.4 Messages ............................................................................................................ 1-10 1.5 File input/output .................................................................................................. 1-11 1.6 The AUI database ................................................................................................ 1-11 1.7 Listings ................................................................................................................ 1-12 1.8 Units .................................................................................................................... 1-13 1.9 Tips for writing batch files ................................................................................... 1-13 1.10 Related documentation ........................................................................................ 1-13 Chapter 2 Quick index .......................................................................................................... 2-1 2.1 New commands, parameters and options ............................................................. 2-1 2.2 Quick overview of commands .............................................................................. 2-3 Chapter 3 Input/output .......................................................................................................... 3-1 3.1 Database operations ............................................................................................. 3-1 3.2 Analysis data files ................................................................................................ 3-7 3.3 External data ......................................................................................................... 3-8 3.4 Auxiliary files ....................................................................................................... 3-19 3.5 Program termination ............................................................................................. 3-25 3.6 Auxiliary commands ............................................................................................ 3-26 Chapter 4 Interface control and editing ............................................................................... 4-1 4.1 Settings ................................................................................................................. 4-3 4.2 Editing ................................................................................................................... 4-7 Chapter 5 Control data .......................................................................................................... 5-1 5.1 General .................................................................................................................. 5-1 5.2 Analysis details ................................................................................................... 5-13 5.3 Options ................................................................................................................ 5-14 5.4 Solver details ....................................................................................................... 5-16 5.5 Automatic control ................................................................................................ 5-19 5.6 Time-dependence ................................................................................................ 5-20 5.7 Iteration ............................................................................................................... 5-22 5.8 Tolerances ........................................................................................................... 5-47 5.9 Analysis output ................................................................................................... 5-51 Chapter 6 Geometry definition ............................................................................................. 6-1 6.1 Coordinate systems .............................................................................................. 6-3 vi AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Table of contents 6.2 Points .................................................................................................................... 6-6 6.3 Lines ..................................................................................................................... 6-8 6.4 Surfaces ............................................................................................................... 6-35 6.5 Volumes ................................................................................................................ 6-50 6.6 Solid models ........................................................................................................ 6-63 6.7 Spatial functions .................................................................................................. 6-76 6.8 Transformations ................................................................................................... 6-83 6.9 Miscellaneous ..................................................................................................... 6-93 6.10 ADINA - M........................................................................................................ 6-101 Chapter 7 Model definition ................................................................................................... 7-1 7.1 Material models .................................................................................................... 7-1 7.2 Element properties ............................................................................................... 7-48 7.3 Boundary conditions ........................................................................................... 7-54 7.4 Loading .............................................................................................................. 7-114 7.5 Initial conditions ................................................................................................ 7-138 7.6 Systems ............................................................................................................. 7-143 7.7 Mass transfer ..................................................................................................... 7-165 7.8 Data functions ................................................................................................... 7-167 7.9 Control data ....................................................................................................... 7-168 Chapter 8 Finite element representation ............................................................................. 8-1 8.1 Element groups ..................................................................................................... 8-1 8.2 Mesh generation................................................................................................... 8-7 Chapter 9 Direct finite element data input ........................................................................... 9-1 9.1 Nodal data ............................................................................................................. 9-1 9.2 Element data ......................................................................................................... 9-6 9.3 Element generation .............................................................................................. 9-11 9.4 Boundary conditions ........................................................................................... 9-24 9.5 Loads ................................................................................................................... 9-26 9.6 Initial conditions .................................................................................................. 9-32 9.7 Moving mesh ....................................................................................................... 9-36 Command index ............................................................................................................... Index-1 Chapter 1 Introduction ADINA R & D, Inc. 1-3 1. Introduction This reference manual provides concise descriptions of the command input requirements for the ADINA User Interface (AUI). This introduction serves to give some background informa- tion and indicate the general command syntax including descriptions of the conventions used. 1.1 Program execution Commands can be entered in the following modes: Interactive (a) AUI is running with the user interface displayed you can enter commands into the user interface command window see the AUI Users Guide. (b) AUI is running in command mode (using the "-cmd" option) you can enter commands from standard input. Batch (a) AUI is running with the user interface displayed you can read commands from a file by choosing File→Batch (UNIX versions) or File→Open (Windows version) see the AUI Users Guide. (b) Commands can be read from a given file using the aui startup options -s (UNIX versions) or -b (Windows version). You can also read commands from a file using the READ command (see Section 3). 1.2 Command syntax Here is the layout of a typical command reference page: COMMAND[1] PARAM1 PARAM2[2]... data1i data2i [3]... General description of command function.[4] Sec. 1.1 Program execution 1-4 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 1 Introduction PARAM1 [<default>][6] Description of parameter PARAM1[5]. {<input choices>}[7] PARAM2 [<default>] Description of parameter PARAM2. {<input choices>} ... data1i [<default>][6] Description of data line entry data1i [5] (ith row, column 1). {<input choices>}[7] data2i [<default>] Description of data line entry data2i (ith row, column 2). {<input choices>} ... Auxiliary commands[8] LIST COMMAND Brief description of this command. DELETE COMMAND Brief description of this command. Issuing a command allows you to alter the data associated with the command. This data comprises the values associated with the command parameters and possibly a table, input via "data lines", associated with the command. In the above, the command name "COMMAND"[1], given at the top of the reference page, has the first few characters emphasized to show the minimum number of characters required to be input to uniquely identify the command. A list of parameters[2] and data lines[3] for the command then follows. In this list the first few characters in the parameter and data line names are emphasized to show the minimum number of characters required to uniquely identify the parameter and data line names. Following a general outline of the command function[4], a description of the command parameters and data line entries is given below the relevant keynames[5]. The parameters usually have default values[6] which are assumed if the parameter is not explicitly specified. The default values are indicated in brackets [ ] a bold value indicates a default value (number or string) and an italicized string indicates the source of the default value, which is either (a) a text description of the default, (b) a parameter name from the same ADINA R & D, Inc. 1-5 command, or (c) a combination of command + parameter names, indicating that the default is taken from the setting of another (different) command parameter. A parameter for which no default is provided means that there is no default i.e., some choice must be entered for that parameter. One important parameter type is that of an entity identifier for which the parameter keyname "NAME" is normally reserved. If the object identified by NAME has already been defined, then the other parameter defaults are set to the previous settings for that object. If a new NAME is given then the defaults, as indicated by the command reference pages herein, are taken. In the former case, execution of the command redefines the named object. The choice of parameter values is often discussed within the parameter description, but, where appropriate, a simple list of choices follows the parameter description[7]. For example, parameters with simple logical choices will have the list "{YES/NO}" appended to the description. When a table is associated with the command, the command includes data input lines. For some commands, the table is initially empty, but for other commands the table already includes data lines. The columns of a data line can be divided into two types: key columns and data columns. When a data line has key columns, the key value columns always precede the data value columns. In this case the values of the key columns uniquely identify the data line, and, therefore, two data lines cannot have the same key column values for such input, the second input data line overwrites the data associated with the key column values. You can delete a data line by preceding the key column values with the DELETE prefix. When a data line does not have key columns, two or more data lines can have the same values but you cannot use the DELETE prefix to delete data lines without key columns. However, you can always delete all of the data lines of a table using the @CLEAR or CLEAR keywords. This is of course especially useful for those tables in which there are no key columns. For data line input, not all the columns need be specified; the ENTRIES keyword, which can be input as the first data line following the command line, can be used to select a subset of the data column entries (see below). Then the values you enter in the subsequent data lines are associated with the columns indicated by the ENTRIES parameters, the other data columns taking default values whenever possible. Note, however, that key columns are required input, and should thus be included in the ENTRIES column list. Many commands have "auxiliary" commands[8] which are entered with one of the following prefixes: Sec. 1.2 Command syntax 1-6 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 1 Introduction LIST List object definitions. DELETE Delete objects from the database. UPDATE Update command defaults. RESET Reset command defaults. COPY Copy objects. SET Set "currently active" objects. SHOW Show "currently active" objects. A LIST prefixed command has several forms: LIST COMMAND List all object identifiers (names). LIST COMMAND NAME List definition of object with identifier NAME. LIST COMMAND FIRST LAST List definitions of a range of objects with integer label numbers. Parameters FIRST, LAST may also take the string values FIRST, LAST, ALL. A DELETE prefixed command has the following forms: DELETE COMMAND NAME Delete the object with identifier NAME. DELETE COMMAND FIRST LAST Delete a set of objects with integer label numbers in the specified range. Note that an object may not be deleted if another model entity depends on its existence as part of its own definition. For example, a geometry line cannot be deleted if it forms a bound- ing edge of some geometry surface. 1.3 Input details Command input Please refer to command AUTOMATIC LOAD-DISPLACEMENT in the following discussion (Section 5.5): AUTOMATIC LOAD-DISPLACEMENT POINT DOF DISPLACEMENT ALPHA DISPMAX CONTINUE RPRINT TYPE NODE When entering commands, only as many characters as necessary to uniquely specify the command name need be entered. The same rule applies to the parameters and data line entry ADINA R & D, Inc. 1-7 key names within a command. The minimum number of characters necessary are indicated in bold. Note that command / parameter is case insensitive. All commands, parameters, values are stored in upper case, except for string variables (headings, graph legends, etc.). Parameter values may be input in any order if the keynames are used, e.g., AUTOMATIC LOAD-DISPLACEMENT DOF=3 RPRINT=YES DISPMAX=5.0 DISPLACEMENT=4.0 POINT=17 Some or all of the parameters can be excluded if the positional order of the parameters is observed, e.g., AUTOMATIC LOAD-DISPLACEMENT 17 3 4.0, ,5.0, ,YES (the parameters ALPHA and CONTINUE have been omitted by the use of the commas). A mix of keyname parameters and positional input is allowed, e.g., AUTOMATIC LOAD-DISPLACEMENT 17 DISPLACEMENT=4.0 DOF=3,,5.0,, YES The above uses of the AUTOMATIC LOAD-DISPLACEMENT command are all equivalent. The omitted parameters in each case take the default values. Data lines Many commands require data line (tabular) input, e.g., MODAL-DAMPING (see Section 5.3): MODAL-DAMPING modei factori Use the ENTRIES keyword to select only the data columns that you want to enter (the other data columns will be given default values): MODAL-DAMPING ENTRIES MODE FACTOR 1 1.0 2 0.5 3 2.5 4 1.5 DATAEND Most commands which take this form of input also allow for incremental row generation via the "STEP inc TO" option where "inc" represents an increment in the generation, i.e., in the above Sec. 1.3 Input details 1-8 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 1 Introduction example modei+k, modei+2k, ..., modej-k, are all generated, with the corresponding values for "factor" linearly interpolated between factori and factorj. When generating integer values, the difference between the first and last values must be an integer multiple of the STEP increment (i.e., modulo((modej-modei),k) = 0). There is a default step increment, which for integer values is normally 1; in this case "STEP 1 TO" may be input simply as "TO". Here are some examples: MODAL-DAMPING 1 5.5 TO 3 7.5 @ or MODAL-DAMPING 1 5.5 STEP 1 TO 3 7.5 DATAEND Both of these are equivalent to MODAL-DAMPING 1 5.5 2 6.5 3 7.5 @ Note that data line input may be terminated either by entering the symbol "@" or the string "DATAEND" data line input will be terminated automatically by input of the next command. Data line rows can be deleted by preceding the key value by the prefix DELETE. This method of deletion also supports row "generation" i.e., "DELETE i STEP k TO j" may be used to delete a range of values. All the data lines associated with a command may be deleted simultaneously using the CLEAR or @CLEAR keywords. This is useful when you want to define a table if you do not know if the table is already defined or not: TIMEFUNCTION 1 CLEAR which removes all the currently defined data lines of timefunction 1. The columns for data line input can be selected by use of the keyword ENTRIES in the first input data line following the command line, e.g., ADINA R & D, Inc. 1-9 COORDINATES POINT ENTRIES NAME Y Z which indicates that only global Y and Z coordinates are to be input for geometry points in the subsequent data lines. The X coordinate assumes the default value 0.0, and thus subsequent data lines entered describe points in the global Y-Z plane. Names AUI names are usually of two types alphanumeric strings of up to 30 characters or integer label numbers. Integer label numbers are normally greater than or equal to 1. Integer values Integers can be input with a maximum of 9 significant digits. For positive values, a preceding + sign may, if desired, be input. Real values Specification of real values can include a decimal point and/or an exponent. The exponent must be preceded by the letters E, e, D, or d, e.g., 2E5 2.0d+07 200000. all refer to the same real number. Alphanumeric values Alphanumeric values must start with a letter (A-Z, a-z) or number (0-9). The only permissible characters allowed are the letters A-Z, a-z, the digits 0 to 9, the hyphen (-), and the underscore (_). Lower-case characters in an alphanumeric value are always converted to upper-case by the AUI. String values A string should be enclosed by apostrophes ('). Any apostrophe within the string must be entered twice. Any character can be included in a string. Lower-case characters in a string value are not converted to upper-case. Filenames A filename should be enclosed by apostrophes ('). Filenames can be up to 256 characters long. Length of input lines Input lines to the AUI can each contain up to 256 characters. Line continuation, line separator, blanks, and commas If the last non-blank character of a command or data line is a comma (,), then the command or Sec. 1.3 Input details 1-10 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 1 Introduction data is continued on the next input line. The total length of an input line and all of its continuations can be up to 2000 characters. A slash (/) in an input line can be used to end a command or data input line; more commands or data can then be entered on the same input line. A blank, several blanks, <Tab> characters, a comma, or a comma surrounded by blanks act as delimiters. Commands, parameter keynames and values must be separated by delimiters. Comments Comment lines can appear anywhere in the input and are identified by an asterisk (*) in column 1, e.g., * This is a comment line Parameter substitution You can define parameters as numeric expressions, and use the parameter values in later commands. This feature is useful when creating batch files used in structural optimization. For example: PARAMETER A `5 + 7` PARAMETER B `2*$A` PARAMETER C `3 + $A + 4*$B` BODY BLOCK DX1=$A DX2=$B DX3=$C 1.4 Messages Commands will often echo messages confirming their successful completion, or provide other information. Otherwise you may get error/warning messages with varying levels of severity: *** INPUT ERROR You have entered an unacceptable parameter value or data. The command will not execute with invalid input. *** WARNING The command has completed, but has detected a possible inconsistency which may have to be resolved. *** ALERT The command has completed, but has detected a definite modeling inconsistency which has to be resolved in order to create a valid model. *** ERROR The command has not completed. ADINA R & D, Inc. 1-11 *** INTERNAL ERROR The program has determined some conflict in the database, normally indicating a software bug. You should contact ADINA R & D Inc. if you encounter such a message. In order to track down the source of the problem it would be most useful if the input responsible for this condition is made available to the support engineers. *** MEMORY OVERFLOW The command has not completed, due to the program running out of memory. Increse the memory allocation to the program 1.5 File input/output The AUI uses several files for handling I/O. Here is a brief description of some of them, together with a suggested filename extension convention (for the UNIX operating system other filename conventions may be appropriate for other operating systems) : <file>.in ADINA-IN batch command input. <file>.idb ADINA-IN permanent database. <file>.plot ADINA-PLOT batch command input. <file>.pdb ADINA-PLOT permanent database. <file>.ses AUI session file (echo of command input). <file>.ps PostScript snapshot. <file>.dat Analysis data. <file>.port Analysis porthole. <file>.out Analysis printout. See the AUI Users Guide, Chapter 6 for more information. 1.6 The AUI database The AUI uses an internal database to store and retrieve data used during program execution. The internal database is stored in main memory and, if main memory is not sufficient, a tempo- rary database file is created to hold the excess data. The internal database can be saved in a disk file, called a permanent database file, so that it can be retrieved in a future run. Five commands are used to create, open and save databases. DATABASE NEW creates a new empty internal database. DATABASE OPEN initializes the internal database using a specified permanent database file. DATABASE SAVE saves the internal database to disk, allowing you to specify the name of the database file. DATABASE ATTACH causes the AUI to use the specified permanent database file as the internal database. DATABASE DETACH renames the internal database file as a permanent database file. All of these commands are described in Section 3.1. Sec. 1.5 File input/output 1-12 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 1 Introduction The permanent database file is similar to a text file used in a word processing program. Like the text file, the permanent database file resides on disk and can be retrieved by the program in a future run. The permanent database file can be saved on disk periodically during program execution to protect against loss of data due to computer failure. During each save operation, a different permanent database file can be selected so that several versions of the database are available for retrieval. (This is similar to saving several versions of a text file on disk when working with a word processing program.) For the differences between DATABASE OPEN and DATABASE ATTACH, see the command description for DATABASE ATTACH. For the differences between DATABASE SAVE and DATABASE DETACH, see the command description for DATABASE DETACH. 1.7 Listings Many AUI commands generate lists. For example, the ZONELIST command (see The AUI Command Reference Manual, Volume IV) lists the values of variables. You can also specify whether listings are to be sent to your terminal or to a disk file (see the FILELIST command). When the listings are sent to your terminal, you are prompted by --More--( %) after each screen of the listing. The number printed before the percent sign represents the percentage of the file that has been displayed so far. Responses to this prompt are as follows: <return> Display another line of the listing. <space bar> Display another screenful of the listing. <i><space bar> Display i more lines. D or d Display the next half-screen (a scroll) of the listing. <i>D or <i>d Set the number of lines in the scroll to i and display the next scroll. <i>Z or <i>z Set the number of lines in each screen to i and display the next screen. <i>S or <i>s Skip i lines and print a screenful of lines. <i>F or <i>f Skip i screenfuls and print a screenful of lines. <i>B or <i>b Skip back i screenfuls and print a screenful of lines. Q or q Stop the listing. = Print the current line number in the listing. . Repeat the last prompt response. In these responses, <i> represents an optional integer argument, defaulting to 1. If you are familiar with the UNIX operating system, you will recognize that the above options corre- spond closely to the options of the 'more' command. ADINA R & D, Inc. 1-13 1.8 Units In model definition no particular unit system is assumed. Any consistent unit system may be adopted. Certain thermodynamic constants do, however, have a choice of temperature unit system (Celsius/Centigrade/Kelvin, Fahrenheit/Rankine). 1.9 Tips for writing batch files Increasing execution speed: The AUI contains features that are useful when you enter commands using the dialog boxes, but are not useful when you read commands from a batch file. These features are activated by default. You can deactivate the features to increase the speed at which batch files are processed, and to reduce the memory requirements of the AUI. The features are Undo/redo storage: Command CONTROL UNDO=-1 turns off storage for undo/redo information. Automatic model rebuilding: Command CONTROL AUTOMREBUILD=NO turns off automatic model rebuilding. Session file creation: Command FILESESSION NO turns off creation of the session file. Storage of session file information in the database: To turn off this feature, use the command CONTROL SESSIONSTORAGE=NO. Stopping after an error or memory overflow is detected: Command CONTROL ERRORACTION=SKIP activate a feature that AUI skips the remaining commands in a batch file after an error or memory overflow is detected. Summary: Use the following commands to perform all of the above actions: FILESESSION NO CONTROL UNDO=-1 AUTOMREBUILD=NO SESSIONSTORAGE=NO, ERRORACTION=SKIP 1.10 Related documentation At the time of printing of this manual, the following documents are available with the ADINA System: Sec. 1.8 Units 1-14 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 1 Introduction Installation Notes Describes the installation of the ADINA System on your computer. ADINA User Interface Command Reference Manual Volume I: ADINA Solids & Structures Model Definition, Report ARD 08-2, February 2008 Volume II: ADINA Heat Transfer Model Definition, Report ARD 08-3, February 2008 Volume III: ADINA CFD Model Definition, Report ARD 08-4, February 2008 Volume IV: Display Processing, Report ARD 08-5, February 2008 These documents describe the AUI command language. You use the AUI command language to write batch files for the AUI. ADINA User Interface Primer, Report ARD 08-6, February 2008 Tutorial for the ADINA User Interface, presenting a sequence of worked examples which progressively instruct you how to effectively use the AUI. Theory and Modeling Guide Volume I: ADINA Solids & Structures, Report ARD 08-7, February 2008 Volume II: ADINA Heat Transfer, Report ARD 08-8, February 2008 Volume III: ADINA CFD & FSI, Report ARD 08-9, February 2008 Provides a concise summary and guide for the theoretical basis of the analysis programs ADINA, ADINA-T, ADINA-F, ADINA-FSI and ADINA-TMC. The manuals also provide references to other publications which contain further information, but the detail con- tained in the manuals is usually sufficient for effective understanding and use of the programs. ADINA Verification Manual, Report ARD 08-10, February 2008 Presents solutions to problems which verify and demonstrate the usage of the ADINA System. Input files for these problems are distributed along with the ADINA System programs. TRANSOR for PATRAN Users Guide, Report ARD 08-14, February 2008 Describes the interface between the ADINA System and MSC.Patran®. The ADINA Preference, which allows you to perform pre-/post-processing and analysis within the Patran® environment, is described. A tutorial example is given. TRANSOR for I-DEAS Users Guide, Report ARD 08-15, February 2008 Describes the interface between the ADINA System and UGS I-deas®. The fully inte- grated TRANSOR graphical interface is described, including the input of additional data not fully described in the I-DEAS® database. A tutorial example is given. ADINA System 8.5 Release Notes, February 2008 Provides a description of the new and modified features of the ADINA System 8.5. ADINA R & D, Inc. 1-15 You will also find the following book useful: K. J. Bathe, Finite Element Procedures, Prentice Hall, Englewood Cliffs, NJ, 1996. Provides theoretical background to many of the solution techniques used in the ADINA System. Sec. 1.10 Related documentation This page is intentionally left blank Chapter 2 Quick index Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-1 2.1 New commands, parameters and options In version 8.5, the following new commands, parameters and options were added to Volume III of the AUI Command Reference Manual. The commands are listed in the order in which they appear. Command Parameter Option/[Default] Page NASTRAN-ADINA ELFACESET, NODESET 3-15 RTOFILE 3-25 MASTER MESHADAPTIVE AUTO, MANUAL 5-3 MASTER ADAPTIVE-FILE 5-3 MASTER IRINT New description 5-3 MASTER ENSIGHT-OUTPUT 5.3 OUTER-ITERATION NODE- INTERPOLATION, FLUID-MAXIT, DISP- MAXIT 5-23 INITIAL-MAPPING TIME 7-142 SPLIT-EDGE 6-68 SPLIT-FACE 6-69 BODY OPTION 6-118 GVOLUME NCOINCIDE VOLUME (removed) 8-44 GFACE NLAYER 2 8-49 GFACE NCOINCIDE BOUNDEXSEL, EXSELECTED 8-49 GFACE NCOINCIDE SELECTED(removed) 8-49 GBODY NLAYER 2 8-54 GBODY NCOINCIDE EXSELECTED 8-54 ADP-MESH 8-81 ADP-CRITERION REQ 8-82 ADP-CRITERION RES 8-83 ADP-CRITERION RVG 8-84 ADP-CRITERION SPHERE 8-85 ADP-CRITERION LIST 8-86 SWEEP ALL-GROUP 9-11 REVOLVE ALL-GROUP 9-14 Chap. 2 Quick index Quick index 2-2 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition This page intentionally left blank Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-3 2.2 Quick overview of commands The following is a quick overview of all AUI commands in Volume III of the AUI Command Reference Manual and their functions. The commands are listed in order of appearance. Section 3.1: Database operations DATABASE NEW, creates a new database. DATABASE OPEN, creates a new database using the specified permanent database file. DATABASE WRITE, saves the modified current internal database as a permanent database file. DATABASE SAVE, saves the current internal database as a permanent database file. DATABASE ATTACH, allows access to the specified file as an AUI database file. DATABASE DETACH, creates a permanent database file by detaching a working copy of the database file. Section 3.2: Analysis data files ADINA-F, initiates model validation and/or creates an ADINA-F data file. Section 3.3: External files LOADDXF, loads an AutoCAD7 DXF file into the database. LOADIGES, loads an IGES file into the database. LOADSOLID, loads a Parasolid7 file into the database. NASTRAN-ADINA, maps a NASTRAN8 data file into the database. EXPORT UNIVERSAL, exports the mesh in ADINA-AUI to an I-DEAS7 universal file format. Section 3.4: Auxiliary files READ, reads AUI input commands from the specified file. FILEREAD, controls the source of input commands to the AUI. FILESESSION, controls the generation and output of a session file. FILELIST, controls the format and output of listings. FILEECHO, controls the echoing of input commands. FILELOG, controls the output of log messages. RTOFILE, defines the contents of a run- time-option file. Section 3.5: Program termination END, terminates the program. Section 3.6: Auxiliary commands PARAMETER, defines a parameter that can be substituted in a later command. REBUILD-MODEL, forces the AUI to rebuild the whole model. Chapter 4: Interface control and editing Section 4.1: Settings CONTROL, defines certain parameters that control program behavior. Section 4.2: Editing UNDO, cancels the effects of previous commands. Chap. 2 Quick index Quick index 2-4 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition REDO, cancels the effects of previous UNDO commands. Chapter 5: Control data Section 5.1: General FEPROGRAM, specifies the finite element analysis program to be used to solve the problem. HEADING, specifies a title for the problem described by the model database. MASTER , defines the data controlling the execution of ADINA-F. NONDIMENSIONAL, defines the scaling factors used for the nondimensional procedure. DATUM-PRESSURE, defines the pressure datum to be added to the computed pressure. Section 5.2: Analysis details ANALYSIS TRANSIENT, defines time integration parameters for transient flow analysis. Section 5.3: Options ACTIVE-VARIABLE, deactivates certain variables that are not used in the current computation. TEMPERATURE-REFERENCE, defines reference temperatures for both initial conditions and loads. Section 5.4: Solver details SOLVER ITERATIVE, defines control data for the iterative solution of the matrix system of equilibrium equations. LIMIT, defines the data controlling the solver for the FCBI element. Section 5.5: Automatic control AUTOMATIC TIME-STEPPING, defines parameters controlling the automatic time- stepping procedure. Section 5.6: Time dependence TIMESTEP, defines a timestep sequence which controls the time/loadstep incrementation during analysis. TIMEFUNCTION, defines a timefunction, which may be referenced, e.g., by an applied load. Section 5.7: Iteration ITERATION, selects the equilibrium iteration scheme to be employed for a non- linear analysis. OUTER-ITERATION, defines control parameters for outer iteration for the FCBI element. INNER-ITERATION, defines the parameters for inner iteration for the FCBI element. OVAR-CONTROL, defines the control data for outer iteration variables. IVAR-CONTROL, defines the control data for inner iteration variables. Section 5.8: Tolerances TOLERANCES GEOMETRIC, specifies certain geometric tolerances. TOLERANCES ITERATION, specifies the convergence criteria and corresponding tolerances controlling the equilibrium iteration scheme. TOLERANCES FLUID-STRUCTURE, specifies the convergence criteria and corresponding tolerance data controlling the iteration of fluid-structure interaction. Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-5 Section 5.9: Analysis output PRINTOUT, controls the amount of output printed. PRINT-STEPS, controls the output timesteps at which results are printed. PORTHOLE, controls the saving of input data and solution results on the porthole file. NODESAVE-STEPS, controls the output timesteps at which nodal results are saved on the porthole file. ELEMSAVE-STEPS, controls the output timesteps at which element results are saved on the porthole file. PRINTNODES, selects nodes (defined by "blocks" or geometry entities) for which solution results shall be printed. SAVENODES, selects nodes (defined by "blocks or geometry entities) for which solution results shall be saved on the porthole file. Chapter 6: Geometry definition Section 6.1: Coordinate systems SYSTEM, defines a local coordinate system. Section 6.2: Points COORDINATES POINT, defines geometry point coordinates. Section 6.3: Lines LINE STRAIGHT, defines a straight geometry line between two geometry points. LINE ARC, defines a geometry line as a circular arc, or as an arc with varying radius. LINE CIRCLE, defines a circle geometry line. LINE CURVILINEAR, defines a geometry line as a linearly interpolated curve in a given local coordinate system. KNOTS, defines a vector of knot values for NURBS definition. LINE POLYLINE, defines a geometry line as a polyline, i.e., a curve controlled by a series of geometry points. LINE SECTION, defines a geometry line to be part of another geometry line. LINE COMBINED, defines a geometry line as a combination of other geometry lines. LINE REVOLVED, defines a geometry line (a circular arc) by rotating a geometry point about an axis. LINE EXTRUDED, defines a geometry line by displacing a geometry point in a given direction. LINE TRANSFORMED, defines a geometry line to be a geometrical transformation of another geometry line. SPLIT-LINE, creates two geometry lines of type SECTION by splitting a given line into two parts connected at some point on the given line. LNTHICKNESS, defines line thicknesses (e.g. for defining axisymmetric shell thicknesses). Section 6.4: Surfaces SURFACE PATCH, defines a geometry surface to be bounded by edges which are specified geometry lines. SURFACE VERTEX, defines a geometry surface to be bounded by edges which are specified by their end geometry points - the vertices of the surface. SURFACE GRID, defines a geometry surface as a grid (array) of geometry points, which control the shape of the surface. SURFACE EXTRUDED, defines a geometry surface by displacing a geometry line in a given direction. Chap. 2 Quick index Quick index 2-6 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition SURFACE REVOLVED, defines a geometry surface by rotating a geometry line about some axis. SURFACE TRANSFORMED, defines a geometry surface via a transformation of another surface. SFTHICKNESS, defines surface thicknesses. CHECK-SURFACES, checks geometry surface connections looking for two adjoining surfaces which are oppositely oriented, i.e., with opposite surface normals. Section 6.5: Volumes VOLUME PATCH, defines a geometry volume to be bounded by faces which are specified geometry surfaces. VOLUME VERTEX, defines a geometry volume in terms of the vertices. VOLUME REVOLVED, defines a geometry volume by rotating a geometry surface about some axis. VOLUME EXTRUDED, defines a geometry volume by displacing a geometry surface in a given direction. VOLUME SWEEP, defines one or more geometry volumes by sweeping one or more geometry surfaces along a line. VOLUME TRANSFORMED, defines a geometry volume to be a geometrical transformation of another volume. Section 6.6: Solid models BODY SURFACES, defines a solid body via a collection of oriented surfaces. BODY VOLUMES, defines a solid body via a collection of volumes. FACE-THICKNESS, defines solid geometry face thicknesses. FACELINK, establishes a link, for meshing purpose, between two faces of distinct solid models, or between a face of a solid model and a surface. SPLIT-EDGE, splits an edge of a body into two edges by giving a parameter along the edge. SPLIT-FACE, splits a face of a body into two faces by giving two points on the face. BODY-DISCREP, creates a "discrete boundary representation" for a given body. BODY-DEFEATURE, removes small features from a discrete boundary representation of a body. BODY-CLEANUP, removes "short" body edges and/or "thin" body faces from the AUI representation of a body. BODY-RESTORE, restores the AUI topological representation of the body corresponding to its state before commands such as BODY-CLEANUP, REM-EDGE or REM-FACE are executed. Section 6.7: Spatial functions LINE-FUNCTION, describes the variation of a quantity along a line. SURFACE-FUNCTION, describes the variation of a quantity over a surface. VOLUME-FUNCTION, describes the variation of a quantity within a volume. Section 6.8: Transformations TRANSFORMATION COMBINED, defines a general transformation as an ordered sequence of existing transformations. TRANSFORMATION DIRECT, defines a general 3-D transformation by directly specifying the transformation matrix. TRANSFORMATION POINTS, defines a rigid-body 3-D transformation by the specification of 6 geometry points, 3 initial points and 3 target points. TRANSFORMATION REFLECTION, defines a 3-D reflection (mirror) transformation. Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-7 TRANSFORMATION ROTATION, defines a 3-D rotation transformation. TRANSFORMATION SCALE, defines a 3-D scaling transformation. TRANSFORMATION TRANSLATION, defines a 3-D translation transformation. TRANSFORMATION INVERSE, defines a 3-D geometry transformation as the inverse of another transformation. Section 6.9: Miscellaneous DOMAIN, defines a geometry domain, which is a collection of geometry entities. MEASURE, determines the distance between two points or the length of an edge or a line. GET-EDGE-FACES, lists the body faces connected to a body edge. GET-EDGE-POINTS, lists the AUI points bounding a body edge. GET-FACE-EDGES, lists the body edges bounding a body face. REM-EDGE, removes a body edge by collapsing one end point onto the other. REM-FACE, removes a body face by collapsing one bounding edge onto the other. Section 6.10: ADINA M BODY BLEND, modifies specified edges of a body to have a radius blend. BODY BLOCK, defines a solid geometry or brick shape. BODY CHAMFER, applies chamfers to edges of a solid body. BODY CONE, defines a cone shape solid geometry. BODY CYLINDER, defines a cylinder shape solid geometry. BODY HOLLOW, hollows a solid geometry with thickness THICKNESS. BODY INTERSECT, modifies an existing solid body by taking the intersection of it with other, overlapping body. BODY LOFTED, creates a sheet body by lofting through a set of lines or edges and creates a solid body by lofting through a set of surfaces, faces, and sheet bodies. BODY MERGE, modifies an existing solid body by joining it with a set of other solid bodies. BODY OPTION, provides the options for ADINA-M bodies. BODY PARTITION, partitions body with a set of faces of the body. BODY PIPE, defines a pipe shape solid geometry. BODY PRISM, defines a prismatic shape solid geometry. BODY PROJECT, projects lines into a face of the body. BODY REVOLVED, creates a body by revolving face of existing body around an axis. BODY SECTION, partition solid body using sheets. BODY SEW, sews a set of sheet bodies into sewn bodies. BODY SHEET, defines a sheet body by a set of geometry lines. BODY SPHERE, defines a sphere shape solid body. BODY SUBTRACT, modifies an existing solid body by removing from it a set of other solid, overlapping bodies. BODY SWEEP, creates a body by sweeping existing face of a body in a given direction or along a line. BODY TORUS, defines a torus shape solid geometry. BODY TRANSFORMED, defines a solid geometry by copying or moving an existing Parasolid® body. SHEET PLANE, defines a planar sheet used for partition of bodies. VOLUME BODY, converts a body into a geometrical volume. SURFACE FACE, converts a face of a body into a geometric surface. Chap. 2 Quick index Quick index 2-8 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition Chapter 7: Model definition Section 7.1: Material models MATERIAL CONSTF, defines a fluid material with constant properties. MATERIAL TEMPDEP-F, defines a fluid material with temperature-dependent properties. MATERIAL TIMEDEP-F, defines a fluid material with time-dependent properties. MATERIAL POWER, defines the properties of a power law fluid material. MATERIAL TEMPDEP-POWER, defines the properties of a temperature-dependent power law fluid material. MATERIAL SECOND-ORDER, defines the properties of a second-order fluid material. MATERIAL CARREAU, defines the properties of a Carreau fluid material. MATERIAL POROUS, defines the properties of a porous material. MATERIAL P-T-DEPENDENT, defines a pressure-temperature dependent material. MATERIAL COMPRESSIBLE- CONSTANT, defines a constant property compressible fluid material model. MATERIAL COMPRESSIBLE-T- DEPENDENT, defines a temperature- dependent property compressible fluid material model. MATERIAL COMPRESSIBLE-P- DEPENDENT, defines a pressure- dependent property compressible fluid material model. MATERIAL COMPRESSIBLE-P-T- DEPENDENT, defines a pressure- and temperature-dependent property compressible fluid material model. MATERIAL COMPRESSIBLE-POWER- LAW, defines a power law property compressible fluid material model. MATERIAL COMPRESSIBLE-USER- SUPPLIED, defines a user-supplied property compressible fluid material model. MATERIAL TURBULENT-KE, defines the properties of a k-g model for a turbulent fluid material. MATERIAL TURBULENT-MIXL, defines the properties for a mixing length model for a turbulent fluid material. MATERIAL TURBULENT-KW, defines the properties of a k-T model for a turbulent fluid material. MATERIAL TURBULENT-LES, defines the properties of an LES model for a turbulent fluid material. MATERIAL TURBULENT-SA, defines the properties of a Spalart-Allmaras model for a turbulent fluid material. MATERIAL MASS, defines the properties of a mass-transfer material model. MATERIAL ASME-STEAM, defines a fluid material based on the ASME Steam Tables. VOF-MATERIAL, defines VOF materials and related control parameters. FCURVE, defines a fluid material properties curve. Section 7.2: Element properties SURF-ELEMDATA TWODFLUID, assigns data for TWODFLUID elements on geometry surfaces. FACE-ELEMDATA TWODFLUID, assigns data for TWODFLUID elements on geometry faces. VOL-ELEMDATA THREEDFLUID, assigns data for THREEDFLUID elements to geometry volumes. BODY-ELEMDATA THREEDFLUID, assigns data for THREEDFLUID elements to geometry bodies. EM-PROPERTY, defines electro-magnetic properties for an existing material. Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-9 Section 7.3: Boundary conditions CONSTRAINT, specifies a constraint equation which expresses a slave (dependent) degree of freedom as a linear combination of a set of master (independent) degrees of freedom. CONSTRAINT-MS, similar to CONSTRAINT, but also allows the specification of multiple slave entities for a single master entity. FIXITY, defines a fixity boundary condition. FIXBOUNDARY, assigns fixity conditions to a set of geometry entities. BOUNDARY-CONDITION WALL, defines a "wall" fluid boundary condition. BOUNDARY-CONDITION FLUID- STRUCTURE, defines a fluid-structure interaction boundary condition. BOUNDARY-CONDITION FREE- SURFACE, defines a free-surface fluid boundary condition. BOUNDARY-CONDITION FLUID- FLUID, defines a fluid-fluid interface boundary condition. BOUNDARY-CONDITION PHASE- CHANGE, defines a phase-change interface boundary condition. BOUNDARY-CONDITION CONVECTION, defines a convection boundary condition. BOUNDARY-CONDITION RADIATION, defines a radiation boundary condition. BOUNDARY-CONDITION THERMAL- RESISTANCE, defines a themal resistance boundary condition. BOUNDARY-CONDITION SPECULAR, defines a specular radiosity boundary condition. BOUNDARY-CONDITION MASS- CONVECTION, defines a mass convection boundary condition. BOUNDARY-CONDITION COMPRESSIBLE, defines a compressible fluid flow boundary condition. BOUNDARY-CONDITION GAP, defines a gap boundary condition. BOUNDARY-CONDITION UNIFORMFLOW, defines a uniformflow boundary condition. BOUNDARY-CONDITION ANGULARVELOCITY, defines an angular velocity boundary-condition. BOUNDARY-CONDITION VOF-WALL- ANGLE, defines a VOF wall-angle boundary condition and specifies regions across which no flow can take place. BOUNDARY-CONDITION SHELL- THERMAL, defines a shell-thermal boundary-condition for ADINA-F and sets the boundary condition to model geometry. BOUNDARY-CONDITION SLIDING- MESH, defines a sliding-mesh boundary- condition for ADINA-F and sets the boundary condition to model geometry. BOUNDARY-CONDITION FRICTION, defines a friction boundary-condition for ADINA-F and sets the boundary condition to model geometry. BOUNDARY-CONDITION VENT, defines a vent boundary-condition for ADINA-F and sets the boundary condition to model geometry. BOUNDARY-CONDITION FAN, defines a fan boundary-condition for ADINA-F and sets the boundary condition to model geometry. BOUNDARY-CONDITION USER- SUPPLIED, defines a user-supplied boundary condition. BCDPAIR, specifies boundary conditions which are used as pairs in analysis. BCELL, defines a boundary cell using a 4- node or 3-node cell. Chap. 2 Quick index Quick index 2-10 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition FIX-MESH, specifies geometry entities for which any generated nodes are fixed - i.e., no mesh movement is allowed. LEADER-FOLLOWER, specifies a mesh- movement constraint between pairs of geometry points. SLIPPING-BOUNDARY, defines a geometry boundary region over which nodes may be constrained to slip. Section 7.4: Loading LOAD CENTRIFUGAL, defines a centrifugal load. LOAD TEMPERATURE, defines a temperature load. LOAD HEATFLUX, defines a heatflux load. LOAD NODAL-HEATFLOW, defines a nodal-heatflow, i.e., a concentrated heat flux load. LOAD NORMAL-TRACTION, defines a normal-traction load. LOAD NODAL-PRESSURE, defines a nodal-pressure load. LOAD VELOCITY, defines a velocity load. LOAD ROTATION, defines a rotational velocity load. LOAD TURBULENCE, defines a turbulence load. LOAD MASSFLUX, defines a massflux load. LOAD MASS-RATIO, defines a mass-ratio load. LOAD ELECTRIC-POTENTIAL, defines an electric potential load. LOAD CURRENT-DENSITY, defines a current density load. LOAD EM-FLUX, defines an electro- magnetic flux load. LOAD VOF-SPECIES, defines a VOF- species load. LOAD FIELD-FRICTION, defines a field- friction force load. LOAD RIGID-MOTION, defines a rigid- motion load. APPLY-LOAD, specifies loads applied to model geometry. Section 7.5: Initial conditions INITIAL-CONDITION, defines an initial condition. SET-INITCONDITION, assigns initial conditions to a set of geometry entities. INITIAL-MAPPING, loads an initial mapping file and interpolates variable values at nodes. Section 7.6: Systems SKEWSYSTEMS CYLINDRICAL, defines a "skew" Cartesian co-ordinate system in terms of a cylinder origin and axis direction. SKEWSYSTEMS SPHERICAL, defines a "skew" Cartesian co-ordinate system in terms of a sphere origin. SKEWSYSTEMS EULERANGLES, defines a "skew" Cartesian coordinates system in terms of Euler angles. SKEWSYSTEMS VECTORS, defines a "skew" Cartesian coordinate system in terms of direction vectors. SKEWSYSTEM POINTS, defines a "skew" Cartesian coordinate system in terms of geometry points. SKEWSYSTEMS NORMAL, defines a skew Cartesian coordinate system to be such that one of its directions is normal to a given line or surface. DOF-SYSTEM POINTS, assigns skew coordinate systems to a set of geometry points. DOF-SYSTEM LINES, assigns skew coordinate systems to a set of geometry lines. DOF-SYSTEM EDGES, assigns skew coordinate systems to a set of geometry edges. Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-11 DOF-SYSTEM SURFACES, assigns skew coordinate systems to a set of geometry surfaces. DOF-SYSTEM FACES, assigns skew coordinate systems to a set of geometry faces. DOF-SYSTEM VOLUMES, assigns skew coordinate systems to a set of geometry volumes. DOF-SYSTEM BODIES, assigns skew coordinate systems to a set of geometry bodies. AXIS-ROTATION, defines a rotational axis which can be referenced by other commands. AXES NODES, defines an "axes-system" via three nodes. Section 7.7: Mass transfer ACTIVEMASS, defines the active species used in mass transfer analysis. BULKDENSITY, defines a "bulk" density by specifying coefficients for a weighted sum of species densities. Section 7.8: Data functions ONE-D-FUNCTION, defines a general function of one variable. Section 7.9: Control data PHASE-CONTROL, defines control parameters governing phase change for a given material. VOF-CONTROL, defines control data for the VOF method. Chapter 8: Finite element representation Section 8.1: Element groups EGROUP TWODFLUID, defines an element group consisting of planar or axisymmetric elements. EGROUP THREEDFLUID, defines an element group consisting of three- dimensional elements. Section 8.2: Mesh generation SUBDIVIDE DEFAULT, defines default mesh subdivision data for the model. SUBDIVIDE MODEL, assigns mesh subdivision data to the entire current model geometry. SUBDIVIDE POINT, assigns mesh subdivision data to geometry points. SUBDIVIDE LINE, assigns mesh subdivision data to geometry lines. SUBDIVIDE SURFACE, assigns mesh subdivision data to geometry surfaces. SUBDIVIDE VOLUME, assigns mesh subdivision data to geometry volumes. SUBDIVIDE EDGE, assigns mesh subdivision data to edges of a solid geometry body. SUBDIVIDE FACE, assigns mesh subdivision data to faces of a solid geometry body. SUBDIVIDE BODY, assigns mesh subdivision data to solid geometry bodies. POINT-SIZE, specifies the element size at geometry points. SIZE-FUNCTION BOUNDS, defines a mesh size function using the vertices of the model bounding box. Chap. 2 Quick index Quick index 2-12 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition SIZE-FUNCTION HEX, defines a mesh size function using the vertices of an input box. SIZE-FUNCTION POINT, defines a mesh size function via a point source. SIZE-FUNCTION AXIS, defines a mesh size function via a line source. SIZE-FUNCTION PLANE, defines a mesh size function via a planar source. SIZE-LOCATIONS, specifies mesh-size at certain locations (other than geometry points). GPOINT, generates nodes at geometry points with the same coordinates. GSURFACE, creates elements on a set of geometry surfaces. GVOLUME, creates elements in a set of geometry volumes. GFACE, creates elements on a set of solid geometry faces. GBODY, creates elements for a set of solid geometry bodies. GHEXA, generates brick element dominant free-form meshes for a given body. GADAPT, deletes and remeshes a finite element mesh. GBCELL, creates 3-D elements from boundary cells. NLTABLE, creates a table which specifies the minimum number of layers across thin sections in a body or on a face. BLAYER, generates boundary layers on specified body faces/edges for the specified group. ELDELETE, deletes elements generated on specified geometry for a given element group. COPY-MESH-BODY, copies a mesh from one body to another body via affine transformation. COPY-TRIANGULATION, copies face triangulation for later use by meshing commands like GFACE or GBODY. DELETE-TRIANGULATION, deletes face triangulations created by the COPY- TRIANGULATION command. LIST-TRIANGULATION, lists all faces (body and face labels) which have triangulation created by the COPY- TRIANGULATION command. MECONSTRAIN, constrains elements of the selected groups during mesh adaptation. ADP-MESH, examines and deletes elements according to the criteria defined in the ADP-CRITERION commands, and remeshes the cavities resulting from the deletion according to the given mesh densities. ADP-MESH REQ, defines the criterion based on Relative Element Quality (REQ). ADP-MESH RES, defines the criterion based on Relative Element Size (RES). ADP-MESH RVG, defines the criterion based on Relative Variable Gradient (RVG). ADP-MESH SPHERE, defines a sphere in which elements shall be repaired. ADP-MESH LIST, defines a direct list of elements to be repaired. Chapter 9: Direct finite element data input Section 9.1: Nodal data COORDINATES NODE, defines coordinates for nodes. SKEWSYSTEMS NODES, defines a "skew" Cartesian co-ordinate system in terms of nodes. DOF-SYSTEM NODES, assigns skew coordinate systems to nodes. NODESET, defines a collection of nodes by label number. Section 9.2: Element data ENODES, defines element nodal connectivity for a specified element group. EDATA, specifies property data associated with individual elements in a group. Quick index Chap. 2 Quick index ADINA R & D, Inc. 2-13 COPY-ELEMENT-NODES, copies all elements and nodes (in groups) between database models for two analysis programs. Section 9.3: Element generation SWEEP, generates a volume of THREEDFLUID elements by extruding TWODFLUID elements along a given vector. REVOLVE, generates a volume of THREEDFLUID elements by revolving TWODFLUID elements about an axis. DELETE-FE-MODEL, deletes all finite- element data from the database. Section 9.4: Boundary conditions ELEDGESET, defines an element edge set containing edges of 2-D elements. ELFACESET, defines an element face set containing faces of 3-D and shell elements. BOUNDARIES, assigns boundary conditions to nodes. CONSTRAINT-NODE, specifies a constraint equation between nodal degrees of freedom. Section 9.5: Loads APPLY CONCENTRATED-LOADS, defines concentrated loads applied to nodes. APPLY VARIABLES, defines prescribed variables applied to nodes. APPLY MASS-RATIO, defines prescribed mass-ratio at nodes. LOADS-ELEMENT, applies loads onto element faces (either normal-traction or heat-flux loads). Section 9.6: Initial conditions INITIAL TEMPERATURES, assigns initial temperatures to nodes. INITIAL VELOCITIES, assigns initial velocities to nodes. INITIAL PRESSURE, assigns initial pressure to nodes. INITIAL MASS-RATIO, assigns initial mass-ratios to nodes. Section 9.7: Moving mesh ALE-NODE, defines an internal ale boundary using nodes. ALE-FACE, defines an ALE boundary using element face node. LFOLLOWER-NODE, defines a mesh- movement constraint such that during analysis, the movement of the follower node is governed by the movement of the leader node. Chapter 3 Input/Output DATABASE NEW Sec. 3.1 Database operations ADINA R & D, Inc. 3-1 DATABASE NEW SAVE PERMFILE PROMPT DATABASE NEW creates a new database. The new database is initially empty. Before creating the new database, you have the option of saving any current internal database to disk. This option is controlled by parameters SAVE and PERMFILE. SAVE [UNKNOWN] Used only when a database has been modified. YES The program saves the current internal database to disk using the filename specified by parameter PERMFILE. Then the program creates a new internal database. NO The program does not save the current internal database before creating a new internal database. UNKNOWN The program asks you if you want to save the database. PERMFILE [the last permanent database name previously specified] Used only when the database has been modified. PERMFILE is the filename of the permanent database file when saving the current database file to disk. You will be prompted for this name if you do not enter a value for this parameter and no permanent database name was previously specified. PROMPT [UNKNOWN] Used when saving a permanent database file. YES You will be prompted "Ready to save permanent database file?". UNKNOWN You will be prompted "Permanent database file already exists" if the database file already exists. NO You will not receive a prompt. Auxiliary commands DATABASE CREATE SAVE PERMFILE DATABASE CREATE has the same effect as DATABASE NEW. Chap. 3 Input/Output DATABASE OPEN 3-2 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition DATABASE OPEN FILE SAVE PERMFILE PROMPT DATABASE OPEN creates a new database using the permanent database file specified in this command. Before creating the new database, the current internal database is optionally saved to disk. FILE [the last previously specified permanent database filename] The filename of the permanent database file to be opened. If you do not enter a filename and there is no default value, the program will prompt you for the filename. SAVE [UNKNOWN] Used only when a database has been modified. YES The current internal database is saved to disk using the filename specified by parameter PERMFILE. NO The current internal database is not saved before clearing the current database and opening the specified database. UNKNOWN The program will ask you if you want to save the database. PERMFILE [the last previously specified permanent database filename] Used only if the database has been modified. PERMFILE is the filename of the permanent database file when saving the current database file to disk. The program will prompt you if you do not enter a value for PERMFILE and if no permanent database filename has previously been specified. PROMPT [UNKNOWN] Used when saving a permanent database file. YES You will be prompted "Ready to save permanent database file?". UNKNOWN You will be prompted "Permanent database file already exists," if the database file already exists. NO You will not receive a prompt. DATABASE WRITE Sec. 3.1 Database operations ADINA R & D, Inc. 3-3 DATABASE WRITE PERMFILE PROMPT DATABASE WRITE saves the current internal database as a permanent database file. It is the same as the DATABASE SAVE command except that DATABASE WRITE is available only when the database has been modified. PERMFILE [the last previously entered permanent database filename specified] Specifies the filename of the permanent database file. The program will prompt you if you do not enter a value for PERMFILE and if no permanent database filename has previously been specified. PROMPT [UNKNOWN] Used when saving a permanent database file. YES You will be prompted "Ready to save permanent database file?". UNKNOWN You will be prompted "Permanent database file already exists" if the database file already exists. NO You will not receive a prompt. Chap. 3 Input/Output DATABASE SAVE 3-4 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition DATABASE SAVE PERMFILE PROMPT DATABASE SAVE saves the current internal database as a permanent database file. PERMFILE [the last previously entered permanent database filename specified] Specifies the filename of the permanent database file. The program will prompt you if you do not enter a value for PERMFILE and if no permanent database filename has previously been specified. PROMPT [UNKNOWN] Used when saving a permanent database file. YES You will be prompted "Ready to save permanent database file?". UNKNOWN You will be prompted "Permanent database file already exists" if the database file already exists. NO You will not receive a prompt. DATABASE ATTACH Sec. 3.1 Database operations ADINA R & D, Inc. 3-5 DATABASE ATTACH FILE DATABASE ATTACH allows access to the specified file as an AUI database file. Unlike DATABASE OPEN, DATABASE ATTACH does not make a working copy of the database file prior to opening it. Instead you work directly with the specified file as you use the AUI, possibly modifying the file's contents. The advantages of DATABASE ATTACH as compared to DATABASE OPEN are: disk requirements are reduced because the AUI does not create a copy of the database file, and the CPU time to attach a database is much less than the CPU time required to open the same file. The disadvantages of DATABASE ATTACH are: (1) important information can be inadvertently modified or deleted from an attached database file, (2) the attached database cannot shrink, but can only grow as the AUI is used and (3) an attached database file cannot be saved, but can only be detached using DATABASE DETACH. Before DATABASE ATTACH can be used, any current database must first be saved, and then DATABASE CREATE or DATABASE NEW must be used to create a new database. DATABASE ATTACH can be used only if the current database is new and unmodified. Exiting the AUI when a database is attached causes the database to automatically detach. FILE The filename of the permanent database file to be attached. If no file name is entered, the AUI will prompt you for the filename. Chap. 3 Input/Output DATABASE DETACH 3-6 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition DATABASE DETACH PERMFILE PROMPT DATABASE DETACH creates a permanent database file by detaching the working copy of the database file. Unlike DATABASE SAVE, DATABASE DETACH does not create a new permanent database file. The advantages of DATABASE DETACH as compared to DATABASE SAVE are: disk requirements are reduced because the AUI does not create a copy of the database file, and the CPU time to detach a database is much less than the CPU time required to save it. The disadvantage of DATABASE DETACH is the AUI does not compress the database file by removing unused records. After the database is detached, the AUI creates a new empty internal database. A database can be detached at any time whether or not it was attached using DATABASE ATTACH. PERMFILE The working copy of the database file is renamed to PERMFILE. PROMPT [UNKNOWN] Used when saving a permanent database file. YES You will be prompted "Ready to save permanent database file?". UNKNOWN You will be prompted "Permanent database file already exists" if the database file already exists. NO You will not receive a prompt. ADINA-F Sec. 3.2 Analysis data files ADINA R & D, Inc. 3-7 ADINA-F OPTIMIZE STARTNODE FILE FIXBOUNDARY MIDNODE OVERWRITE FORMATTED OPTIMIZE ADINA-F initiates model validation and, if the model is valid, creates an ADINA-F input data file. OPTIMIZE [SOLVER] Equation numbering is optimized so as to minimize the profile and bandwidth of the ADINA-F solution matrices. The node label numbers are not affected by the equation numbering. {SOLVER / YES / NO} SOLVER If the sparse solver is used (see parameter SOLVER in command MASTER), then equation numbering is not optimized. Otherwise, equation numbering is optimized. YES Equation numbering is optimized. NO Equation numbering is not optimized. STARTNODE [automatically selected] Label number of a main structure node, used to initiate the optimized equation numbering algorithm. If such a node is not given, one will be automatically selected. The starting node should be a peripheral node on the boundary of the model. FILE The filename of the ADINA-F input file to be generated. If no filename is given, only model validation is performed. FIXBOUNDARY [YES] Inactive degrees of freedom, i.e., those which are not connected to any elements and are not used as slaves in constraint equations, may be automatically deleted. {YES / NO} MIDNODE [NO] Midside nodes on element edges may be moved to the straight line connecting the relevant vertex nodes. {YES / NO} OVERWRITE [UNKNOWN] Determines, if the filename given by FILE already exists, whether the command will overwrite its contents with the currently generated input data. If set to UNKNOWN, a prompt will be given requesting confirmation for overwriting an existing file. {YES / NO / UNKNOWN} FORMATTED [YES] The ADINA-F data file records may be formatted or written in unformatted binary. {YES / NO} Chap. 3 Input/Output LOADDXF 3-8 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition LOADDXF FILE GCOINCIDE GCTOLERANCE LOADDXF loads an AutoCAD7 DXF file into the database. The points and lines are converted into AUI geometry entities. FILE The DXF file to be loaded in this command. Only a file in R-12 DXF format is accepted. GCOINCIDE [YES] Point coincidence checking. If GCOINCIDE is set to YES then point coordinates are checked, and if within GCTOLERANCE * (max. difference in global coordinates between all previous points) then no new point number is created at that location, i.e., the previous point label number is assumed. {YES / NO} GCTOLERANCE [1.0E-5] Tolerance used to determine point coincidence. LOADDXF Sec. 3.2 Analysis data files ADINA R & D, Inc. 3-9 This page intentionally left blank. Chap. 3 Input/Output LOADIGES 3-10 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition LOADIGES FILE GCOINCIDE GCTOLERANCE TWOD-XY ADINA-M LABEL SEWING SEWGAP TOLER1 TOLER2 OPTION1 REVERSE OPTION3 OPTION4 SCALEFACTOR PRECS PLABEL LLABEL XZERO Loads an IGES file into the database. FILE The IGES file to be loaded in this command. Only a formatted and uncompressed file is accepted. GCOINCIDE [YES] Point coincidence checking option. If set to YES, then point coordinates are checked, and if within GCTOLERANCE * (max. difference in global coordinates between all previous points) then no new point is created at that location, i.e. the previous point label number is assumed. {YES / NO}. GCTOLERANCE [1.0E-5] Tolerance used to determine point coincidence. TWOD-XY [NO] Indicates whether or not to rotate the IGES geometry model so that the XY plane is transformed into the YZ plane (as used in two-dimensional ADINA, ADINA-T, and ADINA- F models). {YES / NO} ADINA-M [NO] Indicates whether IGES data is to be loaded into ADINA-M. {YES/NO} Parameters GCOINCIDE, GCTOLERANCE and TWOD-XY are ignored by ADINA-M. LABEL [(highest current body label number) + 1] Sheet body or solid body label number. SEWING [NO] Indicates wether ADINA-M sheet bodies are to be sewn together. {YES / NO} SEWGAP [0.01] ADINA-M sewing body gap ratio. The gap value used to sew the body is SEWGAP * (max. difference in global coordinate between the maximum and minimum of the IGES body). TOLER1 This tolerance is obsolete. LOADIGES Sec. 3.3 External data ADINA R & D, Inc. 3-11 TOLER2 This tolerance is obsolete. OPTION1 This tolerance is obsolete. REVERSE This tolerance is obsolete. OPTION3 This tolerance is obsolete. OPTION4 This tolerance is obsolete. SCALEFACTOR [1.0] ADINA-M scale factor - input IGES coordinate values are to be divided by, i.e. (x-coordinate, y-coordinate, z-coordinate)/scalefactor. PRECS This tolerance is obsolete. PLABEL [(current highest point label number) + 1] Point label number of the importing IGES model into AUI native geometry database. LLABEL [(current highest point label number) + 1] Line label number of the importing IGES model into AUI native geometry database XZERO [NO] The flag to set the x coordinate to 0. {NO / YES} Chap. 3 Input/Output LOADIGES 3-12 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition This page intentionally left blank. LOADSOLID Sec. 3.3 External data ADINA R & D, Inc. 3-13 LOADSOLID PARTFILE BODYNAME XORIGIN YORIGIN ZORIGIN AX AY AZ BX BY BZ PCOINCIDE PCTOLERANCE MANIFOLD FORMAT OLD-UNIT NEW-UNIT SYSTEM REPAIR The LOADSOLID command loads a Parasolid7 part (or "transmit") file into the database. The model can be displayed, meshed, and loads, boundary conditions may be assigned to its faces, edges, and vertices. For each body within the Parasolid7 file a solid geometry BODY is created which is used to reference that body. This command is only active when ADINA-M has been licensed. PARTFILE The name of a Parasolid7 part file (i.e. for part file name "abcdef.x_t" you input PARTFILE=abcdef). BODYNAME [(current highest body label number) + 1] This is the label number to be assigned to the first BODY to be created which is used to refer to the first body in the part file -- other bodies in the part file will automatically be assigned BODY label numbers incremented from this parameter (i.e. (BODYNAME+1), (BODYNAME+2), ... .) XORIGIN [0.0] YORIGIN [0.0] ZORIGIN [0.0] ADINA-M translates the imported model so that the origin of the model is assigned these global coordinates. AX [1.0] AY [0.0] AZ [0.0] ADINA-M rotates the imported model so that the model X-axis has this direction (in global coordinates). BX [0.0] BY [1.0] BZ [0.0] ADINA-M rotates the imported model so that the model X-Y plane lies in the plane given by (AX, AY, AZ) and (BX, BY, BZ) (in global coordinates). PCOINCIDE [NO] Indicates whether or not the vertices of the model are to be checked for coincidence with existing geometry point coordinates. {NO / YES} Chap. 3 Input/Output LOADSOLID 3-14 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition PCTOLERANCE [0.00001] Tolerance used to determine whether two points are coincident. MANIFOLD [NO] Indicates whether non-manifold bodies are converted into manifold bodies. {NO / YES} FORMAT [TEXT] Parasolid7 part file format. TEXT text format. BINARY binary format. OLD-UNIT [METER] The unit of the part in the Parasolid7 file to be imported. { METER / CMETER / MMETER / INCH / FOOT } NEW-UNIT [METER] The unit of the part after it is imported into ADINA-M. { METER / CMETER / MMETER / INCH / FOOT } SYSTEM [0] If system label is greater than 0 and it is Cartesian coordinate system, replace XORIGIN, YORIGIN, ZORIGIN, AX, AY, AZ, BX, BY, BZ with the values from the given system. REPAIR [NO] Repair the bodies if errors are detected. {NO / YES} NASTRAN-ADINA Sec. 3.3 External data ADINA R & D, Inc. 3-15 NASTRAN-ADINA FILE XY-YZ SUBCASE BCELL DUPLICATE SPLIT ELFACESET NODESET NASTRAN-ADINA maps a NASTRAN® data file into the ADINA-IN database. FILE The NASTRAN® data filename. XY-YZ This parameter is now obsolete. The program will automatically rotate 2D models in the XY plane to the YZ plane. SUBCASE [0] The label number of a subcase defined in the NASTRAN® data file. If not specified, the first subcase is used. {≥1} BCELL [NO] Indicates whether boundary cells (see command BCELL) are created from shell elements according to the property identification number (PID). All elements with the same PID are put into the same BCELL. {NO/YES/REPLACE} NO Do not create boundary cells. YES Create boundary cells. In addition, if the shell elements are attached to 3-D elements, the program will also create element-face sets (see ELFACESET command) and node sets (see NODESET command). REPLACE Same as BCELL=YES. DUPLICATE [YES] This flag indicates whether or not to issue an error message when the Nastran file has a duplicate node or element. {NO/YES} NO No error message issued. Later entries will override the earlier entries. YES Error message issued. SPLIT [NO] The flag indicates whether same PID but different command will be split into different element groups. {NO/YES} ELFACESET [BCELL] Flag to create elfaceset from attached SHELL element. {BCELL/NO/YES/REPLACE} Chap. 3 Input/Output NASTRAN-ADINA 3-16 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition BCELL Take the default flag from BCELL parameter NO No elfaceset will bce created YES Create elfaceset and keep the attached SHELL element group REPLACE Create elfaceset then delete the attached SHELL element group Note that as long as one of BCELL, ELFACESET or NODESET = REPLACE the attached SHELL element will be deleted. NODESET [BCELL] Flag to create nodeset from attached SHELL element. {BCELL/NO/YES/REPLACE} BCELL Take the default flag from BCELL parameter NO No nodeset will bce created YES Create nodeset and keep the attached SHELL element group REPLACE Create nodeset then delete the attached SHELL element group Note that as long as one of BCELL, ELFACESET or NODESET = REPLACE the attached SHELL element will be deleted. EXPORT UNIVERSAL Sec. 3.3 External data ADINA R & D, Inc. 3-17 EXPORT UNIVERSAL FILE Exports the mesh in ADINA-AUI to an I-DEAS7 universal file format. FILE Specifies the name of the universal file to be created. Chap. 3 Input/Output EXPORT UNIVERSAL 3-18 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition This page intentionally left blank. READ Sec. 3.4 Auxiliary files ADINA R & D, Inc. 3-19 READ FILE REWIND SCANDATA READ reads AUI input commands from the file specified by parameter FILE until the end of the file is reached or the READ END command is encountered in the file. After the READ command is executed, subsequent input is read from the previous command input source (that is, the input source from which the READ command was entered). READ commands can be nested (that is, a file processed by the READ command can itself include a READ command). FILE The name of the file from which AUI commands are read (up to 80 characters long). Note that the name END is not allowed. REWIND [NO] If the file pointer is at end-of-file or if the file is not currently open, the read file is rewound before beginning to read commands regardless of the value of this parameter. {YES / NO} SCANDATA [' '] If SCANDATA is specified, the file is scanned until the SCANDATA string (1 - 80 characters) is found anywhere within an input record. Reading of input data from the file starts at the beginning of the record that contains the string. Auxiliary commands READ END Terminates reading from file. Chap. 3 Input/Output FILEREAD 3-20 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition FILEREAD OPTION FILE FILEREAD controls the source of input commands to the AUI. OPTION [INTERFACE] INTERFACE Commands are read from the terminal or window from which you invoked the AUI. FILE Commands are read from the file specified by the FILE parameter. FILE The filename of the file from which commands are read. Used only if OPTION=FILE. Auxiliary commands LIST FILEREAD FILESESSION Sec. 3.4 Auxiliary files ADINA R & D, Inc. 3-21 FILESESSION OPTION FILE FILESESSION controls the generation and output of a session file. The session file contains the commands needed to repeat an AUI session. A session file differs from an echo file in that: 1) You can generate a session file from a user-interface AUI session (this is the primary use of the session file). 2) A session file contains all command parameters, regardless of whether you entered them or whether they were default parameters. 3) Changes to data input lines are handled in a different manner. OPTION [NO] NO No session file is created. OVERWRITE A session file is generated and overwrites any existing contents of the specified file. APPEND A session file is generated and is appended to any existing contents of the specified file. FILE The filename of the session file. Auxiliary commands LIST FILESESSION Chap 3 Input/Output FILELIST 3-22 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition FILELIST OPTION FILE LINPAG EJECT FILELIST controls the format and output of listings. OPTION [INTERFACE] INTERFACE Listings are output at the terminal or window from which you invoked the AUI. Listings are buffered using an interface similar to UNIX "more" that allows you to scroll through listings. FILE Listings are output to the file specified by the FILE parameter. FILE The filename of the file to which listings are written. Used only if OPTION=FILE. This can be the same file used for command echoing or logging. LINPAG [0] The maximum number of lines output between list headings. You can suppress list headings (except for the first list heading) by specifying LINPAG=0. EJECT [NO] Specifies whether page ejects are placed before headings. {YES / NO} Auxiliary commands LIST FILELIST FILEECHO Sec. 3.4 Auxiliary files ADINA R & D, Inc. 3-23 FILEECHO OPTION FILE FILEECHO controls the echoing of your input commands. OPTION [INTERFACE] NO No echoing of input commands. INTERFACE Input commands are echoed back to the terminal or window from which you invoked the AUI. FILE Input commands are echoed back to the file specified by the FILE parameter. FILE The filename of the file to which input commands are echoed back. Used only if OPTION=FILE. This can be the same file for logs or listings. Auxiliary commands LIST FILEECHO Chap 3 Input/Output FILELOG 3-24 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition FILELOG OPTION FILE FILELOG controls the output of log messages. OPTION [INTERFACE] INTERFACE Log messages are written to the terminal or window from which you invoked the AUI. FILE Log messages are written to the file specified by the FILE parameter. FILE The filename of the file to which log messages are written. Used only if OPTION=FILE. This can be the same file used for echoed commands or listings. Auxiliary commands LIST FILELOG RTOFILE Sec. 3.4 Auxiliary files ADINA R & D, Inc. 3-25 RTOFILE PROGRAM texti This command defines the contents of a run-time-option (.rto) file. When an ADINA, ADINA-T or ADINA-F data file (.dat file) is created, a corresponding run-time-option file (.rto file) is also created. If the RTOFILE command is not run, or if there are no lines of text in the RTOFILE command, then no .rto file is created. PROGRAM [Current FE program] The finite element program for which the .rto file will be created. {ADINA / ADINA-T / ADINA-F} texti A line of text in the .rto file. This text must be enclosed by single quotes. There can be an arbitrary number of lines of text in the .rto file. Allowable input in the .rto file depends on the finite element program. Auxiliary commands LIST RTOFILE DELETE RTOFILE Chap. 3 Input/output END 3-26 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition END SAVE PERMFILE PROMPT IMMEDIATE END terminates the program. EXIT, QUIT and STOP are equivalent to END. If the program is reading data from a file specified by the FILEREAD command and the end of the file is reached, the END command is executed automatically. SAVE [UNKNOWN] Used only when a database has been modified. YES The program saves the current internal database to disk using the filename specified by parameter PERMFILE. Then the program creates a new internal database. NO The program does not save the current internal database before creating a new internal database. UNKNOWN The program asks you if you want to save the database. PERMFILE [the last previously specified permanent database filename] PERMFILE is the filename of the permanent database file when saving the current database file to disk; used only if the database has been modified. The program will prompt you if you do not enter a value for PERMFILE and if no permanent database filename has previously been specified. PROMPT [UNKNOWN] Used when saving a permanent database file. YES You will be prompted "Ready to save permanent database file?". UNKNOWN You will be prompted "Permanent database file already exists" if the database file already exists. NO You will not receive a prompt. IMMEDIATE [NO] If IMMEDIATE=YES, the program immediately stops execution without saving the database or prompting you. This option is most useful when writing batch scripts to force the program to terminate. {YES / NO} Auxiliary commands EXIT SAVE PERMFILE PROMPT QUIT SAVE PERMFILE PROMPT STOP SAVE PERMFILE PROMPT EXIT, QUIT and STOP are equivalent to END. PARAMETER Sec. 3.6 Auxiliary commands ADINA R & D, Inc. 3-27 PARAMETER NAME EXPRESSION Defines a parameter that can be substituted in a later command. The AUI evaluates the given expression and stores the resulting number as the value of the parameter. Note: Parameter definitions and values are not stored in the database. NAME The name of the parameter (1 to 30 alphanumeric characters). The name is not case sensitive. If the parameter is not already defined, a new parameter is created, otherwise the existing parameter is modified. EXPRESSION A string (up to 256 characters long) that contains a numeric expression. The expression string can contain the following items: The arithmetic operators +, -, *, /, ** (exponentiation) Numbers (either real numbers or integers) The following functions: ABS(x) absolute value AINT(x) truncation ANINT(x) nearest whole number ACOS(x) arccosine ASIN(x) arcsine ATAN(x) arctangent ATAN2(x,y) arctangent(x/y) COS(x) cosine COSH(x) hyperbolic cosine DIM(x,y) positive difference EXP(x) exponential LOG(x) natural logarithm LOG10(x) common logarithm MAX(x,y,...) largest value MIN(x,y,...) smallest value MOD(x,y) remaindering SIGN(x,y) transfer of sign SIN(x) sine SINH(x) hyperbolic sine SQRT(x) square root STEP(x) the unit step function: 0.0 if x <= 0.0 1.0 if x > 0.0 TAN(x) tangent TANH(x) hyperbolic tangent Chap 3 Input/Output PARAMETER 3-28 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition All trigonometric functions operate on or return angles in radians. Examples PARAMETER A '3.0' // A = 3 PARAMETER B '5 + 7' // B = 12 PARAMETER C '6 * \ // The string can be entered on several 5 ' // command lines as in this example; C = 30 Parameter substitution When the command-line parser finds a token value that starts with a $, the parser finds the parameter name with that token value and substitutes the parameter value. For example, in the commands PARAMETER X1 '2.0/3.0' PARAMETER X2 'SQRT(5.0)' PARAMETER X3 'SIN(2.0)' BODY BLOCK DX1=$X1 DX2=$X2 DX3=$X3 the parser looks for the values of X1, X2 and X3 and substitutes the values (e.g. the characters '0.666666666666667') for the names (e.g. the characters 'X1'). Hence the above commands are exactly equivalent to the command BODY BLOCK DX1=0.666666666666667 DX2=2.23606797749979, DX3=0.909297426825682 The token values need not be in upper-case: BODY BLOCK DX1=$x1 DX2=$x2 DX3=$x3 Parameter substitution occurs before command execution, so the following is allowed: PARAMETER A '2.0' PARAMETER A '$A + 1' // A = 3 Now you may want to put the symbol $ into a string without parameter substitution occuring. The rule is: if the next character after the $ is a letter [a-z], the command-line parser attempts parameter substitution. So PARAMETER A '3.0' USERTEXT ABC 'The cost is $2000.00' 'The size is $A' DATAEND PARAMETER Sec. 3.6 Auxiliary commands ADINA R & D, Inc. 3-29 is equivalent to USERTEXT ABC 'The cost is $2000.00' 'The size is 3' DATAEND A convenient way to output the value of a single parameter is with the ECHO command: PARAMETER X1 '2.0/3.0' ECHO $X1 ECHO 'The value of X1 is $X1' Auxiliary commands LIST PARAMETER Lists the values of all parameters. ECHO STRING Outputs the given string. This command can be used to output the value of a parameter, see the examples given in the PARAMETER command description. STRING is a string (up to 256 characters long). Chap 3 Input/Output REBUILD-MODEL 3-30 AUI Command Reference Manual: Vol. III − ADINA CFD Model Definition REBUILD-MODEL Forces the AUI to rebuild the whole model. Chapter 4 Interface control and editing ADINA R & D, Inc. 4-3 Sec. 4.1 Settings CONTROL PLOTUNIT VERBOSE ERRORLIMIT LOGLIMIT UNDO PROMPT AUTOREPAINT DRAWMATTACH DRAWTEXT DRAWLINES DRAWFILLS AUTOMREBUILD ZONECOPY SWEEPCOINCIDE SESSIONSTORAGE DYNAMICTRANSFORM UPDATETHICKNESS AUTOREGENERATE ERRORACTION FILEVERISON CONTROL defines certain parameters that control program behavior. The parameters defined by the CONTROL command are stored in the database. PLOTUNIT <not currently active> [PERCENT] VERBOSE <not currently active> [YES] ERRORLIMIT <not currently active> [0] LOGLIMIT <not currently active> [0] UNDO [5] The UNDO parameter controls the number of commands that can be undone using the UNDO command. If UNDO = 0, the UNDO command cannot be used, if UNDO = 1, UNDO can be used to undo the effects of the previous command, if UNDO = 2, UNDO can be used to undo the effects of the previous two commands, etc. Setting UNDO = 0 can significantly speed up the processing of batch files. PROMPT [UNKNOWN] Controls the default behavior for prompts which may arise from various commands. NO No command prompts will be issued - this is useful in batch mode - eliminating any interaction. YES Command prompts are always issued. UNKNOWN Command prompts are issued only when necessary. AUTOREPAINT [YES] When AUTOREPAINT = YES, the AUI automatically repaints that area of the graphics window that is exposed to the removal or motion of overlapping windows or dialogs. You may want to set AUTOREPAINT to NO to suppress the repainting; in that case, you can use the REFRESH command whenever you want to repaint the graphics window. DRAWMATTACH [YES] When DRAWMATTACH = YES, mesh plot attachments (band plots, load plots, element vector plots, reaction plots, line contour plots) are drawn. Otherwise, they are not drawn. CONTROL 4-4 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 4 Interface control and editing One use of this option would be to turn off drawing of mesh plot attachments before moving the mesh plots with the mouse. DRAWTEXT [EXACT] DRAWLINES [EXACT] DRAWFILLS [EXACT] These options control the drawing of text, lines and fills: EXACT Use the requested colors while drawing. SATURATED Convert all colors to saturated colors before drawing. GRAY Convert all colors to gray scales before drawing. INVERSE Convert all colors to the INVERSE color before drawing (the INVERSE color is the opposite of the background color). NO Do not draw. AUTOMREBUILD [YES] When you enter a command that alters the geometry or finite element model, the AUI rebuilds all corresponding data structures so that the model can be re-plotted. This feature can be deactivated by setting AUTOMREBUILD = NO (in this case, if you want to plot the model, you must use the ADINA, ADINA-T or ADINA-F commands to rebuild the model before- hand). Setting AUTOMREBUILD = NO can significantly speed up the processing of batch files. Notes : 1) One important use of parameters DRAWTEXT, DRAWLINES, DRAWFILLS is when making plots in black and white for reports. In this case you might use DRAWTEXT = INVERSE, DRAWLINES = INVERSE, DRAWFILLS = GRAY. 2) The drawing parameters apply both to graphics as displayed on the screen and to graphics as produced using SNAPSHOT or MOVIESAVE. 3) One use of DRAWFILLS = SATURATED is to speed up shaded color image drawing, especially using X Window graphics; all shades of each color are converted to the same color, resulting in significantly fewer color changes. ZONECOPY [NO] Controls whether the commands BANDPLOT, MESHPLOT, ELINEPLOT, EVECTORPLOT, LCPLOT, REACTIONPLOT, BANDSTYLE, MESHSTYLE, ELINESTYLE, EVECTORSTYLE, LCSTYLE, REACTIONSTYLE create copies of the input zones. Zone copies are always created by these commands in AUI 7.0 but not in later versions of the AUI. The preferred CONTROL ADINA R & D, Inc. 4-5 Sec. 4.1 Settings CONTROL setting of ZONECOPY is NO, but YES may be necessary to read input/session files produced for/by AUI 7.0. {YES/NO} SWEEPCOINCIDE [YES] Controls whether the SURFACE/VOLUME REVOLVED/EXTRUDED geometry definition commands check for coincident lines and surfaces, as well as for coincident vertices (points). AUI 7.0 did not attempt to connect adjacent surfaces/volumes, resulting in duplicate lines and surfaces fro such sweep geometry definition. The default in AUI 7.1 and higher is to connect adjacent surfaces/volumes whenever possible. However, AUI 7.0 input/session files which contain such sweep geometry will likely fail, so it may well be necessary to set SWEEPCOINCIDE=NO to correctly process older input files. {YES/NO} SESSIONSTORAGE [YES] If SESSIONSTORAGE = YES, the subsequent commands are stored in the AUI database. You can output these commands using the command COMMANDFILE. In the event of a system crash, you can retrieve these commands by opening the AUI temporary database, and subsequently issuing the COMMANDFILE command. If SESSIONSTORAGE = NO, subsequent commands are not stored in the AUI database and therefore cannot be retrieved. You may wish to set SESSIONSTORAGE = NO before reading commands from a batch file to eliminate the overhead of storing those commands within the AUI database. Note that the storage of commands in the AUI database is independent of the writing of commands to the session file determined by command FILESESSION. DYNAMICTRANSFORM [YES] Controls how the program indicates the transformation when you move, resize or rotate graphics using the mouse. If DYNAMICTRANSFORM=YES, the program redraws all picked graphics completely and redraws all other graphics that overlap the picked graphics. If DYNAMICTRANSFORM=PARTIAL, the program partially redraws all picked graphics and does not redraw overlapping graphics. If DYNAMICTRANSFORM=NO, the program indicates the transformation using a bounding box. UPDATETHICKNESS [YES] When you change the thickness of geometry surfaces or faces, all elements generated onto the surfaces or faces are automatically updated with the updated thickness. {YES/NO} In AUI 7.2 and lower, elements are not automatically updated. Therefore you may need to set UPDATETHICKNESS=NO so that input files constructed for use with AUI 7.2 and lower work correctly. 4-6 AUI Command Reference Manual: Vol. III ADINA CFD Model Definition Chap. 4 Interface control and editing AUTOREGENERATE [NO] If AUTOREGENERATE=YES, the program regenerates the graphics after you run a command that changes the model definition. This parameter only applies to commands that are run from the command-line (or read from a file); it does not apply to dialog box input from the user interface. Note that the user interface always regenerates the graphics after you use a dialog box that changes the model definition. {YES/NO} ERRORACTION [CONTINUE] Defines AUI action when error is detected. Parameter affects only commands read from a batch file. CONTINUE AUI continues to process commands. SKIP AUI skips the remaining commands up to the next READ END command, if any. Note: For more details see AUI Command Reference Manual: Vol. IV - Display processing. FILEVERISON [V74] Flag to request algorithms from previous version of AUI. Note: For more details see AUI Command Reference Manual: Vol. IV - Display processing. Auxiliary commands LIST CONTROL Lists the values of the parameters set by the CONTROL command. CONTROL