Post

(1)

POST User Manual

Version 13.0

ANSYS, Inc. is certified to ISO 9001:2008 ANSYS, Inc. Southpointe 275 Technology Drive Canonsburg, PA 15317 [email protected] http://www.ansys.com (T) 724-746-3304 (F) 724-514-9494

(2)

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Revision Information

The information in this guide applies to all ANSYS, Inc. products released on or after this date, until superseded by a newer version of this guide. This guide replaces individual product installation guides

from previous releases.

Copyright and Trademark Information

© 2010 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited. ANSYS, ANSYS Workbench, AUTODYN, CFX, FLUENT and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in the United States or other countries. ICEM CFD is a trademark used by ANSYS, Inc. under license. All other brand, product, service and feature names or

trademarks are the property of their respective owners.

Disclaimer Notice

THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFIDENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS

SUBSIDIARIES, OR LICENSORS. The software products and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement that contains provisions

concerning non-disclosure, copying, length and nature of use, compliance with exporting laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products and documentation may be used, disclosed, transferred, or copied only in accordance with the

terms and conditions of that software license agreement. ANSYS, Inc. is certified to ISO 9001:2008

U.S. Government Rights

For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use, duplication, or disclosure by the United States Government is subject to restrictions

stated in the ANSYS, Inc. software license agreement and FAR 12.212 (for non-DOD licenses).

Third-Party Software

The products described in this document contain the following licensed software that requires reproduction of the following notices.

Formula One is a trademark of Visual Components, Inc.

See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software and third-party software. If you are unable to access the Legal Notice, please

contact ANSYS, Inc.

(3)

POST User Manual

Update Sheet for Version 13.0

November 2010

Modifications:

The following modifications have been incorporated:

(4)

_i

POST User Manual

TABLE OF CONTENTS

1. Introduction ... 1-1

1.1. General Description ... 1-1

1.2. Facilities Available ... 1-2

1.2.1. Shell Elements ... 1-2

1.2.2. Laminated Shell Elements ... 1-3

1.2.3. Beam Elements ... 1-3

1.2.4. Axisymmetric Solid and Shell Elements ... 1-3

1.2.5. Harmonic Solids... 1-3

1.3. Program Requirements... 1-4

1.4. Element Grouping ... 1-4

1.5. Loadcase Combination... 1-5

1.6. Local Axes Consideration ... 1-5

1.6.1. Local Axes for SHELL, LAMI and SBEAM Data ... 1-5

1.6.2. Local Axis for BRICK Data ... 1-6

1.6.3. Output Axes Definition ... 1-6

1.6.4. Averaging Groups with Differing Output Systems ... 1-13

1.6.5. Material Axes for Laminated Shells ... 1-14

1.7. Processing of Summed Out-of-Plane Shear Forces for the TRB3 Element

1-15

1.8. Boundary Conditions for Harmonic Runs ... 1-16

1.9. UNITS ... 1-16

2. INPUT Data ... 2-1

2.1. General Principles ... 2-1

2.1.1. Special Symbols ... 2-3

2.2. UNITS Command ... 2-9

2.3. Data Type Commands... 2-11

2.3.1. Data Type and Sub-Type Commands ... 2-11

2.4. Output Axis Commands ... 2-13

2.4.1. CONS Command (SHELL or SBEAM data) ... 2-13

2.4.2. OUTP Command (SHELL data only)... 2-14

2.4.3. OUTR Command (SHELL data only) ... 2-15

2.4.4. OUTT Command (SHELL data only) ... 2-16

2.4.5. OUTB Command (SBEAM data only) ... 2-16

2.4.6. SKEW Command (SHELL data only) ... 2-17

2.5. Group Data Commands... 2-18

2.5.1. LAYE Command (LAMI data only)... 2-18

2.5.2. RDAT Command ... 2-20

2.5.3. TCRD Command ... 2-21

2.6. Group/Element Selection Commands ... 2-22

2.6.1. GROU Command... 2-22

2.6.2. EXTR Command ... 2-23

2.6.3. SKIP Command ... 2-24

2.6.4. NOAV Command ... 2-25

2.6.5. AVGR Command... 2-26

2.7. Loadcase Combination Commands ... 2-27

2.7.1. NEWC Command ... 2-27

2.7.2. ADDC Command... 2-28

(5)

_ii

POST User Manual

2.7.3. ADDF Command ... 2-29

2.8. Stress Type Selection Commands ... 2-31

2.8.1. FACT Command ... 2-31

2.8.2. AVST Command ... 2-31

2.8.3. FANM Command (SHELL data only) ... 2-32

2.8.4. BANM Command (SHELL data only) ... 2-33

2.8.5. PRST Command ... 2-34

2.8.6. PRVM Command... 2-35

2.8.7. SHRS Command (SHELL data only) ... 2-36

2.8.8. WOOD Command (SHELL data only)... 2-37

2.8.9. REIN Command (SHELL data only) ... 2-38

2.9. Control Output Commands ... 2-39

2.9.1. PRIN Command ... 2-39

2.9.2. PLOT Command ... 2-40

2.10. Check Stresses ... 2-41

2.10.1. FECS and FECM Commands (SHELL data only) ... 2-41

2.10.2. VONM Command ... 2-42

2.10.3. TRES Command ... 2-43

2.11. Harmonic Combination Commands ... 2-44

2.11.1. Data for Harmonic Analyses ... 2-44

2.11.2. ANGL Command (HARM Data only) ... 2-45

2.11.3. COMB Command (HARM data only) ... 2-45

2.11.4. SELE Command (HARM data only) ... 2-46

2.11.5. COS and SIN Commands (HARM data only) ... 2-47

2.12. Miscellaneous Commands ... 2-49

2.12.1. SECT Command ... 2-49

2.12.2. ANGL Command (SHELL data only) ... 2-50

2.12.3. END Command ... 2-50

3. Examples ... 3-1

3.1. Example 1: Default Data ... 3-1

3.2. Example 2: Simple Shell Result Processing ... 3-1

3.3. Example 3: Simple Axi-symmetric Result Processing ... 3-2

3.4. Example 4: Post Processing Component Results from Multi Level

Axisymmetric Analysis ... 3-3

3.5. Example 5: Loadcase Combinations ... 3-4

3.6. Example 6: Post Processing Harmonic Analyses ... 3-5

3.7. Example 7: Harmonic Combinations ... 3-6

3.8. Example 8: Post Processing Shell Compatible Beams ... 3-7

3.9. Example 9: Post Processing Laminated Shells ... 3-8

4. Output ... 4-1

4.1. Printed Output ... 4-1

4.1.1. SHELL Data... 4-1

4.1.2. LAMI Data ... 4-2

4.1.3. Shell BEAM Data ... 4-2

4.1.4. BRICK, AXIS and HARM Data ... 4-2

4.2. Backing Files ... 4-2

4.3. Plotting Program Input ... 4-3

4.3.1. FEMVIEW Input ... 4-3

4.3.2. PATRAN

®

Input ... 4-4

Appendix A -

Preliminary Data Block for POST ... A-1

(6)

_iii

POST User Manual

A.1 Introduction ... A-1

A.2 SYSTEM Command ... A-2

A.3 PROJECT Command ... A-2

A.4 JOB Command ... A-3

A.5 FILES Command ... A-3

A.6 TITLE Command ... A-3

A.7 TEXT Command ... A-4

A.8 STRUCTURE Command... A-4

A.9 COMPONENT Command ... A-5

A.10 NEWSTRUCTURE Command ... A-6

A.11 OPTIONS Command ... A-6

A.12 SAVE Command ... A-8

A.13 RESU Command ... A-9

A.14 UNITS Command (not valid for fixed format ASAS data) ... A-9

A.15 END Command ... A-10

Appendix B -

- Running Instructions for POST ... B-1

B.1 ASAS Files Required by POST ... B-1

B.2 Running Instructions for POST ... B-1

Appendix C -

- Equations used for Stress Calculations ... C-1

C.1 Notation... C-1

C.2 Stress Formulae ... C-2

C.3 Wood-Armer Calculations ... C-3

C.3.1 Wood-Armer Moments - Orthogonal Reinforcing ... C-3

C.3.2 Wood-Armer Moments - Skewed Reinforcing ... C-4

C.4 Reinforcement Area Calculations ... C-4

Appendix D -

- Loadcase Combination Methods ... D-1

(7)

Introduction

POST User Manual

Page 1-1

POST

Post-processing for ASAS Stress Output

1. Introduction

1.1. General Description

POST is a general post-processing program designed to aid the engineer using ASAS to analyse shell, solid and three-dimensional axisymmetric structures. It performs many tedious tasks on the ASAS results such that the engineer can concentrate on the design of his structure without the need to waste precious man time in repetitive arithmetic calculations.

ASAS and LOCO finish by printing stresses and/or moments for each node of each element and storing these on a backing file. POST reads these stresses from the backing file and averages the stresses given by all the elements at each node. From these, surface, principal, von-Mises, Tresca, section stresses and Wood-Armer moments may be calculated and printed depending on the processing requested and the element type. These and other facilities are described fully in the next section.

Note that if POST is to be run, the command SAVE LOCO FILES must be included in the preliminary data of the previous ASAS or LOCO run, so that the appropriate files will be retained for use by the program.

The program will also convert stress results into a suitable format ready for plotting using FEMVIEW or PATRAN®*.

To produce an interface file for one of these plotting programs, SAVE commands must be given in the POST preliminary data (see Appendix A-). In addition, the run results may be saved permanently on the project files using the RESU command.

Note that the BR32 element is not available with FEMVIEW at present. * PATRAN® - a corporate trademark of the MSC Software Corporation.

(8)

Introduction

POST User Manual

Page 1-2

1.2. Facilities Available

POST has six different processing paths depending on which type of element is being considered. The process required is selected by the user and causes POST to processes only those elements of the correct type in the model. Thus an analysis having a number of differing element types will require more than one run of POST to post-process the whole model. The processes are identified by data type as follows:

Data Type Command

Element Family Elements

SHELL thick & thin shells plate membranes sandwiches triangular plate QUS4 TCS6 TCS8 GCS6 GCS8 TBC3 SLB8 QUM4 QUM8 TRM3 TRM6 SND6 SND8 SN12 SND16 TRB3

LAMI laminated shells QUS4 TCS6 TCS8

SBEAM shell compatible beams GCB3 TCBM

BRICK bricks BRK6 BRK8 BR15 BR20 BR32 TET4 TE10

AXIS SOLID AXIS SHELL axisymmetric solids axisymmetric shells QUX4 QUX8 TRX3 TRX6 ASH2 HARM SOLID HARM SHELL

harmonic axisymmetric solids harmonic axisymmetric shells

QHX4 QHX8 THX3 THX6 AHH2

Only one data type command may be submitted in each run; other data type commands will be ignored.

Restriction: When using SAVE FEMS or SAVE PICA, only one of the shell element families may be processed in each run. The GROU command should be used to restrict the element type(s) to those associated with one of the SHELL families. (Note that thick and thin plates are considered as one element family).

1.2.1. Shell Elements

For Shell elements, top, middle and bottom surface stresses are calculated for each element in turn, and a set of average stresses is calculated for each node which is associated with two or more elements. The outshears for plate and shell elements, with the exception of the TRB3 element, may also be averaged by using the SHRS command.

The in-plane principal stresses ( 1 and 2) are printed for each of the three surfaces along with the principal

stress difference ( 1 - 2). Two ‟check stresses‟ can be provided by the user, against which the stresses at each

node can be compared and flagged if they exceed the check stress. As an aid to results interpretation, asterisks are used to highlight the highest absolute values of 1, 2 and ( 1 - 2) for each surface.

(9)

Introduction

POST User Manual

Page 1-3

1.2.2. Laminated Shell Elements

The nodal stresses in and normal to the fibre direction and also the inshear stress are calculated for individual laminae from the resultant strain for the whole composite section. Where a node is associated with more than one element in the same group the strains for the whole composite section will be averaged at the node prior to the layer stresses being calculated.

1.2.3. Beam Elements

Results for TCBM and GCB3 elements are processed in terms of member forces and moments. Where a node is associated with more than one element within the same groups the averaged results will be presented. The user may also specify a new output axes for the elements to override the default element local axes.

1.2.4. Axisymmetric Solid and Shell Elements

The program calculates average nodal stresses for the solid elements. The user may print the averaged nodal stresses for any or all of the loadcases, each factored by a constant if required. In addition to the average nodal stresses the program prints the von Mises equivalent stress for each node and the factor by which this stress exceeds a user defined allowable level.

The user may also request a printout of principal stresses and directions for any or all of the loadcases, again factored by a constant if required. In addition to the principal stresses and directions, the program prints the sum of the principal stresses, the von Mises equivalent stress, the Tresca stress and the factor by which the Tresca stress exceeds a user defined allowable level.

For axisymmetric solids only, the user may request additional information for the stresses across a specified section of the structure. This comprises the average „membrane‟ stress components across the section and the bending stress components at each node across the section. The principal membrane stresses are also printed along with the corresponding stress intensities.

1.2.5. Harmonic Solids

Additional features of POST permit the calculation of the average nodal stresses for the harmonic solid elements THX3, QHX4, THX6 and QHX8. The user may generate a number of combined loadcases from structures with different harmonic numbers (analogous to the manner of operation of LOCO) and produce stress output at a number of angular stations around the structure for these combined loadcases. This allows the user to perform Fourier series types of analysis for known harmonics of load at substantially less cost than would be involved in a full three dimensional (brick) analysis.

(10)

Introduction

POST User Manual

Page 1-4

In order to identify the combined results being created, a new structure name is required and this is defined using the NEWSTRUCTURE command in the preliminary data. If the set of files for the combined loadcases has been saved and additional POST runs on the same load cases are needed, a harmonic re-run with simplified data input requirements may be performed. In the re-run, the structure name becomes the new structure name in the original run with the NEWSTRUCTURE command omitted. All the loadcase combination data are also omitted. Average nodal stresses at each circumferential station, von Mises equivalent stress and the factor by which it exceeds a user defined allowable are printed.

Principal stresses may be produced in an analogous manner to the purely axisymmetric values described above. Currently the facility to produce extra information about stresses across specific sections is not available with the harmonic elements.

1.3. Program Requirements

The program works directly from backing files created during an ASAS or LOCO run. The files described must be saved using the appropriate commands described in the User Manuals. All other information is provided via the data commands described in detail in Chapter 2 Any elements other than those allowed for the data type specified in Section 1.2 are ignored by the program; however, at least one of these elements types must be encountered.

For an axisymmetric job all the elements are not only axisymmetric themselves but the loading is also axisymmetric. For harmonic analyses the program checks that the user specified harmonic number on all the harmonic elements accessed from an individual ASAS structure have the same harmonic number. Clearly, a structure with a mixed harmonics in a loadcase is physically meaningless as discontinuities in displacements are implied.

1.4. Element Grouping

It may not always be desirable, or even meaningful, to average the nodal stresses of adjacent elements. For example, where there are different material properties or thicknesses between elements, the strains may be continuous but there will be step changes in the stresses. If the nodal stresses are averaged at such discontinuities, these step changes will be lost and a false average obtained.

For this reason, POST considers the elements in groups. These groups may be made up of one ASAS element group (i.e. the groups defined in the ASAS element topology data), or of elements defined by a list of element numbers in the POST data. In the case of the former, individual elements may be omitted from a group by using the SKIP command in the POST data. Note that if EXTR groups are created in POST, then the CREATE Command should be used on the SAVE FEMS line.

POST works through the groups in order, considering all loadcases for one group before moving on to the next. Within the groups, all nodal stresses are averaged, but no averaging occurs across the group boundaries.

(11)

Introduction

POST User Manual

Page 1-5

If a group contains a mixture of more than one sub-type, e.g. shells, plates and membranes, then POST will only process elements with the same type as the first valid element found for that group (i.e. shell, membrane or plate). If other element types are required from a group then new groups can be created using the EXTR command (Section 2.6.2) containing only the element types required.

In SHELL data, should any thickness discontinuity be encountered between adjacent elements within a group, an error message is printed and POST moves on to the next group. The allowable tolerance is 1% difference in thickness at each node. It is possible to override this error by a warning if option CCGO is specified in the preliminary data.

For SHELL and SBEAM data, a check is also provided to ensure the offset compatibility between adjacent elements within a group. An error message is printed if this check fails and POST moves on to the next group. As before, it is possible to change the error status to warning status by specifying option CCGO in the preliminary data.

For LAMI data, strains rather than stresses are averaged. Nodal thickness however, is used in the calculation of the individual lamina stresses and so once again there may not be nodal discontinuities within a group. Additionally all the elements within the group must have a consistent ASAS material axes and composite layer data in order that the layer stresses are calculated correctly from the averaged strains. Further consideration of the ASAS material orientation is given in Section 1.6.5.

1.5. Loadcase Combination

The program allows the user to create new loadcases by factoring and combining any or all of the existing loadcases, including new loadcases already created. Average nodal stresses and principal stresses may be printed for these combinations as well as for the original loadcases. A number of combination methods are available in addition to simple summation. These are described in detail in Appendix D-.

1.6. Local Axes Consideration

1.6.1. Local Axes for SHELL, LAMI and SBEAM Data

ASAS nodal stresses are calculated in the element local axis system for some shell elements and the shell beam elements. In cases where the element local axis systems of adjacent elements within an element group are not consistent (that is, the same orientation with respect to the global axis system), it is not meaningful to average nodal stresses across element boundaries. In such cases it is possible to reorientate the stresses into a consistent set before averaging by specifying a new axis system, called the output axis system, which is common to all elements within the group. The new output axis systems are defined by the OUTP, OUTR, and OUTT commands for shell elements and the OUTB command for the shell beam elements.

Whilst an output command must be used for any group containing elements with inconsistent axes they may also be used whenever the user simply wants to reorientate the output axes. If an output command is not used for a

(12)

Introduction

POST User Manual

Page 1-6

given group, then the CONS command should be used for that group, indicating the axes are consistent. POST is not able to check for axes consistency, so if CONS is used it is the user‟s responsibility to satisfy himself that the axes are consistent.

For laminated shells the strains used to calculate the individual layer stresses are once again in the element‟s local axes system. In this case the output orientation of the results is already predefined by the fibre orientation for each layer which in turn is related to the material axes of each each element. POST automatically converts the ASAS strains into the material axes before the nodal averaging, and then further rotates the strains into the fibre direction for each of the individual layers examined.

1.6.2. Local Axis for BRICK Data

In the case of brick and axi/harmonic elements, the ASAS results are in the global axis system and therefore consistent. For this reason there are no commands for reorientating stresses for these element types.

1.6.3. Output Axes Definition

(a) Cartesian Axes System - OUTP Command

The cartesian axes are defined in terms of a reference direction and a reference point. Firstly, the top and bottom surfaces of the shell are defined. This is done by drawing a vector from the reference point towards the node in question. This is called the control vector. The first surface cut by the control vector is defined as the bottom surface, and the second as the top surface. The new Z axis at this node is normal to the shell and positive in the direction from the bottom surface towards the top surface. See Figure 1.

The new X axis lies in the plane containing the new Z axis and the reference direction: note that the reference direction is specified by direction cosines with respect to the global axis system. The X axis is positive on the side of the Z axis containing the positive reference direction. The new Y axis forms a right-handed set with the new X and Z axes. See Figure 2.

The above rules break down in two cases. The first is where the reference direction and the new Z axis are parallel and the second where the control vector is tangential to the shell surface.

In both cases, warnings are printed when the control vector is within 5 of the shell surface tangent. Errors are printed should the angle be less than 1 . In the case of an error the node in question is omitted.

(13)

Introduction

POST User Manual

Page 1-7

(14)

Introduction

POST User Manual

Page 1-8

Example: Cylindrical Shells

Consider a cylindrical shell of diameter 10 and length 100 orientated parallel to the Z axis with its central axis at X=5, Y=0. A suitable output axes may be specified by a reference direction parallel to the central axis and the reference point on the central axis halfway along the cylinder.

Figure 3

The reference point could be anywhere within the boundary of the tube, but the central location ensures the least chance of failing the 5º check. The resulting output axes system has the outer surface of the cylinder as the top surface, the local x‟ stress in the longitudinal direction and the local y‟ stress in the hoop direction.

(15)

Introduction

POST User Manual

Page 1-9

Example: Flat Shells/Plates

For a flat plate the ideal position for the reference point is on the plate normal through the centre of the plate at a distance equivalent to half the plate length below the plate. Again the exact position is not critical. The reference direction should then be defined in the plane of the plate in the direction required for the local x‟ stress.

Figure 4

In some cases it may be desirable to use the same output axes definition for a series of plates. If the reference point is placed between plates this will result in a reversal of the local y‟ direction. This may not be significant for stress results but will affect the definition of the skew angles for Wood-Armer moments and reinforcement area calculations. Figure 5

2 L

y ' x' x' y ' Reference point x' y ' Reference point x' y ' B T T B T B T B

(16)

Introduction

POST User Manual

Page 1-10

(b) Radial Axes System - OUTR Command

The cartesian axes definition cannot be used to give radial and hoop stresses for a flat circular disc. In order to cover this case the radial axes definition may be used. These axes are defined by two points, the first is the centre point for the radial axes system and the second is a reference point as for the cartesian axes system. A reference direction is set up for each individual node within the group and is defined by the vector from the node to the centre point. The local axes system for the node is then set up from the reference direction and the reference point using the same conventions as for cartesian axes definition. See Figure 6.

At the centre of the disc the centre point may coincide with the central node, such that a reference direction is not defined. In this case (and also if the reference direction defined is normal to the shell) the local X will be defined as lying in the plane containing the local Z (or shell normal) and the global ordinate that is most normal to the local Z. In the case of the local Z being normal to two global ordinates, the global X would be used as first preference and the global Y as the second. The local Y is then defined normally to both local X and Z.

Figure 6

Reference Direction for Node 1

(17)

Introduction

POST User Manual

Page 1-11

Example: Hemispherical Shell/Disc

For a hemispherical shell the reference point should be placed at or near the centre of the hemisphere (at zero radius) and the centre point on the hemisphere at the centre.

In the case of a flat disc the reference point should be positioned on the axis of the disc at a distance equivalent to the radius of the disc below the disc.

Figure 7

In both cases the local y‟ stress will be in the hoop direction. For the hemispherical shell the local x‟ stresses will be in the longitudinal direction and for the flat disc in the radial direction.

(18)

Introduction

POST User Manual

Page 1-12

(c) Toroidal Axes System - OUTT Command

The toroidal axes system is used to give hoop and longitudinal stresses for torus shaped structures. These axes are defined by the coordinates of the torus centre point, the direction cosines for the major axes and the major radius. For each node a radial slice is made through the torus at the position of the node. The axes reference point for the node is then defined as being on the circular minor axis at the position of the slice, and the reference direction as tangential to the circular minor axis at the same point. The reference direction is positive in the positive sense of the minor axes which itself follows a right hand screw rule with the direction cosines defining the major axes. The local axes system for the node is then set up form the reference direction and reference point using the same conventions as for the cartesian axes definition. See Figure 8.

For the toroidal axes system, the major radius may not be zero (instead the OUTP or OUTR systems should be used). Also if the node under consideration lies on the circular minor axes, the local axes for the node cannot be defined and the elements containing this node will be skipped.

Figure 8 OUTT Axes System

(19)

Introduction

POST User Manual

Page 1-13

(d) Beam Axes System - OUTB Command

The new output axes system is assumed to have the X lying tangentially along the beam element. The positive direction is defined by specifying a reference direction for the output X-axis. The positive direction along the beam is that which gives an angle in the range of ±90 with the reference direction.

A second reference direction (relating to the Z) is used to complete the output axes system. The new Y is positioned such that it is mutually perpendicular to the new X and the second reference direction, the direction forming a right handed set with the reference direction and the new X. Finally the new Z is positioned to form an orthogonal right handed axes set with the new X and Y.

Example output systems for beam elements are shown in Figure 9.

Figure 9 OUTB Axes System

1.6.4. Averaging Groups with Differing Output Systems

The AVGR command gives the user the ability to average across group boundaries with differing output axes systems. This is admissible, but the user must ensure that where the groups meet the local axes systems are aligned so that averaging is valid. Figure 10 shows a typical example of where averaging across group

Z

X Y

X

Z

Y

X Axis Reference Direction

Z Axis Reference Direction

(20)

Introduction

POST User Manual

Page 1-14

boundaries with differing output axes systems may be used. The structure consists of a cylinder (Group 1 with output system OUTP), connected to a 90 section of a pipe bend or torus (Group 2 with output system OUTT). The other end of the bend connects to a second cylinder (Group 3 with output system OUTP). Finally the second cylinder is closed with a spherical cap (Group 4 with output system OUTR). For each section, the longitudinal stress is x and the hoop stress is y. The through thickness direction for all Groups in the local Z

axis.

Figure 10 Example of Averaging Across Groups

1.6.5. Material Axes for Laminated Shells

The consistency of the material axes is a requirement for POST since the element strains are converted into the material axes prior to combination. This is usually satisfied unless different global reference axes have been defined to set up the material axes on adjacent elements. Figure 11 shows the relationship between global axes, element local axes, material axes and fibre orientation. Layers are numbered from the bottom surface of the shell element (on the negative local Z side of the element) towards the top surface.

(21)

Introduction

POST User Manual

Page 1-15

Figure 11

1.7. Processing of Summed Out-of-Plane Shear Forces for the TRB3 Element

For the TRB3 elements only, the nodal shear value obtained using the FANM command is the sum of the nodal shear force from all elements surrounding the node. This value is of limited use as it represents the outforce balancing any external force or reaction at that node and gives little indication of the internal shearing force in the plate. More useful values are obtained if the nodal shears are summed either side of a line or section defined by the element boundaries. The section may form a closed loop ie, first and last nodes identical, or may be open ended.

If the FANM/BANM/AVST and the SECT commands are present in the data, the normal output is augmented by an extra table. The summed nodal shears on each side of the section are reported for each nodal point on the section, giving two shear forces at each node. The elements which contribute to each value are also reported.

(22)

Introduction

POST User Manual

Page 1-16

These shear forces may be interpreted to give a picture of the internal shearing forces at each node on the section.

1.8. Boundary Conditions for Harmonic Runs

If the harmonic part of the program is used then each ASAS job accessed must have the same element topology data. Thus, if an analysis was to combine a purely axisymmetric structure (and load) this must be run as a harmonic job with the geometry property for the harmonic number set to 0.0. To restrain rigid body motions special suppression data are required for the harmonics 0 and 1. For harmonic 0 at least one TH ( ) degree of freedom should be removed, to prevent the structure rotating as a rigid body about the Z axis. For harmonic 1 there must be at least one R and one degree of freedom suppressed as the displaced shape implied by this harmonic corresponds to a rigid body motion of the section in the R– plane. All harmonics require at least one Z suppression, but for the harmonics 2 and above there is no need to have any R or suppressions to remove rigid body movements.

1.9. UNITS

If UNITS have been employed in the ASAS analysis it is possible to specify modified units for both the POST input data and the results. The default units will be those utilised in the original analysis and if this is satisfactory then no additional information is required in the POST data. Note, however, that the angular data

unit defaults to degrees.

If modified units for input data are required, this is achieved by specifying one or more UNITS commands within the main body of the POST data thus permitting a combination of unit systems within the one data file (see Section 2.2 UNITS command).

If the stress results are required in different units to the default, the UNITS command can be specified in the Preliminary data. See Appendix A-, Preliminary Data.

If UNITS were not employed in the ASAS analysis, the units of all data supplied must be consistent with that adopted for the original data. No modification to reported stresses is possible under these circumstances.

(23)

Introduction

POST User Manual

Page 1-17

(24)

Input Data

POST User Manual

Page 2-1

2. INPUT Data

As with most of the member programs of the ASAS suite, the input of information and data is divided into two sections. The first is the Preliminary Data and the second is the POST Data.

The Preliminary Data defines the relationship of the run to all the other runs already completed in the project, the backing files required, and also specifies the title of the run. If subsequent processing is required after POST, the data to be saved from the run must also be defined in the Preliminary Data. The full details of these commands, along with examples, are given in Appendix A- of this manual.

A summary of the POST commands available is given in Table 1. Detailed descriptions of each of the commands will be found in the remainder of Chapter 2

2.1. General Principles

The input data for POST are specified according to syntax diagrams similar to the one shown below. The conventions adopted are described in the following paragraphs.

Within a data block, each horizontal branch represents a possible input instruction. Input instructions are composed of keywords (shown in upper-case), numerical values or alphanumerics (shown in lower-case characters), and special symbols. Each item in the list is separated from each other by a comma or one or more blank spaces.

An input line must not be longer than 80 characters. Numerical values have to be given in one of two forms:

(i) If an integer is required a decimal point must not be supplied.

(ii) If a real is required the decimal point may be omitted if the value is a whole number.

Exponent formats may be utilised when real numbers are required. For example 0.004 4.0E-3 4.0D-3 are equivalent similarly 410.0 410 4.10E2 have the same value

(25)

Input Data

POST User Manual

Page 2-2

The letters A-Z may be supplied in either upper or lower case but no distinction is made between the upper and lower case form. Hence “A” is assumed identical with “a”, “B” with “b” and so on.

For example COMB are all identical strings Comb

comb

Integer lists are terminated by supplying an END command either on the last line of the integer data, or on the line immediately after. For example

GROU is the same as GROU

1 5 6 END 1 5 6 END

Note that END following immediately after the header line specifies no values. For example GROU

END

In order to reduce the amount of data required, facilities exist to abbreviate the integer lists.

(i) Where the integer list represents all items from an existing list (for example, choosing all groups for processing) the list may be replaced by the word ALL.

GROU ALL

Note that when ALL is utilised, the keyword END is omitted.

This may not be used where the integer list is to specify new items of information, for example, new loadcase numbers.

(ii) A sequence of integers may be generated by giving the first value and following this with the negative of the last value for example 5 -8 generates the numbers 5,6,7 and 8.

If a command is optional, this is shown by an arrow which bypasses the line(s)

A data list is indicated by a horizontal arrow around the list variable

HEADER

(26)

Input Data

POST User Manual

Page 2-3

Where one or more possible alternative items may appear in the line, these are shown be separate branches for each

2.1.1. Special Symbols

The following is a list of characters which have a special significance to the LOCO input.

*

An asterisk is used to define the beginning of a comment, whatever follows on the line will not be interpreted. It may appear anywhere on the line, any preceding data will be processed as normal. For example

* THIS IS A COMMENT FOR THE WHOLE LINE

case 4 2.7 * THIS IS A COMMENT FOR PART OF A LINE

’

single quotes are used to enclose some text strings which could contain otherwise inadmissible characters. The quotes are placed at each end of the string. They may also be used to provide in-line comments between data items on a given line.

For example

STRUCTURE ’As used for design study’ STRU

,

A comma or one or more consecutive blanks will act as a delimiter between items in the line.

For example 5, 10, 15 is the same as 5 10 15

list

KEYWORD1

(27)

Input Data

POST User Manual

Page 2-4

Note that two commas together signify that an item has been omitted. This may be permissible for certain data blocks.

For example 5,, 15 is the same as 5 0 15

(28)

Input Data

POST User Manual

Page 2-5

Table 1 : Summary of Commands

Units Command

Section 2.2

Command Meaning Additional Data

Required

Valid For

Note

UNIT Input units definition Unit name(s) all 1

Data Type Commands

Section 2.3

Required

Valid For

Note

SHELL SHELL None S

LAMI LAMI type data None L

SBEAM Shell BEAM type data None Sb

BRICK BRICK type data None B

AXIS AXISYMMETRIC type data Data sub-type (on new line) A

HARM HARMONIC type data Data sub-type (on new line) H

SOLID Data sub-type - SOLID elements None A H

SHELL Data sub-type - SHELL elements None A H

Output Axis Commands

Section 2.4

Required

Valid For

Note

CONS Consistent local axis system throughout elements

None Sb 2

OUTP Define cartesian output axis system

6 real numbers = 3 direction cosines, 3 coordinates

S 2

OUTR Define radial output axis system 6 real numbers = 2 sets of 3 coordinates

S 2

OUTT Define toroidal output axis system 7 real numbers = 3 coordinates, 3 direction cosines, 1 radius

S 2

OUTB Define beam output axis system 6 real numbers = 2 sets of direction cosines

Sb

SKEW Defines (non orthogonal) x, y, directions for Wood-Armer and reinforcement area calculations

(29)

Input Data

POST User Manual

Page 2-6

Group Data Commands

Section 2.5

Required

Valid For

Note

LAYE Define laminate layers to be processed

Integer list of lamina layers or ALL

L

RDAT Define data required for tensile reinforcement area calculations

4 real numbers = 2 design stresses, 2 cover depths

S 3

TCRD Define data required for

tensile/compressive reinforcement area calculations

5 real numbers = 3 design stresses, 2 cover depths

S 3

Group/Element Selection Commands

Section 2.6

Required

Valid For

Note

GROU Selection of specified ASAS groups

Integer list of ASAS groups or ALL

all

EXTR Selects extra groups of elements Integer list of user element numbers

all

SKIP Selects elements not to be considered

Integer list of element numbers all

NOAV Prevents stress averaging at nodes None all

AVGR Amalgamates groups for stress averaging

Integer list of ASAS groups or ALL

all

Loadcase Combination Commands

Section 2.7

Required

Valid For

Note

NEWC Defines new loadcase numbers Integer list of loadcase numbers all ADDC Defines loadcases to be used in

creating new loadcases

Integer list of ASAS loadcase numbers

all

ADDF Defines loadcases with specific factors used in creating new loadcases

Integer loadcase number followed by integer-real pairs for loadcase number and factor

(30)

Input Data

POST User Manual

Page 2-7

Stress Type Selection Commands

Section 2.8

Required

Valid For

Note

FACT Defines a factor to be applied to results

One real factor all

AVST Selects loadcases for processing of averaged stresses

Integer list of loadcase numbers or ALL

all

FANM Forces and Moments printout for average stresses

S

BANM Bending and membrane printout for average stresses

S

PRST Selects loadcases for processing of principal stresses

S Sb B A H PRVM Selects loadcases for processing

of von Mises stresses

S 4

SHRS Selects loadcases for processing of averaged out-of-plane shear forces

Integer list of loadcase numbers S

WOOD Selects loadcases for processing of Wood-Armer moments

S

REIN Selects loadcases for processing of reinforcement areas

S

Control Output Commands

Section 2.9

Required

Valid For

Note

PRIN Selects loadcases for printing Integer list of loadcase numbers or ALL

all

PLOT Selects loadcases for plotting Integer list of loadcase numbers or ALL

all

Check Stresses Commands

Section 2.10

Required

Valid For

Note

FECS Defines surface stress allowable One real stress value S FECM Defines mid-plane stress

allowable

One real stress value S

VONM Defines level of allowable von Mises stress

One real stress value B A H

TRES Defines level of allowable Tresca stress

(31)

Input Data

POST User Manual

Page 2-8

Harmonic Combination Commands

Section 2.11

Required

Valid For

Note

ANGL Defines angular position around structure for stress output

List of angles H 5

COMB Defines number of new loadcases One integer value H 5

SELE Define new loadcase numbers and titles List of new loadcase numbers and titles

H 5

COS Selects component loadcases and defines factors for combined cases (even expansion about =0 )

List of component loadcase numbers and factors

H 5

SIN Selects component loadcases and defines factors for combined cases (odd expansion about =0 )

List of component loadcase numbers and factors

H 5

Miscellaneous Commands

Section 2.12

Required

Valid For

Note

SECT Defines a section across which stresses are to be calculated

Integer list of ASAS group numbers, section numbers and node numbers

A S

ANGL To print the angle of the principal axes for SHELL type data or define angular location for HARM type data

None for SHELL type data. Real list of angular locations for HARM type data

S H

NAME For PATRAN, instructs POST to create stress files using the first four

characters of the name followed by a unique integer and extension, e.g. MODE0001.NOD MODE0002.NOD etc

Name of model to be created in PATRAN database e.g. MODE

all

VMPS This command defines that von Mises stress is to be calculated from principal stresses. If no VMPS command is present the von Mises stress is calculated from average stresses. Not applicable for PATRAN.

S B A H

END Terminate the run all 6

Data types: S - Shell type data Sb - Shell beam type data L - Laminated shell type data B - Brick type data A - Axisymmetric type data H - Harmonic type data

(32)

Input Data

POST User Manual

Page 2-9

Notes

1. UNIT command may only be used if units have been specified in the preceding ASAS run.

2. Only one is applicable to a group of elements, however different groups may have different output axis within the same run. If none are present then CONS is assumed.

3. RDAT and TCRD may be used in same run but must apply to different groups.

4. For shell elements von-Mises stresses are not printed but the PRVM command will cause them to be added to the plot file.

5. For HARM type jobs, these commands must follow the data sub-type command. 6. Mandatory END command: all other decks are optional subject to note 2

2.2. UNITS Command

Specifies the units associated with subsequent data. This command is only valid if UNITS were employed in the ASAS analysis (see Section 1.9).

Parameters

UNITS : keyword

unit : name of unit to be utilised (see below) Note

Force, length and angular unit may be specified. Only those terms which are required to be modified need to be specified, undefined terms will default to those of the analysis global units unless previously overwritten by another UNITS command. The default angular unit is degrees for all data types.

Valid unit names are as follows:

Length METRE(S) M

CENTIMETRE(S) CM MILLIMETRE(S) MM

FOOT,FEET FT

INCH,INCHES IN

Force unit NEWTON(S) N

KILONEWTON(S) KN

unit UNITS

(33)

Input Data

POST User Manual

Page 2-10

MEGANEWTON(S) MN TONNEFORCE(S) TNEF POUNDAL(S) PDL POUNDFORCE LBF KIP(S) KIP TONFORCE(S) TONF KGFORCE(S) KGF

Angular unit RADIAN(S) RAD(S)

DEGREES(S) DEG(S)

The UNITS command may be repeated throughout the data deck thus permitting the greatest flexibility in the data input.

(34)

Input Data

POST User Manual

Page 2-11

Example

Command

Operational Units

Notes

SYSTEM DATA AREA 50000

. UNITS do not have to . appear in the Preliminary . data, see Section 1.9 UNITS N M NEWTON, METRES, DEGREES and Appendix A-.

.

. . END

SHELL NEWTONS, METRES, DEGREES Default global analysis CONS units except that angular GROU input is in degrees

ALL

AVST ALL

UNIT MM NEWTONS, MILLIMETRES, DEGREES Stress now input in

FECS N/mm2

200.0 END

2.3. Data Type Commands

2.3.1. Data Type and Sub-Type Commands

This command defines the type of elements to be processed in the POST run and must be the first command to follow the preliminary data.

(35)

Input Data

POST User Manual

Page 2-12

Parameters

SHELL : keyword to denote that one or more of the following element types are to be processed: Shell GCS6, GCS8, TCS6, TCS8, TBC3, QUS4

Plate SLB8, TRB3

Membrane QUM8, QUM4, TRM6, TRM3 Sandwich SND6, SND8, SND12, SND16

Only one element type will be processed for each group defined (see Section 1.4)

LAMI : keyword to denote that laminated shells are to be processed: QUS4, TCS6 and TCS8 elements

SBEAM : keyword to denote that shell beam elements are to be processed: TCBM or GCB3 elements

BRICK : keyword to denote that brick elements are to be processed: BRK6, BRK8, BR20, BR32, TET4, TE10 elements

AXIS : keyword to denote that the axisymmetric elements are to be processed

SOLID : subcommand to AXIS to denote that axisymmetric solid elements are to be

processed: TRX3, TRX6, QUX4, QUX8 elements

SHELL : subcommand to AXIS to denote that the axisymmetric shell element is to be

processed: ASH2 elements

If neither subcommand is given, SOLID is assumed.

HARM : keyword to denote that the axisymmetric harmonic elements are to be processed.

SHELL LAMI BRICK AXIS SOLID SHELL SOLID SHELL HARM SBEAM

(36)

Input Data

POST User Manual

Page 2-13

SOLID : subcommand to HARM to denote that harmonic solid elements are to be processed: THX3, THX6, QHX4, QHX8 elements

SHELL : subcommand to HARM to denote that the harmonic shell element is to be processed: AHH2 elements

If neither subcommand is given, SOLID is assumed. Note

All POST runs require either SHELL, LAMI, SBEAM, BRICK, AXIS or HARM as the first command following the preliminary data; they are mutually exclusive options.

2.4. Output Axis Commands

2.4.1. CONS Command (SHELL or SBEAM data)

Specifies that the element local axis systems are consistent and that no stress reorientation is required (see Section 1.6)

Parameters

CONS : keyword

When CONS is specified, any groups referenced by subsequent GROU and EXTR group commands will be assumed to have consistent local element axis systems until a new output axis system is defined (OUTP, OUTR,

OUTT, OUTB). If no output command is supplied, CONS will be assumed.

Notes

1. A group may only be assigned one axis system within the same run. Different groups however, may have different output axis systems.

2. This command does not make elements within a group have consistent axes. If they do not already have consistent axes in the ASAS model then the CONS command must not be used otherwise invalid stress averaging will occur. In this instance one of the alternative output commands (OUTP, OUTR, OUTT,

OUTB) must be used.

Example

(37)

Input Data

POST User Manual

Page 2-14

CONS GROU

1 5 END EXTR

10 15 16 17 END

2.4.2. OUTP Command (SHELL data only)

Defines a cartesian/cylindrical output axis system into which all nodal stresses are to be converted prior to nodal averaging (see Section 1.6)

Parameters

OUTP : keyword

dx,dy,dz : direction cosines of the reference direction with respect to the global axis system. (Real) x,y,z : global coordinates of the reference point. (Real)

When OUTP is specified, any groups referenced by subsequent GROU and EXTR group commands will adopt the output axis system defined by the direction cosines and reference point until a new output axis system is defined (CONS, OUTR, OUTT, OUTP).

Note

A group may only be assigned one axis system within the same run. Different groups, however, may have different output axis systems.

Example OUTP 0.7071 0.7071 0.0 10.0 0.0 0.0 GROU 1 5 END OUTP dx dy dz x y z

(38)

Input Data

POST User Manual

Page 2-15

EXTRA

10 15 16 17 END

2.4.3. OUTR Command (SHELL data only)

Defines a radial/spherical output axes system into which all nodal stresses are to be converted prior to nodal averaging (see Section 1.6).

Parameters

OUTR : keyword

xo,yo,zo : global coordinates of the centre point. (Real) xr,yr,zr : global coordinates of the reference point. (Real)

When OUTR is specified, any groups referenced by subsequent GROU and EXTR group commands will adopt the output axis system defined by the two pairs of coordinates until a new output axis system is defined (CONS,

OUTP, OUTT, OUTR).

Note

Example OUTR 1.0 0.0 10.0 1.0 0.0 2.0 GROU 1 5 END EXTRA 10 15 16 17 END OUTR xo yo zo xr yr zr

(39)

Input Data

POST User Manual

Page 2-16

2.4.4. OUTT Command (SHELL data only)

Defines a toroidal output axes system into which all nodal stresses are to be converted prior to nodal averaging (see Section 1.6).

Parameters

OUTT : keyword

xc,yc,zc : global coordinates of centre of torus (Real) dx,dy,dz : direction cosines of major axis (Real) r : major radius (Real)

When OUTT is specified, any groups referenced by subsequent GROU and EXTR group commands will adopt the output axis system defined by the specified torus until a new output axis system is defined (CONS, OUTR,

OUTT, OUTP).

Note

Example OUTT

100.00 0.0 100.0 0.0 1.0 0.0 25.0 GROUP

2.4.5. OUTB Command (SBEAM data only)

Specifies information to determine output axis system for shell beam elements (see Section 1.6)

OUTT

(40)

Input Data

POST User Manual

Page 2-17

Parameters

OUTB : keyword

dxx,dxy,dxz : directions cosines for x-axis reference direction with respect to the global axis system. (Real) dzx,dzy,dzz : direction cosines for z-axis reference direction with respect to the global axis system. (Real)

When OUTB is specified, any groups referenced by subsequent GROU and EXTR group commands will adopt the output axis system defined by these direction cosines until a new output axis system is defined (CONS,

OUTB).

Note

Example OUTB 0.7071 0.7071 0.0 0.0 0.0 1.0 GROU 7 5 END EXTRA 10 15 16 17 END

2.4.6. SKEW Command (SHELL data only)

Defines the local axes for Wood-Armer moment and reinforcement area calculations.

OUTB

(41)

Input Data

POST User Manual

Page 2-18

Parameters

SKEW : keyword

angx : angle that local x axis makes to the output x axis (CONS, OUTP, OUTR or OUTT) (Real)

angy : angle between local y axis and local x axis. (Real). Notes

1. The WOOD/REIN commands normally assume that orthogonal axes are in use. The SKEW command allows non-orthogonal axes to be defined.

2. The angles defined are measured in a conventional right-handed system. The units are degrees. Example

SKEW

22.5 78.5

2.5. Group Data Commands

2.5.1. LAYE Command (LAMI data only)

Specifies which layers of a laminated shell are to be processed.

SKEW

(42)

Input Data

POST User Manual

Page 2-19

Parameters

LAYE : keyword

ilay : individual layers to be processed

END : keyword to denote the end of the current block of layer data. If the list of layers continues onto subsequent lines, END is required on the last line only.

ALL : keyword to denote that all layers are to be reported. END not required. Note

When LAYE is specified, any groups referenced by subsequent GROU and EXTR group commands will have the layers processed that are defined on this command. If no LAYE command is given then all layers of the groups selected will be processed.

Example LAYE 1 2 5 6 END GROU 1 2 END LAYE ALL EXTR 11 1 -20 END LAYE ilay END ALL

(43)

Input Data

POST User Manual

Page 2-20

2.5.2. RDAT Command

Specifies details of allowable stresses and cover depths for tensile (only) reinforcement calculations.

For this case it is assumed that all compressive stress is carried by the matrix (e.g. concrete) alone and all the tensile stress by the reinforcement (e.g. steel) alone.

Parameters

RDAT : keyword

rdstrs : reinforcement design stress (Real)

mdstrs : matrix design stress (Real)

cdeps : cover depths (Real) Notes

1. If cdeps is omitted the cover depth for all reinforcing will default to 10% of the shell thickness. 2. If only one cdeps value is specified, this is taken as the cover depth for all reinforcing.

3. If two cdeps values are specified, these are taken as the top and bottom surface cover depths respectively.

4. If four cdeps values are specified, these are taken as the top X and Y direction cover depths followed by the bottom X and Y direction cover depths.

5. This data applies to any groups of elements defined on subsequent GROU or EXTR commands, until superceded by further RDAT or TCRD commands.

6. RDAT and TCRD may appear in the same run but may not be for the same group of elements. RDAT

rdstrs cdeps

(44)

Input Data

POST User Manual

Page 2-21

2.5.3. TCRD Command

Specifies details of allowable stresses and cover depths for tensile/compressive reinforcement calculations. For this case it is assumed that the tensile stress is carried by the reinforcement (e.g. steel) alone, but the compressive stress is carried by both the matrix (e.g. concrete) and the reinforcement.

Parameters

RDAT : keyword

rdtstr : tensile reinforcement design stress (Real)

rdcstr : compressive reinforcement design stress (Real)

mdstrs : matrix design stress (Real)

cdeps : cover depths (Real) Notes

1. If cdeps is omitted the cover depth for all reinforcing will default to 10% of the shell thickness. 2. If only one cdeps value is specified, this is taken as the cover depth for all reinforcing.

3. If two cdeps values are specified, these are taken as the top and bottom surface cover depths respectively.

TCRD

cdeps

(45)

Input Data

POST User Manual

Page 2-22

4. If four cdeps values are specified, these are taken as the top X and Y direction cover depths followed by the bottom X and Y direction cover depths.

5. This data applies to any groups of elements defined on subsequent GROU or EXTR commands, until superseded by further RDAT or TCRD commands.

6. RDAT and TCRD may appear in the same run but may not be for the same group of elements.

2.6. Group/Element Selection Commands

2.6.1. GROU Command

Specifies the ASAS group numbers to be processed by subsequent execution commands (AVST, PRST, SHRS,

WOOD and REIN)

Parameters

GROU : keyword

igroup : ASAS group number to be processed (Integer). All the group numbers specified must exist otherwise POST will stop after data checking.

GROU

igroup END

Post

POST User Manual

Version 13.0

Revision Information

Copyright and Trademark Information

Disclaimer Notice

U.S. Government Rights

Third-Party Software

POST User Manual

Update Sheet for Version 13.0

November 2010

Modifications:

Contents

i

POST User Manual

1.

Introduction ... 1-1

1.1.

General Description ... 1-1

1.2.

Facilities Available ... 1-2

1.2.1.

Shell Elements ... 1-2

1.2.2.

Laminated Shell Elements ... 1-3

1.2.3.

Beam Elements ... 1-3

1.2.4.

Axisymmetric Solid and Shell Elements ... 1-3

1.2.5.

Harmonic Solids... 1-3

1.3.

Program Requirements... 1-4

1.4.

Element Grouping ... 1-4

1.5.

Loadcase Combination... 1-5

1.6.

Local Axes Consideration ... 1-5

1.6.1.

Local Axes for SHELL, LAMI and SBEAM Data ... 1-5

1.6.2.

Local Axis for BRICK Data ... 1-6

1.6.3.

Output Axes Definition ... 1-6

1.6.4.

Averaging Groups with Differing Output Systems ... 1-13

1.6.5.

Material Axes for Laminated Shells ... 1-14

1.7.

Processing of Summed Out-of-Plane Shear Forces for the TRB3 Element

1-15

1.8.

Boundary Conditions for Harmonic Runs ... 1-16

1.9.

UNITS ... 1-16

2.

INPUT Data ... 2-1

2.1.

General Principles ... 2-1

2.1.1.

Special Symbols ... 2-3

2.2.

UNITS Command ... 2-9

2.3.

Data Type Commands... 2-11

2.3.1.

Data Type and Sub-Type Commands ... 2-11

2.4.

Output Axis Commands ... 2-13

2.4.1.

CONS Command (SHELL or SBEAM data) ... 2-13

2.4.2.

OUTP Command (SHELL data only)... 2-14

2.4.3.

OUTR Command (SHELL data only) ... 2-15

2.4.4.

OUTT Command (SHELL data only) ... 2-16

2.4.5.

OUTB Command (SBEAM data only) ... 2-16

_i

_ii