Altair HyperMesh Interfacing with NASTRAN

Version 5.1

Contact Altair Engineering at: Web site FTP site www.altair.com Address: Login: Password: ftp.altair.com or ftp2.altair.com ftp <your e-mail address>

Location North America Germany India

Telephone 248.614.2425 49.7031.6208.22 91.80.658.8540 91.80.658.8542 39.0832.315.573 39.800.905.595 81.3.5396.1341 46.46.286.2052 44.1327.810.700

e-mail hmsupport@altair.com support@altair.de support@altair-eng.soft.net

Italy

support@altairtorino.it

Japan Scandinavia United Kingdom

aj-support@altairjp.co.jp support@altair.se support@uk.altair.com

2002 Altair Engineering, Inc. All rights reserved. Trademark Acknowledgments: HyperWorks, HyperMesh, OptiStruct, HyperForm, MotionView, HyperView, HyperGraph, HyperOpt, HyperShape/Pro, StudyWizard, HyperView Player and Templex are registered trademarks of Altair Engineering, Inc. All other trademarks and registered trademarks are the property of their respective owners.

NASTRAN Translation Overview

This section describes the HyperMesh NASTRAN input translator, output template, results translator, and summary templates. HyperMesh treats NASTRAN as a card image code. Follow these guidelines when creating a model for use with the HyperMesh NASTRAN interface: The NASTRAN interface is based on MSC/NASTRAN version 70.5. During input, the NASTRAN interface assumes that the continuation line always follows the line before, therefore no continuation cards are needed in the input file. During export, to ensure that the continuation line follows the reference card, HyperMesh writes + or * as a continuation card. Warnings and error messages are written to a file called nastran.msg. The lines that are unrecognized by the translator are written to a *.hmx file. These files are created in the same directory from which HyperMesh is launched. The HyperMesh NASTRAN input translator supports single, double, free, and fixed formats. The input translator does not import data that is in tab delimited fields. Two templates are available for export and viewing (editing) NASTRAN cards. The nastran/general template outputs all cards in single precision, fixed format. The nastran/generallf template outputs GRID, property and material cards in fixed, double precision format with all other cards in fixed, single precision format.

Note:

Before exporting or editing NASTRAN cards, a NASTRAN template must be loaded into HyperMesh.

See Also Import and Export Components Control Cards Coordinate Systems Elements Groups hmnast Utility hmnasto2 Utility hmnastf06 Utility hmnastopt Utility Working with Comment Cards Load Collectors Loads Mass Calculation Materials Multi-point Constraints Nodes Properties Results Translation Sets Summary Templates Supported Cards Templates Vector Collectors and Vectors

Altair Engineering

Interfacing with NASTRAN

Importing and Exporting a NASTRAN File

HyperMesh imports NASTRAN files using an internal reader called NASTRAN that is selected in the import panel. HyperMesh exports NASTRAN files using an internal program (template) called general (short fixed format) or generallf (long fixed format). This template is selected in the export panel.

To import a NASTRAN file into HyperMesh:

1. Select the files panel. 2. Click import. 3. Click FE (if not already selected). 4. Select NASTRAN. 5. In the filename window, enter the directory and the name of the file to be read. 6. Click import.

To export a NASTRAN file from HyperMesh:

1. Select the files panel. 2. Click export. 3. Double click template. 4. Click NASTRAN. 5. Select either general (for short fixed format) or generallf (for long fixed format). 6. In the filename window, enter the directory and the name of the file to be written to. 7. Click write.

Supported Cards
The NASTRAN interface supports the following cards. The cards are grouped with their corresponding HyperMesh entity. Components Control Cards Coordinate Systems Elements Groups Load Collectors

Interfacing with NASTRAN

Altair Engineering

Load Steps Loads Materials Multi-point Constraints Nodes Properties Sets Vectors and Vector Collectors

Control Cards
NASTRAN Keyword DIAG ID SOL TIME TITLE SUBTITLE MAXLINES PARAM The maximum number of lines is 999999999 (NASTRAN default). The following parameters are supported: ASING, AUTOSPC, BAILOUT, COUPMASS, CURV, CURVPLOT, DDRMM, EPPRT, EPZERO, GRDPNT, K6ROT, MAXRATIO, MPCX, NEWSEQ, OLDSEQ, OUNIT2, POST, PRGPST, SPCGEN, TINY, USETPRT, WTMASS. Only real number sets can be created using control cards. For node and element sets, see Sets. CEND, BEGIN BULK, ENDDATA ACMODL When the model is created from HyperMesh, the cards are on by default. The cards can be turned on or off individually. Notes

SET

To create a control card:

1. From the BCs page, select the cntl cards panel. 2. Click the NASTRAN control card to be created. 3. Type in the necessary information for the control card you are creating. 4. Click return.

Altair Engineering

Interfacing with NASTRAN

Coordinate Systems
NASTRAN Keyword CORD1R CORD2R CORD1C CORD2C CORD1S CORD2S NOTE Only CORD2R, CORD2C, and CORD2S card images are supported. Supported on feinput only. Converted to CORD2S on export. Supported on feinput only. Converted to CORD2C on export. Notes Supported on feinput only. Converted to CORD2R on export.

To create a coordinate system card:

1. Ensure that at least three nodes are available to create a coordinate system. 2. Select the systems panel on the BCs page. 3. Select the create subpanel. 4. Click origin. 5. Pick the node that defines the origin. If the nodes are not displayed, use the temp nodes panel to add pick handles to the nodes. 6. Pick the node that defines the x direction. 7. Pick the node that defines the xy plane. 8. Select the coordinate system type you want to create: rectangular, spherical, or cylindrical. 9. Click create. 10. Click return. NOTE HyperMesh automatically assigns a system ID. For cylindrical and spherical systems, the x-axis defines the radial direction ( = 0) and the xy plane defines the r- plane.

To assign a CID to a load:

1. Select the systems panel on the BCs page. 2. Select the assign subpanel. 3. Click the upper switch and select loads. 4. Pick the loads that need to be referenced to this coordinate system. 5. Click system. 6. Pick the coordinate system from the graphics window.

Interfacing with NASTRAN

Altair Engineering

7. Click set reference. 8. Click return. NOTE You can also assign a load to a local coordinate system by choosing the local system switch in the forces, moments, velocities, or accel panel when creating these loads.

Nodes
NASTRAN Keyword GRID SPOINT Notes Permanent single point constraint field supported for feinput only. On export, equivalent SPC cards are output. In HyperMesh 5.1, SPOINT is supported the same way GRID is supported. You have the choice of placing SPOINT anywhere in the model.

To create a GRID card:

1. Select the create nodes panel on the geom page. 2. Select the type in subpanel and enter the coordinate values for the node. 3. Click create node. 4. Click return. NOTE If a local coordinate system has been defined previously, you can define the node in a reference coordinate system by specifying the ID of the system in the system = field before clicking create.

To assign a CP ID to a GRID card:

1. Select the systems panel on the BCs page. 2. Select the assign subpanel. 3. Click the upper switch and select nodes. 4. Pick the nodes that need to be defined in this coordinate system. 5. Click system. 6. Pick the coordinate system. 7. Click set reference. 8. Click return.

Altair Engineering

Interfacing with NASTRAN

To assign a CD ID to a GRID card:

1. Select the systems panel on the BCs page. 2. Select the assign subpanel. 3. Click the upper switch and select nodes. 4. Pick the nodes that have dof directions defined using this coordinate system. 5. Click system. 6. Pick the coordinate system. 7. Click set analysis. 8. Click return.

To create a SPOINT card:

SPOINT is supported the same way GRID is supported. 1. Select the create nodes panel on the geom page. 2. Select the type in subpanel and enter the coordinate values for the node. 3. Click create node. 4. Click return. 5. Click card. 6. Choose Node (if not already chosen). 7. Click on the node designated to be SPOINT 8. Click edit. 9. Check SPOINT box. 10. Click return.

Materials
Some of the material data cards provided by NASTRAN can be created by loading and editing the appropriate card images in HyperMesh. These card images have the same name as the corresponding cards. NASTRAN Keyword MAT1 MAT2

Interfacing with NASTRAN

Altair Engineering

MAT4 MAT8 MAT9 MAT10

To create a MAT card:

1. Select the collectors panel. 2. Select the create subpanel. 3. Click the upper switch and select mats. 4. Click name = and enter the name for the material collector. 5. Click card image =. 6. Select the card image type. 7. Click create/edit. 8. Enter the relevant data for the MAT card. 9. Click return.

Properties
The property data cards for NASTRAN 1-D elements (beams, bars, rods, spring, and so on) can be created by loading and editing card images into property collectors in HyperMesh. For Shell and Solid element properties see Components. NASTRAN Keyword PBAR PBARL PBEAM PBEAML PBEND PDAMP PELAS PROD PTUBE Blank fields are not supported for intermediate stations. Appropriate default values are inserted during feinput. Blank fields are not supported for intermediate stations. Appropriate default values are inserted during feinput. Notes

Altair Engineering

Interfacing with NASTRAN

PGAP PBUSH PWELD HM_ELAS NOTE See Using HM_ELAS Only one card image can be loaded into each property collector. 1-D elements can be grouped into components with 2-D and 3-D elements for display purposes. The component groupings are maintained on export and import. To assign 1-D elements to property collectors, select the property collector from property = in the appropriate 1-D element panel. Properties for PBAR and PBEAM cards can be manually input in the card image or automatically created using the HyperBeam module. See the HyperBeam on-line help for more information.

Using HM_ELAS
Note NASTRAN users should consider using the PBUSH property card instead of HM_ELAS.

The HyperMesh spring entity is a single dof and single spring constant finite-length element. HM_ELAS property cards can be used to convert single HyperMesh spring elements into a group of zero-length springs and rigids. Six dofs are defined in a single property card, and the springs in this group are created as zero-length to avoid some of the common modeling errors caused by finitelength springs. The following diagram illustrates how a single HM_ELAS spring element converts to a NASTRAN bulk data file:

As shown above, the single spring element in HyperMesh writes a group of rigids and springs. On export, the following occurs: 1. A new node is created (Node 3) which is coincident with Node 2. The new node references the same local coordinate system as Node 2. 2. An RBE2 element is created, with 6 DOFS fixed, between Node 1 and Node 3. 3. Up to six zero-length elements are created, between Node 2 and Node 3, based on the following settings in the HM_ELAS property card:

Interfacing with NASTRAN

Altair Engineering

If the DOF is a value you set, a CELAS2 element is created for that DOF, with the K field equal to the supplied value If the DOF is set to RIGID, an RBE2 element is created, with that DOF fixed If the DOF is set to FREE, no elements are created for that DOF

4. HyperMesh comment cards are written at the beginning and end of each HM_SPRING element so that the element can be imported correctly in the HyperMesh session. These comment cards suppress the reading of the individual CELAS2 and RBE2 elements and the third "artificial" nodes so that you are left with the two original nodes and a single spring element once the bulk data file is loaded back into HyperMesh. Note Removing these comment cards allows you to load the elements back into HyperMesh the way NASTRAN sees them. If this is done, make sure that any equivalencing operations performed using these elements are done properly.

To create and assign properties to CONROD elements:

1. Select the element types panel on the 1-D page. 2. Click rod = and select the CONROD element type. 3. Click return. 4. Select the rods panel on the 1-D page. 5. While the upper node is highlighted, select end A from the graphics window. 6. While the lower node is highlighted, select end B from the graphics window. After you select end A and end B, HyperMesh creates the CONROD element. NOTE The property = field is not used for CONROD elements.

7. Repeat steps 4 - 6 to create additional CONROD elements. 8. Select the card panel on the permanent menu. 9. Click the switch and select elems. 10. Select the CONROD elements for which you want to specify properties. 11. Click config = and select rod. 12. Click type = and select CONROD. 13. Click edit. 14. Edit the A, J, C, and NSM fields in the card image and enter the properties for the selected elements. 15. Click MID and select a material for these elements from the list of material collectors. 16. Click return. NOTE It is not necessary to create a property collector for CONROD elements.

Altair Engineering

Interfacing with NASTRAN

To create HM_SPRING elements:

1. Select the collectors panel. 2. Select the create subpanel. 3. Click the upper switch and select props. 4. Enter a property name after name =. 5. Click card image = and select HM_ELAS. 6. Click material = and select a material collector. 7. Click create/edit. 8. There are three choices for each DOF: FREE, RIGID, and SPRING constant. To enter a SPRING constant: Select the appropriate DOF switch from the options list. Type in the spring constant value under the appropriate DOF label in the card image. Ensure the appropriate DOF switch is unselected in the options list. Click the button under the DOF label in the card image and select RIGID from the pop-up menu. Ensure the appropriate DOF switch is unselected in the options list. Click the button under the DOF label in the card image and select FREE from the pop-up menu. FREE is the default option for the DOF fields when the card is created.

To select the RIGID option:

To select the FREE option: NOTE

9. Click return. 10. Select the element types panel on the 1-D page. 11. Click spring = and select the HM_SPRING element type. 12. Click return. 13. Select the springs panel on the 1-D page. 14. Click property = and select the property with the HM_ELAS card image loaded. 15. Click the orientation vector toggle switch to no vector. NOTE The orientation vector option is not used for HM_ELAS elements.

16. While the upper node is highlighted, select end A from the graphics window. 17. While the lower node is highlighted, select end B from the graphics window. 18. After selecting end A and end B, HyperMesh creates the HM_SPRING element.

10 Interfacing with NASTRAN

Altair Engineering

NOTE

The DOF buttons in this panel are ignored, since they are defined in the HM_ELAS property card.

To create CGAP elements:

1. Create an orientation vector using the vectors panel. NOTE For more information on creating vectors, see the vectors panel in the on-line help.

2. Select the gaps panel on the 1-D page. 3. Click property = and select the property with the PGAP card image loaded. 4. Click the orientation vector toggle switch to orient vector. 5. Click from node and select end A from the graphics window. 6. Click to node and select end B from the graphics window. 7. There are three options for choosing an orientation vector: If you select a vector which was created using the two nodes option: If the first node in the vector definition (from node) is the same as end A of the CGAP element, the second node of the vector definition (to node) is added as a direction node (G0) in the element definition. If the first node in the vector definition (from node) is not the same as end A of the CGAP element, a direction vector (X1, X2, X3) is added to the element definition, which is the direction of the selected vector resolved into the local coordinate system assigned to end A.

If you select a vector which was created using the base and magnitude or cross product options: A direction vector (X1, X2, X3) is added to the element definition which is the direction of the selected vector resolved into the local coordinate system assigned to end A. Click the orientation vector toggle switch to no vector.

If you want to use a local coordinate system (CID) to define the element coordinate system:

8. Once you select the orientation vector, HyperMesh creates the CGAP element. 9. Repeat steps 2 - 8 to create additional CGAP elements. 10. If you select no vector, follow these procedures: Select the card panel on the permanent menu. Click the switch and select elems. Select the CGAP elements that you want to edit. Click config = and select gap. Click edit. Click CID and select a local coordinate system from the graphics window, or activate any of the X1, X2, or X3 fields and manually edit an orientation vector.

Altair Engineering

Interfacing with NASTRAN

11

NOTE

The default CID is blank, which stands for the basic global coordinate system.

Click return.

To create a property collector:

1. Select the collectors panel. 2. Select the create subpanel. 3. Click the upper switch and select props. 4. Enter a property name after name =. 5. Click card image = and select the card image type. 6. Click material = and select a material collector. 7. Click create/edit. 8. Enter the relevant data. 9. Click return.

Composite Materials
The PCOMP card contains all information regarding composite materials, including the orientation of the longitudinal direction of each ply. You can view each ply direction through the composites panel. The material longitudinal axis of the element, shown in the composites panel as elem orientation is obtained either by rotating the x axis of the element THETA degree (from THETA field in the element card) counterclockwise, or by projecting the x axis of a system (from MCID field in the element card) onto the surface of the element. Each ply orientation, shown in the composites panel as ply direction, is obtained by rotating the material longitudinal axis THETAi degree (from the THETAi field in the PCOMP card) counterclockwise.

Components
The property data cards for NASTRAN shells and solids can be created using the component collector in HyperMesh. Elements that share property data are collected into one component, and a corresponding property data card is created by loading and editing the appropriate component card image. These card images have the same name as their corresponding cards. NASTRAN Keyword PSHELL PSHEAR PSOLID PCOMP

12 Interfacing with NASTRAN

Altair Engineering

To create a component card:

1. Select the collectors panel. 2. Select the create subpanel. 3. Click the upper switch and select comps. 4. Enter a component name after name =. 5. Click card image = and select the card image type. 6. Click color and select a display color from the menu. 7. Click material = and select a material collector from the list. 8. Click create/edit. 9. Enter the relevant data. 10. Click return.

Elements
NASTRAN Keyword CONM2 CMASS2 PLOTEL RBAR RBAR CNA field defaults to 123456. To edit the CNA, CNB, CMA, or CMB fields, you must view the card image for the RBAR element. An RBE2 element with one dependent node is identified as a rigid element, while an element with multiple dependent nodes is identified as a rigid link element. Individual weight factors can be created on the independent nodes of RBE3 using the update functionality in the rbe3 panel. See the on-line help for the rbe3 panel for more information. Elements CELAS2, CDAMP1, and CDAMP2 with grounded terminals are not supported. Notes

RBE2

RBE3

CELAS1, CELAS2, CDAMP1, CDAMP2, and CBUSH

CROD, CONROD, CTUBE CBAR, CBEAM, CBEND CGAP CTRIA3, CTRIAR CQUAD4, CQUADR, CSHEAR

Altair Engineering

Interfacing with NASTRAN

13

CTRIA6

In NASTRAN, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID. In NASTRAN, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID.

CQUAD8

CTETRA (4-noded) CPENTA (6-noded) CHEXA (8-noded) CTETRA (10-noded) In NASTRAN, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID. In NASTRAN, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID. In NASTRAN, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID. HyperMesh can read Node-Node, Node-Patch, or Patch-Patch weld elements. CWELD element is stored in HyperMesh as an element of the "rod" configuration. CWELD elements using the ELEMID option, which were not created in HyperMesh will be displayed as zero length. Currently, the HyperMesh spotweld panel can only create Node-Node and Patch-Patch CWELD elements. HyperMesh always calculates the location of GA and GB by projecting GS in the normal direction of surface patch A and surface patch B, respectively. HM_SPRING

CPENTA (15-noded)

CHEXA (20-noded)

CWELD

To create CBUSH elements:

1. Select the element types panel on the 1-D page. 2. Click spring = and select the CBUSH element type. 3. Click return. 4. Create an orientation vector using the vectors panel.

14 Interfacing with NASTRAN

Altair Engineering

NOTE

For more information on creating vectors, see the vectors panel in the HyperMesh Panels On-line Help.

5. Select the springs panel on the 1-D page. 6. Click property = and select the property with the PBUSH card image loaded. 7. Click the orientation vector toggle switch to orient vector. 8. Click the upper node and select end A from the graphics window. 9. Click the lower node and select end B from the graphics window. 10. There are three options for choosing an orientation vector: If you select a vector which was created using the two nodes option: If the first node in the vector definition (from node) is the same as end A of the CBUSH element, the second node of the vector definition (to node) is added as a direction node (G0) in the element definition. If the first node in the vector definition (from node) is not the same as end A of the CBUSH element, a direction vector (X1, X2, X3) is added to the element definition which is the direction of the selected vector resolved into the local coordinate system assigned to end A. A direction vector (X1, X2, X3) is added to the element definition, which is the direction of the selected vector resolved into the local coordinate system assigned to end A. Click the orientation vector toggle switch to no vector.

If you select a vector which was created using the base & magnitude or cross product options:

If you want to use a local coordinate system (CID) to define the element coordinate system:

11. Once you select the orientation vector, HyperMesh creates the CBUSH element. NOTE The DOF selection buttons are not needed to define a CBUSH element.

12. Repeat steps 5 - 11 to create additional CBUSH elements. 13. If you select the no vector option or you want to specify an offset for any of the CBUSH elements, follow these procedures: Click the card panel on the permanent menu. Click the switch and select elems. Select the CBUSH elements that you want to edit. Select config = and select springs. Select type = and select CBUSH. Click edit. To use a local coordinate system as the element coordinate system, click on the CID field and select a local coordinate system from the graphics window. The default CID is blank, which stands for the basic global coordinate system.

NOTE

Altair Engineering

Interfacing with NASTRAN

15

To add an offset to the element: Click CONT and select one of the OCID options Type in the data in the card image.

Click return.

To create and assign properties to CELAS2 elements:

1. Select the element types panel on the 1-D page. 2. Click spring = and select the CELAS2 element type. 3. Click return. 4. Select the springs panel on the 1-D page. 5. Select the toggle next to the DOF for this element. 6. Click the orientation vector toggle switch to no vector. NOTE The orientation vector option is not used for CELAS2 elements.

7. While the upper node is highlighted, select end A from the graphics window. 8. While the lower node is highlighted, select end B from the graphics window. After selecting end A and end B, HyperMesh creates the CELAS2 element. 9. Repeat steps 4 - 8 to create additional CELAS2 elements. 10. Select the card panel on the permanent menu. 11. Click the switch and select elems. 12. Select the CELAS2 elements for which you want to specify properties. 13. Click config = and select spring. 14. Click type = and select CELAS2. 15. Click edit. 16. Edit the K, GE, and S fields in the card image and enter the properties for the selected elements. 17. Click return. NOTE It is not necessary to create a property collector for CELAS2 elements.

16 Interfacing with NASTRAN

Altair Engineering

Creating CWELD Elements

CWELD element is created using ROD element configuration, therefore before creating any CWELD element, it is important that CWELD is assigned to ROD element configuration (which is currently the default value). You can create CWELD elements using either the rods panel (node-node only) or the spotweld panel (node-node and patch-patch).

To assign CWELD to ROD elements configuration:

1. On the 1D page, select the elem types panel. 2. Click rod =. 3. Select CWELD. 4. Click return.

To create CWELD elements using the rods panel:

1. On the 1D page, select the rods panel. 2. Pick the first node to weld (click on the node). 3. Pick the second node to be weld (click on the node). 4. Click property = and select the desired property. 5. Click return.

Creating CONM2 Elements

CONM2 element is created using MASS element configuration, therefore before creating any CONM2 element, it is important that CONM2 is assigned to MASS element configuration (which is currently the default value).

To assign CONM2 to MASS element configuration: 1. On the 1D page, select the elem types panel. 2. Click mass =. 3. Select CONM2. 4. Click return. 5. Create CONM2. Click masses. Choose create (if not already chosen).

Altair Engineering

Interfacing with NASTRAN

17

Click on the node where CONM2 will be attached. Fill in the mass value of CONM2 element. Click system to assign a system to CONM2 (blank or 1 is assigned through card viewer) Click create. Click return.

Creating CMASS2 Elements

CMASS2 element is created using MASS element configuration, therefore before creating any CMASS2 element, it is important that CMASS2 is assigned to MASS element configuration (which is currently the default value). To assign CONM2 to MASS element configuration: 1. On the 1D page, select the elem types panel. 2. Click mass =. 3. Select CMASS2. 4. Click return. 5. Create CMASS2. Click masses. Choose create (if not already chosen). Click on the node where CMASS2 will be attached. Fill in the mass value of CMASS2 element. Click create. Click return.

6. Assign C1,G2,C2 Click card. Choose element. Click on CMASS2 element to be edited Click edit. Fill in the value of C1,G2 and C2. Click return.

18 Interfacing with NASTRAN

Altair Engineering

To select an element type:

1. Select the elem types panel on the 1-D, 2-D, or 3-D page. 2. Set the NASTRAN type you want to use for each configuration of element. These types are used for any new elements created. 3. Click return.

To change an existing elements type:

1. Select the elem types panel from the 1-D, 2-D, or 3-D page. 2. Set the NASTRAN type you want to use for each configuration of element. 3. Click elems. 4. Indicate which elements you want to update by picking them from the graphics window, or click elems and choose from the extended entity selection menu. 5. Click update. 6. Click return.

To check an existing elements type:

1. Select the appropriate NASTRAN template. 2. Select the card panel on the permanent menu. 3. Click the leftmost switch and select elems from the pop-up menu. 4. Select the element for which you want to find the element type from the graphics window. 5. Click edit. 6. Verify the element type. 7. Click return.

Groups
Heat transfer surfaces can be defined for NASTRAN using groups in HyperMesh. Only convective heat transfer can be defined using this method. NASTRAN Keyword PCONV

Altair Engineering

Interfacing with NASTRAN

19

To create CHBDYE elements and assign a PCONV card:

1. Select the interfaces panel on the BCs page. 2. Select the add subpanel. 3. Click name = and select the group with the PCONV card image loaded. 4. Click the switch under slave and select entities from the pop-up window. 5. Click elems. 6. Select the elements that you want to use to define the heat transfer surface. NOTE For solid elements, see Comments.

7. Click add on the same line as slave to add those elements to the surface. 8. Select the card panel on the permanent menu. 9. Click the switch and select elems. 10. Select the CHBDYE slave elements for which you want to specify properties. 11. Click config = and select slave3 or slave4. 12. Click type = and select CHBDYE3 or CHBDYE4. 13. Click edit. 14. Click CONV. 15. Click TA1 and select the first ambient node from the graphics window. 16. If you want to define FLMND, CNTRLND, or any other ambient nodes, click the appropriate field and select a node from the graphics window. For ambient nodes TA5-TA8, click CONV_CONT and select the node input field from the card image. 17. Click return. NOTE Comments When elements are added to a group, HyperMesh creates ghost element images that are placed into the group. These ghost elements can be used to define the type of heat transfer occurring on the surface. The original element that was selected is not modified. For surfaces which are defined using the faces of solid elements: Before you can select elements to define your surface, you must use the faces panel to create face elements on the surface of the solid elements where the heat transfer will occur. You can then add these face elements to the group using the procedure above. For the ghost elements to refer to the solid elements and not to the face elements, click delete faces on the faces panel before exporting the model to NASTRAN. PCONID is determined automatically from the group to which the CHBDYE elements belong.

20 Interfacing with NASTRAN

Altair Engineering

If more than one solid element shares the same face along a contact surface, the solid element to which the ghost elements normal points is selected.

To create a PCONV card:

1. Select the interfaces panel on the BCs page. 2. Select the create subpanel. 3. Enter a collector name after name =. 4. Click type = and select PCONV. 5. Click interface color and select a color. 6. Click create/edit. 7. Click MID in the card image and select a material collector from the list. 8. Edit the FORM and EXPF fields as necessary. 9. Click return. NOTE Any CHBDYE elements created using this group are assigned to this PCONV card.

Sets
NASTRAN Keyword SET NOTE Notes Node and element sets supported with the THRU option. When reading input decks that were not created in HyperMesh, HyperMesh attempts to create two sets for each set found: one containing elements and one containing nodes. You can delete the unnecessary set. Sets that are created in HyperMesh are maintained as node or element sets by using $HMSET comment cards.

To create an entity set:

1. Select the entity sets panel on the BCs page. 2. Enter a set collector name after name =. 3. Click the upper switch and select nodes or elems. 4. Indicate the nodes or elems you want to include in the set by picking them from the graphics window, or click nodes or elems and choose from the extended entity selection menu. 5. Click create. 6. Click return.

Altair Engineering

Interfacing with NASTRAN

21

To review an entity set:

1. Select the entity sets panel on the BCs page. 2. Click review. 3. Select the set you want to review. HyperMesh selects the entities contained in the set that you selected.

To update an entity set:

1. Select the entity sets panel on the BCs page. 2. Click review. 3. Select the set to update. HyperMesh selects the entities contained in the set you selected. 4. Select or deselect nodes or elements to change the definition of the set. 5. Click update.

Vector Collectors
In HyperMesh, vector collectors are used to group vectors. For Nastran, vectors can be used to define orientation directions for gap and spring elements or to define the SNORM card. For orientation vectors, it is not necessary to load any card image data onto the vector collector. For SNORM vectors, you must load the SNORM card image onto the vector collector. Once this is done, all vectors organized into that vector collector will write out as SNORM vectors to the Nastran bulk data file. NASTRAN Keyword SNORM Notes There is no card image associated with the collector. In order to view the actual SNORM cards, each vector must be individually card edited. Loading the SNORM card image onto the collector assigns the SNORM type onto all of the vectors contained in that collector.

Vectors
For NASTRAN, vectors can be used to define orientation directions for gap and spring elements or to define the SNORM card. For SNORM vectors, you must load the SNORM card image onto the vector collector (see Vector Collectors above). Once this is done, all vectors organized into that vector collector will write out as SNORM vectors to the NASTRAN bulk data file. NASTRAN Keyword SNORM Notes If the SNORM card image is loaded onto the vector collector containing this vector, this vector can be card edited. Loading the SNORM card image onto the collector assigns the SNORM type onto all of the vectors contained in that collector.

22 Interfacing with NASTRAN

Altair Engineering

Load Collectors
When reading in a NASTRAN deck, loads that have the same SID are collected into the same load collector. If a load collector already exists in the database with the same SID, one of the following can occur: If overwrite is off (default), the new load collectors ID is offset and all loads in that collector will have a new SID upon export. If overwrite is on, the new load collector replaces the existing load collector. The original load collector and the loads it contains are deleted.

NASTRAN Keyword SPCADD LOAD EIGRL MPCADD GRAV RFORCE EIGB EIGC EIGP EIGR

Using load collectors and load steps to arrange subcases In HyperMesh, there are two types of load collectors for NASTRAN: Specific load collectors with a card image Generic load collectors without a card image

Generic load collectors are used to collect loads and constraints for display purposes and to assign an ID to the loads. Specific load collectors are used for specialized loading cards, such as EIGRL, LOAD, SPCADD, MPCADD, GRAV, and RFORCE. Specific load collectors have card images which can be edited to do the following: Group other load collectors together for simultaneous application in a single load step Provide special information for a specific analysis type (such as modal analysis)

General boundary conditions, such as loads and constraints, should not be collected into specific load collectors. Putting loads and constraints into a specific load collector results in errors in NASTRAN. Load steps are used to group load collectors into subcases. Each load step is a single subcase. During export, HyperMesh writes SPC= or LOAD= cards based on the load collectors selected for the load step. The following diagram illustrates how loads, load collectors, and load steps interact in HyperMesh:

Altair Engineering

Interfacing with NASTRAN

23

Click on one of the following to learn how load collectors and load steps can be combined to provide subcases for NASTRAN: Modal analysis with one subcase Static analysis with one subcase Static analysis with two subcases and multi-point constraints Static analysis with combined subcases

To create a load collector:

1. Select the collectors panel. 2. Select the create subpanel. 3. Click the upper switch and select loadcols. 4. Enter a load collector name after name =. 5. Click color and select a color from the pop-up menu. 6. If creating a generic load collector: Click the switch under creation method: and select no card image. Click create. Click return.

7. If creating a specific load collector: Click the switch under creation method: and select card image. Click card image = and select the card image type (EIGRL, LOAD, SPCADD, MPCADD, GRAV, RFORCE). Click create/edit. Enter the relevant data in the card image. Click return.

24 Interfacing with NASTRAN

Altair Engineering

NOTE

Loads and constraints should not be organized into specific load collectors. Putting loads and constraints into specific load collectors results in errors in NASTRAN. For more information, see the Load Collectors section. It contains information on using load collectors and load steps to arrange subcases.

To organize loads into load collectors:

1. Select the organize panel. 2. Click the leftmost switch and select loads. 3. Enter a load collector you want to copy or move the loads into after destination =. 4. Click copy or move. 5. Click return. NOTE Loads and constraints should not be organized into specific load collectors. For more information, see the Load Collectors section. It contains information on using load collectors and load steps to arrange subcases.

To create a subcase for NASTRAN using modal analysis with one subcase:
SUBCASE 1 SPC=1 METHOD=2 BEGIN BULK EIGRL 2

1.00

1000.00

To create the subcase in HyperMesh:

1. Create a generic load collector called generic1. 2. Create constraints and place them in the generic1 load collector. 3. Create a specific load collector called specific2 with the EIGRL dictionary loaded. 4. Create a load step called subcase1. 5. Select load collectors generic1 and specific2 to be included in the subcase definition. 6. Export the deck to NASTRAN.

Altair Engineering

Interfacing with NASTRAN

25

To create a subcase for NASTRAN using static analysis with one subcase:
SUBCASE 1 SPC=1 LOAD=2 To create the subcase in HyperMesh: 1. Create a generic load collector called generic 1. 2. Create constraints and place them in the generic1 load collector. 3. Create a generic load collector called generic2. 4. Create loads and place them in the generic2 load collector. 5. Create a loadstep called subcase1. 6. Select load collectors generic1 and generic2 to be included in the subcase definition. 7. Export the deck to NASTRAN.

To create a subcase for NASTRAN using static analysis with two subcases and multi-point constraints:
SUBCASE 1 SPC=1 LOAD=2 MPC=3 SUBCASE2 SPC=1 LOAD=4 MPC=3 To create the subcase in HyperMesh: 1. Create a generic load collector called generic1. 2. Create constraints and place them in the generic1 load collector. 3. Create a generic load collector called generic2. 4. Create the loads for subcase1 and place them in the generic2 load collector. 5. Create a generic load collector called generic3. 6. Create multi-point constraints and place them in the generic3 load collector. 7. Create a generic load collector called generic4. 8. Create the loads for subcase2 and place them in the generic4 load collector. 9. Create a loadstep called subcase1.

26 Interfacing with NASTRAN

Altair Engineering

10. Select load collectors generic1, generic2, and generic3 to be included in the subcase definition. 11. Create a loadstep called subcase2. 12. Select load collectors generic1, generic3, and generic4 to be included in the subcase definition. 13. Export the deck to NASTRAN.

To create a subcase for NASTRAN using static analysis with combined subcases:
SUBCASE1 LABEL=X-FORCE SPC=1 LOAD=2 SUBCASE2 LABEL=Y-FORCE SPC=3 LOAD=4 SUBCASE3 LABEL=Z-FORCE SPC=5 LOAD=6 SUBCASE4 LABEL=ALL-FORCES SPC=7 LOAD=8 To create the subcase in HyperMesh: 1. Create a generic load collector called generic1. 2. Create the constraints for subcase1 and place them in the generic1 load collector. 3. Create a generic load collector called generic2. 4. Create the loads for subcase1 and place them in the generic2 load collector. 5. Create a generic load collector called generic3. 6. Create the constraints for subcase2 and place them in the generic3 load collector. 7. Create a generic load collector called generic4. 8. Create the loads for subcase2 and place them in the generic4 load collector. 9. Create a generic load collector called generic5. 10. Create the constraints for subcase3 and place them in the generic5 load collector.

Altair Engineering

Interfacing with NASTRAN

27

11. Create a generic load collector called generic6. 12. Create the loads for subcase3 and place them in the generic5 load collector. 13. Create a specific load collector called specific7 with the SPCADD card image loaded. 14. Group load collectors generic1, generic3, and generic5, using the fields in the SPCADD card image. 15. Create a specific load collector called specfic8 with the LOAD card image loaded. 16. Group load collectors generic2, generic4, and generic6, using the fields in the LOAD card image. 17. Create a loadstep called subcase1. 18. Select load collectors generic1 and generic2 to be included in the subcase definition. NOTE You can edit the LABEL field in the subcase1 loadstep card image to add the label as shown above.

19. Create a loadstep called subcase2. 20. Select load collectors generic3 and generic4 to be included in the subcase definition. 21. Create a loadstep called subcase3. 22. Select load collectors generic5 and generic6 to be included in the subcase definition. 23. Create a loadstep called subcase2. 24. Select load collectors specific7 and specific8 to be included in the subcase definition. 25. Export the deck to NASTRAN.

Load Steps
NASTRAN Keyword SUBCASE LABEL DISPLACEMENT STRESS STRAIN ELFORCE ESE SPCFORCES

28 Interfacing with NASTRAN

Altair Engineering

DISPLACEMENT (arg1, arg2, arg3) = arg4

To select displacement as an output: 1. Select Output. 2. Select Displacement. 3. Select the displacements argument box to activate one or more of the following arguments. arg1 = SORT1 (Default), SORT2 arg2 = PRINT (Default), PUNCH, PRINT, PUNCH, PLOT arg3 = REAL (Default), IMAG, PHASE arg4 = ALL (Default), NONE

STRESS (arg1, arg2, arg3, arg4, arg5, arg6) = arg7

To select stress as an output: 1. Select Output. 2. Select Stress. 3. Select the stess argument box to activate one or more of the following arguments. arg1 = SORT1 (Default), SORT2 arg2 = PRINT (Default), PUNCH, PRINT, PUNCH, PLOT arg3 = REAL (Default), IMAG, PHASE arg4 = VON MISES (Default), SHEAR arg5 = STRCUR (Default), FIBER arg6 = CENTER (Default), CORNER, SGAGE, BILIN arg7 = ALL (Default), NONE

STRAIN (arg1, arg2, arg3, arg4, arg5, arg6) = arg7

To select strain as an output: 1. Select Output. 2. Select Strain. 3. Select the strain argument box to activate one or more of the following arguments. arg1 = SORT1 (Default), SORT2 arg2 = PRINT (Default), PUNCH, PRINT, PUNCH, PLOT arg3 = REAL (Default), IMAG, PHASE

Altair Engineering

Interfacing with NASTRAN

29

arg4 = VON MISES (Default), SHEAR arg5 = STRCUR (Default), FIBER arg6 = CENTER (Default), CORNER, SGAGE, BILIN arg7 = ALL (Default), NONE

ELFORCE (arg1, arg2, arg3, arg4) = arg5

To select ELFORCE as an output: 1. Select Output. 2. Select ELFORCE. 3. Select the ELForce argument box to activate one or more of the following arguments. arg1 = SORT1 (Default), SORT2 arg2 = PRINT (Default), PUNCH, PRINT, PUNCH, PLOT arg3 = REAL (Default), IMAG, PHASE arg4 = CENTER (Default), CORNER, BILIN, SGAGE, CUBIC arg5 = ALL (Default), NONE

ESE (arg1, arg2) = arg7

To select ESE as an output: 1. Select Output. 2. Select ESE. 3. Select the ESE argument box to activate one or more of the following arguments. arg1 = PRINT arg2 = PUNCH arg3 = ALL (Default), NONE

SPCFORCES (arg1, arg2, arg3) = arg4

To select SPCFORCES as an output: 1. Select Output. 2. Select SPCFORCES. 3. Select the SPCFORCES argument box to activate one or more of the following arguments. arg1 = SORT1 (Default), SORT2 arg2 = PRINT (Default), PUNCH, PRINT, PUNCH, PLOT

30 Interfacing with NASTRAN

Altair Engineering

arg3 = REAL (Default), IMAG, PHASE arg4 = ALL (Default), NONE

To create load steps:

1. Select the load steps panel on the BCs page. 2. Click name = and enter a load step name. 3. Click loadcols. 4. Select the load collectors that are to be included in this subcase definition. 5. Click return. 6. Click create. 7. Click return.

To edit load steps:

1. Select the NASTRAN/General template from the global panel. 2. Select the card panel on the permanent menu. 3. Click the leftmost switch and select loadsteps from the pop-up menu. 4. Click loadsteps. 5. Select the load step for which you want to edit the card image. 6. Click edit. 7. Enter the relevant data. 8. Click return. NOTE See the Load Collectors section for instructions on using load collectors and load steps to arrange subcases.

Loads
NASTRAN Keyword FORCE MOMENT SPC, SPCD, ASET1, QSET1, BSET1, CSET1, OMIT1 SPC1 Supported for feinput only. On export, equivalent SPC cards are written. Alternate format with THRU in the fifth field is supported. Notes

Altair Engineering

Interfacing with NASTRAN

31

PLOAD, PLOAD2, PLOAD4, QBDY1

For PLOAD2 and PLOAD4 cards, the THRU field is supported for feinput only. On export, additional pressure cards for the range specified are written. For PLOAD4 card, unequal nodal pressures are now supported. The average pressure value is used as the magnitude of the pressure for visualization only. The individual field values, P1P4, can be viewed or edited using the card editor. NOTE Updating the magnitude of pressure from the pressures panel will have no effect on PLOAD4 cards defined using unequal nodal pressures.

To create load cards:

1. Select the type of load card to create on the BCs page. 2. Select the create subpanel. 3. Enter the relevant data. 4. Click create. 5. Click return.

To select a load type:

1. Select the load types panel on the BCs page. 2. Set the NASTRAN type you want to use for each loads configuration. These types are used for any new loads created. 3. Click return.

To change an existing loads type:

1. Select the load types panel on the BCs page. 2. Set the NASTRAN type you want to use for each loads configuration. 3. Click loads. 4. Indicate the loads you want to update by picking them from the graphics window, or click loads and choose from the extended entity selection menu. 5. Click update. 6. Click return.

To check an existing loads type:

1. Select the appropriate NASTRAN template.

32 Interfacing with NASTRAN

Altair Engineering

2. Select the card panel on the permanent menu. 3. Click the leftmost switch and select loads from the pop-up menu. 4. Select the load for which you want to find the load type from the graphics window. 5. Click edit. 6. Verify the load type. 7. Click return.

Multi-point Constraints
NASTRAN Keyword MPC Note Individual weight factors can be created on the nodes of an MPC equation using the update functionality in the equations panel. See the on-line help for the equations panel for more information. Is supported as load collector. Multi-point constraints are considered loads in HyperMesh. Use load collectors to group multi-point constraints and to display them.

MPCADD NOTE

To create multi-point constraint cards:

1. Click the equations panel on the BCs page. 2. Select the create subpanel. 3. Enter the relevant data. 4. Click create. 5. Click return.

Optimization - General
Some of the functionality of the optimization capability is general. This includes the equation utility, delete, rename, renumber, and reorder. To set up an optimization problem, responses, an objective function and constraints need to be defined. To define design variables see Optimization - Problem Setup. Further, design variables need to be defined. To define design variables, see Optimization Design Variables. The optimization panels have separate delete, rename, renumber, and reorder panels to manipulate optimization entries. These can be reached through the optimization panel on the BCs page.

Altair Engineering

Interfacing with NASTRAN

33

OptiStruct Keyword DEQATN DTABLE DOPTPRM DSCREEN

Notes Equations referenced on DRESP2, DVPREL2 Table entries referenced on DRESP2, DVPREL2 Optimization control card Constraint screening

To define an equation:
1. Select the optimization panel on the BCs page. 2. Select the equations panel. 3. Enter a name (max. 8 characters) in name = . 4. Click edit equation. 5. Type the function into the window that appears in the graphics area. 6. Click create. 7. Click return.

Optimization Design Variables

Design variables need to be defined to solve an optimization problem. Further, to set up an optimization problem, responses, an objective function and constraints need to be defined. To define design variables, see Optimization - Problem Setup. Some more general feature such as the equation utility, table entries, constraint screening, delete, rename, renumber, and reorder are described in Optimization - General. OptiStruct Keyword DESVAR DLINK DVPREL1 DVPREL2 Notes Design variable definition Design variable link Generic Property Function Property

To define design variables for size optimization:

1. Select the optimization panel on the BCs page. 2. Select the size DV panel. 3. Select desvar using the toggle in the upper left

34 Interfacing with NASTRAN

Altair Engineering

4. Enter a name (max. 8 characters) in desvar = . 5. Click create. Create as many design variables as needed in your size optimization. 6. Select generic properties using the toggle in the upper left. This is to create the relationships between the properties to be designed and the design variables. The property is defined as a linear combination of one or more design variables. 7. Enter a name (max. 8 characters) in dvprel = . 8. Select a component, property collector or element from the database. Then automatically a selector pops up that gives a choice of which property is to be designed. 9. Select the property, for example a shell thickness. 10. Click on designvars. You enter the list of design variables. 11. Use the toggles to select the design variables for the given property. You may change the linear factors that are defaulted to 1.0 by editing them. 12. Click return. 13. Edit PMAX, <PMIN, and C0 if needed. 14. Click create. 15. Click return.

To define design variable links:

1. Select the optimization panel on the BCs page. 2. Select the desvar link panel. 3. Enter a name (max. 8 characters) in dvlink = . 4. Select a dependent design variable. 5. Select the independent design variables. Click on designvars. You enter the list of design variables. 6. Use the toggles to select the design variables for the given link. You may change the linear factors that are defaulted to 1.0 by editing them. 7. Click return. 8. Enter C0 or CMULT if needed. 9. Click create. 10. Click return.

Altair Engineering

Interfacing with NASTRAN

35

Optimization - Problem Setup

To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. To define design variables, see Optimization Design Variables. More general features, such as the equation utility, table entries, constraint screening, delete, rename, renumber, and reorder are described in Optimization - General. OptiStruct Keyword DRESP1 DRESP2 DCONSTR DCONADD DESOBJ Notes Generic response Function response Constraint to define lower and upper bounds Collects constraints Objective function, can be in or out of the load step; Belongs in the subcase section Constraint dependent on the load step; Belongs in the subcase section Global constraint; Belongs in the subcase section

DESSUB DESGLB

To define a response:
1. Select the optimization panel on the BCs page. 2. Select the responses panel. 3. Enter a name (max. 8 characters) in response = . 4. Set the response type using the selector. If required, select more information from the database such as nodes, components, properties, materials, elements. 5. Click create. 6. Click return.

To define a constraint:
1. Select the optimization panel on the BCs page. 2. Select the constraints panel. 3. Enter a name (max. 8 characters) in constraint = . 4. Select a response. 5. Activate and enter the bounds lowerbound= and/or upperbound= as needed. 6. If the selected response is dependent on a specific load step, select a load step

36 Interfacing with NASTRAN

Altair Engineering

7. Click create. 8. Click return.

To define the objective function:

1. Select the optimization panel on the BCs page. 2. Select the objective panel. 3. Select min/max. 4. Select a response. 5. If the objective is dependent on a specific load step, select the load step. 6. Click create. 7. Click return.

Working with Comment Cards

HyperMesh reads and writes certain HyperMesh commands in the NASTRAN bulk data file as commands. These comment cards enable HyperMesh to preserve pre-defined preferences across sessions. The HyperMesh commands that can be defined are listed below. $HMCOLOR Format $HMCOLOR <COLLECTORTYPE> ID Color $HMCOLOR is an 8-character field followed by a space. COLLECTORTYPE is one of COMP, MAT, PROP, LOADCOL, SYSTCOL, CURVES, VECTORCOL, GROUP, or LOADSTEP, and is left justified in a 15character field. ID is the collector ID, right justified in an 8-character field. Color is an integer between 0 and 15, right justified in an 8-character field. feinput feoutput Comments $HMMOVE Format $HMMOVE ID Color definition of collectors. Each component creates a $HMCOLOR comment. The color command allows color information from the HyperMesh database to be included in the NASTRAN bulk data.

Altair Engineering

Interfacing with NASTRAN

37

$id1 id2 id3 id4 id5 id6 id7 id8 id9 $id10 $id11 $HMMOVE is left justified in an 8-character field. ID is the collector id, right justified in an 8-character field. The format of the continuation cards is (8A,9I8). feinput feoutput Comments Organization commands. Each 1-D element writes $HMMOVE commands. Each $HMMOVE command moves the list of elements to the component specified by ID.

$HMASSEM Format $HMASSEM ID Color <Assembly Name could be 32 characters> $HMASSEM_IDS id1 id2 id3 id4 id5 id6 id7 id8 $HMASSEM_IDS id9 id19 id11 $HMASSEM is left justified in an 8-character field. ID is the assembly id, right justified in an 8-character field. Color is an integer between 0 and 15, right justified in an 8-character field. A blank space must appear between color and assembly name. The assembly name is a left justified strong no longer than 32 characters. $HMASSEM_IDS is left justified in a 16-character field. The format of the component collector IDs is (818). Extra continuation lines all have the same $HMASSEM_IDS format. feinput feoutput Comments Create assemblies, component organization commands. Each assembly writes $HMASSEM and $HMASSEM_IDS commands. Each $HMASSEM commands adds the list of components to the assembly specified by the ID.

$HMNAME Format $HMNAME <COLLECTOR TYPE> ID "Collector Name could be 32 characters"

38 Interfacing with NASTRAN

Altair Engineering

$HMNAME is left justified in an 8-character field. COLLECTOR TYPE is one of COMP, MAT, PROP, LOADCOL, SYSTCOL, CURVES, VECTORCOL, GROUP, BEAMSECTS, BEAMSECTCOLS, or LOADSTEP and is left justified in a 16-character field. ID is the collector ID, right justified in an 8-character field. The collector name is a left justified, double quoted string. feinput feoutput Comments The name of a collector. Each component creates a $HMNAME comment. The name command allows the names of components and load collectors from the HyperMesh database to be included in the NASTRAN bulk data file.

In addition to the above comments, HyperMesh also writes the following comment cards: $HMAGEOM, $HMALINE, $HMASURF, and $HMASSOC These cards are generated when you create lines and surfaces and enable the geometry option during feoutput. $HMBEAMSEC, $HMNAME BEAMSECTS These cards are generated when you create a beam section using the HyperBeam module and tie those cross sections to a property card. $HMNAME CWELD GRID, $HMNAME CWELD GAGB, $HMNAME CWELD GA1, $HMNAME CWELD GB1, $HMNAME CWELD SHDA SHDB These cards are generated when you create a CWELD element.

Templates
The general template generates NASTRAN input decks in fixed, single precision format. The generallf template generates NASTRAN input decks in fixed, double precision format.

Summary Templates
The following summary templates are available for NASTRAN: elements Summarizes the number of each element type in the current HyperMesh database. Summarizes the forces and moments applied to the current model. Calculates the center of gravity of the model. Summarizes some common model errors.

loads ctr_of_gravity errorcheck

Altair Engineering

Interfacing with NASTRAN

39

mom_of_intertia

Calculates the mass moment of inertia of each component of the model as well as the mass moment of inertia of the entire model. Summarizes the component information in the current HyperMesh database.

components

To summarize the number of each element in the HyperMesh database:

1. Click the summary panel on the Post page. 2. Double click template file. 3. Click nastran (when using summary template for the first time, jump to step 4 thereafter). 4. Click element. 5. Click summary.

To summarize the forces and moments applied to the model:

1. Click the summary panel on the Post page. 2. Double click template file. 3. Click nastran (when using summary template for the first time, jump to step 4 thereafter). 4. Click loads. 5. Click summary.

To calculate the center of gravity of the model:

1. Click the summary panel on the Post page. 2. Double click template file. 3. Click nastran (when using summary template for the first time, jump to step 4 thereafter). 4. Click ctr_of_gravity. 5. Click summary.

To summarize common model errors:

1. Click the summary panel on the Post page. 2. Double click template file. 3. Click nastran (when using summary template for the first time, jump to step 4 thereafter). 4. Click errorcheck.

40 Interfacing with NASTRAN

Altair Engineering

5. Click summary.

To calculate the mass moment of inertia of each component of the model and the entire model:
1. Click the summary panel on the Post. 2. Double click template file. 3. Click nastran (when using summary template for the first time, jump to step 4 thereafter). 4. Click mom_of_inertia. 5. Click summary.

To summarize the component information in the HyperMesh database:

1. Click the summary panel on the Post page. 2. Double click template file. 3. Click nastran (when using summary template for the first time, jump to step 4 thereafter). 4. Click component. 5. Click summary.

Mass Calculation
Certain functions in the templates allow you to calculate the mass of the model. Material densities needed to calculate mass are retrieved from the material associated with the element or component. To compute the volume of surface elements, such as CQUAD4 and TRIA3, the thickness information is retrieved from the component to which the elements are attached. If the elements are not attached to any component, such as PSHELL or PSHEAR, the thickness provided in the element continuation card is used. For elements with non-uniform thickness, the average thickness is used to compute the volume. Volume computation of 1-D elements, such as CBAR and CBEAM, uses the section properties of the corresponding property entities, such as PBAR and PBEAM. For CBEAM elements with variable cross-sections, it is assumed that the variation between two successive cross-sections is linear.

Altair Engineering

Interfacing with NASTRAN

41

Results Translation
You can view the result files from the contour, deformed, hidden line, and transient panels. hmnast hmnasto2 hmnastf06 hmnastopt

hmnast Utility
hmnast translates NASTRAN ASCII punch files into HyperMesh binary results files. hmnast can be executed either independently or directly from HyperMesh. To run hmnast independently, use the following syntax: hmnast [arguments] <inputfile> <outputfile> where [arguments] are optional arguments. Arguments such as displacements, stresses and strains are on by default. To obtain these arguments, use the command hmnast -u. To run hmnast from Hypermesh: 1. Select solver on the BCs page. 2. Click the translator toggle and select hmnast. 3. Click input file = and select the punch file. 4. Click output file = and select the output file location and name. 5. Enter the options. To create an h3d file for a specific result, add h3d after the first option. For example, to create an h3d file of the displacement, the option should be: -d h3d 6. Click solve.

The following options are off by default: Flag -m -minimums -iter -trans -corner -bulk -noconv -nolabels -title -subtitle -disk Meaning Displacements and maximums Minimums instead of maximums Nonlinear iterations (from SOL 106) Transient thermal Corner stresses (for CQUAD4 and solid elements) Reads element connectivity from the bulk file (for use with the corner option) Do not convert local displacements into global coordinates Do not use subcase labels Use title for simulation name Use subtitle for simulation name Translation is performed on disk

42 Interfacing with NASTRAN

Altair Engineering

-size -file -csa -1Dforce -1Dstress -2Dforce -repR -h3d

Number of entities (10000 = default) Scratch file name Translates CSA/NASTRAN Reads all forces for 1-D elements Reads all stresses for 1-D elements Reads all forces for 2-D elements Replaces R/NaN/nan fields with 0.0 (found in strain energy data types) Outputs file to an H3D file instead of an hmresults file. The hmresult file includes translated model and results information. The punch file must contain geometry for it to be output to an H3D file. If there is no geometry in the punch file, use bulk <filename> in addition to h3d. Example: hmnast -h3d -bulk myFile.dat myFile.pch myFile.h3d H3D files can be created either by using hmnast or from HyperMesh.

hmnast supports the following data types: Displacements, rotations, velocities, and accelerations SPC forces and SPC moments Grid Point Force Balance (totals block only) Real element forces Element name codes: 1, 2, 10, 11, 12, 33, 34, 74, 100 Real stresses Element name codes: 1, 2, 4, 10, 33, 34, 39, 64, 67, 68, 70, 74, 75, 82, 85, 88, 90, 91, 93, 144 Real strains Element name codes: 4, 33, 39, 64, 67, 68, 70, 74, 75, 82, 85, 88, 90, 91, 93, 144 Complex stresses Element name codes: 33, 39, 64, 67, 68, 70, 74, 75, 82 Complex strains Element name codes: 33, 39, 64, 67, 68, 70, 74, 75, 82 Temperatures Flux Strain energies Time Eigenvectors Frequency

How HyperMesh displays displacement results translated by hmnast: When hmnast reads displacement results, a flag is set to 1. The -noconv option sets this flag to 0. When HyperMesh reads the results file translated by hmnast, it checks the value of the flag. If the value is 1, HyperMesh translates the nodal displacement into basic* coordinate using the system attached to the node, in the case where no system is attached to the node, HyperMesh performs no further translation. If the value of the flag is 0, HyperMesh performs no further translation. * As defined by MSC-Nastran.

Altair Engineering

Interfacing with NASTRAN

43

NOTES To extract displacements and maximum von Mises stresses from the punch file, use the option d -von_max. To extract only the maximum values of the data types, specify the option -m. For iterative solutions encountered in SOL 106, use the option -iter. For transient solutions encountered in SOL 159, use the option -trans. For nonlinear transient solutions encountered in SOL 129, use the options -trans -iter. Corner stresses: Use -corner option when STRESS(CORNER) or STRESS(BILIN) is used in the data file. When using -corner option, hmnast requires the bulk data information. This can be done by using ECHO=PUNCH during analysis. Otherwise, use the -bulk <bulkfilename> option. When using STRESS(CORNER), NASTRAN gives corner stresses on a per-element basis. However, hmnast averages the corner stresses at the nodes for adjacent elements. HyperMesh converts the nodal displacements into global coordinates if there are non-zero values in the CD field of the GRID cards. To display the results in HyperMesh as they are reported in the punch file, use the option -noconv Simulation names: hmnast organizes the punch file results into a series of simulation names and data types. The simulation names correspond to the LABEL card of the punch file for SOL101. To create a simulation name, the first 27 characters from the LABEL card are appended with the SUBCASE ID. The corresponding data types are Displacements, von Mises Stress, and so on. If the option -nolabels is selected, the simulation name corresponds to the SUBCASE ID number. Use -title to use the TITLE card of your punch file as the simulation name. Use -subtitle to use the SUBTITLE card of your punch file as the simulation name. The simulation name for SOL106 is SUBCASE # Iter #. For modal frequency response problems, the simulation name is Mode # f #Hz. For modal frequency response problems where the complex part of the eigenvalue is used (SOL 107 and SOL 110), the simulation name is Mode # f #Hz(c). For direct frequency response, the simulation name is Subcase # f #. For transient problems (SOL159, SOL129), the simulation name is Time #. Do not use -nolabels for SOL106, SOL159, and SOL129. If the size of the punch file is too large, use the option -disk -size n -file /temp/scratch.tmp, where n corresponds to the maximum number of nodes/elements in the model and scratch.tmp is the scratch file name that hmnast creates in the /tmp/ directory. hmnast supports punch files for the following solutions: SOL 101, 103, 105, 106, 107, 108, 109, 110, 111, 112, 129, 153 and 159 Both SORT1 and SORT2 formats are supported. To extract only selected nodes from a punch file, use the option -selmodes <selmodesfile>, where selmodesfile contains the mode numbers that need to be extracted. These numbers must have spaces separating them. Any number of lines can be entered. A line cannot exceed 256 characters. To extract only a selected number of subcases, use the option -selsubc <selsubcfile>.

44 Interfacing with NASTRAN

Altair Engineering

hmnasto2 Utility
hmnasto2 translates OUTPUT2 NASTRAN binary results into HyperMesh binary results files. hmnasto2 can be executed either independently or directly from HyperMesh. To run hmnast02 independently, use the following syntax: hmnasto2 [arguments] <inputfile> <outputfile> where [arguments] are optional arguments. Arguments such as displacements, stresses, and strains are on by default. To obtain those arguments, use the command hmnasto2 -u. To run hmnasto2 from Hypermesh: 1. Select solver on the BCs page. 2. Click the translator toggle and select hmnasto2. 3. Click input file = and select the op2 file location and name. 4. Click output file = and select the output file location and name. 5. Enter the options. The first option should be the machine used to generate the NASTRAN binary results file. To create an h3d file for a specific result, add h3d after the second option. For example, to create an h3d file of the displacement result that was created from SGI computer, the option would be: -sgi -d h3d The following options are off by default: Flag Meaning -m Displacements and maxs -iter Nonlinear iterations -nolabels Do not use subcase labels -corner Corner stresses -csa Translate CSA/NASTRAN -subcman Subcase manager -cray Cray -dec Dec 5000 -decalpha Dec Alpha -hp Hewlett Packard -ibm IBM RS\6000 -pc PC -sgi SGI -sun Sun -h3d Outputs file to an H3D file instead of an hmresults file. The file includes translated model and results information. The model must contain geometry for it to be output to an H3D file. If there is no geometry in the op2 file, use bulk <filename> in addition to h3d. Example: hmnasto2 -h3d -bulk myFile.dat myFile.op2 myFile.h3d H3D files can be created either by using hmnast or from HyperMesh.

Altair Engineering

Interfacing with NASTRAN

45

When you use hmnasto2, specify the machine used to generate the NASTRAN binary results file (cray, -sgi or -pc, and so on). hmnasto2 supports the following data types: Displacements, velocities and accelerations Nonlinear Stress and Strain Element Name Codes: 90, 88, 85, 91, 93 Real and complex stresses Element Name Codes: 4, 33, 39, 64, 67, 68, 74, 75, 144 Real strains Element Name Codes: 4, 33, 39, 64, 67, 68, 74, 75, 144 Strain energies Shear Flux

How HyperMesh displays displacement results translated by hmnasto2: MSC-Nastran writes displacement results into different data blocks based on selected parameters. When hmnasto2 reads these data blocks, a flag is set to 0 if it reads displacement results in basic* * coordinate or 1 if it reads displacement result in global coordinate. The -noconv option sets this flag to 0. When HyperMesh reads the results file translated by hmnasto2, it checks the value of the flag. If the value is 1, HyperMesh translates the nodal displacement into basic* coordinate using the system attached to the node. If the value of the flag is 0, HyperMesh performs no further translation. * As defined by MSC-Nastran.

NOTES To extract displacements and maximum von Mises stresses from the OUTPUT2 file, use the option -d von_max. To extract only the maximum values of the data types, use the option -m. For iterative solutions encountered in SOL 106, use the option -iter. Simulation names: hmnasto2 organizes the punch file results into series of simulation names and data types. The simulation names correspond to the LABEL card for SOL101. The corresponding data types are displacements and von Mises stress, for example. If the option -nolabels is selected, the simulation name corresponds to the SUBCASE ID number. The simulation name for SOL106 is SUBCASE # Iter #. For modal frequency response problems, the simulation name is Mode # f #Hz. For modal frequency response problems where the complex part of the eigenvalue is used (SOL 107 and SOL 110), the simulation name is Mode # f #Hz(c). For direct frequency response, the simulation name is Subcase #f #.

46 Interfacing with NASTRAN

Altair Engineering

Do not use -nolabels for SOL106. Corner options: Use -corner option when STRESS(CORNER) or STRESS(BILIN) is used in the data file. Note that when STRESS(CORNER) is used, NASTRAN gives corner stresses on a per-element basis. However, hmnasto2 averages the corner stresses at the nodes for adjacent elements. If there is no geometry information in the op2 file, use an additional bulk <bulkfilename> option. In general, geometry information is written into the op2 file if PARAM,POST,-2 is used in the input file. For more information regarding geometry information in an op2 file, see NASTRAN documentation. If the size of the punch file is too large, use the option -disk -size n -file /temp/scratch.tmp, where n corresponds to the maximum number of nodes/elements in the model and scratch.tmp is the scratch file name that hmnasto2 creates in the /temp/ directory. hmnasto2 supports OUTPUT2 files for the following solutions: SOL 101, 103, 105, 106, 107, 108, 109, 110, 111 and 153. hmnasto2 supports the following data block names for PARAM,POST,-1: OQG1, OUGV1, OES1, OEF1, OSTR1, ONRGY1, OES1X and OPG1. hmnasto2 supports the following data block names for PARAM,POST,-2: OQG1, BOUGV1, BOPHIG, OUGV1, OES1, OEF1, OSTR1, ONRGY1, ONRGY2 and OES1X. Use -nosubcman for SOL103 OUTPUT2 files when the HMNASTO2 default is unsatisfactory. To extract only a selected set of nodes and subcases, use the option -selsubc <selsubcfile> or -selmodes <selmodesfile>. See hmnast for the file format.

hmnastf06 Utility
hmnastf06 translates NASTRAN *.f06 ASCII files into HyperMesh binary results files. hmnastf06 reads only the GPSTRESS output from the .f06 file for SOL101 analyses. The syntax to run the translator is: hmnastf06 [arguments] <inputfile> <outputfile> where [arguments] are the optional arguments. To obtain the arguments, use the command hmnastf06 -u. hmnastf06 arguments are on by default. NOTES hmnastf06 requires that FIBRE ALL is used in the SURFACE command during analysis hmnastf06 organizes the GPSTRESS results into simulations based on subcase ID and surface ID/volume ID

Altair Engineering

Interfacing with NASTRAN

47

hmnastopt Utility
hmnastopt translates NASTRAN SOL 200 punch files into HyperMesh binary results files. hmnastopt requires the following options in the dat file: DISPLACEMENT(PUNCH) = ALL STRESS(PUNCH) = ALL ANALYSIS = STATICS ANALYSIS = MODES PARAM, DESPCH>0 The syntax to run the translator is: hmnastopt [options] <inputfile> <outputfile> NOTES Use the command hmnastopt -u to obtain information about the options. The h3d flag outputs file to an H3D file instead of to an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file. If the punch file contains the keywords GRID and DESVAR, the option -bulk <bulkfile>must be provided To generate HyperMesh compatible x-y plot data (design cycle number vs. thickness), use the option -plot <plotfile>

To post-process NASTRAN results in HyperMesh:

Before viewing the result file, make sure that the model is loaded. The model can be loaded prior to or after translating the result file. To translate NASTRAN results: 1. Select the files panel. 2. Select the results subpanel. 3. Click file = to read the HyperMesh binary results file generated by the hmnast, hmnast02, or hmnastf06 translator. 4. Click return. To view the contour result: 1. From the Post page, click contour. 2. Click simulation to choose simulation title. 3. Click data type to choose the data to be simulated. 4. Click contour, to view the smooth transition result. Or

48 Interfacing with NASTRAN

Altair Engineering

Click assign, to view the border line result.

To view the deform result: 1. From the Post page, click deform. 2. Click simulation to choose simulation title. 3. Click data type to choose the data to be simulated. 4. Click deform, to view deformation in static condition. Or Click linear, to view deformation in dynamic condition.

To view the transient result: 1. From the Post page, click transient. 2. Click start with to choose the begining of the transient simulation. 3. Click end with to choose the end of the transient simulation. 4. Click data type to choose the data to be simulated. 5. Click transient.

Altair Engineering

Interfacing with NASTRAN

49