Home

ASTROS User`s Reference Manual for Version 20.

1. BEGIN BULK GRIDLIST 1 5 10 15 20 25 DCONF 101 CASE1 CONST DCN1 DCN1 GLIST 1 CASEID 1 ULPT 2 ALLOW 20 0 DCONF 101 CASE2 CONST DCN1 DCN1 GLIST 1 CASEID 2 ULPT 2 ALLOW 20 0 DCONF 101 CASE3 CONST DCN1 DCN1 GLIST 1 CASEID 3 ULPT 2 ALLOW 20 0 DCONF 101 CASE4 CONST DCN1 DCN1 GLIST 1 CASEID 4 ULPT 2 ALLOW 20 0 DCONF 101 CASES CONST DCN1 DCN1 GLIST 1 CASEID 5 ULPT 2 ALLOW 20 0 ENDDATA Example 6 Invalid List Cardinality The following example demonstrates an invalid request for a set of grid point data recovered for a list of unique subcases The solution control packet references the functional design constraint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC STATICS DCFUNCTION 101 The Function Packet defines the function specification for computing the allowable displacements compo nent for T3 The general expression for the F unction packet is grid 5 recovered at subcase 1 grid 10 recovered at subcase 2 grid 15 recovered at subcase 3 grid 20 recovered at subcase 4 COMP 2 T3 for which is defined by the F unction packet ASTROS THE FUNCTION PACKET 6 21 USER S MANUAL FUNCTIONS Recover the Displacement component T3 time
2. 1 2 3 4 5 6 Y 8 9 10 DMIG NAME PREC FORM CONT CONT GCOL CCOL GROW CROW Xij Yij CONT CONT GCOL CCOL GROW CROW Xij Y CONT DMIG TEST RDP REC ABC BC 1001 4 2001 2 1 25 5 DEF EF 1001 4 3001 3 2 67 4 etc Field Contents NAME Any valid data base entity name Character PREC The precision of the matrix entity to be loaded Any one of the following character strings RSP RDP CSP Or CDP FORM The form of the matrix entity to be loaded Any one of the following REC SYM DIAG IDENT SQUARE TRIANG GCOL Grid scalar or extra point identification for column index Integer CCOL Component number for GCOL O lt CCOL lt 6 if GCOL is a grid point zero or blank for scalar or extra points Integer GROW Grid scalar or extra point identification for row index Integer CROW Component number for GROW O lt CROW lt 6 if GROW is a grid point zero or blank for scalar or extra points Integer Xij Yij Matrix term Xij is real part for real or complex matrices Yij is the imaginary part for complex matrices and is ignored for real matrices Real Remarks 1 If the named entity exists it will be flushed and reloaded If the entity does not exist it will be created 2 The number of rows and columns will be either p set size or g set size depending on whether the named entity is requested by K2PP M2PP B2PP Or K2GG M2GG etc
3. 1 2 3 4 5 6 7 8 10 DCONFRQ SID MODE CTYPE FRQALL DCONFRQ 3 1 LOWER 6 0 Field Contents SID Constraint set identification Integer gt 0 MODE Modal number of the frequency to be constrained Integer gt 0 CTYPE Constraint type either UPPER for upper bound or LOWER for lower bound Character Default LOWER FRQALL Frequency constraint in Hz Remarks 1 More than one constraint can be placed on a mode allowing specification of pseudo equality con straints 7 80 THE BULK DATA PACKET ASTROS USER S MANUAL DCONFT Input Data Entry DCONFT Fiber Transverse Strain Constraint Definition Description Defines fiber transverse strain constraints for composite elements by specifying the iden tification numbers of constrained elements Format and Example al 2 3 4 5 6 7 8 9 10 DCONFT SID EFT EFC ETT ETC ETYPE LAYRNUM EID1 CONT CONT EID2 EID3 etc DCONFT 100 Le 2 f 10 538 shed QUAD4 He 101 ABC BC 102 110 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONFT SID EFT EFC ETT ETC ETYPE LAYRNUM EID1 CONT CONT THRU EID2 Field Contents SID Strain constraint set identification Integer gt 0 EFT Tensile strain limit in the fiber direction Real gt 0 0 EFC C
4. NAMES TYPE DESCRIPTION OFPGRAD ENG Processes output requests for objective and constraint gradients OFPLOAD ENG Prints selected applied external loads from any analyses in the current boundary condition OFPMROOT ENG Processes output requests for normal modes OFPSPCF ENG Processes output requests for single point constraint forces PARTN MAT Partitions a matrix into two or more submatrices based on row and column partitioning vectors PBKLEVAL ENG Evaluates panal buckling constraints PBKLSENS ENG Evaluates panal buckling constraint sensitivity PFBULK ENG Performs a number of preface operations to form additional collections of data GHRTCEN ENG eet or O unsteady aerodynamic matrices for GusT analyses in the RBCHECK ENG Outputs tothe print file the rigid body checks computed for each support point RECEND CADDB Terminates setting conditions on a MAPOL relational access Recovers the symmetric or asymmetric f set displacements or accelerations if there are omitted RECOVA ENG degrees of freedom pore ENG ae the eigenvalues and eigenvectors of the system as directed by the boundary METHOD RELCND CADDB Sets conditions on attribute values for MAPOL retrieval of relational entities RELADD CADDB Addsatupletoan entity opened with RELUSE RELEND CADDB Closes an entity opened from the MAPOL sequence using RELUSE ARTET CADDB Pea a relational tuple into execution memory for a relation opened for usein the MAPOL
5. 1 2 3 4 5 6 af 8 9 10 PMASS PID M TMIN PID M TMIN PMASS 7 4 29 0 2 6 ES Ot Field Contents PID Property identification number Integer gt 0 M Value of scalar mass Real TMIN The minimum mass value in design Default 0 0001 Remarks 1 This entry defines a mass value 2 Upto2 mass values may be defined by this entry 3 TMIN is ignored unless the mass element is linked to design variables through SHAPE entries ASTROS THE BULK DATA PACKET 7 197 PQDMEM1 USER S MANUAL Input Data Entry PQDMEM1 Quadrilateral Membrane Property Description Used to define the properties of a quadrilateral membrane referenced by the CQDMEM1 entry No bending properties are included Format and Examples 1 2 3 4 5 6 7 8 9 10 PQDMEM1 PID MID T NSM TMIN PQDMEM1 235 2 0 5 0 0 Field Contents PID Property identification number Integer gt 0 MID Material identification number Integer gt 0 T Thickness of membrane Real gt 0 0 NSM Nonstructural mass per unit area Real gt 0 0 TMIN Minimum thickness for design Real gt 0 0 or blank Default 0 0001 Remarks 1 All PQDMEM1 entries must have unique property identification numbers 2 TMIN is ignored unless the element is linked to the global design variables by a SHAPE entry 7 198 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry PROD Rod Property
6. Description Defines airfoil properties for the static aerodynamic model Format and Example 1 2 3 4 5 6 7 8 9 10 AIRFOIL ACID CMPNT CP CHORD USO THK LSO CAM RADIUS CONT CONT Xi Y1 z1 X12 IPANEL AIRFOIL 1 WING 10 20 30 ABC BC 0 0 0 0 0 50 0 Field Contents ACID Associated aircraft component identification number referenced by a matching CAERO6 bulk data entry Integer gt 0 CMPNT Type of aircraft component Character selected from See Remark 3 WING FIN CANARD CP Coordinate system for airfoil Integer gt 0 or blank See Remark 4 CHORD Identification number of an AEFACT data entry containing a list of division points in terms of percent chord at which airfoil thickness and camber data are specified Integer gt 0 USO THK Identification number of an AEFACT data entry defining either the upper surface ordinates in percent chord if Lso is not blank or the half thicknesses about the camber ordinates if cam is not blank Integer gt 0 or blank See Remark 3 LSO Identification number of an AEFACT data entry defining the lower surface ordinates in percent chord Must be used in conjunction with uso Integer gt 0 or blank See Remark 3 CAM Identification number of an AEFACT data entry defining the mean line camber line ordinates in percent chord Integer See Remark 3 RADIUS Radius of leading edge in percent chord Real gt 0 0 X1 Y1 21 Location of the airfoil leadin
7. 1 2 3 4 5 6 7 8 9 10 BAROR PID X1 GO X2 X3 BAROR 39 0 6 2 9 5 87 Field Contents PID Identification number of PBAR property entry Integer gt 0 or blank Xi Vector components measured in displacement coordinate system at GA to determine with the vector from end A to end B the orientation of the element coordinate system for the bar element Real or blank GO Grid point identification number Integer gt 0 Remarks 1 The contents of fields on this entry are used for any CBAR entry whose corresponding fields are blank 2 Only one BAROR entry may appear in the Bulk Data Packet 7 26 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry BODY BODY Description Defines body configuration parameters for steady aeroelasticity Format and Example 1 2 3 4 5 6 7 8 9 10 BODY BCID CMPNT CP NRAD XLOC YLOC ZLOC BODY 10 FUSEL 0 3 Field Contents BCID Body component identification number Integer gt 0 CMPNT Component type FUSEL for the fuselage and Pop for a pod CP Coordinate system of the geometry input Integer gt 0 or blank NRAD Number of equal radial cuts used to define the body Integer gt 0 or blank XLOC YLOC Ordinates of the nose of the pod in the cP coordinate system Real ZLOC Remarks 1 NRAD is input if equally spaced radial cuts are desired Arbitrary radial cuts are specified using the AXSTA
8. Description Defines sets of single point constraints and enforced displacements Format and Examples E 2 3 4 5 6 7 8 9 10 SPC SID G Cc D G D SPC 2 32 436 25 3 6 5 259 Field Contents SID Identification number of single point constraint set Integer gt 0 G Grid or scalar point identification number Integer gt 0 Component number of global coordinate 6 gt Integer gt 0 up to 6 unique digits may be placed in the field with no embedded blanks D Value of enforced displacement for all coordinates designed by G and c Real Remarks 1 Degrees of freedom specified on this entry form members of a mutually exclusive set They may not be specified on other entries that define mutually exclusive sets 2 Single point forces of constraint are recovered during stress data recovery Single point constraint sets must be selected in Solution Control SPc SID to be used 4 spc degrees of freedom may be redundantly specified as permanent constraints on the GRID entry ASTROS THE BULK DATA PACKET 7 219 SPCADD USER S MANUAL Input Data Entry SPCADD Single Point Constraint Set Combination Description Defines a single point constraint set as a union of single point constraint sets defined via SPC Or SPC1 entries Format and Examples 1 2 3 4 5 6 7 8 9 10 SPCADD SID s1 S2 3 S4 S5 S6 S7 CONT CONT s8 s9 etc SPCADD 101 3 2 9
9. 1 2 3 4 5 6 7 8 9 10 MAT2 MID G11 G12 G13 G22 G23 G33 RHO CONT CONT Al A2 A12 TO GE ST SC ss CONT CONT MCSID MAT2 13 6 2 3 6 2 3 53143 0 056 ABC BC 6 5 6 6 5 6 500 0 0 002 20 5 Field Contents ID Material identification number Integer gt 0 Gij The material property matrix Real RHO Mass density Real gt 0 0 Ai Thermal expansion coefficient vector Real TO Thermal expansion reference temperature Real GE Structural element damping coefficient Real ST SC SS Stress limits for tension compression and shear Real Used to compute margins of safety in certain elements MCSID Material Coordinate System identification number Integer gt 0 or blank Remarks 1 Material identification numbers must be unique for all MAT1 MAT2 MAT8 and MAT9 bulk data entries 2 Themass density RHO will be used to automatically compute mass for all structural elements 3 Weight density may be entered in Field 9 if the value 1 g where g is the acceleration of gravity is entered on the CONVERT entry 4 The convention for the Gij in Fields 3 through 8 are represented by the matrix relationship 61 G11 Gy 613 1 Ay 0 G12 G22 G33 E p TT 4 2 Ti2 G13 G23 G33 Y Az 5 2x2 matrices for example transverse shear use elements G11 G12 and G22 For this case G33 must be blank 6 Ifthemar2 entry is referenced by the Pcomp entry the transverse shear flexibility for the referenced laminae is zero
10. Description Defines a multipoint constraint equation of the form Y Aj uj 0 0 j Format and Example 1 2 3 4 5 6 7 8 9 10 MPC SID G0 co AO CONT CONT G C A MPC 3 28 3 6 2 2 3 4 29 B B 1 4 25 91 Field Contents SID Set identification Integer gt 0 G0 G Identification number of grid or scalar point Integer gt 0 co C Component number any one of the digits 1 through 6 in the case of geometric grid points blank or zero in the case of scalar points Integer AO A Coefficient Real AO must be nonzero Remarks 1 The first coordinate GO CO in the sequence is assumed to be the dependent coordinate A dependent degree of freedom assigned by one Mpc entry cannot be assigned dependent by another mpc entry or by a rigid element 2 Forces of multipoint constraint are not recovered Multipoint constraint sets must be selected in Solution Control MPC SID to be used 4 The m set coordinates specified on this entry may not be specified on other entries that define mutually exclusive sets ASTROS THE BULK DATA PACKET 7 167 MPCADD USER S MANUAL Input Data Entry MPCADD Multipoint Constraint Set Combination Description Defines a multipoint constraint set as a union of multipoint constraint sets defined via MPC entries Format and Example 1 2 3 4 5 6 7 8 9 10 MPCADD SID s1 S2 S3 S4 S5 S6 S7 CONT CONT s8 s9 Hetc gt MPCADD 101
11. PRIORITY OPERATOR 1 Logical FUNCTION 2 NOT 3 AND 4 OR 5 XOR Any operation in a logical expression may be enclosed in parentheses the parenthetical expression is evaluated and the resulting value is used as an operand Thus parentheses may be used to alter the order in which operations are to be performed When parenthetical expressions are nested evaluation begins with the innermost set of parentheses and proceeds to the outermost set 9 3 3 RELATIONAL EXPRESSIONS A relational expression uses relational operators to compare two arithmetic expressions A relational expression produces a logical data type with a value of TRUE or FALSE Thus a relational expression may be an operand in a logical expression 9 3 3 1 Relational Operators Table 9 7 summarizes the relational operators available in MAPOL Table 9 7 Relational Operators in MAPOL OPERATOR DESCRIPTION Equality lt gt Inequality gt Greater than gt Greater than or equal to lt Less than lt Less than or equal to ASTROS MAPOL PROGRAMMING 9 15 USER S MANUAL 9 3 3 2 Relational Operands Relational operands must be of an arithmetic type integer or real A complex operand is permitted only when the relational operator is or lt gt 9 3 3 3 Evaluation of Relational Expressions In a relational expression involving the comparison of arithmetic operands each of t
12. 1 2 3 4 5 6 7 8 9 10 DCONFTM SID EFT EFC ETT ETC MID1 THRU MID2 Field Contents SID Strain constraint set identification Integer gt 0 EFT Tensile strain limit in the fiber direction Real gt 0 0 EFC Compressive strain limit in the fiber direction Real Default EFT ETT Tensile strain limit in the transverse direction Real gt 0 0 ETC Compressive strain limit in the transverse direction Real Default ETT IDi Material identification numbers Integer gt 0 Remarks 1 Strain constraints are selected in Solution Control with the discipline option STRAIN sid Fiber transverse strain constraints may only be applied to elements defined using composite materials 3 If the alternate form is used MID2 must be greater than or equal to MID1 Material properties in the range which do not exist are ignored 4 Thestrain limits for compression EFC and ETC are always treated as negative values regardless of the signs of the input values 7 82 THE BULK DATA PACKET ASTROS USER S MANUAL DCONFTP Input Data Entry DCONFTP Fiber Transverse Strain Constraint Definition Description Defines fiber transverse strain constraints for composite elements by specifying property identification numbers Format and Example 1 2 3 4 5 6 7 8 9 10
13. 1 2 3 4 5 6 7 8 9 10 DCONVMP SID ST sc Ss PTYPE LAYRNUM PID1 THRU CONT CONT PID2 Field Contents SID Stress constraint set identification Integer gt 0 ST Tensile stress limit Real gt 0 0 or blank SC Compressive stress limit Real Default sT SS Shear stress limit Real gt 0 0 or blank PTYPE Property type Character selected from PBAR PROD PSHEAR PQDMEM1 PTRMEM PSHELL PCOMP PCOMP1 PCOMP 2 LAYRNUM The layer number of a composite element Integer gt 0 or blank PIDi Property identification numbers Integer gt 0 Remarks 1 Stress constraints are selected in Solution Control with the discipline option STRESS sid 2 If the alternate form is used PID2 must be greater than or equal to PID1 Properties in the range which do not exist are ignored 3 The stress limit for compression sc is always treated as a negative value regardless of the sign of the input value 4 LAYRNUM is only used if the element is composed of a composite material defined with Pcomp Bulk Data entries ASTROS THE BULK DATA PACKET 7 103 DENSLIST USER S MANUAL Input Data Entry DENSLIST Description Defines a list of density ratio values Format and Example 1 2 3 4 5 6 7 8 9 10 DENSLIST SID DENS1 DENS2 DENS3 DENS4 DENS5 DENS6 DENS7 CONT CONT DENS8 DENS9 etc DENSLIST 201 1 0 0 5 0 7 Field Contents
14. BOUNDARY E E 20 AUTOSPC NO METHOD 100 BOUNDARY STIFF M2GG MASS BOUNDARY ED 2 INER 4 Note that all desired specifications are listed and that their order of appearance is not important At least one option is required Several boundary conditions may appear within a given subpacket F or example ANALYZE BOUNDARY SPC 10 STATICS MECH 5 BOUNDARY SPC 20 REDUCE ETHOD 1111 STATICS THERM 10 In this case a STATICS analysis is performed using the first boundary condition followed by a STATICS and modes analysis for the second boundary condition Note that unlike NASTRAN the sets of points to be retained in the Guyan reduction and used for the support definition are selected The appearance of a BOUNDARY command leads to expensive matrix partitioning and decomposition operations Therefore some thought should be expended to avoid unnecessary computer resource use F or example suppose an ASTROS execution was directed to perform static analyses with two boundaries SPC 10 and sPc 20 and a dynamic analysis with two boundaries SPc 10 and spc 100 The direct solution sequence could be 5 6 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL ANALYZE BOUNDARY SPC 10 STATICS MECH 10 BOUNDARY SPC 20 STATICS MECH 20 BOUNDARY SPC 10 M MODES BOUNDARY SPC 100 METHOD 40 MODES This sequence woul
15. USER S MANUAL RBE1 Input Data Entry RBE1 Rigid Body Element Form 1 Description Defines a rigid body connected to an arbitrary number of grid points Format and Example 1 2 3 4 5 6 7 8 9 10 RBE1 SETID EID GN1 CN1 GN2 CN2 GN3 CN3 CONT CONT GN4 CN4 GN5 CN5 GN6 CN6 CONT CONT ym GM1 CM1 GM2 CM2 GM3 CM3 CONT CONT GM4 CM4 GM5 CM5 etc RBE1 1001 11 1 2 2 134 3 5 ABC BC 4 2 DEF EF UM 1 13 2 1 12 5 Field Contents SETID Multipoint constraint set identification number specified in Solution Control Integer gt 0 EID Rigid body element identification number Integer gt 0 GNi Grid point identification numbers at which independent degrees of freedom are as signed Integer gt 0 CNi Component numbers of independent degrees of freedom in the global coordinate sys tem at grid points GNi indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 Remark 2 UM Character string indicating the start of the list of dependent degrees of freedom GMj Grid point identification numbers at which dependent degrees of freedom are as signed Integer gt 0 CMj Component numbers of dependent degrees of freedom in the global coordinate system at grid points EM3 indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 Remark 2 Remarks 1 The RBE1 entry is selected in the Solution Control with the MPC SETID option of the BOUNDARY command THIS IS AN ENHANCEMENT TO THE NA
16. Input Data Entry CMASS2 Scalar Mass Property and Connection Description Defines a scalar mass element of the structural model without reference to a property entry Format and Example 1 2 3 4 5 6 7 8 9 10 CMASS2 EID M G1 C1 G2 C2 TMIN TMAX CMASS2 32 9 25 6 1 Field Contents EID Element identification number Integer gt 0 The value of the scalar mass Real Gi Geometric grid point identification number Integer gt 0 i Component number 6 gt Integer gt 0 TMIN TMAX The minimum and maximum mass values in design Real Remarks 1 Scalar points may be used for G1 and or G2 in which case the corresponding C1 and or c2 must be zero or blank Zero or blank may be used to indicate a grounded terminal G1 or G2 with a correspond ing blank or zero C1 or C2 A grounded terminal is a point whose displacement is constrained to zero 2 This single entry completely defines the element since no material or geometric properties are required 3 The two connection points G1 C1 and G2 C2 must be distinct Except in unusual circumstances one of them will be a grounded terminal with blank entries for G and C 4 The TMIN and TMAX values are used only for shape function design variable linking 7 42 THE BULK DATA PACKET ASTROS USER S MANUAL CONEFFF Input Data Entry CONEFFF Flutter aerodynamic control effectiveness data Des
17. EBASE eb_mem PHYSICAL phys_mem work _mem Specifies the dynamic working memory size used by ASTROS modules The working memory may be increased for large problems to reduce the amount of physical I O Note however that this may cause increased paging Contact your ASTROS Support Specialist for additional details eb_mem Specifies the eBASE database memory size This memory is a separate memory pool used by the database during execution Normally the default value in the Preference File is sufficient but if you use block sizes larger than the default for any database this value may need to be increased phys_mem Specifies the real physical memory memory size The physical memory is used to control certain advanced algorithms Contact your ASTROS Support Specialist for additional details The units of the memory size are determined by the two optional command arguments The first argument indicates an order of magnitude for memory_space M for millions K for thousands The second argument indicates the unit specifier as single precision words w bytes B or computer precision words P If neither is present then memory_space is taken to be single precision computer words The working memory for ASTROS is dynamically acquired during execution The amount of memory used is determined in order of precedence by the MEMORY Resource command the m option of the astros script and the configuration parameter working_
18. STATICS MECH 10 In this case bulk data applied load entries with a set ID of 10 are used to construct a mechanical load vector in a STATICS analysis n general the discipline commands have the form lt disc gt lt type gt lt caseid gt lt option gt lt n gt lt option gt lt n gt The discipline options that are available are OPTION DESCRIPTION MECHANICAL GRAVITY Specify load set I Ds for the STATIC discipline THERMAL Specifies a TRIM bulk data entry which gives flight condition TRIM f i ERA information for the SAERO discipline DCON Specifies the set IDs of constraint bulk data entries that apply for the DCONSTRAINT given discipline DCFUNCTION Specifies the set ID of a DCFUNC Bulk Data entry STRESS Specifies the set IDs of stress constraint bulk data entries that apply STRESSCONSTRAINT for the given STATICS or SAERO discipline STRAIN Specifies the set IDs of strain constraint bulk data entries that apply STRAINCONSTRAINT for the given STATICS or SAERO discipline DLOAD Specifies applied loads for the TRANSIENT and FREQUENCY disciplines Specifies the time step for the TRANSIENT discipline as well as for the TSTEP l A discrete form of the Gust discipline Satan Specifies the frequencies for the FREQUENCY and the harmonic form of the Gust discipline j Specifies the initial conditions that are to be used in the direct method for the TRANSIENT
19. o e e 8 7 Table 8 9 ASTROS Aerodynamic and Structural Elements 8 10 Table 8 10 BAR Element Output Quantities 0 8 12 Table 8 11 IHEX1 Element Solution Quantities o 8 14 Table 8 12 ROD Element Solution Quantities 0 8 18 Table 8 13 QDMEM1 Solution Quantities o o 8 20 Table 8 14 QUAD4 and TRIA3 Solution Quantities 8 21 Table 8 15 SHEAR Solution Quantities o 8 23 Table 8 16 Displacement Vector 8 24 Table 8 17 Complex Displacement Vector 0 0 8 24 Table 8 18 Design Variable Values o 8 27 Table 8 19 Design Constraint Summary e 8 27 Table 8 20 Flutter Solution Results 2 o 2 8 29 Table 8 21 Modal Participation Factors 0 8 30 xii ASTROS USER S MANUAL Table 8 22 Real Eigenanalysis Results 2 20 4 8 30 Table 8 23 Symmetric Trim Results 0 000000 8 32 Table 8 24 Antisymmetric Trim Results 0 e e 8 34 Table 8 25 Summary of Output Quantities o o 8 35 Table 9 1 MAPOL Command Options o e e e 9 2 Table 9 2 Summary of MAPOL User Options o o
20. e 9 4 Table 9 3 MAPOL Arithmetic Operators 0 9 11 Table 9 4 MAPOL Operation Rules o e 9 13 Table 9 5 MAPOL Logical Operators 0 e 9 13 Table 9 6 Evaluation of MAPOL Logical Expressions 9 14 Table 9 7 Relational Operators in MAPOL o 9 15 Table 9 8 Matrix Operators in MAPOL 0 o e eee 9 16 Table 9 9 Assignment Rules in MAPOL o 9 18 Table 9 10 Intrinsic Mathematical Functions in MAPOL 9 29 Table 9 11 Intrinsic Relational Procedures in MAPOL 9 30 ASTROS xiii USER S MANUAL This pageis intentionally blank xiv ASTROS USER S MANUAL Chapter 1 INTRODUCTION There are five manuals documenting ASTROS the Automated Structural Optimization System e The User s Reference Manual e The Theoretical Manual e TheProgrammer s Manual e TheASTROS eBASE Schemata Definition e Thelnstallation and System Support M anual This User s Manual provides a complete description of the user interface to the ASTROS system in order to facilitate the preparation of input data It introduces the features of the ASTROS system that enable the user to direct the software system and documents the mechanisms by which the user can communi cate with the system It is assumed that the reader is familiar from a study of the Theoreti
21. Format and Example 1 2 3 4 5 6 zi 8 9 10 DLONLY SID A P A DLONLY 3 2 15 10 Field Contents SID Identification number of DLONLY set Integer gt 0 P Grid extra point or scalar point identification number Integer gt 0 C Component number 1 through 6 for grid point blank or O for extra points or scalar points A Load factor A for the designated coordinate Real Remarks 1 One or two load factors may be defined on a single entry Refer to RLOAD1 RLOAD2 TLOAD1 or TLOAD2 entries for the formulas which define the load factor A Component numbers refer to global coordinates The stp field is referred to as the DLAGS entry uF WN The scale factor A applied to any grid component will be the sum of all Ai for that degree of freedom on all DLONLY entries with the same SID ASTROS THE BULK DATA PACKET 7 111 DMI USER S MANUAL Input Data Entry DMI Direct Matrix Input Description Used to input matrix data base entities directly Generates a real or complex matrix of theform Au Ai2 Ain A A21 A22 A2n Ant Am2 Amn where the elements Aij may be real or complex Format and Example 1 2 3 4 5 6 7 8 9 10 DMI NAME PREC FORM M N CONT CONT Cl R1 A R1 C1 C2 R2 A R1 C2 A RI L C2 C3 CONT CONT R1 A R1 C3 C4 R2 A R2 C4 DMI TEST RDP REC 3 4 A
22. STRAIN DLOAD TSTEP FSTEP O IC FFT O DIRECT O MODAL O FLCOND GUST K2PP M2PP B2PP TFL O 0 JO JO JO JO IO IO O 0 0 O JO IO JO O O JO JO JO O JO DAMPING SYMMETRIC O ANTISYMMETRIC O Notes Required Commands o Optional Commands O ASTROS THE SOLUTION CONTROL PACKET 5 11 USER S MANUAL 5 3 2 STATICS Discipline Options One or more of the MECHANICAL GRAVITY Or THERMAL load specifications must be called out as a discipline option for STATICS Each STATICS discipline constitutes one subcase one load vector so specifying a combination of load types will generate a linear combination of the selected loads A refer ence to the LOAD bulk data entry as a MECHANICAL load can also be used to obtain linear load combina tions If the STATICS discipline appears in the OPTIMIZE subpacket the DCONSTRAINT option can be used to refer to DCONDSP bulk data entries to apply displacement constraints Stress constraints defined ON DCONTW DCONTWM DCONTWP DCONVM DCONVMM DCONVMP are selected by the STRESSCONSTRAINT option Strain constraints defined on DCONFT DCONFTM DCONFTP DCONEP DCONEPM and DCONEPP are selected by the STRAINCONSTRAINT option All DCONxxx bulk data entries such as DCONTHK that do not have SETID fields will be applied to the model in combination with set selectable constraints to
23. gid Identification of a grid specified in the Bulk Data Packet grid_sid Set identification of a GRIDLIST bulk data entry used to specify the grid Xi Component for the geometric coordinate cid Identification of a coordinate system specified in the Bulk Data Packet Notes 1 If the cid reference is omitted then the coordinate value is returned in the input coordinate system of the GRID point 2 A cid of 0 requests that the coordinate be returned in the basic coordinate system 3 The interpretation of x1 X2 and x3 depends on whether the cid coordinate system is rectangular cylindrical or spherical 6 28 THE FUNCTION PACKET USER S MANUAL USER S MANUAL DISP Intrinsic Function DISP Purpose Toretrieve the current value of a displacement Usage DISP gid caseid GRIDLIST grid_sid CASELIST case_sid Function Arguments gid Identification of a grid point specified in the Bulk Data Packet grid_sid Set identification of a GRIDLIST bulk data entry used to specify the grid Ti Ri Displacement component to recover cid Identification of a coordinate system specified in the Bulk Data Packet caseid Identification of a subcase case_sid Set identification of a CASELIST bulk data entry used to specify the subcase identification number Notes 1 If the subcase reference is omitted then the specific discipline request defines the requested subcase 2 Iftheciareferenceis omitted then the coordinat
24. DOF Component number One of the integers 1 6 Required only if NORM POINT and GID is a geometric grid point Remarks 1 The real eigenvalue extraction method set must be selected in Solution Control METHOD SID to be used 2 Both the GIv and MGIV methods are full spectrum tridiagonalization procedures which compute all eigenvalues and a range of eigenvectors selected by the user The GIv method requires that the a set 7 120 THE BULK DATA PACKET ASTROS USER S MANUAL EIGR GIVENS and Modified GIVENS mass matrix be positive definite The MGIv method uses an additional transformation to remove this requirement 3 IfMETHOD is GIV the mass matrix for the analysis set must be positive definite This means that all degrees of freedom including rotations must have mass properties 4 The number of eigenvalues which are computed depend on the values of FL FU and NVEC The following table summarizes the options FL FU NVEC Mode Shapes Computed Blank Blank Blank The lowest mode only Blank Blank n_val The first n_val modes Blank hi_val Blank All modes between and hi_val Blank koyal aval Sre modes in the range and low_val Blank Blank First mode above low_val low_val Blank n_val First n_val modes above low_val low_val hi_val Blank All modes between low_val and hi_val vall Rival en First n_val modes between low_val and hi_val If you are extracting rigid body mode
25. Format and Example T 2 3 4 5 6 7 8 9 10 CONM2 EID G CID M X1 X2 X3 CONT CONT I11 121 122 131 132 133 TMIN TMAX CONM2 2 15 6 49 7 123 23 16 2 16 2 7 8 Field Contents EID Element identification number Integer gt 0 G Grid point identification number Integer gt 0 CID Coordinate system identification number Integer gt 1 A CID of 1 integer allows the user to input xi as the center of gravity location in the basic coordinate system A CID of 0 implies the basic coordinate system M Mass value Real Xi Offset distances from the grid point to the center of gravity of the mass in the coordinate system defined in Field 4 unless CID 1 in which case Xi are the coordinates of the center of gravity of the mass in the basic coordinate system Real TiS Mass moments of inertia measured at the mass c g in coordinate system defined by Field 4 Real If cID 1 the basic coordinate system is implied TMIN TMAX The minimum and maximum mass values for design Real Remarks 1 The continuation entry may be omitted 2 If CID 1 offsets are internally computed as the difference between the grid point location and Xi The grid point locations may be defined in a nonbasic coordinate system In this case the values of lij must be in a coordinate system that parallels the basic coordinate system ASTROS THE BULK DATA PACKET 7 47 CONM2 USER S MANUAL 3 Theform of the inertia matrix about its cg is taken as M
26. Lift a ETS a c ic s fori 1 Novy o a q 2V 3 Pitching Moment qSc Sm Cy a Cm Cy 5 fori 1 Meyi where q Dynamic Pressure S Reference Area c Reference Chord V Reference Velocity Noy The number of symmetric control surfaces These definitions are the standard forms used in aircraft stability and control see Reference 5 Each of these three quantities drag lift and pitching moment coefficients is shown in up to three forms Table 8 23 ASTROS OUTPUT FEATURES 8 31 USER S MANUAL Table 8 23 Symmetric Trim Results 1SIMPLIFIED WING STRUCTURE DESIGN ASTROS VERSION 9 0 03 03 93 Py 9 STRESS DISP LIFT AND AILERON EFFECTIVENESS CONSTRAINTS ASTROS ITERATION 1 SYMMETRIC CONDITION NONDIMENSIONAL LONGITUDINAL STABILITY DERIVATIVES COMPUTED AT THE AERODYNAMIC REFERENCE GRID AND INCLUDING ANY CONTROL EFFECTIVENESS TRIM IDENTIFICATION 100 REFERENCE GRID 20 REFERENCE AREA 2 4000E 03 REFERENCE CHORD 2 0000E 01 lt lt lt DRAG gt gt gt lt lt lt LIFT gt gt gt lt lt lt PITCHING MOMENT gt gt gt RIGID RIGID FLEXIBLE RIGID RIGID FLEXIBLE RIGID RIGID FLEXIBLE PARAMETER LABEL DIRECT SPLINED DIRECT SPLINED DIRECT SPLINED THICKNESS CAMBER THKCAM 0012 N A N A 0099 0099 0173 0057 0057 0069 ANGLE OF ATTACK ALPHA 1 DEG 0010 N A N A 1173 1173 1928 0062 0062 0080 ANGLE OF ATTACK ALPHA 1 RAD 0582 N A N A 6 7223 6 7223 11 0489 3992 3552 4573 PITCH RAT
27. PROD Description Defines the properties of a rod which is referenced by the CROD entry Format and Examples ol 2 3 4 5 6 7 8 10 PROD PID MID A J E NSM TMIN PROD Ed 23 42 17 92 4 236 0 5 Field Contents PID Property identification number Integer gt 0 ID Material identification number Integer gt 0 A Area of rod Real gt 0 0 or blank J Torsional constant Real gt 0 0 or blank C Coefficient to determine torsional stress Real gt 0 0 or blank NSM Nonstructural mass per unit length Real gt 0 0 or blank TMIN Minimum rod area for design Real gt 0 0 or blank Default 0 0001 Remarks 1 PROD entries must all have unique property identification numbers 2 For structural problems PROD entries may only reference MAT1 material entries 3 Theformula used to compute torsional stress is where M is the torsional moment 4 TMIN is ignored unless the rod element is linked to the design variables by SHAPE entries ASTROS THE BULK DATA PACKET 7 199 PSHEAR USER S MANUAL Input Data Entry PSHEAR Shear Panel Property Description Defines the elastic properties of a shear panel Referenced by the CSHEAR entry Format and Examples 1 2 3 4 5 6 7 8 9 10 PSHEAR PID MID T NSM TMIN PSHEAR 13 2 4 9 16 2 Field Contents PID Property identification number Integer gt 0 MID Material id
28. S MANUAL Notes 1 When an element identification is used then the eid must be unique and if the eidis not unique then an element list must be used The allowable response components for each element type are shown in Table 20 Composite elements must have their layer identification number specified Stress components will always be recovered at the center of thelayer for composite elements uF WN The specific discipline request defines whether the case and or mode is a valid request in the response functions The mode sequence number is used only if the discipline is MODES If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 46 THE FUNCTION PACKET USER S MANUAL USER S MANUAL THICK Intrinsic Function THICK Purpose Toreturn the thickness of the requested two dimensional elements Usage THICK l eid plyid ELEMLIST elem_sid PLYLIST ply_sid Function Arguments eid Identification of an element specified in the Bulk Data Packet elem_sid Set identification of an ELEMLIST bulk data entry used to specify an element plyid Identification of a layer number for a composite element ply_sid Set identification of a PLYLIST bulk data entry used to specify the layer number for a composite element Notes 1 When an element identification is used then the eid must be unique and if the eidis not unique then an element list must be used 2 C
29. S MANUAL USER S MANUAL var_name argi expression Where variable names var_name may be any string of one to eight alphanumeric characters starting with a letter Arguments argi may also be passed to the function and used in the expression These arguments must be referenced in the expression and on the design constraint Bulk Data entry DCONF Expressions combine arguments constants and other functions They may be continued over multiple lines as long as the final line ends with a semicolon character All of the rules for arithmetic expression evaluation follow the standard rules of FORTRAN Note that unlike FORTRAN arguments which are not used may be omitted from the calling list as is the case with the MAPOL language Examples of this will be shown in later Subsections The following example defines a function which computes the allowable value of the stress resultant for an element FUNCTIONS SIG eid allow SORT STRESS eid SIGX 2 STRESS eid SIGY 2 allow 1 0 ENDFUNC In this example the function name is SIG which has two arguments the element identification number eid and the allowable stress allow It also references one intrinsic response function STRESS and one mathematical intrinsic SQRT Specifically intrinsic functions are built in functions which retrieve either standard mathematical functions such as sine and cosine or they are the functions which recover the
30. actual printing of the data occurs Table 8 25 Summary of Output Quantities QUANTITY IF PRINT IS REQUESTED IF PUNCH IS REQUESTED ACCEL PRINT File Relation OGRDDISP AIRDISP Relation OAGRDDSP Relation OAGRDDSP BUCK PRINT File Relations OPNLBUCK OEULBUCK CGRAD Relation GRADIENT Relation GRADIENT DCON PRINT File Relation CONST DISP PRINT File Relation OGRIDDSP ENERGY PRINT File Relation EOxxxx FORCE PRINT File Relation EOxxxx GDESIGN PRINT File Relation GLBDES GPFORCE Relation GPFDATA Relation GPFDATA GPWG PRINT File Relation OGPWG KSNS Unstructured DKVI Unstructured DKVI LDESIGN PRINT File Relation OLOCALDV LOAD Relation OGRIDLOD Relation OGRIDLOD MASS Matrix MGG Matrix MGG MODEL PUNCH File MSNS Unstructured DMVI Unstructured DMVI OGRADIENT Relation GRADIENT Relation GRADIENT QHH Matrix QHHL QHHLFL Matrix QHHL QHHLFL QHI Matrix QHJL Matrix QHJL ROOT PRINT File Relations LAMBDA CLAMBDA SPCF Relation OGRIDLOD Relation OGRIDLOD STIFFNESS Matrix KGG Matrix KGG STRAIN PRINT File Relation EOxxxx STRESS PRINT File Relation EOxxxx TPRESSURE PRINT File Relation OAGRDLOD VELOCITY PRINT File Relation OGRIDDSP TRIM PRINT File 1 xxxx represents an element name BAR ELAS HEX1 HEX2 HEX3 QDMM1 QUAD4 ROD SHEAR TRIA3 or TRMEM ASTROS OUTPUT FEATURES 8 35 USER S MANUAL 8 4 OTHER SELECTABLE QUANTITIES The DEBUG
31. ajjdc The Amp option controls the output of several intermediate matrices or of individual matrices from the matrix lists QKKL QKJL and QJJL that are formed in AMP for FLUTTER and GUST analyses respectively The user is referred to the Programmer s Manual for complete documentation of these data base entities The following matrices are output 8 36 OUTPUT FEATURES ASTROS USER S MANUAL IF PRIN AND AND THEN IS The SKJ matrix The above and the matrix X representing the solution to the equation AJ J 1 IX DY K ik D2J K If flutter entries arein 1 If there is only one the bulk data packet aerodynamic group If gust entries arein the The above and the matrix QK from the bulk data packet corresponding matrix list If flutter entries arein The above and the matrices D1 K and the bulk data packet D2 K gt 1 The above and the matrix AJ J T after extraction from the corresponding matrix list The optional matrix AJJDC is used to store the intermediate matrix x described in the options shown above If AJIJDC is blank a scratch data base entity is used to store x In either case X may be printed through the Amp option Only the last x matrix calculated will be returned to the executive sequence in AJJDC for use in additional processing 8 4 3 Flutter Root Iteration Output The flutter analysis module FLUTTRAN has an optional DEBUG
32. lt expl gt TO lt exp2 gt BY lt exp3 gt DO ENDDO The loop counter var is called the control variable and may be any integer or real variable lt exp1 gt lt exp2 gt and lt exp3 gt are called the initial terminal and incremental parameters respectively Note the incrementation clause BY lt exp3 gt is optional as in the example If it does not appear the increment is taken to be one Each loop terminates with the instruction ENDDO The following rules must be noted 1 If lt exp1 gt gt lt exp2 gt then the body of the loop will still be executed once 2 The type of the control variable and the three expressions must be the same 3 The control variable may not be redefined inside of the the loop 9 4 3 2 The WHILE DO Loop Another way to execute a group of statements repeatedly is with a WHILE loop This type of loop is used to repeat groups of statements that typically modify a more complex condition than the simpler incre mentation of the FOR loop As an example suppose it is desired to compute the cube root of a number X If a is an approximation to the answer then 2 2a Soy a is an improved guess The program shown below will compute the cube root of 10 to 3 significant figures 9 20 MAPOL PROGRAMMING ASTROS USER S MANUAL MAPOL REAL X OLD NEW TEMP EPS X 10 OLD 2 0 TH INITIAL GU EPS 0 001 THE CONVERGENCE WHILE ABS
33. B ASTROS MAPOL PROGRAMMING 9 29 USER S MANUAL Table 9 11 Intrinsic Relational Procedures in MAPOL PROCEDURE DESCRIPTION AND CALLING SEQUENCE RECEND Toend the definition of relational conditions A maximum of 10 may be applied per relation CALL RECEND lt rel var gt To define relational conditions CALL RELCND lt rel var gt lt attr gt lt relop gt lt value gt RELCND lt attr gt is an attribute named in quotation marks lt relop gt is one of GT NETES TEQ NE GE TE lt value gt is the conditional value A maximum of 10 may be applied per relation To add a tuple to a relation RELADD CALL RELADD lt rel var gt To dose a relation RELEND CALL RELEND lt rel var gt Toretrieve a tuple form an open relation BELGE CALL RELGET lt rel var gt lt status gt lt status gt is an integer variable that is non zero if an error occurred To update the fields in an existing tuple RELUPD CALL RELUPD lt rel var gt To open a relation CALL RELUSE lt rel var gt lt ntuple gt lt status gt RELUSE is an integer variable which contains the number of tuples in the Se relation on output lt status gt is an integer variable that is non zero if an error occurred 9 30 MAPOL PROGRAMMING AST
34. DCONVM DCONVMM DCONVMP ASTROS Aileron effectiveness constraint definition Buckling constraint definition Euler buckling constraint definition Lift effectiveness constraint definition Displacement constraint definition Principal strain constraint definition Principal strain constraint definition Principal strain constraint definition Functional constraint definition Flutter constraint definition Modal frequency constraint definition Fiber transverse strain constraint definition Fiber transverse strain constraint definition Fiber transverse strain constraint definition Composite laminate constraint definition Composite laminate minimum gauge constraint definition Composite element ply minimum gauge constraint definition Flexible stability coefficient constraint definition BAR element cross sectional parameter side constraint definition BAR element cross sectional parameter side constraint definition Composite layer thickness constraint definition for shape linking BAR element cross sectional parameter definition for shpae linking Thickness constraint definition for use with shape function design variable linking Aeroelastic trim parameter constraint definition Tsai Wu stress constraint definition Tsai Wu stress constraint definition Tsai Wu stress constraint definition Von Mises stress constraint definition Von Mises stress constraint definition Von Mises stress constraint defi
35. DESVARS Description Designates shape function linked global design variable properties Format and Example 1 2 3 4 5 6 7 8 9 10 DESVARS DVID SHAPEID VMIN VMAX VINIT LAYERNUM LAYRLST LABEL DESVARS 1 0 01 2 0 1 0 13 INBDTOP Field Contents DVID Design variable identification Integer gt 0 SHAPEID Identification number of SHAPE SHAPEM Or SHPGEN Bulk Data entries defining the shape function Integer gt 0 or blank Default DVID VMIN Minimum allowable value of the design variable Real Default 107 VMAX Maximum allowable value of the design variable Real Default 10 VINIT Initial value of the design variable Real VMIN lt VINIT lt VMAX No default a value must be supplied LAYRNUM Layer number if referencing a single layer of composite element s Integer gt 0 or blank LAYRLST Set identification of PLYLIST entries specifying a set of composite layers to be linked Integer gt 0 or blank LABEL Optional user supplied label to define the design variable Character Remarks 1 The elements linked to the DESvars are specified using SHAPE and or SHAPEM Bulk Data entries 2 Theinitial local variables are computed from tinit P VINIT Where P is the design variable linking matrix and the minimum and maximum values for the local variables are taken from the TMIN and TMAX values on the property and connectivity entrie
36. Direct 6 x 6 mass matrix definition at a structural node Concentrated mass at a structural node Rod element soparametric quadrilateral membrane element soparametric quadrilateral element with bending and membrane stiffness Rod element Shear panel soparametric triangular element with bending and membrane stiffness Constant strain triangular membrane element General element 7 5 13 Structural Element Properties PBA PBA PCO PCO PCO PTRME R R1 P P1 Prismatic beam element Prosmatic beam element defined with standard cross sectional parameters Composite laminate definition for CQDMEM1 CQUAD4 CTRIA3 and CTRMEM elements Composite laminate definition for CQUAD4 and CTRIA3 elements Composite laminate definition for CQUAD4 and CTRIA3 elements Scalar elastic spring element Linear quadratic and cubic isoparametric hexahedral element Scalar mass element soparametric quadrilateral membrane element Rod element Shear panel Definition of shell element properties for CQUAD4 and CTRIA3 elements Constant strain triangular membrane element 7 5 14 Unsteady Aerodynamics AER CAE CAE CONI ELF o RO RO2 EFFF ACT Reference parameters Aerodynamic macroelement panel definition Body configuration definition Definition of flutter aerodynamic control effectiveness Parameter definition for flutter analysis 7 10 THE BULK DATA PACKET
37. ERROR CHECKING IN THE INPUT FILE PROCESSOR As mentioned in the preceding subsection the 1rP module performs basic error checking to ensure that the input data is of the correct type In addition the templates provide for error checks that enable the IFP to check that the data satisfy particular requirements For example the IFP can be directed to require that a particular value be greater than zero or be one of a finite number of selections At its most complex the bulk data processor checks to ensure specific relationships among data on a single bulk data entry It is important to understand however that no error checks occur in the IFP to ensure that references to and interrelationships among multiple bulk data entries are satisfied These more complex checks occur in subsequent engineering modules A complete description of the available template error checks and the mechanism provided to add additional error checks is presented in the Programmer s Manual The reader may find it helpful to study this documentation since the bulk data packet and the bulk data entries are closely linked to the software in both the SYSGEN utility and the rrp module 7 5 BULK DATA ENTRY SUMMARY This section contains a summary of all the bulk data entries in the ASTROS system separated into logically related groups The groups are composed of either model definition entries subcase definition entries or general list entries This is followed by a detailed desc
38. IF lt cond gt THEN Rather than a single statement the body on the block may contain any number of statements IF A lt B THEN C 1 0 D 4 0 CALL UTMPRT MMAT ENDIF 9 4 4 3 The IF THEN ELSE The IF THEN ELSE statement is used to execute one of two separate blocks of code depending on a specific condition The syntax of this statement is IF lt cond gt THEN BLOCK 1 ELSE BLOCK 2 ENDIF If the lt cond gt is satisfied the instructions in BLOCK 1 are executed If lt cond gt is not satisfied then BLOCK 2 is executed 9 22 MAPOL PROGRAMMING ASTROS USER S MANUAL 9 4 4 4 Nested IF Statements IF statements may be nested to any level That is each IF or ELSE part may contain another IF statement as shown below IF A gt B THEN A 100 ELSE IF C lt D THEN C 200 ELSE C 3 ENDIF ENDIF Note that each IF THEN ELSE must terminate with its own ENDIF It is helpful to indent code so that the blocks are obvious 9 4 5 THE END AND ENDP STATEMENTS The END and ENDP statements are used to indicate the physical end of a MAPOL program or in line procedure respectively 9 5 INPUT OUTPUT STATEMENTS The MAPOL compiler does not have facilities for input in the programming language All input is handled by the ASTROS executive system MAPOL does however allow direct output to the system print device as defined by the ASTROS host computer Output is merged with
39. Naturally a relatively new code like ASTROS cannot attempt to address all these features Instead the ASTROS designers consid ered it important to focus on design optimization and provide a large but finite number of options for post processing outside this area To support a powerful and general purpose ability to query solution results UAI provides the program called eSHELL This special program allows users to access any ASTROS data to view it interactively and to generate files which can be moved from one computer to another or used as input to other application programs 8 40 OUTPUT FEATURES ASTROS USER S MANUAL Chapter 9 MAPOL PROGRAMMING This chapter contains the programmer s manual for the ASTROS executive language MAPOL It pre sents the syntax and features of the MAPOL language and it contains the general information needed to make syntactically correct modifications to the ASTROS standard MAPOL sequence and to write inde pendent MAPOL programs to direct the ASTROS system All variable types statement forms input out put features and intrinsic functions are presented 9 1 INTRODUCTION AND USER OPTIONS The Matrix Analysis Problem Oriented Language MAPOL is a high level computer language that has been designed to support the large scale matrix operations typically encountered in engineering analysis Its conceptual roots may be traced to the Direct Matrix Abstraction Program DMAP capability found in the NASTRA
40. SID Density set identification number Integer gt 0 DENSi Density ratio value Real gt 0 0 Remarks 1 DENSLIST Bulk Data entries are selected in the Function Packet 2 The density ratios will be used to select particular intrinsic function values for those intrinsics that are associated with a density ratio e g flutter roots 7 104 THE BULK DATA PACKET ASTROS USER S MANUAL DESELM Input Data Entry DESELM Description Designates design variable properties when the design variable is uniquely associated with a single finite element Format and Example 1 2 3 4 5 6 g 8 9 10 DESELM DVID EID ETYPE VMIN VMAX VINIT LAYERNUM LABEL CONT CONT DVSYMBL DESELM T 10 CBAR 0 01 10 0 1 0 ABC BC D1 Field Contents DVID Design variable identification Integer gt 0 EID Element identification Integer gt 0 ETYPE Element type Character selected from CELASi CMASSi CONM2 CBAR CROD CONROD CSHEAR CQDMEM1 CTRMEM CQUAD4 CTRIA3 VMIN Minimum allowable value of the design variable Real gt 0 0 Default 001 VMAX Maximum allowable value of the design variable Real gt 0 0 Default 1000 VINIT Initial value of the design variable Real VMIN lt VINIT lt VMAX Default 1 0 LAYERNUM The layer number of a composite element to be designed Integer gt 0 or blank LABEL Optional user supplied lab
41. Set definition for aerodynamic analysis USER S MANUAL Description Defines a set of integers by a list Format and Examples 1 2 3 4 5 6 7 8 9 10 SET1 SID G1 G2 G3 G4 G5 G6 G7 CONT CONT G8 etc SET1 3 31 62 93 124 16 1 7 18 ABC BC 19 Alternate Form T 2 3 4 5 6 7 8 9 10 SET1 SID G1 THRU G2 Field Contents SID Set of identification numbers Integer gt 0 Gi List of integers Integer gt 0 Remarks 1 These entries are referenced by the SPLINE1 and FLUTTER data entries When using the THRU option all intermediate quantities will be assumed to exist 2 3 When used by SPLINE1 the entry refers to a list of structural grid points 4 When used by FLUTTER the entry refers to mode numbers to be omitted in the flutter analysis 7 214 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description Defines a set of structural grid points in terms of aerodynamic macro elements SET2 Format and Examples Grid Point List af 2 3 4 5 6 7 8 SET2 SID SP1 SP2 CH1 CH2 ZMAX ZMIN SET2 3 0 0 0 73 0 0 0 667 150 3191 Field Contents SID Set identification number Integer gt 0 SP1 SP2 Lower and higher span division points defining prism containing set 1 01 gt Real gt 0 01 CH1 CH2 Lower and higher chord
42. USER S MANUAL This pageis intentionally blank 10 2 REFERENCES ASTROS
43. When subscripted matrix entities are used the executive system generates a CADDB entity name and relates that name to the subscript value The MAPOL programmer is therefore cautioned that unlike other high order variables subscripted variables and subscripted matrix entities do not have a corre sponding CADDB entity of the same name Due to the nature of the name generation algorithm sub scripted entity names must be unique in their first five characters 9 2 4 2 Data Type Relation The most complex and powerful MAPOL data type is the RELATION Briefly a relation can be thought of simply as a table The rows of the table are called entries and the columns attributes The CADDB isa collection of such relations as shown in Figure 9 1 In the figure a single relation called GRID has been highlighted The GRID relation has four attributes an identification number GID and three spatial coordinates X Y and Z The formats or schemas of relations that reside on CADDB are fixed 9 8 MAPOL PROGRAMMING ASTROS USER S MANUAL ENT1 ENT3 lt Database HH OG HH Attributes gt GID x Y Z 101 0 0 0 0 0 0 Entries 102 1 0 0 0 0 0 103 1 0 1 0 0 0 104 0 0 1 0 0 0 Figure 9 1 Schematic Representation of Relation All of the relations that are generated by the ASTROS modules that appear in the MAPOL program must be declared The rules for these declarations are lt decl
44. case _sid Function Arguments mvalue Mach value mach_sid Set identification of a MACHLIST bulk data entry used to specify the mach value dvalue Density ratio value dens_sid Set identification of a DENSLIST bulk data entry used to specify the density ratio value modeid Mode index mode_sid Set identification of a MODELIST bulk data entry used to specify the mode index vvalue Velocity value vel_sid Set identification of a VELOLIST bulk data entry used to specify the velocity value caseid Subcase identification 6 38 THE FUNCTION PACKET USER S MANUAL USER S MANUAL FROOT case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number Notes 1 The specific discipline request defines whether the case and or mode is a valid request in the response functions 2 If the subcase reference is omitted then the specific discipline request defines the requested subcase 3 The function returns the Real part of the flutter root If the Imaginary part is required then the IMAG intrinsic function must be used ASTROS THE FUNCTION PACKET 6 39 MASS USER S MANUAL Intrinsic Function MASS Purpose Toreturn the mass of selected elements Usage nee l eid plyid ELEMLIST elem_sid PLYLIST ply_sid Function Arguments eid Identification of an element specified in the Bulk Data Packet elem_sid Set identification of an ELEMLIST bulk data entry used to specify an el
45. entities themselves are stored in the DATA component To provide the maximum flexibility for a wide variety of data storage requirements the data components may be stored in a number of different physical files Most database systems are organized in this manner because the index component is generally small in size and referenced often while the data component may be extremely large and not fit ina single file or even on a single disk drive 2 1 6 4 ASSIGNing Databases Each logical database must be defined in the ASTROS job stream Details of this are found in Chapter 2 2 1 6 5 Database File Names The naming of database files follows a convention that is different from that of other UAI NASTRAN files The file names are generated automatically at execution time The conventions used are also described starting in Section 2 2 of this chapter 2 6 RUNNING ASTROS ASTROS USER S MANUAL 2 1 6 6 Very Large Databases You may be solving extremely large problems with ASTROS In such cases it may be possible that a databases exceeds the capacity of a single disk drive ASTROS has made provision for this and you must contact your UAI System Support Specialist for details describing the use of this advanced feature 2 1 7 Host Computer Dependencies The sections that follow provide detailed information describing the differences in ASTROS execution procedures and commands which depend on your host computer system 2 2 UNIX BASED COMPUTER
46. these options provide the name of the last module entered prior to the failure This provides a starting point to diagnose the problem Table 3 1 Executive MAPOL Debug Commands KEYWORD DESCRIPTION MSTACK MAPOL compiler stack output MEXEC MAPOL execution debug flag MOBI MAPOL object code debug packet MTRACE MAPOL trace debug output MATRIX MAPOL peeper matrix operation trace LOGMODULE Expanded log entries for each module LOGBEGIN Beginning entries for each module in log file ASTROS THE INPUT DATA STREAM 3 13 USER S MANUAL 3 4 2 DATABASE AND MEMORY MANAGER DEBUG COMMANDS The database management system has a number of debug options which can be divided into three categories trace options control options and memory manager options These are shown in Table 3 2 The first group of database debug commands contain two tracing options TRACE and IOSTAT The IOSTAT keyword selects either a FULL tracing or a summary The first of these options and the IOSTAT FULL option are further controlled by the ENTITY option which completes the first group of keywords Note the tracing keywords generate an overwhelming amount of data which are often of limited use unless the user is familiar with the internal structure of the database files The ENTITY keyword limits the activation of the tracing options to those times when the named database matrix relation or unstructured entity is open If no en
47. tude and phase If used with the PRINT command all data that are not otherwise specified use the requested Form FREQ ITER MODE and TIME if applicable for that type of data If used with an option Form FREQ ITER MODE and TIME override the global request Options a through af can be either ALL NONE or a positive integer and additionally option b ITER can be LAST and options h CGRA and i DCON can be ACTIVE ALL requests all values NONE turns off a request from a previous hierarchy while an integer value refers to a bulk data entry LAST requests that output be printed for only the final value in a list For example ITER LAST selects output for the final iteration in an optimization ACTIVE selects the active constraints HIST and TRIM are toggles If they are present the specified data are punched TRIM indicates that stability derivative data associated with an aeroelastic trim are to be punched HIST indicates that the design iteration history summary is to be punched Aerodynamic macro elements are selected indirectly A macro element is chosen by selecting one or more aerodynamic box elements contained within the macro element See Table 47 for a summary of how the items are punched or written to the CADDB database 5 38 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL SAERO Solution Control Command SAERO Description Invokes the static aerodynamics discipline Hierarchy Level Discipline Format and Example
48. where N is the vector defined in Fields 6 7 and 8 2 ACID of zero references the basic coordinate system 7 134 THE BULK DATA PACKET ASTROS USER S MANUAL FORCE1 Input Data Entry FORCE1 Static Load Alternate Form 1 Description Used to define a static load by specification of a value and two grid points which deter mine the direction Format and Example 1 2 3 4 5 6 if 8 9 10 FORCE1 SID G F G1 G2 FORCE1 6 13 2 393 16 13 Field Contents SID Load set identification number Integer gt 0 G Grid point identification number Integer gt 0 F Value of load Real Gi Grid point identification numbers Integer gt 0 G1 G2 Remarks 1 Thedirection of the force is determined by the vector from G1 toG2 ASTROS THE BULK DATA PACKET 7 135 FREQ Input Data Entry Defines a set of frequencies to be used in the solution of frequency response problems FREQ USER S MANUAL Description Format and Example 1 2 3 4 5 6 7 8 9 10 FREQ SID F1 F2 F3 F4 F5 F6 F7 CONT CONT F8 F9 etc CONT FREQ 3 2 598 3 05 17 216 25 28 31 2 ABC BC 29 2 22 4 19 3 Field Contents SID Frequency set identification number Integer gt 0 Fi Frequency value Real 0 0 Remarks 1 The units for the frequencies are cycles per unit time 2 Frequency sets must be selected by the Solution Cont
49. while an UPPER bound constraint excludes all values to the right irrespective of the sign of AEREQ 3 The effectiveness in roll of multiple control surfaces may be specified using multiple DCONALE entries with one constraint generated for each LABEL CTYPE combination ASTROS THE BULK DATA PACKET 7 67 DCONBK USER S MANUAL Input Data Entry DCONBK Buckling Constraint Definition Description Defines a local panel buckling constraint of the form Y Lower Bound giona 25E 1 0 x lt 0 0 for A gt AREOQ or AREQ Ye Upper Bound g uppe 1 0 ea lt 0 0 for A lt AREQ Format and Example i 2 3 4 5 6 7 8 9 10 DCONBK SID ETYPE EID LENGTH WIDTH CTYPE REO DCONBK 25 QUAD4 101 15 LOWER 3 65 Field Contents SID Plate buckling panel constraint set identification Integer gt 0 ETYPE Plate buckling control element type May be QUAD4 or TRIA3 Character EID Element identification number Integer gt 0 LENGTH Plate buckling panel length in consistant length units Real gt 0 0 or blank See Remark 3 WIDTH Plate buckling panel width in consistant length units Real gt 0 0 or blank See Remark 3 CTYPE Constraint type either LOWER for lower bound or UPPER for upper bound Character AREO Buckling eigenvalue limit Real Default 1 0 Remarks 1 Buckling constraints are selected in Solution Control with the
50. xT YT Tensile stress limit in the transverse direction Real gt 0 0 YC Compressive stress limit in the transverse direction Real Default yT ss Shear stress limit for in plane stress Real gt 0 0 F12 Tsai Wu interaction term Real MIDi Material identification numbers Integer gt 0 Remarks 1 Stress constraints are selected in Solution Control with the discipline option STRESS sid 2 If the alternate form is used MID2 must be greater than or equal to MID1 Materials in the range which do not exist are ignored 3 The stress limits for compression xc and Yc are always treated as negative values regardless of the sign of the input values ASTROS THE BULK DATA PACKET 7 99 DCONTWP USER S MANUAL Input Data Entry DCONTWP Tsai Wu Stress Constraint Definition Description Defines Tsai Wu stress constraints by specifying element property identification num bers Format and Example 1 2 3 4 5 6 7 8 9 10 DCONTWP SID XT XC YT YG SS F12 PTYPE CONT CONT LAYRNUM PID1 PID2 PID3 etc DCONTWP 100 1 6 RO 1 4 1 4 LEDS PCOMP ABC BC 100 200 300 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONTWP SID XT XC YT YC ss F12 PTYPE CONT CONT LAYRNUM PID1 THRU PID2 Field Contents SID Stress constraint set identification Integer gt 0 XT Tensile stress limit in the longitudinal direction Re
51. 0 SYMXZ SYMXY Remarks Symmetry flags associated with aerodynamics Integer 1 Symmetric o or Blank Asymmetric 1 Antisymmetric 1 Thecust entry is selected as a discipline option for FREQUENCY Or TRANSIENT in Solution Control 2 Thegust angleis in the z direction of the aerodynamic coordinate system The value is X Xo WG T t V where T is the tabular function 3 The symmetry flags will be used to select the appropriate unsteady aerodynamic matrices from the list of m k pairs for each symmetry option given on the MKAERO entries 7 148 THE BULK DATA PACKET ASTROS USER S MANUAL Ic Input Data Entry Ic Transient Initial Condition Description Defines values for the initial conditions of coordinates used in transient analysis Both displacement and velocity values may be specified at independent coordinates of the structural model Format and Example 1 2 3 4 5 6 7 8 9 10 Ic SID G UO VO IG 1 3 2 52 0 6 0 Field Contents SID Set identification number Integer gt 0 G Grid or scalar or extra point identification number Integer gt 0 C Component number blank or zero for scalar or extra points any one of the digits 1 through 6 for a grid point UO Initial displacement value Real vo Initial velocity value Real Remarks 1 Transient initial condition sets must be selected in the Solution Control IC SID to be used 2
52. 0858 1 20677E 03 8 84749E 03 1 00000E 01 6 91372E 02 8 33210E 03 2 21727E 03 13 0858 1 20677E 03 8 84749E 03 2 Q 1 00000E 01 5 43684E 02 7 64178E 03 2 58719E 03 18 0457 2 99228E 02 8 48469E 03 1 00000E 01 5 43683E 02 7 64178E 03 2 58719E 03 18 0457 2 99228E 02 8 48469E 03 13 0 1 00000E 01 6 16923E 02 3 07066E 03 1 17650E 03 73 7292 3 41404E 03 9 60305E 02 1 00000E 01 6 16923E 02 3 07066E 03 1 17650E 03 73 7292 3 41404E 03 9 60305E 02 1SIMPLIFIED FIGHTER WING ASTROS VERSION 9 0 03 03 93 Px 14 FINAL ANALYSIS SEGMENT STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 STRAINS IN QUADRILATERAL PLATES QUAD 4 ELEMENT LAYER FIBER STRAINS IN STRESS COORD SYSTEM PRINCIPAL STRAINS ZERO SHEAR ID NO DISTANCE NORMAL X NORMAL Y SHEAR XY ANGLE MAJOR MINOR 3 0 1 00000E 01 3 50886E 04 8 56139E 04 5 91205E 04 13 0479 4 19391E 04 9 24645E 04 1 00000E 01 3 50886E 04 8 56139E 04 5 91205E 04 13 0479 4 19391E 04 9 24645E 04 7 O 1 00000E 01 1 93048E 04 7 46862E 04 6 85105E 04 18 0443 3 04642E 04 8 58457E 04 1 00000E 01 1 93048E 04 7 46862E 04 6 85105E 04 18 0443 3 04642E 04 8 58457E 04 13 0 1 00000E 01 1 64593E 04 3 26487E 04 3 13462E 04 73 7247 3 72245E 04 2 10351E 04 1 00000E 01 1 64593E 04 3 26487E 04 3 13462E 04 73 7247 3 72245E 04 2 10351E 04 1SIMPLIFIED FIGHTER WING ASTROS VERSION 9 0 03 03 93 Pi 15 FINAL ANALYSIS SEGMENT STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 FORCES IN QUADRILATERAL PLATES QUAD 4 ELEMENT MEM
53. 1 4 BAR 101 102 ABC BC 107 108 142 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONVM SID ST Sc Ss ETYPE LAYRNUM EID1 THRU CONT CONT EID2 Field Contents SID Stress constraint set identification Integer gt 0 ST Tensile stress limit Real gt 0 0 or blank SC Compressive stress limit Real Default sT ss Shear stress limit Real gt 0 0 or blank ETYPE Element type Character selected from BAR ROD QDMEM1 TRMEM QUAD4 TRIA3 LAYRNUM The layer number of a composite element Integer gt 0 or blank EIDi Element identification numbers Integer gt 0 Remarks 1 Stress constraints are selected in Solution Control with the discipline option STRESS sid 2 If the alternate form is used EID2 must be greater than or equal to EID1 Elements in the range which do not exist are ignored 3 The stress limit for compression sc is always treated as a negative value regardless of the sign of the input value 4 LAYRNUM is only used if the element is composed of a composite material defined with Pcomp Bulk Data entries ASTROS THE BULK DATA PACKET 7 101 DCONVMM USER S MANUAL Input Data Entry DCONVMM Von Mises Stress Constraint Definition Description Defines a Von Mises stress constraint by specifying material identification numbers Format and Example 1 2 3 4 5 6 7 8 9 10
54. 1 Field Contents SID Identification number for new single point constraint set Integer gt 0 Si Identification numbers of single point constraint sets defined via spc or by SPC1 entries Integer gt 0 SID Si Remarks 1 Single point constraint sets must be selected in Solution Control SPC SID to be used 2 Nosi may be the identification number of a single point constraint set defined by another SPCADD entry The si values must be unique 4 SPCADD entries take precedence over SPC or SPC1 entries If both have the same set ID only the SPCADD entry will be used 7 220 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry SPC1 Single Point Constraint Alternate Form 1 SPC1 Description Defines sets of single point constraints Format and Examples T 2 3 4 5 6 7 8 9 10 SPC1 SID Cc G1 G2 G3 G4 G5 G6 CONT CONT G7 G8 G9 eter SPC1 3 2 1 3 10 9 6 5 ABC BC 2 8 Alternate Form T 2 3 4 5 6 7 8 9 10 SPC1 SID C GID1 THRU GID2 SPC1 313 456 10 THRU 1000 Field Contents SID Identification number of single point constraint set Integer gt 0 C Component number of global coordinate any unique combination of the digits 1 through 6 with no embedded blanks when point identification numbers are grid points must be null if point identification numbers are scalar points Gi GIDi Grid or
55. 1 00000E 00 DEG USER INPUT ROLL RATE PRATE 1 03324E 02 1 30519E 02 DEG S COMPUTED As in the longitudinal case discrepancies between the data for the first two forms may indicate an error in the spline transformations or more likely the boundary conditions to allow the applied load to reach the SUPORT point unreacted The effectiveness calculations are performed using the third form Finally the trim parameters that were computed for the current flight condition are shown In general these are the yaw angle in degrees the yaw rate in deg s the roll rate in deg s and the ANTISYMMETRIC control surface deflection angle s in degrees In each case the rigid and flexible trim state is shown the rigid is informational only and the parameter is labeled as COMPUTED if it was a free parameter in the trim analysis or USER INPUT if it was a fixed user input trim parameter Only those parameters explicitly called out on the TRIM bulk data entry are listed 8 3 SUMMARY OF SOLUTION RESULTS Some of the solution results of ASTROS are written to the print file while others are placed on the CADDB database In the latter case they can be accessed using the ICE interactive program Table 8 25 8 34 OUTPUT FEATURES ASTROS USER S MANUAL provides a summary of each quantity and indicates whether the data are printed or stored In each case if the PUNCH request results in storage of the data the PRINT request also stores the data even if the
56. 10 PLOAD4 LID EID1 P1 P2 P3 P4 THRU EID2 CONT CONT CID v1 v2 v3 PLOAD4 1 101 10 10 20 20 THRU 201 Field Contents LID Load set identification number I nteger gt 0 EID Element identification number I nteger gt 0 Remark 1 Pi Pressure at the grid points defining the element surface Real Remarks 2 3 4 CID Coordinate system identification number I nteger gt 0 Remarks 3 4 Vi Components of a vector in system CID that defines the direction of the grid point loads generated by the pressure Real Remarks 3 4 Remarks 1 For compatibility with commercial NASTRAN products ASTROS element type identifiers are not used Therefore the referenced element identification numbers must be unique among the plate element types If only P1 is given the pressure is assumed to be uniform over the element surface The P4 value is ignored for a triangular face The pressure intensity is the load per unit surface area If a direction vector is not specified the direction of the grid point loads is normal to the element mid surface at each grid point in the local 4z direction If the surface of the element is curved the direction of pressure may vary from point to point When the direction vector is defined and a value for CID is not entered the grid point load vectors are applied in the Basic Coordinate System Equivalent grid point loads are computed which depend on the specific element geometry and type A uniform pressure m
57. 2 LOGICAL EXPRESSIONS A logical expression produces a logical data type result with a value of TRUE Or FALSE 9 3 2 1 Logical Operators Table 9 5 lists the logical operators that may be used in logical expressions Table 9 5 MAPOL Logical Operators OPERATOR DESCRIPTION OPERATOR DESCRIPTION NOT Negation U nary OR Disjunction AND Conjunction XOR Equivalence ASTROS MAPOL PROGRAMMING 9 13 USER S MANUAL Logical operators must be separated by logical operands except for the following cases AND NOT OR NOT 9 3 2 2 Logical Operands Any of the following operands may be used in logical expressions e LOGICAL e LOGICAL CONSTANTS VARIABLES e LOGICAL ARRAY ELEMENTS e LOGICAL FUNCTION REFERENCE e LOGICAL EXPRESSION e RELATIONAL EXPRESSION Both logical and relational expressions may be enclosed on parentheses 9 3 2 3 Evaluation of Logical Expressions Logical expressions are evaluated based on truth tables shown in Table 9 6 L1 and 12 are logical variables T and F signify TRUE and FALSE Table 9 6 Evaluation of MAPOL Logical Expressions VARIABLES RESULT L1 L2 NOT L1 L1 OR L2 L1 AND L2 L1 XOR L2 T T F T T F T F F T F T F T T T F T F F T F F F 9 14 MAPOL PROGRAMMING ASTROS USER S MANUAL Logical operators have a hierarchy similar to the arithmetic operations
58. 4 1 MAPOL Declarations ee 4 6 4 4 2 The Solution Algorithm o 4 12 4 4 2 1 MAPOL Engineering and Utility Modules 0 4 13 4 4 2 2 The Preface Segment a 4 19 4 4 2 3 The Analysis Optimization Segments o e 4 19 4 4 3 Modifying the Standard MAPOL Sequence o 00000 ee eae 4 20 4 44 Restart Capability vv aa Ae A A a eG 4 22 4 4 4 1 Ensuring proper STATUS of the run time database 4 22 4 4 4 2 Suspending Restarting Execution 0 o e ee e 4 23 4 4 4 3 Resetting MAPOL Parameters 0 e eee eee ee ees 4 23 4 5 MAPOL PROGRAM LISTING 227 oe BA e eke edie es 4 24 ii ASTROS USER S MANUAL 5 THE SOLUTION CONTROL PACKET 5 1 5 1 OPTIMIZE AND ANALYZE SUBPACKETS 0 5 3 5 2 BOUNDARY CONDITIONS coa o i a 5 4 5 3 DISCIPLINES Fira de A ee Nab a Sek Se E AAA o E 5 7 53 1 DISGIPEINE OPTIONS gt 2000 Aopen ble Sg eR ao BR ae ee Be Ga ee es 5 9 5 3 2 STATICS Discipline Options s s i wa i eai a a ee 5 12 5 3 3 MODES Discipline Options 2 a a 5 12 5 3 4 SAERO Discipline Options o oo a a 5 12 5 3 5 FLUTTER Discipline Options aoaaa ee 5 13 5 3 6 TRANSIENT Discipline Options aooaa ee 5 13 5 3 7 FREQUENCY Discipline Options aooaa a ee 5 13 5 4 OUTPUT REQUESTS p iea t O18 3 See da e Oe ok SS Es 5 14 5 4 te Subset Options 2 cede ees
59. 4 5 6 7 8 9 10 DCONCLA SID CTYPE CLAREQ DCONCLA 25 UPPER 0 8 Field Contents SID Aerodynamic set identification for the imposed constraint Integer gt 0 CTYPE Constraint type either UPPER for upper bound or LOWER for lower bound Character Default LOWER CLAREQ Required flexible to rigid lift curve slope Real 0 0 Remarks 1 Displacement constraints are selected in Solution Control with the discipline option DCON SID 2 A LOWER bound constraint excludes all values to the left of CLAREQ on a real number line while an UPPER bound constraint excludes all values to the right irrespective of the sign of CLAREQ ASTROS THE BULK DATA PACKET 7 71 DCONDSP USER S MANUAL Input Data Entry DCONDSP Description Defines a deflection constraint of the form Y Ajuy lt dall UPPER BOUND or Y Aj uj gt 5 LOWER BOUND Format and Example 1 2 3 4 3 6 7 8 9 10 DCONDSP CTSET DCID CTYPE DALL LABEL G e A CONT CONT G Cc A G E A etc DCONDSP 1 10 LOWER 2 3 TIP 32 3 2 0 ABC BC 7 3 4 0 Field Contents CTSET Constraint set identification number Integer gt 0 DCID Constraint identification number Integer gt 0 CTYPE Constraint type either UPPER or LOWER bound Character Default UPPER DALL Allowable displacement Real LABEL User specified label to identify constraint Character G Grid identification Integer gt 0 C Componen
60. 6 7 8 9 10 SEQGP ID SEQID ID SEQID ID SEQID ID SEQID CONT CONT ID SEQID etc SEQGP 5392 15 6 596 0 2 2 Liso 3 Field Contents ID Grid point identification number Integer gt 0 SEQID Sequenced identification number a special number described below Remarks 1 ID is any grid or scalar point identification number which is to be reidentified for sequencing purposes The sequence number identifies a special number which may have any of the following forms where X is a decimal integer digit XXXX X X X XXXX X X XXXX X or XXXX where any of the leading Xes may be omitted This number must contain no embedded blanks The leading character must not be a decimal point 2 If the user wishes to insert a point between two already existing grid or scalar points such as 15 and 16 for example he would define it as say 5392 and then use this card to insert extra point number 5392 between them by equivalencing it to say 15 6 All output referencing this point will refer to 5392 3 The SEQID numbers must be unique and may not be the same as a point ID which is not being changed No extra point ID may be referenced more than once 3 The SEQID numbers must be unique and may not be the same as a point ID which is not being changed No extra point ID may be referenced more than once 4 Ifa point ID is referenced more than once the last reference will determine its sequence ASTROS THE BULK DATA PACKET 7 213 SET1 Input Data Entry SET1
61. 7 10 USER S MANUAL AERO Input Data Entry AERO Aerodynamic Physical Data Description Gives basic aerodynamic parameters for unsteady aerodynamic disciplines Format and Example 1 2 3 4 5 6 7 8 9 10 AERO ACSID REFC RHOREF AERO 100 300 0 1 1E 7 Field Contents ACSID Aerodynamic coordinate system identification Integer gt 0 or Blank See Remark 2 REFC Reference length for reduced frequency Real gt 0 RHOREF Reference density Real gt 0 Remarks 1 This entry is required for unsteady aerodynamic disciplines Only one AERO entry is allowed 2 The acsiIp must be a rectangular coordinate system Flow is in the positive x direction If blank the basic coordinate system is used ASTROS THE BULK DATA PACKET 7 17 AEROS USER S MANUAL Input Data Entry AEROS Steady Aero Physical Data Description Gives basic aerodynamic parameters for the steady aerodynamic discipline Format and Example 1 2 3 4 5 6 7 8 9 10 AEROS ACSID RCSID REFC REFB REFS GREF REFD REFL AEROS 10 20 10 100 1000 1 Field Contents ACSID Aerodynamic coordinate system identification Integer gt 0 or blank See Remark 2 RCSID Reference coordinate system identification for rigid body motions Integer gt 0
62. ASTROS USER S MANUAL MACHLIST Input Data Entry MACHLIST Description Defines a list of Mach numbers Format and Example 1 2 3 4 5 6 T 8 9 10 MACHLIST SID MACH1 MACH2 MACH3 MACH4 MACH5 MACH6 MACH7 CONT CONT MACH8 MACH9 etc MACHLIST 201 1 0 0 5 0 7 Field Contents SID Mach set identification number Integer gt 0 MACHi Mach number Real gt 0 0 Remarks 1 MACHLIST Bulk Data entries are selected in the Function Packet ASTROS THE BULK DATA PACKET 7 155 MAT1 Input Data Entry Description MAT1 Material Property Definition Form 1 USER S MANUAL Defines the material properties for linear temperature independent isotropic materials Format and Example 1 2 3 4 5 6 7 8 9 10 MATL MID E G NU RHO A TREF E CONT CONT ST SC ss MCSID MATL 17 BT 0 33 4 28 976 AS 23 ABC B 20 4 15 4 12 4 Field Contents ID Material identification number Integer gt 0 E Young s modulus Real gt 0 0 or blank G Shear modulus Real or blank NU Poisson s ratio 1 0 lt Real lt 0 5 or blank RHO Mass density Real gt 0 0 A Thermal expansion coefficient Real TREF Thermal expansion reference temperature Real GE Structural element damping coefficient Real ST SC SS Stress limits for tension compression and shear Real Used to compute margins of safety i
63. ASTROS 1 SYMMETRIC and 2 ANTISYMMETRIC The number of degrees of freedom SuPORTed at the support point determine the number of trim degrees of freedom SYMMETRIC analyses may have DOF s 1 3 and or 5 thrust lift pitch or any combination ANTISYMMETRIC analyses may have 2 4 and or 6 side force roll yaw or any tOO1E 01 L2 287 88 4R REAL TJ1 3600 eL 3 r 9 214w y4R 5 Oboi 21 Mo 84 afffffffffff 1TISYMMETRIC USER S MANUAL combination The thrust DOF should never be free since ASTROS has no mechanism to input thrust and the drag computations based on potential aerodynamics are invariably poor The code does not impose any restriction however Each TRIM print is labeled with the Mach number dynamic pressure reference grid point and the appropriate normalization parameters These parameters are the reference area and chord length for longitudinal coefficients and reference area and span for lateral coefficients The SYMMETRIC trim print includes in the most general case the drag lift and pitching moment stability coefficients for Co a Cm Thickness and camber effects Cpa CL Cm Angle of attack a in both radians and degrees Cp CL Cm User defined control surface deflection s 5 both radians and degrees Epi EL Cu Pitch rate q in both radians and degrees These nondimensional factors are implicitly defined in the following equations Drag as eae es a Cy sy tCy si fori 1 ney o a q 3
64. C 3 102325E 01 LZ oe NRE e 64 123 9 X 0 000000E 00 XY 2 000000E 01 A 2 535997E 01 LX 62 lt 17 15 2 955829E 00 1 710619E 01 Y 9 217892E 00 YZ 3 080879E 00 B 1 615026E 01 LY 78 62 00 Z 3 504066E 01 ZX 0 000000E 00 C 3 422195E 01 LZ 09 liz 7299 STRAINS IN 8 NODED SOLID ELEMENT IHEXI ELEMENT STRAIN CENTER AND CORNER POINT STRAINS DIRECTION COSINES MEAN OCTAHEDRAL ID POINT NORMAL SHEAR PRINCIPAL A B 10 STRAIN SHEAR STRAIN 123 1 X 5 659012E 06 XY 7 415626E 06 A 8 498356E 06 LX 61 79 00 1 886337E 06 9 344843E 06 Y 0 000000E 00 YZ 0 000000E 00 B 1 415737E 05 LY 53 41 00 Z 0 000000E 00 ZX 8 082256E 06 C 0 000000E 00 LZ 58 45 00 123 2 X 5 377361E 06 XY 7 563655E 06 A 1 477920E 05 LX 78 62 00 1 792454E 06 9 952897E 06 Y 0 000000E 00 YZ 0 000000E 00 B 9 401835E 06 LY 40 50 00 Zz 0 000000E 00 ZX 9 041167E 06 C 0 000000E 00 LZ 48 60 00 123 3 X 2 660247E 07 XY 5 200001E 06 A 5 628016E 06 LX 66 74 15 1 182329E 07 4 334298E 06 Y 9 323016E 07 YZ 8 010304E 07 B 4 962797E 06 LY 75 67 00 8 2 1 5 IHEX2 Element Output The IHEX2 element is a quadratic isoparametric solid hexahedron element with three extensional de grees of freedom for each of its 20 nodes Stresses strains and strain energies are available as output for the HEX2 element through the STRESS STRAIN and ENERGY solution control print command options Force output is not available for thel HEX2 element On reques
65. CONT CONT EID3 EID4 etc DCONEP 100 1 2 dia Lis 2 BAR 101 102 ABC BC 107 108 142 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONEPM USER S MANUAL Input Data Entry DCONEPM Principal Strain Constraint Definition Description Defines a principal strain constraint by specifying material identification numbers Format and Example 2 3 4 5 6 7 8 9 10 DCONEPM SID ST SC ss MID1 MID2 MID3 MID4 CONT CONT MID5 MID6 etc DCONEPM 100 1 2 1 2 1 2 8888 9999 1 99 ABC BC PI 123 Alternate Form 2 3 4 5 6 7 8 9 10 DCONEPM SID ST SC ss MATL THRU MAT2 Field Contents SID Strain constraint set identification Integer gt 0 ST Principal strain limit in tension Real gt 0 0 SC Principal strain limit in compression Real Default sT SS Principal strain limit in shear Real gt 0 0 MIDi Material identification numbers Integer gt 0 Remarks 1 Strain constraints are selected in Solution Control with the discipline option STRAIN sid 2 Ifthe alternate form is used MID2 must be greater than or equal to MID1 Material properties in the range which do not exist are ignored The shear strain limit ss is used only with the SHEAR element 4 The strain limit for compression Sc is always treated as a negative value regardless of the sign of the input value 7 74 THE BUL
66. DCONFTP SID EFT EFC ETT ETC PTYPE LAYRNUM PID1 CONT CONT PID2 PID3 etc DCONFTP 100 2 Ta DTO 35 43 PCOMP 2 100 CONT CONT 110 120 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONFTP SID EFT EFC ETT ETC ETYPE LAYRNUM PID1 CONT CONT THRU PID2 Field Contents SID Strain constraint set identification Integer gt 0 EFT Tensile strain limit in the fiber direction Real gt 0 0 EFC Compressive strain limit in the fiber direction Real Default EFT ETT Tensile strain limit in the transverse direction Real gt 0 0 ETC Compressive strain limit in the transverse direction Real Default ETT PTYPE Property type Character selected from PCOMP PCOMP1 PCOMP2 LAYRNUM The layer number of a composite element Integer gt 0 or blank PIDi Property identification numbers Integer gt 0 Remarks 1 Strain constraints are selected in Solution Control with the discipline option STRAIN sid 2 Fiber transverse strain constraints may only be applied to elements defined using composite materials 3 If the alternate form is used PID2 must be greater than or equal to PID1 Properties in the range which do not exist are ignored 4 The strain limits for compression EFC and ETC are always treated as negative values regardless of the signs of the input values ASTROS THE BULK DATA PACKET 7 83 DCONLAM USER S MANUAL Input Data Entry DCONLAM Composite laminate composition constraint Description Defines a constraint on the relati
67. DCONVMM SID ST SC SS MID1 MID2 MID3 MID4 CONT CONT MID5 MID6 Sete DCONVMM 100 1 6 S16 1 4 101 201 301 401 ABC BC 501 601 701 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONVMM SID ST sc Ss MID1 THRU MID2 Field Contents SID Stress constraint set identification Integer gt 0 ST Tensile stress limit Real gt 0 0 or blank sc Compressive stress limit Real Default sT ss Shear stress limit Real gt 0 0 or blank MIDi Material identification numbers Integer gt 0 Remarks 1 Stress constraints are selected in Solution Control with the discipline option STRESS sid 2 If the alternate form is used MID2 must be greater than or equal to MID1 Materials in the range which do not exist are ignored 3 The stress limit for compression sc is always treated as a negative value regardless of the sign of the input value 7 102 THE BULK DATA PACKET ASTROS USER S MANUAL DCONVMP Input Data Entry DCONVMP Von Mises Stress Constraint Definition Description Defines a Von Mises stress constraint by specifying property identification numbers Format and Example 1 2 3 4 5 6 7 8 9 10 DCONVMP SID ST sc SS PTYPE LAYRNUM PID1 PID2 CONT CONT PID3 PID4 etc DCONVMP 100 L246 1 6 1 4 PBAR 102 103 ABC BC 107 108 142 Alternate Form
68. Data Entry DVTOPTP Type definition for designed element thickness variation Description Defines the thickness variation type for a designed element by specifying the element property identification numbers Format and Examples 1 2 3 4 5 6 7 8 9 10 DVTOPTP TYPE PTYPE PID1 PID2 PID3 PID4 PID5 PID6 CONT CONT PID7 PID8 etc DVTOPTP TOP PSHELL 100 200 Alternate Form 1 2 3 4 5 6 7 8 9 10 DVTOPTP TYPE PTYPE PID1 THRU PID2 Field Contents TYPE Designed element thickness variation type one of the character values CENTER TOP or BOTTOM Character default CENTER CENTER Element thickness varies about a fixed element reference plane TOP Element thickness varies about a fixed element top plane BOTTOM Element thickness varies about a fixed element bottom plane PTYPE Property type Character selected from PSHELL PCOMP PCOMP1 PCOMP2 PIDi Property identification number Integer gt 0 Remarks 1 The thickness option for elements connected to the specified properties will be ignored if it they are not designed bending plate elements USER S MANUAL DYNRED Input Data Entry DYNRED Dynamic Reduction Data Description Defines dynamic reduction control data Format and Example 1 2 3 4 5 6 7 8 9 10 DYNRED SID FMAX
69. EFFID LABEL1 EFF1 LABEL2 EFF2 LABEL3 EFF 3 CONT CONT LABEL4 EFF A etc CONEFFS 10 AILI 0 65 INBORD 0 55 Field Contents EFFID A unique identification number identifying the set LABELi A unique alphanumeric string of up to eight characters to identify a control surface defined by an AESURF entry EFFi Effectiveness value for the associated surface Real Remarks 1 Theset identification number is referenced by the TRIM bulk data entry 2 All aerodynamic forces created by the control surface will be reduced to the reference amount For example EFF1 0 70 indicates a 30 percent reduction in the forces 7 44 THE BULK DATA PACKET ASTROS USER S MANUAL CONLINK Input Data Entry CONLINK Linked Control Surfaces Description Causes control surfaces to vary in a prescribed fashion relative to one another Format and Example 1 2 3 4 5 6 7 8 9 10 CONLINK LABEL LABEL1 VAL1 LABEL2 VAL2 LABEL3 VAL3 CONT CONT LABEL4 VAL4 etc CONLINK ROLL1 AIL 1 0 LEFLAP 1 0 Field Contents LABEL A unique alphanumeric string of up to eight characters to identify the control surface taht is composed of other control surfaces LABELi A unique alphanumeric string of up to eight characters to identify a control surface defined by an AESURF entry VALi Participation factor Real Remarks 1 All of the LABEL surfaces must be of the same TYPE e g
70. G3 CID G1 G2 G3 CORD1S 3 16 32 19 Field Contents CID Coordinate system identification number Integer gt 0 Gi Grid point identification number Integer gt 0 G1 G2 G3 Remarks 1 Coordinate system identification numbers on all CORD1R CORD1C CORD1S CORD2R CORD2C and CORD2s8 entries must be unique 2 Thethree points G1 G2 and G3 must be noncollinear 3 The location of a grid point P in the sketch in this coordinate system is given by R 8 6 where O and q are measured in degrees 4 The displacement coordinate directions at P are dependent on the locations of P as shown above by U Up Uo 5 Points in the polar axis may not have their displacement direction defined in this coordinate system since an ambiguity results Q 6 One or two coordinate systems may be defined on a single entry ASTROS THE BULK DATA PACKET 7 53 CORD2C USER S MANUAL Input Data Entry CORD2C Cylindrical Coordinate System Definition Form 2 Description Defines a cylindrical coordinate system by reference to the coordinates of three grid points The first point defines the origin The second point defines the direction of the z axis The third lies in the plane of the azimuthal origin The reference coordinate system must be independently defined Format and Example 1 2 3 4 5 6 7 8 9 10 CORD2C CID RID Al A2 A3 B1 B2 B3 CONT CONT c1 C2 C3 CORD2C 3 17 S29 1 0
71. GN Grid point identification number at which all 6 independent degrees of freedom are assigned Integer gt 0 Cc Component numbers of dependent degrees of freedom in the global coordinate system assigned by the element at grid points GM1 GM2 etc Indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 or blank GMi Grid point identification number at which dependent degrees of freedom are assigned Integer gt 0 Remarks 1 The RBE2 entry is selected in the Solution Control with the MPC SETID option of the BOUNDARY command THIS IS AN ENHANCEMENT TO THE NASTRAN METHOD WHICH DOES NOT ALLOW RIGID CONNECTIONS TO BE CHANGED FOR DIFFERENT BOUNDARY CONDI TIONS 2 The components indicated by cm are made dependent at all grid points GMi 3 Them set degrees of freedom specified on this entry may not be specified on other entries that define mutually exclusive sets 4 Rigid element identification numbers must be unique within each element type for each Mpc set identification number 7 206 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description Defines the motion of a reference grid point as the weighted average of motions at a set RBE3 Rigid Body Element Form 3 of other grid points Format and Example 1 2 3 4 5 6 7 8 9 RBE3 SETID EID REFG REFC W
72. Integer gt 0 CP Identification number of coordinate system in which the location of the grid point is defined Integer gt 0 or blank Xi Location of the grid point in coordinate system cP Real CD Identification number of coordinate system in which displacements degrees of free dom constraints and solution vectors are defined at the grid point Integer gt 0 or blank PS Permanent single point constraints associated with grid point any of the digits 1 6 with no embedded blanks Integer gt 0 or blank Remarks 1 All grid point identification numbers must be unique with respect to all other structural and scalar points 2 Themeaning of X1 X2 and x3 depend on the type of coordinate system CP as follows TYPE x1 X2 X3 Rectangular X Y Z Cylindrical R 9 deg Z Spherical R 9 deg deg Also see CORDi j entry descriptions 3 Thecollection of all cp coordinate systems defined on all GRID entries is called the Global Coordinate System All degrees of freedom constraints and solution vectors are expressed in the Global Coordi nate System 7 146 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry GRIDLIST GRIDLIST Description Defines a list of points at which outputs are desired Format and Example dt 2 3 4 5 6 7 8 9 10 GRIDLIST SID GID1 GI
73. Intermediate Steady Aerodynamic Matrix Output oaa a a 8 36 8 4 2 Intermediate Unsteady Aerodynamic Matrix Output o 8 36 8 4 3 Flutter Root Iteration Output e e 8 37 8 4 4 Stress Constraint Computation Output 2 2 e e e 8 37 8 4 5 Intermediate Optimization Output o ee 8 38 8 5 EXECUTIVE SEQUENCE OUTPUT UTILITIES 8 38 8 5 1 Structural Set Definition Print Utility USETPRT 0 8 38 8 5 2 Special Matrix Print Utility UTGPRT 0 oo e e 2 8 39 8 5 3 General Matrix Print Utility UTMPRT 0 0000002 e e 8 39 8 5 4 General Relation Print Utility UTRPRT 0 o e 8 39 8 5 5 General Unstructured Print Utility UTUPRT o o o 8 40 8 6 THE eSHELL INTERACTIVE PROGRAM 8 40 9 MAPOL PROGRAMMING 9 1 9 1 INTRODUCTION AND USER OPTIONS o 9 1 941 1 USEROPTIONS Esad A e A A eae Es 9 2 9 1 2 MAPOL PROGRAM FORM o o 9 2 9 1 3 THE STANDARD ASTROS SOLUTION 0 0 o e 9 3 9 1 4 MODIFYING THE STANDARD SOLUTION aoaaa o e o 9 3 9 1 5 CREATING MAPOL PROGRAMS o e 00 00 eee eee ees 9 3 91 05 UMMARYS amp tres 6 dite A e a es Ls ake A 9 4 9 2 DATA TYPES AND DECLARATIONS 9 5 9 2 1 DEFINITIONS AND NOTATION 0 0 0000 a 9 5 9 2
74. M SYM M M l1 l21 122 i 131 132 133 where M p dv i p x5 x dv 122 0 x x3 dv 133 9 x x3 dv 121 p X1 X2 dv 131 p X1 X3 dv 132 Pp X2 X3 dv and Xy X gt X3 are components of distance from the center of gravity in the coordinate system defined in Field 4 The negative signs for the off diagonal terms are supplied by the program A warning message is issued if the inertia matrix is non positive definite as this may cause fatal errors in dynamic analysis modules 4 For design the mass moments of inertia must be zero 5 The TMIN and TMAX values are used only for shape function design variable linking 7 48 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry CONROD CONROD Rod Element Property and Connection Description Defines a rod element of the structural model without reference to a property entry Format and Example 1 2 3 4 5 6 8 9 10 CONROD EID G1 G2 MID A NSM CONT CONT TMIN TMAX CONROD 2 16 17 23 69 Field Contents EID Element identification number Integer gt 0 G1 G2 Grid point identification numbers of connection points Integer gt 0 ID Material identification number Integer gt 0 A Area of rod Real gt 0 0 J Torsional constant Real gt 0 0 C Coefficient for torsional stress determination Real NSM Nonstructural mass per unit length Real TMIN TMAX Mi
75. MANUAL Solution Control Command MODES Description Selects the Normal Modes discipline Hierarchy Level Discipline Format and Examples MODES caseid DCONS n DCFUNCTION o MODES MODES DCONS 10 Option Meaning caseid Case identification number I nteger gt 0 n Set identification of DCONFRO bulk data entries which define frequency con straints for the optimization task o Set identification of DCONF constraint functions Remarks 1 If any discipline has a caseid then all disciplines must have a caseid All caseid values must be unique but they need not be in any particular order Disciplines are implicitly numbered from 1 to n if no caseid values are specified The caseid is only used as a reference from user defined functions in the Function Packet 2 Only one modal analysis can be performed in a boundary condition using the EIGR bulk data entry selected on the BOUNDARY command 5 30 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL OPTIMIZE Solution Control Command OPTIMIZE Description Invokes the ASTROS design capability Hierarchy Level Type of boundary condition Format and Examples OPTIMIZE MINIMIZE STRATEGY m1 niterl m2 niter2 m3 niter3 MAXITER n MAXIMIZE MOVLIM o WINDOW p ALPHA r CNVRGLIM s NRFAC t EPS u FDSTEP v FDSTEP v OBJECTIVE DCFUNCTION x OPTIMIZE OPTIMIZE MAXITER 10 NRFAC 0 6 EPS 05 MOVLIM 1 3 OPTIMIZE STRA
76. Manual This section documents each of the debug options and indicates how the option can be useful in debugging the ASTROS procedure Emphasis is placed on those debug options that are of interest to the general user The debug packet is initiated by the keyword DEBUG which must appear alone on the line of the input stream that follows the last command in the Resource Section and that precedes any other data packet Following the initiator any number of debug lines can be included in the data stream Each debug command line can be composed of a number of debug commands appearing in any order separated by blanks or commas The DEBUG packet is terminated when a new data packet initiator or the end of the input stream is encountered Most debug commands consist of single keywords which toggle flags activating the debug functions The appearance of these debug keywords is all that is required to activate the option Other debug commands select that a flag take on a particular value These commands have the form lt command gt lt value gt There can be any number of blanks between the end of the command keyword the value and the equal sign but neither the command nor the value can contain imbedded blanks Any errors in the DEBUG packet input will result in warnings but will not terminate the execution and the erroneous command will be ignored The tables shown in this section indicate the list of keywords that can be included in the DEBUG p
77. NVEC DYNRED 1 50 0 Field Contents SID Set identification number Integer gt 0 FMAX Highest frequency of interest Hertz Real gt 0 or blank NVEC Number of generalized coordinates desired Integer gt 0 or blank Remarks 1 Dynamic reduction data must be requested in the Solution Control packet with DYNRED SID 2 The user should select either an FMAX or both the FMAX and NVEC fields FMAX should not be greater than necessary for the specific dynamic analysis NVEC if specified should be significantly less than the size of the f set to realize any computational cost savings NVEC will limit dynamic reduction to using NVEC flexible vectors 3 Dynamic reduction transforms the motions of the f set to the motions of the user defined A set plus motions of generalized coordinates created in the process The generalized coordinates represent overall structure displacements which are approximate normal mode shapes The generalized coordi nates are identified by SCALAR points that are automatically generated The SCALAR point identifi cation numbers begin with 1 greater than the highest user GRID SCALAR or EXTRA point identification number ASTROS THE BULK DATA PACKET 7 117 EIGC Input Data Entry EIGC Complex Eigenvalue Extraction Data USER S MANUAL Description Specifies complex eigensolution control data Format a
78. Property identification numbers Integer gt 0 or blank DVSYMi Symbol defining the local design variable Remarks 2 and 3 Remarks 1 The LINKID is referenced by DESVARP data to connect the global design variable to the local vari ables 2 The following symbols may be used for the different types of properties ELEMENTS ALLOWABLE DvsYm VALUES PELAS K PMASS PBAR PROD A PBAR1 D1 D2 D3 D4 D5 D6 D7 D8 DI D10 SHEAR QDMEM1 TRMEM PSHELL T PCOMP PCOMP1 PCOMP2 3 Ifall elements to be linked have only one possible pvsym e g K then the PLIST Bulk Data entry may be used 7 192 THE BULK DATA PACKET ASTROS Input Data Entry PLOAD Static Pressure Load Description Defines a static pressure load on a triangular or quadrilateral surface Format and Examples T 2 3 4 5 6 7 8 9 10 PLOAD SID P G1 G2 G3 G4 PLOAD 1 4 0 16 32 11 Field Contents SID Load set identification number Integer gt 0 P Pressure Real Gi Grid point identification numbers Integer gt 0 G4 may be zero Remarks 1 The grid points define either a triangular or a quadrilateral surface to which a pressure is applied If G4 is zero or blank the surface is assumed to be triangular 2 In the case of a triangular surface the assumed direction of the pressure is computed according to the right hand rule using the sequence of grid points G1 G2 an
79. Py 26 STRESS DISP LIFT AND AILERON EFFECTIVENESS CONSTRAINTS ASTROS ITERATION 2 ANITSYMMETRIC CONDITION NONDIMENSIONAL LATERAL STABILITY DERIVATIVES COMPUTED AT THE AERODYNAMIC REFERENCE GRID AND INCLUDING ANY CONTROL EFFECTIVENESS TRIM IDENTIFICATION 200 REFERENCE GRID 20 REFERENCE AREA 2 4000E 03 REFERENCE SPAN 6 0000E 01 lt lt lt SIDE FORCE gt gt gt lt lt lt ROLLING MOMENT gt gt gt lt lt lt YAWING MOMENT gt gt gt RIGID RIGID FLEXIBLE RIGID RIGID FLEXIBLE RIGID RIGID FLEXIBLE PARAMETER LABEL DIRECT SPLINED DIRECT SPLINED DIRECT SPLINED YAW ANGLE BETA 1 DEG 0000 N A N A 0000 0000 0000 0000 N A N A YAW ANGLE BETA 1 RAD 0000 N A N A 0000 0000 0000 0000 N A N A YAW RATE RRATE S DEG 0000 N A N A 0000 0000 0000 0000 N A N A YAW RATE RRATE S RAD 0000 N A N A 0000 0000 0000 0000 N A N A ROLL RATE PRATE S DEG 0000 N A N A 0418 0418 0510 0002 N A N A ROLL RATE PRATE S RAD 0000 N A N A 2 3951 2 3951 2 9248 0112 N A N A CONTROL SURFACE AILERON 1 DEG 0000 N A N A 0166 0166 0160 0000 N A N A CONTROL SURFACE AILERON 1 RAD 0000 N A N A 9508 9508 9191 0018 N A N A VALUES MARKED N A CANNOT BE COMPUTED UNLESS THE CORRESPONDING DOF IS SUPPORTED TRIM RESULTS FOR TRIM SET 200 OF TYPE ROLL MACH NUMBER 8 00000E 01 DYNAMIC PRESSURE 6 50000E 00 VELOCITY 9 86400E 03 TRIM PARAMETERS DEFINITION LABEL FLEXIBLE RIGID CONTROL SURFACE ROTATION AILERON 1 00000E 00
80. QDMEM1 TRMEM QUAD4 TRIA3 LAYRNUM The layer number of a composite element Integer gt 0 or blank EIDi Element identification numbers Integer gt 0 Remarks 1 Stress constraints are selected in Solution Control with the discipline option STRESS sid 2 If the alternate form is used EID2 must be greater than or equal to EID1 Elements in the range which do not exist are ignored 3 The strain limits for compression xc and Yc are always treated as negative values regardless of the sign of the input values 4 LAYRNUMis only used if the element is composed of a composite material defined with pcomP Bulk Data entries 7 98 THE BULK DATA PACKET ASTROS USER S MANUAL DCONTWM Input Data Entry DCONTWM Tsai Wu Stress Constraint Definition Description Defines Tsai Wu stress constraints by specifying material identification numbers Format and Example 1 2 3 4 5 6 7 8 9 10 DCONTWM SID XT XC YT YC SS F12 MID1 CONT CONT MID2 MID3 MID4 ete gt DCONTWM 100 1 6 6 1 4 1 4 L543 101 ABC BC 102 200 310 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONTWM SID XT XC YT YC ss F12 MID1 CONT CONT THRU MID2 Field Contents SID Stress constraint set identification Integer gt 0 XT Tensile stress limit in the longitudinal direction Real gt 0 0 XC Compressive stress limit in the longitudinal direction Real Default
81. RELATIONAL EXPRESSIONS 0 0 0 e e 9 15 9 3 3 1 Relational Operators ee 9 15 9 3 3 2 Relational Operands 9 16 9 3 3 3 Evaluation of Relational Expressions 02000002 eee 9 16 9 3 4 MATRIX EXPRESSIONS 2 aaa a 9 16 9 3 4 1 Matrix Operators 9 16 9 3 4 2 Matrix Operands and Expressions pee ee ee 9 17 9 3 5 ASSIGNMENT STATEMENTS 0 00 0000 eee ee ee 9 17 9 4 CONTROL STATEMENTS were ai Se Bd E Be ee ae 9 19 9 4 1 INTRODUCTION 0 000 a a a aap a ee 9 19 9 4 2 THE UNCONDITIONAL GOTO STATEMENT 2 200 0202 2s 9 19 9 4 3 ITERATION lt 4 2 gchar x ee cy Qo eS Be a a wt a Eee a Poe ae dha 9 19 9 43 11 The FOR DOLD 120000 ee ae ee Bees Bone Ree te a aes e 9 19 9 4 3 2 The WHILE DOL00p 3 03 ae i ad a BE Reet o td 9 20 9 4 4 THE IF STATEMENT 3 6 ace aoa elas Soe ae ee A EE A A 9 21 9 4 4 1 The LOgiCal Pers as deed chee RP e eh eh OE ade a eh a he 9 21 9 44 25 TNE BIOCKIF vico Wl alee e Bbw hd wee wD el wae 9 22 9 4 4 3 The THEN ELSE scp no Sok eS A ee BE a we A a ai A 9 22 9 4 4 4 Nested IF Statements 0 0 00 9 23 9 4 5 THE END AND ENDP STATEMENTS 000000 eee 9 23 9 5 INPUT OUTPUT STATEMENTS 0 e o 9 23 9 5 1 THE PRINT STATEMENT 000 e 9 23 9 6 PROCEDURES AND FUNCTIONS 204 9 24 9 6 1 INTRODUCTION Su s ioiai a iA a e a a e a A E aE aiad aga
82. ROOT Form ITER b MODE c z SPCF Form FREQ a ITER b MODE c TIME d aa STIF ITER b ab STRA Form FREQ a ITER b MODE c TIME d ah ac STRE Form FREQ a ITER b MODE c TIME d ah ad TPRE ITER b ae VELO Form FREQ a ITER b MODE c TIME d af TRIM PRINT DISP ALL PRINT RECT MODE 10 ITER 20 DISP ITER LAST 6 ENERGY POLA 10 PRINT MODE NONE Options Meaning Form RECT or POLA requests output in RECTangular or POLAr format See Remarks 1 and 2 a Set identification of a FREQLIST bulk data entry that is used to request the frequencies at which output is to be printed See Remark 2 b Set identification of an ITERLIST bulk data entry that is used to request the optimization iterations at which output is to be printed See Remark 2 ASTROS THE SOLUTION CONTROL PACKET 5 33 PRINT USER S MANUAL Set identification of a MODELIST bulk data entry that is used to request the modes at which output is to be printed See Remark 2 Set identification of a TIMELIST bulk data entry that is used to request the times at which output is to be printed See Remark 2 Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which accelerations are to be printed Set identification of an ELEMLIST bulk data entry that is used to request the aerody namic box elements at which displacements for the aerodynamic model are to b
83. Re eo RASS A ey hale See we eae A E 5 14 5 4 2 Response Quantity Options 2 e 5 16 54 3 Forn OPON S ees scsi eo a Soe Bees eed eee oh Te Be ek ims Sa ein Be 5 17 5 4 4 Labeling Options 2 2 sa fe eae hae Dee Bae ed be e ed a a ed 5 17 5 5 SOLUTION CONTROL COMMANDS 20 4 5 17 6 THE FUNCTION PACKET 6 1 6 C BAGCGKGROUND kiei ou eso SR Gee ee A Se a A a i 6 1 6 2 THE FUNCTION EVALUATION PROCEDURE 6 1 6 2 1 Solution Control Packet ee 6 2 6 2 1 1 Synthetic Objective Function o o 6 2 6 2 1 2 Synthetic Design Constraints 2 2 ee e 2 6 3 6 2 2 BulkData Packet sp a a AA a HOLA A GPa SS 6 4 63 FUNCTION SYNTAX s ac oe a O ew a a tea e Sd 6 4 6 3 1 Mathematical Functions 2 2 e o 6 5 6 3 2 Response Functions 2 a oa Ee aya w sa a a Aa r R 6 5 6 3 2 1 Design Variable Function 2 e e areae PR e 6 7 6 3 2 2 Selection Functions y pepu a ann SO we ee he a 6 7 6 3 2 3 Geometric Functions oaoa aaa a ee 6 7 6 3 2 4 Grid Point Response Functions aaa a a 6 9 6 3 2 5 Element Response Functions a aa aa aaa a 6 9 6 3 2 6 Natural Frequency Constraints aoa aaa a 6 11 6 3 2 7 Flutter Response Functions sa csaa rara a ee 6 11 6 3 2 8 Static Aero Response Functions 2 eee ee ee ee 6 12 6 3 3 Ordered Sets i a 6 ee 6 13 G4 EXAMPLES s are d 235 al aca es O
84. Rectangular coordinate system definition Spherical coordinate system definition Extra point definition for dynamics Default parameters for fields on the GRID entry Grid point location and coordinate system selection Scalar point definition 7 5 8 Material Properties MAT MAT al 2 MAT8 MAT9 Isotropic elastic properties definition Two dimensional anisotropic properties definition Orthotropic properties definition Anisotropic properties definition for isoparametric hexahedral elements 7 5 9 Miscellaneous Inputs CONVER DMI T Commentary data Conversion factor definitions Direct matrix input 7 8 THE BULK DATA PACKET ASTROS USER S MANUAL DMIG MFORM SAVE SEQGP Direct matrix input at structural nodes Mass matrix form LUMPED or COUPLED List of database entities not to be purged Structural set resequencing definition 7 5 10 Selection Lists CASELIS DCONLIST DENSLIS HES FREQLIS GDVLIST GPWG GRIDLIST ITERLIS LDVLIST MACHLIST MODELIS PLYLIST TIMELIS VELOLIS List of subcase identification numbers List of design constraint identification numbers List of density ratio values List of element identification numbers List of frequency step values List of global design variable identification numbers Definition of the location to perform grid point w
85. SYM See the AESURF entry for additional information 2 An arbitrary number of entries are allowed 3 TheCONLINK entry may not reference the LABEL of another CONLINK entry ASTROS THE BULK DATA PACKET 7 45 CONM1 Input Data Entry CONM1 USER S MANUAL Concentrated Mass Element Connection General Form Description Defines a 6 x 6 symmetric matrix at a geometric grid point of the structural model Format and Example 1 2 3 4 5 6 7 8 9 10 CONM1 EID G CID M11 M21 M22 M31 M32 CONT CONT 33 M41 M42 M43 M44 M51 M52 M53 CONT CONT 54 M55 M61 M62 M63 M64 M65 M66 CONM1 2 22 2 2 9 64 3 1 1 1 4 8 28 6 2 2 28 6 28 6 Field Contents EID Element identification number Integer gt 0 G Grid point identification number Integer gt 0 CID Coordinate system identification number for the mass matrix Integer gt O or blank Mij Mass matrix values Real Remarks 1 For a less general means of defining concentrated mass at grid points see CONM2 2 Nophysical property in this element can be used as a local design variable for automated design 7 46 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry CONM2 CONM2 Concentrated Mass Element Connection Rigid Body Form Description Defines a concentrated mass at a grid point of the structural model
86. THN3 PAERO2 2 Z 6 0 1 0 22 91 100 abc tbe 1 3 Field Contents PID Property identification number Integer gt 0 ORIENT Orientation flag z Y or zy Type of motion allowed for bodies Character Refers to the aerodynamic coordinate system y and z directions see AERO data entry WIDTH Reference half width of body Real gt 0 0 AR Aspect ratio height width Real gt 0 0 LRSB Identification number of an AEFACT data entry containing a list of slender body half widths If blank the value of WIDTH will be used Integer gt 0 or blank LRIB Identification number of an AEFACT data entry containing a list of interference body half widths If blank the value of WIDTH will be used Integer gt 0 or blank LTH1 LTH2 Identification number of AEFACT data entries for defining theta arrays for interfer ence calculations Integer gt 0 THIi THNi The first and last interference element of a body to use the 9i array Integer gt 0 Remarks 1 The EID of all CAERO2 elements in any IGID group must be ordered so that their corresponding ORIENT values appear in the order Z ZY Y 2 The half widths given on AEFACT data entries referenced in fields 6 and 7 are specified at division points The number of entries on an AEFACT data entry used to specify half widths must be one greater than the number of elements 3 The half width at the first point i e the nose on a slender body is usually 0 thus it is recom mended but not
87. USER S MANUAL Input Data Entry Description RLOAD1 RLOAD1 Defines a frequency dependent dynamic load of the form P f A CA iD A 2 Format and Examples 1 2 3 4 5 6 7 8 9 10 RLOAD1 SID DLAGID TC TD RLOAD1 10 3 1 2 Field Contents SID Set identification number Integer gt 0 DLAGID Identification number of a DLAGS set which defines A 0 and t Integer gt 0 TC Set identification number of TABLEDi entry which gives C f Integer gt 0 TC TD gt 0 TD Set identification number of TABLEDi entry which gives D f Integer gt 0 TC TD gt 0 Remarks 1 RLOAD1 loads may be combined with RLOAD2 loads only by specification on a DLOAD entry 2 SID must be unique for all RLOAD1 RLOAD2 TLOAD1 and TLOAD2 entries ASTROS THE BULK DATA PACKET 7 209 RLOAD2 USER S MANUAL Input Data Entry RLOAD2 Description Defines a frequency dependent dynamic load of the form Format and Examples 1 2 3 4 5 6 7 8 9 10 RLOAD2 SID DLAGID TB TP RLOAD2 10 6 100 101 Field Contents SID Set identification number Integer gt 0 DLAGID Identification of a DLAGS entry which defines A 8 and 1 I nteger gt 0 TB Set identification number of TABLEDi entry which gives B f Integer gt 0 TP Set identification number of TABLEDi entry which gives f in degrees Integer gt 0 Remarks 1 RLOAD2 loads ma
88. When editing the standard sequence you are cautioned to obtain the most recent listing either from the SYSGEN output or by executing ASTROS with an input stream containing only an ASSIGN command and the one line MAPOL packet EDIT LIST NOGO This input stream will result in an output file containing the current listing of the standard executive sequence 4 3 THE STANDARD EXECUTIVE SEQUENCE As previously mentioned the MAPOL language has its conceptual roots in the DMAP language In order to allow the user of NASTRAN to perform certain predefined analyses a set of rigid formats or DMAP algorithms were written alleviating the user of the need to learn the details of the control language Each rigid format allowed the user to perform analyses in a different engineering discipline for example static structural analyses normal modes analyses or transient analyses In a similar manner a standard executive sequence or MAPOL algorithm is available in the ASTROS system which supports all Table 4 1 MAPOL Edit Commands STATEMENT FUNCTION EDIT Modify the standard solution DELETE a b Remove lines a through b inclusive Removes lines a through b inclusive and replaces them REPLACE a b with the following lines INSERT a Insert the lines following the command after line a ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 3 USER S MANUAL the engineering disciplines and optimization features of the
89. X direction The general expression for the Function packet is VALUE SIGX for elements 5 10 15 20 which is defined by the Function packet ASTROS THE FUNCTION PACKET 6 23 USER S MANUAL FUNCTIONS Constraint for Eleme VALUE ELIST STRE EL ELIST SIGX 45000 0 1 0 ENDFUNC The Bulk Data Packet defines design constraint 101 which referenced the design constraint function VALUE BEGIN BULK ELEMLIST 1 5 10 15 20 DCONF 101 VALUE DCN1 DCN1 GLIST 1 ENDDATA No constraints will be generated because there is no definition in the pconr bulk data entry for the element list argument Example 9 Modified Flutter Damping Constraint The following example will compute 32 constraints on the critical damping ratio for mach values of 0 8 and 1 2 density ratio values of 0 8 and 1 0 mode index list of 1 and 2 and a velocity list from 600 0 through 1000 0 The solution control packet references the functional design constraint 101 in the Bulk Data Packet for the FLUTTER discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC FLUTTER DCFUNCTION 101 END The Function Packet defines the function specification for computing the constraint values for The general expression for the Function packet is 2 Y Re p j a mo Re p where p is the
90. Y 0 plane ANTISYNMETRIC Specifies that the SAERO subcase is to use aerodynamics derived with antisymmetric conditions about the Y 0 plane The case identification number caseid is only used by the Function Packet see Section 4 when user defined constraint functions are defined which span two or more different analysis disciplines Note that all disciplines must have identification numbers or none may have them User functions may still span disciplines by using default caseid values The default is the ordinal numbering of the disciplines from 1ton Table 5 3 presents a matrix that defines options and types available for each of the disciplines In addition disciplines requiring particular boundary condition specifications are noted for example modal disciplines require a METHOD specification on the BOUNDARY command The following subsections present each discipline in turn to more explicitly define the discipline options Most importantly these subsec tions present the definition of a subcase of the discipline as it is defined in the ASTROS system and present the response quantities that can be constrained in the optimization task 5 10 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL Table 5 3 Summary of Discipline Options COMMAND DISCIPLINE STAT MODE SAER FLUT TRAN FREQ MECH O GRAV O THERM O TRIM DCONSTRAINT DCFUNCTION STRESS O O JO O O O O JO O O
91. a reference from user defined functions in the F unction Packet The FREQUENCY discipline does not generate design constraints for optimization type DLOAD and FSTEP are required No more than one FREQUENCY analysis can be done in a single boundary condition uF WN M2PP B2PP and K2PP names will typically refer to DMI and DMIG entries but may refer to any existing database entity of the proper dimension ASTROS THE SOLUTION CONTROL PACKET 5 27 K6ROT USER S MANUAL Solution Control Command K6ROT Description Provides a stiffness value for in plane stiffnesses for plate elements Hierarchy Level Initial level above ANALYZE OPTIMIZE Format and Examples K6ROT val K6ROT 1 0 K6ROT 10 0E3 Option Meaning val Real value used to compute the stiffness associated with the in plane rotations of plate elements Default K6ROT 0 0 K6ROT gt 0 0 5 28 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL LABEL Solution Control Command LABEL Description Provides identifying information on subcase output Hierarchy Level Label information Format and Examples LABEL n LABEL SYMMETRIC MANEUVER LOAD Option Meaning n Any descriptive message that the user wishes to use to distinquish output Remarks 1 LABEL information is used until it is superseded 2 The LABEL command is optional 3 Labels are limited to no more than 72 characters ASTROS THE SOLUTION CONTROL PACKET 5 29 MODES USER S
92. a W a k o ah 9 24 9 6 2 PROGRAM UNITS AND SCOPE OF VARIABLES aahua aaa aaa 9 24 9 6 3 DEFINING A PROCEDURE 00000 eee ee 9 25 9 6 4 INVOKING A PROCEDURE 0000 0 ee ee 9 26 vi ASTROS USER S MANUAL 9 6 5 FUNCTION PROCEDURES 00 0000 eee es 9 26 9 6 5 1 Examples of Variable Scope o eee ee 9 27 9 6 6 INTRINSIC FUNCTION PROCEDURES AND INTRINSIC PROCEDURES 9 27 9 6 7 INTRINSIC MATHEMATICAL FUNCTIONS 02 0002220 9 27 9 6 8 INTRINSIC RELATIONAL PROCEDURES 2 0 00 20004 9 28 9 6 9 GENERAL INTRINSIC PROCEDURES 0 0000550048 9 28 10 REFERENCES ASTROS vii USER S MANUAL This pageis intentionally blank viii ASTROS USER S MANUAL LIST OF FIGURES Figure 3 1 Structure of the ASTROS Input Data Stream 3 2 Figure 3 2 Features of a Sample ASTROS Input Stream 3 3 Figure 3 3 Function of the ASSIGN Command 4 4 3 7 Figure 4 1 Structure of the Standard MAPOL Sequence 4 5 Figure 7 1 Bulk Data Entry Formats e 2 7 3 Figure 8 1 BAR Element Coordinate System o 8 11 Figure 8 2 BAR Element Forces Sign Conventions 0 8 11 Figure 8 3 IHEX1 Element Geometry 0 e 8 14 Figure 8 4 IHEX2 Element Geometry o o e 8 15 Fig
93. a second example you may suspend execution and again using eSHELL replace ASTROS computed data with their external equivalent such as the QHHL or QKKL matrices of unsteady aerodynamic influence coeffi cients Clearly the ability to suspend restart executions in combination with the eSHELL environment opens limitless possibilities Without an automated restart however you are responsible for ensuring that several requisite tasks are completed These are gt Ensuring that the run time database has the proper STATUS on suspension and on restart Selecting wherein the MAPOL sequence to suspend execution i Writinga MAPOL sequencetorestart execution This may or may not be a modification tothe standard sequence fi Ensuring that those scalar variable s that are common to both the original and the restart MAPOL sequences are initialized to the correct value s Each of these tasks are discussed in the following sections 4 4 4 1 Ensuring proper STATUS of the run time database When suspending execution the run time database must be saved ASTROS stores all the information that it has generated during the execution on the run time database and on any restart the downstream modules will expect that those data will exist when they are executed in the restart environment The run time database is also the location of the data that the user may wish to modify or add to using eSHELL prior to initiating the restart Saving the run time
94. a zero participation factor will be shown for normal modes that the user omitted from the flutter analysis Table 8 20 Flutter Solution Results 1 ASTROS VERSION 9 0 03 03 93 P 20 ASTROS ITERATION 4 SUMMAR Y OF P K FLUTTER EVALUATION MODE 1 MACH NUMBER 8000 DENSITY RATIO 1 0000E 00 VEL TYPE CONSTRAINT VELOCITY DAMP ING FREQUENCY COMPLEX EIGENVALUE NO COUNT VALUE EQUIVALENT TRUE RATIO CYC SEC RAD SEC REAL IMAGINARY 1 1 1 890E 00 1 01150E 04 1 01150E 04 3 78041E 01 2 28032E 01 1 43276E 02 6 42583E 02 3 39954E 01 2 7 1 008E 01 1 51725E 04 1 51725E 04 2 01653E 00 2 49806E 01 1 56958E 02 2 50330E 01 2 48278E 01 3 13 2 202E 00 1 71955E 04 1 71955E 04 4 40401E 01 0 00000E 00 0 00000E 00 1 52631E 01 5 78939E 08 4 19 1 711E 00 1 82070E 04 1 82070E 04 3 42128E 01 0 00000E 00 0 00000E 00 1 18573E 01 2 59419E 11 5 25 1 536E 00 1 87128E 04 1 87128E 04 3 07225E 01 0 00000E 00 0 00000E 00 1 06476E 01 1 89918E 14 MODE 2 MACH NUMBER 8000 DENSITY RATIO 1 0000E 00 VEL TYPE CONSTRAINT VELOCITY DAMP ING FREQUENCY COMPLEX EIGENVALUE NO COUNT VALUE EQUIVALENT TRUE RATIO CYC SEC RAD SEC REAL IMAGINARY 1 2 2 292E 00 1 01150E 04 1 01150E 04 4 58386E 01 4 39390E 01 2 76077E 02 1 50133E 01 6 55051E 01 2 8 1 017E 00 1 51725E 04 1 51725E 04 2 03466E 01 2 88941E 01 1 81547E 02 2 92149E 02 2 87173E 01 3 14 3 128E 01 1 71955E 04 1 71955E 04 6 25583E 02 2 99157E 01 1 87966E 02 8 20597E 03 2 62346E 01 4 20 2 659E 02 1 82070E 04 1 82070E
95. addition if the flutter analyses appear in the ANALYZE subpacket of the solution control packet the modal participation factors of any flutter conditions will be printed The roots are ordered such that the lowest frequency root at each velocity is associated with the lowest frequency normal mode and so on in increasing frequency order For each normal mode the corresponding velocity value damping ratio frequency and complex eigenvalue are shown For OPTIMIZE flutter analyses only the user s input velocities are used in the root extraction algorithm ANALYZE flutter analyses may generate additional velocities in the process of converging to a flutter crossing Further OPTIMIZE flutter analyses assume that constraints are imposed and print out the TYPE COUNT and CONSTRAINT VALUE as shown in Table 8 20 These columns do not appear for analysis cases The complex modal participation factors for each of the normal modes in the modal representation of the structure are printed if the ROOTS PRINT option is selected in ANALYZE flutter disciplines and a flutter crossing is found A flutter crossing can occur for each Mach number and density ratio combination in the flutter analysis Therefore the flutter condition is identified by velocity Mach number and density ratio to distinguish among multiple flutter conditions in the same analysis An example is given in Table 8 21 in which the INDEX is the normal mode and REAL IMAG are the complex factor Note that
96. an AEFACT data entry containing a list of division points for chord wise boxes Used only if NCHORD is zero or blank Integer gt O or blank IGID Interference group identification aerodynamic elements with different IGIDs are uncoupled Integer gt 0 XL YL 21 Location of points 1 and 4 in coordinate system cP Real X4 Y4 24 X12 X43 Edge chord lengths in aerodynamic coordinate system Real gt 0 and not both zero Remarks 1 The boxes are numbered sequentially beginning with EID 2 Thecontinuation entry is required 3 The number of division points is one greater than the number of boxes Thus if NSPAN 3 the division points are 0 0 0 333 0 667 1 000 If the user supplies division points the first and last points need not be 0 and 1 in which the corners to the panel would not be at the reference points 4 Atriangular element is formed if x12 or x43 0 0 7 28 THE BULK DATA PACKET ASTROS USER S MANUAL CAERO1 5 The element coordinate system right handed is shown in the sketch below Y elem X aero X elem ASTROS THE BULK DATA PACKET 7 29 CAERO2 Input Data Entry USER S MANUAL CAERO2 Unsteady Aerodynamic Body Connection Description Defines an aerodynamic body for Doublet L attice aerodynamics Format and Examples 1 2 3 4 5 6 7 8 9 10 CAERO2 EID PID CP NSB NINT LSB LINT IGID CONT BC xi Y1 Z1 X12 CA
97. analysis When defining functional constraints which are subcase dependent a similar DCFUNCTION option is included within each discipline lt disc gt lt type gt lt case_id gt DCFUNCTION set id where set idis the identification number of one or more DCONF Bulk Data entries For example OPTIMIZE DCFUNCTION 1000 Subcaselndependent Functional Contraint BOUNDARY SPC 1 STATICS DCFUNCTION 101 Subcase Dependent Functional Contraint BOUNDARY SPC 2 METHOD 10 MODES DCFUNCTION 201 Subcase Dependent Functional Contraint ASTROS THE FUNCTION PACKET 6 3 USER S MANUAL An additional option is available for each of the ASTROS discipline commands Each discipline may include an identification number case id which can be used in selecting response quantities for user functions This identification number simply follows the discipline name If case ids are not specified then they are numbered consecutively from 1 to n If case ids are specified then they must appear for all discipline commands In a typical case the case id associated with a constrained response will be inherited from the discipline that references the function It is possible however to explicitly reference a case id in a user function You use this feature to create synthetic functions that combine results from many subcases 6 2 2 Bulk Data Packet The calling arguments that instantiate functional
98. anywhere in the MAPOL sequence after the specified entity has been filled with data The USETPRT utility provides the user with the ability to print the structural set definition table USET ina format which aids in debugging the structural model These utilities provide the user with some simple tools to allow closer interaction with the data stored on the database and to provide capability to more closely track the execution The print utilities provide data visibility without modifying the basic execution of the standard sequence At a slightly more complex level the user might desire to fine tune the optimization procedure or to track the iterations of the optimizer more closely Table 4 4 includes a number of parameters which are used by ASTROS to direct the optimization All of these parameters can be modified through the OPTIMIZE command in solution control That modification however only occurs once Any of these parameters can be changed by the user at any point in the MAPOL sequence For example the MOVLIM parameter could be changed to a different value after the fifth iteration by placing the following statement immediately after the WHILE test on GLBCNVRG IF NITER gt 5 MOVLIM 1 5 Obviously the conditional testing can become as complex as the MAPOL programmer desires The brief discussion above does not begin to describe all the options open to the sophisticated ASTROS user It does however outline some of the most commonly
99. appear in the MAPOL program It must however be declared so that the CADDB will be properly initialized The last entity type the TEMPORARY entity is used mostly as a scratch area for intra module use As such it is created and deleted by the module needing it In summary all of the MAPOL and HIDDEN entities must be declared in the MAPOL program TEMPORARY entities are not declared 9 3 EXPRESSIONS AND ASSIGNMENTS In this section the relationships between the various data types are described Of particular importance is the manner in which data are combined by arithmetic expressions and how values are assigned to the ASTROS machine memory 9 3 1 ARITHMETIC EXPRESSIONS Arithmetic expressions are formulae for computing numeric values An arithmetic expression consists of either a single operand or two or more operands separated by arithmetic operators 9 3 1 1 Arithmetic Operators MAPOL supports five arithmetic operators as shown in Table 9 3 Successive operands must be sepa rated by operators and two operators may not be used in succession 9 3 1 2 Arithmetic Operands Arithmetic operands may be constants symbolic names of constants variables including relational attributes array elements or function references Operands may also be arithmetic expressions and arithmetic expressions enclosed in parentheses The data type of an arithmetic operand may be INTEGER REAL Or COMPLEX n some cases it may also be MATRIX Or IMAT
100. are local to the main program and cannot be used by either procedure Variables may be global to all PRocs or local to the main program All proc definitions must appear contiguously in the program with no intervening declarations 9 6 6 INTRINSIC FUNCTION PROCEDURES AND INTRINSIC PROCEDURES In addition to the user defined procedures and functions within a MAPOL main program unit MAPOL provides a set of predefined functions and procedures to perform certain tasks in a similar manner to other high level languages such as Fortran These intrinsic procedures are in addition to the engineering modules defined as part of the ASTROS system generation process The set of intrinsic procedures within the MAPOL language can be broken into three groups intrinsic mathematical functions intrinsic rela tional procedures and general intrinsic procedures Each group is discussed separately in the following sections 9 6 7 INTRINSIC MATHEMATICAL FUNCTIONS Table 57 shows the list of intrinsic mathematical functions available in MAPOL These functions make up the mathematical function library within the MAPOL language and provide the user with the capacity ASTROS MAPOL PROGRAMMING 9 27 USER S MANUAL to perform a wide variety of tasks within the MAPOL program units With very few exceptions the MAPOL mathematical functions are identical in form to those in the Fortran language the exceptions are noted in Table 9 10 Trigonometric functions in MAPOL use
101. automated design 7 38 THE BULK DATA PACKET ASTROS Input Data E ntry CIHEX3 Cubic soparametric H exahedron Element Connection Description Defines a cubic isoparametric hexahedron element of the structural model Format and Example 1 2 3 4 5 6 7 8 9 CIHEX1 EID PID G1 G2 G3 G4 G5 G6 CONT CONT G7 G8 G9 G10 G11 G12 G13 G14 CONI CONT G15 G16 G17 G18 G19 G20 G21 G22 CONI CONT G23 G24 G25 G26 G27 G28 G29 G30 CONT CONT G31 G32 CIHEX1 15 3 4 9 12 17 18 19 ABC BC 20 13 10 7 6 5 22 25 DEF EF 31 32 33 28 25 24 108 214 GHI HI 106 213 413 95 67 40 45 90 KL KL 38 3H Field Contents EID Element identification number Integer gt 0 PID Identification number of a PIHEX property entry Integer gt 0 Default is EID Gi Grid point identification number of connection points Integer gt 0 G1 G2 G32 G7 G15 G10 G25 G24 G12 G1 G13 G17 G21 CIHEX3 USER S MANUAL Remarks 1 Au FW DN Grid points G1 612 must be given in counterclockwise order about one quadrilateral face when viewed from inside the element G13 616 G17 G20 and G21 G32 must also be in a counter clockwise direction with G1 G13 G17 and G21 along the same edge as shown in the previous figure There is no nonstructural mass The quadrilateral faces need not be planar Stresses are given in the basic coordina
102. block the required matrix partitions and reductions are performed Once the reduced matrices have been obtained for the analyses being performed within the loop the lowest level response quantities e g displacements eigenvalues etc are computed Following the solution the execution proceeds through another group of dependent set BLOCK IF s to recover the solution vectors to the global set At this point the analysis segment is completed with calls to the output file processor modules to compute and output high level response quantities e g stresses In the optimization phase of the optimization segment the AcTcON module determines the status of the global convergence flag CONVERGE and if the optimization is not complete the redesign task is per ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 19 USER S MANUAL formed Three redesign methods are supported by the standard sequence and selected through the Solution Control If the option for Fully Stressed Design FSD is selected the redesign is performed in the FSD modules The mathematical programming method only requires sensitivity information In this case the sensitivities of the active constraints chosen by ACTCON based on the NRFAC and EPS parame ters are computed The sensitivities of the active constraints which are explicit functions of the design variables are com puted first in the MAKDFv module Then the second boundary condition loop within the optimization segment beg
103. by a stress or strain point ID The stress and strain point IDs are numbered 1 through 9 with the first eight ordered as on the associated CIHEX1 input data entry and the ninth located at the element center as illustrated in Figure 8 3 All output is provided in the basic coordinate system since there is no naturally occurring element coordi nate system for the IHEX1 An example of the output for the IHEX family of elements is shown in Table 8 11 The IHEX1 element is shown with the HEX2 and I HEX3 elements differing only in the number of data recovery points ASTROS OUTPUT FEATURES 8 13 Strain energy output may be requested for the HEX1 element The strain energy print for the IHEX1 is identical to that for the BAR element and includes a breakdown by element and by element type Table 8 11 IHEX1 Element Solution Quantities STRESSES IN 8 NODED SOLID ELEMENT EREK de ELEMENT STRESS CENTER AND CORNER POINT STRESSES DIRECTION COSINES MEAN OCTAHEDRAL ID POINT NORMAL SHEAR PRINCIPAL A B Cc STRESS SHEAR STRESS 123 1 X 7 617902E 01 XY 2 852164E 01 A 6 942204E 00 LX 92 85 00 4 715845E 01 4 009525E 01 Y 3 264816E 01 YZ 0 000000E 00 B 1 018850E 02 LY 58 35 74 Z 3 264816E 01 ZX 3 108560E 01 C 3 264816E 01 LZ 63 38 68 123 2 X 7 238755E 01 XY 2 909098E 01 A 1 015376E 02 LX 84 54 00 4 481134E 01 4 183963E 01 Y 3 102324E 01 YZ 0 000000E 00 B 1 873196E 00 LY 35 54 17 Z 3 102324E 01 ZX 3 477372E 01
104. constants or expressions 6 6 THE FUNCTION PACKET USER S MANUAL USER S MANUAL 6 3 2 1 Design Variable Function To specify the current value of a design variable the function ov avrat esa is used where the design variable is specified in the Bulk Data Packet as an identification dvid or as a set GDVLIST 6 3 2 2 Selection Functions Selection functions are provided to aid in the reference of data items such as grid or element identifica tions The data items may be referenced by either individual data entries through the definition of values passed in the DCONF argument list or by data lists through the passing of a list defined in the Bulk Data packet The functions that represent data lists are shown in Table 6 2 along with the Bulk Data entries which define the set lists The argument represents a list sid defined by the parameters in DCONF Bulk Data 6 3 2 3 Geometric Functions Geometric functions are provided to facilitate the eventual definition of geometry based design variable linking and to define kinematic admissibility constraints The first function is Table 6 2 Selection Functions SELECTION FUNCTION BULK DATA ENTRY DESCRIPTION CASELIST sid CASELIST Case List DENSLIST sid DENSLIST Density List ELEMLIST sid ELEMLIST Element List GDVLIST sid GDVLIST Global design variable List GRIDLIST sid GRIDLIST Grid List ITERLIST sid
105. convergence has been reached K2GGFLG MK2GG Set TRUE in MK2GG if a K2GG matrix is input for the current boundary condition LOOP General logical used to control DO WHILE loops M2GGFLG MK2GG Set TRUE in MK2GG if an M2GG matrix is input for the current boundary condition PFLAG ACTCON Set TRUE in ACTCON if DESPUNCH needs to punch a new model DESPUNCH ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 11 USER S MANUAL 4 4 2 The Solution Algorithm Finite element structural analysis which forms the core of the ASTROS system requires the manipula tion of large matrices The MAPOL control language is designed with this requirement in mind and therefore is able to directly support the manipulation of matrices Consequently the majority of the MAPOL sequence consists of matrix equations The algorithmic nature of the MAPOL syntax allows the reader to follow these matrix operations fairly easily and the notation roughly follows that used in the Theoretical Manual Therefore the focus of this section is the description of modules called by the MAPOL sequence There are a number of engineering and utility modules called to perform tasks associated with the several analysis disciplines supported by the ASTROS system Table 4 8 of Section 4 4 2 1 lists the modules defined to the ASTROS executive system and provides a brief description of each Not all of these modules appear in the standard solution sequence These are included in
106. coordinate systems whose definition does not involve the coordinate system being defined The first point is the origin the second lies on the z axis and the third lies in the plane of the azimuthal origin Format and Example I 2 3 4 5 6 7 8 9 10 CORD1C CID G1 G2 G3 CID G1 G2 G3 CORD1C 3 16 32 19 Field Contents CID Coordinate system identification number Integer gt 0 Gi Grid point identification number Integer gt 0 G1 G2 G3 y Remarks 1 Coordinate system identification numbers on all CORD1R CORD1C CORD1S CORD2R CORD2C and CORD2s entries must be unique 2 Thethree points G1 G2 and G3 must be noncollinear 3 The location of a grid point P in the sketch in this coordinate system is given by R 0 Z where 9 is measured in degrees 4 The displacement coordinate directions at P are dependent on the location of P as shown above by u Ug Uz 5 Points on the z axis may not have their displacement directions defined in this coordinate system since an ambiguity results 6 One or two coordinate systems may be defined on a single entry ASTROS THE BULK DATA PACKET 7 51 CORD1R Input Data Entry Description CORD1R Rectangular Coordinate System Definition Form 1 USER S MANUAL Defines a rectangular coordinate system by reference to three grid points These points must be defined in coordinate systems whose definition does not in
107. discipline of boundary condition 1 OPTIMIZE DCFUNCTION 10 BOUNDARY SPC STATICS 100 STATICS 200 STATICS 300 STATICS 400 STATICS 500 The Function Packet defines the function specification for computing the allowable displacement compo nent T3 The general expression for the function is grid 5 recovered at subcase 1000 grid 10 recoveredat subcase 2000 COMP 35 for grid 15 recovered at subcase 3000 i grid 20 recovered at subcase4000 grid 25 recovered at subcase 5000 which is defined by the Function packet FUNCTIONS Recover the Normalized Displacement component T3 for given grid and subcase list COMP GLIST CLIST FACT DISP GRIDLIST GLIST T3 CASELIST CLIST FACT Constraint for the displacement component CONST GLIST CLIST ALLOW COMP GLIST CLIST 2 0 ALLOW 1 0 ENDFUNC The Bulk Data Packet defines a grid list and a subcase list references design constraint 101 which links the design variable const to the Functional Packet and defines three arguments The first argument represents the GRIDLIST identification the second argument is the CASELIST identification and the third argument defines the allowable upper limit of the constraint ASTROS THE FUNCTION PACKET 6 19 USER S MANUAL BEGIN BULK GRIDLIST 1 5 10 15 20 25 CASELIST 101 1000 2000 3000 4000 5000 DCONF 101 CONST DCN1 DCN1 G
108. discipline option y DCON sid 2 The buckling control element which must be a de signed element supplies the running loads Nx Ny and Nxy and material properties to the rectangular pseudo panel of dimension LENGTH x WIDTH ex 3 If LENGTH or WIDTH are omitted the corresponding value will be computed from the rectangle that cir cumscribes the control element LENGTH is defined as the side most closely associated with the element x axis as shown in the adjoining figure LENGTH 7 68 THE BULK DATA PACKET ASTROS USER S MANUAL DCONBKE Input Data Entry DCONBKE Euler Buckling Constraint Definition Description Defines an Euler buckling constraint of the form Lower Bound glowe ES 1 0 lt 0 0 for A gt AreQ or Upper Bound g uppe 1 0 a lt 0 0 for A lt AREQ Format and Example T 2 3 4 5 6 7 8 9 10 DCONBKE SID ETYPE EID LENGTH BCTYPE CTYPE REO CONT CONT RSOR ALPHA DCONBKE 25 BAR 101 1 5 FIX FIX LOWER 3 65 Field Contents SID Euler buckling constraint set identification I nteger gt 0 ETYPE Euler buckling control element type Character selected from BAR ROD EID Control element identification number Integer gt 0 LENGTH Rod buckling length in consistant length units Real gt 0 0 or blank See Remark 2 BCTYPE Boundary conditions for control element Character See Re
109. division points defining prism containing set 1 01 gt Real gt 0 01 ZMAX ZMIN Z coordinates of top and bottom using right hand rule with the order of the corners as listed on a CAEROi entry of the prism containing set Real Usually ZMAX gt 0 0 ZMIN lt 0 0 Remarks 1 These entries are referenced by the SPLINE1 data entries 2 Every grid point within the defined prism and within the height range will be in the set For example The shaded area in the figure defines the cross section of the prism for the sample data given above Points exactly on the boundary may be missed hence to get all the grid points within the area of the macro element use sP1 0 01 SP2 1 01 etc 3 Azerovalue for ZMAX or ZMIN implies infinity is to be used ASTROS THE BULK DATA PACKET 7 215 SHAPE USER S MANUAL Input Data Entry SHAPE Description Defines element connectivity entries associated with a design variable Format and Examples 1 2 3 4 5 6 7 8 9 10 SHAPE SHAPEID ETYPE EID1 PREF1 EID2 PREF2 EID3 PREF3 CONT CONT EID4 PREF4 EID5 PREF5 etc SHAPE 10 CROD 12 12 0 22 1 0 Field Contents SID Shape function identification number Integer gt 0 ETYPE Character input identifying the element type One of the following CELASi CMASSi CONM2 CBAR CROD CONROD CSHEAR CODMEM1 CTRMEM CQUA
110. either LAYRNUM or LAYRLST must be given Noncomposite elements must be called out on DCONTHK entries The purpose of this bulk data list is to ensure that adequate physical move limits are retained in optimization with shape function design variable linking without requiring retention of all move limits For problems with large numbers of local variables using shape functions the move limits often cause too many minimum thickness constraints see Remark 3 to be retained in the optimiza tion task Using this bulk data entry or its noncomposite counterpart DCONTHK to name critical minimum gauge constraints see Remark 4 will cause only the named elements thickness con straints to be computed and retained All layers of composite elements named on DCONTHK will be retained Note that all thickness constraints for an element will always be computed irrespective of the DCONTHK entries but may be deleted in the constraint deletion The global design variable in shape function linking is non physical and no reasonable restriction for a global variable move limit side constraint can be defined Therefore constraints on the local design variables controlled by shape functions are generated by ASTROS to ensure that the design is reasonable ie nonnegative thicknesses ASTROS THE BULK DATA PACKET 7 93 DCONTH2 USER S MANUAL 4 TheDCONTH2 entry should select a minimum number of elements linked to shape functions that will enable the optimize
111. following example computes for a mach value of 0 8 a density value of 0 8 a mode index of 1 and a velocity of 600 0 2 Y C fers Re p 2 where p is the complex flutter eigenvalue Im p ASTROS USER S MANUAL DCONF The solution control packet references the functional design constraint 101 in the Bulk Data Packet for the FLUTTER discipline of boundary condition 1 ANALYZE BOUNDARY SPC 1 FLUTTER DCFUNCTION 101 END The Function Packet defines the function specification for computing the design constraint gt 0 15 FUNCTIONS ZETA mach dens mode velo 1 0 FDAMP ZETA mach dens mode velo 0 15 ENDFUNC The Bulk Data Packet defines values for the MACH DENS MODE and VELO arguments for function design constraint 101 which points to the function ZETA in the Functional Packet BEGIN BULK DCONF 101 ZETA DCN1 DCN1 MACH 0 8 DENS 0 8 MODE 1 VELO 600 0 ENDDATA 2 ARGi and VALi must be defined together They represent by name the substitution parameters for the function FNAME The following example computes the normal stress in the element s X direction for element 1 The Function Packet defines the function specification for recovering the allowable normal stress in the element s X direction FUNCTIONS VALUE eid allow STRESS eid SIGX allow 1 0 ENDFUNC The Bulk Data Packet defines the element identification and references design constraint 101 wh
112. function contribution is in the direction of these coordinate axes x0 The x coordinate in the basic system of the new origin for shape generation Real YO The y coordinate in the basic system of the new origin for shape generation Real 20 The z coordinate in the basic system of the new origin for shape generation Real DVSYMBL Character symbol specifying the PBAR1 cross sectional parameter if ETYPE iS PBAR D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 Remarks 1 SHAPEID is referenced by a DESVARS Bulk Data entry which defines the shape used for the global variable 2 Toprint or punch the resulting SHAPE or SHAPEM entries you may use the DEBUG Command SHPGEN 3 The SHAPE is a character string that consists of one two or three digits The first digit specifies the order of the contribution to the shape of the basic x coordinate of the element centroid The second and third digits represent the same data for the y coordinate and z coordinate of the centroid respectively The value of each digit may vary from O to 9 which represents the order of the shape term as 2 2 3 232 indicates to use the terms x x i o i 2 2 4 The shape function contributions are about the specified point in the basic coordinate system unless you specify a CID Then the contributions are relative to this system 7 218 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry SPC SPC Single Point Constraint
113. grid points at which accelerations are to be punched Set identification of an ELEMLIST bulk data entry that is used to request the aerodynamic box elements at which displacements for the aerodynamic model are to be punched Set identification of an DCONLIST bulk data entry that is used to request the the subset of active constraints for which gradients are to be punched See Remark 2 Set identification of an DCONLIST bulk data entry that is used to request the the subset of active constraints which are to be punched See Remark 2 Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which displacements are to be punched Set identification of an ELEMLIST bulk data entry that is used to request the elements for which strain energies are to be punched Set identification of an ELEMLIST bulk data entry that is used to request the elements for which forces are to be punched Set identification of a GDVLIST bulk data entry that is used to request the global design variable IDs for which global design variables are to be punched Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which grid point forces are to be punched Either ALL or NONE depending on whether the Gpwe is to be computed punched If a GPWG entry is in the Bulk Data file it will be used by the algorithm Set identification of an LDVLIST and or a GDVLIST bulk data entry that is used to reque
114. grid points GMi which are ASTROS placed in the m set Indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 or blank Remark 2 THE BULK DATA PACKET 7 207 RBE3 USER S MANUAL Remarks 1 The RBE3 entry is selected in the Solution Control with the MPC SETID option of the BOUNDARY command THIS IS AN ENHANCEMENT TO THE NASTRAN METHOD WHICH DOES NOT ALLOW RIGID CONNECTIONS TO BE CHANGED FOR DIFFERENT BOUNDARY CONDI TIONS 2 The form of Gi j is different than NASTRAN The first data field on the continuations has been reserved for the um identifier The Gi j list must be contained within data fields 3 through 9 Blanks may appear anywhere in the list 3 The default for um should be used except in cases where the user wishes to include some or all of the REFC components in displacement sets other that the m set If the default is not used for UM then the total number of components in UM must equal the number of components in REFC the components in UM must be a subset of the components specified in the REFG REFC and Gi 3 Ci the m set coefficient matrix in the constraint equation must be nonsingular 4 Them set degrees of freedom specified on this entry may not be specified on other entries that define mutually exclusive sets 5 Rigid element identification numbers must be unique within each element type for each Mpc set identification number 7 208 THE BULK DATA PACKET ASTROS
115. gt RELATION lt rel list gt lt rel list gt lt rel list gt lt rel var gt lt rel var gt lt rel var gt lt ident gt If the user wishes to use the individual attributes of a relation or to define a new relation the PROJECT declaration is used lt decl gt PROJECT lt rel var gt USING lt att list gt lt rel var gt lt ident gt lt att list gt lt att list gt lt attname gt lt attname gt lt attname gt lt ident gt The names of each of the attributes lt attname gt must match those defined in the CADDB schema if the relation already exists otherwise they are used to define the schema for the new relation Note that in MAPOL the attribute names cannot be shared among relations This is the pure relational model which is not enforced within ASTROS itself ASTROS MAPOL PROGRAMMING 9 9 USER S MANUAL As an example the GRID relation of Figure 9 1 would be INTEGER GID REAL X Y Z PROJECT GRID USING GID X Y Z Note that each attribute must be declared and be of the appropriate type Once a relation and its projection have been declared specific entries may be retrieved After a retrieval any or all of the relation s attributes may be used directly by variables of the form lt relname gt lt attname gt This is illustrated in the following program segment INTEGER GID ID REAL X Y Z REAL C1 C2 C3 PROJECT GRID USING GID X Y Z The value
116. in ASTROS is very similar for all nodal output quantities therefore only general descriptions will be given rather than individually describing each response quantity in turn In general the nodal output includes the node point identification number sorted by external identification number and node type G rid S calar point or E xtra point This is followed by either one or six quantities associated with the node point The columns of the print are labeled Ti for the translations and Ri for the rotation where i 1 2 or 3 An example is shown in Table 8 16 Complex nodal quantities are generated by FLUTTER and FREQUENCY disciplines and can be printed in either polar coordinates or cartesian coordinates through the form option on the PRINT or PUNCH command Cartesian print is the default Complex quantities are printed using the same columns as real nodal data but use two lines of output The first line contains either the real part or the magnitude and the second line either the imaginary part or the phase angle in degrees An example of POLAR complex print is shown in Table8 17 All structural disciplines generate DISPLACEMENT output except some FLUTTER analyses Flutter mode shapes are generated only if a flutter condition occurs in the selected range of velocities and then only if the FLUTTER discipline occurs in the ANALYZE subpacket of the solution control VELOCITYS are only available for TRANSIENT and FREQUENCY analyses ACCELERATIONS are avai
117. is shown in Table 8 13 The output for the TRMEM is identical except for the titling The strain energy print for the QDMEM1 is identical to that for the BAR element and includes a breakdown by element and by element type 8 2 1 9 QUAD4 TRIA3 Element Output The QUAD4 and TRIA4 isoparametric quadrilateral and triangular plate elements include both mem brane and bending behavior Transverse shear flexibility may be requested as can the coupling of membrane and bending behavior The QUAD4 element coordinate system and node numbering are shown in Figure 8 9 The TRIA3 element coordinate system and node numbering are shown in Figure 8 10 These elements may be assigned general anisotropic or composite material properties F or designed composites the layers are treated as stacked membrane elements similar to the QDMEM1 element In this case the layers are identified by number in the order specified on the PCOMP PCOMP1 or PCOMP2 entry For design invariant composite laminates the output always refers to the aggregate laminate properties and refers to layer number zero The reference plane of the QUAD4 TRIA3 elements may be offset from the plane of the grid points and variation in the element thickness may be modeled by ASTROS OUTPUT FEATURES 8 19 assigning different element thicknesses at each of the grid points The reader is referred to Appendix A of the ASTROS Theoretical Manual for additional information on these plate bending elements Stress
118. k4 k5 k6 k7 Kg MKAERO1 al 0 0 1 0 7 ABC ABC 0 3 0 6 TO Field Contents SYMXZ SYMXY USER S MANUAL Input Data Entry Description Format and Example Provides a list of Mach numbers m and reduced frequencies k for aerodynamic matrix MKAERO2 calculation Mach Number Frequency Table MKAERO2 Y 2 3 4 5 6 7 8 9 10 MKAERO2 SYMXZ SYMXY mi ky m2 ko m3 k3 CONT CONT m4 k4 m5 k5 etc MKAERO2 0 0 10 60 0 70 30 0 70 1 0 ABC BC 0 8 0 9 0 8 1 40 Field Contents SYMYZ SYMXY Symmetry flags Integer See Remarks 4 and 6 mi ki List of pairs of Mach numbers Real gt 0 and reduced frequencies real gt 0 Remarks 1 This entry will cause the aerodynamic matrices to be computed for the given sets of parameter pairs 2 Several MKAEROi entries may be in the input packet If these data entries are in the packet they will be used Any number of continuations are allowed 4 Thesymmetry flags have the following definition 1 for symmetric Cannot be used with symxy option O for asymmetric 1 for antisymmetric Them k pairs listed on the entry will generate aerodynamic matrices having the symmetries selected m k pairs may be repeated with different symmetry options 6 The following restrictions are imposed on the symmetry flags a Ground effect if present must be antisymmetric Symxy 0 or 1 b Ground effect is not availa
119. lt paramlist gt lt paramlist gt lt ident gt lt paramlist gt lt ident gt Examples are PROC MYPROC A B C PROC GETONE The PROC statement is called the procedure head It is followed by the body and an ENDP statement This defines the procedure program unit As an example to find the square root of a real number 1 a b 2 a Newton Raphson iteration technique can be used an USER S MANUAL A MAPOL procedure for this is shown below PROC USORT A SORTA REAL A SORTA EPS DELTA AOLD EPS 0 0001 SORTA 1 0 DELTA LO WHILE ABS DELTA gt EPS DO AOLD SORTA SORTA AOLD AOLD AOLD A 2 0 AOLD DELTA SORTA AOLD ENDDO END 9 6 4 INVOKING A PROCEDURE Once procedures are defined they may be used anywhere within the main program or in a subsequent procedure Thisis done with the MAPOL statement CALL lt procname gt lt userparm gt where lt procname gt is one of the defined procedures The optional lt userparm gt are the actual user defined variables to be passed to the procedure They must agree in number and type with the PROC definition Parameters are passed by name For example a program segment using the square root procedure of the last Section is MAPOL REAL X Y X SSF CALL USORT X Y END The parameters x and y are the actual variables that will be us
120. moments for the full vehicle s c and B are the non dimensional factors from the AEROS Bulk Data entry the inputs are assumed to be for the full vehicle and DP and vo are defined on the TRIM Bulk Data entry 6 RADIANS Or DEGREES refer to the units of the unit control surface deflection or unit rate RADIANS imply the value due to a unit RAD or RAD S while DEGREES imply the value due to a unit DEG or DEG S THKCAM has no valid angular unit hence the UNITS field is ignored 7 A LOWER bound constraint excludes all values to the left of PRMREQ on a real number line while an UPPER bound excludes all values to the right irrespective of the sign of PRMREQ 7 90 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry DCONSDE DCONSDE BAR element side constraints Description Defines Side constraints on BAR element cross sectional parameters Format and Example ck 2 3 4 5 6 7 8 9 10 DCONSDE DVSYM TMIN TMAX ETYPE 1D1 EID2 EID3 EID4 CONT CONT EID5 EID6 etc DCONSDE D1 02 1 0 3 BAR 200 205 206 Alternate Form di 2 3 4 5 6 7 8 9 10 DCONSDE DVSYM TMIN TMAX ETYPE ID1 THRU ETD2 Field Contents DVSYM Character symbol specifying the PBAR1 cross sectional parameter Remark 1 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 TMIN Minimum value of the PBAR1 cross s
121. of airfoil are defined cam Must be blank THK CAM Illegal specification cam must be blank USO LSO CAM Illegal over specification of data LSO CAM Illegal cam must be blank N Illegal under specification of data and cam must be blank for CANARD For FIN components the options are very limited only symmetric airfoils are allowed and they must be entered as an upper surface ordinate the lower surface ordinates are then defaulted All Blank Default flat plat airfoil generated automatically Lower and upper surface ordinates of airfoil are defined with USO alone effectively LSO usO internally generated Only Legal Nonblank Fin Option 4 The basic coordinate system must be used CP blank This field exists to allow the addition of user defined coordinate systems in the future ASTROS THE BULK DATA PACKET 7 21 ASET USER S MANUAL Input Data Entry ASET Selected Coordinates for the a set Description Defines degrees of freedom that the user desires to place in the analysis set Used to define the number of independent degrees of freedom Format and Examples 1 2 3 4 5 6 7 8 9 10 ASET SETID ID Cc ID Cc ID ASET 16 2 23 3516 Field Contents SETID The set identification number of the REDUCE set Integer gt 0 ID Grid or scalar point identification number Integer gt 0 C Component number zero or blank for scalar poin
122. of symbol is an explicit part of the language In MAPOL such symbols include special characters such as and reserved words such as REAL RELATION IF ELSE WHILE In this Chapter reserved words are indicated by bold capitalized names The second kind of symbol is an identifier or variable name which may be chosen by the programmer Identifiers are composed of letters and digits but the first character must always be a letter This and other definitions in this manual are shown as lt ident gt lt letter gt lt ident gt lt letter gt lt ident gt lt digit gt The vertical line is read as or This definition clearly specifies all possible legal identifiers because no matter how many times the rules lt ident gt lt ident gt lt letter gt or lt letter gt lt ident gt lt digit gt are used the user must finally use the rule lt ident gt lt letter gt This final rule ensures that the identifier begins with a lt letter gt In MAPOL lt letter gt refers to any of the upper case letters from a to z and digit to the integers from 0 to 9 Note that although this open ended definition of an identifier which is called recursive implies that arbitrarily long names may be used the MAPOL compiler has an implementation limit of eight charac ters for a variable name However for subscripted database entities the implementation limit is five characters the subscipt is later
123. of the aerodynamic boxes that coorespond to the structural displacements These data are computed and stored on the relational entity OAGRDDSP Aerodynamic geometry data are computed and stored by default to a set of relational entities that parallel the structural model These data forms are designed primarily for mode checkout of the SAERO model using existing FE preprocessors that support NASTRAN style input data These relations are AEROGEOM which supplies the GRID like data and CAROGEOM which provides connectivity data for the boxes in a ROD or QUAD4 form The ROD is used to model the outline of the airfoils and the QUAD4 elements are used to model the boxes For unsteady aerodynamics the box on box aerodynamic forces are only available through the DE BUG UNSTEADY and DEBUG AMP options see Chapter 2 The geometry data are not available 8 10 OUTPUT FEATURES ASTROS USER S MANUAL GID2 Xe Figure 8 1 BAR Element Coordinate System 8 2 1 2 Bar Element Output The BAR element includes extension torsion bending in two perpendicular planes and the associated shears The shear center is assumed to coincide with the elastic axis The BAR element coordinate system is shown in Figure 8 1 The orientation of the BAR element is described in terms of two reference planes defined through the use of the orientation vector v as shown in that figure The positive direc tions for the element forces are shown in Figure 8 2 Additional info
124. of the passwords as desired For OLD databases the password must match the access type specified by the ACCESS parameter EW Defines the status of the file The file may be NEw in which case it is allocated at OLD run time an existing or OLD file which is the default or a TEMP file which is TEMP deleted at the end of the run Requests that a new physical file be reallocated if it already exists If you specify REALLOC NEW for a file that already exists and you do not indude the REALLOC parameter your job will be terminated params are optional installation dependent parameters e g DBLKSIZE n IBLKSIZE n etc logical_name Defines a logical ASTROS file name ASTROS THE INPUT DATA STREAM 3 5 USER S MANUAL The entries on the ASSIGN commands are keyword controlled but the options within the command must be entered in the order shown The keywords may be separated by commas or blanks An example is ASSIGN RUNDB ASTDB OLD PASSWORD SECRET Figure 3 3 illustrates the function of the ASSIGN command In the case shown the installation dependent parameters DLOC and ILOC have been used to select the physical devices on which the requested files for DB1 reside The optional params on the ASSIGN command may or may not be keyword controlled and are installation dependent They provide a mechanism for the user to direct machine or installation dependent file operations to be performed by the ASTROS procedure At each
125. of the proper dimension ASTROS THE SOLUTION CONTROL PACKET 5 45 USER S MANUAL This page is intentionally blank 5 46 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL Chapter 6 THE FUNCTION PACKET 6 1 BACKGROUND The Function Packet allows the user to define one or more functional forms that may be used to define an objective function or synthetic design constraints beyond those available directly through the Bulk Data packet The Function Packet consists of functions that define mathematical equations which may reference intrinsic response functions for grid point and element response quantities such as displace ments and stresses Furthermore these responses may be selected from any of the optimization boundary conditions or discipline cases 6 2 THE FUNCTION EVALUATION PROCEDURE The user references the functions defined in the Function Packet from the Bulk Data Packet The Bulk Data Packet in turn is referenced from the Solution Control Packet Specifically the Solution Control Packet references the functional design constraint or objective in the Bulk Data Packet in a manner similar to the way it currently references other design constraints The Bulk Data Packet then links the design constraint to the functions within the the Function Packet The Function Packet in turn defines the function specifications The Function Packet is compiled by ASTROS at run time The compiled code which is stored on the ASTROS
126. one group could be a wing body tail combination while a second group could be a pod fin combination 2 Note that the chord wise cuts are in percent while the span wise cuts require physical coordinates For span wise cuts y coordinates are input for wings and canards while z coordinates are input for fins 3 Only the right half plane can be modeled in USSAERO As such all y coordinates specified by LSPAN must be positive 4 The basic coordinate system must be used cP blank This field exists for the addition of a user defined coordinate system in the future ASTROS THE BULK DATA PACKET 7 31 CASELIST USER S MANUAL Input Data Entry CASELIST Description Defines a list of Subcase identification numbers Format and Example 1 2 3 4 5 6 7 8 9 10 CASELIST SID CASE1 CASE2 CASE3 CASE4 CASE5 CASE6 CASE7 CONT CONT CASE8 CASE9 etc CASELIST 101 THRU 6 Alternate Form 2 3 4 5 6 7 8 9 10 CASELIST SID CASE1 THRU CASE2 Field Contents SID Subcase set identification number Integer gt 0 CASEi Subcase identification number Integer gt 0 Remarks 1 CASELIST Bulk Data entries are selected in the Function Packet 2 Refer to the Solution Control discipline commands for details on assigning subcase identification numbers 7 32 THE BULK DATA PACK
127. or blank REFC Reference chord length Real gt 0 0 D 1 0 REFB Reference span Real gt 0 0 D 1 0 REFS Reference wing area Real gt 0 0 D 1 0 GREF Reference grid point for stability derivative calculations Integer gt 0 REFD Fuselage reference diameter Real gt 0 or blank D 1 0 REFL Fuselage reference length Real gt 0 or blank D 1 0 Remarks 1 This entry is required for static aeroelasticity problems Only one AEROS entry is allowed 2 The ACSID must be a rectangular coordinate system Flow is in the positive x direction If ACSID is blank the Basic Coordinate system is used 3 The RCSID must be a rectangular coordinate system All degrees of freedom defining trim variables will be defined in this coordinate system If RCSID is blank the Basic Coordinate system is used 7 18 THE BULK DATA PACKET ASTROS Input Data Entry AESURF Aerodynamic Control Surface Description Specifies an Aerodynamic Control Surface Format and Example ak 2 3 4 5 6 7 8 9 10 AESURF LABEL TYPE ACID CID FBOXID LBOXID AESURE E LEV SY 6000 6010 6030 Field Contents LABEL Unique alphanumeric string of up to eight characters used to identify the control surface TYPE Surface type Character Remark 2 SYM symmetric surface ANTISYM AIRFOIL Input Data Entry AIRFOIL Airfoil Definition USER S MANUAL
128. orm Defines coordinates degrees of freedom that the user desires to use in the computation of inertia relief mode shape s in Dynamic Reduction Format and Example 1 2 3 4 5 6 7 8 9 10 JSET1 SETID e GID1 GID2 GID3 GID4 GID5 GID6 CONT CONT G1D7 GID8 etc JSET1 345 2 1 3 10 9 6 ABC tbe 7 8 Alternate Form 1 2 3 4 5 6 7 8 9 10 JSET1 SETID E GID1 THRU GID2 Field Contents SETID The INERTIA set identification number Component number any unique combination of the digits 1 through 6 with no embedded blanks when point identification numbers are grid points must be blank or zero if point identification numbers are scalar points GIDi Grid or scalar point identification numbers Integer gt 0 Remarks 1 Coordinates specified on this entry form members of a set that is exclusive from other sets defined by bulk data entries 2 When JSET and or JSET1 entries are present all degrees of freedom not otherwise constrained will be placed in the o set 3 If the alternate form is used all points in the sequence 1D1 through ID2 are required to exist and ID2 must be greater than or equal to 1D1 4 Useof JSET1 in dynamic reduction a JSET1 defines the structural and nonstructural j set degrees of freedom inertia relief shapes An alternate input format is provided by the JSET entry b The S
129. output request for each selected ELAS element Strains have no meaning for the scalar spring element and any such requests will be ignored without warning Element strain energies however are available for the element and are computed from the spring constant and the nodal displacement s The strain energy print for the ELAS is identical to that for the BAR element and includes a breakdown by element and by element type If no scalar value is given for the element stress but the stress value is requested a value of zero will be computed and printed for the response quantity with no warnings given 8 2 1 4 IHEX1 Element Output The lHEX1 element is a linear isoparametric solid hexahedron element with three extensional degrees of freedom for each of its eight nodes Stresses strains and strain energies are available as output for the HEX1 element through the STRESS STRAIN and ENERGY solution control print command options Force output is not available for the HE X1 element On request the following stresses and strains are output in the basic coordinate system at the center and at each corner grid point 1 Normal stresses or strains in all three directions 2 Shear stresses or strains in all three planes 3 Principal stresses or strains in all three directions with associated direction cosines 4 Mean stress or strain 5 Octahedral shear stress or strain The stress and strain output at each of the nine points is identified
130. packet has been used to control several low level outputs in a number of ASTROS modules This subsection documents the outputs generated by those DEBUG parameters that relate to modifying the level or form of output from an ASTROS module 8 4 1 Intermediate Steady Aerodynamic Matrix Output The preface aerodynamic module STEADY has a selectable print level DEBUGs called STEADY These options will generate output from the USSAERO submodule of the preface aerodynamics modules There are four print levels available PRINT ACTION 1 Prints steady aerodynamic model geometry and a few miscellaneous debugs 2 Prints the above and stability coefficient data 3 Prints the above and pressure data from the USOLVE submodule Prints the above and voluminous data from the calculation of velocity components and intermediate matrices from the USSAERO submodule The user is cautioned that a print level of 4 generates a large amount of data Most of these prints are vestigial prints from the USSAERO code that was adapted for use in the ASTROS system In cases where the output data is not self evident the user is referred to the USSAERO documentation Reference 6 8 4 2 Intermediate Unsteady Aerodynamic Matrix Output The secondary unsteady aerodynamic preface module AMP has an optional print DEBUG called Amp and an optional matrix argument as its last argument CALL AMP AJJTL D1JK D2JK SKJ OKKL QKJL QJUJL
131. performed modifications to the standard MAPOL algorithm The concepts described can be extended to a large number of similar changes e g modifying the input dynamic pressure value within the MAPOL sequence could be done to avoid re run ning the base run of an ASTROS execution At a more advanced level the MAPOL relational database entity utilities can be used to directly modify the design variable values or objective sensitivities ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 21 USER S MANUAL 4 4 4 Restart Capability Although ASTROS does not support a formal restart capability this does not imply that restarts cannot be performed in ASTROS The restart capability in ASTROS is limited in that you must use a modified MAPOL sequence in order to terminate the system early and the restarted job MUST use a tailored MAPOL sequence to restart the job at the desired point Otherwise there are no limits to what can be done by the experienced user The ASTROS restart capability is best described as a full featured Manual Restart ASTROS does not have an Automated Restart There are several reasons why you may wish to suspend an ASTROS execution and then perform a restart and the program supports this basic capability For example you may wish to examine the progress of a design after each optimization iteration With the run stopped you would then have the freedom to use eSHELL and alter ASTROS data to redirect the optimization path if desired As
132. print control called FLUTTRAN to generate additional information on the flutter eigenvalue extraction The FLUTTRAN option in this case pertains to prints that give information on the iterative solution of the flutter matrices It has the following meaning PRINT ACTION 1 Print the number of iterations required to find each flutter root Print the above plus information on each of the estimated roots for each iteration This voluminous information may sometimes be of use when the flutter solution goes astray in determining if a modified set of velocities would give improved results gt 1 8 4 4 Stress Constraint Computation Output The stress strain constraint evaluation module SCEVAL has an optional DEBUG parameter called SCEVAL The SCEVAL argument if non zero will generate a listing by element type of all the con strained elements the current value of their stress components and the resultant constraint value for each design load condition Also included in the print is the running type count for stress and strain constraints that appears in the Active Constraint Summary print described in Subsection 5 2 3 This allows the user to identify exactly which elements and subcases are associated with each particular stress or strain constraint This print is a remnant from the ASTROS development when the element stresses were not available but it may still be useful in checking out the constraint modeling fo
133. procedure Unlike the multiple DMAP rigid formats however there is a single MAPOL sequence that supports all the available engineering disci plines as well as optimization This fundamental difference is necessary to permit multidisciplinary optimization One consequence of having a single multidisciplinary algorithm is that the standard sequence appears to be very complicated The purpose of this section is to present the internal structure and flow of the standard MAPOL sequence thereby providing the user with sufficient information to tailor the standard sequence to suit individual needs The discussion in this section will be general in order to provide the necessary overview and to introduce the concepts embodied in the standard sequence Modifications to the standard sequence will be presented primarily in terms of capabilities but the presentation will be supported by examples that represent both simple and more complex modifications Finally the Chapter closes with a detailed line by line presentation of the standard executive sequence The reader is also referred to the Programmer s Manual for information on the addition of modules to the ASTROS engi neering library 4 4 STANDARD EXECUTIVE SEQUENCE STRUCTURE The standard MAPOL sequence consists of two major components the variable declarations and the solution algorithm The solution algorithm can be further divided into preface modules the optimiza tion segment and the final analys
134. required that the LRSB data is supplied with a zero first entry 4 THIi and THNi are interference element locations on a body The element numbering begins at one for each body 5 A body is represented by a slender body surrounded by an interference body The slender body creates ASTROS the down wash due to the motion of the body while the interference body represents the effects upon panels and other bodies This is illustrated in the following Figure THE BULK DATA PACKET 7 175 PAERO2 USER S MANUAL SLENDER BODY 6 Elements Shown INTERFERENCE BODY 3 Elements Shown Theta array receiving points for interference body elements _ lt Half Width END VIEW Looking Forward 7 176 THE BULK DATA PACKET ASTROS USER S MANUAL PAERO6 Input Data Entry PAERO6 Description Defines body analysis parameters for steady aerodynamics Format and Examples I 2 3 4 5 6 7 8 9 10 PAERO6 BCID CMPNT CP IGRP NRAD LRAD LAXIAL PAERO6 10 FUSEL 0 3 4 Field Contents BCID Body component identification number Integer gt 0 CMPNT Component type FUSEL for the fuselage and Pop for a POD CP Coordinate system of the geometry input Integer gt 0 or blank IGRP Group flag Integer gt 0 NRAD Number of equal radial cuts used to define the body panels Integer gt O or blank LRAD Identification number of an AEFACT data entry which defines t
135. solution results which are called response functions There are 20 mathematical functions and 27 response functions which may be used in the Function Packet 6 3 1 Mathematical Functions There are 20 intrinsic mathematical functions The definitions for these functions are shown in Table 6 1 6 3 2 Response Functions The 27 available response functions fall into the following categories e Design Variables e Selection e Geometry e Grid Point Response e Element Response e Natural Frequency e Flutter e Static Aero Each of these is described in the following Sections ASTROS THE FUNCTION PACKET 6 5 USER S MANUAL Table 6 1 Mathematical Intrinsics FUNCTION DESCRIPTION ABS a Absolute value a ACOS a Inverse cosine cosa ASIN a Inverse sine si mx a ATAN2 a b Inverse tangent tan CMPLX a b Convert to complex a bi COS a Cosine COS a DEGS a Convert to degrees ar 5 100 EXP a Exponential function HERTZ a Convert to hertz z IMAG a Use the imaginary part of complex a INT a Convert to integer LOG a Logs LOG10 a Logio MOD a b Remainder RADS a Convert to radians l 10a REAL a Usethe real part of complex a erenta Algebraic sense function 1 for negative a for positive a and 0 if a 0 SIN a Sine sin a SORT a Square root TAN a Tangent tan a The arguments a and b represent either
136. that existed in the NASTRAN bulk data definitions and in the interface between bulk data and solution control have been replaced with solution control dependent options There are however still limitations imposed through the interactions between the model and the solution control on combining symmetric antisymmetric and asymmetric boundary condi tions within a single run The eleven boundary condition specifications in ASTROS are shown in the following table OPTION DESCRIPTION AUTOSPC Controls the automatic singularity processor BCID Optional boundary condition identification number Specifies an EIGC bulk data entry which gives eigenvalue extraction CMETHOD a data if an eigenanalysis is to be performed DYNRED Invokes dynamic reduction BEN Specifies the extra point DOF s to be included in dynamic response analyses INERTIA Specifies a JSET bulk data set for dynamic reduction es Specifies the name of the direct mass matrix input in the structural set g set to be included in ALL analyses ee Specifies the name of the direct stiffness matrix input in the structural set g set to be included in ALL analyses Specifies an EIGR bulk data entry which gives eigenvalue extraction METHOD ae data if an eigenanalysis is to be performed Selects multi point constraints defining dependency relations among MPC ya gt specific DOF s REDUCE Defines the DOF s to be retained after a Guyan re
137. the MKAEROi entries The LINEAR QUAD and CUBIC fits are separate first second and third order respectively fits of the real and complex terms of the generalized aerodynamic matrix between each hard point k Only the closest 2 3 or 4 respectively k s are utilized for each fit and LINEAR fitting is used off the ends of the hard point kLIsT The program automatically reduces the order of the fit if too few points are available for the higher order fit e g CUBIC becomes QUAD if only 3 k s are used in the kLIST Refer to the Version 9 0 Release Notes for more information The or1Ginal fit documented in the Theoretical Manual is a cubic fit over all the hard point k s Its use is not recommended since it tends to experience numerical problems for any but small k ranges and small numbers of k s For all fitting options the generalized aerodynamic matrices are normalized by the hard point k value before fitting as documented on the Theoretical Manual Equivalent velocity is defined as the true velocity multiplied by the density ratio See Remark 3 7 132 THE BULK DATA PACKET ASTROS USER S MANUAL FLUTTER 12 When PKIT is selected the fields GFLUT and GFILTER effect the flutter crossings reported during a flutter analysis GFLUT defines the damping value at which flutter occurs GFILTER is used to filter out crossings of lightly damped modes A flutter crossing will only be identified if the damping in the mode drops below GFILT
138. the first non blank line in order to allow the use of the run time database in the subsequent input stream interpretation A single data packet can be split among included files or an INCLUDE file may contain parts of multiple data packets The input interpreter merely replaces the INCLUDE directive with the data contained in the named file so the only requirement is that the input stream that results from the combination of all INCLUDES have the form of a normal input stream The INCLUDE feature can be very useful in certain circumstances For example a special user developed MAPOL sequence can be stored and maintained external to the files containing the engineering data for particular runs or conversely the bulk data representing a large model can be included into the file containing the solution control directives ASTROS THE INPUT DATA STREAM 3 11 USER S MANUAL 3 4 THE DEBUG PACKET The debug packet represents a development tool and is intended to be used primarily by those responsi ble for maintaining the software The debug packet provides the system programmer with the means to invoke or control certain executive and database management system functions that are helpful in tracking the ASTROS execution and or testing the executive and database management system software However because some of the debug options can be useful to the general user the debug packet is fully documented in the User s Manual rather than in the Programmer s
139. the suspension is performed by editing the standard MAPOL sequence and inserting an EXIT call after the last line that is to be executed in the current execution Alternatively if no missing IF THEN ENDIFS Or ENDDOS result portions of the sequence can simply be deleted Some care should be taken in suspending execution in the middle of DO and DO WHILE loops or block IFs Although possible to do suspensions during execution of these repetitive segments can leave the system in a state that is more difficult to reinitialize on the restart exectution Some experience with MAPOL and with ASTROS is needed before attempting these more complex suspensions Suspending execution at the beginning or end of the preface analysis phase of either the optimization or final analysis segements or the sensitivity phase is most likely to yield success To restart the execution you must generate a special MAPOL program either by editing the standard sequence or by writing a new sequence The restart execution of ASTROS does not have any information on where the initial execution terminated Only the data on the database is saved i e available for the current execution Obviously the new execution may start up at any point the user wishes and need not be associated with the area where the initial run terminated although only experienced ASTROS users should attempt to drastically alter the flow of the MAPOL sequence To generate the special MAPOL sequence the user
140. to the dependent coordinate uy In fact the terms on the left side of Equation 1 are simply added to the terms from all other sources in the row for ug 4 Any number of continuations are allowed 7 230 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry TIMELIST TIMELIST Description Defines a list of times at which outputs are desired Format and Examples I 2 3 4 5 6 7 8 9 10 TIMELIST SID TIME TIME TIME TIME TIME TIME TIME CONT CONT TIME TIME etc TIMELIST 100 02 1 0 2 05 1 0 Field Contents SID Set identification number referenced by Solution Control Integer gt 0 TIME Time in consistent time unit at which outputs are desired Real Remarks 1 In order to be used the SID must be referenced by Solution Control 2 Thenearest time to TIME either above or below which was used in the Transient Response analysis will be used to satisfy the output requests 3 Any number of continuations is allowed ASTROS THE BULK DATA PACKET 7 231 TLOAD1 USER S MANUAL Input Data Entry TLOAD1 Description Defines a time dependent function of the form P t AF t 1 for use in a transient response problem Format and Examples 1 2 3 4 5 6 7 8 9 10 TLOAD1 SID DLAGID TID TLOAD1 10 8 13 Field Contents SID Set identificatio
141. unit This section explains the use of procedures and provides examples of their use 9 6 2 PROGRAM UNITS AND SCOPE OF VARIABLES Earlier aMAPOL program was defined very simply as having the form This form is called a main program A main program may also contain other program units that may be procedures or functions such as All procedures must appear in the main program before any executable statements Each procedure or function may have variable declarations within it If it does these variables are called local to the procedure Variables defined in the main program prior to the definition of the procedures are called global The value of a local variable is not available outside of the procedure in which it is defined while 9 24 MAPOL PROGRAMMING ASTROS global variables are available to all procedures that are defined after the declaration of the variable Note that global variables must be defined in the main program preceding procedure definitions Declarations following the procedures are local to the main program 9 6 3 DEFINING A PROCEDURE A procedure is defined in MAPOL by a declaration PROC lt procname gt lt params gt where lt procname gt is any identifier If this name is the same as a run time procedure the new proce dure will be used lt params gt is an optional list of formal parameters that are used to pass information into and retrieve information from the procedure lt params gt
142. use is however discouraged SAERO symtype TRIM k CONSTRAINT STRESS m STRAIN n GENERAL 0 ASTROS THE SOLUTION CONTROL PACKET 5 39 SOLUTION USER S MANUAL Solution Control Command SOLUTION Description The first command in the solution control packet Hierarchy Level Beginning of solution Format SOLUTION Remarks 1 One SOLUTION command must always appear as the first command of the solution control packet 5 40 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL STATICS Solution Control Command STATICS Description Invokes the statics analysis discipline Hierarchy level Discipline Format and Examples STATICS caseid MECH i THERMAL j GRAVITY k DCON o STRESS m STRAIN n DCFUNCTION p STATICS MECH 10 STATICS MECH 4 THERMAL 6 DCFUNCTION 10 Option Meaning caseid Case identification number I nteger gt 0 i Set identification for external loads as defined by LOAD PLOAD FORCE FORCE1 MOMENT and MOMENT1 bulk data entries Set identification for temperatures defined by TEMP or TEMPD bulk data entries Set identificaton of GRAV bulk data entries which define gravity forces m Set identification for stress constraints defined by DCONVM DCONVMM DCONVMP DCONTW DCONTWM Or DCONTWP bulk data entries n Set identification for strain constraints defined by DCONEP DCONEPM DCONEPP DCONFT DCONFTM Or DCONFTP bulk data entries o Set identification of
143. used to generate these names are given in the System Support Manual These simple rules pertain to the simplest and most used AssIGNments of databases If you are using very large databases then there are additional rules These will be provided by your ASTROS System Support Specialist ASTROS RUNNING ASTROS 2 9 2 2 3 The eShell Program If your site has the eShell interactive eBase interface program then to execute this program you enter shell ps prefname pu prefname pl prefname database where prefname Specifies the substitution string used to generate Preference File names You may specify a different string for the System ps the User pu and the Local p1 preference files If you have the unusual case where all of these files have the same name you may use the option p followed by the prefname database Is the name of a database to be opened with read access This places you in the command mode Unless directed otherwise by eShell commands all subsequent output will be sent to the terminal device The optional prefname information is an advanced feature used for customizing eShell which is described in the Installation Guide and System Support Man ual The eShell Tutorial Problem library is available Contact your Systems Support Specialist to obtain the name of the directory where these problems may be found A description of how you may use them is given in the eShell User s Manual 2 2 4 Au2
144. whenever a MAPOL program is not found in the input data stream While Chapter 2 provides a complete listing of the standard MAPOL algorithm for ASTROS the actual program changes with each release of the system Because of this it is recommended that the user request the current listing if it is needed This may be done by executing the ASTROS system generation program SYSGEN This program provides a listing of the standard solution algorithm as part of its output 9 1 4 MODIFYING THE STANDARD SOLUTION In some cases the user may wish to modify the standard ASTROS solution in order to for example perform some auxiliary computations not currently available or to execute only a portion of the solution Special MAPOL editing commands allow for these modifications DELETE REPLACE INSERT DELETE is used to remove one or more statements starting with line a and optionally ending with line b inclusively REPLACE performs a deletion of the specified line or lines and replaces them with any following MAPOL statements The INSERT command allows any number of MAPOL statements to be inserted after line a For example EDIT INSERT 1 MY MODIFICATION REPLACE 20 23 A 2 B DELETE 101 237 Note that rather than entering the MAPOL command the special EDIT declaration is used In the example a comment is added at the beginning of the algorithm to document the modification Several lines 20 23 are replaced by a new com
145. 0 DZ Linear attachment flexibility Real gt 0 0 Remarks 1 The interpolated points k set will be defined by aero cells The sketch shows the cells for which u is interpolated if Box1 111 and Box2 118 2 The attachment flexibility units of area is used for smoothing the interpolation If Dz 0 0 the spline will pass through all deflected grid points If Dz gt gt area of spline a least squares plane fit will occur Intermediate values will provide smoothing If no cP is specified the spline plane is assumed to be the CAERO macro element plane 4 The SPLINE EID is used only for error messages and need not be related to the macroelement identification number 7 222 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description SPLINE2 SPLINE2 Defines a beam spline for interpolating panels and bodies for steady and unsteady aeroelastic analyses Format and Examples 1 2 3 4 5 6 7 8 9 10 SPLINE2 EID MACROID BOX1 BOX2 SETG DZ DTOR CID CONT CONT DTHX DTHY SPLINE2 1000 5000 5000 5100 10 0 1 0 4 ABC BC 1 Field Contents EID Element identification number Integer gt 0 ACROID The identification of a CAERO1 CAERO2 CAERO6 Or PAERO6 aerodynamic macroele ment to be splined Integer gt 0 BOX1 BOX2 The identification numbers of the first and last boxes on the macroelement to be interpol
146. 0 PCOMP PID ZO NSM SBOND F T TMIN LOPT CONT CONT ID1 T1 THi SOUT1 MID2 T2 TH2 SOUT2 CONT CONT ID3 T3 TH3 SOUT3 etc PCOMP 100 0 5 1 5 5 3 HOFF MEM ABC BC 150 0 05 90 YES 45 DEF EF 45 0 Field Contents PID Property identification number Integer gt 0 20 Offset of the laminate lower surface from the element mean plane A positive value means the Ze direction Real or blank see Remark 2 NSM Nonstructural mass per unit area Real gt 0 0 SBOND Allowable shear stress of the bonding material Real gt 0 0 Bu Te Failuretheory one of the strings HILL HOFF TSAI STRESS Or STRAIN See Remark 4 TMIN Minimum ply thickness for design Real gt 0 0 or blank Default 10 LOPT Lamination generation option MEM or blank See Remark 5 MIDi Material identification number of the i th layer Integer gt 0 or blank Ti Thickness of the i th layer Real gt 0 0 or blank THi Angle between the longitudinal direction of the fibers of the i th layer and the mate rial X axis Real or blank SOUTi Stress output request for i th layer one of the strings YES or NO Default NO Remarks 1 For non designed elements the plies are numbered from 1 to n beginning with the bottom layer 7 182 THE BULK DATA PACKET ASTROS USER S MANUAL PCOMP 2 For composities there are two methods for specifying the offset of the element reference plane from the element mean plane zo on this entry and zorF on the CQUAD4 or CTRI
147. 0 0 00307736 0000931911 2953322025737 00 00 00 0 00 07 56 00 05 15 1 DESIGN ITERATION 1 00 00 08 1 00 08 22 00 05 23 3 BOUNDARY CONDITION 1 00 00 02 8 00 08 28 00 05 26 1 MPC REDUCTION 00 00 28 7 00 09 03 00 05 54 9 SPC REDUCTION 00 00 03 6 00 09 07 00 05 58 5 STATIC CONDENSATION 00 00 54 3 00 10 12 00 06 52 9 gt gt gt DISCIPLINE NORMAL MODES 00 00 01 9 00 10 15 00 06 54 8 gt gt gt DISCIPLINE FLUTTER 00 00 09 1 00 10 33 00 07 04 0 DATA RECOVERY 00 00 00 0 00 10 33 00 07 04 1 STATIC CONDENSATION RECOVERY 00 00 00 7 00 10 34 00 07 04 8 SPC RECOVERY 00 00 00 2 00 10 34 00 07 05 0 MPC RECOVERY 00 00 00 3 00 10 34 00 07 05 4 CONSTRAINT EVALUATION 00 00 00 0 00 10 34 00 07 05 4 OUTPUT PROCESSING 00 00 00 1 00 10 35 00 07 05 5 BOUNDARY CONDITION 2 00 00 00 7 00 12 34 00 08 48 0 CONSTRAINT EVALUATION 00 00 19 7 00 13 20 00 09 07 8 OUTPUT PROCESSING 00 00 00 1 00 13 20 00 09 07 9 SENSITIVITY ANALYSIS 00 00 44 7 00 14 47 00 09 52 7 DESIGN MODULE 00 00 03 3 OOS TASS 2 0009856 HH gt 00 00 00 0 00 14 52 00 09 56 1 DESIGN ITERATION 2 00 00 08 2 01 30 33 00 45 23 8 END ASTROS caused by incorrect use of the system or by incorrect system installation The ASTROS Programmer s Manual contains further information on the causes of particular database errors The standard ASTROS error messages are printed by the UTMWRT utility module and represent error checks that the modules are coded to perform or errors that may c
148. 0 0 3 6 0 0 1 0 123 23 DL 1 0 2 9 Field Contents CID Coordinate system identification number Integer gt 0 RID Reference to a coordinate system which is defined independently of new coordinate system Integer gt 0 or blank Ai Bi Ci Coordinates of three points in coordinate system defined by RID Real Remarks 1 Continuation entry must be present 2 The three points Al A2 A3 B1 B2 B3 C1 C2 C3 must be unique and noncollinear Noncol linearity is checked by the geometry processor 3 Coordinate system identification numbers on all CORD1R CORDIC CORD1S CORD2R CORD2C and CORD2S entries must all be unique 7 54 THE BULK DATA PACKET ASTROS USER S MANUAL CORD2C 4 An RID of zero references the basic ordinate system The location of a grid point P in the sketch in this coordinate is given by R Z where 6 is measured in degrees 6 The displacement coordinate directions at P are dependent on the location of P as shown above by U Ug U3 7 Points on the z axis may not have their displacement direction defined in this coordinate system since an ambiguity results ASTROS THE BULK DATA PACKET 7 55 CORD2R USER S MANUAL Input Data Entry CORD2R Rectangular Coordinate System Definition Form 2 Description Defines a rectangular coordinate system by reference to coordinates of three points The first point defines the origin The second defines the direction of the z axis The third point de
149. 04 5 31809E 03 3 02772E 01 1 90237E 02 6 66799E 04 2 50766E 01 5 26 1 055E 01 1 87128E 04 1 87128E 04 2 11023E 02 3 04440E 01 1 91285E 02 2 58853E 03 2 45332E 01 ASTROS OUTPUT FEATURES 8 29 Table 8 21 Modal Participation Factors ASTROS VERSION 9 0 03 03 93 P 31 FINAL ANALYSIS SEGMENT MODES ANALYSIS BOUNDARY 2 MODAL PARTICIPATION FACTORS FOR CRITICAL FLUTTER SPEED OF MACH 8000 V TRUE 18306 8594 V EQ 18306 8594 DENSITY RATIO 1 000000 FREQUENCY 30 310659 HZ 190 447495 RAD S INDEX REAL IMAG INDEX REAL IMAG INDEX REAL IMAG 1 9 8031E 01 0 0000E 00 2 6 4565E 02 1 8495E 01 3 1 5952E 02 9 2147E 03 4 1 1690E 02 8 5903E 03 5 5 0619E 03 2 7755E 03 6 5 2087E 03 8 6489E 04 The Roots print option for normal modes illustrated in Table 8 22 selects that the eigenvalue extraction table be printed It will appear immediately ahead of any eigenvectors if any were selected The table is patterned after that in NASTRAN and includes the eigenvalues in sorted order the extraction order the cydic and radian frequency and generalized mass and generalized stiffness for each eigenvector computed The table is prefaced by data identifying the eigenvalue extraction method and some self ex planatory method dependent data 8 2 5 Aeroelastic Trim Quantities The TRIM solution control print option select that the aeroelastic trim parameters and stability coeffi cients be printed There are two types of aeroelastic trim analyses in
150. 04 924499 103 4 288774E 03 9 772738 104 1 405888E 02 32 035667 105 1 847305E 02 42 094154 106 5 228124E 03 11 913216 BAR ELEMENTS SUBTOTAL 4 388508E 02 100 000000 8 12 OUTPUT FEATURES ASTROS USER S MANUAL the same and or coincide with the element axis Also margins of safety are printed even if no stress limits were given on the material entry In these cases a very large value for the margin of safety is used to indicate that no limits were specified In addition ASTROS fully supports strain output for the BAR element Strain energies may also be requested for the BAR element The strain energy print which is identical for all ASTROS structural elements is patterned after that in NASTRAN It shows the total strain energy for the given displacement field the strain energy in each selected element and the total strain energy for all the elements of a given type e g all the BAR elements Examples of each of these outputs are shown in Table 8 10 8 2 1 3 ELAS Element Output The ELAS element is a scalar spring element which relates the displacements at a pair of scalar points or degrees of freedom or that relates a single degree of freedom to a ground state The element force and strain energy are directly available for the element and the user can if desired input a scalar quantity that relates the stress in the element to the displacement s of the connected degree s of freedom On output these values will be printed for each
151. 10 FREQLIST SID FREO1 FREQ2 FREQ3 FREO4 FREO5 FREQ6 FREQ7 CONT CONT FREQ8 FREQ9 etc FREQLIST 100 10 0 20 0 50 0 100 0 Field Contents SID Set identification number referenced by Solution Control Integer gt 0 FREQi Frequency in Hertz at which outputs are desired Real Remarks 1 In order to be used the SID must be referenced by Solution Control 2 The nearest frequency to FREQ either above or below which was used in the Frequency Response analysis will be used to satisfy the output requests 3 Any number of continuations is allowed ASTROS THE BULK DATA PACKET 7 139 GDVLIST USER S MANUAL Input Data Entry GDVLIST Global Design Variable List Description Defines a list of global design variables for which outputs are desired Format and Example 1 2 3 4 5 6 7 8 9 10 GDVLIST SID GDVID1 GDVID23 GDVID3 GDVID4 GDVID5 GDVID6 GDVID7 CONT CONT GDVID8 GDVID9 etc GDVLIST 100 1 2 3 5 7 9 Alternate Form 1 2 3 4 5 6 7 8 9 10 GDVLIST SID GDVID1 THRU GDVID2 Field Contents SID Set identification number referenced by Solution Control Integer gt 0 GDVID Global design variable identification number Integer gt 0 or blank Remarks 1 In order to be used the SID must be referenced by Solution Control 2 Ifthe alternate form is used GDVID2 must be greater than or equal to GDVID1 3 No
152. 2 USER S MANUAL 2 2 5 Online Manuals The entire suite of ASTROS manuals is available online in the Adobe Portable Document Format PDF This allows you to view the documentation on any computer that has the Adobe Acrobat Reader 3 0 Readers for the MAC PC Sun OS and Solaris and HP were delivered with your system To use the documents from the command line you enter uaidoc manual_name If you omit the manual_name then you will see a splash screen that allows you to navigate to the appropriate manual You may also go directly to a manual by placing its name on the command lines The names of the astros manuals are e astros_theory e astros_prog e astros_ref e astros_schema e eshell e system_support ASTROS RUNNING ASTROS 2 11 USER S MANUAL This pageis intentionally blank 2 12 RUNNING ASTROS ASTROS USER S MANUAL Chapter 3 THE INPUT DATA STREAM 3 1 INTRODUCTION The ASTROS user directs the system through an input data stream composed of a Resource Section which allocates ASTROS databases and specifies memory utilization which is followed by multiple Data Packets Each packet contains a set of related data providing the information needed to execute AS TROS The packets begin with a keyword indicating the nature of the data within the packet and terminate with an ending keyword or with the start of the next data packet All the packets in the input data stream are optional although the order
153. 2 3 1 6 4 Field Contents SID Set identification number Integer gt 0 Sj Set identification numbers of multipoint constraint sets defined via MPC entries Integer gt 0 Remarks 1 Thesj must be unique 2 Multipoint constraint sets must be selected in Solution Control MPC SID to be used 3 sj may not be the identification number of a multipoint constraint set defined by another MPCADD entry 4 MPCADD entries take precedence over MPC entries If both have the same set identification number only the MPCADD entry will be used 7 168 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry MPPARM MPPARM Description Identify values of user defined optimizer parameters that overrides the default values Format and Example aD 2 4 5 6 7 8 9 10 MPPARM PARAM VALUE PARAM VALUE PARAM VALUE PARAM VALUE CONT CONT PARAM VALUE etc MPPARM ISCAL STOL 0 005 Field Contents PARA Name of parameter to be overridden Character VALUE Integer or real value to be used for the parameter Remarks 1 Any number of PARAM VALUE combinations can be specified on an MPPARM entry 2 See the EDO software manual ADS V 1 10 for a definition of parameters but the most useful are shown below REAL PARAMETER DEFINITION DEFAULT Constraint tolerance in the Method of Feasible r Directions or the Mo
154. 2 COMMENTARY recline tae ak Ree Boks Gk Seat de ale a a rd hen Gia 9 6 9 23 SIMPLE DATA TYPES o s ne AS Bea eet ROAD A ee Pe eed ee 9 6 9 2 3 1 DataTypeINTEGER 0 0000 e 9 6 9 2 3 2 Data Type REAL 02 eee 9 6 9 2 3 3 Data Type COMPLEX 000300030 dutena aa a Pegg 9 7 9 2 3 4 Data Type LOGICAL e 9 7 9 2 3 5 Data Type LABER ro ae rior ea A a Be PR a a ay 9 7 9 2 4 COMPLEX DATA TYPES e 9 8 ASTROS v USER S MANUAL 9 2 4 1 Data Types MATRIX and IMATRIX aoaaa o e e 9 8 9 2 4 2 Data Type Relation e e aa E a a E E A A A S D 9 8 9 2 4 3 Data Types UNSTRUCT and IUNSTRUCT 2 4 9 10 9 2 4 4 Data Base Entity Declaration Requirements 0 e 9 10 9 3 EXPRESSIONS AND ASSIGNMENTS co e 9 11 9 3 1 ARITHMETIC EXPRESSIONS 0 0 e 9 11 9 3 1 1 Arithmetic Operators 9 11 9 3 1 2 Arithmetic Operands ee 9 11 9 3 1 3 Evaluation of Arithmetic Expressions 2 0 o e 0 9 12 9 3 1 4 The Uses of Parentheses eo 9 12 9 3 1 5 Type and Value of Arithmetic Expressions 0 9 13 9 3 2 LOGICAL EXPRESSIONS 0 0 0 e 9 13 93 21 Logical OPOratorS ecos ptos ar mer a a 9 13 9 3 2 2 Logical Operands 9 14 9 3 2 3 Evaluation of Logical Expressions a a a a 9 14 9 3 3
155. 3 CALL UTMPRT AMAT SOLUTION TITLE TEN BAR TRUSS OPTIMIZE PRINT DCON ALL HIST BOUNDARY SPC 1 LABEL STATIC ANALYSIS STATICS MECH 1 CONST STRESS 100 GENERAL 100 END ANALYZE BOUNDARY SPC 1 METHOD 2 STATICS MECH 1 LABEL FINAL STATIC ANALYSIS PRINT DISP ALL MODES LABEL FINAL MODAL ANALYSIS PRINT MODES ALL DISP ALL ROOT ALL END BEGIN BULK GRID di 720 0 360 0 0 0 GRID 2 p 720 0 0 0 0 0 GRID 3 360 0 360 0 0 0 GRID 4 360 0 0 0 0 0 GRID 5 5 0 0 360 0 0 0 GRID 6 f 0 0 0 0 0 0 CROD 1 10 3 5 CROD 2 10 Y 3 CROD 373 TOs 4 6 CROD 9 10 2y 3 CROD 10 10 1 4 PROD 10 Do 150 MAT1 2 1 E 7 0 3 0 1 y y 25000 0 25000 0 SPCl i 123456 5 6 SPC1 1 3456 1 THRU 4 FORCE 1 2 E 0 0 1 0 0 FORCE 1 4 1 E5 0 0 1 0 0 CONVERT MASS 2 59E 3 EIGR 2 GIV 0 0 700 0 Dy Dee y ABC BC MAX MPPARM ISCAL 1 DESELM 1 1 CROD 6 667E 3 1000 0 2 0 ROD1 DESELM 2 2 CROD 6 667E 3 1000 0 2 0 ROD2 DESELM 9 9 CROD 6 667E 3 1000 0 2 0 ROD9 DESELM 10 10 CROD 6 667E 3 1000 0 2 0 ROD10 DCONVMM 100 2 5 4 2 5 4 2 DCONDSP 100 1 UPPER 2 0 POSNOD1 1 2 1 0 DCONDSP 100 2 UPPER 2 0 POSNOD2 2 2 20 DCONDSP 100 8 LOWER 2 0 NEGNOD1 4 2 1 0 ENDDATA Figure 3 2 Features of a Sample ASTROS Input Stream THE INPUT DATA STREAM 3 3 USER S MANUAL data packet is the BULK DATA packet The BULK DATA pack
156. 3 Each non null term in the matrix requires a continuation entry The column index and row index values can appear any number of times on a logical entry but a fatal error will occur if the same term is entered more than once 4 Thematrix terms can be entered in any order The TRIANG input FORM implies that only the upper or lower triangular portion of the symmetric matrix is input ASTROS will automatically expand the input across the diagonal ASTROS THE BULK DATA PACKET 7 113 DVTOPTE USER S MANUAL Input Data Entry DVTOPTE Type definition for designed element thickness variation Description Defines the thickness variation type for a designed element by specifying the element identification numbers Format and Examples 1 2 3 4 3 6 7 8 9 10 DVTOPTE TYPE ETYPE EID1 EID2 EID3 EID4 EID5 EID6 CONT CONT EID7 EID8 etc DVTOPTE TOP QUAD4 101 102 104 Alternate Form 1 2 3 4 5 6 7 8 9 10 DVTOPTE TYPE ETYPE EID1 THRU EID2 Field Contents TYPE Designed element thickness variation type one of the character values CENTER TOP or BOTTOM Character default CENTER CENTER Element thickness varies about a fixed element reference plane TOP Element thickness varies about a fixed element top plane BOTTOM Element thickness varies about a fixed element b
157. 3 1 NOT CONVERGED 5 5 89348E 03 47 11 18 1 0 4 0 NOT CONVERGED 6 5 74943E 03 56 13 18 J 0 4 0 NOT CONVERGED F 5 62364E 03 38 9 18 I 0 4 AL NOT CONVERGED 8 5 50224E 03 40 10 18 ak 0 4 aL NOT CONVERGED 9 5 38496E 03 24 7 18 J 0 4 il NOT CONVERGED 10 5 27604E 03 36 8 18 2 0 4 di NOT CONVERGED 11 5 18694E 03 43 11 18 2 0 4 1 NOT CONVERGED 12 5 14224E 03 33 5 18 2 0 4 1 NOT CONVERGED 13 5 13861E 03 10 2 18 2 0 4 1 NOT CONVERGED 14 5 13618E 03 10 J 18 2 0 4 d NOT CONVERGED 15 5 11049E 03 18 3 18 2 0 4 El CONVERGED THE FINAL OBJECTIVE FUNCTION VALUE IS FIXED 0 00000E 00 DESIGNED 5 11049E 03 TOTAL 5 11049E 03 8 6 OUTPUT FEATURES ASTROS USER S MANUAL Table 8 8 ASTROS Execution Summary FOCI SIG ICICI GIGI ICICI ICICI CI ICI ICI I ICI k xxx xxx ASTROS TERMINATED Aa 02 16 93 11 45 50 PE kk kk ORIO ROO ROO k k k k k k k k ee k k ASTROS TIMING SUMMARY ELAPSED TOTAL STEP TIME CPU CPU 00 00 00 00 00 00 0 BEGIN ASTROS 00 00 02 00 00 01 9 BEGIN PREFACE MODULES 00 00 08 4 00 00 12 00 00 10 4 ELEMENT MATRIX GENERATION 00 02 56 9 00 04 43 00 03 07 4 NON PLANAR STEADY AERODYNAMICS 00 00 00 0 00 04 43 00 03 07 4 PHASE 1 ELEM MATRIX ASSEMBLY 00 00 30 4 00 05 54 00 03 37 8 PHASE 1 STATIC LOADS GENER 00 00 00 2 00 05 55 00 03 38 0 STEADY AERODYNAMICS 00 00 00 0 00 05 55 00 03 38 1 UNSTEADY AERODYNAMICS 00 01 36 9 00 07 56 00 05 15 1 RR RRR RRR RR Kk 00 00 00 0 00 07 56 00 05 15 1 BEGIN OPTIMIZATION 00 00 0
158. 35 FLEXCF USER S MANUAL 3 The allowable control surfaces trim_param are ALPHA BETA PRATE QRATE RRATE PACCEL QACCEL RACCEL trim_param User Surfaces The User Surfaces are defined using AESURF Bulk Data entries 4 If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 36 THE FUNCTION PACKET USER S MANUAL USER S MANUAL FREQ Intrinsic Function FREQ Purpose Toretrieve the current value of the natural frequency computed in a Normal Modes analysis Usage MODELIST mode_sid CASELIST case_sid modeid caseid FREQ Function Arguments modeid Identification of a mode index mode_sid Set identification of a MODELIST bulk data entry used to specify the mode index caseid Subcase identification case_sid Set identification of a CASELIST bulk data entry used to specify the subcase identification number Notes 1 If the subcase reference is omitted then the specific discipline request defines the requested subcase ASTROS THE FUNCTION PACKET 6 37 FROOT USER S MANUAL Intrinsic Function FROOT Purpose Toretrieve the current value of the flutter root p k y i Usage FROOT machop densop modeop velop caseop where a mvalue HARAPR MACHLIST mach_sid de dvalue P DENSLIST dens_sid modeid MOGEOR MODELIST mode_sid I es vvalue ERES m VELOLIST vel_sid as caseid A p CASELIST
159. 4 5 6 7 8 9 10 PLIST LINKID PTYPE PID1 PID2 PID3 PID4 PID5 PID6 CONT CONT PID PID8 PID9 etc PLIST 6 PROD 12 14 22 Alternate Form I 2 3 4 5 6 7 8 9 10 PLIST DVID PTYPE PID1 THRU PID2 Field Contents LINKID Property list identifier Integer gt 0 PTYPE Property type associated with this list e g PROD PID1 PID2 Property entry identifications Integer gt 0 or blank PID3 Remarks 1 Allowable PTYPES are PROD PSHEAR PCOMP PCOMP1 PCOMP2 PELAS PSHELL PMASS PTRMEM PQDMEM1 and PBAR 2 Ifthe alternate form is used PID2 must be greater than or equal to PID1 3 All elements using properties listed on PLIST entries for a particular LINKID will be designed by linked to that design variable that references the PLIST LINKID ASTROS THE BULK DATA PACKET 7 191 PLISTM Input Data Entry Description PLISTM referencing an element property entry Format and Example USER S MANUAL Defines elements and their local design variables associated with a design variable by 1 2 3 4 9 6 7 8 9 10 PLISTM LINKID PTYPE PID1 DVSYM1 PID2 DVSYM2 PID3 DVSYM3 CONT PID4 DVSYM4 etc PLISTM 6 PBAR1 12 D1 22 D1 Field Contents LINKID Element list identifier Integer gt 0 PTYPE Character input identifying the property type One of the following PELAS PMASS PBAR PBAR1 PROD PSHEAR PQDMEM1 PTRMEM PSHELL PCOMP PCOMP1 PCOMP2 PIDi
160. 7 Unlike the mMAT1 entry data from the MAT2 entry are used directly without adjustment of equivalent E G Or NU values ASTROS THE BULK DATA PACKET 7 157 MAT8 Input Data Entry Description Defines the material property for an orthotropic material MAT8 Format and Example Material Property Definition Form 8 USER S MANUAL 1 2 3 4 5 6 7 8 9 MAT8 MID El E2 NU12 612 Gl Z G2 Z RHO CONT CONT Al A2 TREF Xt Xc Yt Ye S CONT CONT GE F12 MAT8 171 30 6 1 6 0 3 2 6 3 6 1 5 6 0 056 ABC BC 28 6 1 5 6 155 0 1 44 1 5 4 2 42 8 42 1 3 DEF EF 1 4 Field Contents ID Material identification number Integer gt 0 El Modulus of elasticity in longitudinal direction also defined as fiber direction or 1 di rection Real 0 0 E2 Modulus of elasticity in lateral direction also defined as matrix direction or 2 direc tion Real 0 0 ee Poisson s ratio a for uniaxial loading in 1 direction Note that NU21 EN for uniaxial loading in 2 direction is related to NU12 E1 E2 by the relation NU12 E2 NU21 E1 Real G12 In plane shear modulus Real gt 0 0 G1 Z Transverse shear modulus for shear in 1 Z plane Real gt 0 0 or blank default implies infinity G2 Z Transverse shear modulus for shear in 2 Z plane Real gt 0 0 or blank default implies infinity RHO Mass density Real gt 0 0 Al Thermal
161. 7 4 728344E 03 3 414915E 03 4 9E 00 21 1 600469E 03 1 250366E 03 1 6E 01 25 5 703891E 03 4 119477E 03 3 9E 00 29 2 716250E 02 2 716250E 02 1 0E 02 32 7 276465E 02 7 276465E 02 3 7E 01 36 3 413748E 03 3 413748E 03 7 2E 00 SIMPLIFIED FIGHTER WING ASTROS VERSION 9 0 03 03 93 P 16 FINAL ANALYSIS SEGMENT STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 STRAINS IN SHEAR PANELS SHEAR ELEMENT MAX AVERAGE ELEMENT MAX AVERAGE BLE SHEAR SHEAR TO SHEAR SHEAR 17 1 257538E 03 9 082221E 04 21 4 256566E 04 3 325442E 04 25 1 516992E 03 1 095605E 03 29 7 224069E 05 7 224069E 05 32 1 935230E 04 1 935230E 04 36 9 079117E 04 9 079117E 04 SIMPLIFIED FIGHTER WING ASTROS VERSION 9 0 03 03 93 P 18 FINAL ANALYSIS SEGMENT STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 FORCES IN SHEAR PANELS SHEAR POINT 1 POINT 2 POINT 3 POINT 4 ELEMENT F FROM 4 F FROM 2 F FROM 1 F FROM 3 F FROM 2 F FROM 4 F FROM 3 F FROM 1 ID KICK 1 SHEAR 12 KICK2 SHEAR 23 KICK 3 SHEAR 34 KICK 4 SHEAR 41 17 6 30889E 03 1 41850E 03 1 41850E 03 6 30889E 03 6 30889E 03 9 45669E 02 9 45669E 02 6 30889E 03 0 00000E 00 9 45669E 02 0 00000E 00 6 30446E 02 0 00000E 00 4 20297E 02 0 00000E 00 6 30446E 02 32 2 91059E 03 6 54882E 02 6 54882E 02 2 91059E 03 2 91059E 03 6 54882E 02 6 54882E 02 2 91059E 03 0 00000E 00 1 45529E 02 0 00000E 00 1 45529E 02 0 00000E 00 1 455 29E 02 0 00000E 00 1 45529E 02 ASTROS OUTPUT FEATURES 8 23 USER S MANUAL The form of nodal output
162. A N A ROD5 1TEN BAR TRUSS ASTROS VERSION 9 0 03 03 93 P 8 ASTROS ITERATION 1 STATIC ANALYSIS SUMMAR Y OF LOCAL DESIGN VARIABLES SS ITERATION 1 ROD ELEMENTS EID LINKING OPTION AREA MINIMUM MAXIMUM 1 UNIQUE PHYSICAL 3 00000000E 01 1 000E 01 1 500E 04 2 UNIQUE PHYSICAL 3 00000000E 01 1 000E 01 1 500E 04 3 UNIQUE PHYSICAL 3 00000000E 01 1 000E 01 1 500E 04 4 UNIQUE PHYSICAL 3 00000000E 01 1 000E 01 1 500E 04 5 UNIQUE PHYSICAL 3 00000000E 01 1 000E 01 1 500E 04 Table 8 19 Design Constraint Summary TEN BAR TRUSS ASTROS VERSION 11 0 04 06 95 Ps 56 ASTROS ITERATION 13 STATIC ANALYSIS SUMMARY OF ACTIVE CONSTRAINTS AFTER ANALYSIS 13 OF A MAXIMUM 16 18 CONSTRAINTS RETAINED OF 18 APPLIED FO III IO IOI IO ISIC ROO IO II ICI IO III ICI IO IOI ICI IO IO I ICA IO I A Ca ae x CONSTRAINT RETENTION ALGORITHM SUMMARY RFAC 3 000 EPS 100 NDV 10 bs OF CONSTRAINTS RETAINED BY RFAC 18 CUTOFF CONSTRAINT VALUE 2 000 ADDED WITH VALUES GREATER THAN EPS 0 bad OF ADDITIONAL MINIMUM THICKNESS x CONSTRAINTS RETAINED ONLY FOR i CONTROLLING MOVE LIMITS DCONTHK 0 FO III IO E E ICI II ICI IO IOI ICI IO IRI ICI IO ICI ICI IO IOI ICI IO IO IR COUNT CONSTRAINT VALUE CONSTRAINT TYPE TYPE COUNT BOUNDARY ID SUBCASE ELEMENT TYPE EID LAYR DIMENSION 1 1 99999E 00 DISP DCID 1 a 1 dl N A N A 2 1 99999E 00 DISP DCID 2 2 1 1 N A N A 3 1 36685E 00 DISP DCID 3 3 1 1 N A N A 4 1 73042E 00 DISP DCI
163. A3 Bulk Data entries The distinction is shown in the figure below UPPER SURFACE LOWER SURFACE Is ZO ELEMENT REFERENCE ZOFF ELEMENT MEAN PLANE You may only specify a zo on this entry if the zorr field of any CQUAD4 or CTRIA3 referencing it is blank The default value for zo is t 2 where t is the overall thickness of the laminate SBOND is required if bonding material failure index calculations are desired 4 The failure theory is used to determine the element failure on a ply by ply basis The available theories are HILL Hill Theory HOFF Hoffman Theory TSAI Tsai Wu Theory STRESS For Maximum Stress Theory STRAIN For Maximum Strain Theory MEM indicates a layup of membrane only plies The material properties MIDi may reference only MAT1 MAT2 and MATS Bulk Data entries If any of the MIDi Ti or THi are blank then the last non blank values specified for each will be used to define the values for the ply 8 TMIN will be ignored unless the element is linked to design variables by SHAPE entries ASTROS THE BULK DATA PACKET 7 183 PCOMP1 Input Data Entry Description USER S MANUAL PCOMP1 Layered Composite Element Property Defines the properties of an n ply laminated composite material where all plies are composed of the same material and are of equal thickness Format and Examples 1 2 3 4 5 6 7 8 9 10
164. AD Form FREQ a ITER b MODE c TIME d q MASS ITER b r MODEL ITER ag ah MSNS ITER b t OGRA ITER b u QHH ITER b MODE c x QHJ ITER b MODE c y ROOT Form ITER b MODE c z SPCF Form FREQ a ITER b MODE c TIME d aa STIF ITER b ab STRA Form FREQ a ITER b MODE c TIME d aj ac STRE Form FREQ a ITER b MODE c TIME d aj ad TPRE ITER b ae VELO Form FREQ a ITER b MODE c TIME d af TRIM PUNCH DISP ALL PUNCH RECT MODE 10 ITER 20 DISP ITER LAST 6 ENERGY POLA 10 PUNCH MODE NONE Options Meaning Form RECT Or POLA requests output in RECTangular or POLAr format See Remarks 1 and 2 a Set identification of a FREQLIST bulk data entry that is used to request the frequencies at which output is to be punched See Remark 2 b Set identification of an ITERLIST bulk data entry that is used to request the optimization iterations at which output is to be punched See Remark 2 5 36 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL PUNCH ASTROS Set identification of a MODELIST bulk data entry that is used to request the modes at which output is to be punched See Remark 2 Set identification of a TIMELIST bulk data entry that is used to request the times at which output is to be punched See Remark 2 Set identification of a GRIDLIST bulk data entry that is used to request the
165. AM ASTROS USER S MANUAL 3 4 4 MISCELLANEOUS DEBUG COMMANDS Table 3 4 shows several miscellaneous DEBUG commands which are used to control optimization and looping optimization scaling and geometry checking of plate elements Table 3 4 Miscellaneous Debug Commands KEYWORD DESCRIPTION DVWARNING opt Sets a limit for the number of design override linking warnings e g Torsion Set to Zero for Design issued by any one element type Use keyword ALL or integer value n Default 50 Controls scaling of design variables MPSCAL opt me Scales global variables to unity before Microdot is invoked Default OFF Does not scale variables Enables Panel Buckling diagnostics PBKDIAG n o Turn off diagnostic print 1 Print roots only 2 Print roots and eigenmatrix eae A Initial number of terms in the Panel Buckling series solution must be less than PBKNMAX EA E Maximum number of terms in the Panel Buckling series solution Power used in linearizing the Panel Buckling constraint 1 Area val PBKPWER val val G F Default 3 0 Determines whether the check for stress constraints on STRESS_DV opt opt undesigned elements will be a warning or fatal error Value is WARNING Default or FATAL WARPMX val val The maximum allowed warping value for QUAD4 elements Se nang vei Sai Specifies a tolerance value for defining the objective function to be the same from one
166. ANUAL VSDAMP Input Data Entry VSDAMP Description Specifies values of g and or m3 to generate either viscous damping that has the same damping forces as structural damping of magnitude g at the frequency w3 or to specify the structural damping g see Remarks 3 and 4 Format and Examples I 2 3 4 5 6 7 8 9 10 VSDAMP SID G 03 SID G 03 VSDAMP 100 0 005 15 0 Field Contents SID Set identification number Integer gt 0 G Damping value Real 03 Frequency value in Hertz Real gt 0 0 Remarks 1 Thesetid is selected by the DAMPING n command in Solution Control 2 Upto two values of g and w3 can be defined on a single entry 3 If 3 is zero g will be used to generate a complex stiffness matrix 3 of theform K 1 ig K If m3 is nonzero a viscous damping matrix of the form B na K is generated 3 ASTROS THE BULK DATA PACKET 7 239 VSDAMP USER S MANUAL This page is intentionally blank 7 240 THE BULK DATA PACKET ASTROS USER S MANUAL Chapter 8 OUTPUT FEATURES In a software system the magnitude of ASTROS the amount of data that may be of interest to you is very large In multidisciplinary optimization the quantity of data is even larger and the expense involved in its computation even more critical It is worthwhile therefore to limit the amount of output to a minimum and to provide a mechanism for you to select those data that are of importance in
167. AST requests that output be printed for only the final value in a list For example ITER LAST selects output for the final iteration in an optimization ACTIVE selects the active constraints HIST and TRIM are toggles If they are present the specified data are printed TRIM indicates that stability derivative data associated with an aeroelastic trim are to be printed HIST indicates that the design iteration history summary is to be printed Aerodynamic macro elements are selected indirectly A macro element is chosen by selecting one or more aerodynamic box elements contained within the macro element See Table 47 for a summary of how the items are printed or written to the CADDB database ASTROS THE SOLUTION CONTROL PACKET 5 35 PUNCH USER S MANUAL Solution Control Command PUNCH Description Specifies the required output file processing for the punch file Hierarchy Level Various Format and Examples PUNCH Form FREQ a ITER b MODE c TIME d ACCE Form FREQ a ITER b TIME d e AIRD Form ITER b MODE c TIME d f BUCK ITER b ah CGRA ITER b h DCON ITER b i DISP Form FREQ a ITER b MODE c TIME d j ENER Form FREQ a ITER b MODE c TIME d k FORC Form FREQ a ITER b MODE c TIME d 1 GDES ITER b m GPFO Form FREQ a ITER b MODE c TIME d n GPWG ITER b n1 KSNS ITER b o LDES ITER b p LO
168. ASTROS USER S MANUAL MKAERO1 Table of symmetries Mach numbers and reduced frequencies MKAERO2 Table of symmetries Mach numbers and reduced frequencies PAERO1 Association between bodies and macroelements PAERO2 Body cross section property definition 7 5 15 Discipline Dependent Problem Control The following bulk data entries are the controlling entries referenced by Solution Control in selecting specific disciplines and subcases In each case many of these inputs can appear in the bulk data packet with the particular input to be used for the subcase referenced in the Solution Control Packet FLUTTER Basic parameters for flutter analyses TRIM Flight condition for steady aeroelastic trim analyses EIGC Complex eigenvalue extraction parameters EIGR Real eigenvalue extraction parameters FFT Fast Fourier Transform parameter definition FREQ Frequency step definition for frequency response FREQ1 Frequency step definition for frequency response FREQ2 Frequency step definition for frequency response T Initial condition definition for direct transient response same as NASTRAN TIC entry TABDMP1 Modal damping table for modal dynamic response TE Dynamic transfer function definition STEP Time step definition for transient response VSDAMP Definition of viscous damping based on equivalent structural damping 7 6 DIFFERENCES BETWEEN ASTROS AND NASTRAN BULK DATA Some of the bulk data en
169. Advanced CAE Applications for Professionals Software that works for you ASTROS User s Reference Manual for Version 20 XA UNIVERSAL ANALYTICS INC 1997 UNIVERSAL ANALYTICS INC Torrance California USA All Rights Reserved First Edition March 1997 Second Edition November 1997 Restricted Rights Legend The use duplication or disclosure of the information contained in this document is subject to the restrictions set forth in your Software License Agreement with Universal Analytics Inc Use duplica tion or disclosure by the Government of the United States is subject to the restrictions set forth in Subdivision b 3 ii of the Rights in Technical Data and Computer Software clause 48 CFR 252 227 7013 The concepts and examples contained herein is for educational purposes only and are not intended to be exhaustive or to apply to any particular engineering problem or design All information is subject to change without notice Universal Analytics Inc does not warrant that this document is free of errors or defects and assumes no liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein UNIVERSAL ANALYTICS INC 3625 Del Amo Blvd Suite 370 Torrance CA 90503 Tel 310 214 2922 FAX 310 214 3420 USER S MANUAL TABLE OF CONTENTS 1 INTRODUCTION y A al l A 2 RUNNING ASTROS o o o ee 2 1 OVERV
170. BC BC 1 2 2 0 2 1 3 0 4 0 4 DEF EF 1 5 0 4 3 625 Field Contents NAME Any valid data base entity name Character PREC The precision of the matrix entity to be loaded Character selected from RSP CSP RDP CDP FORM The form of the matrix entity to be loaded Any one of the following REC SYM DIAG IDENT SQUARE M The number of rows in the matrix Integer gt 0 N The number of columns in the matrix Integer gt 0 Ci The column number of the column being loaded Integer Ri The row number of the first row in the string being loaded Integer A Ri Ci Matrix terms Real Remarks 1 If the named entity exists it will be flushed and reloaded If the entity does not exist it will be created 2 Column and row identifiers ci Ri must always appear together although they can appear in any two contiguous fields 3 Columns must be loaded in increasing column number order If more than one string is to be loaded for a particular column the ci field must contain the same value as in the previous string Strings must be loaded in increasing row order without overlap Complex matrices require two real values for each matrix term These can be split across physical entry boundaries 7 112 THE BULK DATA PACKET ASTROS USER S MANUAL DMIG Input Data Entry DMIG Direct Matrix Input at Grid Points Description Defines structurerelated direct input matrices with terms located by external grid com ponent values Format and Example
171. BRANE FORCES BENDING MOMENTS TRANSVERSE SHEAR FORCES ID FX EY FXY MX MY MXY QX QY 2 10645E 02 1 73879E 03 2 46591E 02 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 5 97852E 01 1 69688E 03 1 03084E 01 2 03451E 07 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 13 1 89788E 02 6 80536E 02 4 45374E 01 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 ASTROS OUTPUT FEATURES 8 21 USER S MANUAL 8 2 1 10 Shear Panel Output The shear panel is an element which resists the action of tangential forces applied to its edges In ASTROS the shear panel supports only isotropic material properties and makes use of the shear flow distribution approximation of Garvey Reference 4 with special handling for warped parallel edge and general trapezoidal geometries The element force sign convention is shown in Figure 8 11 The stresses strains forces and strain energies are available for the shear panel The element forces that are com puted include the following 1 The eight forces between each pair of nodes each force is directed along the line connect ing the adjacent nodes the element edge 2 The four kick forces at each node normal to the plane formed by the two adjacent ele ment edges 3 The shear flows forces unit length along each edge When stresses or strains are requested they are computed at the node points in skewed coordinates parallel to the adjacent edges Both the average and maximum s
172. CADDB database see the Programmer s Manual for a detailed description of CADDB is then used to evaluate functions as necessary during the design process The Function Packet while it may look like a Fortran program is non procedural This means that the functional definitions including any intermediate terms used in the functions may be specified in any order When it is necessary to evaluate a function during an ASTROS execution the evaluation is performed by a process called ASTROS THE FUNCTION PACKET 6 1 USER S MANUAL instantiation nstantiation is the process of determining the value of a function by retrieving the components needed to evaluate it During instantiation ASTROS determines the validity of each function both in terms of its syntax and that of the other functions it may use This process determines that each function is legal completely defined and that the supporting Bulk Data if any are present on the database As part of this operation the actual number of function evaluations or instances is determined The user may define one function in the function packet but invoke it many times Each of the invocations must be legal and complete The instantiation process results in the creation of data structures that describe each instance con straint or function evaluation These data structures are used by ASTROS to control the computation of the constituent responses For example if a function calls for the SI
173. CONT SID SID etes DCONPMN 0 010 1001 1002 SID Field INTHK PLYNUM PLYSET Contents Minimum ply thickness Real gt 0 0 Default 10 Single ply number numbered in the order used on the PcomMpPi that constitutes the ply thickness Only one of PLYNUM or PLYSET may be used Integer gt 0 or blank Set identification number of one or more PLYLIST bulk data entries naming a set of plies whose summed thicknesses constitute the ply thickness in the constraint Only one of PLYNUM or PLYSET may be used Integer gt 0 or blank Set identification of one or more ELEMLIST entries that define the set of composite elements to which this composition constraint will be applied Integer gt 0 or blank Remarks 1 2 7 88 THE BULK DATA PACKET One and only one of either PLYNUM or PLYSET must be given Because of the generality of the definition of the pl y there is no real distinction between the DCONLMN and the DCONPMN constraints Only the defaults are different to allow simple definitions of the common laminate in DCONLMN ALL or ply PLYNUM in DCONPMN The definition of ply thickness can vary from entry to entry If PLYNUM is used to define toy that one layer constitutes a ply otherwise toy is the sum of the layer thicknesses of all the layers listed in PLYSET If this constraint is applied to a composite element with undesigned layers these laye
174. CTOR POLAR FORM POINT ID TYPE rd T2 T3 R1 R2 R3 7 G 0 00000E 00 0 00000E 00 1 17367E 01 0 00000E 00 5 63383E 01 0 00000E 00 0 00000E 00 0 00000E 00 3 47650E 02 0 00000E 00 1 67894E 02 0 00000E 00 8 24 OUTPUT FEATURES ASTROS USER S MANUAL the APPLIED component is printed on request TRANSIENT and FREQUENCY disciplines compute loads at user specified time or frequency steps which may be printed The FLUTTER and MODES disciplines have no loads output The print of single point forces of constraint the PRINT sPCF option has been implemented in a computational sense with the PRINT or PUNCH request generating the SPCFORCE forces for all disciplines including SAERO and storing the terms in the relation OGRIDLOD IN SAERO the applied load that is used is the sum of the trimmed rigid load and the flexible correction The actual printing of the spcror CES to the output file is not available The GPFORCE PRINT PUNCH request does not send data to the output file or to the punch file Instead a PRINT Or PUNCH request will result in the storage of the data on the database The relation used to store GPFORCE data is called GPFDATA and is loaded in module EDR The format of the relational tuple is ATTRIBUTE DESCRIPTION NITER Iteration Number BC Boundary Condition id DISC Discipline Type as in CASE relation SUBCASE Subcase number EID Element id ETYPE Element Type CMPLX Complex Flag 1 Real 2 Comp
175. D 4 4 1 1 N A N A 5 8 14951E 06 DISP DCID 5 5 1 1 N A N A 6 6 63099E 06 DISP DCID 6 6 1 He N A N A 7 6 33147E 01 DISP DCID 7 7 1 1 N A N A 8 2 69576E 01 DISP DCID 8 8 1 1 N A N A 9 7 30348E 01 VON MISES STRESS 1 1 1 ROD 1 10 9 99997E 01 VON MISES STRESS 2 1 1 ROD 2 11 6 70627E 01 VON MISES STRESS 3 1 1 ROD 3 12 7 28571E 01 VON MISES STRESS 4 1 1 ROD 4 ASTROS OUTPUT FEATURES 8 27 USER S MANUAL ordering in the active constraint summary is not necessarily the order that constraints appear in the sensitivity matrices the DESIGN module or other discipline dependent output Finally in interpreting the constraint values the user must be aware of some features of ASTROS design constraints The constraints in ASTROS are all formulated such that a value greater than zero repre sents a violated constraint Also all the constraints are normalized in some manner by the design allowable The normalization has been formulated in such a way as to provide the best behavior under the linear approximations used in the approximate optimization problem but this has the effect of obscuring the physical meaning of the constraint The user is referred to the Theoretical Manual for the exact form of each constraint 8 28 OUTPUT FEATURES ASTROS USER S MANUAL 8 2 4 Flutter Normal Modes Response Quantities The solution control print option Roots for flutter selects that the root extraction summary for flutter analyses be printed In
176. D The reduce set identification number Integer gt 0 ID Grid or scalar point identification number Integer gt 0 Cc Component number zero or blank for scalar points any unique combination of the digits 1 through 6 for grid points Remarks 1 Coordinates specified on this entry form members of a mutually exclusive set They may not be specified on other entries that define mutually exclusive sets 2 In many cases it may be more convenient to use OMIT1 ASET Or ASET1 entries 7 172 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description Format and Example OMIT1 Omitted Coordinates Alternate Form OMIT1 Defines degrees of freedom that the user desires to omit from the problem through matrix partitioning Used to reduce the number of independent degrees of freedom 1 2 3 4 5 6 7 8 9 10 OMIT1 SETID C GID1 GID2 GID3 GID4 GID5 GID6 CONT CONT GID7 GID8 etc OMIT1 3 2 1 3 10 9 6 5 ABC BC 7 8 Alternate Form T 2 3 4 5 6 7 8 9 10 OMIT1 SETID C GID1 THRU GID2 Field Contents SETID The reduce set identification number Integer gt 0 C Component number Any unique combination of the digits 1 through 6 with no embedded blanks when point identification numbers are grid points must be null or zero if point identification numbers are scalar points GIDi Grid or scalar p
177. D2 GID3 GID4 GID5 GID6 GID7 CONT CONT GID8 GID9 etc GRIDLIST 100 1001 1010 1020 Alternate Form 2 3 4 5 6 7 8 9 10 GRIDLIST SID GID1 THRU GID2 Field Contents SID Set identification number referenced by Solution Control Integer gt 0 GIDi Grid scalar or extra point id at which outputs are desired Integer gt 0 Remarks 1 In order to be used the SID must be referenced by Solution Control If the alternate form is used GID2 must be greater than or equal to GID1 2 3 Nonexistent points may be referenced and will result in no error message 4 Any number of continuations is allowed ASTROS THE BULK DATA PACKET 7 147 GUST Input Data Entry USER S MANUAL GUST Aerodynamic Gust Load Description Description Defines a stationary vertical gust for use in aeroelastic analysis Format and Example 1 2 3 4 5 7 8 9 10 GUST SID GLOAD WG XO v QDP MACH CONT CONT SYMXZ SYMXY GUST 133 61 1 0 0 1 4 13 9 0 9 ABC BC 1 0 Field Contents SID Gust set identification number Integer gt 0 GLOAD The SID of a TLOAD or RLOAD data entry which defines the time or frequency depend ence Integer gt 0 WG Scale factor gust velocity forward velocity for gust velocity Real 0 XO Location of reference plane in aerodynamic coordinates Real V Velocity of vehicle Real gt 0 0 QDP Dynamic pressure Real gt 0 0 MACH Mach number Real gt 0
178. D4 CTRIA3 EIDi Element identification numbers Integer gt 0 or blank PREFi Linking factor for the associated EID Real Remarks 1 The shape function identification is referenced by the DESvarRs entry to connect the global variable to the shape 2 Thelinking factors define a shape function to be used as the global design variable 3 Designed properties e g thicknesses of elements listed on SHAPE entries will be set to unity to ensure proper shape function definition that is the PREF values define the shape to be applied toa uniform property distribution 4 If PBAR1 cross sectional parameters are used as design variables the SHAPEM Bulk Data entry must be used 7 216 THE BULK DATA PACKET ASTROS USER S MANUAL SHAPEM Input Data Entry SHAPEM Description Defines element connectivity entries and their local variables associated with a design variable Format and Examples 1 2 3 4 5 6 7 8 9 10 SHAPEM SHAPEID ETYPE EID1 DVSYM1 PREF1 EID2 DVSYM2 PREF2 CONT CONT EID3 DVSYM3 PREF3 etc SHAPEM 10 CROD 12 A 1 0 22 A 0 5 Field Contents SHAPEID Shape function identification Integer gt 0 ETYPE Character input identifying the element type One of the following CELASi CMASSi CONM2 CBAR CROD CONROD CSHEAR CQDMEM1 CTRMEM CQUAD4 CTRIA3 EIDi Element identification numbers Int
179. DCONDSP bulk data entries which define displacement con straints p Set identification of DCONF constraint functions Remarks 1 If any discipline has a caseid then all disciplines must have a caseid All caseid values must be unique but they need not be in any particular order Disciplines are implicitly numbered from 1 to n if no caseid values are specified The caseid is only used as a reference from user defined functions in the F unction Packet The sum of all the loads forms a single right hand side for a statics analysis At least one of the load types must be present The CONSTRAINT section is optional Gravity forces may be included indirectly if referenced by the LOAD bulk data entry uF WN For compatibility the alternate form of constraint specification shown below is also allowed Its use is however discouraged STATICS MECH i THERMAL j GRAVITY k CONSTRAINT STRESS m STRAIN n GENERAL 0 ASTROS THE SOLUTION CONTROL PACKET 5 41 SUBTITLE USER S MANUAL Solution Control Command SUBTITLE Description Defines a subtitle which will appear in the output Hierarchy Level Label information Format and Example SUBTITLE n SUBTITLE SUPERSONIC DESIGN CONDITION Option Meaning n Any descriptive information can be inserted here Remarks 1 SUBTITLE information is used until it is superseded 2 The SUBTITLE command is optional 3 Subtitles are limited to 72 characters 5 42 THE SOLUTION CONTR
180. DCONF Bulk Data entries defining subcase independent functions variable increment Av for finite difference computa 1 None of the options are required 2 MAXITER and CNVRGLIM are global parameters that apply to the MP and FSD strategies 3 MOVLIM and WINDOW control the move limits for MP WINDOW is only useful for LOCAL design variables that need to cross between positive and negative values 4 NRFAC and EPS control the constraint deletion algorithm for mp both values are always applied 5 32 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL Solution Control Command PRINT PRINT Description Specifies the required output file processing for the print file or CADDB database Hierarchy Level Various Format and Examples PRINT Form FREQ a ITER b MODE c TIME d ACCE Form FREQ a ITER b TIME d e AIRD Form ITER b MODE c TIME d f BUCK ITER b ag CGRA ITER b h DCON ITER b i DISP Form FREQ a ITER b MODE c TIME d j ENER Form FREQ a ITER b MODE c TIME d k FORC Form FREQ a ITER b MODE c TIME d 1 GDES ITER b m GPFO Form FREQ a ITER b MODE c TIME d n GPWG ITER b n1 KSNS ITER b o LDES ITER b p LOAD Form FREQ a ITER b MODE c TIME d q MASS ITER b r MSNS ITER b t OGRA ITER b u QHH ITER b MODE c x QHJ ITER b MODE c y
181. E FREQ or BOTH Default is TIME FLIM Frequency load interpolation method Character string LINEAR or CUBIC Default is LINEAR Remarks 1 SID must be selected by a FFT option on a TRANSIENT command in solution control 2 TIME is the period for periodic dynamic loads defined in the time domain For non periodic loads T is the total time duration of the excitation plus any quiet portion desired for response decay T may be larger than the time duration defined by TLOAD1 or TLOAD2 data in which case the forcing function will be automatically set to zero for the additional time 3 NT should be a power of 2 i e NT 2 m m 1 2 or NT 2 4 8 If NT is not a power of 2 it will be automatically set to the next highest power of 2 value 4 The incremental frequency A F required by the FFT algorithm is 1 T The value of A F may be adjusted by the user with the RDELTF factor However the most accurate results are normally obtained with the default case of RDELTF 1 0 5 The frequency duration required by the FFT algorithm is F NT 2 T This is the frequency duration used when the default value of RF 1 0 is used If RF lt 1 0 the response between RF and 1 0 is set to zero when using the inverse F ourier transform to compute time domain responses 6 The frequency list used in the frequency response calculations is generated using a constant incre mental frequency of del F RDELTF AF and the total frequency duration is
182. E ORATE S DEG 0015 N A N A 0923 0923 1004 2034 2034 1999 PITCH RATE QRATE S RAD 0870 N A N A 5 2878 5 2878 5 7517 11 6513 11 6513 11 4535 CONTROL SURFACE ELEV 1 DEG 0012 N A N A 0118 0118 0128 0431 0431 0420 CONTROL SURFACE ELEV 1 RAD 0670 N A N A 6775 6775 7346 2 4704 2 4704 2 4069 COMPUTED DRAG VALUES ARE INCLUDED FOR COMPLETENESS AND MODEL CHECK OUT ONLY USE CAUTION IN INTERPRETING THEIR PHYSICAL VALIDITY VALUES MARKED N A CANNOT BE COMPUTED UNLESS THE CORRESPONDING DOF IS SUPPORTED TRIM RESULTS FOR TRIM SET 100 OF TYPE PITCH MACH NUMBER 8 00000E 01 DYNAMIC PRESSURE 6 50000E 00 VELOCITY 9 86400E 03 TRIM PARAMETERS DEFINITION LABEL FLEXIBLE RIGID LOAD FACTOR NZ 3 09119E 03 3 09119E 03 USER INPUT PITCH RATE QRATE 1 56990E 01 1 56990E 01 DEG S USER INPUT ANGLE OF ATTACK ALPHA 1 26089E 00 2 17052E 00 DEG COMPUTED CONTROL SURFACE ROTATION ELEV 2 11388E 00 2 63485E 00 DEG COMPUTED THICKNESS CAMBER THKCAM 1 00000E 00 1 00000E 00 USER INPUT 1 The stability derivative for the rigid aerodynamic model as computed directly from the forces acting on the aerodynamic boxes termed DIRECT in the output This output al ways appears since it comes directly from the aerodynamic model 2 The stability derivative for the rigid aerodynamic model as computed from the forces transformed to the structural degrees of freedom termed SPLINEd in the output This output only appears if the
183. EID1 THRU EID2 Field Contents LID Load set identification number I nteger gt 0 P Pressure value Real 1 2 EIDi Element identification numbers I nteger gt 0 Remark 3 Remarks 1 The pressure intensity is the load per unit surface area 2 The direction of the pressure is computed according to the right hand rule using the grid point sequence specified on the element connection entry If the surface of an element is curved the direction of the pressure may vary over the surface Refer to PLOAD4 for a more general pressure load capability 3 For compatibility with commercial NASTRAN products ASTROS element type identifiers are not used Therefore the referenced element identification numbers must be unique among the plate element types 4 Equivalent grid point loads are computed which depend on the specific element geometry and type A uniform pressure may not result in equal grid point loads 7 194 THE BULK DATA PACKET ASTROS USER S MANUAL PLOAD4 Input Data Entry PLOAD4 Plate element static pressure load Description Defines a load on the surface of a TRIA3 or QUAD4 element Format and Examples cl 2 3 4 5 6 7 8 9 10 PLOAD4 LID EID P1 P2 P3 P4 CONT CONT CID V1 V2 v3 PLOAD4 101 2043 15s 18 23 6 12 4 ABC BC 52 1 0 0 0 0 0 Alternate Form 1 2 3 4 5 6 7 8 9
184. EN ASTROS AND NASTRAN BULK DATA 7 11 T t BUEKIDATA DESCRIPTIONS ie Ai it a o o as a a 7 13 OUTPUT FEATURES 00 a ee eee ee a 8 1 8 1 SYSTEM CONTROLLED OUTPUT 2 2 8 2 8 1 1 Default Output Printed by Modules 2 o eee ee 8 2 8 1 2 Error Message Output a 8 6 8 2 SOLUTION CONTROL OUTPUT OPTIONS 8 8 8 2 1 Element Response Quantities 2 0 000 o o 8 9 8 2 1 1 Aerodynamic Element Output 0 000022 eee eee 8 10 8 2 1 2 Bar Element Output 2 ee 8 11 8 2 1 3 ELAS Element Output ee 8 13 8 2 1 4 IHEX1 Element Output ee 8 13 8 2 1 5 IHEX2 Element Output 2 2 2 t a ale eA aa l a aa ada a ap a 8 15 8 2 1 6 IHEX3 Element Output a 8 16 ASTROS USER S MANUAL 8 2 1 7 Rod Element Output aoaaa 8 17 8 2 1 8 QDMEM1 TRMEM Element Output a aaa aaa a 8 17 8 2 1 9 QUAD4 TRIA3 Element Output a 8 19 8 2 1 10 Shear Panel Output e 8 22 8 2 2 Nodal Response Quantities o 8 22 8 2 3 Design Variables and Design Constraints o pees 8 25 8 2 4 Flutter Normal Modes Response Quantities eae 8 29 8 2 5 Aeroelastic Trim Quantities o e ee 8 30 8 3 SUMMARY OF SOLUTION RESULTS 8 34 8 4 OTHER SELECTABLE QUANTITIES 0 4 8 36 8 4 1
185. ER before exceeding GFLUT This allows lightly damped modes to be filtered even if GFLUT otherwise defines a flutter crossing i e has damping of zero The figure below shows two example curves GFLUT is 0 005 and GFILTER is 0 03 Point 1 on Curve A would not be considered a flutter crossing even though the curve exceeds GFLUT This occurs because the damping was not less than GFILTER before GFLUT was exceeded Point 2 on Curve B would be reported as a flutter crossing at the velocity where the curve crosses GFLUT GFLUT and GFILTER have no effect during optimization 0 2 0 1 SELUT 0 005 Damping a Curve B 0 1 0 2 FOR BIRD 2000 10000 Velocity ASTROS THE BULK DATA PACKET 7 133 FORCE Input Data Entry USER S MANUAL FORCE Static Load Description Defines a static load at a grid point by specifying a vector Format and Example 1 2 3 4 5 6 7 8 9 10 FORCE SID G CID F N1 N2 N3 FORCE 2 5 6 229 0 0 1 0 0 0 Field Contents SID Load set identification number Integer gt 0 G Grid point identification number Integer gt 0 CID Coordinate system identification number Integer gt 0 or blank Default 0 F Scale factor Real Ni Components of a vector measured in the coordinate system defined by CID Real must have at least one nonzero component Remarks 1 The static load applied to grid point G is given by f F N
186. ERO2 1500 2 100 4 99 1 ABC BC 1 0 100 30 175 Field Contents EID Element identification number Integer gt 0 PID Property identification number Integer gt 0 CP Coordinate system for locating point 1 Integer gt 0 or blank NSB Grid point identification number of connection points Integer gt 0 NINT Number of interference elements if a positive number is given NSB equal divisions are assumed if zero or blank see LSB for a list of divisions Integer gt 0 or blank LSB Identification number of an AEFACT data entry for slender body division points used only if NSB is zero or blank Integer gt 0 or blank LINT Identification number of an AEFACT data entry containing a list of division points for interference elements used only if NINT is zero or blank Integer gt 0 or blank IGID Interference group identification aerodynamic elements with different IGID s are uncoupled Integer gt 0 XL YU Zi Location of points 1 and 4 in coordinate system cP Real X12 Edge chord lengths in aerodynamic coordinate system Real gt 0 and not both zero Remarks 1 Point 1is the leading point of the body 2 All CAERO1 panels and CAERO2 bodies in the same group IGID will have aerodynamic interac tion At least one interference element is required for each aerodynamic body specified by this entry 4 Element identification numbers on the aerodynamic bodies must have the following sequence A Panels first B Z
187. ET ASTROS USER S MANUAL Input Data Entry CBAR Simple Beam Element Connection CBAR Description Defines a simple beam element BAR of the structural model Format and Example Jl 2 3 4 5 6 7 8 9 10 CBAR EID PID GA GB X1 GO X2 X3 TMAX CONT CONT PA PB W1A W2A W3A W1B W2B W3B CBAR 2 39 7 3 13 23 123 Field Contents EID Unique element identification number Integer gt 0 PID Identification number of a PBAR property entry Default is EID unless BAROR entry has nonzero entry in Field 3 Integer gt 0 GA GB Grid point identification numbers of connection points Integer gt 0 Xi Components of vector v at end A measured at end A parallel to the components of the displacement coordinate system for Ga to determine with the vector from end A to end B the orientation of the element coordinate system for the BAR element Real GO Grid point identification number to optionally supply xi Integer gt 0 Direction of orientation vector is GA to Go TMAX Maximum allowable cross sectional area in design Real gt 0 0 or blank Default 10 PA PB Pin flags for bar ends A and B respectively up to 5 of the unique digits 1 through 6 W1A W2A W3A W1B W2B W3B ASTROS anywhere in the fields with no embedded blanks Integer gt 0 or blank Used to remove connections between the grid point and selected degrees of freedom of the bar The degr
188. ET GDRi Number of degrees of freedom in the k set in dynamic reduction Set in GDR1 LSIZE GDR1 The number of set degrees of freedom GDR1 An output from GDR1 indicating the number of eigenvalues below the maximum NEIV GDR2 frequency specified for dynamic reduction Logical flag equal to negative one if dynamic reduction is selected for the current NGDR BOUND boundary condition BOUND Logical flag equal to the number of degrees of freedom in the multipoint constraint set NMPC ABOUND for the current boundary condition BOUND NOMIT ABOUND USER S MANUAL Table 4 4 Integer Design Parameters NAME MODULES DESCRIPTION FSDE SOLUTION The last iteration to use fully stressed design Output from SOLUTION FSDS SOLUTION The first iteration to use fully stressed design Output from SOLUTION FSD Parameter set in the MAPOL sequence indicating the maximum number of resizing MAXITER SOLUTION cydes that are to be performed Set through the Solution Control OPTIMIZE command ACTCON Def 15 MPE SOLUTION The last iteration to use mathematical programming Output from SOLUTION MPS SOLUTION The first iteration to use mathematical programming Output from SOLUTION FSD The number of active stress and displacement constraints in the current active boundary NACSD ABOUND condition Used to select either the virtual load or grad
189. ETYPE Character input identifying the element type One of the following CELAS1 CELAS2 CMASS1 CMASS2 CONM2 CBAR CROD CONROD CSHEAR C QDMEM1 CTRMEM CQUAD4 CTRIA3 EIDi Element identification numbers Integer gt 0 or blank DVSYMi Symbol defining the local design variable Remarks 2 and 3 Remarks 1 The LINKID is referenced by DESVARP data to connect the global design variable to the local vari ables 2 Thefollowing symbols may be used for the different types of elements ELEMENTS ALLOWABLE pvsym VALUES ELASi K MASSi CONM2 M BAR PBAR ROD CONROD A BAR PBAR1 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 SHEAR QDMEM1 TRMEM QUAD4 TRIA3 T 3 If all elements to be linked have only one possible pvsyM e g K the ELIST Bulk Data entry may be used ASTROS THE BULK DATA PACKET 7 127 EPOINT Input Data Entry EPOINT Extra Point List USER S MANUAL Description Defines extra points of the structural model for use in dynamics problems Format and Example 1 2 3 4 5 6 7 8 9 10 EPOINT SETID ID1 ID2 ID3 ID4 ID5 ID6 1D7 CONT CONT ID8 ID9 etc EPOINT 1000 3 18 1 4 16 2 Alternate Form 1 2 3 4 5 6 7 8 9 TO EPOINT SETIC ID1 THRU ID2 Field Contents SETID Extra point sets identification numbers Integer gt 0 IDi Extra point identification number Integer gt 0
190. Entry DCONFLT Flutter Constraint Definition Description Defines a flutter constraint in the form of a table ner lt 0 0 Format and Example 1 2 3 4 5 6 g 8 9 10 DCONFLT SID VTYPE GFACT v1 GAM1 v2 GAM2 CONT CONT v3 GAM3 v4 GAM4 etc DCONFLT 100 EQUIV 0 1 0 0 0 0 30 0 05 Field Contents SID Constraint set identification the constraints are referenced by the design constraint id in Solution Control Integer gt 0 VTYPE Nature of the velocity referred to in the table Either TRUE for true velocity or EQUIV for equivalent air speed Default TRUE GFACT Constraint scaling factor Real gt 0 0 Default 0 10 vi Velocity value Real gt 0 0 GAMi Required damping value Real Remarks 1 Flutter constraints are selected in Solution Control with the discipline option DCON SID A negative value of GAMi refers to a stable system Thevi must be in either ascending or descending order Linear interpolation is used to determine Gama for a given velocity At least two pairs must be entered DU FW N J umps between two points vi Vit1 are allowed but not at the end points If the jump point is used the average of the two GAMi will be returned ASTROS THE BULK DATA PACKET 7 79 DCONFRQ Input Data Entry DCONFRQ Description Defines a frequency constraint of the form f lt fan or f 2 fall Format and Example USER S MANUAL
191. F RF F ASTROS THE BULK DATA PACKET 7 129 FLFACT USER S MANUAL Input Data Entry FLFACT Aerodynamic Physical Data Description Used to specify density ratios velocity lists and reduced frequencies for FLUTTER analysis Format and Example 1 2 3 4 5 6 7 8 9 10 FLFACT SID F1 F2 F3 F4 F5 F6 F7 CONT CONT F8 F9 etc FLFACT 97 23 lt 7 3 5 Field Contents SID Set identification number Integer gt 0 Fi Aerodynamic factor Real Remarks 1 Only the factors selected by a FLUTTER data entry will be used 2 Embedded blank fields are forbidden 3 Parameters must be listed in the order in which they are to be used within the looping of FLUTTER analysis 4 All FLFACT entries having the same SETID will be treated as a single set 7 130 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry FLUTTER Aerodynamic FLUTTER Data FLUTTER Description Defines data needed to perform FLUTTER analysis Format and Example A 2 3 4 5 6 7 8 9 10 FLUTTER SID METHOD DENS MACH VEL MLIST KLIS EFFID CONT CONT SYMXZ SYMXY EPS CURFIT NROOT VTYPE GFLUT GFILTER FLUTTER 19 PKIT 119 0 85 319 ABC BC 1 0 01 CUBIC EQUIV Field Contents SID Set identification number See Remark 1 Integer gt 0 METHOD FLUTTER analysis method P
192. GL Constraint for RDISP XMAG SDOT RDISP GLIST1 GLIST ENDFUNC T2 SI2 X1 DISP GLIST ST2 X1 COORD GL ST2 X2 DISP GLIST ST2 X2 COORD GL ST2 X3 DISP GLIST ST2 X3 COORD GL relative disp XMAG GLST GL SDOT GLST GL T1 GLST GLIST2 GLST GLIST2 T1 COORD GLIST1 X1 DISP GLIST1 T1 T1 X1 T2 COORD GLIST1 X2 DISP GLIST1 T2 T1 X2 T3 COORD GLIST1 X3 DISP GLIST1 T3 T1 X3 The Bulk Data Packet defines two grid lists references design constraint 101 which links the design variable RDISP to the Functional Packet and defines two arguments The arguments identify the GRIDLISTs to use in the function BEGIN BULK GRIDLIST 1 5 THRU 20 GRIDLIST 2 105 THRU 120 DCONF 101 RDISP DCN1 DCN1 GLISTI 1 GLIST2 2 ENDDATA Example 4 Constraint Instantiation with Explicit Subcases The following example computes five constraints from subcases defined independently of the analysis discipline The function evaluates the expression which takes the displacement component T3 and divides by 2 0 for a set of grid points recovered for a set of unique displacements The solution 6 18 THE FUNCTION PACKET USER S MANUAL USER S MANUAL control packet references the functional design constraint 101 in the Bulk Data Packet for the STATIC
193. GPRT The print utility UTGPRT has been provided in order to view particular matrices whose rows correspond to the structural degrees of freedom In general these matrices are very large and virtually impossible to interpret without some additional formatting beyond that which is available for more general matrix prints Therefore for the supported matrix entities the matrix columns are printed in a form similar to that used for the nodal response quantities as presented in Section 5 2 2 The UTGPRT utility has the following calling sequence CALL UTGPRT BC USET BC mat1 mat2 mat10 where up to ten matrix arguments may be supplied The Bc integer argument and the name of the USET entity for the Bc th boundary condition identifies the associated boundary condition so that the utility can make use of the USET entity in formatting the output The following entities are supported DKUG DMUG DPVJ DUG DPGV DUGV DPTHVI DPGRVI PG DFDU The utility keys off the entity names so the above names must be used although the matrices can be subscripted if the user wishes The reader is referred to the Programmer s Manual for additional informa tion on the data contained in these entities 8 5 3 General Matrix Print Utility UTMPRT The matrix print utility UTMPRT has been written such that any data base matrix entity can be printed to the output file The calling sequence for UTMPRT is CALL UTMPR
194. GX stress of QUAD4 100 ASTROS will ensure that the stress component is computed Following the normal constraint screening process active synthetic constraints along with these data structures are used to compute required sensitivities This is done by explicitly differentiating the user functions and using the chain rule to compute constraint gradients from the necessary response deriva tives The response gradients are computed in the normal ASTROS manner The following sections describe the relationship between the Solution Control Packet including the OPTIMIZE command the Bulk Data Packet and the F unction Packet 6 2 1 Solution Control Packet The Solution Control packet is used to select functions for use as either design constraints or as the objective function The relevant commands are described in the following sections 6 2 1 1 Synthetic Objective Function The ASTROS OPTIMIZE command is used to specify the objective function and the type of optimization to be performed The general form of the command is set id OPTIMIZE WEIGHT MINIMIZE ECTIVE MAXIMI ZE DCFUNCTION indep set id other options WEIGHT is a keyword that selects the weight as objective function the original ASTROS objective func tion while set id is the identification number of ONE DCONF Bulk Data entry that may be used to define a synthetic objective The DCONF entry MUST be one that resolves to a single scalar value
195. ID is selected by Solution Control Command BOUNDARY INERTIA N c Use 0 as the grid point identification number to select the origin of the basic coordinate system as one of the j set degrees freedom 7 152 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry LDVLIST LDVLIST Local Design Variable List Description Defines a list of local design variables for which outputs are desired Format and Example dl 2 3 4 5 6 7 8 9 10 LDVLIST SID ETYPE LAYER DVSYMBL EID1 EID2 EID3 EID4 CONT CONT EID5 EID6 etc LDVLIST 100 QUAD4 2 100 100 200 300 700 Alternate Form I 2 3 4 5 6 7 8 9 10 LDVLIST SID ETYPE LAYER EID1 THRU EID2 Field Contents SID Set identification number referenced by Solution Control Integer gt 0 ETYPE Character input identifying the element type One of the following BAR MASS ROD TRMEM CONM2 QDMEM1 SHEAR ELAS QUAD4 TRIA3 LAYER Layer number if element is composite laminate Integer gt 0 or blank DVSYMBL Character symbol specifying the PBAR1 cross sectional parameter if ETYPE iS PBAR D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 EIDi Element identification number Integer gt 0 or blank Remarks 1 In order to be used the SID must be referenced by Solution Control 2 3 4 selected wn ASTROS If
196. IEW 2 E O A e oN oe Sarl eee 2 2 2c Executing ASTROS a A A A A A A Gk aA 2 2 2 1 2 The ASTROS Configuration and Preference Files 0 2 2 2 1 2 1 The Format of Preference Files 2 3 2 1 3 Configuration Parameters a 2 3 2 1 4 The Configuration Sections e 2 3 2 1 4 1 The Host Configuration Section o e e e 2 3 2 1 4 2 The eBASE Kernel Configuration Section 0 o 2 5 2 1 4 3 The ASTROS Configuration Section o 00000020 2 5 2 1 4 4 The eBASE APPLIB and eBASE MATLIB Sections 2 2 5 2 1 4 5 The eSHELL Configuration Section 0 ee 2 5 2 1 5 Dynamic M6MOry x cu eae da ee aa RA ee a 2 5 2 1 6 The eBASE Database ee 2 6 2 1 6 1 The Two Types of Databases 2 eo 2 6 2 1 6 2 The Logical and Physical Views of the Database 2 6 2 1 6 3 The Physical Model e e 2 6 2 1 6 4 ASSIGNing Databases e 2 6 2 1 6 5 Database File Names e eo 2 6 2 1 6 6 Very Large Databases o 2 7 2 1 7 Host Computer Dependencies e 2 7 2 2 UNIX BASED COMPUTERS lt a yaa aa de da Ke De SS 2 7 2 2 1 Executing ASTROS a aa a E aon E a Dan aa i E aa 2 7 222 AS TROS File NaMES 5 paa a RA Oe ES ad heh ee a a Ma
197. IS SEGMENT TRANSIENT ANALYSIS BOUNDARY 1 TIME 4 9999997E 02 STRESSES IN BAR ELEMENTS BAR ELEMENT SAL SA2 SA3 SA4 AXIAL SA MAX SA MIN M S T ID sB1 SB2 SB3 SB4 STRESS SB MAX SB MIN M S C 106 2 810616E 03 0 000000E 00 2 810616E 03 2 810616E 03 0 000000E 00 2 810616E 03 2 810616E 03 1 7E 38 7 498176E 02 0 000000E 00 7 498176E 02 7 498176E 02 7 498176E 02 7 498176E 02 1 7E 38 1 ASTROS VERSION 9 0 03 03 93 P 23 FINAL ANALYSIS SEGMENT TRANSIENT ANALYSIS BOUNDARY 1 TIME 9 9999998E 03 STRAINS IN BAR ELEMENTS BAR ELEMENT SAL SA2 SA3 SA4 AXIAL SA MAX SA MIN ID SB1 SB2 SB3 SB4 STRAIN SB MAX SB MIN 106 1 963023E 04 0 000000E 00 1 963023E 04 1 963023E 04 0 000000E 00 1 963023E 04 1 963023E 04 5 857950E 10 0 000000E 00 5 857950E 10 5 857950E 10 5 857950E 10 5 857950E 10 1 ASTROS VERSION 9 0 03 03 93 P 31 FINAL ANALYSIS SEGMENT TRANSIENT ANALYSIS BOUNDARY 1 TIME 9 9999998E 03 FORCES IN BAR ELEMENTS BAR ELEMENT BEND MOMENT END A BEND MOMENT END B SHEAR AXIAL ID PLANE 1 PLANE 2 PLANE 1 PLANE 2 PLANE 1 PLANE 2 FORCE TORQUE 106 0 000000E 00 3 195801E 00 0 000000E 00 9 536743E 06 0 000000E 00 6 391621E 01 0 000000E 00 0 000000E 00 1 ASTROS VERSION 9 0 03 03 93 P 31 FINAL ANALYSIS SEGMENT TRANSIENT ANALYSIS BOUNDARY 1 TIME 9 9999998E 03 ELEMENT STRAIN ENERGIES BAR ELEMENTS TOTAL ENERGY OF ALL ELEMENTS IN THE SUBCASE 4 388508E 02 ELEMENT ID STRAIN ENERGY PERCENT OF TOTAL 101 1 430531E 03 3 259722 102 4 057172E
198. ISES STRESS 7 1 1 QDMEM1 5 76223E 01 VON MISES STRESS 8 1 id QDMEM1 9 77223E 01 VON MISES STRESS 10 1 1 ROD 9 81333E 01 VON MISES STRESS 28 1 1 SHEAR SUMMAR Y OF ACTIVE CONSTRAINTS AFTER ANALYSIS 4 OF A MAXIMUM 16 12 CONSTRAINTS RETAINED OF 60 APPLIED THE APPROXIMATE OPTIMIZATION PROBLEM WAS CONVERGED WITH FEASIBLE CONSTRAINT CRITERIA ACTIVE CONSTRAINT CRITERIA CURRENT MAXIMUM CONSTRAINT VALUE TO TERMINATE 5 00000E 04 AND 7 50000E 04 CTLMIN OTIS oo eret 4 97155E 04 2 25000E 03 lt 4 97155E 04 lt ASTROS OPTIMIZATION HAS CONVERGED FO II IO ISIC IO ISI ICI IO II ICI IO III ICI IO IOI ICI IO IOI ICI IO IO I ICI IO IO A A ae i CONSTRAINT RETENTION ALGORITHM SUMMARY RFAC 3 000 EPS 100 NDV 4 OF CONSTRAINTS RETAINED BY RFAC 12 ii CUTOFF CONSTRAINT VALUE 981 x ADDED WITH VALUES GREATER THAN EPS 0 dd OF ADDITIONAL MINIMUM THICKNESS CONSTRAINTS RETAINED ONLY FOR CONTROLLING MOVE LIMITS DCONTHK 0 ORIO ROO RIOR ROO OOOO ICI ICI IO II ICI IO ROO ROO RIO 1 00000E 03 EID LAYR N A N A 13 14 16 17 20 21 23 26 2 29 Table 8 6 Approximate Optimization Summary Hk kK ASTROS APPROXIMATE OPTIMIZATION SUMMARY EK ITERATION 1 ai ae RESIZING METHOD MATHEMATICAL PROGRAMMING ae SS DESIGN VAR MOVE LIMIT 2 000000 EE UPPER BOUND PERCENT MOVE 1 000000 PERCENT CRITERION 1 OBJECTIVE CHANGE g CURRENT
199. ITERLIST Iteration List LDVLIST sid LDVLIST Local design variable List MACHLIST sid MACHLIST Mach List MODELIST sid MODELIST Mode List PLYLIST sid PLYLIST Ply List VELOLIST sid VELOLIST Velocity List ASTROS THE FUNCTION PACKET 6 7 USER S MANUAL COORD gad GRIDLIST sid The COORD function retrieves the current value of a geometric coordinate X1 X2 or x3 for the requested grid points referenced either as a grid value or a grid list GRIDLIST The grid point will be retrieved in the selected coordinate system cid If the cid reference is omitted then the coordinate value is returned in the input coordinate system of the GRID point i e the cp field of the Bulk Data entry GRID A cid of O requests that the coordinate be returned in the basic coordinate system The interpretation of x1 x2 and x3 depends on whether the cid coordinate system is rectangular cylindrical or spherical In addition to the grid point geometry there are functions which return informa tion about the specific finite elements These are a l eid plyid ELEMLIST elem_sid PLYLIST ply_sid CENTROID ake x2 cid ELEMLIST elem_sid X3 Ai eid plyid ELEMLIST elem_sid PLYLIST ply sid ELEMLIST elem_sid PLYLIST ply sid eid plyid The THICK function returns the thickness of the requested two dimensional element The CENTROID function returns the ce
200. If an ASTROS analysis is not using the standard solution then a MAPOL program is required as the first part of the input data stream The MAPOL data packet must be formed as shown MAPOL lt option list gt As introduced in Chapter 1 all bold capitalized words e g MAPOL must appear exactly as they are written A symbol enclosed in angle brackets e g lt opt ion list gt represents one or more choices to be made If the symbol is enclosed in square brackets e g lt id gt the choice is optional The MAPOL command which must be the first statement in the program selects compiler options These options are shown in Table 9 1 where the default option options are indicated by boldface Table 9 1 MAPOL Command Options NAME OPTION LIST Lists the MAPOL source program NOLIST a Selects or deselects execution after program compilation As an example the statement will cause the MAPOL program to be compiled and executed with no listings produced while the statement MAPOL NOGO will cause the MAPOL program to be compiled and a listing of the source code produced After compila tion ASTROS will terminate without executing the program 9 2 MAPOL PROGRAMMING ASTROS USER S MANUAL 9 1 3 THE STANDARD ASTROS SOLUTION As mentioned earlier the ASTROS multidiscpliniary solution algorithm is a MAPOL program The code resides on the ASTROS system database It is retrieved and used
201. If the optional OBJECTIVE specifier is omitted WEIGHT is selected by default The OPTIMIZE and MINIMIZE options direct ASTROS to minimize the objective function while MAXIMIZE directs the opposite The indep set id allows the user to specify a single subcase independent functional constraint See Chap ter 3 for details about the other options 6 2 THE FUNCTION PACKET USER S MANUAL USER S MANUAL To illustrate the use of the OPTIMIZE command consider the following examples For the standard weight minimization problem the following are equivalent OPTIMIZ CNVRGLIM 1 3 L OPTIMIZE E WEIGHT MAXITER 10 CNVRGI WEIGHT MAXITER 10 CNVRGI MINIMIZE MINIMIZE 101 MAXIT OPTIMIZE 101 MAXIT MAXIMIZE ECTIVE 2001 MAXITI RGLIM 1 5 MOVLIM 6 2 1 2 Synthetic Design Constraints Subcase independent constraints such as weight and thickness may be selected directly using the DCFUNCTION option of the OPTIMIZE command OPTIMIZE DCFUNCTION indep set id The DCFUNCTION defines a Design Constraint Function n addition the user has a mechanism to specify subcase dependent constraints by using the DCFUNCTION option within the four disciplines e STATICS Static structural analysis MODES Normal modes of vibration e SAERO Steady state aeroelastic analysis e FLUTTER Aeroelastic stability
202. Ifno IC set is selected all initial conditions are assumed zero 3 Initial conditions for coordinates not specified on rc entries will be assumed zero 4 Initial conditions may be used only in direct formulation In a modal formulation the initial condi tions are all zero ASTROS THE BULK DATA PACKET 7 149 ITERLIST USER S MANUAL Input Data Entry ITERLIST Iteration List Description Defines a list of iteration steps for which outputs are desired Format and Example 1 2 3 4 5 6 7 8 9 10 ITERLIST SID ITER ITER ITER ITER ITER ITER ITER CONT CONT ITER ITER etc ITERLIST 100 1 2 3 5 7 9 Alternate Form 2 3 4 5 6 7 8 9 10 ITERLIST SID ITER THRU ITER Field Contents SID Set identification number referenced by Solution Control Integer gt 0 ITER Iteration step number Integer gt 0 or blank Remarks 1 In order to be used the SID must be referenced by Solution Control 2 Nonexistent iteration steps may be referenced and will result in no error message 3 Any number of continuations is allowed except when using the alternate form which allows no continuations 7 150 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description JSET Select Coordinates for the j set JSET Defines coordinates degrees of freedom that the us
203. K DATA PACKET ASTROS USER S MANUAL DCONEPP Input Data Entry DCONEPP Principal Strain Constraint Definition Description Defines a principal strain constraint by specifying element property identification numbers Format and Example 2 3 4 5 6 7 8 9 10 DCONEPP SID ST SC ss PTYPE LAYRNUM PID1 PID2 CONT CONT PID3 PID4 etc DCONEPP 100 1 2 1 2 1 2 PBAR 100 200 ABC BC 300 400 500 Alternate Form 2 3 4 5 6 7 8 9 10 DCONEPP SID ST SC ss PTYPE LAYRNUM PID1 THRU ABC BC PID2 Field Contents SID Strain constraint set identification Integer gt 0 ST Principal strain limit in tension Real gt 0 0 SC Principal strain limit in compression Real Default sT Ss Principal strain limit in shear Real gt 0 0 PTYPE Property type Character selected from PBAR PROD PSHEAR PQDMEM1 PTRMEM PSHELL PCOMP PCOMP1 PCOMP2 LAYRNUM Layer number of a composite element Integer gt 0 or Blank PIDi Property identification numbers Integer gt 0 Remarks 1 Strain constraints are selected in Solution Control with the discipline option STRAIN sid 2 If the alternate form is used PID2 must be greater than or equal to PID1 Property identification numbers in the range which do not exist are ignored The shear strain limit ss is used only with the SHEAR element 4 Thestrain limit for compre
204. K or PKIT See Remark 2 Character Default PK DENS Identification number of an FLFACT set specifying density ratios to be used in FLUT TER analysis See Remark 3 Integer gt 0 MACH Mach number to be used in the FLUTTER analysis Real gt 0 0 VEL Identification number of an FLFACT set specifying velocities to be used in the FLUT TER analysis I nteger gt 0 MLIST Identification number of a SET1 set specifying a list of normal modes to be omitted from the FLUTTER analysis See Remark 4 Integer gt 0 or blank KLIST Identification number of an FLFACT set specifying a list of hard point reduced frequencies for the given Mach number for use in the FLUTTER analysis See Remark 5 Integer gt 0 or blank EFFID Identification number of a CONEFFF set specifying control surface effectiveness values See Remark 6 Integer gt 0 or blank SYMXZ Symmetry flags associated with the aerodynamics See Remark 7 Integer SYMXY 1 Symmetric Oor blank Asymmetric 1 Antisymmetric EPS Convergence parameter for FLUTTER eigenvalue Real Default 10 CURFIT Type of curve fit to be used in the PK FLUTTER analysis One of LINEAR QUAD CUBIC Or ORIG See Remarks 8 9 and 10 Character Default LINEAR NROOT Requests that only the first NROOT eigenvalues be found Integer or blank VTYPE Input velocities are in units of true TRUE or equivalent EQUIV speed See Remark 11 Character Default T RUE GFLUT The damping a mode must exceed to be c
205. L sequence that define the matrix reduction path for the current BOUND boundary condition BOUNDUPD ENG Updates boundary condition definitions CEIG ENG Computes the complex eigenvalues and eigenvectors of a matrix COLMERGE MAT Merges two or more submatrices into a single matrix based on column partitioning vectors COLPART MAT Partitions a matrix into two or more submatrices based on column partitioning vectors ENG Reorders constraints in boundary condition order to match the order in which constraint CONORDER sensitivities are computed DCEVAL ENG Evaluates displacement constraints in the current boundary condition DDLOAD ENG Computes the sensitivities of design dependent loads for active boundary conditions DECOMP MAT Decomposes a matrix into its triangular factors Performs redesign by math programming methods based on the current set of active constraints and constraint sensitivities DESPUNCH UTIL Writes new modified Bulk Data entries for the current design iteration to the PUNCH file ENG Assembles the direct and or modal stiffness mass and or damping matrices including extra DMA point degrees of freedom for dynamic analysis disciplines ENG Assembles the direct and or modal time and or frequency dependent loads including extra point DYNLOAD degrees of freedom for dynamic response disciplines ENG Computes the direct or modal displacements velocities and accelerations for TRANSIENT and DYNRSP FREQUENCY analyses EBKLEVAL ENG Evaluates Euler b
206. LIST 1 CLIST 101 ALLOW 0 2 ENDDATA Example 5 Multiple Function Evaluations The following example will compute 25 constraints The function evaluates the expression which takes two times the displacement component T3 for a set of grid points recovered for subcases 1 2 3 4 5 The solution control packet references the functional design constraint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC 1 STATICS DCFUNCTION 101 The Function Packet defines the function specification for computing the allowable displacement compo nent for T3 The general expression for the F unction packet is comp 2 T3 for grids 5 10 15 20 25 which is defined by the F unction packet FUNCTIONS Recover the Displacement component T3 times 2 0 COMP GLIST CASEID MULPT MULPT DISP GRIDLIST GLIST T3 CASEID Constraint for the component value CONST GLIST CASEID MULPT ALLOW COMP GLIST CASEID MULPT ALLOW 1 0 ENDFUNC The Bulk Data Packet gives the grid list defines five invocations of design constraint 101 references the design constraint function CONST and defines its four arguments The arguments identify the multiplier used with the displacement component the GRIDLIST the subcase identification and the allowable upper limit of the constraint 6 20 THE FUNCTION PACKET USER S MANUAL USER S MANUAL
207. LIST bulk data entry that is used to request the grid points degrees of freedom for which the stiffness matrix is to be punched ac Set identification of an ELEMLIST bulk data entry that is used to request the elements at which strains are to be punched ad Set identification of an ELEMLIST bulk data entry that is used to request the elements for which stresses are be punched ae Set identification of an ELEMLIST bulk data entry that is used to request the aerodynamic elements for which the pressure coefficients at aeroelastic trim are to be punched af Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which velocities are to be punched ag Specifies the iterations at which the design model will be punched May be ALL NONE LAST or the set identification of an ITERLIST bulk data entry which specifies the iterations at which to punch the model ah Specifies the portion of the model which will be punched May be ALL or NONE Note an integer value is accepted and treated as ALL ai Specifies the elements for which local buckling results are to be punched may be ALL or NONE aj Selects the type of stresses or strains to be output for composite elements The options are LAYER LAMINATE Or BOTH The default is LAYER Remarks 1 Form is an optional parameter for printing complex data Recrangular data outputs complex data with real and imaginary components while poLar outputs complex data using magni
208. LOWER SURFACE lA ZO ELEMENT REFERENCE ZOFF ELEMENT MEAN PLANE You may only specify a zo on this entry if the zorr field of any CQUAD4 or CTRIA3 referencing it is blank The default value for zo is t 2 where t is the overall thickness of the laminate SBOND is required if bonding material failure index calculations are desired 4 The failure theory is used to determine the element failure on a ply by ply basis The available theories are HILL Hill Theory HOFF Hoffman Theory TSAI Tsai Wu Theory STRESS For Maximum Stress Theory STRAIN For Maximum Strain Theory MEM indicates a layup of membrane only plies The material properties MIDi may reference only MAT1 MAT2 and MATS Bulk Data entries TMIN will be ignored unless the element is linked to design variables by SHAPE entries ASTROS THE BULK DATA PACKET 7 185 Input Data Entry Defines the properties of an n ply laminated composite material where all plies are composed of the same material but are of different thickness Description PCOMP 2 Format and Examples Layered Composite Element Property 1 2 3 4 5 6 7 8 9 10 PCOMP2 PID Z0 NSM SBOND F T TMIN MID LOPT CONT CONT T1 TH1 T2 TH2 T3 TH3 etc PCOMP2 100 0 49 ia Diet TSAI 200 ABC BC 052 5 45 0 0 5 90 0 0725 45 0 Field Contents PID Property identification number Integer gt 0 ZO Offset of the laminate lower surface from
209. LYZE subpacket Hierarchy Level Type of run Format ANALYZE 5 22 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL BOUNDARY Solution Control Command BOUNDARY Description Specifies the displacement sets and related data used in a particular boundary con dition Hierarchy Level Boundary condition Format and Examples BOUNDARY BCID bcid MPC i SPC j REDUCE k SUPPORT 1 METHOD m CMETHOD t PRINT NOPRINT AUTOSPC NO PUNCH USING s EPS x mo DYNRED n INERTIA o ESET p K2GG q M2GG r BOUNDARY SPC 6 BOUNDARY SPC 10 REDUCE 20 SUPPORT 30 BOUNDARY SPC 12 DYNRED 100 INERTIA 100 K2GG FUSSTIFF BOUNDARY AUTOSPC NOPRINT PUNCH USING 1001 YES SUPPORT 101 Option Meaning bcid Boundary condition identification number I nteger gt 0 i Set identification of a multipoint constraint set Invokes Mpc and MPCADD bulk data entries Integer gt 0 j Set identification of a single point constraint set Invokes spc SPC1 and SPCADD bulk data entries I nteger gt 0 k Set identification of a static condensation set Invokes ASET ASET1 OMIT and OMIT1 bulk data entries I nteger gt 0 1 Set identification of the free body support Invokes SUPORT bulk data entries Integer gt 0 m Set identification of the EIGR bulk data entry to be used Integer gt 0 n Selects the dynamic reduction parameters from the DYNRED bulk data entry Integer gt 0 o Sel
210. N system developed by NASA in the late 1960 s The DMAP language used to create NASTRAN s solution algorithms is very crude however it has been a prime factor in extending the life cycle of the system It has done this by providing a simple method of installing new code and functional capabilities into the system It also affords the user an opportunity to interact with the software MAPOL has been selected to provide the same advantages to the ASTROS system Additionally it extends the primitive DMAP design by assimilating the many advances that were made in computer science over the intervening two decades MAPOL is a structured procedural language that directly supports high order matrix operations the manipulation of database entities and complex data types The syntax of the language is similar to PASCAL and it should be easily learned by anyone familiar with Fortran or PASCAL This Chapter details all of the features of the MAPOL language and gives examples of their use ASTROS MAPOL PROGRAMMING 9 1 USER S MANUAL 9 1 1 USER OPTIONS In this section the different kinds of MAPOL programs and their uses are discussed MAPOL is the control language of the ASTROS system and as such the multidisciplinary solution algorithm is simply a MAPOL program that is embedded in the system the user is free to modify this standard algorithm and can also create individual MAPOL programs or specialized procedures 9 1 2 MAPOL PROGRAM FORM
211. N 9 0 IBM RISC SYSTEM 6000 JUL 01 1992 ASTROS DEBUG PACKET ECHO DEBUG KEY LOGBEGIN HAS BEEN SELECTED DEBUG KEY LOGMODULE HAS BEEN SELECTED DEBUG KEY MATRIX HAS BEEN SELECTED ASTROS ASSIGN DATABASE COMMAND ECHO Mig ose LOLs fees PO A A sees Oo AA RS ee OO E TOS O AO ASSIGN DATABASE COMB SHAZAM NEW Biss seh sero Rie et DO sores OF og A AA AEE sr OO cree OR sot OO re Rs et TO os i Rs ee BO ees DATA BASE NAME COMB DATA BASE PASSWORD SHAZAM DATA BASE STATUS NEW Ok USER PARAMETERS ARE NONE GIVEN Table 8 2 Boundary Condition Summary BOUNDARY CONDITION MATRIX REDUCTION SUMMARY THE PHYSICAL SET CONTAINS SUMMARY FOR 3948 DEGREES OF FREEDOM BOUNDARY DOFS 3948 PHYSICAL DOFS ARE STRUCTURAL O PHYSICAL DOFS ARE EXTRA POINTS DEPENDENT MULTIPOINT CONSTRAINT DOFS LEAVING CONSTRAINT DOFS LEAVING AND THERE ARE 12 3936 INDEPENDENT DOFS THERE ARE 1563 SINGLE POINT 2373 FREE DOFS THE FREE DOFS ARE REDUCED USING STATIC CONDENSATION THERE ARE 2221 OMITTED DOFS 152 ANALYSIS SET 0 OF WHICH ARE 152 DISCIPLINE SUBCASE SUMMARY STATICS HAS BEEN SELECTED 5 SUBCASE S ARE DEFINED FLUTTER HAS BEEN SELECTED A REAL EIGENANALYSIS WILL 1 SUBCASE S ARE DEFINED LEAVING DOFS SUPPORTED LEAVING DOFS LEFT OVER kkk BY SOLUTION CONTROL kkk ALSO BE DONE IF NOT ALREADY SELECTED BY SOLUTION CONTROL CONDITION 2 ASTROS OUTPUT FEATURE
212. NASTRAN 3 The bulk data entries will not be used in ASTROS unless selected in Solution Control 4 None of the options are required but at least one must appear 5 K2GG and M2GG affect the system stiffness and mass matrices respectively for all disciplines within the boundary condition 6 K2GG and M2GG names will typically refer to DMI or DMIG entries but may refer to any data base matrix entity of the proper dimension 7 TheAUTOSPC command AUTOSPC PRINT EPS 1 0E 8 YES is the default value To disable the feature use AUTOSPC NO 5 24 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL END Solution Control Command END Description Indicates the end of a subpacket Hierarchy Level End Format END Remarks 1 The ANALYZE and OPTIMIZE subpackets each require an END command ASTROS THE SOLUTION CONTROL PACKET 5 25 FLUTTER USER S MANUAL Solution Control Command FLUTTER Description Invokes the flutter analysis discipline Hierarchy Level Discipline Format and Examples FLUTTER caseid FLCOND i DCONSTRAINT j DCFUNCTION q CONTROL k K2PP 1 M2PP m B2PP n TFL o DAMPING p DCFUNCTION q FLUTTER FLCOND 100 FLUTTER FLCOND 100 CONTROL AILERON K2PP KAIL TFL 5 Option Meaning caseid Case identification number I nteger gt 0 i Set identification of a FLUTTER bulk data entry that provides flutter parameters j Set identification of a DCONFLT bulk d
213. No physical property in this element can be used as a local design variable for automated design ASTROS THE BULK DATA PACKET 7 37 CIHEX2 USER S MANUAL Input Data Entry CIHEX2 Quadratic soparametric Hexahedron Element Connection Description Defines a quadratic isoparametric hexahedron element of the structural model Format and Example 1 2 3 4 5 6 7 8 9 10 CIHEX1 EID PID G1 G2 G3 G4 G5 G6 CONT CONT G7 G8 G9 G10 G11 G12 G13 G14 CONT CONT G15 G16 G17 G18 G19 G20 CIHEX1 110 7 3 8 12 13 14 9 ABC BC 5 4 16 19 20 17 23 27 DEF EF 31 32 33 28 25 24 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PIHEX property entry Integer gt 0 Default is EID Gi Grid point identification numbers of connection points Integer gt 0 G1 G2 G20 Remarks 1 Grid points G1 e8 must be given in counterclockwise order about one quadrilateral face when viewed from within the element G9 612 and G13 620 must also be in a counterclockwise direction with G1 G9 and G13 along the same edge as shown in the figure below G17 G16 G15 There is no nonstructural mass The quadrilateral faces need not be planar Stresses are given in the basic coordinate system The continuations are required Au FW N No physical property in this element can be used as a local design variable for
214. OL PACKET ASTROS USER S MANUAL TITLE Solution Control Command TITLE Description Defines a title which will appear in the output Hierarchy Level Label information Format and Examples TITLE n TITLE DESIGN OF A FORWARD SWEPT WING MODEL Option Meaning n Any descriptive information can be inserted here Remarks 1 TITLE information is used until it is superseded 2 The TITLE command is optional 3 Titles are limited to no more that 72 characters ASTROS THE SOLUTION CONTROL PACKET 5 43 TRANSIENT USER S MANUAL Solution Control Command TRANSIENT Description Invokes the transient analysis discipline Hierarchy Level Discipline Format and Examples TRANSIENT type caseid DLOAD i TSTEP j FFT k Ic 1 GUST m K2PP n M2PP o B2PP p TFL q DAMPING r TRANSIENT MODAL DLOAD 10 TSTEP 20 TRANSIENT DIRECT DLOAD 100 TSTEP 30 K2PP KFREQ IC 45 TFL 5 TRANSIENT MODAL DLOAD 100 TSTEP 20 FFT 999 GUST 55 Option Meaning caseid Case identification number I nteger gt 0 type Selects the solution approach from DIRECT or MODAL i Set identification of a DLOAD bulk data entry j Set identification of TSTEP bulk data entries which provide the time step informa tion for the analysis k Set identification of an FFT bulk data entry which provides parameters to use the Fast Fourier Transform methods in performing the transient analysis 1 Set identi
215. OLD NEW gt EPS DO TEMP NEW NEW 2 0 OLD X OLD 2 3 0 OLD TEMP ENDDO PRINT 1X X CUBERT X 2F15 5 X NE END The general form of the WHILE loop is WHILE lt cond gt DO ENDDO The lt cond gt is any conditional expression that results in a logical outcome 9 4 4 THE IF STATEMENT It is often necessary in a program to specify two or more alternatives that must be selected depending upon other program results The IF statement allows this selection There are three types of IF state ments in MAPOL e LOGICAL IF BLOCK IF e IF THEN ELSE 9 4 4 1 The Logical IF The logical IF is used if a single expression is to be executed based on a particular condition The syntax of this statement is IF lt cond gt lt statement gt where lt cond gt is any logical expression and lt statement gt is any legal executable MAPOL statement except A WHILE or FOR loop Another logical IF AN END ENDP ENDIF Or ENDDO instruction A PROC definition Pd un ASTROS MAPOL PROGRAMMING 9 21 USER S MANUAL Examples of the logical IF are IF A lt B PRINT 1X A 15 A IF ABS NEW OLD gt EXP NEW OLD IF A AND B OR C CALL UTMPRT KMAT 9 4 4 2 The Block IF It is often necessary to perform a number of instructions based on a given condition This can be accomplished by a block IF statement the syntax of which is
216. PC 1 STATICS DCFUNCTION 101 The Function Packet defines the function specification for computing the allowable normal stress in the element X direction The general expression for the Function packet is 6 22 THE FUNCTION PACKET USER S MANUAL USER S MANUAL VALUE SIGX for elements 5 10 15 20 which is defined by the Function packet FUNCTIONS Constraint for E VALUE ELIST S EL ELIST SIGX 25000 0 ENDFUNC The Bulk Data Packet defines design constraint 101 defines the design constraint function VALUE and defines one argument the ELEMLIST identification 1 for the function BEGIN BULK Design Constraint Function DCONF 101 VALUE DCN1 DCN1 ELIST 1 ENDDATA No constraints will be generated because element list 1 is not defined in the Bulk Data packet Example 8 Missing Argument Definitions The following example demonstrates an invalid request to compute the constraints for the normal stress in the element s X direction The solution control packet references the functional design con straint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC STATICS DCFUNCTION 101 The Function Packet defines the function specification for computing the allowable normal stress in the element s
217. PCOMP1 PID Z0 NSM SBOND E T TMIN MID LOPT CONT CONT TPLY TH1 TH2 TH3 TH4 TH5 TH6 TH7 CONT CONT TH8 TH9 TH10 etc PCOMP1 100 0 5 1 7 5 3 STRAIN 200 ABC BC 0 25 45 0 45 0 90 0 90 0 45 0 Field Contents PID Property identification number 1 000 000 gt Integer gt 0 20 Offset of the laminate lower surface from the element mean plane A positive value means the ze direction Real or blank see Remark 2 NSM Nonstructural mass per unit area Real gt 0 0 SBOND Allowable shear stress of the bonding material Real gt 0 0 F T Failure theory one of the strings HILL HOFF TSAI STRESS Or STRAIN See Remark 4 TMIN Minimum ply thickness for design Real gt 0 0 or blank Default 0 0001 MID Material identification number for all layers Integer gt 0 0 or blank LOPT Lamination generation option MEM or blank See Remark 5 TPLY Thickness of each layer Real gt 0 0 THi Angle between the longitudinal direction of the fibers of the i th layer and the material X axis Real or blank Remarks 1 For nondesigned elements the plies are numbered from 1 to n beginning with the bottom layer 7 184 THE BULK DATA PACKET ASTROS USER S MANUAL PCOMP1 2 For composities there are two methods for specifying the offset of the element reference plane from the element mean plane zo on this entry and zorF on the CQUAD4 or CTRIA3 Bulk Data entries The distinction is shown in the figure below UPPER SURFACE
218. RELUPD CADDB Performs a relational update from execution memory of a tuple retrieved using RELGET RELUSE CADDB Opens a relational entity for access from the executive sequence ROWMERGE MAT Merges two or more submatrices into a single matrix based on row partitioning vectors ROWPART MAT Partitions a matrix into two or more submatrices based on row partitioning vectors Solves the trim equation for steady aeroelastic trim analyses Computes the rigid and flexible SAERO ENG stability coefficients for steady aeroelastic analyses and the aerodynamic effectiveness constraints for constrained optimization steady aerodynamic analyses SAERODRV ENG Driver for SAERO disciplines SAEROMRG ENG Merges the SAERO results into MATOUT in case order Computes the stress and or strain constraint values for the statics or steady aeroelastic trim SCEVAL ENG analyses in the current boundary condition SDCOMP MAT Decomposes a symmetric matrix into its lower triangular factor and a diagonal matrix Generates a set of SHAPE entries based on the element centroidal locations for a group of SHAPEGEN a selected elements ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 17 USER S MANUAL Table 3 8 Summary of ASTROS Modules Continued MODULE NAME TYPE DESCRIPTION Interprets the solution control packet forms the CASE entity and outputs certain key SOLUTION ENG parameters to the executive sequenc
219. RIX It may never be LOGICAL LABEL RELATION without an attribute specification UNSTRUCT Or IUNSTRUCT Table 9 3 MAPOL Arithmetic Operators OPERATOR DESCRIPTION Addition when connecting two operands Unary plus when preceding an operand Subtraction when connecting two operands Negation when preceding an operand Multiplication Division a E xponentiation ASTROS MAPOL PROGRAMMING 9 11 USER S MANUAL 9 3 1 3 Evaluation of Arithmetic Expressions Expressions are evaluated from left to right according to the following hierarchy of operations PRIORITY OPERATOR 1 FUNCTION E valuation 2 3 and 4 and This hierarchy is used to determine which of two sequential operations is to be performed first If two sequential operations are of unequal rank the higher ranking operation is performed first When a unary minus or plus appears in an arithmetic expression it follows the same hierarchy as a minus or plus used for subtraction or addition For example S T sevaluated as R S T S T is evaluated as R S T S T is evaluated as R S T The division of operands in an expression may result in a truncated value for integer operands or a fractional value for non integer operands Therefore parentheses should be used when a specific order of evaluation other than left to right is desired for the operands For example th
220. ROS USER S MANUAL MAPOL ELATION GPOINT EGER GID NTUPLES ERRSTAT EAL X Y Z ROJECT GPOINT USING GID X Y Z CALL RELUSE GPOINT NTUPLES ERRSTAT PRINT NTUPLES 16 NTUPLES IF ERRSTAT lt gt 0 THEN PRINT ERRSTAT IS 16 ERRSTAT ELADD GPOINT GID 3 TX 2 097 PY 067 T Z 07 ELADD GPOIN END GPOIN1 Figure 9 2 MAPOL Program Using Relational Procedures ASTROS MAPOL PROGRAMMING 9 31 USER S MANUAL This pageis intentionally blank 9 32 MAPOL PROGRAMMING ASTROS USER S MANUAL Chapter 10 REFERENCES 1 Herendeen D L Hoesly R L and J ohnson E H Automated Strength Aeroelastic De sign of Aerospace Structures AF WAL TR 85 3025 September 1985 2 The NASTRAN User s Manual Leve 17 5 National Aeronautics and Space Administra tion NASA SP 222 05 December 1978 3 Garvey S J The Quadrilateral Shear Panel Aircraft Engineering May 1951 p 134 Etkin B Dynamics of Flight J ohn Wiley and Sons Inc New York May 1967 5 Woodward F S USSAERO Computer Program Development Versions B and C NASA CR 3227 1980 6 Herendeen D L and Ludwig M R Interactive Computer Automated Design Database CADDB Environment User s Manual AF WAL TR 88 3060 August 1988 ASTROS REFERENCES 10 1
221. ROS is NOT written in MAPOL only the executive control algorithm is written in the MAPOL language In fact ANSI standard FORTRAN was used to write the compiler for MAPOL and for all the engineering software of the ASTROS system MAPOL allows you to manipulate the software system in many ways to tailor the available capabilities to perform particular tasks At a higher level of sophistication you may add modules to the system or replace modules that already exist Obviously some of these features ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 1 USER S MANUAL require a knowledge of the ASTROS system that is beyond the scope of the User s Manual Those features that require detailed information are more fully discussed in the Programmer s Manual but their existence is emphasized here in order to introduce you to the flexibility that the executive system provides This Chapter presents the mechanics of the MAPOL packet The potential of the executive system to tailor the ASTROS software is explored in this discussion of the standard sequence In addition to this Chapter Chapter 8 presents a detailed description of the MAPOL language its syntax and features It cannot be overemphasized that while the capabilities implemented in the ASTROS software are signifi cant the true power embodied in the ASTROS system is its immense flexibility largely provided by the executive system and its MAPOL language The MAPOL packet is initiated either by the
222. RY Memory manager debug print 3 14 THE INPUT DATA STREAM ASTROS USER S MANUAL The last group of database debug options consists of the MEMORY command This option causes an echo of all the memory management calls made in the modules The user can then track the ASTROS execution into the engineering modules themselves In addition to the echo the MEMORY option invokes a checksum operation which checks for the integrity of the memory block headers on every memory manager opera tion If the checksum fails a message is written to the effect that a block header has been overwritten This option is very effective in uncovering errors in engineering modules that make use of dynamic memory allocation 3 4 3 INTERMEDIATE RESULTS PRINTING COMMANDS Many of the ASTROS engineering modules have intermediate output print options that are useful in tracing the details of an analysis or in reviewing the quality of the inputs These many options are listed in Table 3 3 ASTROS THE INPUT DATA STREAM 3 15 USER S MANUAL Table 3 3 Intermediate Results Debug Commands KEYWORD DESCRIPTION Intermediate unsteady Aero matrices Prints the SKJ matrix and if only one group includes AJ J QKJ and QJ J if they exist gt 1 Includes D1 K D2 K and AJ J T matrices Prints initial design information AMP n 1 Includes function values at each iteration Includes internal Microdot parameters DESIGN n A i Inc
223. Remarks 1 The extra point set identification is selected on the BOUNDARY entry All extra points defined with this SETID will be used in dynamic analyses in the boundary condition 2 All extra point identification numbers must be unique with respect to all other structural and scalar points 3 This entry is used to define coordinates used in transfer function definitions see TF entry and Direct Matrix input 4 Ifthealternate form is used 1D2 must be greater than or equal to ID1 7 128 THE BULK DATA PACKET ASTROS USER S MANUAL FFT Input Data Entry FFT Description Defines parameters for controlling the Fast Fourier Transformation FFT during time domain response analysis Format and Example 1 2 3 4 5 6 7 8 9 10 FFT SID TIME NT RDELTE RE FRIM OTYPE FLIM FFT 3 20 1024 1 0 Field Contents SI FFT set identification number Integer gt 0 TIME Length of time period to be analyzed Real gt 0 0 NT Number of time points to be used for the FFT Integer gt 2 RDELTF Ratio of incremental frequency del F to 1 T See remarks 4 and 6 Default 1 0 Real gt 0 0 RF Ratio of total frequency duration F to NT 2 T See remarks 5 and 6 Default 1 0 Real gt 0 0 FRIM Frequency response interpolation method Character string LINEAR or CUBIC De fault is LINEAR OTYPE Type of response to be output Character string TIM
224. S This section describes the host dependent information that you need to execute ASTROS on Unix based computer systems UAI supports a wide variety of manufacturers including Silicon Graphics Hewlett Packard IBM RS 6000 Sun and more For a complete list of platforms please contact your UAI sales representative 2 2 1 Executing ASTROS An sh script file called ast ros is provided to execute ASTROS To execute you enter W astros m memory l gt p prefname B e astros_exe c config_file filelist where memory specifies the amount of memory that the job will use Options allow you to use shorthand notation for large values and allocation types The options K and mM indicate that the memory value is specified in thousands or millions of units respectively The units may be specified in single precision words w bytes B or machine precision words P If none of these arguments are used then memory is assumed to be single precision words Chapter 3 has a further discussion of memory allocation The prefname specifies the substitution string used to generate Preference File names When performing software development with ASTROS there may be several versions of the program The name as tros_exe specifies the name of the ASTROS executable program version to use By default a file named astros out located in the local directory or the version in the installation directory will be used The config_file
225. S 8 3 Table 8 3 Active Boundary and Constraint Summary USER S MANUAL SENSITIVITY SUMMARY FOR BOUNDARY CONDITION 4 FLUTTER CONSTRAINTS 4 TOTAL ACTIVE CONSTRAINTS FOR THIS BOUNDARY CONDITION SENSITIVITY SUMMARY FOR BOUNDARY CONDITION 2 TSAI WU STRESS CONSTRAINTS ON STATIC SUBCASE L 6 TSAI WU STRESS CONSTRAINTS ON STATIC SUBCASE 2 4 FLUTTER CONSTRAINTS 12 TOTAL ACTIVE CONSTRAINTS FOR THIS BOUNDARY CONDITION Table 8 4 Resequencing Summary ARE SUMMAR Y OF AUTOMATIC RESEQUENCING ERA METHOD SELECTED CM CRITERION RMS WAVEFRONT BEFORE AFTER BANDWIDTH 648 60 PROFILE 25960 23960 MAXIMUM WAVEFRONT 50 60 AVERAGE WAVEFRONT 39 453 36 413 RMS WAVEFRONT 40 632 38 159 NUMBER OF GRID POINTS 658 MAXIMUM NODAL DEGREE 14 NUMBER OF MPC EQUATIONS PROCESSED 12 ELEMENTS PROCESSED CSHEAR 565 CTRMEM 40 CONROD 305 CONM2 35 CBAR 152 CQUAD4 662 TOTAL ELEMENTS 1759 8 4 OUTPUT FEATURES ASTROS USER S MANUAL Table 8 5 Active Constraint Summary COUNT MID HOBWNH PRR NRO CONSTRAINT VALUE CONSTRAINT TYPE TYPE COUNT BOUNDARY ID SUBCASE ELEMENT TYPE 7 09291E 02 UPPER BND LIFT EFFECT 1 1 1 N A 4 97155E 04 DISPLACEMENT 1 1 1 N A 4 20226E 01 VON MISES STRESS 1 1 dL QDMEM1 8 19597E 01 VON MISES STRESS 2 1 1 QDMEM1 8 42767E 01 VON MISES STRESS 3 1 1 QDMEM1 5 62036E 01 VON MISES STRESS 4 1 1 QDMEM1 4 38053E 01 VON MISES STRESS 5 1 1 QDMEM1 8 14886E 01 VON MISES STRESS 6 1 1 QDMEM1 8 52344E 01 VON M
226. S Baars an ae Ad Gee as aie 6 14 ASTROS iii USER S MANUAL 6 5 INSTRINSIC RESPONSE COMMANDS 44 6 25 THE BULK DATA PACKET ooo o 7 1 Lal BULK DATA EGHO OPTIONS o oime a ewig a ae ak ae Poa WS Gnd 7 2 7 2 FORMAT OF THE BULK DATA ENTRY oa ecos ta we ee ee we e 7 3 3 DATA FIELD FORMATS 00d ene wa BAR bdd de ee We A ee a 7 4 7 4 ERROR CHECKING IN THE INPUT FILE PROCESSOR 7 5 7 5 BULK DATA ENTRY SUMMARY 2 2 000502 ae 7 5 7 5 1 Aerodynamic Load Transfer e 7 5 7 5 2 Applied Dynamic Loads 2 a e aea e a EEN A R E T a NE R 7 6 5 32 Applied Staic boadS oaa A a ae ME end A A a 7 6 7 5 4 Boundary Condition Constraints o ooo e 7 6 7 5 5 Design Constraints aoaaa a 7 7 7 5 6 Design Variables Linking and Optimization Parameters aoa o ao 7 8 TOT GEOMEUY serina cates a aban ents a a at at ale 7 8 7 5 8 Material Properties ue iva 4 die gel yee ee e Bee Gob wee ee A dee 4 7 8 7 5 9 Miscellaneous Inputs 2 ae e a E a a EIE E E A 7 8 F510 Selection LIStS as e a Mee a a chan gd abe mee Sees ra al d ae al eh erg ch 7 9 7 5 11 Steady Aerodynamics a 7 9 7 5 12 Structural Element Connection o 7 9 7 5 13 Structural Element Properties 2 aa ee 7 10 7 5 14 Unsteady Aerodynamics aoaaa a a a 7 10 7 5 15 Discipline Dependent Problem Control a aoaaa eee eee 7 11 7 6 DIFFERENCES BETWE
227. SER S MANUAL CQDMEM1 Input Data Entry CQDMEM1 I soparametric Quadrilateral Element Connection Description Defines the isoparametric quadrilateral membrane element Format and Example cl 2 3 4 5 6 7 8 9 10 CODMEM1 EID PID G1 G2 G3 G4 TM TMAX CQDMEM1 72 13 13 14 15 16 29 2 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PODMEM1 or PCOMP property entry Default is EID Integer gt 0 Gi Grid point identification numbers of connection points Integer gt 0 TM Material property orientation angle If TM is real the sketch below gives the sign convention for TM If TM is an integer the material x axis is along the projection onto the plane of the element of the x axis of coordinate system identified by the integer TMAX Maximum allowable element thickness in design Real gt 0 0 or blank Default 10 Remarks 1 Grid points G1 through G4 must be ordered consecutively around the perimeter of the element as shown in the figure below Ye G3 G4 TM Xe G2 G1 2 All interior angles must be less than 180 3 TMAX is ignored unless element is linked to global design variable by a SHAPE entry ASTROS THE BULK DATA PACKET 7 59 CQUAD4 USER S MANUAL Input Data Entry CQUAD4 Quadrilateral Element Connection Description Quadrilateral plate element QUAD4 of the structural model This is
228. SHEAR Shear Panel Element Connection Description Format and Example dt 2 3 4 5 6 7 8 9 10 CSHEAR EID PID Gl G2 G3 G4 TMAX CSHEAR 3 6 1 5 3 7 Field Contents EID Element identification number Integer gt 0 PID CTRIA3 Input Data Entry USER S MANUAL CTRIA3 Triangular Element Connection Description Defines a triangular shell element TRIA3 of the structural model Format and Example 1 2 3 4 5 6 7 8 9 10 CTRIA3 EID PID G1 G2 G3 TM ZOFF CONT CONT TMAX TL T2 T3 CTRIA3 101 L7 1001 1005 1010 45 0 0 01 ABC BC 0203 0 125 0 05 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PSHELL or PCOMPi property entry Default is EID Integer gt 0 Gi Grid point identification numbers of connection points Integer gt 0 TM Material property orientation specification Real or blank or O lt Integer lt 1 000 000 If Real or blank specifies the material property orientation angle in degrees If Integer the orientation of the material x axis is along the projection onto the plane of the element of the x axis of the coordinate system specified by the integer value ZOFF Offset of the element reference plane from the plane of grid points A positive value means the ze direction Real or blank see Remark 2 for default TMAX Maximum allowabl
229. SIGN convergence in ACTCON If value gt CTL the constraint is active Set in FSD DESIGN or FSD ACTCON Criteria for denoting a constraint to be feasible in determining CTLMIN DESIGN convergence in ACTCON If maximum constraint value lt CTLMIN the FSD design is feasible Set in DESIGN or FSD Criteria used in ACTCON for selecting active constraints All constraints EPS SOLUTION with values greater than EPs will be retained Set through the Solution 0 10 ACTCON Control OPTIMIZE command See also NRFAC NLEMG FDSTEP EBKLEVAL Finite difference step size for sensitivity calculations 0 001 MAKDFV MAKDFU The maximum frequency value associated with the NEIV eigenvalues FMAX GRD1 computed for dynamic reduction in the current boundary condition GRD2 Output from GDR1 K6ROT EMG Stiffness value for plate element drilling degrees of freedom 0 0 MACH SAERODRV Mach number for the current case Set in SAERODRV QOLUTTON A move limit applied to the physical design variable v for MOVLIM DESIGN mathematical programming methods The moveis V MOVLIM lt V lt 2 0 MAKDFV V MOVLIM Set through the Solution Control OPTIMIZE command 1 0 TCEVAL Criteria used in ACTCON for selecting active constraints At least NRFAC NRFAC SOLUTION times NDV constraints will be retained Set through the Solution Control 3 0 ACTCON OPTIMIZE command See also EPS SAERODRV Dynamic pressure value used in the current steady aeroelastic subcase QDP SAERO Output from SAERODRV use
230. STRAINCONSTRAINT option All DCONxxx bulk data entries such as DCONTHK that do not have SETID fields will be applied to the model in combination with set selectable constraints to make up the set of design constraints Finally the DCFUNCTION option may be used to select functional constaints that are applied to the SAERO responses from the current solution 5 3 5 FLUTTER Discipline Options The FLUTTER discipline must have a flight condition specified in the solution control through the FLCOND option In addition the k2PP B2PP M2PP TFL and DAMPING options may be used with or without an ESET Boundary Condition option to impose a case by case set of additional inputs degrees of freedom for modelling control systems etc For analysis this selection completes the specification of the discipline with each FLCOND condition generating up to one subcase consisting of up to one flutter eigenvector for each Mach number and density ratio if flutter occurs In the OPTIMIZE subpacket the DCONSTRAINT option can be used to select DCONFLT bulk data entries to place a required damping limit on each of the roots extracted in the flutter analysis The DCFUNCTION option may also be used to select functional constaints that are applied to the FLUTTER responses in the current solution The actual flutter root and eigenvector cannot be obtained in the OPTIMIZE subpacket 5 3 6 TRANSIENT Discipline Options The TRANSIENT discipline must have time step and load in
231. STRAN METHOD WHICH DOES NOT ALLOW RIGID CONNECTIONS TO BE CHANGED FOR DIFFERENT BOUNDARY CONDI TIONS 2 The total number of components in CNi must be six for example CN1 123 CN2 3 CN3 2 and CN4 3 The components must jointly be capable of representing any general rigid body motion of the element The m set degrees of freedom specified on this entry may not be specified on other entries that define mutually exclusive sets 3 A degree of freedom cannot be both independent and dependent for the same element However both independent and dependent components may exist at the same grid point 4 Rigid element identification numbers must be unique within each element type for each Mpc set identification number ASTROS THE BULK DATA PACKET 7 205 RBE2 Input Data Entry RBE2 Rigid Body Element Form 2 USER S MANUAL Description Defines a body whose independent degrees of freedom are specified at a single grid point and whose dependent degrees of freedom are specified at an arbitrary number of grid points Format and Example 1 2 3 4 5 6 7 8 9 10 RBE2 SETID EID GN CM GM1 GM2 GM3 GM4 CONT CONT GM5 GM6 GM7 GM8 etc RBE2 1001 9 8 12 10 12 14 15 ABC BC 16 20 Field Contents SETID Multipoint constraint set identification number specified in Solution Control Integer gt 0 EID Rigid body element identification number Integer gt 0
232. T method mat1 mat2 mat10 where up to ten matrices can be printed in a single call The optional integer METHOD argument selects from among two formats that are available If METHOD is zero or absent the entire matrix column starting with the first non zero term and ending with the last non zero term will be printed including all intermediate zeros f METHOD is non zero only the non zero terms of each column will be printed 8 5 4 General Relation Print Utility UTRPRT The print utility UTRPRT has been written such that any data base relational entity can be printed to the output file The calling sequence for UTRPRT is CALL UTRPRT reli rel2 rell0 j where up to ten relations can be printed in a single call Relational entities are tables in which the columns are called attributes The UTRPRT utility attempts to print the relation in a format in which each ASTROS OUTPUT FEATURES 8 39 USER S MANUAL column represents one attribute and each row represents a single entry in the relation The utility is not very sophisticated however and relations having more attributes than can fit in the width of a page 128 characters or approximately 12 attributes will have the trailing attributes ignored Also string attrib utes are only printed if they are eight characters long Despite its limitations the UTRPRT utility can be very useful in viewing ASTROS data base relations 8 5 5 General Unstructured Print Ut
233. T 7 227 TEMP Input Data Entry TEMP Grid Point Temperature Field Description Defines temperature at grid points for determination of 1 Thermal Loading and 2 data recovery Format and Examples USER S MANUAL 1 2 3 4 5 6 7 8 9 10 TEMP SID G T G T G T TEMP 3 94 316 2 49 219 8 Field Contents SID Temperature set identification number Integer gt 0 G Grid point identification number Integer gt 0 T Temperature Real Remarks 1 Fromonetothree grid point temperatures may be defined on a single entry 2 Average element temperatures are obtained as a simple average of the connecting grid point tempera tures when no element temperature data are defined 3 For each thermal load temperatures must be specified for all grid points using either TEMP or TEMPD entries 7 228 THE BULK DATA PACKET ASTROS USER S MANUAL TEMPD Input Data Entry TEMPD Grid Point Temperature Field Default Description Defines a temperature value for all grid points of the structural model which have not been given a temperature on a TEMP entry Format and Examples 1 2 3 4 5 6 7 8 9 10 TEMPD SID T SID T SID T SID al TEMPD 1 215 3 Field Contents SID Temperature set identification number Integer gt 0 T Default temperature value Real Remarks 1 From oneto four default temperatures may be d
234. T ASTROS USER S MANUAL DCONLMN Input Data Entry DCONLMN Composite laminate minimum gauge constraint Description Defines a lower bound constraint on the total thickness of all or part of the layers of a composite element The constraint is of the form Lois amg tmin Format and Example 1 2 3 4 5 6 7 8 9 10 DCONLMN MINTHK LAM SID SID SID SID SID SID CONT CONT SID SID etc DCONLMN 0 20 ALL 1001 1002 5 Field Contents INTHK Minimum laminate thickness Real gt 0 0 Default 10 LAM The character string ALL or the set identification number of one or more PLYLIST entries naming a set of plies whose summed thicknesses constitute the laminate thickness in the constraint If ALL the laminate is defined to be all the layers on the PCOMPS of the elements selected by SIDi Character ALL or Integer gt 0 Default ALL SID Set identification of one or more ELEMLIST entries that define the set of composite elements to which this composition constraint will be applied Integer gt 0 or blank Remarks 1 Because of the generality of the definition of the laminate there is no real distinction between the DCONLMN and the DCONPMN constraints Only the defaults are different to allow simple definitions of the common laminate in DCONLMN ALL or ply PLYNUM in DCONPMN 2 The definition of laminate thickness can vary from entry to entry If ALL is used every layer of the
235. T1 C1 G1 1 G1 2 CONT CONT G1 3 WT2 C2 G2 1 G2 2 etc WT3 CONT CONT C3 G3 1 tc te WT4 C4 G4 1 CONT CONT G4 2 etc CONT CONT UM GM1 CM1 GM2 CM2 GM3 CM3 CONT CONT GM4 CM4 etc RBE3 1001 14 100 1234 10 123 al 3 ABC BC 5 4 7 1 2 4 6 5 2 DEF EF 2 7 8 9 Sal 1 15 GHI HI 16 JKL KL UM 100 14 5 3 7 2 Field Contents SETID Multipoint constraint set identification number specified in Solution Control Integer gt 0 EID Rigid body element identification number Integer gt 0 REFG Reference grid point identification number Integer gt 0 REFC Component numbers of degrees of freedom in the global coordinate system that will be computed at REFG Indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 WTi Weighting factor for most common defined by Gi j Real Ci Component numbers of degrees of freedom in the global coordinate system which have weighting factor wri at grid points Gi j Indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 Gi j Grid point identification number whose components ci have weighting factor wri Integer gt 0 UM Character string indicating the start of the list of dependent degrees of freedom The default is that all of the components in REFC at REFG and no others will be placed in the m set GMi Grid point identification numbers with components in the m set Integer gt 0 CMi Component numbers in the global coordinate system at
236. TEGY FSD ALPHA 0 8 MAXFSD 10 OPTIMIZE STRATEGY FSD 3 ALPHA 0 8 MAXFSD 10 Option Meaning m1 m2 m3 The strategy to be used in optimization Either mp for math programming meth ods or FSD for fully stressed design The order of input on the strategy command is the order that will be used Each strategy MP or FSD may only appear once Default for m1 MP Only MP methods will be used niterl The number of iterations for m1 m2 and m3 respectively The default for each is to niter2 use the last named method for those iterations remaining up to MAXITER If niter3 MAXITER is less than the sum of specified iterations ASTROS will warn the user but stop at MAXITER iterations STRATEGY MP for iterations 1 thru MAXITER STRATEGY MP MP for iterations 1 thru MAXITER Fsp for iterations 1 thru 5 mp for STRATEGY FSD 5 i g iterations 6 thru MAXITER FSD for iterations 1 thru 5 mp for STRATEGY FSD 5 MP a a iterations 6 thru MAXITER n The maximum number of iterations to be performed using MPor FSD Default 15 o The move limit applied to local design variables in Mp The local variable after each redesign will lie between t MOVLIM and t MOVLIM where t is the initial value Default 2 0 must be greater than 1 0 p The window around zero in which the MovLIM bound is overridden to allow the local variable to change sign If WINDOW 0 0 the local variable may not change
237. TIFFNESS Selects stiffness matrix at nodal points STRAIN Selects strains at structural elements STRESS Selects stresses at structural elements TPRESSURE Selects trim pressures at aerodynamic boxes TRIM Selects trim and stability coefficients for steady aeroelastic analyses VELOCITY Selects velocities at nodal points 5 18 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL Table 5 5 Response Quantities by Discipline OPTION DESIGN STAT MODE SAERO FLUT TRANS FREQ ACCEL Y Y Y Y AIRDISP Y CGRADIENT Y DCONSTRAINT Y DISP ENERGY FORCE NNN NNN NNN NNN GDESIGN Y GPFORCE Y Y GPWG Y Y Y Y Y Y KSNS Y LDESIGN Y LOAD Y Y Y Y MASS Y Y Y Y Y Y MODEL MSNS OGRADIENT QHH Y Y QHJ ROOT Y Y SPFORCE NNN STIFFNESS STRAIN STRESS NNN NNN NNN TPRESSURE NNN NINN TRIM VELO Y Y ASTROS THE SOLUTION CONTROL PACKET 5 19 USER S MANUAL This pageis intentionally blank 5 20 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL Solution Control Command Description Allows commentary data to be placed in the Solution Control packet Hierarchy Level Various Format THIS IS A COMMENT ASTROS THE SOLUTION CONTROL PACKET 5 21 ANALYZE USER S MANUAL Solution Control Command ANALYZE Description The first command in the ANA
238. TYP field has the following interpretation LIFT Implies that the vertical acceleration will be trimmed by one FREE symmetric control parameter or surface or the acceleration computed for some set of symmetric parameters surfaces 7 234 THE BULK DATA PACKET ASTROS ROLL implies that the roll acceleration PACCEL will be trimmed by some one FREE antisymmetric control parameter or surface OR the acceleration computed for some set of antisymmetric parameters surfaces Any number of antisymmetric parameters may be fixed but the FREE parameters are limited to PACCEL OR any oneantisymmetric parameter or surface F or example PACCEL 0 0 AILERON 1 0 PRATE FREE PITCH implies that the vertical acceleration Nz and the pitch acceleration QACCEL will be trimmed by no more than two FREE symmetric control parameters or surfaces OR the accelerations computed for some set of symmetric parameters surfaces Any number of symmetric parameters may be fixed but the FREE parameters are limited to QACCEL and Nz OR up to two symmetric parameters or surfaces OR some combination F or example NZ 8 0g s QACCEL 0 0 ALPHA FREE ELEV FREE blank implies that the support DOF s are equal to the number of free parameters Appropriate trim equations are assembled and solved 4 Units for QpP are force per unit area TRIM USER S MANUAL 8 The number of FREE Values of VALUEi must correspond exactly to the number of u
239. UD Indicates the start of the up degrees of freedom Character Required GIDDi Grid or scalar point identification numbers of points in the uD list I nteger gt 0 Required DOFDi Single degree of freedom corresponding to the points GIDDi DOF Code Required K Z Indicates the start of the element stiffness K or flexibility z matrix Character Required Kij Elements of the K or z matrix See Remark 2 Real Default 0 0 ngn Indicates the start of data defining the rigid body s matrix Character Required Sij Elements of the s matrix See Remark 3 Real Default 0 0 Remarks ASTROS THE BULK DATA PACKET 7 141 GENEL USER S MANUAL 1 Element identification numbers must be unique 2 TheK or z matrices are entered as lower triangular matrices by columns High precision input format may be used The s matrix is entered by rows There are four distinct sections of data to input the ur list the uD list the K or z matrix and the s matrix 5 Thestiffness approach fi K KS il or faf S K s KS Ud 6 The flexibility approach le sr 3 e where uj Ui1 Ui2 Uim Ud Ud1 Ud2 Udn KZ11 KZi2 KZim KZ22 KZ l o Z and KZ KZ KZm1 sie ae K Zmm SL as Sin S Sm1 O Smn The required input is the U list and the lower triangular portion of K or Z Additional input may include the U list and S If S is input Uj must also be input If U is i
240. UNDARY command One of these methods must be used 2 Each continuation entry defines a rectangular search region Any number of regions may be used and they may overlap Roots in overlapping regions will not be extracted more than once Q Imaginary Axis Al Se P Real Axis A2 B1 Wi The units of P Q and w are radians per unit time 4 At least one continuation entry is required For the Upper Hessenberg method ND1 controls the number of vectors computed Only one continu ation entry is considered and the P Q pairs along with the parameters w1 and NE1 are ignored All eigenvalues are computed for this method 6 If P Q pairs and parameters W1 and NE1 are provided and insufficient memory exists for the U pper Hessenberg method ASTROS will switch to the Inverse power method 7 A pair P Q defines a complex eigenvalue From this pair the following may be computed fy undamped frequency V P24 Q EA P amp damping coefficient PQ fp damped frequency f Y 1 E for lightly damped systems Q is a measure of the radian frequency and P is a measure of the damping 8 Parameter wi should be kept greater than 5 percent of the segment length Ai to Bi for relatively efficient processing ASTROS THE BULK DATA PACKET 7 119 EIGR GIVENS and Modified GIVENS Input Data Entry Description USER S MANUAL EIGR GIVENS and Modified GIVENS Specifies real eigensolution contro
241. VALUE 4 3531E 01 bs PREVIOUS VALUE 2 7840E 01 DELTA 1 5691E 01 x PERCENT MOVE 56 3603 x CRITERION 2 DESIGN VECTOR MOVE ii NORM OF X X0 1 3076E 00 EUCLIDEAN NORM OF X0 2 3200E 00 PERCENT MOVE 56 3603 ll CRITERION 3 DESIGN VARIABLE MOVE ld Bas MAXIMUM MOVE 3 6390E 01 hs hal AT DESIGN VARIABLE 3 a CURRENT VALUE 1 2339E 00 PREVIOUS VALUE 8 7000E 01 ki E PERCENT MOVE 41 8275 ER THE APPROXIMATE PROBLEM IS NOT CONVERGED FO ISIC IO IO IC IO IG ICI IO II ICI IO ICI ICI IO ISIC IO ICI ICI IO III ICA IO IOI I ICA AR ASTROS OUTPUT FEATURES 8 5 USER S MANUAL value is greater the approximate problem will not be considered converged otherwise it will be A message indicating the state of convergence closes the Approximate Optimization Summary The last default design print Table 8 7 is generated by the acrcon module on the final design iteration The ACTCON module prints out the design iteration history The iteration history includes statistics summarizing each approximate optimization problem and shows the increments in the objective func tion All values in this table are associated with the approximate problem Since weight in ASTROS is explicitly linear in the design variables the objective function values are exact The final default outputs are a trailer indicating the status of the termination either with or without errors the date and the time the run was completed and
242. XL EPSAXL SIGCA EPSCA SIGDA EPSDA SIGEA EPSEA SIGFA EPSFA SIGCB EPSCB SIGDB EPSDB SIGEB EPSEB SIGFB EPSFB SHEAR AXSHEAR AXSHEAR SIGX EPSX SIGY EPSY TAUXY EPSXY QDMEM1 SIG1 EPS1 TRMEM SIG2 EPS2 MAXSHEAR MAXSHEAR FIBER FIBER TRANSV TRANSV SIGX EPSX SIGY EPSY TAUXY EPSXY SIG1 EPS1 MIDPLANE SIG2 EPS MAXSHEAR MAXSHEAR FIBER FIBER TRANSV TRANSV TSIGX TEPSX TSIGY TEPSY QUAD4 TTAUXY TEP SXY TRIA3 TSIGL TEPS1 TOP SURFACE TS1G2 TEPS2 TMAXSHEAR TMAXSHEAR TFIBER TFIBER TTRANSV TTRANSV BSIGX BEPSX BSIGY BEPSY BTAUXY BEPSXY BOTTOM BSIG1 BEPS1 SURFACE BSIG2 BEPS2 BMAXSHEAR BMAXSHEAR BFIBER BFIBER BTRANSV BTRANSV 6 10 THE FUNCTION PACKET USER S MANUAL USER S MANUAL The specific discipline request defines whether the case and or mode is a valid request in the response functions The mode sequence number is used only if the discipline is MODES If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 3 2 6 Natural Frequency Constraints To select a natural frequency computed in a MODES discipline the function FREQ l modeid caseid MODELIST mode_sid CASELIST case_sid is used Again a single mode modeid or a list of modes MODELIST is selected The optional caseid allows the selection of modes from a specific case 6 3 2 7 Flutter Response Functions The flutter response functions are FROOT FDAMP and FFREQ which represen
243. able as output for the HEX3 element through the STRESS ENERGY solution control print command options Force output is not available for the HEX3 request the following stresses and strains are output in the basic coordinate system at the ated at the center corners and mid edges of the element Normal stresses or strains in all three directions Shear stresses or strains in all three planes Principal stresses or strains in all three directions with associated direction cosines Mean stress or strain Octahedral shear stress or strain d strain output at each of the 21 points is identified by a stress or strain point ID The rain point IDs are numbered 1 through 21 The first 20 points are ordered as on the EX3 input data entry except that there is only one mid edge point per edge instead of two point is located at the element center Although the corner stress and strain points are corner grid points of the element the mid edge stress and strain points may or may not be id point depending on the location of the mid edge grid points The stress strain points for illustrated in Figure 8 5 All output is provided in the basic coordinate system since there occurring element coordinate system for the HEX3 utput may be requested for the HEX3 element The strain energy print for the IHEX3 is for the BAR element and includes a breakdown by element and by element type USER S MANUAL 8 2 1 7 Rod Element Output The ASTROS ROD e
244. acket The debug commands are grouped into executive system and database management system debugs Each of these groups is described in greater detail in the following sections 3 12 THE INPUT DATA STREAM ASTROS USER S MANUAL 3 4 1 EXECUTIVE SYSTEM DEBUG COMMANDS The first four executive system keywords are intended to assist the system programmer in following the actions of the MAPOL compiler and execution monitor The options are shown in Table 3 1 As such they are of limited value to the general user The MATRIX option however can be useful in tracking the execution of the MAPOL program It echoes the matrix utility calls for all matrix operations that are in the MAPOL sequence For example if the MAPOL program includes the expression A TRANS B C D the MATRIX trace echoes the resultant call to the mPYAD large matrix utility with the arguments shown in detail This trace can be very useful in determining which particular MAPOL instruction is being exe cuted when a problem occurs Large MAPOL programs with many loops and a large number of matrix expressions can be debugged quite simply using the MATRIX trace All MAPOL statements that result in calls to any of the large matrix utilities such as PARTN MERGE MPYAD and MXADD are echoed LOGBEGIN and LOGMODULE provide expanded echoes of the module timing summary that is found at the end of each ASTROS output file When problems cause early termination of the job
245. ained In the restart execution however the user must make sure that the last value of the variable is the desired initial value for restart In some cases the variables contain invariants like the variable NDV which contains the number of global design variables In other cases like BC the variable is a loop counter that should be reset The MAPOL sequence may perform the reinitialization automatically for example if a DO loop is re executed for values 1 through 10 the do loop counter will be reset to 1 no matter what value it contains If however the restart MAPOL omits the loop the last loop counter that was achieved will be stored in the loop counter on restart Determining which MAPOL parameters should be left alone and which should be reset rather than default to their last value is the challenge of the manual restart Tables 4 2 through 4 7 section 4 4 1 of this Manual have a list of all the MAPOL parameters These tables list each parameter and give a description of how and where the parameter is used Together with the ASTROS Programmer s Manual which document the actions that occur in each ASTROS module the user can decide which parameters should be reset and which should be allowed to default to the value set in the initial execution 4 5 MAPOL PROGRAM LISTING The current MAPOL listing is not given here because it is subject to change if you wish to obtain the current listing you may print the file MAPOLSEQ DAT which i
246. al gt 0 0 XC Compressive stress limit in the longitudinal direction Real Default xT YT Tensile stress limit in the transverse direction Real gt 0 0 YC Compressive stress limit in the transverse direction Real Default yT ss Shear stress limit for in plane stress Real gt 0 0 F12 Tsai Wu interaction term Real PTYPE Property type Character selected from PQDMEM1 PTRMEM PSHELL PCOMP PCOMP1 PCOMP2 LAYRNUM The layer number of a composite element Integer gt 0 or blank PIDi Property identification numbers Integer gt 0 Remarks 1 Stress constraints are selected in Solution Control with the discipline option STRESS sid 2 If the alternate form is used PID2 must be greater than or equal to PID1 Properties in the range which do not exist are ignored 3 The stress limits for compression xc and YC are always treated as negative values regardless of the sign of the input values 4 LAYRNUM is only used if the element is composed of a composite material defined with Pcomp Bulk Data entries 7 100 THE BULK DATA PACKET ASTROS USER S MANUAL DCONVM Input Data Entry DCONVM Von Mises Stress Constraint Definition Description Defines a Von Mises stress constraint by specifying the identification numbers of con strained elements Format and Example 1 2 3 4 5 6 7 8 9 10 DCONVM SID ST Sc SS ETYPE LAYRNUM EID1 EID2 CONT CONT EID3 EID4 etc DCONVM 100 1 6 LO
247. allows you to override the default uaidef file that is referenced through the UAICONFIG global variable This may be a useful option if more than one ASTROS system is available at your site Finally filelist specifies a list of one or more file names separated by spaces that contain ASTROS input data streams The actual file names must have the proper trailing component which is usually d The script file will execute ASTROS using each of the data files that you provide Examples illustrating the use of the script are shown below ASTROS RUNNING ASTROS 2 7 USER S MANUAL 1 Execute ASTROS using the input file test d astros test 2 Execute ASTROS in the background for all of the input files in directory astros demodata astros astros demodata d amp 3 Execute ASTROS using the input file test d and request one million words of memory astros m 1000000 test or astros m lmw test or astros m 1000kw 4 Suppose that you have created a Preference File name my pref execute ASTROS using the input file test d using these preferences astros p my test 5 Suppose you have created your own version of ASTROS named myast ros out in your local directory Execute input file test d using this program version astros e myastros test 2 8 RUNNING ASTROS ASTROS USER S MANUAL 2 2 2 ASTROS File Names When you execute the astros script a number of files may be created which have names that are automatically
248. amic force or moment by naming the corresponding structural acceleration in a manner consistent with the TRIM entry See Remarks 2 and 4 PRMLAB Alphanumeric string identifying a constrained control surface or aeroelastic trim parameter e g ALPHA Or PRATE See Remarks 3 and 4 CTYPE Constraint type either UPPER for upper bound or LOWER for lower bound Character default UPPER PRMREQ Bound for the stability coefficient For units see Remarks 5 and 6 Real UNITS Units for the stability coefficient Either RADIANS Or DEGREES See Remark 6 Real Default DEGREES Remarks 1 The DCoNscrF entry is selected in Solution Control with the DCONSTRAINT SETID option of the SAERO command 2 The ACCLAB may refer to any of the TRIM Bulk Data entry trim parameters that are structural accelerations Valid trim parameters are NX NY NZ PACCEL QACCEL and RACCEL 3 The PRMLAB may refer to AESURF Or CONLINK control surfaces or to any of the TRIM entry parame ters except the structural accelerations Valid selections are PRATE QRATE RRATE ALPHA BETA THKCAM and any control surface label Invalid trim parameters are NX NY NZ PACCEL QACCEL and RACCEL 4 Any combination of forces or moments and trim parameters control surfaces may be used on this entry provided they have the same symmetry as the associated TRIM entry Furthermore to apply the constraint to the flexible derivative the degree of freedom corresponding to the force or
249. an execution timing summary The timing summary shown in Table 8 8 indicates the CPU time spent in each phase of the execution The elapsed clock time is shown upon leaving each phase of the MAPOL execution This summary is useful in determining where a problem may have occurred and in confirming that the proper path was taken through the MAPOL sequence It is of course also useful as an indication of the relative CPU costs of each phase of execution 8 1 2 Error Message Output Error messages can be printed from virtually all the modules of the ASTROS system as well as from the data base management software Database errors should not occur unless you have modified or otherwise written a special MAPOL sequence incorrectly assigned file names or used other incorrect or inconsistent database information Typically database errors cause immediate termination of the execution The system administrator should be able to assist in solving such problems which it is felt will most likely be Table 8 7 Design Iteration History ASTROS DESIGN ITERATION HISTORY ITERATION OBJECTIVE NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER APPROXIMATE FUNCTION FUNCTION GRADIENT RETAINED ACTIVE VIOLATED LOWER UPPER PROBLEM NUMBER VALUE EVAL EVAL CONSTRAINTS CONSTRAINTS CONSTRAINTS BOUNDS BOUNDS CONVERGENCE 1 1 25894E 04 INITIAL FUNCTION VALUE 2 7 12705E 03 31 4 18 d 0 0 0 NOT CONVERGED 3 6 36273E 03 30 6 18 1 0 1 1 NOT CONVERGED 4 6 08681E 03 39 8 18 1 0
250. an isoparametric membrane bending element Format and Example 1 2 3 4 5 6 7 8 9 10 CQUAD4 EID PID G1 G2 G3 G4 TM ZOFF CONT CONT TMAX T1 T2 T3 T4 CQUAD4 101 17 1001 1005 1010 1024 45 0 0 01 ABC BC 02 03 0 125 0 05 0 04 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PSHELL or PCOMPi entry Default is EID Integer gt 0 Gi Grid point identification numbers of connection points Integer gt 0 TM Material property orientation specification Real or blank or O lt Integer lt 1 000 000 If Real or blank specifies the material property orientation angle in degrees If Integer the orientation of the material x axis is along the projection onto the plane of the element of the x axis of the coordinate system specified by the integer value ZOFF Offset of the element reference plane from the plane of grid points A positive value means the ze direction Real or blank see Remark 2 for default TMAX Maximum allowable element thickness in design Real gt 0 0 Ti Membrane thickness of element at grid points Gi Real or blank see Remark 3 for default Remarks 1 Theguap4 geometry coordinate systems and numbering are shown in the figure below Ye G3 G4 TM G2 G1 7 60 THE BULK DATA PACKET ASTROS USER S MANUAL CQUAD4 2 The material coordinate system TM and the offset ZOFF may also be pr
251. and AEFACT data entries 2 The geometry given with the xLoc YLoc zLoc entries is used only with Pop components ASTROS THE BULK DATA PACKET 7 27 CAERO1 USER S MANUAL Input Data Entry CAERO1 Aerodynamic Panel Element Connection Description Defines an aerodynamic macroelement panel in terms of two leading edge locations and side chords This is used for Doublet L attice theory Format and Example 1 2 3 4 5 6 7 8 9 10 CAERO1 EID PID CP NSPAN NCHORD LSPAN LCHORD IGID CONT BC X1 Y1 Z1 X12 x4 Y4 Z4 X43 CAERO1 1000 1 3 2 1 ABC BC 0 0 Field Contents EID Element identification number Integer gt 0 PID Identification number of property entry Integer gt 0 or blank Used to specify associated bodies CP Coordinate system for locating points 1 and 4 Integer gt 0 or blank NSPAN Number of span wise boxes if a positive value is given NSPAN equal divisions are assumed if zero or blank a list of division points is given at LSPAN Integer gt O or blank NCHORD Number of chord wise boxes if a positive value is given NCHORD equal divisions are assumed if zero of blank a list of division points is given at LCHORD Integer gt O or blank LSPAN Identification number of an AEFACT data entry containing a list of division points for span wise boxes Used only if NSPAN is zero or blank Integer gt 0 or blank LCHORD Identification number of
252. and simple load sensitivities for all applied loads in the Bulk LODGEN ENG Data File ENG Assembles the sensitivities to the displacements of active stress and displacement constraints in MAKDFU the current active boundary condition MAKDFV ENG Assembles the sensitivities of active thickness constraints MAKDVU ENG Multiplies the stiffness or mass design sensitivities by the active displacements or accelerations ENG Generates the element summary relational entities for all structural elenents Determines the MAKEST design variable linking and generates sensitivities for any thickness constraints Merges two or more submatrices into a single matrix based on row and column partitioning MERGE MAT vectors Assembles the constraint sensitivity matrix from the sensitivity matrices formed by MAKDFU and MKAMAT ENG the sensitivities of the displacements for active static load conditions in the current active boundary condition MKDFDV ENG Computes the sensitivity of PBAR1 cross sectional parameters with respect to design variables ENG Computes the matrix DF SV which contains the design variable nonlinear s matrix derivatives MKDFSV related to active stress and strain constraint sensitivity terms MKPVECT MAT Generates partitioning vectors ENG Generates the structural set definition entity USET for each boundary condition and forms the MKUSET partitioning vectors and transformation matrices used in matrix reduction MK2GG ENG Interprets solution control and gene
253. appended to this basic name If such a name is too long to accomodate a subscript then characters are truncated on the right with warning ASTROS MAPOL PROGRAMMING 9 5 USER S MANUAL 9 2 2 COMMENTARY Commentary may be included in the MAPOL program by enclosing the text between two dollar signs Comments may be one or more complete lines or they may be embedded in a line as shown below 2 ET B TO 4 UY HIS IS A MULTI INE COMMENT HAT SHOWS HOW 1T MUST ONLY START END WITH DOLLAR A B THIS IS AN INTERLINE Z U A S B T L E A E 9 2 3 SIMPLE DATA TYPES The MAPOL language supports five simple data types e INTEGER REAL e COMPLEX e LOGICAL e LABEL MAPOL is a strongly typed language and as such all variables must be declared at the beginning of a program unit This is done with one or more declaration statements The syntax of a declaration state ment is defined by the rules shown below lt decl gt lt type gt lt var list gt lt type gt REAL INTEGER COMPLEX LOGICAL LABEL lt var list gt lt var gt lt var gt lt var list gt Each simple variable with the exception of LABEL may be an array with one subscript This is defined by 9 2 3 1 Data Type INTEGER INTEGERS are whole numbers such as 157 83 or 22 An INTEGER may also havea sign associated with it such as 47 or 1024 The range of integers depends upo
254. are written when the system encounters data that arein error to the ex tent that continuation is impossible The system will terminate execution either immedi ately or after some minor clean up If the user is unable to decipher the error message the following steps can be helpful in determining the source of the error 1 Check the timing summary with the LOGBEGIN and LOGMODULE options in the DE BUG packet against the MAPOL sequence path to determine which module generated the error message Also check the SYSGEN output to determine the module that wrote the message Note that the message number is included in the error message print if the message is a standard one and the message number can be used to trace the module that uses the message 2 Check the Programmer s Manual documentation for the relevant module to determine the error checks it performs and to get further information on the source of the error 8 2 SOLUTION CONTROL OUTPUT OPTIONS This Section presents a detailed description of the output quantities that can be selected through the solution control packet These quantities fall into five categories 1 element 2 nodal 3 design 4 eigenvalues for flutter and normal modes and 5 aeroelastic trim quantities Each of these categories is presented in the separate subsections that follow The PRINT and PUNCH solution control commands are used to request the desired output quantities These commands have three gro
255. argument identifies the GRIDLIST to use in the function and the second argument defines the allowable upper limit allow of the constraint Note that this is the technique used to define a normalized constraint for the optimization step It is highly recommended that functional constraints be normalized in this manner In order for the optimizer to perform properly it is mandatory that the syn thetic constraint be negative when satisfied and positive when violated It is recommended that the synthetic constraint be normalized such that its values areon the order of unity The Bulk Data used to define the functional parameters is then given by BEGIN BULK GRIDLIST 1 5 10 15 20 DCONF 101 CONST DCN1 DCN1 GLIST l ALLOW 100 0 ENDDATA Example 2 Stress Resultant Limits The following example computes multiple constraints for the stress resultants of selected QUAD4 elements The Solution Control packet references the functional design constraint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC STATICS DCFUNCTION 101 The Function Packet defines the function specification for computing the allowable stress resultant The general expression for this is RESULT V SIGX SIGY ASTROS THE FUNCTION PACKET 6 15 USER S MANUAL This is then applied to all QUAD4 elements in the rang
256. associated DOF is SUPORTed 3 The flexible derivative which includes corrections for the flexibility and inertia relief ef fects This output only appears if the associated DOF is SuPoRTed If the first two forms do not agree closely within 1 2 percent the spline transformation may be incorrect or some of the applied load is being reacted by model spcs or mpcs before reaching the SUPORT points This latter is the most common occurrence so that SPCFORCE and GPFORCE data are the first place to look to correct the problem The SPLINEd and FLEXIBLE forms are used in the stability coefficient constraint calculations DCONALE DCONCLA DCONSCF 8 32 OUTPUT FEATURES ASTROS USER S MANUAL Finally the trim parameters that were computed for the current flight condition are shown In general these are the angle of attack in degrees the pitch rate in deg s and the SYMMETRIC control surface deflection angle s in degrees In each case the rigid and flexible trim state is shown the rigid is informational only and the parameter is labeled as COMPUTED if it was a free parameter in the trim analysis or USER INPUT if it was a fixed user input trim parameter Only those parameters explicitly called out on the TRIM bulk data entry are listed The ANTISYMMETRIC trim print is similar except that the degrees of freedom that are available result in coefficients for side force rolling moment and yawing moment ey Cr Cn Yaw angle in both radia
257. ata and to compute and view additional data In fact these options enable the user to obtain virtually any data that reside on the data base or that can be computed and stored on the data base Finally a quick overview of the Interactive eBASE Environment eSHELL is given The eSHELL program provides for complete Standard Query Language interactive queries on the eBASE entities ASTROS OUTPUT FEATURES 8 1 USER S MANUAL 8 1 SYSTEM CONTROLLED OUTPUT Many of the engineering and executive system program units write data to the ASTROS output listing automatically As enumerated in the introduction to this section output of this nature in ASTROS is very limited but sufficient amounts exist to justify a brief presentation of the data and their formats It is also useful to present the basic ASTROS listing in order to facilitate contrasting it to listings containing user selected output quantities The first page of ASTROS output is the title page showing the version number date and host machine Each page of output following the solution control listing is labeled with six lines of header information including the user selected title subtitle and label The version number date and if applicable the design iteration number will also appear in the header of each page 8 1 1 Default Output Printed by Modules The DEBUG packet echo and the ASSIGN DATABASE entries shown in Table 8 1 are the first output following the title page Immediately foll
258. ata entry that defines flutter constraint conditions k Selects the input matrix for splining the extra points to the aerodynamic model Refers to a DMI bulk data entry 1 Selects the direct input stiffness matrix Refers to a DMI Or DMIG bulk data entry m Selects the direct input mass matrix Refers to a DMI Or DMIG bulk data entry n Selects the direct input damping matrix Refers to a DMI Or DMIG bulk data entry o Selects the transfer function set to be added to the input matrices Refers to TF bulk data entries p Set identification of VSDAMP and or TABDMP bulk data entries that define damping data q Set identification of DCONF constraint functions Remarks 1 If any discipline has a caseid then all disciplines must have a caseid All caseid values must be unique but they need not be in any particular order Disciplines are implicitly numbered from 1 to n if no caseid values are specified The caseid is only used as a reference from user defined functions in the F unction Packet The FLCOND option is required all others are optional 3 M2PP B2PP and K2PP and CONTROL names will typically refer to DMI and DMIG entries but may refer to any existing database entity of the proper dimension 4 The use of the CONTROL matrix requires that extra points be defined in the boundary condi tion 5 26 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL FREQUENCY Solution Control Command FREQUENCY Description Invokes the frequ
259. ated using this spline I nteger gt 0 SETG The identification of a SETi entry which lists the structural grid points to which the spline is attached Integer gt 0 DZ Linear attachment flexibility Real gt 0 0 SS Torsional flexibility J Real gt 0 0 use 1 0 for bodies CID Rectangular coordinate system which defines the y axis of the spline Integer gt 0 if lifting surface or blank not used for bodies DTHX DTHY Rotational attachment flexibility DTHX is for rotation about the x axis not used for bodies DTHY is for rotation about the y axis used for slope of bodies Real Remarks 1 Theinterpolation points k set will be defined by aero cells 2 For panels the spline axis is the projection of the y axis of coordinate system CID projected onto the plane of the panel For bodies the spline axis is parallel to the x axis of the aerodynamic coordinate system 3 The flexibilities are used for smoothing Zero attachment flexibilities will imply rigid attachment i e no smoothing Negative values of DTHX and or DTHY will imply no attachment The continuation card is optional The SPLINE2 EID must be unique with respect to all other SPLINEi data entries it is used only for error messages ASTROS THE BULK DATA PACKET 7 223 SPOINT Input Data Entry SPOINT Scalar Point List USER S MANUAL Desc
260. ause problems in the current module s algorithm As much as possible these error messages are intended to be standalone in that the user should be able to interpret the message without referring to the Programmer s Manual There are four different levels of errors that can occur in ASTROS each labeled differently when printed 1 System Fatal Message These messages come about due to errors or inconsistencies in the system definitions Usually these relate to erroneous input to the system generation utility SYSGEN or are a result of using an outdated system data base You should contact your system adminis ASTROS OUTPUT FEATURES 8 7 USER S MANUAL trator to effect a correction Hopefully these errors will rarely occur and should never oc cur in an unmodified ASTROS system 2 User Information Message These messages are written when the system encounters data that may represent an in put error or may later generate a problem but that may only bea special user input that falls outside the expected range Usually these messages can be ignored This is the least serious type of user message in ASTROS 3 User Warning Message These messages are written when the system encounters data that are incorrect but which may not cause termination In some cases this level of error is issued to signify that the system will continue to search for errors but will terminate abnormally following the search 4 User Fatal Message These messages
261. ay not result in equal grid point loads ASTROS THE BULK DATA PACKET 7 195 PLYLIST Input Data Entry PLYLIST A list of composite element layer numbers USER S MANUAL Description Defines a set of layers of composite elements by a list Format and Examples 1 2 3 4 5 6 7 8 9 10 PLYLIST SID P1 P2 P3 P4 P5 P6 P7 CONT CONT P8 etc PLYLIST 3 1 2 3 4 16 15 14 ABC BC 13 Alternate Form T 2 3 4 5 6 7 8 9 10 PLYLIST SID P1 THRU P2 Field Contents SID Set of identification numbers Integer gt 0 Pi List of ply numbers Integer gt 0 Remarks 1 These entries are referenced by the DESVARP DESVARS DCONLMN DCONPMN DCONLAM and DCONTH2 data entries 2 When using the THRU option all intermediate plies will be assumed to exist 3 When used by DESVARS and DESVARP the entry refers to composite layer numbers to be linked together in the design model 4 When used by DCONLMN DCONPMN and DCONLAM the entry refers to composite layers that together define a ply or a laminate whose summed thicknesses will be contribute to the constraint 7 196 THE BULK DATA PACKET ASTROS USER S MANUAL PMASS Input Data Entry PMASS Scalar Mass Property Description Used to define the mass value of a scalar mass element which is defined by means of the CMASS1 entries Format and Examples
262. be printed Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which applied loads are to be printed Set identification of a GRIDLIST bulk data entry that is used to request the grid points degrees of freedom for which the mass matrix is to be printed Set identification of an LDVLIST and or a GDVLIST bulk data entry that is used to request the design variables for which mass sensitivities are to printed Set identification of a GDVLIST bulk data entry that is used to request the design variables for which objective function gradients are to be printed Set identification of an ELEMLIST bulk data entry that is used to request the aerodynamic elements for which QuHH is to be printed Set identification of an ELEMLIST bulk data entry that is used to request the aerodynamic elements for which 9HJ is to be printed Set identification of an MODELIST bulk data entry that is used to request the modes for which flutter and normal modes eigenvalue results are to be printed 5 34 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL PRINT aa Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which spc forces are to be printed ab Set identification of a GRIDLIST bulk data entry that is used to request the grid points degrees of freedom for which the stiffness matrix is to be printed ac Set identification of an ELEMLIST bulk data entry that is used to request the
263. ber of eigenvectors to be computed 2 Integer gt 0 default 3 NEST E The mass orthogonality test and eigenvalue convergence parameter A non zero value requests a check of the mass orthogonality of the eigenvectors Real gt 0 0 default 10 NORM Method for eigenvectors normalization 5 6 Method for normalizing eigenvectors one of the character values MASS MAX or POINT mass Normalize to unit value of the generalized mass MAX Normalize to unit value of the largest component in the analysis set Default POINT Normalize to unit value of the component defined by G c defaults to max if point is not defined GID Grid or scalar point identification number Required only if NORM POINT nteger gt 0 DOF Component number One of the integers 1 6 Required only if NORM POINT and G is a geometric grid point Remarks 1 The real eigenvalue extraction method set must be selected in Solution Control METHOD SID to be used 2 The number of eigenvalues and eigenvectors extracted depends on the FL FU and NVEC values A summary is given in the table found with entry EIGR Lanczos 3 If you select NORM MASS the eigenvectors are normalized to a unit value of the generalized mass If you select NORM MAX the eigenvectors are normalized with respect to the largest component value in the g set When using the Max normalization with Dynamic Reduction the g set degrees of freedom excluding the dynamic reduction genera
264. ble at all for supersonic flow 7 Reduced frequency is computed using bo 2v where b is the reference chord defined by an AERO entry is the frequency in radians per sec and v is the true velocity ASTROS THE BULK DATA PACKET 7 163 MODELIST Input Data Entry MODELIST USER S MANUAL Description Defines a list of modes at which outputs are desired Format and Example 1 2 3 4 5 6 7 8 9 10 MODELIST SID MODE1 MODE2 MODE3 MODE4 MODE5 MODE6 MODE7 CONT CONT MODE8 MODE9 etc CONT MODELIST 100 1 2 4 Alternate Form 1 2 3 4 5 6 7 8 9 10 MODELIST SID MODE1 THRU MODE2 Field Contents SID Set identification number referenced by Solution Control Integer gt 0 MODE i Mode number of mode at which outputs are desired Integer gt 0 Remarks 1 In order to be used the SID must be referenced by Solution Control 2 Ifthe alternate form is used MODE2 must be greater than or equal to MODE1 3 Modes are numbered from 1 to n starting at the lowest frequency for which a eigenvector was computed 4 Nonexistent modes may be referenced and will result in no error message 7 164 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry MOMENT MOMENT Static Moment D
265. bodies see PAERO2 orientation flag C ZY bodies D Y bodies 7 30 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry CAERO6 CAERO6 Description Defines an aerodynamic macroelement panel for USSAERO Format and Example I 2 3 4 5 6 7 8 9 10 CAERO6 ACID CMPNT CP IGRP LCHORD LSPAN CAERO6 1 WING 1 20 30 Field Contents ACID Component identification number Integer gt 0 CMPNT Aircraft component Character selected from WING FIN CANARD CP Coordinate system Integer gt 0 or blank See Remark 4 IGRP Group number for this component Integer gt 0 LCHORD Identification number of an AEFAcT Bulk Data entry containing a list of division points in percent chord for chord wise boxes for the aerodynamic surface If LCHORD is zero the chord wise divisions are identified by the IPANEL entry on the AIRFOIL Bulk Data entry Integer gt 0 or blank LSPAN Identification number of an AEFACT Bulk Data entry containing a list of division points for spanwise boxes For WINGS and CANARDs use the y lateral dimensional coordinates of the stations and for FINs use the z vertical dimensional coordinates If LSPAN is zero or blank the y z locations from the AIRFOIL Bulk Data entries for the component ACID are used Integer gt 0 or blank Remarks 1 The IGRP field allows related components to be processed together for interference effects e g
266. cal Manual with the engineering capabilities of the ASTROS system and is using this manual to define the form of the particular input that directs the system to perform a desired function The Theoretical Manual describes the range of capabilities of the ASTROS system while the Program mer s Manual is provided to give details of the internal function of the engineering and programming utility modules The eBASE Schemata Manual documents all of the database entities The Installation and System Support Manual describes how ASTROS is installed on host computers and how it may be configured for customized use This manual is intended to provide the user with a convenient reference for all forms of input to the system and is therefore organized along the same lines as the input data stream The discussion of each topic is brief and generic and is followed by detailed documentation of the user inputs Information on ASTROS output formats is in a separate chapter as is the description of the Matrix Analysis Problem Oriented Language MAPOL used for programming ASTROS ASTROS INTRODUCTION 1 1 USER S MANUAL Finally this manual is directed toward the engineer designer analyst who is using ASTROS to perform engineering design or analysis While ASTROS is perfectly capable of performing many tasks not explic itly supported in the standard execution the user must know the engineering software in considerable detail to direct the system to perform th
267. cally resorts the input subcases to solve the maximum number of right hand sides for a given aeroelastic correction matrix The results are then returned to the order specified by the user with no limitations imposed Similarly the flutter discipline loops over a set of direct dynamic input matrices to accommo date multiple closed loop systems using a single set of structural matrices The only limits are those of symmetry discussed earlier in which the structural and aerodynamic symmetries should be the same for all subcases in a boundary condition and the restriction to a single transient and a single frequency response per boundary condition Table 5 2 Summary of ASTROS Disciplines DISCIPLINE DESCRIPTION STATICS Static structural analysis MODES Normal modes of vibration SAERO Steady state aeroelastic analysis FLUTTER Aeroelastic stability analysis TRANSIENT Transient response analysis FREQUENCY Frequency response analysis 5 8 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL 5 3 1 DISCIPLINE OPTIONS Each of the disciplines requires further options to completely define the execution process These options point to set IDs in the bulk data packet that define engineering data For example the STATICS discipline requires that loads information be supplied This is implemented in ASTROS by a parentheti cal phrase attached tothe statics discipline SOLUTION OPTIMIZE STRATEGY FSD
268. cally compute mass for all structural elements 5 Weight density may be entered in Field 9 if the value 1 g where g is the acceleration of gravity is entered on the CONVERT entry ASTROS THE BULK DATA PACKET 7 159 MAT9 Input Data Entry Description MAT9 Material Property Definition Form 9 als for solid isoparametric elements Format and Example USER S MANUAL Defines the material properties for linear temperature independent anistropic materi 1 2 3 4 5 6 7 8 9 10 MAT9 MID G11 G12 G13 G14 G15 G16 G22 CONT CONT G23 G24 G25 G26 G33 G34 G35 G36 CONT CONT G44 G45 G46 G55 G56 G66 RHO Al CONT CONT A2 A3 A4 A5 A6 TREF GE MAT9 17 6 2 3 6 2 3 ABC BC DEF EF Dia lrES E SLFS 372 6 6 6 Field Contents ID Material identification number Integer gt 0 Gij Elements of the 6x6 symmetric material property matrix Real gt 0 0 RHO Mass density Real gt 0 0 Ai Thermal expansion coefficient vector Real TREF Thermal expansion reference temperature Real GE Structural element damping coefficient Real Remarks 1 The material identification numbers must be unique for all MAT1 MAT2 MAT8 and MAT9 entries 2 The mass density RHO will be used to automatically compute mass in a structural dynamics problem 3 Weight density may be entered in Field 9 if the value 1 g where g is the acceleration of gravity is entered o
269. case 6 42 THE FUNCTION PACKET USER S MANUAL USER S MANUAL STRAIN Intrinsic Function STRAIN Purpose Toretrieve current element STRAIN values Usage STRAIN elemop strain_comp plyop caseop modeop where eid elemop gt ELEMLIST elem sid e plyid DIYOR r PLYLIST ply_sid a ES caseid eT CASELIST case_sid modeo gt modei p MODELIST mode_sid Function Arguments eid Identification of an element specified in the Bulk Data Packet elem_sid Set identification of an ELEMLIST bulk data entry used to specify an element strain_comp Element response component plyid Identification of a layer number for a composite element ply_sid Set identification of a PLYLIST bulk data entry used to specify the layer number for a composite element caseid Subcase identification case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number modeid Identification of a mode index mode_sid Set identification of a MODELIST bulk data entry used to specify the mode index ASTROS THE FUNCTION PACKET 6 43 STRAIN USER S MANUAL Notes 1 When an element identification is used then the eid must be unique and if the eidis not unique then an element list must be used The allowable response components for each element type are shown in Table 20 Composite elements must have their layer identification number specified Strain components will always be reco
270. cription Defines adjustment factors of control surface effectiveness values for use in flutter analy sis Format and Example 1 2 3 4 5 6 7 8 9 10 CONEFFF EFFID EFF MODE MACROID BOX1 BOX2 CONEFFF 10 0 60 6 1001 1007 1021 Field Contents EFFID Effectiveness identification number Integer gt 0 EFF Effectiveness value Real ODE Structural mode to which the effectiveness is to be applied Integer gt 0 ACROID Aerodynamic component macroelement on which the control surface lies BOX1 BOX2 First and last box whose effectiveness is to be altered Integer gt 0 BOX2 gt BOX1 Remarks 1 TheEFFID is referenced by the FLUTTER bulk data entry 2 The EFFID need not be unique 3 The pressures for the referenced mode and all the referenced boxes will be modified by the EFF parameter For example EFF 0 60 indicates a 40 percent reduction in the effectiveness for the affected boxes 4 Refer tothe SPLINE1 bulk data entry for the interpretation of BOX1 and BOX2 ASTROS THE BULK DATA PACKET 7 43 CONEFFS USER S MANUAL Input Data Entry CONEFFS Static aerodynamic control effectiveness data Description Defines adjustment factors for control surface effectiveness values for use in static aeroe lastic analysis and nonplanar aerodynamic analysis Format and Example 1 2 3 4 5 6 7 8 9 10 CONEFFS
271. cteristics memory utilization and algorithm control For maximum flexibility configurations may be controlled by the site i e the UAI support specialist or the end user Many different configurations may be defined for a site For example when configuring ASTROS the UAI support specialist may create different configurations for very small and for very large analyses The starting point for configuring the UAI products is the Default Preference File uaidef included in your delivery The other modifications described above are made in other Preference Files The actual configuration used for a given execution is determined by applying the specified Preference Files in the following sequence e First the Default Preference File is processed and all parameters included in this file are set to their specified values e Second the System Preference File is processed and any parameters included in it replace those previously defined e Third the User Preference Fileis processed and again any parameters included in it replace those previously defined In summary the final configuration is the union of the Preference files The Default Preference file contains a value for every parameter used by the product suite The other Preference Files need only contain those parameters that differ from and override the default values 2 2 RUNNING ASTROS ASTROS USER S MANUAL Each Preference File is composed of as many as six Sections e Th
272. d G3 as illustrated below 2 The total load on the surface AP is divided into three equal parts and applied to the grid points as concentrated loads A minus sign in field 3 reverses the direction of the load 3 In the case of a quadrilateral surface the grid points G1 G2 G3 and G4 should form a consecutive sequence around the perimeter The right hand rule is applied to find the assumed direction of the pressure Four concentrated loads are applied to the grid points in approximately the same manner as for a triangular surface The following specific procedures are adopted to accommodate irregular and or warped surfaces a The surface is divided into two sets of overlapping triangular surfaces Each triangular surface is bounded by two of the sides and one of the diagonals of the quadrilateral b One half of the pressure is applied to each triangle which is then treated in the manner described in Remark 2 4 Load sets must be selected in Solution Control to be used PLOAD2 USER S MANUAL Input Data Entry PLOAD2 Plate element static pressure load Description Defines a uniform static pressure load applied to plate elements Format and Example 1 2 3 4 5 6 7 8 9 10 PLOAD2 LID P EID1 EID2 EID3 EID4 EID5 EID6 PLOAD2 156 9862 101 432 657 Alternate Form 1 2 3 4 5 6 7 8 9 10 PLOAD2 LID P
273. d Set identification of a MODELIST bulk data entry used to specify the mode index vvalue Velocity value vel_sid Set identification of a VELOLIST bulk data entry used to specify the velocity value caseid Subcase identification ASTROS THE FUNCTION PACKET 6 33 FFREQ USER S MANUAL case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number Notes 1 The frequency is returned in Radians Conversion to Hertz may be accomplished by using the HERTZ intrinsic function 2 The specific discipline request defines whether the case and or mode is a valid request in the response functions 3 If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 34 THE FUNCTION PACKET USER S MANUAL USER S MANUAL FLEXCF Intrinsic Function FLEXCF Purpose To retrieve flexible stability coefficients for a specific trim parameter from a Static Aerody namics analysis Usage l caseid FLEXCF axis trim_param CASELIST case_sid l l Function Arguments axis Input axis param Trim parameters caseid Subcase identification case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number Notes 1 This function returns its results in radians If degrees are required the results may be converted using the DEGS intrinisic function 2 The allowable values for axis are ASTROS THE FUNCTION PACKET 6
274. d cause four separate partitionings of the system level matrices On the other hand the sequence ANALYZE BOUNDARY SPC 10 METHOD 30 STATICS MECH 10 ODES BOUNDARY SPC 20 STATICS MECH 20 BOUNDARY SPC 100 METHOD 40 MODES eliminates one of the four partitioning operations 5 3 DISCIPLINES A number of types of analyses or disciplines can be performed during a given ANALYZE Or OPTIMIZE boundary condition In fact it is this multidisciplinary capability that makes the ASTROS code viable in a preliminary design context The preceding sections have already alluded to the fact that each of these disciplines has an associated set of commands ASTROS THE SOLUTION CONTROL PACKET 5 7 USER S MANUAL ANALYZE BOUNDARY SPC 30 DISCIPLINE 1 DISCIPL A suite of eight disciplines are available in ASTROS as shown in Table 5 2 Of these options TRANSIENT and FREQUENCY do not generate any design constraints and so are not useful in OPTIMIZE boundary conditions Should the user wish to see output from these disciplines during the optimization however they are supported in the OPTIMIZE subpacket The standard MAPOL sequence contains almost no restrictions on the combination of disciplines and subcases in a boundary condition SAERO disciplines for example require multiple symmetry Mach number and dynamic pressure dependent correction matrices The standard algorithm automati
275. d subsequently in MAPOL expressions and others modules The window in which the MovLIM bound is overridden to allow local variables to change sign If WINDOW is 0 0 then the local variable may not change sign If it is nonzero the half width of a band around zero called EPS is computed by 0 0 WINDOW TCEVAL EPS WINDOW 100 MAX ABS TMIN ABS TMAX 20 0 If the local variable falls within the band then the new minimum or maximum for the current iteration is changed to lie on the other side of zero from the local variable Output from SOLUTION ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 7 NAME MODULES DESCRIPTION ASIZE GDR3 The number of a set degrees of freedom BC N A Boundary condition loop counter BCID many Boundary condition identification number Indicates if the current statics subcases contain design dependent gravity or thermal DDFLG DDLOAD loads Output by DDLOAD ESIZE BCBGEDT The number of extra points in the boundary condition others GNORM GDR3 The sum of LJSET and LKSET IFP The number of structural degrees of freedom in the model Output from IFP and GSIZEB dthers subsequently used in many modules GSIZE SDR GSIZEB modified subject to dynamic reduction others FLUTTRAN OFPEDR N i i HSIZE umber of eigenvectors extracted by the REIG module Set in REIG REIG others LJSET GDRi Number of degrees of freedom in the j set in dynamic reduction Set in GDR1 LKS
276. d substitution phase to solve general systems of linear equations GFBS that have been decomposed with module DECOMP Processes the n set stiffness matrix to identify singularities and if requested automatically GPSP ENG remove them GPWG ENG Grid point weight generator module ENG Reduces the symmetric g set stiffness mass or loads matrix to the n set if there are multipoint GREDUCE constraints in the boundary condition Assembles the current static applied loads matrix for any statics subcases in the current GTLOAD ENG boundary condition from the constant simple load vectors and the design dependent load sensitivities Reads the Bulk Data File and loads the input data to relations Computes the external IFP ENG coordinate system transformation matrices and creates the basic grid point data Also performs bandwidth minimization INERTIA ENG Computes the rigid body accelerations for statics analyses with inertia relief ITERINIT ENG Initializes the const relation for the current iteration LAMINCON ENG Computes constraint values for laminate thickness constraints ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 15 USER S MANUAL Table 3 8 Summary of ASTROS Modules Continued MODULE TYPE DESCRIPTION NAME LAMINSNS ENG Computes constraint sensitivities for laminate thickness constraints Assembles the simple load vectors
277. data types e MATRIX e IMATRIX RELATION e UNSTRUCT e IUNSTRUCT All of these types represent database entities Matrices and unstructured entities may be handled only in their entirety in MAPOL Relations may be accessed on an entry by entry and attribute by attribute basis Use of the IMATRIX and IUNSTRUCT I for indexed data types allows for more efficient retrieval of data that are accessed in a random order 9 2 4 1 Data Types MATRIX and IMATRIX Matrix database entities are declared in a slightly different manner from the remaining data types The rules for their declaration are lt decl gt MATRIX lt mat 1list gt lt mat list gt lt mat list gt lt mat var gt lt mat var gt lt mat var gt lt ident gt lt ident gt subl sub 2 lt subl gt E INTEGER lt sub2 gt INTEGER Note that the matrix lt ident gt is enclosed in square brackets i e for clarity and ease of reading of MAPOL programs Matrix expressions then look as they do written in standard mathematical nota tion Matrix variables may also be subscripted to allow multiple entities to be referenced using the same lt ident gt This feature is used in ASTROS to allow data from multiple boundary conditions to be saved for subsequent evaluation There is an implementation limit of two subscripts each of which may take on any integer value from 1 to 1000 However no more than 1000 entities may result from this declaration
278. database is done by selecting a STATUS of NEw with the optional user parameter KEEP if required on the local host on the ASSIGN DATABASE entry For example ASSIGN DATABASE CALVIN HOBBES NEW ASSIGN DATABASE VIN HOBBE 4 22 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL When restarting ASTROS using an existing database whose contents are to be preserved ASTROS must be notified to attach the existing run time database files without re initializing them This is done by selecting a STATUS Of OLD on the ASSIGN DATABASE entry For example ASSIGN DATABASE CALVIN HOBBES OLD If the status of OLD is not given existing database files are typically overwritten by the system The STATUS flag indicates the status of the data not of the files so the files may exist with a STATUS of NEW and will result in the database contents being replaced by the new execution 4 4 4 2 Suspending Restarting Execution ASTROS execution is controlled by the MAPOL sequence that is supplied in the MAPOL packet This may be the standard sequence if the packet is omitted an edited version of the standard sequence or a user supplied sequence To suspend execution a MAPOL sequence must be defined which results in clean termination one without fatal errors of the ASTROS execution This may be the standard execution or more typically an edited standard sequence or even a standalone MAPOL program Most commonly
279. defaults to the material coordinate system if scsID is blank 7 202 THE BULK DATA PACKET ASTROS USER S MANUAL PTRMEM Input Data Entry PTRMEM Description Defines property data for TRMEM element Format and Examples 1 2 3 4 5 6 7 8 9 10 PTRMEM PID MID T NSM TMIN PTRMEM 500 1000 0 15 Field Contents PID Property entry identification number Integer gt 0 MID Material property identification Integer gt 0 E Thickness of membrane element Real gt 0 0 NSM Nonstructural mass associated with the element Real gt 0 0 or blank TMIN Minimum thickness for design Real gt 0 0 or blank Default 0 0001 Remarks 1 The PTRMEM entry can reference either MAT1 MAT2 or MATS entries 2 TMIN is ignored unless the element is linked to global design variables by SHAPE entries ASTROS THE BULK DATA PACKET 7 203 RBAR Input Data Entry USER S MANUAL RBAR Rigid Bar Description Defines a Rigid Bar element with 6 degrees of freedom at each end Format and Example 1 2 3 4 5 6 7 8 9 10 RBAR SETID EID GA GB CNA CNB CMA CMB RBAR 1001 5 1 2 234 123 Field Contents SETID Multipoint constraint set identification number specified in Solution Control Integer gt 0 EID Rigid Bar element identification number Integer gt 0 GA GB Grid point identification numbers of connection points I
280. dered to be a separate subcase It is important to note in this case that more than one subcase is represented by a single solution control discipline statement In output requests therefore the subcases for which output is desired must be explicitly selected This is presented in greater detail in Section 5 4 and in Chapter 6 5 3 4 SAERO Discipline Options The SAERO discipline must have a TRIM condition and symmetry type specified in the solution control The symmetry default is SYMMETRIC For analysis this selection completes the specification of the discipline with each TRIM condition generating one subcase In the OPTIMIZE subpacket the DCON STRAINT option can be used to select a number of different constraint types which depend on the type of TRIM analysis selected In general the DCONSTRAINT can refer to DCONDSP bulk data entries for displace ment constraints DCONCLA for lift effectiveness constraints DCONALE for aileron effectiveness con straints DCONSCE for stability coefficient constraints and DCONTRM for constraints on trim parameters The SAERO discipline always generates a static displacement field to which any static constraint may be applied Stress constraints defined on DCONTW DCONTWM DCONTWP DCONVM DCONVMM DCONVMP are 5 12 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL selected by the STRESSCONSTRAINT option Strain constraints defined on DCONFT DCONFTM DCONFTP DCONEP DCONEPM and DCONEPP are Selected by the
281. design constraints are defined using the DCONF entry in the Bulk Data packet The primary use of functions is for synthetic response constraints and synthetic objective functions that are requested in the Solution Control packet In the following example the Bulk Data Packet defines values for the element identification numbers and the allowable stress resultant for functional design constraint 101 It points to the function SIG in the Function Packet This will be more fully explained in subsequent sections BEGIN BULK DCONF 101 SIG DCN1 DCN1 EID 10 ALLOW 45000 0 ENDDATA The DCONF Bulk Data defines the calling arguments for the named function stc Each argument is defined by its name e g EID and the value to be used in this invocation of the function Notice that by using name value pairs there is no order dependence While arguments may thus be defined on the DCONF entry it is still required to define all of the function arguments 6 3 FUNCTION SYNTAX The function packet contains the functional specification equations that are used as either the design constraints or the objective function This packet has the general form FUNCTIONS func_def ENDF UNC where func_def is the definition of a specific function Each function func_def must have a single variable specified on the left of an equality expression 6 4 THE FUNCTION PACKET USER
282. dified Method of Feasible 0 003 Directions A constraint is active if its numerical i value is more positive than CT CTL Same as cr but for linear constraints 0 003 CTLMIN Same as CTMIN but for linear constraints 0 0005 Minimum constraint tolerance for nonlinear CTMIN constraints If a constraint is more positive than 0 0005 CTMIN it is considered to be violated Maximum absolute change in the objective DABOBJ between two consecutive iterations to indicate maxo 001 Fo 0 0001 convergence in optimization Absolute convergence criterion for the DABOBM optimization sub problem when using Note 3 sequential minimization techniques DABSTR Same as DABOBJ but used at the strategy level Note 3 Maximum relative change in the objective DELOBJ between two consecutive iterations to indicate 0 001 convergence in optimization ASTROS THE BULK DATA PACKET 7 169 MPPARM USER S MANUAL REAL PARAMETER DEFINITION DEFAULT DELOBM Relative convergence criterion for the optimization sub problem when using sequential minimization techniques Note 3 DELSTR Same as DELOBJ but used at the strategy level Note 3 DOBJ1 Relative change in the objective function attempted on the first optimization iteration Used to estimate initial move in the one dimensional search Updated as the optimization progresses DOBJ2 Absolute change in the objective function attempted on the f
283. discipline aa Specifies that the Fast Fourier technique is to be used in the TRANSIENT Or GUST disciplines THE SOLUTION CONTROL PACKET 5 9 USER S MANUAL OPTION DESCRIPTION FLCOND Specifies parameters for the FLUTTER discipline CONTROL Specifies the name of a control surface modifier matrix for flutter analysis cust Specifies that a gust analysis is to be performed for the accompanying transient or frequency discipline ete Specifies an input stiffness matrix on the physical degrees of freedom for FREQUENCY TRANSIENT and FLUTTER disciplines MPB Specifies an input mass matrix on the physical degrees of freedom for FREQUENCY TRANSIENT and FLUTTER disciplines sone Specifies an input damping matrix on the physical degrees of freedom for FREQUENCY TRANSIENT and FLUTTER disciplines TEL Specifies transfer functions that are to be included in FREQUENCY TRANSIENT and FLUTTER disciplines Specifies structural or viscous damping to be used in FREQUENCY DAMP ING an TRANSIENT and FLUTTER disciplines The discipline types are OPTION DESCRIPTION O Specifies that the direct method is to be used in the TRANSIENT or FREQUENCY disciplines NODAL Specifies that the modal method is to be used in the TRANSIENT or FREQUENCY disciplines Specifies that the SAERO subcase is to use aerodynamics derived with SYMMETRIC E symmetric conditions about the
284. do not appear in any but the dynamic response disciplines FLUTTER TRANSIENT and FREQUENCY When nodal output is requested for dynamic analyses any extra point results may be selected using the GRIDLIST entry just as are grid and scalar point results Nodal output is available for all disciplines in ASTROS although particular nodal response quantities may not be available for all disciplines The solution control print options VELOCITY DISPLACEMENT GPFORCE LOAD SPCFORCE and ACCELERATION are used to select print of the nodal response quantities Each of these print options selects either ALL NONE or an integer set identification number that refers to one or more GRIDLIST bulk data entries Chapter 3 contains the complete description of the solution control print command Each output is carefully labeled as to its boundary condition number which discipline generated the output quantities and which load condition mode shape time step frequency step or flight condition is represented by the output 8 22 OUTPUT FEATURES ASTROS USER S MANUAL q2 F34 K1 gt F21 _ L F P 12 q1 F23 F14 Figure 8 11 Shear Panel Forces Table 8 15 SHEAR Solution Quantities SIMPLIFIED FIGHTER WING ASTROS VERSION 9 0 03 03 93 Pa 14 FINAL ANALYSIS SEGMENT STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 STRESSES IN SHEAR PANELS SHEAR ELEMENT MAX AVERAGE SAFETY ELEMENT MAX AVERAGE SAFETY TDs SHEAR SHEAR MARGIN TDs SHEAR SHEAR MARGIN 1
285. duction spe Selects single point constraints defining DOF s with fixed or prescribed motion SUPPORT Defines DOF s to provide support conditions for free free modal extraction inertial relief and aeroelastic analyses A boundary condition is defined by the BOUNDARY request and one or more of these further specifications all of which except BCID and AUTOSPC point to bulk data entries The boundary condition identification number BCID is only used by the Function Packet see Section 4 when user defined constraint functions are defined which span two or more different boundary conditions Note that all boundary conditions must have identification numbers or none may have them User functions may still span boundary conditions by using default BCID values The default is the ordinal numbering of the boundaries from 1 to n As enumerated above the specification of METHOD and ESET at this level in the hierarchy is in recogni tion of the fact that a number of the disciplines could require different sets of data for the associated items and it is desirable to group operations with one set of items together This does by definition create a restriction that only one eigenanalysis and only one size of p size matrices can be accommodated per boundary condition Examples of boundary definitions are ASTROS THE SOLUTION CONTROL PACKET 5 5 USER S MANUAL BOUNDARY BOUNDARY 100 BOUNDARY 20 REDUCE 30 SUPPORT 40
286. e Generates interpolation matrix relating displacements and forces between the steady aero and SPLINES ENG structural models Generates interpolation matrix relating displacements and forces between the unsteady aero SPLINEY ENG and structural models STEADY ENG Computes rigid unit forces and aeroelastic corrections for steady aero STEADYNP ENG Computes rigid trimmed forces for non planar models TCEVAL ENG Computes the current values of thickness constraints for this optimization iteration TRNSPOSE MAT Transposes a matrix UNSTEADY ENG Computes unsteady generalized forces USETPRT UTIL Prints the structural set definition table from the user entity for the specified boundary condition UTGPRT UTIL Prints several specific matrix entities in an interpretable form UTMPRG UTIL Purges matrix entities UTMPRT UTIL To print any matrix entity UTRPRG UTIL Purges relational entities To print any relational entity Only the first twelve attributes are printed and character UTRPRT JME attributes must be eight characters in length or they will be ignored UTUPRG UTIL Purges unstructured entities UTUPRT UTIL To print any unstructured entity WOBJGRAD ENG Computes the default objective function weight sensitivity YSMERGE ENG a ni lb ee for merging ys like vectors vectors of enforced displacements 4 18 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL 4 4 2 2 The Preface Segment In the context of optimization invarian
287. e Host Section e The eBase Section The eBase applib Section The eBase matlib Section e The eShell Section e The ASTROS Section The format of the Preference File and a brief description of its various sections are described in the following sections 2 1 2 1 The Format of Preference Files A Preference File is a text file which is composed of as many as six Sections indicated above Each Section includes a header followed by the parameters associated with the Section For ease of use the eBase and ASTROS Sections are subdivided into groups which contain related parameters The form of the file is shown in Table 2 1 2 1 3 Configuration Parameters Configuration parameters are defined using one of the forms param_name value param_name value value value The param_names are case insensitive The values when character strings or floating point numbers with exponents are also case insensitive unless they are enclosed in single quotations tics as param_name This is a Case Sensitive String Only one parameter may be specified on each line of the file Any characters that appear after value are treated as commentary and ignored You may also enter comments into the file by beginning a line with any of the characters or 2 1 4 The Configuration Sections The following sections provide an overview of the six Configuration Sections Details of each section as well as information needed to def
288. e Parameters NAME MODULES DESCRIPTION Indicates if there are any direct FREQUENCY response subcases in the current boundary BDFR BOUND condition Indicates if there are either TRANSIENT Or FREQUENCY response disciplines in the BDRSP BOUND current boundary condition Indicates if there are any direct TRANSIENT response subcases in the current boundary BDTR BOUND condition Indicates if there are any dynamic analyses FLUTTER TRANSIENT Of FREQUENCY in BDYN BOUND the current boundary condition BFLUTR BOUND Indicates if there are any FLUTTER analyses in the current boundary condition Indicates if there are any gust loads for either TRANSIENT Or FREQUENCY disciplines in BGUST BOUND the current boundary condition Indicates if there are any mechanical thermal or gravity static applied loads in the BLOAD BOUND current boundary condition BMASS BOUND Indicates if a mass matrix exists in the current boundary condition Indicates if there are any modal FREQUENCY response subcases in the current boundary BMFR BOUND condition Indicates if there are any disciplines that require that a normal MODES analysis be BMODES BOUND performed Indicates if there are any modal TRANSIENT response subcases in the current boundary BMTR BOUND condition BSAERO BOUND Indicates if there are any SAERO subcases in the current boundary condition DMODES BOUND Indicates if there are any modal disciplines in the current b
289. e corresponding c1 and or c2 must be zero or blank Zero or blank may be used to indicate a grounded terminal G1 or G2 with a correspond ing blank or zero c1 or c2 A grounded terminal is a point whose displacement is constrained to zero The two connection points G1 C1 and G2 c2 must be distinct 3 TMAX is ignored unless the element is designed using shape function linking ASTROS THE BULK DATA PACKET 7 35 CELAS2 Input Data Entry CELAS2 Scalar Spring Property and Connection USER S MANUAL Description Defines a scalar spring element of the structural model without reference to a property entry Format and Example 1 2 3 4 5 6 7 10 CELAS2 EID K G1 C1 G2 C2 CONT CONT TMIN TMAX CELAS2 28 6 2 3 32 19 4 Field Contents EID Element identification number Integer gt 0 K The value of the scalar spring Real gt 0 0 Gi Geometric grid point identification number Integer gt 0 Ci Component number 6 gt Integer gt 0 GE Damping coefficient Real gt 0 0 S Stress coefficient Real gt 0 0 TMIN TMAX Minimum and maximum values for design Real Remarks 1 Scalar points may be used for G1 and or G2 in which case the corresponding c1 and or c2 must be zero or blank Zero or blank may be used to indicate a grounded terminal G1 or G2 with a correspond ing blank or zero c1 or c2 A grounded terminal is a point whose displace
290. e element thickness in design Real gt 0 0 Default 10 Ti Membrane thickness of element at grid points Gi Real or blank see Remark 3 for default Remarks 1 TheTRIA3 geometry coordinate systems and numbering are shown in the figure below 7 64 THE BULK DATA PACKET Ye G3 TM Xe G2 G1 ASTROS USER S MANUAL CTRIA3 2 The material coordinate system TM and the offset ZOFF may also be provided on the PSHELL entry The property data will be used if the corresponding field on the CTRIA3 entry is blank The element reference plane is located at the mid thickness of the element parallel to the element mean plane 3 The Ti are optional if not supplied they will be set to the value of T specified on the PSHELL entry In such cases the continuation entry is not required 4 TMAX is ignored unless the element is linked to the global design variables by a SHAPE entry ASTROS THE BULK DATA PACKET 7 65 CTRMEM Input Data Entry CTRMEM Description Defines a triangular membrane element Format and Examples USER S MANUAL 1 2 3 4 5 6 7 8 9 10 CTRMEM EID PID G1 G2 G3 TM TMAX CTRMEM 100 500 1 7 12 Field Contents EID Element identification number Integer gt 0 PID Identification of PTRMEM or PCOMP entry Integer gt 0 Default EID Gi Grid point identifications of connection points Integer gt 0 TM Material orientation angle R
291. e entry which signifies that large data fields are to be used For continuation lines the asterisk used as the continuation character plays the role of the large fidd marker as shown below Each bulk data line must be either all narrow field or all large field although separate lines of a single bulk data entry can have different field widths simply by using the proper field marker This means that the same bulk data entry in wide and narrow formats are functionally identical with no need for separate templates Unlike NASTRAN the continuation mnemonics need not be unique among all the bulk data entries in the bulk data packet since there is no provision for randomly sorted continuations The input on a bulk data line can either be in fixed format in which each item must reside within the field to which it belongs or in free format in which fields are separated by commas and can be positioned anywhere to the left of the column in which the fixed field would normally start Free format input is indicated by the appearance of a comma in the first 10 characters of the input line ASTROS requires that each line not each bulk data entry be either all fixed or all free format and that each free format field be separated by a comma The NASTRAN use of a blank character as a field separator is not supported When free format input is used the continuation lines can reside on the same physical line of input with the continuation labels either included or not a
292. e equations to be programmed are shown in the following Ge SY Sg OT Seep Toy LO 20 GF So F WS 106 7 LOT eaey 118 E 4 120 In the following equations the elements of these sets are denoted by ie G2 je G1 6 16 THE FUNCTION PACKET USER S MANUAL USER S MANUAL 2 XMAGj Tara Ty ery 4 ra 8T2 T2 872 j 2 sde 13013 13 513 le G1 jeG2 SDOTi sign Tu Ty Tas ora Ty ery T2 E ra 8T2 73 8T2 4 T3 T3 Ta oTa 13 53 leG1 jeG2 XMAGij The solution control packet references the functional design constraint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC 1 STATICS DCFUNCTION 101 ASTROS THE FUNCTION PACKET 6 17 USER S MANUAL The Function Packet defines the function specifications for computing the relative displacements between two sets of grid points FUNCTIONS Alias for the grid list GLST GLIST GRIDLIST GLIST XMAG magnitude XMAG GLIST1 GLIST2 SORT COORD GLIST1 X1 DISP GLIST1 T1 COORD GLIST2 X1 DISP GLIST2 T1 2 COORD GLIST1 X2 DISP GLIST1 T2 COORD GLIST2 X2 DISP GLIST2 T2 2 COORD GLIST1 X3 DISP GLIST1 T3 COORD GLIST2 X3 DISP GLIST2 T3 2 SDOT Sign of the dot product Continued on following page SDOT GLIST1 G SIGN COORD GL COORD COORD COORD COORD COORD
293. e expression 8 7 4 has a resultant value of 14 the expression 8 7 4 has a resultant value of 8 the resultant value of the expression 3 0 2 0 6 0 is0 25 9 3 1 4 The Uses of Parentheses Parentheses may be used in arithmetic expressions to specify the order of operation This allows an evaluation that is different from the standard hierarchy Whenever parentheses are used the enclosed expression is evaluated prior to its use When such expressions are nested the innermost expressions are evaluated first The expression LU dd bed db dd 9 12 MAPOL PROGRAMMING ASTROS USER S MANUAL Table 9 4 MAPOL Operation Rules FOR TYPE OF X INTEGER REAL COMPLEX f INTEGER INTEGER REAL COMPLEX Binary Operators X op Y REAL REAL REAL COMPLEX COMPLEX COMPLEX COMPLEX COMPLEX Pon INTEGER INTEGER REAL ILLEGAL Exponentiation x y REAL REAL REAL ILLEGAL COMPLEX COMPLEX ILLEGAL ILLEGAL 9 3 1 5 Type and Value of Arithmetic Expressions Type conversions are performed when mixed expressions are evaluated The final value of an arithmetic expression may depend upon this type conversion Table 9 4 shows the conversions that occur when two operands are combined with an arithmetic operator Special rules apply to operations when one or more of the operations is of the type MATRIX These rules are discussed in Section 9 5 9 3
294. e length 3 Them set degrees of freedom specified on this entry may not be specified on other entries that define mutually exclusive sets 4 Rigid element identification numbers must be unique within each element type for each MPC set identification number ASTROS THE BULK DATA PACKET 7 211 SAVE Input Data Entry SAVE USER S MANUAL Description Defines a list of data base entities that are not to be purged Format and Examples 1 2 3 4 5 6 7 8 9 10 SAVE NAME1 NAME2 NAME3 NAME4 NAME5 NAME6 NAME7 NAME8 CONT CONT NAME9 NAME10 NAME11 etc SAVE DVCT Field Contents NAME i The name of a data base entity whose contents are not to be purged Remarks 1 Any number of continuations are allowed 2 This data entry is used by the UTPURG utility to determine if a requested purge of an entity will take place 7 212 THE BULK DATA PACKET ASTROS USER S MANUAL SEQGP Input Data Entry SEQGP Grid and Scalar Point Resequencing Used to manually order the grid points and scalar points of the problem The purpose of this card is to allow the user to reidentify the formation sequence of the grid and scalar points of the structural model in such a way as to optimize bandwidth Description Format and Examples 1 2 3 4 5
295. e of 1 through 10000 by the following Function Packet FUNCTIONS S Alias for the element list selection function ELST ELIST ELEMLIST elist Stress resultant RESULT ELIST SQRT STRESS ELST ELIST SIGX 2 STRESS ELST ELIST SIGY 2 Constraint for the Stress resultant CONST ELIST ALLOW RESULT ELIST ALLOW 1 0 ENDFUNC The Bulk Data Packet defines the element list for the QUAD4 elements defines functions and arguments for design constraint set 101 which points to the design constraint function const The first argument identifies the ELEMLIST to use in the function and the second argument defines the allowable upper limit of each constraint BEGIN BULK ELEMLIST 1 QUAD4 1 THRU 10000 DCONF 101 CONST DCN1 DCN1 ELIST 1 ALLOW 100 0 3 ENDDATA Example 3 Noninterference Constraints This example computes 16 constraints for the relative location between two sets of grid points G1 and G2 The relative location equals the magnitude of the square root of the sum of the squares of the displaced coordinate divided by the sense of the dot product between the points such that a positive number means that the two points are not touching This algorithm assumes that the geometric locations and the displacements are in the same coordinate system Th
296. e performed in either subpacket 5 2 BOUNDARY CONDITIONS Each analysis discipline requires a set of physical boundary conditions and in the case of unrestrained structures a set of fictitious supports These are defined in ASTROS in a manner very similar to that in NASTRAN namely through the definition of multipoint constraints MPC single point constraints SPC and support points SUPORT Unlike NASTRAN however ASTROS requires a more rigorous definition of a boundary condition The reason for this is that the user must ensure that the system matrices at each stage of matrix reduction up to the analysis set are uniquely defined by the boundary condition specification At or below the analysis set certain disciplines allow looping over families of direct matrix input damping options transfer functions etc For example if the user intends to perform a normal modes analysis a modal transient analysis and a modal flutter analysis in the same boundary condition ASTROS requires that the modal representation of the system under analysis be the same for each discipline in the boundary condition This requirement which is necessary to efficiently perform multidis ciplinary analysis adds a number of additional parameters to the boundary condition definition beyond the MPC SPC and SUPORT definitions They include definitions to perform matrix reductions available in NASTRAN through Bulk Data but not always selectable in the Case Control Packe
297. e printed Set identification of an DCONLIST bulk data entry that is used to request the the subset of active constraints for which gradients are to be printed See Remark 2 Set identification of an DCONLIST bulk data entry that is used to request the the subset of active constraints which are to be printed See Remark 2 Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which displacements are to be printed Set identification of an ELEMLIST bulk data entry that is used to request the elements for which strain energies are to be printed Set identification of an ELEMLIST bulk data entry that is used to request the elements for which forces are to be printed Set identification of a GDVLIST bulk data entry that is used to request the global design variable IDs for which global design variables are to be printed Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which grid point forces are to be printed Either ALL or NONE depending on whether the GPWG is to be computed printed If a GPWG entry is in the Bulk Data file it will be used by the algorithm Set identification of an LDVLIST and or a GDVLIST bulk data entry that is used to request the design variables for which stiffness sensitivities are to printed Set identification of an LDVLIST bulk data entry that is used to request the local design variable Ds for which local design variables are to
298. e valueis returned in theoutput coordinate system of the grid points 3 A cid of 0 requests that the coordinate be returned in the basic coordinate system ASTROS THE FUNCTION PACKET 6 29 DV USER S MANUAL Intrinsic Response Function DV Purpose Toretrieve the current value of a design variable Usage ae dvid GDVLIST gdv_sid Function Arguments dvid Identification of a design variable specified in the Bulk Data packet gdv_sid Set identification of a GDVLIST Bulk Data entry used to specify the design vari able 6 30 THE FUNCTION PACKET USER S MANUAL USER S MANUAL FDAMP Intrinsic Function FDAMP Purpose Toretrieve the current value of flutter damping Usage FDAMP l Sai FL machop densop modeop velop caseop where TE mvalue E MACHLIST mach_sid d dvalue STOLE DENSLIST dens_sid modeid mgdeop MODELIST mode_sid i vvalue ae a VELOLIST vel_sid caseop gt caseid CASELIST case_sid Fucntion Arguments mvalue Mach value mach_sid Set identification of a MACHLIST bulk data entry used to specify the mach value dvalue Density ratio value dens_sid Set identification of a DENSLIST bulk data entry used to specify the density ratio value modeid Mode index mode_sid Set identification of a MODELIST bulk data entry used to specify the mode index vvalue Velocity value vel_sid Set identification of a VELOLIST bulk data e
299. each particular case Chapter 4 of this manual described one mechanism provided to select particular itera tions disciplines subcases and response quantities that of the Solution Control output request This Chapter endeavors to present the totality of output options available The system controlled outputs from the engineering modules are described in order to establish a familiarity with an ASTROS output listing This is followed by a more complete description of output from each Solution Control request than is contained in Chapter 4 with different disciplines elements design constraints and node types accounted for in some detail These represent the outputs that are fully supported by the ASTROS software and require little or no user intervention to obtain The presentation of these features assumes that the standard executive sequence is used If the user substantially modifies the standard sequence to the point where certain modules are not called some or all of the presented output features may no longer be available The more advanced forms of user output requests are also presented in this section The most basic of these forms involve changing the engineering module print control levels through the use of the DEBUG packet Then the MAPOL addressable print utilities are presented The use of these utilities in conjunc tion with the general versatility of the MAPOL language provides the user with the capacity both to look at existing d
300. eal or O lt nteger lt 1 000 000 If integer then material x axis lies along the projection onto the plane of the element of the x axis of coordi nate system identified by the integer TMAX Maximum allowable thickness in design Real gt 0 Default 10 Remarks 1 The TMAX value is used only for shape function design variable linking 7 66 THE BULK DATA PACKET ASTROS USER S MANUAL DCONALE Input Data Entry DCONALE Description Defines an aileron effectiveness constraint of the form AE lt AEREO upper bound or AE gt AEREO lower bound where C AES 2 C pb 2v Format and Example T 2 3 4 5 6 7 8 9 10 DCONALE SID LABEL CTYPE AEREQ DCONALE 25 OUTBDAIL LOWER 0 4 Field Contents SID Aerodynamic set identification for the imposed constraint Integer gt 0 LABEL A string of up to eight characters to identify the AESURF or CONLINK control surface LABELS must be unique CTYPE Constraint type either UPPER for upper bound or LOWER for lower bound Character Default LOWER AEREQ Required aileron effectiveness Real 0 0 Remarks 1 This constraint constraint will only be applied if selected by the Solution Control discipline option DCON SID and if an antisymmetric aeroelastic trim analysis is being performed 2 A LOWER bound constraint excludes all values to the left of AEREQ on a real number line
301. ectional characteristics Format and Example 1 2 3 4 5 6 7 8 9 10 PBAR1 PID MID SHAPE D1 D2 D3 D4 D5 cont cont NSM D6 D7 D8 D9 D10 PBAR1 101 56 TUBE 0 0 1 A A 1 20 Field Contents PID Property identification number I nteger gt 0 MID Material identification number Integer gt 0 See Remark 1 SHAPE Cross sectional shape Character I T BOX BAR TUBE ROD HAT or GBOX See Remark 2 Di Cross sectional dimensions Real gt 0 0 See Remark 2 NSM Nonstructural mass per unit length Real Remarks 1 PBAR1 entries may only reference MAT1 material data 2 The cross sectional properties and shear flexibility factors of the BAR are computed using the SHAPE and Di geometric data as defined by the figures on the following page The stress recovery points are also shown Note that the orientation of the element coordinate system is important for the element definition 7 180 THE BULK DATA PACKET ASTROS USER S MANUAL PBAR1 Definition of Cross Sectional Geometry and Stress Recovery Points SHAPE TUBE SHAPE D2 ASTROS THE BULK DATA PACKET 7 181 PCOMP Input Data Entry PCOMP Layered Composite Element Property Description Defines the properties of an n ply composite material laminate Format and Examples USER S MANUAL 1 2 3 4 5 6 7 8 9
302. ectional parameter specified by DVSYM Real Default 0 0001 TMAX Maximum value of the PBAR1 cross sectional parameter specified by DVSYM Real Default 0 0001 ETYPE Character input identifying the element type Must be BAR EIDi Element identification numbers Integer gt 0 or blank Remarks 1 Seethe PBAR1 Bulk Data entry for a description of the cross sectional parameters ASTROS THE BULK DATA PACKET 7 91 DCONSDL USER S MANUAL Input Data Entry DCONSDL BAR element side constraints Description Defines Side constraints on BAR element cross sectional parameters by referencing list of elements Format and Example 1 2 3 4 5 6 7 8 9 10 DCONSDL DVSYM TMIN TMAX ELID1 ELID2 ELID3 ELID4 ELID5 CONT CONT ELID6 ELID7 etc DCONSDL D3 0 001 0 05 99 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONSDL DVSYM TMIN TMAX ELID1 THRU ELID2 Field Contents DVSYM Character symbol specifying the PBAR1 cross sectional parameter Remark 1 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 TMIN Minimum value of the PBAR1 cross sectional parameter specified by DVSYM Real Default 0 0001 TMAX Maximum value of the PBAR1 cross sectional parameter specified by DVSYM Real Default 0 0001 ELIDi Element list identification numbers Integer gt 0 or blank Remark 2 Remarks 1 Seethe PBAR1 Bulk Data entry for a de
303. ects the JSETi bulk data entries identifying inertia relief degrees of freedom for performing dynamic reduction I nteger gt 0 p Set identification of the extra degrees of freedom for the boundary condition Invokes EPOINT bulk data entries I nteger gt 0 q Selects the direct input stiffness matrix in the g set This matrix will be added to KGG for this boundary condition Refers to a DMI or DMIG Bulk Data entry ASTROS THE SOLUTION CONTROL PACKET 5 23 BOUNDARY USER S MANUAL r Selects the direct input mass matrix in the g set This matrix will be added to MGG for this boundary condition Refers to a DMI or DMIG Bulk Data entry s Specifies a set identification number to be used for punching the spc Bulk Data entries generated by the aAuTOSPC option I nteger gt 0 less than 9 digits t Defines a default ErGc set identification to be used by the cere module if it is passed a zero value in ts call sequence x Defines the aurospPc threshhold Singularities with values less than x are auto matically constrained Real Default 10 8 Remarks 1 If any BOUNDARY has a beid then all boundaries must have a bcid All becid values must be unique but they need not be in any particular order Boundaries are implicitly numbered from 1 to n if no beid values are specified The beid is only used as a reference from user defined functions in the Function Packet 2 Notethat the REDUCE and ESET set specifications are innovative relative to
304. ed and if so no error messages are issued 3 Any number of continuations is allowed ASTROS THE BULK DATA PACKET 7 125 Input Data Entry ELIST Description Defines elements associated with a design variable Format and Example 1 2 3 4 5 6 7 8 9 10 ELIST LINKID ETYPE EID1 EID2 EID3 EID4 EID5 EID6 CONT CONT EID7 EID8 EID9 etc CONT ELIST 6 CROD 12 14 22 Alternate form 1 2 3 4 5 6 7 8 9 10 ELIST LINKID ETYPE ETD1 THRU EID2 Field Contents LINKID Element list identifier I nteger gt 0 ETYPE Character input identifying the element type One of the following CELAS1 CELAS2 CMASS1 CMASS2 CONM2 CBAR CROD CONROD CSHEAR CQDMEM1 CTRMEM CQUAD4 CTRIA3 EIDi Element identification numbers Integer gt 0 or blank USER S MANUAL ELISTM ELISTM Defines elements and their local design variables associated with a design variable Input Data Entry Description Format and Example af 2 3 4 5 6 7 8 9 ELISTM LINKID ETYPE EID1 DVSYM1 EID2 DVSYM2 EID3 DVSYM3 CONT CONT EID4 DVSYM4 etc CONT ELISTM 6 BAR 12 A 22 A Field Contents LINKID Element list identifier I nteger gt 0
305. ed and if the FLUTTER discipline is within an ANALYZE boundary condition 3 Applied LOAD print requests 4 The displacement nodal response quantities DISPLACEMENTS VELOCITYS and ACCEL ERATIONS 5 Element response quantities in the order STRESS STRAIN FORCE and STRAIN ENERGY for each subcase elements are processed alphabetically within each quantity type In the OPTIMIZE subpacket these data are followed by the selected design and resizing prints in the following order 7 Active constraint summary either the default abbreviated print or the full print if the DCONSTRAINT print option is selected 8 The print of the global and then local design variables representing the current design de peding on the GDESIGN and LDESIGN PRINT requests On the final design iteration the iteration history precedes the design variable output by default Within each response quantity s print module the disciplines are not treated in the order given in the solution control packet instead they are treated where applicable in the following order A STATICS B MODES C SAERO D TRANSIENT E FREQUENCY The subcases within each discipline are treated in the order given in the solution control packet In the case of MODES the eigenvectors are ordered in increasing eigenvalue order TRANSIENT and FREQUENCY subcases are ordered in increasing time or frequency step 8 2 1 Element Response Quantities ASTROS has two basic form
306. ed in place of the formal parameters in the procedure definition Note that procedures may call other procedures if the called procedure has already been defined 9 6 5 FUNCTION PROCEDURES A special kind of procedure that can have only one output value is called a FUNCTION Because it is a value the type of the function must be dedared Valid types are integer real complex or logical Therefore the function head differs slightly from that of the procedure lt type gt FUNC lt funcname gt lt params gt Again lt t ype gt must be included and all other rules are the same as those for a regular procedure 9 26 MAPOL PROGRAMMING ASTROS USER S MANUAL Unlike procedures functions are invoked with their name and arguments as in Fortran and they can therefore be used directly in assignment statements and expressions e g A SIN X B X Y SORT Z 9 6 5 1 Examples of Variable Scope To dlarify the concept of variable scope consider the following example MAPOL INTEGER A PROC MYPROG B C INTEGER B C B A Aisavailable E and F are not ENDP PROC YOURPG H I REAL H 1 ENDP REAL E F RELATION FOO BAR In this example the variable A is global to all procedures because its declaration precedes the proc declarations B and c are local to MYPROG because their declarations appear in the body of that proce dure Finally E F FOO and BAR
307. ees of freedom are defined in the element s coordinate system The bar must have stiffness associated with the pin flag For example if PA 4 is specified the PBAR entry must havea value for J the torsional stiffness Components of offset vectors wa and wb respectively in displacement coordinate systems at points GA and GB respectively Real or blank THE BULK DATA PACKET 7 33 CBAR USER S MANUAL Remarks 1 The element coordinate system is shown in the following figure GID2 Xe 2 If there are no pin flags or offsets the continuation entry may be omitted 3 The TMAX value is used only for shape function design variable linking 4 Seethe BAROR entry for default options for Fields 3 and 6 through 8 7 34 THE BULK DATA PACKET ASTROS USER S MANUAL CELAS1 Input Data Entry CELAS1 Scalar Spring Connection Description Defines a scalar spring element of the structural model Format and Example I 2 3 4 5 6 7 8 9 10 CELAS1 EID PID G1 C1 G2 C2 TMAX CELAS1 2 6 8 il Field Contents EID Element identification number Integer gt 0 PID Identification number of a PELAS property entry Default is EID Integer gt 0 Gi Geometric grid point identification number Integer gt 0 Ci Component number 6 gt Integer gt 0 TMAX Maximum value for design Real Default 1 0 E 4 Remarks 1 Scalar points may be used for G1 and or G2 in which case th
308. efault 0 0001 K1 K2 Area factor for shear Real Stress recovery coefficients Real Ci Di Ei Fi R12 R22 ALPHA Inertia linking terms for design see Remark 6 Remarks 1 TheBAR element geometry and coordinate system is shown in the Figure on the following page 2 PBAR entries may only reference MAT1 material entries 3 The transverse shear stiffnesses in planes 1 and 2 are K1 AG and K2 AG respectivelyntsg 002 Tc1 PBAR Tj1 USER S MANUAL PBAR 6 For design the following applies to the R12 and R22 values The moments of inertia are linked to the Ze Plane 2 GID2 Xe cross sectional area by the following expressions Il R12 A ALPHA I2 R22 A ALPHA A If R12 0 0 then the missing value is computed from R12 11 A ALPHA The same is true for R22 and 12 B The ALPHA value defaults to 1 0 and must be gt 1 0 C If both 11 and R12 or 12 and R22 are given the linking expression will override the input values 7 Ifthe CBAR is to be designed the following restrictions apply A J NSM K1 K2 112 0 0 If any of these values are not zero a warning message will be issued and the value set to zero ASTROS THE BULK DATA PACKET 7 179 PBAR1 Input Data Entry USER S MANUAL PBAR1 Geometric BAR element property Description Defines the properties of a BAR element by specifying its cross s
309. efined on a single entry 2 Average element temperatures are obtained as a simple average of the connecting grid point tempera tures when no element temperature data are defined 3 For each thermal load temperatures must be specified for all grid points using either TEMP or TEMPD entries ASTROS THE BULK DATA PACKET 7 229 TF USER S MANUAL Input Data Entry TF Dynamic Transfer F unction Description 1 Used to define a transfer function of the form BO Bl p B2 p ud Y AQ A1 i p a2 i p uj 0 i 2 May also be used as a means of direct matrix input See Remark 3 Format and Examples T 2 3 4 5 6 7 8 9 10 TF SID GD CD BO B1 B2 CONT CONT G 1 C 1 AO 1 Al 1 A2 1 TF 1 2 3 4 0 540 6 0 ABC ABC 13 4 5 0 6 0 7 0 Field Contents SID Set identification Integer gt 0 GD G i Grid scalar or extra point identification numbers Integer gt 0 CD C i Component numbers null or zero for scalar or extra points any one of the digits 1 through 6 for a grid point BO Bl B2 Transfer function coefficients Real AQ i Al i A2 i Remarks 1 The matrix elements defined by this entry are added to the dynamic matrices for the problem 2 Transfer function sets must be selected in Solution Control TFL SID to be used 3 The constraint relation given in Equation 1 will hold only if no structural elements or other matrix elements are connected
310. eger gt 0 or blank DVSYMi Symbol defining the local design variable Remarks 2 and 3 PREFi Linking factor for the associated local design variable Real Remarks 1 The shape function identification number is referenced by the DESVARS entry to connect the global variable to the shape 2 The following symbols may be used for the different types of properties ELEMENTS ALLOWABLE DvsYm VALUES PELAS PMASS PBAR PROD A PBAR1 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 SHEAR QDMEM1 TRMEM PSHELL T PCOMP PCOMP1 PCOMP2 3 Ifall elements to be linked have only one possible pvsym e g K then the SHAPE Bulk Data entry may be used ASTROS THE BULK DATA PACKET 7 217 SHPGEN USER S MANUAL Input Data Entry SHPGEN Description Defines a design variable which performs shape linking using the automatic shape generation capability Format and Examples 1 2 3 4 5 6 7 8 9 10 SHPGEN SHAPEID ESETID SHAPE X0 CID YO ZO DVSYMBL SHPGEN 10 11 1 2 120 22 0 Hea Field Contents SHAPEID Shape function identification Integer gt 0 ESETID Identification number of an ELEMLIST Bulk Data entry Integer gt 0 SHAPE Desired shape function Character Remark 1 CID The identification number of a user defined coordinate system in which the origin is the new origin for shape generation and the shape
311. eger Modelling Parameters o 4 8 Integer Design Parameters o 4 9 Integer Aerodynamic Parameters a 4 9 Integer Discipline Parameters o 4 10 Logical Discipline Parameters 00522 eee 4 11 Summary of ASTROS Modules o e 4 13 Levels of Solution Control 2 ada E rd 5 2 Summary of ASTROS Disciplines a aoa a a 5 8 xi USER S MANUAL Table 5 3 Summary of Discipline Options o o 5 11 Table 5 4 Response Quantity Output Options o 5 18 Table 5 5 Response Quantities by Discipline 0 5 19 Table 6 1 Mathematical Intrinsics a o e 6 6 Table 6 2 Selection Functions 2 rd a a e 6 7 Table 6 3 Element Response Components o e e o 6 10 Table 8 1 DEBUG and ASSIGN DATABASE Output 8 3 Table 8 2 Boundary Condition Summary o e 0005044 8 3 Table 8 3 Active Boundary and Constraint Summary 8 4 Table 8 4 Resequencing Summary 2 200002 ee eee 8 4 Table 8 5 Active Constraint Summary o e 8 5 Table 8 6 Approximate Optimization Summary o 8 5 Table 8 7 Design Iteration History o eee 8 6 Table 8 8 ASTROS Execution Summary
312. eight generation List of GRID point identification numbers List of iteration step identification numbers List of local design variable identification numbers List of Mach number values List of normal mode identification numbers List of GRID point identification numbers List of time step values List of velocity values 7 5 11 Steady Aerodynamics AEROS AEFACT AESURF AIRFOIL AXSTA BODY CAERO6 CONEFE S CONLINK PAERO6 Reference parameters List of real parameters Aerodynamic control surface definition Airfoil property definition Body axial station parameter definition Body configuration definition Macroelement pane definition Definition of static aerodnamic control effectiveness Definition of linked control surfaces Body parameter definition 7 5 12 Structural Element Connection BAROR CBAR CELAS1 CELAS2 ASTROS Definition of default parameters for the CBAR bar element Prismatic beam element Scalar elastic spring element Scalar elastic spring element THE BULK DATA PACKET 7 9 CIH CIH CIH CMA CMA CON CON CON CQD CQU CRO CSH CIR EX1 EX2 EX3 ssi 8s2 M1 M2 ROD MEM1 AD4 D EAR IA3 RMEM GENEL USER S MANUAL Linear isoparametric hexahedral element Quadratic isoparametric hexahedral element Cubic isoparametric hexahedral element Scalar mass element Scalar mass element
313. el to define the design variable Character DVSYMBL Design variable symbol associated with this local design variable Remark 3 Remarks 1 The initial element thickness or area used in the structural analysis is derived from the VINIT value and the property value on the associated property entry tinit VINIT property_value Similarly the minimum and maximum values are the VMIN and vMAX values of the element property are derived from tmin VMIN property_value tmax VMAX property_value 2 DVID must be unique among all DESELM DESVARP and DESVARS entries ASTROS THE BULK DATA PACKET 7 105 DESELM USER S MANUAL 3 If the designed element has only one designable property the continuation containing DVSYMBL may be omitted Otherwise a selection must be made from the following table ELEMENTS ALLOWABLE DvsYMBL VALUES ELASi K MASSi CONM2 M BAR PBAR ROD CONROD A BAR PBAR1 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 SHEAR QDMEM1 TRMEM QUAD4 TRIA3 T 7 106 THE BULK DATA PACKET ASTROS USER S MANUAL DESVARP Input Data Entry DESVARP Description Designates physically linked global design variable properties Format and Example I 2 3 4 5 6 zi 8 9 10 DESVARP DVID LINKID VMIN VMAX VINIT LAYERNUM LAYRLST LABEL DESVARP 1 0 01 2 0 1 0 13 NBDTOP Field Contents DVID Design variable identif
314. element is used to compute tlam including undesigned layers see Remark 3 otherwise the summed thicknesses of the layers specified by the PLYLIST set will be used 3 If this constraint is applied to a composite element with undesigned layers these layers may be freely included in the layer s composing the ply and or the layer s composing the laminate The only restriction is that at least one layer in the laminate must be a local design variable 4 If the laminate is composed of a single layer this constraint becomes redundant with the TMIN entered on the PcompPi field for shape function linking or the vMIN entered on the DESELM or DESVARP entry for physical linking In this case the most critical limit will be determined from among all sources DCONPMN DCONLMN TMIN VMIN and will be used to update the local variable side constraint The DCONxxx entry will then be automatically removed since it will no longer be necessary A summary of this action will be echoed to the print file ASTROS THE BULK DATA PACKET 7 87 DCONPMN Input Data Entry Description USER S MANUAL DCONPMN Composite element ply minimum gauge constraint Defines a lower bound constraint on the total thickness of all or part of the layers of a composite element The constraint is of the form Lo PY lt 9 tmin Format and Example 1 2 3 10 DCONPMN MINTHK PLYNUM PLYSET SID SID SID SID SID CONT
315. elements at which strains are to be printed ad Set identification of an ELEMLIST bulk data entry that is used to request the elements for which stresses are be printed ae Set identification of an ELEMLIST bulk data entry that is used to request the aerody namic elements for which the pressure coefficients at aeroelastic trim are to be printed af Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which velocities are to be printed ag Specifies the elements for which local buckling results are to be printed may be ALL Or NONE ah Selects the type of stresses or strains to be output for composite elements The options are LAYER LAMINATE or BOTH The default is LAYER Remarks 1 Form is an optional parameter for printing complex data REcTangular data outputs complex data with real and imaginary components while POLAr outputs complex data using magni tude and phase If used with the PRINT command all data that are not otherwise specified use the requested Form FREQ ITER MODE and TIME if applicable for that type of data If used with an option Form FREQ ITER MODE and TIME override the global request Options a through af can be either ALL NONE or a positive integer and additionally option b ITER can be LAST and options h CGRA and i DCON can be ACTIVE ALL requests all values NONE turns off a request from a previous hierarchy while an integer value refers to a bulk data entry L
316. ement plyid Identification of a layer number for a composite element ply_sid Set identification of a PLYLIST bulk data entry used to specify the layer number for a composite element Notes 1 When an element identification is used then the eid must be unique and if the eidis not unique then an element list must be used 2 Composite elements must have their layer number specified 6 40 THE FUNCTION PACKET USER S MANUAL USER S MANUAL RIGIDCF Intrinsic Function RIGIDCF Purpose To retrieve rigid stability coefficients for a specific trim parameter from a Static Aerodynam ics analysis Usage l caseid RIGIDCF axis trim_param CASELIST case_sid l Function Arguments axis Input axis trim param Trim parameters caseid Subcase identification sid Set identification of a CASELIST bulk data entry used to specify the subcase number Notes 1 This function returns its results in radians If degrees are required the results may be converted using the DEGS intrinisic function 2 The allowable values for axis are ASTROS THE FUNCTION PACKET 6 41 RIGIDCF USER S MANUAL 3 The allowable control surfaces trim_param are ALPHA BETA PRATE ORATE RRATE PACCEL QACCEL RACCEL trim_param User Surfaces The User Surfaces are defined using AESURF Bulk Data entries 4 If the subcase reference is omitted then the specific discipline request defines the requested sub
317. en defined to the ASTROS system because they are not supported by any ASTROS code Thus there will be instances where a NASTRAN input deck will have to be modified to remove these entries which serve no purpose in ASTROS The majority of these bulk data entries deal with unsupported elements plotting options output options etc which are not felt to present a major problem More important is the support for NASTRAN s model definitions most of which have already been adopted by ASTROS 7 12 THE BULK DATA PACKET ASTROS USER S MANUAL 7 7 BULK DATA DESCRIPTIONS This Section contains a complete description of each of the ASTROS Bulk Data entries ASTROS THE BULK DATA PACKET 7 13 USER S MANUAL This pageis intentionally blank 7 14 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Comment Description Allows commentary text to be inserted into the unsorted echo of the input Bulk Data Deck The entry is otherwise ignored by the program These entries do not appear in a sorted echo Format and Example 1 2 3 4 5 6 7 8 9 10 Followed by any legitimate characters in columns 2 80 THIS Remarks 1 The comment entry may also be used in the Solution Control packet ASTROS THE BULK DATA PACKET 7 15 Input Data Entry AEFACT Aerodynamic Lists Description Used to specify lists of real numbers for aeroelastic analysis Format and Example 1 2 3 4 5 6
318. ency response analysis discipline Hierarchy Level Discipline Format and Examples FREQUENCY type caseid DLOAD i FSTEP j GUST k K2PP 1 M2PP m B2PP n TFL o DAMPING p FREQUENCY DIRECT DLOAD 10 FSTEP 20 FREQUENCY MODAL DLOAD 100 FSTEP 30 M2PP MFREQ TFL 5 FREQUENCY DIRECT DLOAD 100 FSTEP 20 GUST 55 Option Meaning type Selects the solution approach from DIRECT or MODAL caseid Case identification number I nteger gt 0 i Set identification of a DLOAD bulk data entry j Set identification of frequency bulk data entries FREQ FREQ1 Or FREQ2 that define the frequency steps for the analysis k Set identification of a Gust bulk data entry which defines the gust parameters Selects the direct input stiffness matrix Refers to a DMI or DMIG bulk data entry m Selects the direct input mass matrix Refers to a DMI or DMIG bulk data entry n Selects the direct input damping matrix Refers to a DMI or DMIG bulk data entry o Selects the transfer function set to be added to the input matrices Refers to TF bulk data entries p Set identification of VSDAMP and or TABDMP bulk data entries that define damping data Remarks 1 If any discipline has a caseid then all disciplines must have a caseid All caseid values must be unique but they need not be in any particular order Disciplines are implicitly numbered from 1 to n if no caseid values are specified The caseid is only used as
319. entification number Integer gt 0 T Thickness of shear panel Real gt 0 0 NSM Nonstructural mass per unit area Real gt 0 0 or blank TMIN Minimum panel thickness for design Real gt 0 0 or blank Default 0 0001 Remarks 1 All PSHEAR entries must have unique identification numbers 2 PSHEAR entries may reference only MAT1 material entries 3 TMIN is ignored unless the element is linked to global design variables by SHAPE entries 7 200 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description PSHELL PSHELL Shell Element Property Defines the membrane bending transverse shear and coupling properties of the shell elements QUAD4 and TRIA3 Format and Examples 1 2 3 4 5 6 7 8 9 10 PSHELL PID MID1 T MID2 121 T3 MID3 TS T NSM CONT CONT z1 Z2 MID4 MCSID SCSID ZOFF TMIN PSHELL 203 204 L290 205 MZ 206 0 8 6 32 ABC BC 95 95 0 0 0 01 Field Contents PID Property identification number Integer gt 0 ID1 Material identification number for membrane Integer gt 0 or blank T Default value for membrane thickness Real gt 0 0 or blank ID2 Material identification number for bending Integer gt 0 or blank 121 T3 Bending stiffness parameter Real gt 0 0 or blank Default 1 0 ID3 Material identification number for transverse shear Integer gt 0 or blank must be blank unless MID2 gt 0 TS T Transve
320. ents The user can select that these results be written to the print output file through the PRINT command and its associated options or written to a punch file through the PUNCH command In addition there are a number of solution control commands that can be used to label the output This subsection documents the PRINT and PUNCH commands and the labeling commands and discusses their use The PRINT and PUNCH commands are identical in form and interpretation so the PRINT command will be used to represent both commands in the following discussion There are also many features and utilities available to the user to obtain output through modifications to the executive MAPOL sequence These include direct use of MAPOL utilities modification of print parameters in functional module calling sequences and user written procedures or modules These output capabilities and a more complete discussion of the output processing PRINT and PUNCH capabilities of the ASTROS system is presented in Chapter 6 of this manual The PRINT and PUNCH commands have a number of options which can be separated into three groups subset options response quantity options and form options The subset options select a set of subcases and or design iterations to which the PRINT command applies while the remaining options select the actual data quantities that are desired e g stresses strains and displacements and the form in which complex quantities are to be printed The output
321. equest applies F or example ANALYZE BOUNDARY SPC 10 METHOD 1000 ODES PRINT MODES ALL DISP 100 selects the displacements eigenvectors for all the computed mode shapes be printed If the MODES ALL selection were not included in the PRINT statement the user would get no output at all The user is cautioned that the output processing in ASTROS is designed to limit output to those quantities that are explicitly selected and therefore the default for subcase option MODES is that no modes are selected Whenever multiple subcases are generated by a discipline as in the case of MODES TRANSIENT and FREQUENCY a subcase selection option is required on the PRINT command in order to get any output If the discipline appears in the OPTIMIZE subpacket the user may request that the output appear only at certain iterations For example OPTIMIZE BOUNDARY SPC 10 METHOD 1000 MODES DCON 1000 PRINT ITER 10 MODES ALL DISP 100 selects the displacements eigenvectors for all the computed mode shapes be printed at the iterations given in ITERLIST 10 Unlike the other subset selectors the default for ITER is ALL Omission of the ITER selector therefore implies that the quantity will be printed at every iteration This default is a consequence of compatibility with early versions of ASTROS in which there was no ITERATION Selection at all The subset selections can be specified at two levels as parenthetical p
322. er gt 0 Default ALL SID Set identification of one or more ELEMLIST entries that define the set of composite elements to which this composition constraint will be applied Integer gt 0 or blank Remarks 1 One and only one of either PLYNUM or PLYSET must be given 2 The definition of ply and laminate thickness can vary from entry to entry If PLYNUM is Used to define toly that one layer constitutes a ply otherwise toy is the sum of the layer thicknesses of all the layers listed in PLYSET 7 84 THE BULK DATA PACKET ASTROS USER S MANUAL DCONLAM Similar rules are applied for tlam If ALL is used every layer of the element is used to compute tlam including undesigned layers see Remark 3 otherwise the summed thicknesses of the layers speci fied by the PLYLIST set will be used As a result there is no real distinction between a ply thickness and a laminate thickness Typically the ply will be a subset of the layers that define the laminate but that is not a requirement 3 If this constraint is applied to a composite element with undesigned layers these layers may be freely included in the layer s composing the ply and or the layer s composing the laminate The only restriction is that at least one layer in the ply must be a local design variable and at least one layer in the laminate must be a local design variable ASTROS THE BULK DATA PACKET 7 85 DCONLIST USER S MANUAL Input Data Entry DCONLIST Design Constraint Lis
323. er desires to use in the computation of inertia relief mode shape in Dynamic Reduction Format and Example 1 2 3 4 5 6 7 10 JSE SETID ID C ID C ID CONT CONT ID ID Cc etc JSET 16 2 23 35 16 Field Contents SETID The set identification number of the INERTIA set Integer gt 0 ID Grid or scalar point identification number Integer gt 0 C Component number zero or blank for scalar points any unique combination of the digits 1 through 6 for grid points Integer Remarks 1 Coordinates specified on this entry form members of a mutually exdusive set They may not be specified on other entries that define mutually exclusive sets 2 When JSET and or JSET1 entries are present all degrees of freedom not otherwise constrained will be placed on the o set 3 Useof JSET in dynamic reduction a JSET defines the structural nonstructural j set degrees of freedom inertia relief shapes An alternate input format is provided by the JSET1 entry b The SID is selected by the Solution Control Command BOUNDARY INERTIA n c Use 0 as the grid point identification number to select the origin of the basic coordinate system as one of the j set degrees of freedom 4 Any number of continuations are allowed ASTROS THE BULK DATA PACKET 7 151 JSET1 Input Data Entry Description USER S MANUAL JSET1 Select Coordinates for the j set Alternate F
324. er represents the radial distance from the origin the magnitude and the second represents the angular displacement from the real coordinate axis the phase angle The phase angle is computed in degrees The form can be specified at two levels as parenthetical phrases attached to the print or punch statement At the higher level the form option generates a default for the entire print or punch statement For example PRINT POLAR STRESS ALL STRAIN ALL requests that polar form be used for both stress and strain response quantities In addition the form option can be attached to the individual quantity options to override the print default For example PRINT POLAR STRESS ALL STRAIN RECT ALL overrides the polar default for the strain output At both levels the default form is rectangular and any polar requests for real output quantities are ignored 5 4 4 Labeling Options Labeling of printed output is performed through the use of three optional commands identical in form to their NASTRAN counterparts OPTION DESCRIPTION TITLE A title header that will appear as the first line on each page of output Rai A secondary header that will appear on the second line of each page of output LABEL A tertiary header that is typically used to identify subcase discipline level output Each of these commands can appear at any level in the solution control hierarchy and will be applied until
325. es If the element is composite the individual layers are treated as independent stacked elements in which each layer as defined on the pcomp bulk data entry represents an element In the case of composite elements the layers are numbered sequentially starting with the first layer appearing on the Pcomp entry Non com posite elements will show a layer number of zero ASTROS OUTPUT FEATURES 8 17 USER S MANUAL Table 8 12 ROD Element Solution Quantities STRESSES IN ROD ELEMENTS ROD ELEMENT AXIAL SAFETY TORSIONAL SAFETY ELEMENT AXIAL SAFETY TORSIONAL SAFETY ID STRESS MARGIN STRESS MARGIN ID STRESS MARGIN STRESS MARGIN 1 6 512166E 03 2 8E 00 0 000000E 00 1 7E 38 2 1 337487E 03 1 8E 01 0 000000E 00 1 7E 38 3 6 821167E 03 2 7E 00 0 000000E 00 1 7E 38 4 1 995846E 03 1 2E 01 0 000000E 00 1 7E 38 1TEN BAR TRUSS ASTROS VERSION 9 0 03 03 93 P 11 FINAL ANALYSIS SEGMENT FINAL STATIC ANALYSIS STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 STRAINS IN ROD ELEMENTS ROD ELEMENT AXIAL TORSIONAL ELEMENT AXIAL TORSIONAL ID STRAIN STRAIN ID STRAIN STRAIN 1 6 512166E 04 0 000000E 00 2 1 337487E 04 0 000000E 00 3 6 821167E 04 0 000000E 00 4 1TEN BAR TRUSS ASTROS VERSION 9 0 03 03 93 P 12 FINAL ANALYSIS SEGMENT FINAL STATIC ANALYSIS STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 FORCES IN ROD ELEMENTS ROD ELEMENT AXIAL ELEMENT AXIAL ID FORCE TORQUE ID FORCE TORQUE 1 1 953650E 05 0 000000E 00 2 4 012462E 04 0 000000E 00 3 2 046350E 05 0 000000E 00 4 St
326. es strains forces and strain energies are available as output for the QUAD4 TRIA3 elements through the STRESS STRAIN FORCE and ENERGY solution control print command options The following element stresses and strains are output on request G2 G1 Figure 8 9 QUAD4 Element Coordinate System USER S MANUAL 1 Combined extensional and bending stresses and strains computed at the element center in the element coordinate system 2 Principal stresses and strains computed at the element center including the angle be tween the element x axis and the principal axis The following forces are output on request 1 Element forces computed at the center of the element in the mean planein the element coordinate system For composite materials all output quantities are computed using the aggregate laminate properties Hence output of stresses or strains at the ply or laminae level is currently not an available print option for the QUAD4 TRIA3 elements in ASTROS An example of the printed output is shown in Table 8 14 Table 8 14 QUAD4 and TRIA3 Solution Quantities 1SIMPLIFIED FIGHTER WING ASTROS VERSION 9 0 03 03 93 P 13 FINAL ANALYSIS SEGMENT STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 STRESSES IN QUADRILATERAL PLATES QUAD 4 ELEMENT LAYER FIBER STRESSES IN STRESS COORD SYSTEM PRINCIPAL STRESSES ZERO SHEAR ID NO DISTANCE NORMAL X NORMAL Y SHEAR XY ANGLE MAJOR MINOR 3 0 1 00000E 01 6 91372E 02 8 33210E 03 2 21727E 03 13
327. escription Defines a static moment at a grid point by specifying a vector Format and Example I 2 3 4 la 6 7 8 9 10 MOMENT SID G CID M N1 N2 N3 MOMENT 2 5 6 2 9 0 0 1 0 0 0 Field Contents SID Load set identification number Integer gt 0 G Grid point identification number Integer gt 0 CID Coordinate system identification number Integer gt 0 M Scale factor Real Ni Components of vector measured in coordinate system defined by CID Real at least one nonzero component Remarks 1 Thestatic moment applied to grid point G is given by m M N 2 ACID of zero references the basic coordinate system ASTROS THE BULK DATA PACKET 7 165 MOMENT1 USER S MANUAL Input Data Entry MOMENT1 Static Moment Alternate Form 1 Description Defines a static moment by specification of a value and two grid points which determine the direction Format and Example 1 2 3 4 5 6 7 8 9 10 MOMENT SID G M G1 G2 MOMENT 6 13 2 93 16 13 Field Contents SID Load set identification number Integer gt 0 G Grid point identification number Integer gt 0 M Value of moment Real Gi Grid point identification numbers Integer gt 0 G1 G2 Remarks 1 The direction of the moment vector is determined by the vector from G1 and G2 7 166 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry MPC MPC Multipoint Constraint
328. ese alternative functions The mechanisms by which these more advanced features are invoked are included in this manual but no attempt is made to provide sufficient information to the user to generate new analysis features or to grossly modify the existing capabilities of the system These more advanced topics are treated in the Programmer s Manual which documents the individual modules in the system and their interactions Rudimentary modifications to the execution sequence and changes to execution parameters are discussed in detail in this manual Machine and installation dependent aspects of ASTROS are also contained in the Programmer s Manuals rather than in the User s Manual Only those machine dependent issues that are logically related to the preparation of the input are discussed in this manual Machine dependencies in the input are limited to the naming conventions for the run time database files and the parameters that can be used on the ASSIGN DATABASE entry Other machine dependencies are handled as part of the installation of the system on each particular host machine These issues are documented in the Programmer s Manual since they are relevant only to the system manager not to the user It will be apparent to many readers that the NASTRAN structural analysis system was used as a guide in the design of the ASTROS program Both NASTRAN and ASTROS comprise large scale finite element structural analysis in executive driven software syste
329. esign On termination or print request this routine computes the values of the local design variables AEROEFFS ENG Evaluates aeroelastic effectiveness sensitivities ENG Computes the sensitivities to active strength constraints and or aeroelastic effectiveness AEROSENS constraints for active steady aeroelastic optimization boundary conditions Computes the discipline dependent unsteady aerodynamic matrices for FLUTTER and GUST AMP ENG analyses ANALINIT ENG Initializes the final analysis pass ENG Flushes the current values of user function responses and gradients at the beginning of each APFLUSH design iteration APPEND MAT Appends one matrix to another AROSNSDR ENG Driver for SAERO sensitivity analysis AROSNSMR ENG Merges SAERO sensitivities for each subscript into MATOUT in case order for active subcases ENG Builds the boundary condition dependent grid point coordinate relation BGPDT for the specified BCBGPDT boundary condition BCBULK ENG Builds boundary condition dependent matrices transfer functions and initial conditions BCEVAL ENG Evaluates the constraints of PBAR1 cross sectional parameters BCIDVAL ENG Converts the boundary condition index value Bc into the user assigned value ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 13 USER S MANUAL Table 3 8 Summary of ASTROS Modules Continued MODULE TYPE DESCRIPTION NAME ENG Returns flags to the MAPO
330. et contains the engineering data describ ing the finite element structural model the aerodynamic model s and the design model as well as all the data needed to perform the specific analysis and or optimization tasks The MAPOL SOLUTION and BULK DATA packets are analogous to the NASTRAN executive control case control and bulk data decks respectivel y In interpreting the input data stream ASTROS recognizes the keywords shown in Figure 3 1 These keywords must be the first nonblank characters on the line leading blanks are allowed and have the structure shown In some cases the keyword is also a command line that makes up part of the data packet which it initiates In these cases the command parameters are documented in the User s Manual chapter discussing the details of the associated data packet For example the MAPOL keyword is part of a command that directs the MAPOL compiler to take certain actions The detailed discussion of the MAPOL command is therefore contained in Chapters 2 and 7 of this manual ASTROS automatically converts the case of the input data stream when necessary The only portions of the data which are not converted are file names which are used in the INCLUDE command the Resource Section and the Solution Control commands TITLE SUBTITLE and LABEL This allows the user to freely enter data in any case Be aware however that file names are never converted and that when using an ASTROS host computer in which case is importa
331. expansion coefficient in the 1 direction Real A2 Thermal expansion coefficient in the 2 direction Real TREF Thermal expansion reference temperature Real Xt Xe Allowable stresses in tension and compression respectively in the longitudinal direc tion Required if failure index is desired Real gt 0 0 Default value for Xe is Xt Yen Ye Allowable stresses in tension and compression respectively in the transverse direc tion Required if failure index is desired Real gt 0 0 Default value for ye is yt S Allowable stress for in plane shear Real gt 0 0 GE Structural damping coefficient Real 7 158 THE BULK DATA PACKET ASTROS USER S MANUAL MAT8 F12 Interaction term in the tensor polynomial theory of Tsai Wu Real Required if failure index or stress constraint by Tsai Wu theory is desired and if value of F 12 is different from 0 0 Remarks 1 IfG zandG Zz values specified as zero or are not supplied transverse shear flexibility calculations will not be performed 2 An approximate value for G Z and G Z is the in plane shear modulus G If test data are not available to accurately determine G Z and G Z for the material and transverse shear calculations are deemed essential the value of G may be supplied for G Z and G Z 3 X X Y and ss are used for composite element failure calculations when requested in the FT field of the PCoMPi entry 4 The mass density RHO is used to automati
332. ey are intended only to be used as guidelines a specific job may take significantly more or less memory than indicated For example to execute ASTROS using 12 million words of working memory any of the following commands may be used 12000000 or 12000KW or 12MW 3 3 THE INCLUDE DIRECTIVE The input data stream typically resides in a single file but the user can direct the input stream interpreter to include other files through the use of the INCLUDE directive in the primary input stream The format of the INCLUDE command is INCLUDE lt filename gt filename is aname identifying the file to be included maximum of 72 characters where The filename which is used in a FORTRAN OPEN statement must satisfy the requirements of the particular host system for file names Beyond this restriction the user is free to have any set of contigu 3 10 THE INPUT DATA STREAM ASTROS USER S MANUAL ous non blank characters in the filename In order to avoid the possibility of an infinite recursion there is a restriction on the include feature that no INCLUDE statement can appear in a file that is being included For example if the file TENBAR is being included it may not itself contain an INCLUDE directive The input stream interpreter will terminate with an appropriate error message should this occur The INCLUDE directive can appear anywhere in the input stream after the ASSIGN command The ASSIGN must always appear as
333. f modules where applicable that use the parame ter For a description of all the variables used as arguments of the engineering modules refer to the ASTROS Programmer s Manual It should be noted that all of these variables can be directly modified within the MAPOL algorithm at your discretion A discussion of those parameters that you are most likely to want to modify is given in Section 4 4 3 but the experienced user is free to change any variable in the MAPOL sequence Higher order variables fall into two categories MAPOL entities and hidden entities MAPOL entities are those that actually appear in the MAPOL sequence while hidden entities are those that are declared but do not subsequently appear in the sequence Their declaration ensures that the corresponding database entity is created and can be used by a number of engineering modules without requiring the entity name to appear in the argument list Hidden entities are typically those that contain the raw data needed by many modules e g bulk data geometry data and connectivity data The declarations of the higher order variables are arranged to place logically related entities together Several of the matrix entities it should be noted are subscripted for example KLLINV 1000 The subscripted matrix entity allows the ASTROS software to perform multiple analyses in several boundary conditions and retain the information needed to compute the sensitivities of the active constraints retained
334. ferenced by MID is defined Integer gt or blank NIP Number of integration points along each edge of the element Integer 2 3 4 or blank AR Maximum aspect ratio ratio of longest to shortest edge of the element Real gt 1 0 or blank ALPHA Maximum angle in degrees between the normals of two subtriangles comprising a quadrilateral face Real 0 0 lt ALPHA lt 180 0 or blank Default 45 0 BETA Maximum angle in degrees between the vector connecting a corner point to an adja cent midside point and the vector connecting that midside point and the other mid side or corner point Real 0 0 lt BETA lt 180 0 or blank Default 45 0 ASTROS THE BULK DATA PACKET 7 189 Examples of Field Definitions Remarks 1 All PIHEX entries must have unique identification numbers 2 CID is not used for isotropic materials 3 Thedefault for crp is the basic coordinate system 4 Thedefault for NIP is 2 for IHEX and 3 for IHEX2 and IHEX3 5 AR ALPHA and BETA are used for checking the geometry of the element The defaults are ALPHA BETA sd degrees degrees CIHEX1 5 0 45 0 CIHEX2 10 0 45 0 45 0 CIHEX3 15 0 45 0 45 0 USER S MANUAL PLIST Input Data Entry PLIST Description Defines property entries associated with a design variable Format and Examples I 2 3
335. fication of rc bulk data entries which define the initial conditions m Set identification of a Gust bulk data entry which defines the gust parameters n Selects the direct input stiffness matrix Refers to a DMI Or DMIG bulk data entry o Selects the direct input mass matrix Refers to a DMI Or DMIG bulk data entry p Selects the direct input damping matrix Refers to a DMI or DMIG bulk data entry q Selects the transfer function set to be added to the input matrices Refers to TF bulk data entries r Set identification of VSDAMP and or TABDMP bulk data entries that define damping data Remarks 1 If any discipline has a caseid then all disciplines must have a caseid All caseid values must be unique but they need not be in any particular order Disciplines are implicitly numbered from 1 to n if no caseid values are specified The caseid is only used as a reference from user defined functions in the F unction Packet 5 44 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL The TRANSIENT discipline does not generate design constraints for optimization type DLOAD and TSTEP are required If Gust is present FFT must also be used uF WN Initial conditions Ic are only valid for DIRECT analyses Ic cannot be used with GUST or FFT No more than one TRANSIENT analysis can be done in a single boundary condition M2PP B2PP and K2PP names will typically refer to DMI and DMIG entries but may refer to any existing database entity
336. fines a vector which with the z axis defines the x z plane The reference coordi nate system must be independently defined Format and Example 1 2 3 4 5 6 7 8 9 10 CORD2R CID RID Al A2 A3 B1 B2 B3 CONT CONT c1 C2 C3 CORD2R 3 17 S29 1 0 0 0 3 6 0 0 1 0 123 23 are 1 0 2 9 Field Contents CID Coordinate system identification number Integer gt 0 RID Reference to a coordinate system which is defined independently of new coordinate system Integer gt 0 or blank Ai Bi Ci Coordinates of three points in coordinate system defined by RID Real Remarks 1 The continuation entry must be present 2 The three points Al A2 A3 B1 B2 B3 C1 C2 C3 must be unique and noncollinear Noncol linearity is checked by the geometry processor 3 Coordinate system identification numbers on all CORD1R CORDIC CORD1S CORD2R CORD2C and CORD2s entries must all be unique 4 An RID of zero references the basic coordinate system The location of a grid point P in the sketch in this coordinate system is given by X Y Z 6 The displacement coordinate directions at P are shown by u uy u 7 56 THE BULK DATA PACKET ASTROS USER S MANUAL CORD2S Input Data Entry CORD2S Spherical Coordinate System Definition Form 2 Description Defines a spherical coordinate system by reference to the coordinates of three points The first point defines the origin The sec
337. flutter eigenvalue which is defined by the F unction packet 6 24 THE FUNCTION PACKET USER S MANUAL USER S MANUAL FUNCTIONS Constraint for ZETA 0 15 ZETA MACH DE MODE VIN 1 0 FDAMP ZETA MACH Di ELOLIST VINDX 0 15 ENDFUNC The Bulk Data Packet defines values for the MACH DENS MODE and VELO arguments for function design constraint 101 which points tothe function ZETA in the Functional Packet BEGIN BULK Velocity list VELOLIST 4 600 800 900 1000 Design constraint function request DCONF 101 MOP810K ZETA DC DCN1 ACH 0 8 DENS 0 8 ODE VINDX 4 DCONF 101 MOP8SL ZETA DCN DCN1 ACH 0 8 DENS 1 0 ODE VINDX 4 DCONF 101 M1P210K ZETA DC DCN1 ACH TE 2 DENS 0 8 ODE VINDX 4 DCONF 101 1P2SL ZETA DC DCN1 ACH A ADA DENS 1 0 ODE VINDX 4 DCONF 101 OP810K ZETA DCN1 DCN1 ACH 0 8 DENS 0 8 ODE 2 VINDX 4 DCONF 101 OP8SL ZETA DC DCN1 ACH 0 8 DENS LQ ODE 2 VINDX 4 DCONF 101 1P210K ZETA DC DCN1 ACH Lo DENS 0 8 ODE 2 VINDX 4 DCONF 101 1P2SL ZETA DC DCN1 ACH dee DENS 1 0 ODE 2 VINDX 4 ENDDATA 6 5 INSTRINSIC RESPONSE COMMANDS The ASTROS Instrinsic Response F unction Commands are desc
338. formation specified in the solution control through the TSTEP and DLOAD options This discipline has no associated constraints and while it is fully supported in the OPTIMIZE subpacket it will not generate data for use in the re design task There are many additional options which can be selected in transient analysis These are 1 initial conditions which can be selected through the IC option for DIRECT transient analyses 2 Fast Fourier Transform techniques which are selected with the FFT option and 3 discrete gust loads which are applied using the GUST option In each case the solution control option points to a bulk data entry having the same name In addition the K2PP B2PP M2PP TFL and DAMPING options may be used with or without an ESET Boundary Condition option to impose a case by case set of additional inputs degrees of freedom for modelling control systems etc In ASTROS each time step for which output is saved is considered to be a separate subcase It is important to note that like the MODES discipline more than one subcase is represented by a single solution control discipline statement In output requests therefore the subcases for which output is desired must be explicitly selected This is presented in greater detail in section 5 4 and in Chapter 6 5 3 7 FREQUENCY Discipline Options The FREQUENCY discipline is very similar to the TRANSIENT discipline presented in the preceding subsec tion Frequency step and load infor
339. from each of these boundary conditions The ASTROS executive system generates a name for each subscripted vari able and that name is used by all the engineering modules receiving the subscripted entity name as an argument The actual database entity name need not be known This does however impose the following restriction a subscripted entity may not be used as a hidden entity in any engineering module it must appear in the calling list for the module because only the executive system knows the actual name of the database entity corresponding to the current subscript value In the standard sequence provision has been made for up to 1000 entities doubly subscripted arrays of entities are set up for 30 boundary conditions and 33 secondary subscript values but you can change the declared number of subscripts to match the required range of indices 4 6 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL Table 4 2 Real Parameters in the Standard Sequence PARAMETER USED IN DESCRIPTION DEFAULT NAME MODULES SOLUTION Exponential move limit for fully stressed design Set through the ALPHA FSD Solution Control OPTIMIZE command 0 90 Convergence test limit specifying the maximum percent objective CNVRGLIM DESIGN change for the appropriate problem to be considered converged 0 50 FSD Output from SOLUTION ACTCON Criteria for defining a constraint to be active in determining CTL DE
340. fying data for each constraint in the print includes the TYPE COUNT which is a running count by constraint type of all active and inactive constraints This allows the user to identify exactly which constraint is active e g the fourth flutter constraint or the 3000th Von Mises stress constraint Additionally if the constraint is associated with a particular boundary condition the associated boundary condition identification is shown Similar connections are made for subcase and element dependent constraints If the constraint is not boundary condition subcase or element dependent zeros blanks or the string N A will appear in the corresponding columns of the active constraint summary The user is cautioned that the constraint 8 26 OUTPUT FEATURES ASTROS USER S MANUAL Table 8 18 Design Variable Values 1TEN BAR TRUSS ASTROS VERSION 9 0 03 03 93 P 7 ASTROS ITERATION 1 STATIC ANALYSIS ASTROS DESIGN VARIABLE VALUES DESIGN DESIGN MINIMUM MAXIMUM OBJECTIVE LINKING LAYER LAYER USER VARIABLE VARIABLE ID VALUE VALUE VALUE SENSITIVITY OPTION NUMBER LIST LABEL 1 2 00000E 00 6 66700E 03 1 00000E 03 5 40000D 02 UNIQUE PHYSICAL N A N A ROD1 2 2 00000E 00 6 66700E 03 1 00000E 03 5 40000D 02 UNIQUE PHYSICAL N A N A ROD2 3 2 00000E 00 6 66700E 03 1 00000E 03 5 40000D 02 UNIQUE PHYSICAL N A N A ROD3 4 2 00000E 00 6 66700E 03 1 00000E 03 5 40000D 02 UNIQUE PHYSICAL N A N A ROD4 5 2 00000E 00 6 66700E 03 1 00000E 03 5 40000D 02 UNIQUE PHYSICAL N
341. g edge in coordinate system cP Real Y1 gt 0 0 X12 Airfoil chord length in x axis coordinate of system cP Real gt 0 or blank IPANEL Identification number of an AEFACT data entry containing a list of chord wise cuts in percent chord for wing paneling Integer gt 0 or blank Remarks 1 Ifthe Raptus field is blank a round leading edge of radius zero is used 2 IPANEL is optional and is used when different chord wise cuts on each end of the panel are desired 7 20 THE BULK DATA PACKET ASTROS USER S MANUAL AIRFOIL 3 For WING components the options for USO LSO THK and CAM are All Blank Default flat plat airfoil generated automatically aia Lower and upper surface ordinates of airfoil are defined with effectively LSO uso internally generated Lower and upper surface ordinates of airfoil are defined cam Must USO LSO be blank Half thicknesses about the camber line are defined Lso Must be THK CAM blank USO LSO CAM Illegal over specification of data LSO CAM Illegal must use THK field for half thickness CAM alone Illegal under specification of data For CANARD components the options are as above except that camber is not allowed so cam Must be blank All Blank Default flat plat airfoil generated automatically Lower and upper surface ordinates of airfoil are defined with uso alone effectively LSo uso internally generated sviso Lower and upper surface ordinates
342. generated by the program These are described in this section 2 2 2 1 Unique ASTROS files There are three unique files that are used frequently by ASTROS These are unique in the sense the program will automatically define file names for these if you do not explicitly ASSIGN them These files and their default names are shown in the table below May Override with Generated Name if ASSIGN FILE ASSIGN Command is Not Used Command The print file NO filename prt The log file NO filename log The PUNCH file YES filename pch The filename represents the name of the file containing the ASTROS input data stream The log file is a special file that contains the history of your execution You may monitor the progress of your job by viewing the log file periodically Upon completion of the job the log file is appended to the print file and then deleted 2 2 2 2 Databases Each database that you use during an execution is comprised of at least two physical files The trailing components of these file names is always generated by ASTROS When you ASSIGN a database with a status Of NEW and provide a physical file name phys_name the program generates the file names phys_name EDB and phys_name 00 There may be times most often in the case of the RUNDB that you ASSIGN a database with a status of TEMP In such cases the program internally generates file names that are unique to your job The detailed rules
343. h the displacements are measured at grid point Integer gt 0 PS Permanent single point constraints associated with grid point any of the digits 1 through 6 with no embedded blanks I nteger gt 0 Remarks 1 The contents of Fields 3 7 or 8 of this entry are assumed for the corresponding fields of any GRID If any of these fields on the GRID entry are blank the default option defined by this entry occurs for that field If no permanent single point constraints are desired or one of the coordinate systems is basic the default may be overridden on the GRID entry by making one of the Fields 3 7 or 8 zero rather than blank Only one GRDSET entry may appear in entry whose Field 3 7 and 8 are blank the user s Bulk Data packet 2 The primary purpose if this entry is to minimize the burden of preparing data for problems with a large amount of repetition e g two dimensional pinned joint problems 3 At least one of the entries CP CD or PS must be nonzero ASTROS THE BULK DATA PACKET 7 145 GRID USER S MANUAL Input Data Entry GRID Grid Point Description Defines the location of a geometric grid point of the structural model the directions of its displacement and its permanent single point constraints Format and Example 1 2 3 4 5 6 7 8 9 10 GRID ID CP XI X2 X3 CD PS GRID 2 3 LD 2 0 3 0 315 Field Contents ID Grid point identification number
344. he angular locations in degrees of the body panels Integer gt O or blank LAXIAL Identification number of an AEFACT data entry which defines the axial locations of in degrees of the body panels Integer gt O or blank Remarks 1 NRAD and LRAD are mutually exclusive 2 If LRAD and NRAD are zero or blank the radial cuts specified by the BODY or AXSTA entries are used 3 LAXIAL is used only for FUSEL components Inputs on the AEFACT entry are the dimensional fuselage stations 4 If LAXIAL is blank the axial locations are the same as those given by AXSTA data entries for the given body component ASTROS THE BULK DATA PACKET 7 177 Input Data Entry PBAR Simple Beam Property Defines the properties of a simple beam bar which is used to create bar elements via the CBAR entry Description Format and Examples 1 2 3 4 5 6 7 8 9 PBAR PID MID A 11 12 J NSM TMIN CONT CONT C1 C2 D1 D2 El E2 F1 F2 CONT CONT K1 K2 112 R12 R22 ALPHA PBAR 39 6 2 9 5 97 1 2 3 23 2 0 4 0 Field Contents PID Property identification number Integer gt 0 MID Material identification number Integer gt 0 A Area of bar cross section Real gt 0 0 Ti Area moments of inertia Real 11 gt 0 0 12 gt 0 0 1112 gt 112 J Torsional constant Real gt 0 0 NSM Nonstructural mass per unit length Real gt 0 0 TMIN The minimum cross sectional area in design Real D
345. he arithmetic oper ands is evaluated prior to testing the relation When the data type of two arithmetic operands differs one operand is converted to the type of the other before the comparison is made See Section 3 2 5 for data type conversions The numeric values of the arithmetic operands are compared as specified by the relational operator and the resulting value is either TRUE or FALSE 9 3 4 MATRIX EXPRESSIONS Matrix expressions are those which combine two or more matrices to yield a matrix result 9 3 4 1 Matrix Operators MAPOL allows four computational matrix operators as shown in Table 9 8 All matrices must be con formable in order to perform these operations In the case of addition and subtraction this means that the number of rows and columns in A and B must be the same In the case of multiplications the number of columns of the premultiplier must equal the number of rows in the post multiplier Table 9 8 Matrix Operators in MAPOL OPERATOR DESCRIPTION A B Aij Bij A B Aij Bij zys Y Aik Bkj k A Aij 9 16 MAPOL PROGRAMMING ASTROS USER S MANUAL Matrix equations are written with the square brackets just as they are when declared Examples of these equations are B Cl Q I Z R S 2 K 1 Matrix operands may also be grouped to direct the order of operation Instead of the parentheses used in scalar expressions the square bracke
346. hear stress or strain are then printed A safety margin based on the maximum stress value is computed for stress output A large safety margin is printed if not limits were specified on the material property entry Table 8 15 contains a sample of the SHEAR panel element output The strain energy print for the SHEAR panel is identical to that for the BAR element and includes a breakdown by element and by element type 8 2 2 Nodal Response Quantities ASTROS has two basic forms of node point the structural node and the extra point The structural node is defined as either a grid point having 6 degrees of freedom three translations and three rotations or a scalar point having a single degree of freedom These node points can be used to connect metric and scalar structural elements The extra point is similar to the scalar point in that it has a single degree of freedom but differs in that extra points included in the model are selected in the boundary condition rather than being implicitly included in the model Further they cannot be connected directly to either metric or scalar structural elements instead these elements are connected through terms introduced by direct matrix input or by transfer functions Extra points are used in dynamic analyses for modeling control systems and other nonstructural mechanisms in the system under analysis These degrees of freedom do not appear in the system matrices until after the dynamic matrix assembly and
347. hrases attached to the print or punch statement At the higher level the subset options generate defaults for the entire print or punch statement F or example ITI E ALL STRESS ALL STRAIN ALL requests that all stresses and strains at all time steps for the iterations in ITERLIST 10 be printed In addition the subset options can be attached to the individual quantity options to override the print default For example ITI E ALL STRESS ALL STRAIN TIME overrides the TIME ALL default for the strain output At both levels the defaults are NONE for TIME FREQ and MODE and ALL for ITER ASTROS THE SOLUTION CONTROL PACKET 5 15 USER S MANUAL The subset options in ASTROS are OPTION DESCRIPTION nRROUENGY Selects the frequency steps of frequency response disciplines at which output is desired by referencing a FREQLIST bulk data entry pone TON Selects the design iterations at which output is desired by referencing a ITERLIST bulk data entry Selects the eigenvectors of a normal modes discipline at which output MODE is desired by referencing a MODELIST bulk data entry Selects the time steps of transient response analysis at which output is TIME desired by referencing a TIMELIST bulk data entry 5 4 2 Response Quantity Options ASTROS is able to compute a number of response quantities for each discipline type Each discipline type generates a different se
348. ication Integer gt 0 LINKID link identification number referring to ELIST ELISTM and or PLIST PLISTM entries Integer gt 0 or blank Default DvID VMIN Minimum allowable value of the design variable Real gt 0 0 Default 0 001 VMAX Maximum allowable value of the design variable Real gt 0 0 Default 1000 0 VINIT Initial value of the design variable Real VMIN lt VINIT lt VMAX Default 1 0 LAYRNUM Layer number if referencing a single layer of composite element s Integer gt 0 or blank LAYRLST Set identification number of PLYLIST entries specifying a set of composite layers to be linked Integer gt 0 or blank LABEL Optional user supplied label to define the design variable Character Remarks 1 The elements linked to the DESVARP are specified using one or more ELIST ELISTM PLIST and PLISTM entries 2 The initial element thickness or area used in the structural analysis is derived from the VINIT value and the property value on the associated property entry tinit VINIT property_value Similarly the minimum and maximum values are the VMIN and vMAX values of the element property are derived from tmin VMIN property_value tmax VMAX property_value LAYRNUM and LAYRLST are mutually exclusive 4 Noncomposite elements may be linked to composite layers by including them in the ELIST ELISTM and or PLIST PLIST sets ASTROS THE BULK DATA PACKET 7 107 DESVARS USER S MANUAL Input Data Entry
349. ich links the design constraint VALUE to the Functional Packet BEGIN BULK DCONF 101 EID1 VALUE DCN1 DCN1 EID 1 ALLOW 57 0 3 ENDDATA ASTROS THE BULK DATA PACKET 7 77 DCONF USER S MANUAL 3 The Dconr entry must uniquely define each argument to the named function and constitutes one or more references to the function FNAME The following example computes the normal stress in the element s X direction for elements 1 and 2 The Function Packet defines the function specification for recovering the allowable normal stress in the element s X direction FUNCTIONS VALUE cid allow STRESS eid SIGX allow 1 0 ENDFUNC The Bulk Data Packet defines two design constraint function requests for the elements 1 and 2 and references design constraint 101 which links the design constraint VALUE to the F unctional Packet BEGIN BULK DCONF 101 EID1 VALUE DCN1 DCN1 EID 1 ALLOW 60 3 DCONF 101 EID2 VALUE DCN1 DCN1 EID 2 ALLOW 60 3 ENDDATA More than one constraint can be created by a single DCONF entry if list identification arguments are used FUNCTIONS VALUE2 list allow STRESS ELEMLIST list SIGX allow 1 0 ENDFUNC BEGIN BULK DCONF 101 EID1 VALUE2 DCN1 DCN1 LIST 101 ALLOW 60 3 ELEMLIST 101 QUAD4 1 2 ENDDATA 4 VALi must be of the type either integer or real required by the function FNAME 7 78 THE BULK DATA PACKET ASTROS USER S MANUAL DCONFLT Input Data
350. ient method in sensitivity analysis Set in ABOUND NAUS ABOUND The number of active displacement vectors for statics Set in ABOUND The total number of boundary conditions in the solution control packet Equal to the NBNDCOND SOLUTION number of optimization boundary conditions plus the number of analysis boundary conditions Output from SOLUTION MAKEST The number of global design variables in the design model Set by MAKEST and used in NDV hens many subsequent modules NITER N A The current optimization iteration number The number of optimization boundary conditions in the solution control packer Set in NUMOP TBC SOLUTION SOLUTION Table 4 5 Integer Aerodynamic Parameters NAME MODULES DESCRIPTION ABOUND The index value for the Mach number dependent subscripted steady aerodynamic MINDEX AEROSENS matrices Typically has a value used to select the proper matrices for the current BOUND boundary condition PFAERO SAERODRV Identifies the subcase subscript SAERO subcases with the same symmetry M ach SUB SAERO number MINDEX trim type and dynamic pressure are processed using the same S others subscript This occurs with multiple load conditions with the same aero correction A control flag denoting whether the symmetric SyM 1 or antisymmetric SyM 1 SYM BOUND steady aeroelastic matrices are to be used are to be used in the current boundary condition ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 9 USER S MANUAL Table 4 6 Integer Disciplin
351. ifies conditions for steady aeroelastic trim or nonplanar steady aerodynamic analy sis Format and Example 1 2 3 4 5 6 7 8 9 10 TRIM TRIMID MACH QDP TRMTYP EFFID vo CONT CONT LABEL1 VAL1 LABEL2 VAL2 LABEL3 VAL3 LABEL4 VAL4 etc TRIM 1001 0 90 1200 LIFT 100 926 3 ABC ABC NZ 8 0 QRATE 0 243 LEV FREE ALPHA FREE Field Contents TRIMID Trim set identification number Integer gt 0 MACH Mach number Real gt 0 0 QDP Dynamic pressure Real gt 0 0 TRMTYP Type of trim required Character or blank See Remark 3 blank SUPORT controlled trim ROLL Axisymmetric roll trim 1 DOF LIFT Symmetric trim of lift forces 1 DOF PITCH Symmetric trim of lift and pitching moment 2 DOF EFFID Identification number of CONEFFS Bulk Data entries which modify control surface effectiveness values Integer gt 0 or blank Remark 2 vo True velocity Real gt 0 0 or blank See Remark 12 LABELi Label defining aerodynamic trim parameters VALi Magnitude of the specified trim parameter Real or the character string FREE Remarks 1 The TRIM entry is selected in Solution Control in the SAERO and NPSAERO disciplines with the TRIM option 2 All aerodynamic forces created by the control surface will be reduced to the referenced amount F or example an EFF1 of 0 70 indicates a 30 reduction in the forces 3 The TRM
352. ility UTUPRT The print utility UTUPRT has been written such that any data base unstructured entity can be printed to the output file The calling sequence for UTUPRT is CALL UTUPRT UNSTRUCT type Unlike other data base entities there is no information in an unstructured entity to identify what type of data is stored in its records The user therefore must supply the TYPE argument to select the proper format to use in the print The following TYPE s are available TYPE lt prints only the record length in single precision words of each record in the entity TYPE 0 prints each record using an integer format TYPE 1 prints each record using a real single precision format TYPE 2 prints each record using a double precision format For TYPE values greater than or equal to zero each record will be printed in its entirety in the selected format If as is typical the record contains mixed data e g both integer and real data the user can make multiple calls to UTUPRT to view first the integer format and then the real format No errors will occur but the real data will give spurious looking integer prints and vice versa 8 6 THE eSHELL INTERACTIVE PROGRAM A code like ASTROS is so general that to make all possible response quantities available would take decades of effort if it could be done at all In fact a mature finite element code like NASTRAN is continuously adding new output capabilities as the user community dictates
353. in which they must appear is fixed The purpose of this section is to document the structure of the input data stream Detailed documentation of the data within each data packet is then presented in separate chapters Figure 3 1 shows the general form of the input data stream and Figure 3 2 illustrates the actual input stream features with a sample stream for a ten bar truss model The first non blank record of the input file must be either the ASSIGN command or a Resource Section If an ASSIGN command is used then this command will enable you to attach the run time database s that are used during the execution of the ASTROS system There are four optional data packets following the ASSIGN command which if they are present must appear in the order shown The first is the DEBUG packet which contains debug com mands to control or select specific actions within the executive and database management systems The second packet is the MAPOL packet containing the executive system control directives consisting of either a standalone MAPOL program or EDIT commands to modify the standard MAPOL program If the MAPOL packet is absent the unmodified standard MAPOL sequence directs the execution The Solution Control commands appear in the third optional packet denoted by the keyword SOLUTION These commands select the engineering data to be used in each subcase from the set of data provided in the Bulk Data packet The fourth packet is the FUNCTION packet It contai
354. ine request defines the requested subcase If the cid reference is omitted then the coordinate value is returned in the displacement coordinate system of the grid points A cid of 0 requests that the coordinate be returned in the basic coordinate system 6 3 2 5 Element Response Functions The element response functions are defined by STRESS elemop stress_comp plyop caseop modeop STRAIN elemop strain_comp plyop caseop modeop where eid lyid plyop gt Pare i PLYLIST ply_sid e caseid GARGEE CASELIST case sid r EN modeid ROSSORE IT MODELIST mode_sid These functions allow a component of the requested element results referenced either by its value eia or a list ELEMLIST to be retrieved for the requested CASES and MODEs value or list When an element identification is used then the eid must be unique and if the eid is not unique then an element list must be used Composite elements must have their layer numbers specified by a layer number pl yid or a layer list PLYLIST The element response components for composite elements will always be recov ered at the center of the layer The allowable response components for each element type are shown in Table 6 3 ASTROS THE FUNCTION PACKET 6 9 Table 6 3 Element Response Components USER S MANUAL ELEMENT stress comp strain comp SIGAXL SIGTOR SIG1 SIG2 MAXSHEAR SIGA
355. ine specific configuration parameters are found in the ASTROS System Support Manual Contact your System Support Specialist if you require this information 2 1 4 1 The Host Configuration Section The Host Configuration Section indudes parameters which identify the type of the host computer and specify the Preference File templates ASTROS RUNNING ASTROS 2 3 2 4 RUNNING ASTROS USER S MANUAL Table 2 1 The Preference File Format Host HOST_params eBase lt Computing Resources gt eBase_params lt I O System Parameters gt eBase_params lt Program Authorization gt eBase_params eBase applib eBase applib_ params eBase matlib eBase matlib_params ASTROS lt Print File Controls gt ASTROS_params lt Computing Resources gt ASTROS_params lt Matrix Conditioning gt ASTROS_params lt Data Checking gt ASTROS_params lt Analysis Output Control gt ASTROS_params lt Solution Techniques gt ASTROS_params lt Element Options gt ASTROS_params lt I O System Parameters gt ASTROS_params lt Optimization Control Options gt ASTROS_params lt Program Authorization gt ASTROS_params eShell eShell_params ASTROS USER S MANUAL 2 1 4 2 The eBase Kernel Configuration Section The eBase Configuration File Section includes parameters which control the eBase Engineering Data base Management System kernel These include such information as default paths were databases are stored physica
356. ins The ABOUND routine determines the types of active constraints in each boundary condi tion and outputs logic flags to control the subsequent sensitivity computations Then boundary condition dependent constraints which are explicit functions of the design variables frequency and flutter are computed Next the sensitivities of the constraints to the displacements for those STATICS constraints which are explicit functions of the displacements e g stress and displacement constraints are computed using the MAKDFu module For these types of constraints the product of the stiffness sensitivities and the displacements and the mass sensitivities and the accelerations are also computed and modified appropri ately to account for design dependent loads and inertia relief The resulting matrix is then reduced and used to solve for the sensitivities of the displacements to the design variables This matrix is recovered to the free displacement set in a manner similar to the recovery of the outputs in the analysis phase of the optimization segment The final module within the boundary condition loop for sensitivity evaluation is MKAMAT Within this module the constraint sensitivities to the design variables are formed from the product of the two sensitivity matrices previously obtained For static aeroelastic analyses a procedure similar to that for STATICS is used twice once for pseudo displacements that allow computation of aeroelastic effectiveness der
357. int of the form Strim lt trimreg OF Strim trimreg Format and Example al 2 3 4 5 6 7 8 9 10 DCONTRM SETID PRMLAB CTYPE PRMREQ DCONTRM 100 AILERON UPPER 25 0 Field Contents SETID Set identification number referenced by the DCONSTRAINT Solution Control com mand Integer gt 0 PRMLAB Alphanumeric string identifying a constrained control surface or aeroelastic trim parameter e g ALPHA Or PRATE See Remark 2 CTYPE Constraint type either UPPER for upper bound or LOWER for lower bound Charac ter Default UPPER PRMREQ Bound for the trim parameter For units see Remark 3 Real Remarks 1 The DCONTRM entry is selected in Solution Control with the DCONSTRAINT SETID option of the SAERO command 2 The PRMLAB may refer to AESURF Or CONLINK control surfaces or to any of the TRIM entry parame ters NX NY NZ PACCEL QACCEL RACCEL PRATE QRATE RRATE ALPHA Or BETA The only require ment is that the constrained control surface must be declared on the TRIM entry The user will be warned if trim parameters not on the TRIM entry are constrained since these parameters are fixed they are design invariant 3 The units for control surface deflections are degrees For rates the units should be radians sec For linear accelerations NX NY NZ the units should be consistent length sec sec or if a CONVERT MASS entry was used sh
358. ints Constraints Discipline 2 End Do OPTIMIZATION SEGMENT SENSITIVITY PHASE Select Active Constraints For Each Active Boundary Condition Do Active Discipline 1 Active Subcase 1 Active Subcase 1 Constraint Sensitivities Constraint Sensitivities Active Discipline 2 End Do OPTIMIZATION PHASE Redesign Based on Current Active Constraints and Constraint Sensitivities END DO FINAL ANALYSIS SEGMENT For Each Boundary Condition Do Discipline 1 Subcase 1 Subcase 2 Discipline 2 End Do ASTROS Figure 4 1 Structure of the Standard MAPOL Sequence THE EXECUTIVE SYSTEM AND MAPOL 4 5 USER S MANUAL 4 4 1 MAPOL Declarations MAPOL is a strongly typed language that requires all variables used in a program unit either the main program or a procedure to be declared This applies to both simple variables like real and integer scalar or array variables and to high order variables like MATRIX that refer to database entities The first several hundred lines of the standard sequence consist solely of these variable declarations Tables 4 2 through 4 7 give a summary of the scalar parameters used in the standard MAPOL sequence These parameters initialized in engineering modules or in the MAPOL sequence are used as either logic control flags or arguments to the engineering modules The tables which are catagorized by function provide a brief description of each variable and a list o
359. iption Defines body axial station parameters There is one AXSTA for each axial station at which the surface points are defined Format and Examples 1 2 3 4 5 6 7 8 9 10 AXSTA BCID XSTA CBOD ABOD LYRAD LZRAD AXSTA 10 10 00 05 10 20 Field Contents BCID Body component identification number Integer gt 0 XSTA Value of the x ordinate of the body station Real CBOD Value of the z ordinate of the center line at this station This defines the body camber Real ABOD Cross sectional area of the body at this station Real gt 0 0 LYRAD LZRAD Identification number of an AEFACT data entry containing a list of the y ordinates z ordinates of the body section Integer gt 0 0 Remarks 1 If ABOD is present the body is assumed to be circular and the radial ordinates are computed at NRAD cf the BODY bulk data entry equal intervals No LYRAD and LZRAD data are allowed when ABOD is present 2 IfABOD is blank LYRAD and LZRAD data must be present For Pods CBOD LYRAD and LZRAD data are not permitted For the fuselage XSTA is actual x location for pods XSTA is relative to the xLoc value given on the BODY bulk data entry ASTROS THE BULK DATA PACKET 7 25 BAROR USER S MANUAL Input Data Entry BAROR Simple Beam BAR Orientation Default Values Description Defines default values for fields 3 and 6 8 of the CBAR entry Format and Examples
360. irst optimization iteration Used to estimate initial move in the one dimensional search Updated as the optimization progresses 0 2 max Xj DX1 Maximum relative change in a design variable attempted on the first optimization iteration Used to estimate initial move in the one dimensional search Updated as the optimization progresses DX2 Maximum absolute change in a design variable attempted on the first optimization iteration Used to estimate initial move in the one dimensional search Updated as the optimization progresses EXTRAP Maximum multiplier on the one dimensional search parameter ALPHA in the one dimensional search using polynomial interpolation extrapolation Note 3 SCFO The user simplified value of the scale factor for the objective function if the default or calculated value is to be overridden Note 3 SCLMIN Maximum numerical value of any scale factor allowed Note 3 STOL Tolerance on the components of the calculated search direction to indicate that the Kuhn Tucker conditions are satisfied Note 3 THETAZ nominal value of the push off factor in the Method of F easible Directions Note 3 7 170 THE BULK DATA PACKET ASTROS USER S MANUAL REAL PARAMETER DEFINITION DEFAULT Multiplier on the move parameter ALPHA in the XMULT one dimensional search to find bounds on the Note 3
361. is segment The declaration segment declares all variables used in the MAPOL sequence This includes all integer and real scalar variables as well as high order variables relations matrices and unstructured database entities Within the solution algorithm the preface mod ules comprise a group of engineering modules exercised prior to the boundary condition loops to perform a number of system initialization tasks eg loads generation and the computation of invariant aerody namic matrices The separate optimization and analysis segments consist of a loop on the number of optimization or analysis boundary conditions in the current execution In the optimization segment a second boundary condition loop is performed to obtain the sensitivities of active boundary condition dependent constraints in preparation for the optimization task Figure 4 1 provides the standard algorithm structure showing how multidisciplinary optimization is performed in ASTROS It is readily apparent that the structure of the standard MAPOL sequence has been determined by the requirement to perform multidisciplinary optimization Each of the segments of the standard sequence are discussed in greater detail in the following sections 4 4 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL PREFACE SEGMENT Initialization PREFACE Segment WHILE NOT CONVERGED DO ANALYSIS PHASE For Each Boundary Condition Do Discipline 1 Subcase 1 Subcase 2 Constra
362. it see Section 9 6 as the Goro statement The label identifier must also have been declared in the program unit s specification statements The general syntax is GOTO lt label gt where lt label gt is any legal identifier that has been declared When used the label is denoted by lt label gt followed by any valid MAPOL statement For example IF A lt B GOTO SKIP Note that the label must be followed by a colon 9 4 3 ITERATION It is often necessary to execute a group of statements repeatedly Generally although the statements themselves remain the same the data on which they operate changes This iteration or looping must terminate after a finite number of iterations therefore a decision must be made to determine whether to continue or terminate the loop MAPOL supports two iteration forms Each is described in this section 9 4 3 1 The FOR DO Loop It is often necessary to perform a set of calculations a specific number of times and that number does not depend on the statements within the loop Consider the problem of summing the first 20 integers ASTROS MAPOL PROGRAMMING 9 19 USER S MANUAL 20 SUM n n 1 Such a problem is ideally suited to the FOR loop and could be evaluated using the following MAPOL program MAPOL INTEGER N SUM TOP TOP 20 SUM 0 FOR N 1 TO TOP DO SUM SUM N ENDDO PRINT 1X SUM END The general syntax of the FOR loop is FOR lt var gt
363. iteration to the next Specifies the maximum number of design iterations that may ZEROITER n n have the same objective function value before ASTROS is terminated ASTROS THE INPUT DATA STREAM 3 17 USER S MANUAL 3 4 5 SEQUENCER INTERMEDIATE PRINT COMMANDS There are a number of print and control options for the grid point sequencer that are shown in Table 3 5 Table 3 5 Sequencer Debug Commands KEYWORD DESCRIPTION Selects sequencing intermediate print SEQPRINTZOpE DETAIL Requests detailed print of sequencing DIAGNOSTIC Requests diagnostic print Select sequencer method SEQMETH meth CM Selects the Cuthill M cK ee Method GPS Selects the Gibbs Poole Stockmayer Method ALL Selects the best of both 1 and 2 NOSEQMPC Requests that MPCs not be processed during sequencing Selects sequencing method BAND Selects minimum bandwidth criteria ng eo cr PROF Selects profile criteria RMS Selects RMS criteria WAVE elects minimum wavefront criteria SEQPUNCH Requests punching of SEQGP bulk data entries SEQOFF Deselects sequencing 3 18 THE INPUT DATA STREAM ASTROS USER S MANUAL Chapter 4 THE EXECUTIVE SYSTEM AND MAPOL The ASTROS system is controlled by an Executive System One of the functions of the ASTROS executive system described in detail in Reference 1 is to determine the sequence in which the modules of the program are invoked F
364. ithout requiring the user to jump to the end of the MAPOL sequence This is particularly useful when an edited standard solution sequence is used The TRNSPOSE procedure provides an additional MATRIX operation that is otherwise missing from the lan guage While the operation A TRANS B C is available within the syntax of MAPOL expression the operation A TRANS B is not The intrinsic procedure TRNSPOSE allows this matrix operation to be performed The form of TRNSPOSE CALL TRNSPOSE A TRANSA where A is the matrix to be transposed and TRANSA is the resultant transposed matrix 9 28 MAPOL PROGRAMMING ASTROS USER S MANUAL Table 9 10 Intrinsic Mathematical Functions in MAPOL PROCEDURE DESCRIPTION USAGE ABS Absolute value ABS B ACOS Cosine ACOS B ASIN Arcsine ASIN B ATAN Arctangent ATAN B CMPLX Complex CMPLX B C cos Cosine COS B COSH Hyperbolic cosine COSH B EXP Exponential EXP B IMAG Imaginary Equivalent to FORTRAN AIMAG IMAG B LN Natural Logarithm Equivalent to FORTRAN LOG LN B LOG Common Logarithm Equivalent to FORTRAN LOG10 LOG B MAX Selects largest value MAX B C RE Real component Equivalent to FORTRAN REAL RE B SIN Sine SIN B SINH Hyperbolic sine SINH B SQRT Square root SQRT B TAN Tangent TAN B TANH Hyperbolic tangent TANH
365. ition of a concentrated load at a grid point Definition of a concentrated load at a grid point Definition of an acceleration vector for gravity loads Definition of linear load combinations Definition of a moment at a grid point Definition of a moment at a grid point Definition of a pressure load over an area Definition of a pressure load on plate elements Definition of a pressure load on plate elements in a specified direction Definition of a temperature at a structural node Definition of default nodal temperatures 7 5 4 Boundary Condition Constraints ASE ASET1 DYNRED JSE JSET1 MPC MPCADD OMIT OMIT1 RBAR RBE1 RBE2 RBE3 RROD Analysis set definition Analysis set definition Dynamic reduction parameters Inertia relief mode shape parameter definition Inertia relief mode shape parameter definition Multipoint constraint definition Definition of combinations of mpc sets Omit set definition Omit set definition Rigid bar element Rigid body element Rigid body element Rigid body element Rigid rod element 7 6 THE BULK DATA PACKET ASTROS USER S MANUAL see SPC1 SPCADD SUPORT Single point constraint enforced displacement definition Single point constraint definition Definition of combinations of SPC sets Definition of coordinates for determinate reactions 7 5 5 Design Constraints DCONTRM DCONTW DCONTWM DCONTWP
366. ivatives and once for real displace ments that support the static strength constraints The static aeroelastic sensitivity code is further complicated by the generality of the aeroelastic correction matrix selections which are subcase depend ent After all the active optimization boundary conditions have been processed the DESIGN module is called Within this module the approximate design problem is arranged for use by the optimizer and is solved Following convergence of the approximate problem execution returns to the top of the optimization loop and a complete reanalysis of all the boundary conditions is performed Once completed the ACTCON module determines if the global problem is converged and if so sets the global convergence flag to TRUE causing the execution to pass to the top of the analysis segment If any analysis boundary conditions exist they will be processed in a manner similar to the analysis phase of the optimization segment After performing the requested final analyses if any the executive system terminates the ASTROS execution 4 4 3 Modifying the Standard MAPOL Sequence The standard MAPOL sequence is provided to allow you to run the ASTROS system without detailed knowledge of the MAPOL language or the standard sequence There is not however any requirement that the standard sequence be used Chapter 8 outlines the procedure for writing a valid MAPOL sequence and any series of syntactically correct MAPOL statements ma
367. kept after the run The other legal optional parameters are DBLKSIZE and IBLKSIZE ASSIGN RUNDB MYDB TEMP PASSWORD X DBLKSIZE 2048 IBLKSIZI NEW Database Example When the status is NEW a new database is created If the files already exist they will be overwritten voldbroot EDB index file voldbroot 00 data file 1 Other legal parameters are DLOC ILOC DBLKSIZE and IBLKSIZE ASSIGN RUNDB MYDB NEW PASSWORD X REALLOC DLOC tmp ILOC tmp In this example a database with files tmp MYDB EDB and tmp MYDB 00 are created If existing files are found they will be overwritten OLD DatabaseE xample When the status is OLD an old database is used The physical files that make up the database must exist Two or more files are used to store the database The names of these files are as follows voldbroot EDB index file voldbroot 00 data file 1 The pLoc and ILOC parameters along with the root database name are used to form the names No other parameters are legal Here is an example ASSIGN RUNDB X OLD PASSWORD X DLOC home dirl ILOC home dir1 In this example a database with files home dir1 MYDB EDB and home dirl MYDB 00 are used 3 8 THE INPUT DATA STREAM ASTROS USER S MANUAL 3 2 3 THE MEMORY COMMAND The MEMORY command specifies the amount of memory ASTROS will use for the internal storage of data The format of this command is WORKING work_mem
368. keyword MAPOL or by the keyword EDIT and is terminated upon encountering the SOLUTION CONTROL packet the BULK DATA packet or the end of the input stream In addition each of the initiator keyword commands act as directives to the MAPOL compiler to take specific actions The MAPOL and EDIT commands are GO LIST PrOD NOGO NOLIST L GO LIST DLI NOGO NOLIST where Saa l selects whether the MAPOL program is to be executed after compilation ee selects whether the MAPOL source code is to be written to the output file The MAPOL command is followed by a MAPOL program which can be any syntactically complete set of MAPOL statements as described in the chapter on MAPOL Programming Chapter 9 The EDIT com mand indicates that the MAPOL packet will consist of edit commands that INSERT DELETE or RE PLACE lines of the standard executive sequence 4 1 THE MAPOL PROGRAM If the MAPOL packet begins with the MAPOL command line the compiler assumes that the remaining statements in the packet constitute a complete MAPOL program That program can be any set of MAPOL statements that satisfy the rules of the language as presented in Chapter 8 The program can call any of a number of intrinsic functions including most of the common FORTRAN intrinsic functions and any of the engineering utilities and modules that are available in ASTROS You can access these modules in any desired order subject only to limits imposed by the engi
369. l block sizes for databases and security information 2 1 4 3 The ASTROS Configuration Section The ASTROS Configuration Section includes parameters which control the program These include con trols on peripheral and computing resources model data checking program defaults and so forth 2 1 4 4 The eBase applib and eBase matlib Sections The eBase applib and eBase matlib Configuration Sections include such items as dynamic memory sizes for applib and timing constants for the matlib high performance matrix utilities 2 1 4 5 The eShell Configuration Section The eShell Configuration Section includes parameters which control the eShell interactive interface to eBase It includes such items as system database locations and dynamic memory specifications 2 1 5 Dynamic Memory The architecture of ASTROS allows the modeling and analysis of finite element models of virtually unlimited size Most numerical calculations perform at maximum efficiency when all data for the opera tion fits in the working memory space of the program Many operations may be performed even when all data that they require does not fit in memory by using what is called spill logic Spill logic simply involves the paging of data to and from disk storage devices as necessary For very large jobs spill commonly occurs In such cases providing ASTROS with additional working memory can often improve performance On the other hand you do not want to give ASTROS excess memor
370. l data for the Givens methods which are used to extract all eigenvalues Format and Examples 1 2 3 4 5 6 7 8 9 10 EIGR SID METHOD FL FU NVEC E cont cont NORM GID DOF Requesting Eigenvectors in a Frequency Range EIGR 13 GIV 0 20 0 A A POINT 32 4 Requesting a Specified Number of Eigenvectors EIGR 13 MGIV 10 A A POINT 32 4 Field Contents SID Set identification number Required nteger gt 0 1 METHOD Method of eigenvalue extraction 2 3 GIV Given s method MGIV Modified Given s method FL FU Frequency range for eigenvector computations cycles sec Real gt 0 0 FL lt FU 4 NVEC Number of eigenvectors to compute Integer gt 0 default 1 E Mass orthogonality test parameter A non zero value requests a check of the mass orthogonality of the eigenvectors Real gt 0 0 default 10 NORM Method for eigenvectors normalization 5 6 Method for normalizing eigenvectors one of the character values MASS MAX or POINT mass Normalize to unit value of the generalized mass MAX Normalize to unit value of the largest component in the analysis set Default POINT Normalize to unit value of the component defined by G c defaults to max if point is not defined GID Grid or scalar point identification number Required only if NORM POINT nteger gt 0
371. lable for STATICS with inertia relief SAERO TRANSIENT and FREQUENCY analyses The LOAD option selects output of externally applied loads at the nodal points For statics the applied mechanical thermal and or gravity loads are output for the selected nodes and subcases Steady aeroe lastic loads output prints for each trim condition those trimmed forces applied to the structure following transformation from the aerodynamic model The SAERO applied load is the sum of the trimmed rigid loads and the flexible correction Each component is stored independently in the relation OGRIDLOD but Table 8 16 Displacement Vector TEN BAR TRUSS ASTROS VERSION 9 0 03 03 93 By 7 FINAL ANALYSIS SEGMENT FINAL STATIC ANALYSIS STATICS ANALYSIS BOUNDARY 1 SUBCASE 1 DISPLACEMENT VECTOR POINT ID TYPE TE T2 T3 R1 R2 R3 1 G 2 82588E 01 1 26504E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 2 G 3 17412E 01 1 31319E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 3 G 2 34438E 01 5 58118E 01 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 4 G 2 45562E 01 6 00705E 01 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 5 G 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 6 G 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 0 00000E 00 Table 8 17 Complex Displacement Vector ASTROS VERSION 9 0 03 03 93 P 8 FINAL ANALYSIS SEGMENT FREQUENCY ANALYSIS BOUNDARY 1 FREQ 3 2179463E 00 COMPLEX DISPLACEMENT VE
372. led documentation of the separate input structures of the data packet then follow within each Chapter This form of documentation enables this manual to be useful as a guide to the beginning user as well as a reference for the experienced user While there are a number of advanced input features the required input for most jobs is the ASSIGN DATABASE command described in Section 1 3 and the Solution Control and Bulk Data packets described in Chapters 3 and 5 respec tively In Chapter 6 following the input stream descriptions the output features of the ASTROS system are documented While these features are selected through directives in the input data stream they are sufficiently numerous and complex to justify a separate chapter devoted solely to output requests The 1 2 INTRODUCTION ASTROS USER S MANUAL output capabilities of the system are described in very general terms while the output requests available for each analysis discipline and optimization feature are documented in detail Most output is selected through Solution Control directives that are documented in Chapter 3 but some are selected through modifications to the executive MAPOL sequence Chapter 2 documents all of the output utilities avail able to the user through MAPOL directives and gives several examples of modifying the MAPOL se quence to obtain additional output Other features are described in the MAPOL Programmer s Manual which comprises Chapter 7 Many exa
373. lement supports both extensional and rotational properties The element coordinate system and sign conventions are shown in Figure 8 6 ASTROS supports stress strain force and strain energy output for the ROD The forces that are computed are 1 Axial force 2 Torque about the element axis The torque and force are both computed even if the particular element does not support torsional or extensional forces respectively In these cases a value of zero will be printed for the appropriate re sponse quantity The stresses and or strains that are available are 1 Axial stress or strain 2 Torsional stress or strain 3 Margin of safety for axial stress 4 Margin of safety for torsional stress The margins of safety for strain are not available and the stress margins are computed even if there are no limits specified on the material property entry In these cases a large safety margin value is used to signify that no limits were imposed An example of the ROD element output prints is shown in Table 8 12 The strain energy print for the ROD is identical to that for the BAR element and includes a breakdown by element and by element type Fx A GID1 Fx GID2 Xe T Figure 8 6 ROD Element Coordinate System 8 2 1 8 QDMEM1 TRMEM Element Output The QDMEM1 isoparametric element and the TRMEM constant strain triangular element are membrane elements which support isotropic orthotropic and composite membrane properti
374. lex SIL Internal DOF number FLAG Type of DOF 6 GRID 1 SCALAR RFORCE Real Part of Forces IFORCE Imaginary Part of Forces where BC NITER DISC and SUBCASE identify the ASTROS analysis EID and ETYPE identify the element SIL identifies which degree s of freedom these forces are associated with obviously it is one of those attached to the element EID ETYPE and the forces are stored in RFORCE and IFORCE with scalar points using only word 1 of each array Notice that there will be one entry for each grid scalar for each element for each subcase for each discipline for each boundary condition for each iteration for which data are requested in Solution Control 8 2 3 Design Variables and Design Constraints Thereis an important distinction between global design variables and local design variables in ASTROS A number of linking options relating global variables to local variables are provided and are described in ASTROS OUTPUT FEATURES 8 25 USER S MANUAL Section 2 of the Theoretical Manual Briefly the local variable is the physical element property e g thickness or cross sectional area that is free to change in the design process while the global variables are the actual variables that are modified by the resizing module The resultant physical variables are then computed based on the user s linking options and the current global design variable values The GDESIGN solution control print option allows the user
375. lized coordinates are used in the normalization process Finally if you select NORM POINT the eigenvectors are normalized with respect to the value of the component defined by GID and DoF This component must bein the analysis set 7 122 THE BULK DATA PACKET ASTROS USER S MANUAL EIGR LANCZOS Bulk Data Entry EIGR LANCZOS Description Specifies real eigensolution control data for the Lanczos method of eigenvalue extraction Format and Examples di 2 3 4 5 6 7 8 9 10 EIGR SID METHOD FL FU NVEC E CONT CONT NORM GID DOF EIGR dl LANCZOS 0 20 0 Field Contents SID Set identification number 1 nteger gt 0 Required ETHOD Method of eigenvalue extraction 2 Character LANCZOS Required FL FU Frequency range for eigenvector computations cycles sec Real FL lt FU 3 NVEC Number of eigenvectors to compute Integer 3 E Mass orthogonality test parameter A non zero value requests a check of the mass orthogonality of the eigenvectors Real gt 0 0 10 NORM Method for eigenvectors normalization 5 6 Method for normalizing eigenvectors one of the character values MASS MAX or POINT MASS Normalize to unit value of the generalized mass MAX Normalize to unit value of the largest component in the analysis set Default POINT Normalize to unit value of the component defined by G c defaults to Max if point is not defined GID Grid or scalar point iden
376. ludes search directions Includes gradient information Includes scaling information NO 0 ah U IND FR Includes one dimensional search information Additional flutter eigenextraction information FLUTTRAN n 1 Prints the number of iterations required to find each flutter root gt 1 Includes the estimated roots for each iteration MKUSET redundant set warnings AROSETSR gt 0 Prints warning messages if the same degree of freedom is placed in a set more than once Planar steady aerodynamics geometry option SAROGEOM n ASTROS execution stops in module STEADY after the steady gt 0 aerodynamic geometry has been computed No printed output is generated unless the STEADY debug is also used Prints additional constraint data SCEVAL gt 0 Prints the stress or strain components the constraint type and the constraint value for each constrained element layer Prints or punches SHAPE or SHAPEM Bulk Data entries automatically created by the SHPGEN capability SHPGEN opt PRINT to print the generated Bulk Data entries PUNCH to punch the generated Bulk Data entries BOTH to print and punch the generated Bulk Data entries Steady preface USSAERO output 1 Prints steady aerodynamic model geometry STEADY n Includes stability coefficient data 2 3 Indudes pressure data 4 Indudes velocity components and matrix output 3 16 THE INPUT DATA STRE
377. make up the set of design constraints Finally the DCFUNCTION option may be used to select functional constaints that are applied to the STATIC responses from the current solution 5 3 3 MODES Discipline Options MODES s completely defined for analysis by the METHOD boundary specification which refers to an EIGR bulk data entry selecting the eigenvalue extraction method If however the modal analysis is performed in the OPTIMIZE subpacket the DCONSTRAINT option can be used to apply frequency constraints through the DCONFRQ bulk data entry Note that more than one frequency can be constrained and that more that one constraint can be placed on the same modal frequency The user is warned against defining the frequency constraints in such a way as to specify an excluded range of frequencies for a mode for example requiring that a modal frequency be below 10 Hz OR above 20 Hz ASTROS treats all applied constraints as Boolean AND statements so the above example would be interpreted by ASTROS as an inconsistent requirement that the frequency be both above 20 Hz and below 10 Hz All DCONxxx bulk data entries such as DCONTHK that do not have SETID fields will be applied to the model in combination with set selectable constraints to make up the set of design constraints Additionally the DCFUNCTION option may be used to select functional constaints that are applied to the MODES responses from the current solution In ASTROS each eigenvector is consi
378. mark 3 CTYPE Constraint type either LOWER for lower bound or UPPER for upper bound Character AREO Buckling constraint value Real Default 1 0 RSQR Parameters which define inertia linking when ETYPE is the ROD element ALPHA Real or blank See Remark 4 Remarks 1 Buckling constraints are selected in Solution Control with the discipline option DCON sid 2 If the LENGTH is omitted the corresponding value will be computed from the length of the control element ASTROS THE BULK DATA PACKET 7 69 DCONBKE 3 The boundary condition types are defined in the following table BCTYPE Boundary Condition PIN PIN Pin connected at both ends PIN FIX Pinned at one end fixed at the other FIX FIX Fixed at both ends FREE COL A free column one end fixed the other free Only PIN PIN May be used for a ROD element while all types may apply to the BAR 4 Theinertia is computed from the relation I RSOR x AREA HA USER S MANUAL where AREA is the area of the control element If not specified a solid circular cross section is assumed 7 70 THE BULK DATA PACKET ASTROS USER S MANUAL DCONCLA Input Data Entry DCONCLA Description Defines a flexible lift curve slope constraint of the form CLA lt CLAREQ or CLA gt CLAREQ where CI wf CLA Ci ar Format and Example 1 2 3
379. mation are specified in the solution control through the FSTEP and DLOAD options This discipline has no associated constraints and while it is fully supported in the OPTIMIZE Subpacket it will not generate data for use in the redesign task There are two additional options which can be selected in frequency response analysis These are 1 Fast Fourier Transform techniques which are selected with the FFT option and 2 harmonic gust loads which are applied using the GUST option In each case the solution control option points to a bulk data entry having the same name In addition the K2PP B2PP M2PP TFL and DAMPING options may be used with or without an ASTROS THE SOLUTION CONTROL PACKET 5 13 USER S MANUAL ESET Boundary Condition option to impose a case by case set of additional inputs degrees of freedom for modelling control systems etc In ASTROS each frequency step for which output is saved is considered to be a separate subcase It is important to note that like the MODES discipline more than one subcase is represented by a single solution control discipline statement In output requests therefore the subcases for which output is desired must be explicitly selected This is presented in greater detail in Subsection 5 4 and in Chapter 6 5 4 OUTPUT REQUESTS Most analysis disciplines in ASTROS have response quantities displacements stresses strains etc computed at either grid points structural elements or aerodynamic elem
380. may use a GOTO statement to jump ahead in the standard sequence to the restart point or the user may use the EDIT commands to delete those initial sections that no longer need execution The latter is typically the case when the preface segment is saved for restart If the user deletes lines care should be taken not to delete half of a looping construct or block IF since that will result in a MAPOL compilation error The restart MAPOL sequence must also contain any new statements that are required to reset values of MAPOL scalar parameters 4 4 4 3 Resetting MAPOL Parameters In the ASTROS system all the values of MAPOL variables are stored on the database For the complex data types like RELATIONS and MATRICES this is obvious since their data resides on the database for ASTROS THE EXECUTIVE SYSTEM AND MAPOL 4 23 USER S MANUAL eSHELL execution or other processing Less obviously the simple data types like REAL and INTEGER including arrays are also saved on the database These data are not easily viewed in the eSEHLL context but are saved in a way that the MAPOL compiler can recognize When a restart job is performed the existence of these old data causes the MAPOL compiler to determine the correspondence between the original data and the new MAPOL sequence Whenever a variable of the same name and type is found its initial value is recovered from the old data thus restoring the value of the original variable to the last value it cont
381. means N 1 elements spread over the range of the shape function e g span or chord where N is the order of the shape N 0 UNIFORM N 1 LINEAR etc ASTROS THE BULK DATA PACKET 7 95 DCONTHK USER S MANUAL Input Data Entry DCONTHK Thickness constraints on elements Description Defines a list of elements linked using SHAPE entries for which thickness constraints are to be retained on all design iterations Format and Example 1 2 3 4 5 6 7 8 9 10 DCONTHK ETYPE EID EID EID EID EID EID EID CONT CONT EID EID ete DCONTHK ODMEM1 100 101 200 205 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONTHK ETYPE EID THRU EID Field Contents ETYPE Character input identifying the element type One of the following BAR QUAD4 CONM2 ROD ELAS SHEAR MASS TRIA3 QDMEM1 TRMEM EID Element identification number Integer gt 0 or blank Remarks 1 The purpose of this bulk data list is to ensure that adequate physical move limits are retained in optimization with shape function design variable linking without requiring retention of all move limits For problems with large numbers of local variables using shape functions the move limits often cause too many minimum thickness constraints see Remark 2 to be retained in the optimiza tion task Using this bulk data entry OR it
382. memory You may provide default values for this command in the lt computing Resources gt group of the AS TROS Section of the Preference File ASTROS has two high performance solvers which take advantage of the latest developments in sparse matrix algorithm technology The first of these is the symmetric matrix decomposition used in static analyses and the second is the Lanczos eigenextraction method This latter method is used for extracting a modest number of eigenvalues from very large systems When these solvers are used memory require ments may become significant The figures below give upper and lower bound estimates for the amount of ASTROS THE INPUT DATA STREAM 3 9 USER S MANUAL 100 1000 UPPER UPPER BOUND BOUND 100 4 LOWER BOUND MWords of Memory o bytes of Memory LOWER BOUND 1 rl l 10 100 1000 10 100 1000 DOF Thousands DOF Thousands Cray Others memory that you should specify on your MEMORY Command Although the eigensolver takes slightly more memory about 20 the same figures may be used to approximate the requirements for either solver Note that in the case of the Linear Solver if you do not specify enough memory for the new algorithm the program will revert to the old solution algorithm This is not the case for Lanczos the job will terminate These curves have been created using a representative sample of real analysis jobs Th
383. ment is constrained to zero 2 This single entry completely defines the element since no material or geometric properties are required The two connection points G1 C1 and G2 c2 must be distinct 4 The TMIN and TMAX values are ignored unless shape function design variable linking is used 7 36 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry CIHEX1 CIHEX1 Linear soparametric Hexahedron Element Connection Description Defines a linear isoparametric hexahedron element of the structural model Format and Example Jl 2 3 4 5 6 7 8 9 10 CIHEX1 EID PID G1 G2 G3 G4 G5 G6 CONT CONT G7 G8 CIHEX1 137 5 3 8 5 4 9 14 ABC BC 88 602 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PIHEX property entry Integer gt 0 Default is EID Gi Grid point identification numbers of connection points Integer gt 0 G1 G2 G8 Remarks 1 Grid points G1 G2 G3 and G4 must be given in counterclockwise order about one quadrilateral face when viewed from within the element Grid points G5 G6 G7 and G8 must also be given in counter clockwise order and G1 and G5 must be along the same edge as shown in the figure below There is no nonstructural mass The quadrilateral faces need not be planar Stresses are given in the basic coordinate system The continuation is required Anu FW N
384. moment must be supported in the boundary condition For example to constrain the pitching moment QACCEL due to angle of attack ALPHA the y rotation of the support point must be on the SUPPORT entry for the boundary condition in which the TRIM is analyzed 5 The stability derivatives are nondimensional quantities derived from the flexible forces and moments due to unit parameters The constraint is applied to the nondimensional derivative at the user de ASTROS THE BULK DATA PACKET 7 89 DCONSCF USER S MANUAL fined reference point To assist the defining PRMREQ the following normalizations are used in AS TROS CONTROL TESSE stability coeff F QDP S SURFACES FORCE y ORCES stability coeff F 2 VO QDP S C RATES unit rate unit dimensional SYMMETRIC rate C 2 VO stability coeff M QDP S C SURFACES MOMENTS stability coeff M 4 VO QDP S C 2 RATES i y i unit rate unit dimensional rate C 2 VO CONTROL aod f stability coeff F QDP S SURFACES FORCES 3 stability coeff F 2 VO QDP S B RATES unit rate unit dimensional ANTISYMMETRIC rate B 2 VO stability coeff M QDP S B SURFACES MOMENTS stability coeff M 4 V Bxx2 RATES O ODE S i unit rate unit dimensional rate B 2 VO F and M are the dimensional flexible forces and
385. mples of user input are used throughout this document In order to ease the burden of interpre tation the conventions shown in Table 1 1 are used in the examples unless otherwise noted Chapter 7 which describes the MAPOL programming interface describes additional conventions required for the programming syntax of MAPOL Table 1 1 Command Syntax Conventions MAPOL NOGO Capital letters indicate that the phrase must appear exactly as shown MAPOL params Lower case italic symbols act as generic place holders indicating that an option or options can or must be included GO MAPOL woco Symbol s enclosed in brackets are optional If more than one symbol is available they will be stacked in vector notation with any defaults denoted by boldface INCLUDE lt filename gt A required symbol is enclosed in angle brackets If the angle brackets surround an option list at least one of the available options must be selected BEGIN_BULK The underscore _ is used to signify a required blank space ASTROS INTRODUCTION 1 3 USER S MANUAL This pageis intentionally blank 1 4 INTRODUCTION ASTROS USER S MANUAL Chapter 2 RUNNING ASTROS As is the case with all major software systems that are available across a broad spectrum of host computers and operating systems ASTROS has features which are implemented differently on different computers The most common differe
386. ms Therefore many of the input and output features are similar NASTRAN has become an industry standard in finite element structural analysis with many pre and post processors developed around NASTRAN data To maintain maximal compatibil ity many aspects of the ASTROS input are similar in form or purpose to those in NASTRAN and in many other cases the same nomenclature has been adopted In some instances in this document there fore ASTROS input will be compared and contrasted to NASTRAN input in order to present a concise picture of the ASTROS input and to assist the reader familiar with NASTRAN in making the connection to the equivalent item in ASTROS Although familiarity with NASTRAN is not a prerequisite to under standing the ASTROS documentation sufficient numbers of potential ASTROS users are expected to be familiar with the NASTRAN system to justify the sometimes casual reference to NASTRAN features Chapter 1 contains a description of the ASTROS input file database assignment and debug control inputs Chapters 2 through 5 are organized to parallel the input file structure Within each of these chapters the function of the particular input packet is presented along with illustrations of how the data are prepared Each packet is described in a generic fashion so as to indicate how the sophisticated user can make use of the more advanced features of the system without cluttering the discussion with details of the input structures The detai
387. n artifact from using physical cards that were punched with the bulk data If the card deck were dropped the resulting random order still had to be interpretable by the code This feature no longer needs to be supported in light of modern computer storage methods but NASTRAN compatibility dictated that similar continuation labeling be used A continuation line is defined for a bulk data entry that requires more than eight or four large data fields The last field of the parent line is used in conjunction with the first field of the continuation line as Small Field Entry with a Small Field Continuation NAME ABC BC Small Field Entry with a Large Field Continuation NAME ABC BC Large Field Entry with both Large and Small Field Continuations NAME ABC BE DEF EF Large Field Entry with a Large Field Continuation NAME ABC BC Figure 7 1 Bulk Data Entry Formats ASTROS THE BULK DATA PACKET 7 3 USER S MANUAL an identifier The parent continuation field can contain any alphanumeric entry while the first field of the continuation line contains a plus as a continuation character in column 1 followed by the last 7 characters from the parent continuation label For the parent line the large field marker is an asterisk following the name of th
388. n certain elements MCSID Material Coordinate System identification number Integer gt 0 or blank Remarks 1 The material identification number must be unique for all MAT1 MAT2 MAT8 and MAT9 bulk data entries 2 Themass density RHO will be used to automatically compute mass for all structural elements 3 Weight density may be used in Field 6 if the value 1 g is entered on the CONVERT entry where g is the acceleration of gravity 4 Either E or G must be specified i e nonblank If any one of E G or NU is blank it will be computed to satisfy the identity E otherwise values supplied by the user will be used 2 1 NU G 6 IfEandNU or G and NU are both blank they will both be given the values 0 0 Implausible data on one or more MAT1 entries will result in a warning message mplausible data is defined as any of E lt 0 0 or G lt 0 0 or NU gt 0 5 or NU lt 0 0 or 1 E 2 1 NU G gt 0 01 except for cases covered by Remark 6 8 It is strongly recommended that only two of the three values E G and Nu be input The three values may be input independently on the MAT2 entry 7 156 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description MAT2 als for two dimensional elements Format and Example Material Property Definition Form 2 MAT2 Defines the material properties for linear temperature independent anisotropic materi
389. n constraint in the Bulk Data Packet The Bulk Data Packet then links the design constraint to the Functional Packet and the Function Packet defines the function specifications Example 1 Displaced Coordinate Limit The following example computes four constraints for the displaced coordinate x for a set of four grid points assuming that xoLD and T1 are in the same coordinate system First the Solution Control packet references the functional design constraint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY SPC 1 STATICS DCFUNCTION 101 The Function Packet defines the function specification for computing the allowable displaced coordinates The general expression for the F unction packet is XNEW XOLD T1 for grids 5 10 15 20 This expression is then coded in the F unction packet as FUNCTIONS Location of the X coordinate for the supplied Grid list XOLD GLIST COORD GLIST X1 Location of the displaced coordinate XNEW GLIST XOLD GLIST DISP GLIST T1 Constraint for the displaced coordinate CONST GLIST ALLOW XNEW GRIDLIST GLIST ALLOW ENDFUNC 6 14 THE FUNCTION PACKET USER S MANUAL USER S MANUAL The Bulk Data Packet defines the grid list glist and arguments for constraint set 101 The constraint set links the design constraint CoNsT to the Functional Packet and defines two arguments The first
390. n number Integer gt 0 DLAGID Identification number of DLAGS set which defines A and 1 Integer gt 0 TID Identification number of a TABLED1 entry which gives F t t Integer gt 0 Remarks 1 SID must be unique for all TLOAD1 TLOAD2 RLOAD1 and RLOAD2 entries 7 232 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry TLOAD2 TLOAD2 Description Defines a time dependent dynamic load of the form 0 when t lt O or t gt t2 t1 PO atPeotcos 2net 0 when O lt t lt t2 t1 where t t t1 1 Format and Examples 1 2 3 4 5 6 7 8 9 10 TLOAD2 SID DLAGID T1 T2 FREQ PHASE CTEXP GROWTH TLOAD2 10 6 2d 4 7 12 0 30 0 20 3 0 Field Contents SID Set identification number Integer gt 0 DLAGID Identification number of the DLacs entry set which define the time invariant load A and the time delay Integer gt 0 T1 Time constant Real gt 0 0 T2 Time constant Real T2 gt T1 FREQ Frequency in cycles per unit time Real gt 0 0 PHASE Phase angle in degrees Real CTEXP Exponential coefficient Real GROWTH Growth coefficient Real Remarks 1 TLOAD2 loads may be combined with TLOAD1 loads only by specification on a DLOAD entry 2 SID must be unique for all TLOAD1 TLOAD2 RLOAD1 and RLOAD2 entries ASTROS THE BULK DATA PACKET 7 233 TRIM USER S MANUAL Input Data Entry TRIM Trim Variable Specification Description Spec
391. n the ASTROS host computer 9 2 3 2 Data Type REAL REAL data represents floating point numbers Such numbers include 1 75 0 00025 1 78E 6 and 3 00271E 36 REAL numbers are represented in a manner determined by the machine precision of the 9 6 MAPOL PROGRAMMING ASTROS USER S MANUAL host computer automatically MAPOL therefore does not distinguish between the REAL and DOUBLE PRECISION types such as is found in Fortran 9 2 3 3 Data Type COMPLEX COMPLEX numbers are those which may be represented in the form Because some host computers automatically handle COMPLEX data while others do not MAPOL and ASTROS handle such data in a manner totally independent of the host computer In the ASTROS machine both a and b are represented as a pair of machine precision floating point numbers Most available mathematical functions operate on COMPLEX data 9 2 3 4 Data Type LOGICAL LOGICAL variables have a value of true or false The ASTROS machine represents true by the Fortran TRUE and false by the Fortran value FALSE Logical constants may only be used in assignment statements 9 2 3 5 Data Type LABEL LABELS are used to define statement locations within a MAPOL program Typically they are only used with the Goto statement see Section 9 4 ASTROS MAPOL PROGRAMMING 9 7 USER S MANUAL 9 2 4 COMPLEX DATA TYPES To best support comprehensive engineering analysis capabilities MAPOL supports five complex or high level
392. n the CONVERT entry 4 Continuation number 4 need not be used The subscripts 1 through 6 refer to x y Z Xy yz zX for example Hm Pp G G p N 22 23 G Go G3 15 G35 6 Gs G3 000000 EG 16 26 SYM 3 44 000 D 4 5745 Ges 6 6 G56 Ge 6 The damping coefficient GE is C GE 2 Co 7 160 THE BULK DATA PACKET m m a E A N lt N NS bad t T T ASTROS USER S MANUAL MFORM Input Data Entry MFORM Mass Matrix Form Description Defines the form of the mass matrix as consistent coupled or lumped Format and Example 1 2 3 4 6 5 7 8 9 10 MFORM VALUE MFORM LUMPED Field Contents VALUE A character string denoting the form of the mass matrix The available forms are 1 LUMPED 2 COUPLED Remarks 1 If more than one MFORM is included in the Bulk Data any COUPLED value will result in coupled mass being used 2 If noMFORM is indicated the LUMPED formulation will be used ASTROS THE BULK DATA PACKET 7 161 Input Data Entry MKAERO1 Mach Number Frequency Table Provides a table of Mach numbers m and reduced frequencies k for unsteady aerody Description namic matrix calculation Format and Example 1 2 3 4 5 6 7 8 9 10 MKAERO1 SYMXZ SYMXY mi m2 m3 m4 ms m6 CONT CONT k1 k2 k3
393. nces are in the way you execute ASTROS and other UAI software products the management of dynamic memory and the manner in which files are handled during execution This Chapter describes these for the most commonly used operating systems Tall computer models and operating system names are trademarks of their respective manufacturers and vendors ASTROS RUNNING ASTROS 2 1 USER S MANUAL 2 1 0VERVIEW This section provides you with an overview of the areas of ASTROS that are directly affected by your host computer and its operating system 2 1 1 Executing ASTROS The manner in which you invoke a ASTROS execution is completely dependent on the operating system of your host computer Subsequent sections of this chapter describe this operation for the most common host computers upon which ASTROS is currently available You will note that Section 2 2 includes all of the host computers using the Unix operating system and its derivatives 2 1 2 The ASTROS Configuration and Preference Files In general UAI s suite of engineering software products uses computing resources intensively As a result there are a number of parameters that must be set to achieve optimal resource management on a given host computer These parameters taken as a group are called the Configuration of the products The configuration is provided through one or more files These files include parameters which are used for controlling database locations physical file chara
394. nch file SORT Sorted echo to both output and punch files BOTH unsort Unsorted echo to both output and punch files NOECHO No echo to either output or punch file 7 2 THE BULK DATA PACKET ASTROS USER S MANUAL 7 2 FORMAT OF THE BULK DATA ENTRY Each bulk data entry consists of a required parent line followed by a number of optional continuation lines Therefore a single bulk data entry resides on one or more lines The basic bulk data line has one mnemonic field of eight characters followed by either eight data fields of eight characters or by four data fields of 16 characters and terminates with an eight character continuation field as shown in Figure 7 1 The data field size either eight or 16 characters is determined by the presence of the optional large field marker in the first mnemonic field of each bulk data line The parent line begins with a character mnemonic identifying the entry followed by 4 or 8 data fields and ending with a continuation field The continuation lines are identical except that the leading mnemonic field contains a continuation label which is used to link it to its parent line This structure is identical to that in NASTRAN One important exception to NASTRAN compatibility is that ASTROS requires that the continuation lines follow continu ously from the parent line although the bulk data entries themselves can be in any order Random placement of continuations in NASTRAN is a
395. nd Example 1 2 3 4 5 6 7 8 10 EIGC SID METHOD NORM G E CONT CONT PAL QA1 PB1 QB1 w1 El ND1 CONT CONT PA2 QA2 PB2 QB2 W2 E2 ND2 EIGC 14 INV POINT 27 8 ABC BC 2 0 3 6 2 0 3 4 2 0 4 4 DEF EF 5 5 5 5 5 6 5 6 1 5 6 3 Field Contents SID Set identification number Unique integer gt 0 METHOD Method of complex eigenvalue extraction one of the strings INV or HESS INV Inverse power method HESS Upper Hessenberg method NORM Method for normalizing eigenvectors one of the strings MAX or POINT MAX Normalize to a unit value for the real part and a zero value for the imaginary part the component having the largest magnitude POINT Normalize to unit value of the component G c defaults to Max if point is not defined G Grid or scalar point identification number Required if and only if NORM POINT Integer gt 0 Cc Component number Required if and only if NoRM POINT and G is a geometric grid point 0 lt Integer lt 6 E Convergence test Real Default 10 PAi QAi Two complex points defining a line in the complex plane Real PBi QBi W Width of region in complex plane Real gt 0 NEi Estimated number of roots in each region Integer gt 0 NDi Desired number of roots in each region Default is 3 NEi Integer gt 0 7 118 THE BULK DATA PACKET ASTROS USER S MANUAL EIGC Remarks 1 The SID may be called out directly in the CEIG module call or may be entered via the Solution Control CMETHOD in the BO
396. neering modules themselves In addition you can write special purpose modules and define them to the compiler through the SYSTEM GENERATION SYSGEN program discussed in the Programmer s Manual Thus a wide range of tasks can be performed using the ASTROS system in combination with a MAPOL program 4 2 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL The MAPOL language can be read and written easily by anyone familiar with a scientific programming language This feature opens the advantages of the executive system to the average user without requir ing specialized knowledge in computer science or requiring effort to learn a radically different program ming language Y ou will often find the simplicity and power of the MAPOL language enables many tasks to be performed using the ASTROS system that are not explicitly supported in the standard executive sequence 4 2 MAPOL EDIT COMMANDS If the MAPOL packet begins with the EDIT command line the compiler assumes that the remainder of the packet if any is composed of MAPOL edit commands and new MAPOL statements that modify the standard executive sequence The set of edit commands is given in Table 4 1 They allow you to insert delete and replace lines of the standard MAPOL sequence All of the edit commands reference a line number or range of line numbers The line numbers are those in a compiled listing of the standard MAPOL sequence which is written as part of the system generation task
397. nexistent global design variables may be referenced and will result in no error message 4 Any number of continuations is allowed except when using the alternate form which allows no continuations 7 140 THE BULK DATA PACKET ASTROS USER S MANUAL GENEL Input Data Entry GENEL General Element Description Defines a general element of the structural model by a stiffness or flexibility matrix Format and Example T 2 3 4 5 6 7 8 9 10 GENEL EID GIDI1 DOFI1 GIDI2 DOFI2 GIDI3 DOFI3 CONT CONT GIDI4 DOFI4 CONTINUES IN GROUPS OF 2 CONT CONT UD GIDD1 DOFD1 GIDD2 DOFD2 GIDD3 DOFD3 CONT CONT GIDD4 DOFD4 CONTINUES IN GROUPS OF 2 CONT CONT RUIZ K11 K21 K31 e K22 K32 K42 CONT CONT TF K33 K43 K53 CONTINUES WITH LIST OF TERMS CONT CONT gr s11 12 13 14 oe 21 S22 CONT CONT S23 Ral 31 32 CONTINUES WITH LIST OF TERMS CONT GENEL 3000 3 1 3 2 3 6 G31 G31 UD 4 1 4 2 4 6 G32 G32 K 6 0 0 0 0 0 6 0 3 0 2 0 G33 G33 S 1 0 0 0 0 0 0 0 1 0 1 0 0 0 G34 G34 0 0 1 0 Field Contents EID Element identification number See Remark 1 I nteger gt 0 Required GIDTi Grid or scalar point identification numbers of points in the uT list I nteger gt 0 Required DOFTi Single degree of freedom corresponding to the points GIDIi DOF Code Required
398. nimum and maximum allowable cross sectional areas in design Real gt 0 0 or blank Remarks 1 For structural problems CONROD entries may only reference MAT1 material entries 2 The continuation entry is optional 3 TMAX and TMIN are ignored unless element is linked to global design variable through a SHAPE entry ASTROS THE BULK DATA PACKET 7 49 CONVERT Input Data Entry CONVERT USER S MANUAL Description Defines conversion factors for various physical quantities Format and Example 1 2 3 4 5 6 7 8 9 10 CONVERT QUANT1 FACTOR QUANT2 FACTOR QUANT5 FACTOR QUANT4 FACTOR CONT CONT QUANT FACTOR QUANT FACTOR etc CONVERT MASS 0 00259 Field Contents QUANTi A character string identifying the physical quantity to be converted MASS Or VELOCITY FACTOR The conversion factor Real 0 0 Remarks 1 Any number of valid quantity factor combinations can be entered on a single entry 2 Only MASS and VELOCITY are currently valid quantity entries 3 Input mass values will be multiplied by the input factor Input velocities will be multiplied by the factor 7 50 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description CORD1C CORD1C Cylindrical Coordinate System Definition Form 1 Defines a cylindrical coordinate system by reference to three grid points These points must be defined in
399. nition THE BULK DATA PACKET 7 7 USER S MANUAL 7 5 6 Design Variables Linking and Optimization Parameters DESELM DESVAR DESVAR P S DVTOP DVTOP DVTOP ELIS ELIS PPAR PLIST PLIST SHAPE S HAPE SHPGEN 7 5 7 Geometry CORD1C L P CORD1R CORD1S CORD2C CORD2R CORD2S EPOI GRDSE GRID SPOINT Unique physical design variable definition Linked physical design variable definition Linked shape function design variable definition Thickness variation type definition for bending plate element design Thickness variation type definition for an element list Thickness variation type definition based on element properties Element list for physical linking Element list for physical linking of different local design variables Mathematical programming default parameter override Physical design variable linking definition Physical design variable linking of different local design variables Definition of element linking factors to define a shape variable Definition of element linking factors of different local design variables to define a shape variable Definition of design variables using the SHAPE generation utility Cylindrical coordinate system definition Rectangular coordinate system definition Spherical coordinate system definition Cylindrical coordinate system definition
400. nknowns in the trim analysis If TRMTYP is blank the number of SuPORT DOF 9 If TRIMID is referenced by an NPSAERO discipline TRMTYP must be blank and FREE is not allowed for VALUEi 10 For NX NY and Nz units are length per second in consistent units unless a CONVERT MASS Bulk Data entry is provided In this case the values are dimensionless 11 The angular accelerations QACCEL PACCEL and RACCEL are entered in units of radians per second per second 12 QRATE PRATE and RRATE are entered in units of radians per second The velocity must be input if any of the rate parameters are given since its value is needed to dimensionalize the forces computed for a unit rate per velocity in the aerodynamic preface 13 The THKCAM label refers to thickness and camber effects and its corresponding value is usually set to 1 0 Non unit values of the THKCAM parameter are available only to provide added generality 14 Any control surfaces trim parameters or structural accelerations not specified on the TRIM entry will not participate in the analysis they will be given fixed values of 0 0 This includes THKCAM 15 Refer tothe STATIC AEROELASTIC TRIM Application Note for more information 7 236 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry TSTEP TSTEP Description Defines time step intervals at which a solution will be generated and ou
401. nput Data Entry PELAS Scalar Elastic Property Description Used to define the stiffness damping coefficient and stress coefficient of a scalar elastic element spring defined by means of the CELAS1 entry Format and Example 1 2 3 4 5 6 7 8 9 10 PELAS PID K GE S TMIN PELAS 7 4 29 0 06 ASO Field Contents PID Property identification number Integer gt 0 K Elastic property value Real GE Damping coefficient Real gt 0 0 S Stress coefficient Real TMIN Minimum value for design Real gt 0 0 or blank Default 0 0001 Remarks 1 Theuser is cautioned to be careful using negative spring values 2 TMIN is ignored unless the element is designed using shape function design variable linking 7 188 THE BULK DATA PACKET ASTROS USER S MANUAL PIHEX Input Data Entry PIHEX soparametric Hexahedron Property Description Defines the properties of an isoparametric solid element including a material reference and the number of integration points Referenced by the CIHEX1 CIHEX2 and CIHEX3 entries Format and Examples 1 2 3 4 5 6 7 8 9 10 PIHEX PID MID CID NIP AR ALPHA BETA PIHEX 15 3 3 5 0 Field Contents PID Property identification number Integer gt 0 MID Material identification number Integer gt 0 CID Identification number of the coordinate system in which the material re
402. nput but S is omitted S is internally calculated In this case U must contain six and only six degrees of freedom The forms shown above for both the stiffness and flexibility approaches assume that the element is a free body whose rigid body motions are defined by U S Uy 7 142 THE BULK DATA PACKET ASTROS USER S MANUAL GPWG Input Data Entry GPWG Weight Generator Data Description Contains definition of the location about which to perform grid point weight generation Format and Example I 2 3 4 5 6 7 8 9 10 GPWG GID XO YO ZO GPWG 10 Field Contents GID Grid point identification of the GPWG reference point Integer X0 X component of basic coordinates of the reference point Real YO Y component of basic coordinates of the reference point Real ZO Z component of basic coordinates of the reference point Real Remarks 1 Either a grid point identification number or the basic x y Z components of the reference point may be given 2 If no GPWG data entry exists the grid point weight generation will be computed about the origin of the basic coordinate system 3 If more than one GPwG entry exists the first one appearing in the sorted bulk data echo will be used ASTROS THE BULK DATA PACKET 7 143 GRAV Input Data Entry Description GRAV Gravity Vector USER S MANUAL Used to define gravity vectors for use in determining gravity loading for the
403. ns and degrees E Ci Cy Yaw rate r in both radians and degrees an a Cn Roll rate p in both radians and degrees Cy E Cn User defined control surface deflection s 5 in both radians and degrees These nondimensional factors are implicitly defined in the following equations Side Force 35 C 8 G 4 fori 1 NANTI Roll Moment asb c aata wte 1 oll M omen q Moi ay o ori 1 NANTI Yaw Moment Sb C Cy Sy tu By ten 8 fori 1 aw Momen q ve N 2V Nay Ori 1 NANTI where b reference semispan NANTI The number of antisymmetric control surfaces These quantities are shown in three forms as shown in Table 8 24 1 The stability derivative for the rigid aerodynamic model as computed directly from the forces acting on the aerodynamic boxes termed DIRECT in the output This output al ways appears since it comes directly from the aerodynamic model 2 The stability derivative for the rigid aerodynamic model as computed from the forces transformed to the structural degrees of freedom termed SPLINEd in the output This output only appears if the associated DOF is SUPORTed 3 The flexible derivative which includes corrections for the flexibility and inertia relief ef fects This output only appears if the associated DOF is SuPoRTed ASTROS OUTPUT FEATURES 8 33 USER S MANUAL Table 8 24 Antisymmetric Trim Results 1SIMPLIFIED WING STRUCTURE DESIGN ASTROS VERSION 9 0 03 03 93
404. ns the definition of functions which allow the user to define new design constraints or an objective function These functions may combine nodal and element response quantities for various boundary conditions and disciplines The final ASTROS THE INPUT DATA STREAM 3 1 USER S MANUAL Any number of leading blank lines The Resource Section ASSIGN RUNDB lt name gt lt status gt lt PASSWORD password gt params MEMORY DEBUG DEBUG directives used for tracing input stream errors MAPOL option list or EDIT option list TASSA MAPOL program or EDIT commands allow user SS modifications to the standard ASTROS solution sequence SOLUTION Solution Control Directives _ select optimization and analysis disciplines FUNCTIONS option_list TOO Function definitions Tee Used to define objective or constraint functions BEGIN_BULK option_list A Bulk Data Entries A defines the structural and aero models boundary conditions loading cases and other engineering data and the design model design variables and constraints required when performing design Similar to NASTRAN ENDDATA Bulk Data Terminator Figure 3 1 Structure of the ASTROS Input Data Stream 3 2 THE INPUT DATA STREAM ASTROS USER S MANUAL ASTROS ASSIGN RUNDB TENBAR NEW REALLOC PASSWORD SHAZAM DEBUG DESIGN 5 EDIT No uist INSERT 146
405. nstraints retained of the total number applied This number is computed even if the current design is considered to be the converged optimum A summary of the convergence criteria and of the critical constraint value is included in the Active Constraint Summary header illustrated in Table 8 5 if the approximate problem was considered converged following the preceding redesign step Each redesign step is summarized in a small table shown in Table 8 6 entitled the Approximate Optimization Summary It indicates the optimization method used in resizing and the changes in three measures of convergence The first measure is the change in the value of the objective function during the solution of the approximate optimization problem The second is the change in the Euclidean norm of the design variable vector and finally the maximum absolute changein any component of the design variable vector Each of the values are computed as an absolute change and a percentage change These values are then printed You may compare the first two percentage values against your input convergence limit denoted UPPER BOUND PERCENT MOVE to determine which if either is greater than the limit If either 8 2 OUTPUT FEATURES ASTROS USER S MANUAL Table 8 1 DEBUG and ASSIGN DATABASE Output AUTOMATED STRUCTURAL OPTIMIZATION SYSTEM kkkkk kkkkk kkkkk kkkkk AR AR o ok x o x kkkkk O KARA es ko o kkkk ok ko o kkkk a eee ees VERSIO
406. nt such as Unix then the correct case must always be used in file names The section of the ASTROS input data steam that appears before the first packet header e g DEBUG EDIT Or SOLUTION is called the Resource Section This section may contain any number of ASSIGN commands and a MEMORY command The INCLUDE command is used only as a convenience These are discussed in detail in the following sections 3 4 THE INPUT DATA STREAM ASTROS USER S MANUAL 3 2 THE RESOURCE COMMANDS As introduced earlier there are two commands that may appear in the Resource Section One or more ASSIGN commands and an optional MEMORY command These are described in the following sections 3 2 1 THE ASSIGN COMMAND The ASSIGN command identifies the run time database files to be used in the current ASTROS execution and specifies certain parameters associated with the files The format of this command is ASSIGN logical_name phys_name d PASSWORD pass IBLKSIZE nwib DBLKSIZE READ ESS WRITE params ADMIN where dbname is a name identifying the run time database files maximum of 8 characters or fewer depending on the local host password Passwords are used but they are not required only when USE iS RUNDB ARCHIVE SOF Or NLDB For databases with a STATUS of NEW the same password is used for the READ WRITE and ADMIN privileges The eSHELL commana SET PASSWORD may be used to change any or all
407. nteger gt 0 CNA Independent degrees of freedom in the global coordinate system for the elements at CNB grid point GA and GB Indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 or blank Remark 2 CMA Component numbers of dependent degrees of freedom in the global coordinate system CMB assigned by the element at grid point Ga and GB Indicated by any of the digits 1 through 6 with no embedded blanks Integer gt 0 or blank Remarks 3 and 4 Remarks 1 The RBAR entry is selected in the Solution Control with the MPC SETID option of the BOUNDARY command THIS IS AN ENHANCEMENT TO THE NASTRAN METHOD WHICH DOES NOT ALLOW RIGID CONNECTIONS TO BE CHANGED FOR DIFFERENT BOUNDARY CONDI TIONS The total number of components in CNA and CNB must be six for example CNA 1236 CNB 34 The components must jointly be capable of representing any general rigid body motion of the element 3 If both cma and cme are zero or blank all of the degrees of freedom not in CNA and CNB will be made dependent e they will be placed in the m set 4 The m set degrees of freedom specified on this entry may not be specified on other entries that define 7 204 THE BULK DATA PACKET mutually exclusive sets Rigid element identification numbers must be unique within each element type for each MPC set identification number ASTROS
408. ntries are present all degrees of freedom not otherwise constrained will be placed in the o set The o set is a mutually exclusive set Degrees of freedom may not be specified on other entries that define mutually exdusive sets 2 Ifthe alternate form is used all points in the sequence ID1 through 1D2 are required to exist 3 ASET1 entries must be selected in Solution Control REDUCE SETID to be used ASTROS THE BULK DATA PACKET 7 23 ATTACH USER S MANUAL Input Data Entry ATTACH Description Defines the aerodynamic control points to be attached to a reference grid for load transfer Format and Example 1 2 3 4 5 6 7 8 9 10 ATTACH EID MACROID BOX1 BOX2 RGRID ATTACH 100 111 111 118 1 Field Contents EID Element identification number Integer gt 0 ACROID Element identification of a CAEROi Or PAEROi element which contains the specified aerodynamic control points Integer gt 0 BOX1 BOX2 Starting and final box whose force is to be transferred to the referenced grid Integer gt 0 BOX2 gt BOX1 RGRID Grid point identification of reference grid point Integer gt 0 Remarks 1 The EID is used only for error messages 2 This entry applies to both the steady and unsteady aerodynamic models 3 The attached aerodynamic boxes are selected as shown below 7 24 THE BULK DATA PACKET ASTROS USER S MANUAL AXSTA Input Data Entry AXSTA Descr
409. ntroid of the requested one dimensional two dimensional and three dimensional element in the coordinate system cid The WEIGHT function returns the weight of the element selected and the mass function returns the mass of the element selected The element is referenced either by an element identification eid or an element list ELEMLIST If an element identification number is used then the eid must be unique If element identification numbers are not unique then an element list must be used If the cid reference is omitted or is 0 then the coordinate is returned in the basic coordinate system Otherwise it is returned in the specified coordinate system Composite elements must have their layer numbers specified by a layer number plyid or a layer list PLYLIST The PLYLIST is not required for non composite elements and if present it is ignored 6 8 THE FUNCTION PACKET USER S MANUAL USER S MANUAL 6 3 2 4 Grid Point Response Functions The grid point response function is defined by DISP gid id caseid GRIDLIST grid_sid pE CASELIST case_sid where DISP represents displacements This function allows the current grid result values in the coordi nate system cid of a component T1 T2 T3 R1 R2 or R3 for the requested grid points defined either by its value gia or a grid point list GRIDLIST to be retrieved in the requested CASE value or list If the subcase reference is omitted then the specific discipl
410. ntry used to specify the velocity value ASTROS THE FUNCTION PACKET 6 31 FDAMP USER S MANUAL caseid Subcase identification case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number Notes 1 When the component GAMMA is specified the following equation is used R e p _ for complex Im p pane Y Re p f n for real p When the component ZETA is specified the following equation is used 2 Y C READ Re p 2 for complex p Imp 2 The specific discipline request defines whether the case and or mode is a valid request in the response functions 3 If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 32 THE FUNCTION PACKET USER S MANUAL USER S MANUAL FFREQ Intrinsic Function FFREQ Purpose Toretrieve the current value of the flutter frequency Usage FFREQ machop densop modeop velop caseop where A mvalue SS MACHLIST mach_sid Jet dvalue Fee DENSLIST dens_sid modeid gee ee MODELIST mode_sid 1 vvalue s m VELOLIST vel_sid BN caseid ARES CASELIST case_sid Function Arguments mvalue Mach value mach_sid Set identification of a MACHLIST bulk data entry used to specify the mach value dvalue Density ratio value dens_sid Set identification of a DENSLIST bulk data entry used to specify the density ratio value modeid Mode index mode_si
411. of all move limits For problems with large numbers of local variables using shape functions the move limits often cause too many minimum thickness constraints see Remark 3 to be retained in the optimiza tion task Using this bulk data entry to name critical minimum gauge constraints see Remark 4 will cause only the named elements thickness constraints to be computed and retained Note that all thickness constraints for an element will always be computed irrespective of the DCONTH3 entries but may be deleted in the constraint deletion The global design variable in shape function linking is non physical and no reasonable restriction for a global variable move limit side constraint can be defined Therefore constraints on the local design variables controlled by shape functions are generated by ASTROS to ensure that the design is reasonable The global design variable in shape function linking is non physical and no reasonable restriction for a global variable move limit side constraint can be defined Therefore constraints on the local design variables controlled by shape functions are generated by ASTROS to ensure that the design is reasonable ie nonnegative thicknesses The DCONTH2 entry should select a minimum number of elements linked to shape functions that will enable the optimizer to select physically reasonable designs without retaining all the minimum thickness constraints potentially a very large number Typically this
412. of an attribute within a relation may be modified if an assignment is made and then the entry is written onto CADDB refer to Chapter 9 8 9 2 4 3 Data Types UNSTRUCT and IUNSTRUCT The simplest CADDB data structure is called an UNSTRUCTUFed entity The form and content of such an entity is the responsibility of the ASTROS programmer The only use of the UNSTRUCT entity is for inter module communications UNSTRUCT entities which may not be subscripted are declared with lt decl gt UNSTRUCT lt un list gt lt un list gt lt un list gt lt un var gt lt un var gt lt un var gt lt ident gt 9 2 4 4 Data Base Entity Declaration Requirements All of the ASTROS database entities may be divided into three classes 1 MAPOL entities 2 HIDDEN entities and 3 TEMPORARY entities MAPOL entities are those that are used and appear in the MAPOL program such as matrices or relations used in calculations and any entity appearing as an argument in a functional module call HIDDEN entities represent data that are used by a functional module but whose contents are generated from required physical data As an example the GRID Bulk Data are stored in a relation called GRID Many modules might wish to access this GRID data Requiring 9 10 MAPOL PROGRAMMING ASTROS USER S MANUAL the GRID relation to appear in the calling list of each such module is more disruptive than it is beneficial As a result GRID might never explicitly
413. oint identification number Integer gt 0 Remarks 1 Coordinates specified on this entry form members of a mutually exclusive set They may not be specified on other entries that define mutually exclusive sets 2 If the alternate form is used points in the sequence 1D1 through ID2 are required to exist and 1D2 must be greater than or equal to ID1 ASTROS THE BULK DATA PACKET 7 173 PAERO1 USER S MANUAL Input Data Entry PAERO1 Aerodynamic Panel Property Description Gives associated bodies for the panels in the unsteady aerodynamic model Format and Examples 1 2 3 4 5 6 7 8 9 10 PAERO1 PID B1 B2 B3 B4 B5 B6 PAERO1 1 3 Field Contents PID Property identification number referenced by CAERO1 Integer gt 0 Bi Identification number of CAERO2 entries for associated bodies Integer gt O or blank Remarks 1 The associated bodies must be in the same aerodynamic group 2 TheBi numbers above must appear on a CAERO2 entry to define these bodies completely 7 174 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry PAERO2 PAERO2 Aerodynamic Body Properties Description Defines the cross section properties of unsteady aerodynamic bodies Format and Examples I 2 3 4 5 6 7 8 9 10 PAERO2 PID ORIENT WIDTH AR LRSB LRIB LTH1 LTH2 CONT CONT THI1 THN1 THI2 THN2 THI3
414. omposite elements must have their layer number specified ASTROS THE FUNCTION PACKET 6 47 TRIM USER S MANUAL Intrinsic Function TRIM Purpose Toretrieve trim parameters from a Static Aerodynamics analysis Usage caseid TRIM ee param CASELIST case_sid Function Arguments trim param Trim parameters caseid Subcase identification case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number Notes 1 This function return its results in radians If degrees are required the results may be converted using the DEGs intrinisic function 2 The allowable control surfaces trim_param are ALPHA BETA PRATE QRATE RRATE PACCEL QACCEL RACCEL trim_param User Surfaces The User Surfaces are defined using AESURF Bulk Data entries 3 If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 48 THE FUNCTION PACKET USER S MANUAL USER S MANUAL WEIGHT Intrinsic Function WEIGHT Purpose Toreturn the weight of selected elements Usage eid plyid ELEMLIST elem_sid PLYLIST ply_sid Function Arguments eid Identification of an element specified in the Bulk Data Packet elem_sid Set identification of an ELEMLIST bulk data entry used to specify an element plyid Identification of a layer number for a composite element ply_sid Set identification of a PLYLIST bulk data entry used
415. ompressive strain limit in the fiber direction Real Default EFT ETT Tensile strain limit in the transverse direction Real gt 0 0 ETC Compressive strain limit in the transverse direction Real Default ETT ETYPE Element type Character selected from QDMEM1 TRMEM QUAD4 TRIA3 LAYRNUM The layer number of a composite element Integer gt 0 or blank EIDi Element identification numbers Integer gt 0 Remarks 1 Strain constraints are selected in Solution Control with the discipline option STRAIN sid 2 Fiber transverse strain constraints may only be applied to elements defined using composite materials 3 If the alternate form is used EID2 must be greater than or equal to EID1 Elements in the range which do not exist are ignored 4 Thestrain limits for compression EFC and ETC are always treated as negative values regardless of the signs of the input values ASTROS THE BULK DATA PACKET 7 81 DCONFTM USER S MANUAL Input Data Entry DCONFTM Fiber Transverse Strain Constraint Definition Description Defines fiber transverse strain constraints for composite elements by specifying material identification numbers Format and Example ali 2 3 4 5 6 7 8 9 10 DCONF TM SID EFT EFC ETT ETC MID1 MID2 MID3 CONT CONT MID4 ID5 etc DCONF TM 100 162 lt 12 13 153 FE 16 101 ABC BC 19 14 Alternate Form
416. on number and if appropriate the layer number The linking option used to connect them to the global variables is also shown This print can be very helpful in checking the correctness of the design model Following these general data are the element dependent local variable value and the allowable range that the primary value can take Note that the BAR element links the moments of inertia to the cross sectional area so all three design variables are shown but the area is the only independent variable The local variable print accounts for all scalar factors that might appear in the design variable linking and therefore indicates the true physical values represented by the current design Finally the two dimensional elements include a print of the ratio of the current thickness to the minimum thickness This additional item is included as a convenience to allow a quick computa tion of the number of composite plys represented by a particular design if the user inputs the ply thickness as the minimum thickness and if the element has composite material properties The solution control print option DCONSTRAINT Selects that the active constraint summary print should include a table indicating which constraints are active their current value the constraint type and other identifying data connecting the constraints to a particular element subcase and or discipline Table 8 18 shows the DCONSTRAINT print in addition to the default ACTCON summary The identi
417. onal modification to the input definitions was made for the TABDMP1 entry to make it more compact and to remove the spurious ENDT table termination symbol In ASTROS all tabular input entries are terminated when no more data appears and require no specific declaration of the table end While a seemingly large number of bulk data entries have been changed relative to their NASTRAN counterparts in fact only a few have been changed in such a way that the NASTRAN version will not work in analysis By far the majority of the modeling bulk data entries are completely unchanged except for certain design variable linking options In unsteady and steady aerodynamic disciplines care must be taken to account for the subcase dependencies that NASTRAN defined implicitly or with PARAM entries Finally the use of ASET and OMIT entries will cause minor problems in that ASTROS requires a set identification for these entries While this latter restriction can require some effort to fix the gain in capability simply required that the bulk data entry be modified The most serious potential problem using NASTRAN models in ASTROS is that the set of bulk data entries is more limited in ASTROS than in NASTRAN The ASTROS system has been developed primar ily as a multidisciplinary preliminary design tool and does not yet contain the wide range of options supported by a mature code like NASTRAN The many NASTRAN input entries supporting these op tions therefore have not be
418. ond point defines the direction of the z axis The third lies in the plane of the azimuthal origin The reference coordinate system must be independently defined Format and Example I 2 3 4 5 6 7 8 9 10 CORD2S CID RID Al A2 A3 B1 B2 B3 CONT CONT c1 C2 C3 CORD2S 3 17 2 o 1 0 0 0 3 6 0 0 1 0 123 23 542 T O 2 i9 Field Contents CID Coordinate system identification number Integer gt 0 RID Reference to a coordinate system which is defined independently of of new coordinate system Integer gt O or blank Ai Bi Ci Coordinates of three points in coordinate system defined by RID Real Remarks 1 The continuation entry must be present 2 Thethree points A1 A2 A3 B1 B2 B3 C1 C2 C3 must be unique and noncollinear 3 Coordinate system identification numbers on all CORD1R CORD1C CORD1S CORD2R CORD2C and CORD2s entries must all be unique 4 An RID of zero references the basic coordinate system ASTROS THE BULK DATA PACKET 7 57 CORD2S USER S MANUAL 5 The location of a grid point P in the sketch in this coordinate system is given by R 6 q where 6 and q are measured in degrees 6 The displacement coordinate directions at P are shown above by u Up U 7 Points on the polar axis may not have their displacement directions defined in this coordinate system since an ambiguity results 0 7 58 THE BULK DATA PACKET ASTROS U
419. onsidered a flutter crossing See Remark 12 Real gt 0 Default 0 0 GFILTER The damping a mode must attain to be considered stable before a flutter crossing ASTROS See Remark 12 Real Default 0 0 THE BULK DATA PACKET 7 131 FLUTTER USER S MANUAL Remarks 1 10 11 The FLUTTER data entry must be selected in the Solution Control packet Only those Mach numbers and symmetries selected in Solution will be processed in the UNSTEADY aerodynamic preface When PK is selected Muller s method is used and when PKIT is selected the iterative method is used The density is given by p x P e where py is the reference value given on the AERO Bulk Data entry and p is the density ratio from the FLFACT entry If the MLIST is blank or zero all computed eigenvectors will be retained in the FLUTTER analysis If the KLIST is blank or zero all hard point k values those on the MKAERO entries associated with the Mach number symmetries on the FLUTTER entry will be used in the interpolation of the aerody namics Specifying a subset may be used to improve the ORIG interpolation Those MKAEROi hard point k values nearest in value to those listed on the FLFACT will be used No duplicate hard point k s will be used and no errors will be printed If the EFFID is blank or zero no effectiveness corrections will be made The symmetry flags are used to select the appropriate unsteady aerodynamic matrices generated from the list on
420. or ASTROS the Matrix Analysis Problem Oriented Language MAPOL has been developed to perform this executive system task The MAPOL language has its conceptual roots in the Direct Matrix Abstraction Program DMAP capability developed for the NASTRAN structural analy sis system Reference 2 MAPOL provides the same advantages to the ASTROS system and represents a considerable advance over DMAP in that MAPOL is a structured procedural language that directly supports high order matrix operations manipulation of database entities and complex data types More over the syntax of the language looks much like that of any scientific programming language and so is easily learned by anyone who knows FORTRAN or PASCAL From the user s point of view ASTROS is directed by a sequence of control statements coded in the MAPOL language just as a NASTRAN rigid format is coded in the DMAP language gt The majority of users will use the standard MAPOL sequence This is the default and as such it requires no special action Advanced users may optionally edit the standard sequence or write their own program The methods used to do this are described in this Chapter Because changes to the executive system arean advanced topic first time users may proceed directly to Chapter 4 The executive system within ASTROS compiles the MAPOL program and executes the resultant AS TROS machine code which directs the execution of the ASTROS procedure Note that AST
421. ottom plane ETYPE Element type Character selected from QUAD4 TRIA3 EIDi Element identification number Integer gt 0 Remarks 1 The thickness option for a selected element will be ignored if it is not a designed plate bending element 7 114 THE BULK DATA PACKET ASTROS USER S MANUAL DVTOPTL Input Data Entry DVTOPTL Type definition for designed element thickness variation Description Defines the thickness variation type for a designed element by specifying the element list set ID number Format and Examples 1 2 3 4 5 6 7 8 9 10 DVTOPTL TYPE ELID1 ELID2 ELID3 ELID4 ELID5 ELID6 ELID7 CONT CONT ELID8 ELID9 etc DVTOPTL TOP 10 99 999 Field Contents TYPE Designed element thickness variation type one of the character values CENTER TOP or BOTTOM Character default CENTER CENTER Element thickness varies about a fixed element reference plane TOP Element thickness varies about a fixed element top plane BOTTOM Element thickness varies about a fixed element bottom plane ELIDi Element list set identification number Integer gt 0 Remarks 1 Thethickness option for a selected element will be ignored if it is not a design bending element 2 Theelements in the specified list will be ignored if they are not QUAD4 or TRIA3 ASTROS THE BULK DATA PACKET 7 115 DVTOPTP USER S MANUAL Input
422. ould be dimensionless Angular accelerations should be in radians sec sec 4 A LOWER bound constraint excludes all values to the left of PRMREQ on a real number line while an UPPER bound excludes all values to the right irrespective of the sign of PRMREQ ASTROS THE BULK DATA PACKET 7 97 DCONTW USER S MANUAL Input Data Entry DCONTW Tsai Wu Stress Constraint Definition Description Defines Tsai Wu stress constraints by specifying the identification numbers of constrained de ments Format and Example 1 2 3 4 5 6 7 8 9 10 DCONTW SID XT XC YT YG SS F12 ETYPE CONT CONT LAYRNUM EID1 EID2 EID3 etc DCONTW 100 Let6 1 6 1 4 1 4 1 543 QUAD4 ABC BC 1 102 106 110 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONTW SID XT XC YT YC ss F12 ETYPE CONT CONT LAYRNUM EID1 THRU EID2 Field Contents SID Stress constraint set identification Integer gt 0 XT Tensile stress limit in the longitudinal direction Real gt 0 0 XC Compressive stress limit in the longitudinal direction Real Default xT YT Tensile stress limit in the transverse direction Real gt 0 0 YC Compressive stress limit in the transverse direction Real Default YT ss Shear stress limit for in plane stress Real gt 0 0 F12 Tsai Wu interaction term Real ETYPE Element type Character selected from
423. oundary condition NGDR BOUND Indicates if dynamic reduction is selected for the current boundary condition 4 10 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL Table 4 7 Logical Discipline Parameters NAME MODULES DESCRIPTION TRUE if the current boundary condition has any active aeroelastic effectiveness ACTAEFF ABOUND constraints TRUE if the current boundary condition has any active constraints associated with ACTAERO ABOUND SAERO analyses ACTBAR ABOUND TRUE if the current boundary condition has any active Euler buckling constraints ACTBOUND ABOUND TRUE if the current boundary condition has any active constraints ACTDYN ABOUND TRUE if the current boundary condition has any active frequency constraints ACTFLUT ABOUND TRUE if the current boundary condition has any active flutter constraints ACTPNL ABOUND TRUE if the current boundary condition has any active panel buckling constraints ACTUAG AROSNSDR TRUE if the current boundary condition has any active displacements or accelerations TRUE if the current boundary condition has any active displacement or stress constraint ACTUAGG MAKDFU sensitivities Logical array which indicates whether the current SAERO subscript value has aeroelastic AEF LG SAERO effectiveness constraints applied to it APPCNVRG DESTSH TRUE when the approximate problem was converged in a previous iteration ACTCON GLBCNVRG ACTCON TRUE when global
424. oundary condition The design of the ASTROS system requires that all optimization boundary conditions precede any analysis boundary conditions The analysis segment labeled the final analysis is intended to follow an optimization with analyses in disciplines whose output values are not constrained but are of interest to the designer or to provide the user with an opportunity to view additional output not desired within the optimization loop Also the analysis segment can be used on a stand alone basis to perform any desired analyses Both the optimization and analysis segments consist of an initial loop on the number of boundary conditions The analyses in these loops support all the disciplines currently available in the ASTROS system and differ only in the respect that the analysis segment does not have calls to constraint evalu ation modules and the optimization segment has convergence tests and design iteration initialization outside the analysis boundary condition loop The first step in these loops is to assemble the boundary condition dependent number of degrees of freedom extra points are BC selectable in ASTROS Then additional PFBULK like operations are performed in BCBULK to ensure that BC dependent user input is correct Then the global stiffness and or mass matrices are assembled and if needed the global loads matrix Following these tasks there are several BLOCK IF statements on the various dependent struc tural sets In executing each
425. oupling 4 Thecontinuation entry is not required The mID4 field should be left blank if the material properties are symmetric with respect to the middle surface of the shell 6 This entry is used only with the QUAD4 and TRIA3 elements 7 For structural problems PSHELL entries may reference MAT1 MAT2 Or MAT8 material property entries 8 If the transverse shear material MID3 references MAT2 data then G33 must be zero If MID3 references MAT8 data then G1 Z and G2 Zz must not be zero 9 IfMCSID SCSDID is left blank 0 0 or is real it is considered to be the angle of rotation of the X axis of the material stress coordinate system with respect to the X axis of the element coordinate system in the XY plane of the latter If Integer the orientation of the material stress x axis is along the projection of the x axis of the specified coordinate system onto the x y plane of the element system The value of MCSID is the default value for the Tm field on CQUADA4 Bulk Data entries 10 The offset zorr may also be provided on the CQUAD4 or CTRIA3 Bulk Data entry The element reference plane is located at the mid thickness of the element parallel to the element mean plane 11 TMIN is ignored unless element is linked to global design variables by SHAPE entries 12 The hierarchy of local coordinate systems is MCSID supplies the default value for the TM field on the element connectivity entry TM overrides MCSID if TMis not blank SCSID
426. output quantities but the reader is referred to Chapter 5 of this document for the in depth presentation of ASTROS output processing The hierarchical nature of solution control means that if the user enters a command at one level in the hierarchy it remains in effect at all subsequent levels at or below the current one unless overridden If it is overridden at the same level that overwrites the original command If on the other hand the command is overridden at a lower level it only supercedes the original command for the duration of that level and lower levels Solution Control reverts to use the higher level default after the lower level has been left Table 5 1 describes how the commands move from one level to the next and the defaults that they use in each Table 5 1 Levels of Solution Control INCREASING LEVELS DECREASING LEVELS CURRENT LEVEL IF USE THEN IF USE THEN IS COMMAND DEFAULTS MOVE COMMAND DEFAULTS MOVE IS FROM TO IS FROM TO LEVEL 1 ANALYZE Initial OPTIMIZE LEVEL 1 LEVEL 2 LEVEL 2 BOUNDARY LEVEL 2 LEVEL 3 Discipline LEVEL 3 commands LEVEL 3 LEVEL 4 e g STATICS Discipline commands LEVEL 3 LEVEL 4 LEVEL 4 e g STATICS BOUNDARY LEVEL 2 LEVEL 3 END LEVEL 1 LEVEL 1 5 2 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL The user must be aware of these hierarchies especially when requesting output at higher levels It is possible
427. ovided on the PSHELL entry The property data will be used if the corresponding field on the cguap4 entry is blank The element reference plane is located at the mid thickness of the element parallel to the element mean plane 3 The Ti are optional if not supplied they will be set to the value of T specified on the PSHELL entry In such cases the continuation entry is not required 4 TMAX is ignored unless the element is linked to the global design variables by a SHAPE entry ASTROS THE BULK DATA PACKET 7 61 CROD USER S MANUAL Input Data Entry CROD Rod Element Connection Description Defines a tension compression torsion element ROD of the structural model Format and Examples 1 2 3 4 5 6 7 8 9 10 CROD EID PID G1 G2 TMAX CROD 12 13 21 23 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PROD property entry Default is EID Integer gt 0 Gi Grid point identification numbers of connection points Integer gt 0 TMAX Maximum allowable rod area in design Real gt 0 0 or blank Remarks 1 See CONROD for alternative method of rod definition 2 Only one ROD element may be defined on a single entry 3 TMAX is ignored unless the element is linked to global design variables by a SHAPE entry 7 62 THE BULK DATA PACKET ASTROS Input Data Entry Defines a shear panel element SHEAR of the structural model C
428. owing these the solution control commands are echoed to the output listing This listing is helpful in identifying the particular disciplines and cases selected in the run The multidisciplinary nature of ASTROS requires further output labeling Therefore in addition to the solution control summary the BOUND module writes a summary of selected disciplines for each boundary condition at the top of the boundary condition loop as shown in Table 8 2 It indicates all disciplines and most discipline options in the current boundary condition to assist you in determining the particular path that will be taken through the standard MAPOL sequence A similar printout Table 8 3 from the ABOUND module appears at the top of the sensitivity phase boundary condition loop to indicate the nature of the active boundary conditions and active design constraints The next set of output Table 8 4 comes from the bandwidth minimizer It details the method selected numbers of grids and elements in the model and the values of the measures of merit in the resequencing of grid points Active constraint information is provided in the Active Constraint Summary from the ACTCON module It indicates the total number of constraints considered active according to the current constraint deletion criteria You may select a complete listing of the active constraints with the PRINT DCONSTRAINT solution control option but you may not suppress the table header indicating the number of co
429. ption Defines modal damping as a tabular function of frequency Format and Examples 1 2 3 4 5 6 7 8 9 10 TABDMP 1 ID TYPE Fi G1 F2 G2 F3 G3 CONT CONT F4 G4 F5 G5 F6 G6 ete TABDMP1 3 G 0 0 0 005 1 0 0 008 2 0 0 001 ABC BC 2 05 0 01057 2 6 0 01362 Field Contents ID Table identification number Integer gt 0 TYPE Data word which indicates the type of damping units G CRIT Q or blank Default is G Fi Frequency value in cycles per unit time Real gt 0 0 Gi Damping value Real Remarks 1 Theri must bein either ascending or descending order but not both 2 J umps between two points Fi Fi 1 are allowed but not at the end points 3 At least two entries must be present 4 Any Fi Gi entry may be ignored by placing the BcD string SKIP in either of two fields used for that entry 5 The TABDMP1 mnemonic infers the use of the algorithm g g F where F is input to the table and g is returned The table look up gy F is performed using linear interpolation within the table and linear extrapolation outside the table using the last two end points at the appropriate table end At jump points the average g F is used There are no error returns from this table look up procedure 6 If TYPE is G or blank the damping values are in structural damping units that is the value of g in 1 Hg K If TYPE is CRIT the damping values are in the units of f
430. putational expression and a larger block of lines 101 237 is removed from the program 9 1 5 CREATING MAPOL PROGRAMS If the standard executive sequence is not selected the MAPOL compiler assumes that a new program is being created This new program may perform any operations that use any of the matrix and database utilities available in the ASTROS system All of these are described in subsequent chapters of this manual ASTROS MAPOL PROGRAMMING 9 3 USER S MANUAL Table 9 2 Summary of MAPOL User Options STATEMENT FUNCTION MAPOL lt option list gt Begins a MAPOL program and selects its name and compiler options END Terminates the MAPOL program EDIT lt option list gt Modifies the standard solution sequence DELETE a b Removes line a or lines a through b when editing aii Retin old linea or lines a through b and inserts new ones when INSERT a Inserts new lines after a when editing 9 1 6 SUMMARY Table 9 2 summarizes the MAPOL statements that have been described in this section along with their uses 9 4 MAPOL PROGRAMMING ASTROS USER S MANUAL 9 2 DATA TYPES AND DECLARATIONS This section describes the data types that are available in the MAPOL language It discusses their specifications during programming and how they are represented in the ASTROS machine 9 2 1 DEFINITIONS AND NOTATION All programming languages are composed of two kinds of symbols The first kind
431. r ges 2 9 ASTROS i USER S MANUAL 2 2 2 1 Unique ASTROS files aaa a 2 9 2 21222 DalaDaS S 400 e wee Hone in A a ye Hae ee ae RCH ME 2 9 2 2 3 The eSHELL Program tercio Malad a Cee ad Hale Hale a Hee 2 10 2 2 4 Automatic Preference Files 4 4 o o 2 10 2 2 5 Online Manuals uo a 6 a e A A E ES e a ee 2 10 3 THE INPUT DATA STREAM o o 3 1 SL INTRODUCTION Lo 2 4 ees dto e o e de ee ld a ae 3 1 3 2 THE RESOURCE COMMANDS 00 00m E A BS es 3 5 3 2 1 THE ASSIGN COMMAND aooaa 3 5 3 2 2 ASSIGN COMMAND DESCRIPTIONS FOR HOST COMPUTERS 3 6 3 2 2 1 UNIX SYSTEM IMPLEMENTATION o e e 3 6 3 2 3 THE MEMORY COMMAND o 3 9 3 3 THE INCLUDE DIRECTIVE 204 208 a A e amp oe 3 10 34 THE DEBUG PAGKE To 2 s 22 5 2 oie 2s te ole He ae 3 12 3 4 1 EXECUTIVE SYSTEM DEBUG COMMANDS o e e e 3 13 3 4 2 DATABASE AND MEMORY MANAGER DEBUG COMMANDS 3 14 3 4 3 INTERMEDIATE RESULTS PRINTING COMMANDS 3 15 3 4 4 MISCELLANEOUS DEBUG COMMANDS o o a 3 17 3 4 5 SEQUENCER INTERMEDIATE PRINT COMMANDS 3 18 4 THE EXECUTIVE SYSTEM AND MAPOL 4 1 4 1 THE MAPOL PROGRAM io A BS Ee A 4 2 4 2 MAPOL EDIT COMMANDS 00 02050054 4 3 4 3 THE STANDARD EXECUTIVE SEQUENCE 4 3 4 4 STANDARD EXECUTIVE SEQUENCE STRUCTURE 4 4 4
432. r large problems ASTROS OUTPUT FEATURES 8 37 USER S MANUAL 8 4 5 Intermediate Optimization Output The DESIGN module for resizing via mathematical programming methods has a DEBUG option called DESIGN that selects a print of intermediate data The DESIGN debug value is passed directly to the MicroDOT optimization package which makes the following intermediate quantities available PRINT ACTION 1 Initial design information and final results 2 The above and function values at each iteration 3 The above and internal MicroDOT parameters 4 The above and search directions 5 The above and gradient information 6 The above and scaling information 7 The above and one dimensional search information These DESIGN DEBUG options allow the user to view the detailed calculations used in the solution of the approximate constrained optimization problem that ASTROS generates at each iteration The user is cautioned that the data printed from the DESIGN module are not necessarily ordered in the same manner as in other design prints and not identified by user supplied design variable identification numbers 8 5 EXECUTIVE SEQUENCE OUTPUT UTILITIES In recognition of the inability to provide for the print of all useful response quantities utilities have been included in the set of MAPOL modules to augment the solution control print options These utilities may be placed in any MAPOL program where the user desi
433. r to select physically reasonable designs without retaining all the minimum thickness constraints potentially a very large number Typically this means N 1 elements spread over the range of the shape function e g span or chord where N is the order of the shape N 0 UNIFORM N 1 LINEAR etc 7 94 THE BULK DATA PACKET ASTROS USER S MANUAL DCONTH3 Input Data Entry DCONTH3 Description Defines a set of BAR element cross sectional properties for a list of elements which are linked using SHAPE entries and for which side constraints are to be retained for all design iterations Format and Example 1 2 3 4 5 6 7 8 9 10 DCONTH3 ETYPE DVSYM EID1 EID2 EID3 EID4 EID5 EID6 CONT CONT EID7 EID8 Setce DCONTH3 BAR D1 100 101 Alternate Form 1 2 3 4 5 6 if 8 9 10 DCONTH3 ETYPE DVSYM EID1 THRU EID2 Field Contents ETYPE Character input identifying the element type Must be BAR DVSY Symbol selecting one of the PBAR1 cross sectional parameters Character D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 EIDi Element identification numbers Integer gt 0 or blank Remarks 1 The purpose of this bulk data list is to ensure that adequate physical move limits are retained in optimization with shape function design variable linking without requiring retention
434. raction of critical damping C CO If TYPE is Q the damping values are in the units of the amplification or quality factor q These constants are related by the following equations C CO g 2 1 0 1 E i 7 226 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry TABLED1 TABLED1 Description Defines a tabular function for use in generating frequency dependent and time depend ent dynamic loads Format and Examples 1 2 3 4 5 6 if 8 9 10 TABLED1 ID CONT CONT X1 y1 X2 y2 X3 y3 etc TABDMP1 32 ABC BC 80 6 9 220 5 6 32 0 5 26 Field Contents ID Table identification number Integer gt 0 Xi Vi Tabular entries Real Remarks 1 The xi must bein either ascending or descending order but not both 2 J umps between two points xi xi 1 are allowed but not at the end points 3 Atleast two entries must be present 4 Any x y entry may be ignored by placing the string SKIP in either of the two fields used for that entry The generated function is Y y 8 where X is input to the table and Y is returned The table look up y x is performed using linear interpolation within the table and linear extrapolation outside the table using the last two end points at the appropriate table end At jump points the average y x is used There are no error returns from this table look up procedure ASTROS THE BULK DATA PACKE
435. radian angles as arguments and result in radian angles just as in Fortran All MAPOL functions are generic in the sense that they support multiple data types INTEGER REAL as arguments and perform the appropriate conversions 9 6 8 INTRINSIC RELATIONAL PROCEDURES As discussed in Section 9 4 MAPOL has provided a means by which individual relational entries row at tribute combinations may be accessed directly Table 9 11 shows the argument lists to the set of intrinsic procedures provided to enable the MAPOL programmer to open relations to retrieve particular rows to update or add rows and to close the relation In combination with the RELATION and PROJECT declara tions these procedures provide a direct database interface that neatly matches the full relational applica tion programming interface in CADDB There is an implementation maximum of five open relational variables at any time during the execution of a MAPOL program Figure 9 2 shows a simple MAPOL procedure that manipulates a relation called GPOINT Two rows are placed in the relation followed by a conditional retrieval to obtain one of the tuples for use in an additional operation 9 6 9 GENERAL INTRINSIC PROCEDURES Two other intrinsic procedures have been provided to enhance the utility of MAPOL the ExIT and TRNSPOSE procedures The first is identical to the common Fortran extension EXIT The MAPOL state ment CALL EXIT will cleanly terminate the ASTROS execution w
436. rates the M2GG and K2GG matrices if necessary MSWGRESP ENG Computes element mass or weight intricsic response function ENG Assembles the element design variable linear and nonlinear stiffness and mass matrices into the NLEMA1 design sensitivity matrices ENG Computes the element nonlinear stiffness mass thermal load and stress component NLEMG sensitivities for all structural elements ENG Assembles the simple nonlinear load vectors and simple nonlinear load sensitivities for all NLLODGEN applied loads in the Bulk Data File ENG Reduces the symmetric n set stiffness mass or loads matrix to the f set if there are single point NREDUCE constraints in the boundary condition NULLMAT ENG Breaks database equivalences from previous boundary conditions OFPAEROM ENG Solves for the SAERO applied loads and displacements on aero boxes for output requests ENG Prints selected displacements velocities and or accelerations from any analyses in the current OFPDISP boundary condition OFPALOAD ENG Solves for the SAERO applied loads and constraint forces for output processing OFPDLOAD ENG Processes output requests for dynamics loads transient frequency and gust ENG Prints selected element stress strain force and or strain energies from any analyses in the OFPEDR current boundary condition 4 16 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL Table 3 8 Summary of ASTROS Modules Continued
437. rd function FFREQ has the same arguments as FROOT and returns the frequency in radians Conversion to Hertz may be accomplished by using the HERTZ intrinsic function 6 3 2 8 Static Aero Response Functions The static aero response functions are defined by j l caseid FLEXCF axis E CASELIST case_sid l l A caseid RIGIDCF axis a CASELIST case_sid l E 7 at caseid r m para CASELIST case_sid where FLEXCF RIGIDCF and TRIM represent flexible stability coefficient rigid direct stability coeffi cient and trim parameter values respectively The flex and rigid functions allow as input the axis axis and the trim parameters trim_param The trim function inputs only the trim parameters When axis see below is ROLL PITCH or YAW these functions return their appropriate results in radians If degrees are required the results may be converted using the DEGs intrinisic function The optional caseid allows the selection of a specific case 6 12 THE FUNCTION PACKET USER S MANUAL USER S MANUAL The allowable values for axis are The allowable control surfaces trim_param are ALPHA BETA PRATE ORATE RRATE PACCEL QACCEL RACCEL trim_param User Surfaces where the User Surfaces are defined using either AESURF Or CONLINK Bulk Data entries 6 3 3 Ordered Sets As seen functions allow the user to define synthetic response constraints and synthetic objective func
438. res to see additional information In general these utilities print the data contained in either general or specific data base entities The formats of these prints are more general and therefore less well identified than the special print options described in the preceding subsections The generality of these utilities however is felt to be a vital addition to the output features of the ASTROS procedure in that almost any data on the user s data base files can be written to the output file These utilities provide a primitive link between ASTROS and external post processing systems ICE now provides a very sophisticated link 8 5 1 Structural Set Definition Print Utility USETPRT The USETPRT utility has been provided to print for each boundary condition in the solution control packet the structural set definition table stored in the ASTROS data base entity USET This utility exactly mimics the capabilities provided by the NASTRAN PARAM USETPRT option TheUSETPRT module has the following calling sequence CALL USETPRT USET BC BGPDT BC 8 38 OUTPUT FEATURES ASTROS USER S MANUAL For the selected boundary condition Bc each degree of freedom in the structural model is listed in a table which shows the structural sets to which the degree of freedom belongs The reader is referred to Section 4 of the Theoretical Manual for more information on the structural set definitions in ASTROS 8 5 2 Special Matrix Print Utility UT
439. res where possible and by using the NASTRAN bulk data style for the additional engineering data ASTROS is highly compatible with existing NASTRAN models and with current finite element model generation methods Just as in NASTRAN the bulk data packet begins with the keyword BEGIN BULK which may be abbreviated BEGIN and is terminated by the optional keyword ENDDATA or by the end of the input stream The intervening bulk data entries can appear in any order An alphabetically sorted listing of the bulk data input will be echoed to the output file unless suppressed by the user through the BEGIN BULK command line options All the input entries are interpreted by IFP through templates that are defined as part of the system generation task The templates provide for basic error checking establish defaults and direct the place ment of the raw data onto the database The use of templates allows additional entries to be added to the system very simply without software changes The definition of the templates and the means of adding new entries are documented in the Programmer s Manual In addition the complete listing of ASTROS ASTROS THE BULK DATA PACKET 7 1 USER S MANUAL bulk data templates is included in the output summary generated by the SYSGEN system generation utility during the creation of the system database files On restart with a bulk data packet in the input stream the FP module will append the new data onto the data from the previo
440. resses strains forces and strain energies are available for each element or layer of a composite element Since the stresses strains and forces vary within a CODMEM1 element the intersection point of the diagonals projected onto the mean plane of a warped element has been chosen as the point at which the stresses strains forces and strain energies for the element are computed The stresses strains and element forces are computed in the element coordinate system The element coordinate system and the stress computation point for the QDMEM1 element are shown in Figure 8 7 and those for the TRMEM in Figure 8 8 G3 G G 2 Figure 8 7 QDMEM1 Element Coordinate System 8 18 OUTPUT FEATURES ASTROS USER S MANUAL G3 Xm 8m G2 G1 Figure 8 8 TRMEM Element Coordinate System ASTROS computes the running loads associated with the stresses for the QDMEM1 element These forces are 1 The force components in the element coordinate system at the stress computation point The QDMEM1 stress and strain print includes the following The normal stresses or strains at the stress point in the element x and y directions The shear stress or strain on the element x face in the element y direction 4 The angle in degrees between the element x axis and the major principal axis The major and minor principal zero shear stresses or strains The maximum shear stress or strain An example of the printed output for the QDMEM 1
441. rgest component value in the g set When using the Max normalization with Dynamic Reduction the g s amp degrees of freedom excluding the dynamic reduction generalized coordinates are used in the normalization process Finally if you select NORM POINT the eigenvectors are normalized with respect to the value of the component defined by GID and DoF This component must bein the analysis set 7 124 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry ELEMLIST ELEMLIST Description Defines a list of elements Format and Example T 2 3 4 5 6 7 8 9 0 ELEMLIST SID ETYPE EID1 EID2 EID3 EID4 EID5 EID6 CONT CONT E1D7 EID8 etc CONT ELEMLIST 100 QDMEM1 100 101 200 205 Alternate Form di 2 3 4 5 6 7 8 9 10 ELEMLIST SID ETYPE EID1 THRU EID2 Field Contents SID Set identification number referenced by Solution Controlcommands or Bulk Data entries Integer gt 0 ETYPE Character input identifying the element type One of the following BAR QDMEM1 CONM2 QUAD4 ELAS ROD IHEX1 SHEAR IHEX2 TRIA3 IHEX3 TRMEM MASS CONROD EIDi Element identification numbers Integer gt 0 or blank Remarks 1 Ifthe alternate form is used EID2 must be greater than or equal to EID1 2 Nonexistent elements may be referenc
442. ribed in this section ASTROS THE FUNCTION PACKET 6 25 USER S MANUAL Comment Purpose Toinsert commentary text into the Function packet Usage any text may appear here 6 26 THE FUNCTION PACKET USER S MANUAL USER S MANUAL CENTROID Intrinsic Function CENTROID Purpose Toreturn the centroidal coordinates of the requested elements Usage eid x1 CENTROID X2 cid ELEMLIST elem_sid x3 Function Argument eid Identification of an element specified in the Bulk Data Packet elem_sid Set identification of an ELEMLIST bulk data entry used to specify an element Xi Component for the geometric coordinate cid Identification of a coordinate system specified in the Bulk Data Packet Notes 1 When an element identification is used then the eid must be unique and if the eidis not unique then an element list must be used 2 If the cidreferenceis omitted then the coordinate valueis returned in theinput coordinate system of the element A cid of 0 requests that the coordinate be returned in the basic coordinate system 4 The interpretation of x1 X2 and x3 depends on whether the cid coordinate system is rectangular cylindrical or spherical ASTROS THE FUNCTION PACKET 6 27 COORD Intrinsic Function COORD Purpose Toretrieve the current value of a geometric coordinate Usage GRIDLIST grid_sid X3 x1 coorp Jan pef li eai USER S MANUAL Function Arguments
443. rimarily to be an automated design tool but it can also perform analyses without doing any design This is reflected in the division of the solution control packet into two subpack ets either of which is optional The first or OPTIMIZE subpacket defines the boundary condition s and disciplines which will generate design constraints to be used in the redesign task In defining an optimization boundary condition the user either implidtly or explidtly specifies that constraints be applied to certain discipline dependent response quantities ASTROS then considers the complete set of constraints from all disciplines in all optimization boundary conditions in the redesign task The second ANALYZE subpacket defines analyses that are to be performed on the possibly redesigned structure The ANALYZE subpacket is intended to provide the designer with the means to obtain additional output that is not desired during the optimization phase or to perform additional analyses which were not performed in the design task It can also be used to perform analyses on structures that are not to be designed at all The form of the solution control packet is then ASTROS THE SOLUTION CONTROL PACKET 5 3 USER S MANUAL SOLUTION OPTIMIZE Optimization Subpacket END ANALYZE Analysis Subpacket If optimization is being performed the OPTIMIZE subpacket must precede the ANALYZE subpacket Any number of boundary conditions and or disciplines can b
444. ription Format and Example DLOAD USER S MANUAL Defines a dynamic loading condition for frequency response or transient response prob lems as a linear combination of load sets defined using RLOAD1 or RLOAD2 entries for frequency response or TLOAD1 or TLOAD2 entries for transient response 1 2 3 4 5 6 7 8 9 10 DLOAD SID S s1 L1 S2 L2 3 L3 CONT CONT S4 L4 ete DLOAD 17 1 0 2 0 6 2 7 2 0 8 A A 2 0 9 Field Contents SID Load set identification number Integer gt 0 S Scale factor Real 0 0 Si Scale Factors Real 0 0 Li Load set identification numbers defined via bulk data entries enumerated above Integer gt 0 Remarks 1 Theload vector being defined by this entry is given by P S gt SiPi j The Li must be unique SID must be unique from all Li TLOAD1 and TLOAD2 loads may be combined only through the use of the DLOAD entry RLOAD1 and RLOAD2 loads may be combined only through the use of the DLOAD entry SID must be unique for all TLOAD1 TLOAD2 RLOAD1 and RLOAD2 entries OW BF WN Linear load sets must be selected by a solution control command DLOAD SID 7 110 THE BULK DATA PACKET ASTROS USER S MANUAL DLONLY Input Data Entry DLONLY Description This entry is used in conjunction with the RLOAD1 RLOAD2 TLOAD1 and TLOAD2 entries and defines the point where the dynamic load is to be applied with the scale factor A
445. ription Defines scalar points of the structural model Format and Examples 1 2 3 4 5 6 7 8 9 10 SPOINT ID1 ID2 ID3 ID4 ID5 ID6 1D7 ID8 SPOINT 3 18 1 4 16 2 Alternate Form 1 2 3 4 5 6 7 8 9 10 SPOINT ID1 THRU ID2 Field Contents IDi ID1 ID2 Scalar point identification number Integer gt 0 ID1 lt ID2 Remarks 1 If the alternate form is used all scalar points 1D1 through ID2 are defined 7 224 THE BULK DATA PACKET ASTROS USER S MANUAL SUPORT Input Data Entry SUPORT Fictitious Support Description Defines coordinates at which the user desires determinate reactions to be applied to a free body during analysis Format and Examples 1 2 3 4 5 6 7 8 9 10 SUPORT SETID ID C ID e ID e SUPORT 1000 16 215 Field Contents SETID Solution control SUPPORT set identification Integer gt 0 ID Grid or scalar point identification number Integer gt 0 C Component number zero or blank for scalar points any unique combination of the digits 1 through 6 for grid points Remarks 1 Coordinates specified on this entry form members of a mutually exclusive set They may not be specified on other entries that define mutually exclusive sets 2 From oneto three support coordinates may be defined on a single entry 3 Continuation entries are not allowed ASTROS THE BULK DATA PACKET 7 225 TABDMP1 USER S MANUAL Input Data Entry TABDMP1 Modal Damping Table Descri
446. ription of each of the entries listed in this section Section 7 6 discusses the differences between NASTRAN and ASTROS for those entries that have been changed or are completely different than in NASTRAN but that use the same mnemonic and serve a similar purpose Entries indicated by are unchanged from NASTRAN 7 5 1 Aerodynamic Load Transfer ATTACH Rigid load transfer definition SET1 A structural grid point list for spline interpolation or a mode list for omitting normal modes in flutter analysis SET2 Structural grid point list in term of aerodynamic macroelements SPLINE1 Surface spline definition for out of plane motion SPLINE2 Beam spline definition for interpolating panels and bodies ASTROS THE BULK DATA PACKET 7 5 USER S MANUAL 7 5 2 Applied Dynamic Loads LAGS LOAD ONLY D D D GUST R R LOAD1 LOAD2 ABLED1 TLOAD1 TLOAD2 Time and phase lag definition for a spatial load Linear combination of dynamic load sets Direct definition of dynamic spatial load Stationary vertical gust definition Frequency dependent dynamic load definition Frequency dependent dynamic load definition Tabular function definition for dynamic load generation Time dependent dynamic load definition Time dependent dynamic load definition 7 5 3 Applied Static Loads FORCE FORCE1 GRAV LOAD MOMEN MOMENT 1 PLOAD Defin
447. rmation on the structural elements is contained in Chapter 5 ofthe ASTROS Theoretical Manual Figure 8 2 BAR Element Forces Sign Conventions ASTROS OUTPUT FEATURES 8 11 USER S MANUAL Stresses strains forces and strain energies are available as output for the BAR element through the STRESS STRAIN FORCE and ENERGY solution control print options The following element forces are output on request Bending moments at each end in both reference planes Shear forces in each reference plane Average axial force Torque about the bar axis The following element stresses and strains in the element coordinate system are output on request 1 2 3 4 Average axial stress or strain Extensional stress or strain due to bending at 4 points on the cross section at each end Maximum and minimum stress or strain at each end Stress margins of safety for the element in both tension and compression re wa Tensile stresses and strains are given a positive value while compressive stresses and strains are given a negative value The bending contribution to the stresses are always computed at the four points on the element cross section that were specified on the connectivity entry for the BAR element This means that the safety margins are computed using all eight stress values even if all four stress points at each end are Table 8 10 BAR Element Output Quantities 1 ASTROS VERSION 9 0 03 03 93 P 16 FINAL ANALYS
448. rol FSTEP SID to be used 3 All FREQ FREQ1 and FREQ2 entries with the same frequency set identification numbers will be used Duplicate frequencies will be ignored N and N 1 are considered duplicated if fu fn 1 lt 10 fMAx MIN 7 136 THE BULK DATA PACKET ASTROS USER S MANUAL FREQ1 Input Data Entry FREQ1 Description Defines a set of frequencies to be used in the solution of frequency response problems by specification of a starting frequency frequency increment and number of increments desired Format and Example 1 2 3 4 5 6 7 8 9 10 FREQ1 SID F1 DF NDF FREQ1 6 229 019 LS Field Contents SID Frequency set identification number Integer gt 0 F1 First frequency in set Real gt 0 0 DF Frequency increment Real gt 0 0 NDF Number of frequency increments Integer gt 0 Remarks 1 Theunits for the frequency F1 and the frequency increment DF are cycles per unit time 2 The frequencies defined by this entry are given by fi F1 i 1 DF i 1 NDF 1 Frequency sets must be selected by the Solution Control FSTEP SID to be used 4 All FREQ FREQ1 and FREQ2 entries with the same frequency set identification numbers will be used Duplicate frequencies will be ignored N and N 1 are considered duplicated if fu fn 1 lt 10 fmax fMin ASTROS THE BULK DATA PACKET 7 137 FREQ2 USER S MANUAL Input Data Ent
449. rs may be freely included in the layer s composing the ply The only restriction is that at least one layer in the ply must be a local design variable If the ply is composed of a single layer this constraint becomes redundant with the TMIN entered on the Pcompi field for shape function linking or the vmIN entered on the DESELM or DESVARP entry for physical linking In this case the most critical limit will be determined from among all sources DCONPMN DCONLMN TMIN VMIN and will be used to update the local variable side constraint The DCONxxx entry will then be automatically removed since it will no longer be necessary A summary of this action will be echoed to the print file ASTROS USER S MANUAL DCONSCF Input Data Entry DCONSCF Stability Derivative Constraint Description Defines a constraint on the flexible stability derivative at the reference grid point associ ated with the force or moment due to a trim parameter or control surface deflection of the form OCF E OCF E OCF 06 trim faa dtrim d trim upper Format and Example 1 2 3 4 5 6 7 8 9 10 DCONSCF SETID ACCLAB PRMLAB CTYPE PRMREQ UNITS DCONSCF 999 PACCEL AILERON LOWER 1 0 RADIANS Field Contents SETID Set identification number referenced by the DCONSTRAINT Solution Control option of the SAERO command Integer gt 0 ACCLAB Alphanumeric string identifying the aerodyn
450. rse shear thickness divided by membrane thickness Real gt 0 0 or blank Default 833333 NSM Nonstructural mass per unit area Real gt 0 0 or blank 71322 Fiber distances for stress computation The positive direction is determined by the right hand rule and the order in which the grid points are listed on the connection entry Real or blank defaults are 1 2 T for Z1 and 1 2 T for Z2 MID4 Material identification number for membrane bending coupling Integer gt 0 or blank must be blank unless MID1 gt 0 and MID2 gt 0 may not equal MID1 or MID2 MCSID Identification number of material coordinate system Real or blank or Integer gt 0 See Remark 9 SCSID Identification number of stress coordinate system Real or blank or Integer gt 0 See Remark 9 ZOFF Offset of the element reference plane from the plane of grid points A positive value means the ze direction Real or blank default 0 0 See Remark 10 TMIN Minimum thickness for design Real gt 0 0 or blank Default 0 0001 Remarks 1 All PSHELL property entries must have unique identification numbers 2 The structural mass is computed from the density using the membrane material properties ASTROS THE BULK DATA PACKET 7 201 PSHELL USER S MANUAL 3 Theresults of leaving an MID field blank are MID1 Nomembraneor coupling stiffness MID2 No bending coupling or transverse shear stiffness MID3 Notransverse shear flexibility MID4 Nobending membrane c
451. ry FREQ2 Description Defines a set of frequencies to be used in the solution of frequency response problems by specification of a starting frequency final frequency and number of logarithmic incre ments desired Format and Example 1 2 3 4 9 6 7 8 9 10 FREQ2 SID F1 F2 NF FREQ2 6 1 0 8 0 6 Field Contents SID Frequency set identification number Integer gt 0 F1 First frequency Real gt 0 0 F2 Last frequency Real gt 0 0 F2 gt F1 NF Number of logarithmic intervals Integer gt 0 Remarks 1 The units for the frequencies F1 and F2 are cycles per unit time 2 The frequencies defined by this entry are given by where Jl For the example shown the list of frequencies will be 1 0 1 4142 2 0 2 8284 4 0 5 6569 and 8 0 cycles per unit time Frequency sets must be selected by the Solution Control FSTEP SID to be used 4 All FREQ FREQ1 and FREQ2 entries with the same frequency set identification numbers will be used Duplicate frequencies will be ignored N and N 1 are considered duplicated if fN fN lt 107 fmax fMIN 7 138 THE BULK DATA PACKET ASTROS USER S MANUAL FREQLIST Input Data Entry FREQLIST Description Defines a list of frequencies for which outputs are defined Format and Example aH 2 3 4 5 6 7 8 9
452. s SAERO caseid symtype TRIM k DCON O STRESS m STRAIN n DCFUNCTION p SAERO TRIM 60 SAERO ANTISYMMETRIC TRIM 70 STRESS 100 Option Meaning caseid Case identification number I nteger gt 0 symtype Selects the symmetry type for the subcase from SYMMETRIC Or ANTISYMMETRIC Default is SYMMETRIC k Set identification of a TRIM bulk data entry which provides flight condition infor mation m Set identification for stress constraints as defined by DCONVM DCONVMM DCONVMP DCONTW DCONTWM Or DCONTWP bulk data entries n Set identification for strain constraints as defined by DCONEP DCONEPM DCONEPP DCONFT DCONFTM Or DCONFTP bulk data entries o Set identification for displacement constraints as defined by DCONDSP DCONTRM DCONCLA DCONALE Or DCONSCF bulk data entries Pp Set identification of DCONF constraint functions Remarks 1 If any discipline has a caseid then all disciplines must have a caseid All caseid values must be unique but they need not be in any particular order Disciplines are implicitly numbered from 1 to n if no caseid values are specified The caseid is only used as a reference from user defined functions in the F unction Packet 2 TRIM is required Both symtyp and the CONSTRAINT section are optional SAERO disciplines may be freely combined with other ASTROS disciplines 4 For compatibility the alternate form of constraint specification shown below is also allowed Its
453. s respec tively LAYRNUM and LAYRLST are mutually exclusive 4 Noncomposite elements may be linked to composite layers by including them in the referenced SHAPE Or SHAPEM Set 7 108 THE BULK DATA PACKET ASTROS USER S MANUAL DLAGS Input Data Entry DLAGS Description This entry is used in conjunction with RLOAD1 RLOAD2 TLOAD1 and TLOAD2 data entries and defines time lags and phase lags as well as the set identification of the static load Format and Example 1 2 3 4 9 6 7 8 9 10 DLAGS SID LID TAU PHASE LID TAU PHASE DLAGS 5 24 0 04 20 0 10 0 0 45 0 Field Contents SID Identification number of DLAGS set Integer gt 0 LID Identification number of time or frequency independent applied load Integer gt 0 TAU Time delay for the designated load set Real PHASE Phase lag in degrees for the designated load set Real Remarks 1 One or two dynamic load sets may be defined on a single entry 2 Refer to RLOAD1 RLOAD2 TLOAD1 or TLOAD2 entries for formulas which define the manner in which TAU and PHASE are used The phase parameter is used only in conjunction with RLOAD1 and RLOAD2 data entries 4 The LID set can refer to statically applied loads as well as to additional dynamic loads input on DLONLY entries 5 TAU and PHASE can be defaulted to zero but LID must not be zero ASTROS THE BULK DATA PACKET 7 109 DLOAD Input Data Entry Desc
454. s 2 0 COMP GLIST CLIST MULT MULT DISP GRIDLIST GLIST 1T3 CASELIST MLIST Constraint for the Component Value CONST GLIST CLIST MULT ALLOW COMP GLIST CLIST MULT ALLOW ENDF The Bulk Data Packet defines the grid list and subcase identification list defines the design constraints 101 which references the design constraint function CONST and defines its four arguments The arguments identify the GRIDLIST the CASELIST the multiplier used with the displacement compo nent and the allowable upper limit of the constraint BEGIN BULK Grid list with 4 Grid points identified GRIDLIST 1 5 10 HS 20 Subcase list with 5 Subcases identified CASELIST 101 1 2 3 4 5 DCONF 101 CONST DCN1 DCN1 GLIST 1 CLIST 101 MULT 2 ALLOW 100 ENDDATA There are no constraints generated because the GRIDLIST contains four values and the CASEL Ist contains five values ASTROS will terminate during the processing of the user input data As indicated earlier the cardinality of the sets must be equal Example 7 Missing Bulk Data The following example demonstrates an invalid request for constraints of the normal stress in the element s X direction The solution control packet references the functional design constraint 101 in the Bulk Data Packet for the STATICS discipline of boundary condition 1 OPTIMIZE BOUNDARY S
455. s composite counterpart DCONTH2 to name critical minimum gauge constraints see Remark 3 will cause only the named elements thickness con straints to be computed and retained All layers of composite elements named on DCONTHK will be retained NOTE that all elements thickness constraints will always be computed irrespective of the DCONTHK entries but may be deleted in the constraint deletion 2 The global design variable in shape function linking is non physical and no reasonable restriction for a global variable move limit side constraint can be defined Therefore constraints on the local design variables controlled by shape functions are generated by ASTROS to ensure that the design is reasonable ie nonnegative thicknesses 3 The DCONTHK entry should select a minimum number of elements linked to shape functions that will enable the optimizer to select physically reasonable designs without retaining all the minimum thickness constraints potentially a very large number Typically this means N 1 elements spread over the range of the shape function e g span or chord where N is the order of the shape N O UNIFORM N 1 LINEAR etc Use DCONTH2 for composite elements in which linking across layers may allow certain layers to be omitted from the retention set 7 96 THE BULK DATA PACKET ASTROS USER S MANUAL DCONTRM Input Data Entry DCONTRM Aeroelastic Trim Parameter Constraint Description Defines a trim parameter constra
456. s delivered with your software or use the method described in Section 4 2 Contact your UAI Systems Support Specialist for information about this file 4 24 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL Chapter 5 THE SOLUTION CONTROL PACKET The solution control packet provides the means by which the user selects the optimization and analysis tasks to be performed by the ASTROS system their order of execution and the engineering data related to each The solution control commands are analogous in purpose to the NASTRAN Case Control com mands but they are very different in form and subtly different in interpretation Understanding the differences between ASTROS and NASTRAN in the area of solution control is fundamental in under standing multidisciplinary optimization in the ASTROS system because the solution control command structure follows directly from the ASTROS capability to perform multidisciplinary analyses in a single run It is critical that the user clearly understand the subtleties of solution control syntax and hierar chies This section therefore augments the presentation of the solution control mechanics with a discus sion of the design considerations that are embodied in the solution control commands The detailed definition of all solution control commands follows at the end of the chapter In ASTROS the solution control is very closely linked to the structure of the standard MAPOL sequence It may be advantageou
457. s for the beginning user to read the standard MAPOL sequence discussion in the preceding section and to study the Theoretical Manual discussion of multidisciplinary optimization before reading the remainder of this section The solution control packet is initiated with the keyword SOLUTION which follows the DEBUG and MAPOL packets if present in the input data stream The packet is terminated when the BULK DATA packet or the end of the input stream is encountered The data are composed of solution control statements which can begin in any column and can extend over multiple physical records Each state ment is formed from a combination of keywords separated by blanks or commas as indicated in the detailed syntactical descriptions at the end of the chapter Further each command keyword can be abbreviated by the first four or more characters of the keyword The solution control packet follows a prescribed hierarchy with the following levels ASTROS THE SOLUTION CONTROL PACKET 5 1 USER S MANUAL INITIAL LEVEL Level 1 TYPE OF BOUNDARY CONDITION Level 2 BOUNDARY CONDITION S Level 3 DISCIPLINE S Level 4 Each of these levels is discussed in the following sections and compared and contrasted to their NAS TRAN counterparts In addition to these hierarchical commands there are commands for output process ing that can occur at several levels in the hierarchy This section presents the available commands and
458. s in the following equivalent examples In the latter case ASTROS will automatically generate the missing continuation mnemonics Care must be taken however that the first two data fields of the continuation line be non blank If not there is an ambiguity as to whether the first continuation field constitutes a continuation label or a data field This ambiguity causes the IFP to terminate execution with an error indicating that there is a missing continuation line Free format input in which the parent and continuation lines are broken into separate physical lines or which explicitly include the continuation mnemonics do not suffer this limitation Free format input is further restricted in that the break between physical lines if needed must occur at a break in the logical line that is the split must occur between the ending continuation field on the current logical line and the continuation field of the next logical line This means for the preceding example that the first example entry could be broken into two lines between the ABc and BC fields but nowhere else When an entry is broken into multiple physical lines the continuation mnemonics must be supplied Obviously fixed format input requires continuation mnemonics for any bulk data entries having continu ation lines 7 3 DATA FIELD FORMATS The interior fields of a bulk data line can contain either integer data real data character data or certain combinations e g either in
459. s of elements aerodynamic elements and structural elements An aerody namic element is defined as a box of an aerodynamic macroelement e g wing component or fuselage segment The nature of the macroelement varies among both aerodynamic models and among aerody namic components within each model In general however a box is the smallest subdivision of the aerodynamic component for which data e g pressures forces and moments are computed Structural elements are either metric elements which connect structural node points grids scalar elements which connect pairs of degrees of freedom or pairs of scalar points or mass elements Table 8 9 shows the list of aerodynamic and structural elements in ASTROS for which element output exist The following subsec tions document the quantities that are available as output for each of these elements The structural mass elements are not induded in this table since they have no element response quantities The NASTRAN User s Manual Reference 2 was used as a major resource in writing this section and you are referred to it for additional information on the structural elements ASTROS OUTPUT FEATURES 8 9 USER S MANUAL Table 8 9 ASTROS Aerodynamic and Structural Elements AERODYNAMIC STRUCTURAL CAERO1 CBAR CAERO2 CELAS1 CELAS2 CAERO6 CIHEX1 CIHEX2 CIHEX3 PAERO6 CROD CONROD CODMEM1 CTRMEM CTRIA3 CQUAD4 Structural element output is available for all disciplines
460. s you should leave the FL Field blank 5 If you select NORM MASS the eigenvectors are normalized to a unit value of the generalized mass If you select NORM MAX the eigenvectors are normalized with respect to the largest component value in the g set When using the Max normalization with Dynamic Reduction the g s amp degrees of freedom excluding the dynamic reduction generalized coordinates are used in the normalization process Finally if you select NORM POINT the eigenvectors are normalized with respect to the value of the component defined by GID and DoF This component must bein the analysis set ASTROS THE BULK DATA PACKET 7 121 EIGR INVERSE POWER USER S MANUAL Bulk Data Entry EIGR INVERSE POWER Description Specifies real eigensolution control data for the Inverse Power method which is used to extract a few eigenvalues in a specified frequency range Format and Example 1 2 3 4 5 6 7 8 9 10 EIGR SID METHOD FL FU NEST NVEC E cont cont NORM GID DOF EIGR 13 INV 1 9 15 6 10 12 1 6 A A POINT 32 4 Field Contents SID Set identification number 1 nteger gt 0 Required ETHOD Method of eigenvalue extraction Character SINV Required FL FU Frequency range of interest cycles sec 2 Real FL lt Fru Required NEST Estimated number of roots in the frequency range FL to FU Integer gt 0 Required NVEC The num
461. scalar point identification numbers Integer gt 0 Remarks 1 Note that enforced displacements are not available via this entry As many continuation entries as desired may appear 2 Coordinates specified on this entry form members of a mutually exclusive set They may not be specified on other entries that define mutually exclusive sets Single point constraint sets must be selected in Solution Control SPC SID to be used SPC degrees of freedom may be redundantly specified as permanent constraints on the GRID entry If the alternate form is used points in the sequence GID1 through GID2 are required to exist ASTROS THE BULK DATA PACKET 7 221 SPLINE1 Input Data Entry USER S MANUAL SPLINE1 Surface Spline Description Defines a surface spline for interpolating out of plane motion for aeroelastic problems Format and Examples 1 2 3 4 5 6 7 8 10 SPLINE1 EID CP MACROID BOX1 BOX2 ETG DZ SPLINE1 3 111 1 118 14 0 0 Field Contents EID Element identification number Integer gt 0 CP Coordinate system defining the spline plane Integer gt O or blank ACROID Identification number of a CAEROi entry which defines plane of spline Integer gt 0 BOX1 BOX2 First and last box whose motions are interpolated using this spline Integer gt 0 SETG Refers to a SETi entry which lists the structural grid points to which the spline is attached Integer gt
462. scription of the cross sectional parameters 2 Element lists are defined using ELEMLIST Bulk Data entries Only designed BAR elements which reference PBAR1 property entries are affected 7 92 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description DCONTH2 DCONTH2 Thickness constraints on layers of composite elements Defines a set of layers for a list of elements linked using SHAPE entries for which the ply thickness constraints are to be retained on all design iterations Format and Example 1 2 3 4 5 6 7 8 9 10 DCONTH2 ETYPE LAYRNUM LAYRLST EID EID EID EID EID CONT CONT EID EID etc DCONTHK QUAD4 100 101 200 205 Alternate Form 1 2 3 4 5 6 7 8 9 10 DCONTH2 ETYPE LAYRNUM LAYRLST EID THRU EID Field Contents ETYPE Character input identifying the element type One of the following QUAD4 TRIA3 QDMEM1 TRMEM LAYRNUM Layer number of the layer s to be retained The given layer will be retained for each element in the list of elements Integer gt 0 or blank See Remark 1 LAYRLST Set identification number of a PLYLIST bulk data entry naming a set of plies to be retained as active for each element Integer gt 0 or blank See Remark 1 EID Element identification number Integer gt 0 or blank Remarks 1 One and only one of
463. se machines are very likely to exist on most machines that may be used The user is referred to their ASTROS system manager for the particulars of the interface between the local host system and ASTROS The following section describes parameters for computers using Unix based Operating Systems 3 2 2 1 UNIX SYSTEM IMPLEMENTATION The ASSIGN command supplies the ASTROS system with the root name of the database files the status of those files and a set of user parameters The status is selected from NEW OLD or TEMP and the set of user parameters can be any of the following keyword commands ILOC path Specifies the location of the Index Component file DLOC path Specifies the location of the Data Component files DBLKSIZE n CADDB data files block size in words IBLKSIZE n CADDB index file block size in words 3 6 THE INPUT DATA STREAM ASTROS USER S MANUAL DB2 EDB Pa DB1 EDB LE DB2 00 a gt DB1 00 fo a DB2 01 TN DISK1 DISK2 DISK3 HOST I O SYSTEM U7 o ASTROS lt INPUTSTREAM gt n ASSIGN RUNDB MYDB OLD PASSWORD X Figure 3 3 Function of the ASSIGN Command ASTROS THE INPUT DATA STREAM 3 7 USER S MANUAL Note that the DLoc parameter may specify a series of locations when very large databases are being created The format is then DLOC path_1 path2 TEMP DatabaseE xample When the status is TEMP a temporary database is created and no data is
464. selection can appear at any level of the solution control hierarchy and will apply at that level until it is overridden When more than one discipline is covered by a print request at the boundary level ASTROS will consider only the relevant print requests for each discipline For example if STATICS and FLUTTER are performed the sTATICS discipline will ignore any ROOTS requests and the flutter discipline will ignore any STRESS requests 5 4 1 Subset Options As indicated in the preceding subsections some disciplines have more than one subcase per solution control statement Others like STATICS and SAERO have a separate solution control statement for each subcase In all cases disciplines within the OPTIMIZE subpacket may be analyzed at one or more design iterations When one subcase is defined per statement the user is free to modify the print requests from subcase to subcase for example ANALYZE BOUNDARY SPC 10 STATICS MECH 10 PRINT STRESS ALL DISP 100 STATICS MECH 20 GRAV 100 PRINT DISP ALL 5 14 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL specifies that stresses for all elements and displacements for nodes listed in set 100 be printed for the first subcase mechanical loads with set identification 10 and only the displacements be printed for the next load condition When the discipline generates more than one subcase however the user must specify the subcases to which the PRINT r
465. sical design variable value if shape function design variable linking is used In cases where data from NASTRAN preprocessors are used there are no changes required unless shape function linking is desired A more subtle set of changes was required to perform multidisciplinary analysis In NASTRAN as was mentioned in the discussion of the Solution Control packet many parameters were specified as part of the model definition or discipline specification because the code was limited to performing a single analysis of the given discipline In order to remove these artificial restrictions these data have been moved to the proper discipline s subcase definition Examples of this form of modification are the addition of symmetry options to the MKAEROi GUST FLUTTER and TRIM entries and the removal of subcase dependent data from the AERO entry Further the rigid elements ASETi OMITi and EPOINT entries were modified to include a set identification number to enable multiple boundary conditions and multiple control systems to be analyzed simultaneously The last type of modification came about because of the nature of the ASTROS database management system These were limited to the DMI and DMIG entries for direct loading of database entities The NASTRAN inputs were not compatible with the ASTROS database and so had to be modified In fact these entries while having the same name as a NASTRAN entry are completely new entries for AS TROS A minor additi
466. sign If WINDOW is nonzero the half width of a band around zero EPS is computed ASTROS THE SOLUTION CONTROL PACKET 5 31 OPTIMIZE Remarks USER S MANUAL EPS WINDOW 100 MAX ABS TMIN ABS TMAX If the local variable falls within the band the new minimum or maximum for the current iteration is changed to lie on the other side of zero from the local variable The bandwidth EPS is a percentage of the larger of TMAX or TMIN where WINDOW specifies the percentage Default 0 0 must be greater than or equal to 0 0 Exponential move limit for rsD Numbers less than 1 0 result in a smaller move with smoother convergence Ignored if sTRAT MP Default 0 90 must be greater than 0 0 Convergence limit specifying the maximum percentage change in the objective function that can be considered converged Default 1 0 must be greater than 0 0 Constraint retention factor for MP methods The number of active constraints will be at least NRFAC times the number of design variables Default 3 0 Constraint retention parameter in which all constraints having a value greater than EPs will be considered active Default 0 10 Finite difference step size for nonlinear design variables The relative design FDSTEP v v 0 0 FDSTEP V 0 0 tion Default 0 001 must be greater than zero Objective function selected from WEIGHT the default value or the set identifica tion of a single scalar DCONF function Identification number of
467. site the installation of the code involves a definition of these parameters and the form they must take The ASTROS system is currently functional on numerous host systems including VAX UItrix IBM AIX SGI 4D series and Crimson l ndigo series HP 9000 series CRAY UNICOS DECStation Convex and SunSparcstation The availability on a spe cific computer may be obtained by contacting UAI The next section documents the installation dependent ASSIGN parameters for some of the more common features hosts These features however may be customized to a very high degree and may be modified by the local system manager Further documentation of the ASSIGN command is left to the local installation or will be included in the delivery material The Programmer s Manual contains the detailed description of how these and other machine dependent parameters are defined 3 2 2 ASSIGN COMMAND DESCRIPTIONS FOR HOST COMPUTERS This section contains the descriptions of the machine and installation dependent parameters on the ASSIGN command for three machines on which ASTROS is currently functional The parameters that are available at each site are listed and details of their use are presented The user is cautioned that these are site dependent parameters which may be different for each installation even if the host system is the same This documentation is provided both as an example to the system programmer and because the features that have been made available on the
468. solution Numerical estimate of zero on the computer Usually the default value is adequate If a ane computer with a short word length is used ZRO ie 1 0E 4 may be preferred INTEGER PARAMETER DEFINITION DEFAULT Scaling parameter By default scaling is done ISCAL every NDV iterations otherwise scaling is 1 performed every ISCA iterations ee Maximum number of iterations allowed at the 40 optimizer level The number of consecutive iterations for which TIRONE the absolute or relative convergence criteria 2 must be met to indicate convergence at the optimizer level The number of consecutive iterations for which TTRMST the absolute or relative convergence criteria Note 3 must be met to indicate convergence at the optimizer level STAX Maximum of iterations allowed at the strategy Note 3 leva MPPARM 3 Some of these parameters indicated in the tables are used only with the original version of the ADS optimizer They are not used in MicroDOT ASTROS THE BULK DATA PACKET 7 171 OMIT Input Data Entry Description OMIT Omitted Coordinates USER S MANUAL Defines degrees of freedom that the user desires to omit from the problem through matrix partitioning Used to reduce the number of independent degrees of freedom Format and Example 1 2 3 4 5 6 7 8 10 OMIT SETID ID C ID ID E OMIT 10 16 2 23 3516 54 23 Field Contents SETI
469. ssion Sc is always treated as a negative value regardless of the sign of the input value 5 LAYRNUM is only used if the element is composed of a composite material defined with Pcomp Bulk Data entries ASTROS THE BULK DATA PACKET 7 75 DCONF Input Data Entry DCONF Functional Design Constraint USER S MANUAL Description Define one or more synthetic response constraints or a synthetic objective function Format and Example 1 2 3 4 5 6 7 8 9 10 DCONF SID LNAME FNAME CONT CONT ARG1 VAL1 ARG2 VAL2 ARG3 VAL3 etc DCONF 101 ZETA DCN1 DCN1 MACH 0 8 DENS 0 8 MODE 1 VELO 600 0 Field Contents SID Set Identification number selected by Solution Control See Remark 1 Integer gt 0 LNAME Optional User defined label for the design constraint function Character or blank FNAME The name of a function defined in the Functions packet Character ARGi The name of an argument as given in the Functions packet defined in the named function FNAME Character VALi The value of the parameter arGi to be used in the named function FNAME Integer or Real Remarks 1 Thepbconr entry is selected in Solution Control with one of the two options 7 76 THE BULK DATA PACKET DCFUNCTION sid or OBJECT sid of the OPTIMIZE command and or by the option DCFUNCTION sid on the discipline commands STATICS MODES SAERO and FLUTTER The
470. st the design variables for which stiffness sensitivities are to punched Set identification of an LDVLIST bulk data entry that is used to request the local design variable Ds for which local design variables are to be punched Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which applied loads are to be punched Set identification of a GRIDLIST bulk data entry that is used to request the grid points degrees of freedom for which the mass matrix is to be punched Set identification of an LDVLIST and or a GDVLIST bulk data entry that is used to request the design variables for which mass sensitivities are to punched Set identification of a GDVLIST bulk data entry that is used to request the design variables for which objective function gradients are to be punched Set identification of an ELEMLIST bulk data entry that is used to request the aerodynamic elements for which QHH is to be punched Set identification of an ELEMLIST bulk data entry that is used to request the aerodynamic elements for which Q g is to be punched Set identification of an MODELIST bulk data entry that is used to request the modes for which flutter and normal modes eigenvalue results are to be punched THE SOLUTION CONTROL PACKET 5 37 PUNCH USER S MANUAL aa Set identification of a GRIDLIST bulk data entry that is used to request the grid points at which spc forces are to be punched ab Set identification of a GRID
471. structural model Format and Example 1 2 3 4 5 6 7 10 GRAV SID CID G N1 N2 N3 GRAV 1 3 32 0 0 0 0 1 Field Contents SID Set identification number Integer gt 0 CID Coordinate system identification number Integer gt 0 G Gravity vector scale factor Real 0 0 Ni Gravity vector components Real at least one nonzero component Remarks 1 Thegravity vector is defined by g G Ni Thedirection of g is the direction of free fall 2 ACID of zeroreferences the basic coordinate system 3 Gravity loads may be combined with simple loads e g FORCE MOMENT by specification on a LOAD entry or by GRAV SID Gravity loads with the same SID as simple load entries will not be used unless referenced by one of these methods 4 Load sets must be selected in Solution Control to be used The units of G should be length sec in consistent length units 7 144 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry GRDSET Grid Point Default GRDSET Description Defines default options for Fields 3 7 and 8 of all GRID entries Format and Example ol 2 3 5 7 8 9 10 GRDSET CP CD PS GRDSET 16 32 3456 Field Contents CP Identification number of coordinate system in which the location of the grid point is defined Integer gt 0 CD Identification number of coordinate system in whic
472. superseded 5 5 SOLUTION CONTROL COMMANDS The ASTROS Solution Control Commands are described in this section ASTROS THE SOLUTION CONTROL PACKET 5 17 USER S MANUAL Table 5 4 Response Quantity Output Options OPTION DESCRIPTION ACCELERATION Selects accelerations at nodal points AIRDISPLACEMENT Selects displacements on aerodynamic boxes CGRADIENT Selects gradients of active constraints DCONSTRAINT Selects active constraints at each iteration DISPLACEMENTS Selects displacements at nodal points ENERGY Selects strain energy at structural elements FORCE Selects element forces at structural elements GDESIGN Selects global design variables GPFORCE Selects grid point forces at nodal points GPWG Selects print of grid point weight summary KSNS Selects stiffness sensitivities at design variables LDESIGN Selects local design variables LOAD Selects applied loads at nodal points MASS Selects mass matrix at nodal points MODEL Selects Bulk Data at current design point PUNCH only MSNS Selects mass sensitivities at design variables OGRADIENT Selects gradient of the objective function QHH Selects QHH generalized unsteady aerodynamic forces at modes QHI Selects QHJ generalized unsteady aerodynamic forces at modes ROOT Selects flutter and normal modes roots eigenvalues SPCFORCE Selects forces of single point constraint at nodal points S
473. t Description Defines a list of design constraints for which constraint value output and or constraint gradient output are desired Format and Example 1 2 3 4 5 6 7 8 9 10 DCONLIST SID TYPE NRFAC EPS DCONLIST 1000 DISP 0 6 05 Field Contents SID Set identification number Integer gt 0 TYPE The design constraint type One of the following FREQ frequency FLUT flutter DISP displacement VMISES Von Mises TSAIWU Tsai Wu STRAIN strain THICK thickness EFF aeroelastic effectiveness SCF stability coefficient TRIM trim ALL all of the above OTHER all EXCEPT the above The Default value is ALL NRFAC Constraint retention factor for math programming methods At least NRFAC number of design variables constraints will be considered active Real gt 0 0 Default 3 0 EPS Constraint retention parameter in which all constraints having a value greater than EPS will be considered active Real Default 0 1 Remarks 1 NRFAC and EPS control the number of constraints that are selected for print and punch output For constraint gradients only those considered active by the global constraint screening algorithm NRFAC and EPS from the OPTIMIZE command in Solution control are available to be selected 2 More than one DCONLIST with the same set identification number may be used to select subsets of different constraint types 7 86 THE BULK DATA PACKE
474. t as well as selection of additional point degrees of freedom In NASTRAN these data are either implicitly selected through the rigid format selection and or bulk data or are a discipline option in the case control packet While the boundary condition definition in ASTROS appears to be very complex it is relatively simple if one realizes that the fundamental purpose of the BOUNDARY command is to uniquely specify the system level matrices and the matrix reductions that should be performed on them The ASTROS automatic singular ity feature AUTOSPC is the default in all cases Unlike NASTRAN this feature is selectable by boundary condition There is one level of boundary condition specification which is not treated in the BOUNDARY command It deals with symmetry options which play a restrictive role in multidisciplinary analysis especially for aerodynamic disciplines The symmetry options are often limited by the nature of the structural and or aerodynamic models that are defined in the bulk data packet For example if the structural model is a half model only the user cannot specify that asymmetric structural boundary conditions be analyzed As a more common example the user might want to perform an asymmetric aeroelastic analysis with a 5 4 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL structural half model Unfortunately this is not possible in ASTROS Whenever possible the implicit model defined boundary condition specifications
475. t the following stresses and strains are output in the basic coordinate system at the twenty one points located at the center corners and mid edges of the element Normal stresses or strains in all three directions Shear stresses or strains in all three planes 3 Principal stresses or strains in all three directions with associated direction cosines Mean stress or strain Octahedral shear stress or strain The stress and strain output at each of the 21 points is identified by a stress or strain point ID The stress and strain point IDs are numbered 1 through 21 with the first 20 ordered as on the associated CIHEX2 input data entry and the 21st located at the element center Although the corner stress and strain points are located at the corner grid points of the element the mid edge stress and strain points may or may not be located at the mid edge grid points depending on the location of those grid points The stress strain points for the IHEX2 are illustrated in Figure 8 4 All output is given in the element coordinate system for the HEX2 Strain energy output may be requested for the HEX2 element The strain energy print for the IHEX2 is identical to that for the BAR element and includes a breakdown by element and by element type HEX3 Element Output element is a cubic isoparametric solid hexahedron element with three extensional degrees of each of its 32 nodes rains and strain energies are avail
476. t data is computed only once and reused subsequently for each iteration This is the underlying principle used in defining preface modules In each instance the data generated are invariant with respect to the design variables The preface segment begins with a call to the solution control interpreter to determine the number and types of analyses to be performed The input file processor IFP is then called The element connection data and element matrices are then formed PFBULK is then called to perform error checking operations on a variety of user input data The EMA1 is called to compute the design invariant stiffness and mass sensitivities to the global design variables Then the simple loads and load sensitivities are computed in LODGEN If any planar static aerodynamic analyses are requested in the solution control the STEADY and SPLINES modules are called to create the aerodynamic matrices required for the aeroelastic analysis Finally unsteady aerodynamics matrices are computed for GUST and FLUTTER analyses in UNSTEADY AMP and SPLINEU 4 4 2 3 The Analysis Optimization Segments The remainder of the MAPOL algorithm consists of the optimization and analysis segments Any particu lar boundary condition is either an optimization boundary condition implying that the quantities com puted in the disciplines selected in the solution control are constrained and that the structure is to be optimized subject to those constraints or an analysis b
477. t expr gt is converted to the type of the variable lt var gt based on the rules of Table 9 9 where the following definitions are used ASTROS MAPOL PROGRAMMING 9 17 VAL X value of x FIX X convert x toan integer value FLOAT X convert x toa floating point value REAL C convert tothe real part of a complex number Table 9 9 Assignment Rules in MAPOL USER S MANUAL TYPE OF TYPE OF ASSIGNMENT RULE lt var gt lt expr gt INTEGER VAL lt expr gt lt VAR gt INTEGER REAL FLOAT VAL lt expr gt lt VAR gt COMP LEX FIX REAL VAL lt expr gt lt VAR gt INTEGER FLOAT VAL lt expr gt lt VAR gt REAL REAL VAL lt expr gt lt VAR gt COMPLEX REAL VAL lt expr gt gt lt VAR gt INTEGER FLOAT VAL lt expr gt gt REAL lt VAR gt COMPLEX REAL VAL lt expr gt gt REAL lt VAR gt COMPLEX VAL lt expr gt gt lt VAR gt 9 18 MAPOL PROGRAMMING ASTROS USER S MANUAL 9 4 CONTROL STATEMENTS 9 4 1 INTRODUCTION Control statements are statements used to alter and control the normally sequential execution of MAPOL instructions There are five MAPOL control statements GOTO e FOR DO e WHILE DO e IF THEN ELSE END ENDP 9 4 2 THE UNCONDITIONAL GOTO STATEMENT The Goto statement causes MAPOL program to jump unconditionally to the specified statement label This label must exist in the same program un
478. t number any one of digits 1 through 6 A Real coefficient Real 0 0 Remarks 1 Displacement constraints are selected in Solution Control with the discipline option DCON CTSET The CTSET is the constraint set identification number and DCID is an arbitrary constraint identifier supplied by the user All DCONDSP that share the same CTSET and DCID will form one constraint equation 2 Both upper and lower bounds on the deflections can be specified by this entry For example if constraints of the form u lt 2 0 are to be imposed one DCONDSP entry would use CTYPE UPPER DALL 2 0 G 32 C 3 A 1 0 while a second entry would use CTYPE LOWER DALL 2 0 G 32 C 3 A 1 0 3 Twist constraints can be specified by differencing two displacements while camber constraints can be expressed as a weighted sum of three displacements 4 Any number of continuation entries are permitted A LOWER bound constraint excludes all values to the left of DALL on a real number line while an UPPER bound constraint excludes all values to the right irrespective of the sign of DALL 7 72 THE BULK DATA PACKET ASTROS Input Data Entry DCONEP Principal Strain Constraint Definition Description Defines a principal strain constraint by specifying the identification numbers of con strained elements Format and Example 2 3 4 5 6 7 8 9 10 DCONEP SID ST Sc SS ETYPE LAYRNUM EID1 EID2
479. t of quantities so that the quantity selected by a particular keyword can some times change from one discipline to another In addition the available quantities are sometimes a function of the boundary condition type For example the flutter mode shape is not available as an output from a flutter analysis performed in the OPTIMIZE subpacket This subsection will present the available quantities the PRINT options which select them and the limitations if any on their availabil ity Table 5 4 summarizes the available PRINT and PUNCH response quantity options As in NASTRAN stresses strains and element forces are computed in the element coordinate system at predetermined or user selected points in the element Nodal quantities are computed in the global coordinate system CGRA DCON GDES KSNS MODEL MSNS OGRA and HIST are only applicable in the OPTIMIZE subpacket above the first BOUNDARY since these requests transcend all analyses The DISP option for flutter analyses is only applicable in the ANALYZE subpacket Other options are available independent of the boundary condition type Table 5 5 presents a matrix of response quantity options for each discipline type showing the applicability of each option Any requests for quantities that do not apply to the particular discipline will be ignored by the output processor without warning Most options can be ALL NONE or an integer value which selects bulk data entry sets listing the items for which
480. t the flutter root flutter damping and flutter frequency respectively These functions are defined by FROOT machop densop modeop velop caseop FDAMP ZETA E machop densop L modeop velop caseop FFREQ machop densop modeop velop caseop where is mvalue RA MACHLIST mach_sid a dvalue FAO DENSLIST dens_sid modeid Pate Re MODELIST mode_sid 1 y vvalue A VELOLIST vel_sid caseid CISSP 77 CASELIST case_sid The arguments to the first function FROOT includes a Mach value machop in either of the two forms shown It may be an explicit value mvalue or a Mach list MACHLIST Similarly it requires a density ratio value dvalue or a density list DENSLIST selected mode index modeid or a mode list ASTROS THE FUNCTION PACKET 6 11 USER S MANUAL MODELIST for the modes in the flutter set and the analysis velocity value vvalue or a velocity list VELOLIST The function FROOT then returns a complex number representing the flutter root p k y i The arguments to the second function FDAMP are a component GAMMA or zETA the Mach value a density ratio a selected mode index for the modes in the flutter set and the analysis velocity The function then returns the specified flutter damping coefficient as defined below Re p Im p for complex p Y Re p In for real p 2 Y Re p S Gs Re p for complex p IM The thi
481. te system The continuations are required No physical property in this element can be used as a local design for automated design 7 40 THE BULK DATA PACKET ASTROS USER S MANUAL CMASS1 Input Data Entry CMASS1 Scalar Mass Connection Description Defines a scalar mass element of the structural model Format and Example cl 2 3 4 5 6 7 8 9 10 CMASS1 EID PID G1 C1 G2 C2 TMAX CMASS1 32 6 2 1 Field Contents EID Element identification number Integer gt 0 PID Identification number of a PMASS property entry Default is EID Integer gt 0 Gi Geometric grid point identification number Integer gt 0 Ci Component number 6 Integer gt 0 TMAX The maximum mass value allowed in design Real Default 10 Remarks 1 Scalar points may be used for G1 and or G2 in which case the corresponding c1 and or c2 must be zero or blank Zero or blank may be used to indicate a grounded terminal G1 or G2 with a correspond ing blank or zero C1 or C2 A grounded terminal is a point whose displacement is constrained to zero 2 The two connection points G1 C1 and G2 C2 must be distinct Except in unusual circumstances one of them will be a grounded terminal with blank entries for G and C 3 The TMAX value is used only for shape function design variable linking ASTROS THE BULK DATA PACKET 7 41 CMASS2 USER S MANUAL
482. teger or real data The template for each entry defines which types of data are acceptable in each field Each data item is limited to the number of characters that fit in the length of the field For narrow width fields no more than eight characters can be used in the data item Unlike NASTRAN any extra characters will spill to the next field and will result in IFP errors there is no provision for rounding real data to fit the field size 7 4 THE BULK DATA PACKET ASTROS USER S MANUAL In order to be considered valid the data item must first satisfy the data type requirement as specified on the template Real numbers including zero must contain a decimal point although there are a number of formats supported For example the real number 3 1 may be encoded as shown or as 3 150 3 1D00 0 31E1 or 3 1 0 Unlike NASTRAN however there cannot be embedded blanks anywhere in the real number and a D edit descriptor is treated as a single precision number until actually loaded to a double precision relational attribute Blank fields that do not have other defaults specified on the template will be interpreted as blank characters an integer zero or a real zero as required Integer values must be formed from the ten decimal digits with an optional leading plus or minus sign Character data consist of any combination of alphanumeric characters including any digits decimal points etc with no restriction that the first character be alphabetic 7 4
483. ter analyses in the current boundary condition and evaluates any flutter FLUTTRAN constraints if it is an optimization boundary condition with applied flutter constraints FNEVAL ENG Evaluates user defined objective and constraint functions ENG Compiles the FUNCTION Packet and instantiates user functions that have been invoked in FPKEVL Solution Control ENG Reduces the symmetric or asymmetric f set stiffness mass and or loads matrix to the a set if FREDUCE there are omitted degrees of freedom Computes the sensitivities of active frequency constraints in the current active boundar FREQSENS ENG seas es A Performs redesign by fully stressed design methods based on the set of applied stress FSD ENS constraints All other applied constraints are ignored ENG Computes the shifted stiffness matrix and the rigid body transformation matrix eco to be GDR1 used in Phase 2 of Generalized Dynamic Reduction ENG Computes the orthogonal basis PHIOK for the general Krylov subspace to be used in Phase 3 GDR2 of Generalized Dynamic Reduction GDR3 ENG Computes the transformation matrix GSUBO for Generalized Dynamic Reduction ENG Computes transformations between displacement sets useful for data recovery from Generalized GDR4 Dynamic Reduction GDVGRAD ENG Computes design variable sensitivity for intricsic functions GDVRESP ENG Computes design variable responses for intrinsic functions MAT Performs the forward backwar
484. that result in a real displacement field This includes STATICS MODES TRANSIENT and SAERO analyses Complex displacement fields from FLUTTER and FREQUENCY analyses result in computation of the selected complex element response quantities but their formatted print is not available except through executive sequence print utilities described in Subsection 3 4 For all disciplines in ASTROS the solution control print options STRESS STRAIN FORCE and ENERGY are used to select print of the structural element quantities The AIRDISP and TPRESSURE options are used for aerodynamic element quantities Each of these print options selects either ALL NONE or an integer set identification number that refers to one or more ELEMLIST bulk data entries specifying which elements are to have output computed and printed Chapter 4 contains the complete description of the solution control print command Each output is carefully labeled as to its boundary condition number discipline generating the response field and load condition mode number time step frequency step or flight condition represented by the output 8 2 1 1 Aerodynamic Element Output The solution control PRINT option TPRESSURE provides the trimmed pressures on the aerodynamic boxes for SAERO The trimmed pressures are computed and stored in the relational entity OAGRDLOD The AIRDISP print option is available for the SAERO discipline and provides the out of plane displacements and streamwise slopes
485. the alternate form is used EID2 must be greater than or equal toEID1 Nonexistent elements may be referenced and will result in no error message If a layer number is omitted for a composite laminate element then all layers in that element will be Any number of continuations is allowed See the PBAR1 Bulk Data entry for a description of the cross sectional parameters THE BULK DATA PACKET 7 153 LOAD Input Data Entry Description LOAD Static Load Combination Superposition USER S MANUAL Defines a static load as a linear combination of load sets defined using FORCE MOMENT FORCE1 MOMENT1 PLOAD and GRAV entries Format and Example 1 2 3 4 5 6 7 8 9 10 LOAD SID Ss s1 L1 s2 L2 s3 L3 CONT CONT S4 L4 LOAD 101 0 5 1 0 3 6 2 4 4 5 10 ABC BC 2 3 115 Field Contents SID Load set identification number Integer gt 0 S Scale factor Real 0 0 Si Scale factors Real 0 0 Li Load set identification numbers defined via data entry types enumerated above Integer gt 0 Remarks 1 Theload vector defined is given by P s S L 2 TheLi must be unique The remainder of the physical entry containing the last entry must be blank Load sets must be selected in the Solution Control if they are to be applied to the structural model 4 A LOAD entry may not reference a set identification number defined by another LOAD entry 7 154 THE BULK DATA PACKET
486. the element mean plane A positive value NSM means the ze direction Real or blank see Remark 2 Nonstructural mass per unit area Real gt 0 0 USER S MANUAL PCOMP2 2 For composities there are two methods for specifying the offset of the element reference plane from the element mean plane zo on this entry and zorF on the CQUAD4 or CTRIA3 Bulk Data entries The distinction is shown in the figure below UPPER SURFACE LOWER SURFACE Is ZO ELEMENT REFERENCE ZOFF ELEMENT MEAN PLANE You may only specify a zo on this entry if the zorr field of any CQUAD4 or CTRIA3 referencing it is blank The default value for zo is t 2 where t is the overall thickness of the laminate SBOND is required if bonding material failure index calculations are desired 4 The failure theory is used to determine the element failure on a ply by ply basis The available theories are HILL Hill Theory HOFF Hoffman Theory TSAI Tsai Wu Theory STRESS For Maximum Stress Theory STRAIN For Maximum Strain Theory MEM indicates a layup of membrane only plies The material properties MIDi may reference only MAT1 MAT2 and MATS Bulk Data entries If any of the Ti or THi are blank then the last non blank values specified for each will be used to define the values for the ply 8 TMIN will beignored unless the element is linked to design variables by SHAPE entries ASTROS THE BULK DATA PACKET 7 187 PELAS USER S MANUAL I
487. the response quantity is desired For example the STRESS option points to the ELEMLIST bulk data entity which lists the elements for which stresses are desired The NONE option is used to override a default established through a print or punch request at a higher level in the hierarchy The ASTROS output philosophy is similar to that of NASTRAN in that it is assumed that mistakes in the output requests should not terminate execution If for example the requested structural element does not exist in the model the output request will be ignored without any warning to the user Other output request errors in ASTROS are treated in a similar manner occasionally generating a warning message but more typically resulting in no visible indication that the request was in error Therefore the user can in most cases request output that does not apply to the discipline for entities nodes or elements which do not exist and or for subcases that are not defined without causing termination of the execution 5 16 THE SOLUTION CONTROL PACKET ASTROS USER S MANUAL 5 4 3 Form Options For complex response quantities the form option is provided to select either RECTANGULAR Or POLAR form Rectangular form gives the cartesian components of the quantity in the rectangular complex plane in which the first number represents the real component and the second number the imaginary compo nent Polar form gives the components in polar coordinates in which the first numb
488. the same file that contains all of the other ASTROS print output 9 5 1 THE PRINT STATEMENT Output printing is requested with the PRINT statement the syntax of which is PRINT lt format gt lt print list gt In order to allow maximum power and flexibility while minimizing training the format specifications used by MAPOL are identical to those used by Fortran The format is entered as a literal string enclosed by quotation marks i e 1X 5E1 6 w 71X X ES E The lt print list gt isa list of one or more defined variables to be printed If only heading information is being printed the lt print list gt may be omitted Examples of print statements are PRINT 1X 3115 1 J K ASTROS MAPOL PROGRAMMING 9 23 USER S MANUAL which prints the three integer variables 1 J and K using the indicated format and PRINT 1X THIS IS A HEADER which prints this message THIS IS A HEADER ASTROS does not attempt to check the validity of a format statement with the data types being printed As a result it is possible to cause a Fortran run time error condition 9 6 PROCEDURES AND FUNCTIONS 9 6 1 INTRODUCTION One of the most powerful features of a programming language is the ability to define procedures or subroutines that perform specialized tasks Some procedures with special characteristics are called functions Each MAPOL main program procedure or function is called a program
489. the table to ensure its completeness and usefulness in modifying the standard sequence The use of these modules is discussed in more detail in the section on modifying the standard MAPOL sequence and are more fully documented in the Programmer s Manual The brief descriptions of the remaining segments of the standard algorithm that follow coupled with the inherent readability of MAPOL syntax provide a complete picture of the flow through the standard sequence 4 12 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL 4 4 2 1 MAPOL Engineering and Utility Modules This section contains a brief description shown in Table 4 8 of each of the MAPOL addressable modules defined to the ASTROS executive system The intrinsic mathematical functions of the MAPOL language are not included The TYPE column indicates whether a module is used for ENGineering functions MATrix manipulations UTILity operations or to address the eBASE database Table 4 8 Summary of ASTROS Modules MODULE TYPE DESCRIPTION Generates flags for the current boundary condition during the sensitivity calculation These are ABOUND ENG then returned to the executive sequence to direct the execution of the required sensitivity analyses Determines whether the design task has converged If the optimization has not converged this ACTCON ENG module selects which constraints are to be included in the current red
490. tification number Required only if NORM POINT Integer gt 0 DOF Component number One of the integers 1 6 Required only if NORM POINT andG is a geometric grid point Remarks 1 The real eigenvalue extraction method set must be selected in Solution Control METHOD SID to be used 2 The Lanczos eigenvalue extraction technique is optimized for processing large sparse matrices It is not recommended to perform either Guyan reduction or Dynamic Reduction with the Lanczos tech nique ASTROS THE BULK DATA PACKET 7 123 EIGR LANCZOS USER S MANUAL 3 The number of eigenvalues and eigenvectors extracted depends on the FL FU and NVEC values A summary is given in the following table FL FU NVEC Eigenvalues and Mode Shapes Computed Blank Blank Blank The lowest mode only Blank Blank n_val The first n_val modes Blank hi_val Blank All modes between and hi_val Blank hi val hval aaa modes in therange and low_val Blank Blank First mode above low_val low_val Blank n_val First n_val modes above low_val low_val hi_val Blank All modes between low_val and hi_val Tow vai hi val avai He e modes between low_val If you are extracting rigid body modes you should leave the FL Field blank 4 If you select NORM MASS the eigenvectors are normalized to a unit value of the generalized mass If you select NORM MAX the eigenvectors are normalized with respect to the la
491. tions To allow maximum flexibility a single function may be referenced many times Because multiple references may become verbose a special provision has been made to allow the use of sets When using a single set in a function the results are straight forward The function is instantiated for every entry in the set When multiple sets are used there are several ways to define the resulting values of a function Specifically these methods relate to the number of members or cardinality and the order of the resulting sets An unambiguous definition of multiple set use has been implemented Each set that appears in the function MUST have the same cardinality or one or more of the sets may have a single member When the function is evaluated the members of each set are placed in a one to one correspondence with each other Consider the following example FUNCTIONS FUN1 DISP GRIDLIST 1 T1 CASELIST 1001 ENDFUNC EGIN BULK RIDLIST 1 1 2 ELIST 1001 3 4 DATA ASTROS THE FUNCTION PACKET 6 13 USER S MANUAL This results in two function evaluations DISP 1 T1 3 DISP 2 T1 4 Other examples of set use are presented in the following Section 6 4 EXAMPLES The following examples demonstrate how the definition and linking of the functions with the Solution Control Bulk Data and the Function Packet is accomplished For each of the examples the Solution Control packet references the functional desig
492. tity specification is made the traces are active for all database operations In addition to their role in debugging the database software the trace options provide a useful means of debugging the interface between a user written module and the database The database control options CALLSTAT and NOCOREDIR provide user control over two internal database functions The CALLSTAT option compiles a summary of the number of calls made to each database subroutine This summary in combination with the IOSTAT option provides statistics on the number of database operations in the execution The NOCOREDIR option is made available for machines with limited core memory resources f NOCOREDIR is selected the database manager stores the database directories on the database files rather than in core This can substantially reduce the database memory require ments at the cost of increasing the number of input output operations Table 3 2 Database Debug Commands KEYWORD DESCRIPTION TRACE Traces all database CALLS Database I O tracing IOSTAT parm PULL Full trace of I O activity sum Summary of I O activity ENTITY name Restricts tracing to entity name Compiles statistics on the number of calls to each database routine at CALLSTAT the end of a job NOCOREDIR Turns off the option to store directories in core NODELAVORE Turns off the option that delays entity creation until the entity is opened MEMO
493. to get print requests by default where they are not expected if oneis not careful with the solution control hierarchy Another common problem is to place an output request on the wrong side of a level in crementing solution command thus placing a command at a higher level than expected Consider the following two examples EXAMPLE 1 EXAMPLE 2 OPTIMIZE OPTIMIZE BOUNDARY SPC 1 BOUNDARY SPC 1 ABEL CASE 1 STATICS MECH 10 STATICS MECH 10 LABEL CASE 1 ABEL CASE 2 STATICS MECH 20 STATICS MECH 20 LABEL CASE 2 ABEL CASE 3 STATICS MECH 30 STATICS MECH 30 LABEL CASE 3 END END In example 1 there are three discipline commands STATICS and three LABEL commands one for each discipline The indenture in the example helps to explain the results of these commands The first STATICS case will be labelled CASE 2 because the LABEL command appears at LEVEL 4 with the STATICS MECH 10 command Similarly the second statics case will be labelled CASE 3 Finally the third statics case will be labelled CASE 1 because that particular LABEL command appeared at LEVEL 3 prior to STATICS MECH 10 Example 2 illustrates the probable intent of the user Here the LABEL commands are placed below the STATICS command As a result the LABELS match the cases 5 1 OPTIMIZE AND ANALYZE SUBPACKETS ASTROS has been designed p
494. to request that a set of the global design variables be printed at some set of iterations The global variable print displays the user assigned design variable identification number the current value the minimum and maximum values allowed for the global variable the sensitivity of the objective function to the design variable and the linking option used to relate it to local design variables The linking options are 1 Unique Physical The user has related the global variable to a single local variable through a DESELM entry 2 Linked Physical The user has related the global variable to some number of local vari ables through a combination of DESVARP and ELIST PLIST entries 3 Shape F unction The user has related this and possibly other global variables to some number of local variables through a combination of DESVARS SHAPE entries The final item in the global design variable print is an eight character user label identifying the design variable An example of this print for the initial iteration of the ten bar truss problem is shown in Table 8 18 along with the LDESIGN print output The LDESIGN solution control print option allows the user to request that some set of local design variables be printed at some set of iterations The local design variables are of course element depend ent Each element type that has elements connected to global design variables is printed separately The elements are identified by element identificati
495. to specify the layer number for a composite element Notes 1 When an element identification is used then the eid must be unique and if the eidis not unique then an element list must be used 2 Composite elements must have their layer number specified ASTROS THE FUNCTION PACKET 6 49 USER S MANUAL This pageis intentionally blank 6 50 THE FUNCTION PACKET USER S MANUAL USER S MANUAL Chapter 7 THE BULK DATA PACKET The bulk data packet provides the ASTROS system with the engineering data needed to perform the specific tasks requested by the user It contains the model geometries for the structural model the aerodynamic model s and the design model as well as the pool of data from which the solution control requests are made Finally specialized information required by the analysis disciplines e g Mach number and reduced frequency pairs for unsteady aerodynamic analyses is also provided to the system through the bulk data packet The basic input item is the bulk data entry which is directly analogous to the NASTRAN bulk data card In fact NASTRAN compatible formats were chosen for the ASTROS bulk data entries whenever possible because modern structures are often analyzed using large NASTRAN finite element models having tens of thousands of lines of bulk data Further these large models are usually prepared using software designed specifically to generate NASTRAN models Thus by utilizing NASTRAN bulk data structu
496. tput in transient analysis Format and Examples 1 2 3 4 5 10 TSTEP SID N 1 DT 1 NO 1 CONT CONT N 2 DT 2 NO 2 STEP 2 10 001 5 ABC ABC 9 0 01 1 Field Contents SID Set identification number Integer gt 0 N i Number of time steps of value DT 1 Integer gt 2 DI 1 Time increment Real gt 0 0 NO i Skip factor for output every NO i th step will be saved for output Integer gt 0 Remarks 1 TSTEP entries must be selected in the Solution Control TSTEP SID 2 Note that the entry permits changes in the size of the time step during the course of the solution Thus in the example shown there are 10 time steps of value 0 001 followed by 9 time steps of value 01 Also the user has requested that output be recorded for t 0 0 0 005 0 01 0 02 0 03 etc ASTROS THE BULK DATA PACKET 7 237 VELOLIST Input Data Entry VELOLIST USER S MANUAL Description Defines a list of velocity values Format and Example 1 2 3 4 5 6 7 8 9 10 VELOLIST SID VELO1 VELO2 VELO3 VELO4 VELO5 VELO6 VELO7 CONT CONT VELO8 VELO9 ete VELOLIST 201 100 0 80 0 200 0 Field Contents SID Velocity set identification number Integer gt 0 VELOi Velocity value Real gt 0 0 Remarks 1 VELOLIST Bulk Data entries are selected in the Function Packet 7 238 THE BULK DATA PACKET ASTROS USER S M
497. tries listed in the preceding Section do not exist in the NASTRAN versions that guided the definition of the bulk data entries Some of them do exist in other NASTRAN systems however the DYNRED JSET JSET1 PCOMP1 and PComP2 entries are examples Others take the place of the NASTRAN PARAM entry which was felt to have been overused to the point where it had lost all utility Examples of these inputs arethe CONVERT MFORM and VSDAMP entries The steady aeroelas tic model is completely new to ASTROS since NASTRAN uses the same modeling for both steady and unsteady analysis Also it was felt that the NASTRAN mechanism for defining dynamic loads was needlessly complicated Working from the NASTRAN inputs a simpler but equally general set of entries was developed This resulted in the generation of a number of new entries and the modification of others The definition of the design variables design variable linking and the design constraints is of course completely new for ASTROS The majority of the changed entries have been modified to accommodate the design task In these cases the bulk data entry is often identical to the NASTRAN version for use in analysis with optional addi tional fields to specify the design data The element connectivity and property entries are all examples of this type of change in that additional field s have been added to specify the maximum and minimum ASTROS THE BULK DATA PACKET 7 11 USER S MANUAL allowable phy
498. ts any unique combinations of the digits 1 through 6 for grid points Remarks 1 When ASET and or ASET1 entries are present all degrees of freedom not otherwise constrained will be placed on the o set The o set is a mutually exclusive set Degrees of freedom may not be specified on other entries that define mutually exclusive sets 2 ASET entries must be selected in Solution Control REDUCE SETID to be used 7 22 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry Description ASET1 ASET1 Selected Coordinates for the a set Alternate Form Defines degrees of freedom that the user desires to place in the analysis set Used to define the number of independent degrees of freedom Format and Examples 1 2 3 4 5 6 7 8 9 10 ASET1 SETID G G G G G CONT CONT G etc ASET1 345 2 1 3 10 9 6 15 ABC tbe 7 8 Alternate Form 1 2 3 4 5 6 7 8 9 10 ASET1 SETI E ID1 THRU ID2 Field Contents SETID The REDUCE set identification number Integer gt 0 E Component number any unique combination of the digits 1 through 6 with no embed ded blanks when point identification numbers are grid points must be null or zero if point identification numbers are scalar points G 1D1 1D2 Grid or scalar point identification numbers Integer gt 0 1D2 gt ID1 Remarks 1 When ASET and or ASET1 e
499. ts are again used as shown below B C D E B C D E F All matrix algebra is optimized to provide the most effective use of computer resources Matrices may also be multiplied by scalars or scalar expressions which may be INTEGER REAL Of COMPLEX These operations are written in the natural way e g x B R S T C DI All scalar multipliers must be placed on the left as shown Note also that the multiplication operator is implied by the parentheses when multiplying a matrix by a scalar In addition to the matrix operations of Table 41 MAPOL allows for matrix transpose and inverse using the syntax of the following example TRANS B C INV KGG PG TRANS A INV A TRANS A 0 B Note that these operations are functions and as such the arguments are enclosed in parentheses Also the use of TRANS is only allowed in expressions See Section 9 6 9 for a discussion of the TRANS function 9 3 4 2 Matrix Operands and Expressions Only matrix operands may be used in matrix expressions with the exception noted in Section 9 5 1 The matrix expressions are evaluated with the same hierarchy as that of arithmetic types 9 3 5 ASSIGNMENT STATEMENTS Assignment statements are used to compute and assign values to variables and array elements The syntax of aMAPOL assignment is lt var gt lt expr gt The type of the expression l
500. uckling constraints EBKLSENS ENG Evaluates Euler buckling constraint sensitivity ENG Computes the stresses strains grid point forces and strain energies for elements selected for EDR output for the particular boundary condition ENG Assembles the linear element stiffness and mass matrices stored in the KELM and MELM EMA1 entities into the linear design sensitivity matrices DKVI DMVI ENG Assembles the element stiffness and mass matrix sensitivities stored in the DKVI and DMvI EMA2 entities into the global stiffness and mass matrices for the current design iteration Computes the el ement linear stiffness mass thermal load and stress component sensitivities for all structural elements UTIL Terminates the execution of the MAPOL sequence Useful to terminate modified MAPOL EXIT sequences FBS MAT Performs the forward backward substitution to solve systems of linear equations FCEVAL ENG Evaluates the current value of all frequency constraints FLUTDMA ENG Assembles the dynamic matrices for the FLUTTER disciplines FLUTDRV ENG Driver for FLUTTER analyses 4 14 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL Table 3 8 Summary of ASTROS Modules Continued MODULE TYPE DESCRIPTION NAME FLUTQHHL ENG Processes the QKKL matrix with normal modes for FLUTTER FLUTSENS ENG Computes the sensitivities of active flutter constraints in the current active boundary condition ENG Performs flut
501. ups of options subset options quantity options and form options These options are fully described in Chapter 4 of this manual but one point must be stressed subset options play an extremely important role in ASTROS output requests Subset options allow you to identify the set of iterations or subcases to which the print selection will apply This selection is necessary because many disciplines MODES for example generate more than one subcase eigenvector with a single solution control directive The critical point is that the default selection for subcases is that there be no output In other words if there are no subcases selected ASTROS will by default print nothing Unlike NASTRAN ASTROS has no options to reorder the output The multidisciplinary nature of ASTROS completely negates the utility of the SoRT1 and SORT2 options found in NASTRAN variants and any other sort options become impossibly complex very quickly Instead a reasonable fixed sort is 8 8 OUTPUT FEATURES ASTROS USER S MANUAL established in which each boundary condition is treated separately and in the order given in the solution control packet If the standard sequence is used the response quantities will appear in the following order within each optimize or analyze boundary condition 1 Steady aerodynamic trim parameters 2 Flutter roots and flutter mode shape modal participation factors note that the mode shape is only available if flutter has occurr
502. ure 8 5 IHEX3 Element bi Se Sad ww ee Ses a es 8 16 Figure 8 6 ROD Element Coordinate System 0 8 17 Figure 8 7 QDMEM1 Element Coordinate System 8 18 Figure 8 8 TRMEM Element Coordinate System 2 8 19 ASTROS ix USER S MANUAL Figure 8 9 QUAD4 Element Coordinate System 0 8 20 Figure 8 10 TRIA3 Element Coordinate System 4 8 20 Figure 8 11 Shear Panel Forces o eee eee 8 23 Figure 9 1 Schematic Representation of Relation 9 9 Figure 9 2 MAPOL Program Using Relational Procedures 9 31 x ASTROS USER S MANUAL LIST OF TABLES Table 1 1 Table 2 1 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 4 1 Table 4 2 Table 4 3 Table 4 4 Table 4 5 Table 4 6 Table 4 7 Table 4 8 Table 5 1 Table 5 2 ASTROS Command Syntax Conventions o e e 1 3 The Preference File Format 0 e 2 4 Executive MAPOL Debug Commands 3 13 Database Debug Commands 02 00500 3 14 Intermediate Results Debug Commands 3 16 Miscellaneous Debug Commands 25 5 3 17 Sequencer Debug Commands o e 5085 3 18 MAPOL Edit Commands 2 ora ao Shee Se te landed CL e 4 3 Real Parameters in the Standard Sequence 4 7 Int
503. us run s There is no provision for deleting existing bulk data except through MAPOL sequence modifications or direct interaction using the ICE program Reference 7 This restart feature while limited can be useful in many instances e g when additional analysis disciplines are desired or when different output requests are desired The remainder of this section presents the struc ture of the bulk data entry for ASTROS and discusses some features of the IFP module that are useful to the general user ASTROS bulk data entries have been carefully designed to be NASTRAN compatible so the NASTRAN User s Manual Reference 2 has provided much of the information in the following discussion as well as having directed the design of the IFP software The reader is also referred to the ASTROS Programmer s Manual for more information on the IFP module and for information on the addition of new bulk data entries 7 1 BULK DATA ECHO OPTIONS There are special options on the BEGIN BULK command which allow the user to control the echoing of the Bulk Data The format of this command is NOECHO NOSORT BOTH PRINT EGIN BULK ECHO Fones SORT The following table describes the actions which are performed for the various options ECHO FILE ORDER ACTION SORT Sorted echo to the output file PRINT unsort Unsorted echo to the output file ECHO SORT Sorted echo to punch file PUNCH UNSORT Unsorted echo to pu
504. ve thickness of a ply that is part of a laminate The constraint is of the form Yoreq _ tply PS lower n 100 tam O lower bound toly _ reg a AAA ES n tam 100 O upper bound Format and Example 1 2 3 4 5 6 7 8 9 10 DCONLAM CTYPE REQ PLYNUM PLYSET LAM SID SID SID CONT CONT SID SID etc DCONLAM UPPER 40 0 100 ALL 1000 1001 Field Contents CTYPE Constraint type either UPPER for upper bound or LOWER for lower bound Character Default UPPER REQ Minimum lower bound or maximum upper bound PERCENTAGE 0 0 to 100 0 of the total laminate thickness that is to be made up of the ply thickness see Remark 2 Real gt 0 0 PLYNUM Single ply number numbered in the order used on the PComPi that constitutes the ply thickness Only one of PLYNUM or PLYSET may be used Integer gt 0 or blank PLYSET Set identification number of one or more PLYLIST bulk data entries naming a set of plies whose summed thicknesses constitute the ply thickness in the constraint Only one of PLYNUM or PLYSET may be used Integer gt 0 or blank LAM The character string ALL or the set identification number of one or more PLYLIST entries naming a set of plies whose summed thicknesses constitute the laminate thickness in the constraint If ALL the laminate is defined to be all the layers on the PCOMPS of the elements selected by SIDi Character ALL or Integ
505. vered at the center of the layer for composite elements uF WN The specific discipline request defines whether the case and or mode is a valid request in the response functions The mode sequence number is used only if the discipline is MODES If the subcase reference is omitted then the specific discipline request defines the requested subcase 6 44 THE FUNCTION PACKET USER S MANUAL USER S MANUAL STRESS Intrinsic Function STRESS Purpose Toretrieve current element STRESS values Usage STRESS elemop stress_comp plyop caseop modeop where eid elemop gt ELEMLIST elem sid E plyid DIYOR ye PLYLIST ply_sid a ES caseid eT CASELIST case_sid modeo gt modei p MODELIST mode_sid Function Arguments eid Identification of an element specified in the Bulk Data Packet elem_sid Set identification of an ELEMLIST bulk data entry used to specify an element stress_comp Element response component plyid Identification of a layer number for a composite element ply_sid Set identification of a PLYLIST bulk data entry used to specify the layer number for a composite element caseid Subcase identification case_sid Set identification of a CASELIST bulk data entry used to specify the subcase number modeid Identification of a mode index mode_sid Set identification of a MODELIST bulk data entry used to specify the mode index ASTROS THE FUNCTION PACKET 6 45 STRESS USER
506. volve the coordinate systems defined The first point is the origin the second lies on the z axis and the third lies in the x z plane Format and Example 1 2 3 4 5 6 7 8 9 10 CORD1R CID G1 G2 G3 CID G1 G2 G3 CORD1R 5 16 32 19 Field Contents CID Coordinate system identification number Integer gt 0 Gi Grid point identification number Integer gt 0 G1 G2 G3 Remarks 1 Coordinate system identification numbers on all CORD1R CORD1C CORD1S CORD2R CORD2C and CORD2S entries must be unique The three points G1 G2 and G3 must be noncollinear The location of a grid point P in the sketch in this coordinate system is given by X Y Z A WN The displacement coordinate directions at P are shown above by u U U y 5 Oneor two coordinate systems may be defined on a single entry 7 52 THE BULK DATA PACKET ASTROS USER S MANUAL CORD1S Input Data Entry CORD1S Spherical Coordinate System Definition Form 1 Defines a spherical coordinate system by reference to three grid points These points must be defined in coordinate systems whose definition does not involve the coordinate systems defined The first point is the origin the second lies on the z axis and the third lies in the plane of the azimuthal origin Description Format and Examples I 2 3 4 5 6 7 8 9 10 CORD1S CID G1 G2
507. y because it will reduce resources that could be used for other processes on your system Under certain circumstances excess memory may actually degrade the performance of ASTROS and in extreme cases even your computer system ASTROS has a second independent dynamic memory which is used to operate on databases that are attached to the execution This memory is typically much smaller than the working memory The main factor influencing the amount of database memory required is the block size used by the active databases This is described in detail in subsequent sections The working memory for ASTROS is dynamically acquired during execution The amount of space that is actually used by the program is typically controlled by the ASTROS execution procedure or the MEMORY Executive Control command Some host computers have alternate means of controlling this memory ASTROS RUNNING ASTROS 2 5 USER S MANUAL 2 1 6 The eBase Database With ASTROS Version 13 UAI introduced the Engineering Database Management System eBase into ASTROS This advanced scientific database technology greatly enhances the data handling capabilities of ASTROS compared with the older CADDB database found in the original ASTROS program 2 1 6 1 The Two Types of Databases There are two types of eBase databases in ASTROS The first type is the run time database or RUNDB This database is used to store the relations and matrices which are used in performing your anal
508. y be combined with RLOAD1 loads only by specification on a DLOAD entry That is the SID on a RLOAD2 entry may not be the same as that on a RLOAD1 entry 2 SID must be unique for all RLOAD1 RLOAD2 TLOAD1 and TLOAD2 entries 7 210 THE BULK DATA PACKET ASTROS USER S MANUAL Input Data Entry RROD RROD Rigid Rod Description Defines a pin ended rod that is rigid in extension Format and Example I 2 3 4 5 6 7 8 9 10 RROD SETID EID GA GB CMA CMB RROD 1001 14 a 2 2 Field Contents SETID Multipoint constraint set identification number specified in Solution Control Integer gt 0 EID Rigid Rod element identification number I nteger gt 0 GA GB Grid point identification numbers of connection points Integer gt 0 CMA Component number of one and only one dependent degree of freedom in the global CMB coordinate system assigned by the element at either grid point Ga or GB Integer 1 2 or 3 either CMA Or CMB may contain the digit and the other must be blank Remarks 1 The RROD entry is selected in the Solution Control with the MPC SETID option of the BOUNDARY command THIS IS AN ENHANCEMENT TO THE NASTRAN METHOD WHICH DOES NOT ALLOW RIGID CONNECTIONS TO BE CHANGED FOR DIFFERENT BOUNDARY CONDI TIONS 2 The degree of freedom selected to be dependent must have a nonzero component along the axis of the rod which also implies that the rod must have a finit
509. y be used to direct the ASTROS procedure All the engineering utility and matrix manipulation modules shown in Subsection 4 4 2 1 are available to any MAPOL sequence used to direct the system In addition there are a number of intrinsic functions such as SIN and ABS that are also available Their use is detailed in the MAPOL Program ming chapter The sophisticated MAPOL user is thus provided with a very flexible control language to 4 20 THE EXECUTIVE SYSTEM AND MAPOL ASTROS USER S MANUAL manipulate the ASTROS system This Section describes simple modifications to the standard algorithm to print out additional data items to fine tune the optimization algorithm and to restore an ASTROS analysis that was partially executed on a previous run No set of examples however can possibly indicate the full range of available capabilities the user is therefore cautioned not to be overly con strained by this discussion In order to avoid vast quantities of output and to limit the execution time the standard output is kept to a minimum Several utilities listed in Section 4 4 2 1 can however be inserted in the standard sequence to output data stored on the database In addition a utility has been written to print out the structural set definition table to aid in the debugging of the structural model The UTMPRT UTGPRT UTRPRT and UTUPRT print utilities dump the contents of specified database entities to the user s output file These can be used
510. ysis task At the end of your job the RUNDB may be deleted The second type is the archival database This type of database represents any eBase database that you wish to use during an ASTROS execution The database may be created by ASTROS or by a second application which uses the eBase applib or matlib Applications Programming Interface API 2 1 6 2 The Logical and Physical Views of the Database To fully understand the database technology you must understand the two views of the database Each database is called a logical database This term is used because from an engineering viewpoint the database is a single entity which is used in its entirety The manner in which the logical database is stored on your host computer depends on the amount of data it contains and the availability of disk storage devices The physical view is a mapping of a logical database to some number of physical files on your host computer It may be necessary for you to understand the physical model because for very large analyses it may be more efficient to organize the actual files in a manner that allows higher performance on your host 2 1 6 3 The Physical Model Each eBase database regardless of its use has two components manifested as a minimum of two physical files The first of these components is called the INDEX component This component is always a single physical file It contains information which identifies and locates actual database entities These

ASTROS User`s Reference Manual for Version 20.

Contents

Download Pdf Manuals

Related Search

Related Contents