Patran - 2014 - Doc - Part 1 Basic Functions PDF
Patran - 2014 - Doc - Part 1 Basic Functions PDF
Patran - 2014 - Doc - Part 1 Basic Functions PDF
Reference Manual
Part 1: Basic Functions
Corporate
Japan
Asia-Pacific
Worldwide Web
www.mscsoftware.com
Support
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx
Disclaimer
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with the
terms of such license.
MSC Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended
to be exhaustive or to apply to any particular engineering problem or design. MSC Software Corporation assumes no liability or
responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein.
User Documentation: Copyright 2014 MSC Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of MSC Software Corporation is prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from MSC Software suppliers.
Additional terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms
and conditions and/or notices may be set forth in documentation and/or at http://www.mscsoftware.com/thirdpartysoftware (or
successor website designated by MSC from time to time).
METIS is copyrighted by the regents of the University of Minnesota. A copy of the METIS product documentation is included with this
installation. Please see "A Fast and High Quality Multilevel Scheme for Partitioning Irregular Graphs". George Karypis and Vipin
Kumar. SIAM Journal on Scientific Computing, Vol. 20, No. 1, pp. 359-392, 1999.
MSC, MSC Nastran, MD Nastran, MSC Fatigue, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered trademarks
of MSC Software Corporation in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group. SAMCEF is a
trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of Livermore Software
Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned subsidiary of ANSYS Inc. ACIS is a
registered trademark of Spatial Technology, Inc. ABAQUS, and CATIA are registered trademark of Dassault Systemes, SA. EUCLID
is a registered trademark of Matra Datavision Corporation. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of
Flexera Software. HPGL is a trademark of Hewlett Packard. PostScript is a registered trademark of Adobe Systems, Inc. PTC, CADDS
and Pro/ENGINEER are trademarks or registered trademarks of Parametric Technology Corporation or its subsidiaries in the United
States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of Siemens Product Lifecycle
Management, Inc. All other brand names, product names or trademarks belong to their respective owners.
P3:V2014:Z:BASC:Z:DC-REF-PDF
Contents
Patran Reference Manual
Introduction to Patran
Introducing Patran
Patran Framework
Patran Workspace
Modeling Window
10
33
24
22
Screen Picking 33
Select Menu 35
Geometry Select Icons
FEM Select Icons 41
The List Processor
39
43
46
57
67
270
270
Viewports
Viewport Concepts and Definitions
Viewport Names 317
Viewport Status 317
316
CONTENTS v
320
Viewport Commands
321
342
343
346
Viewing a Model
View Concepts and Definitions
350
Current View 350
Named Views 350
Model Space 350
Screen Space 350
Viewing Coordinate System Parameters 351
Fitting a View 352
View Transformations 352
Perspective Views 353
View Parameters 353
The Viewing Menu
354
Viewing Commands
356
Fit View 358
Select Center 358
Select Corners 358
Managing the Parameters of Perspective Viewing
Display Control
Display Concepts and Definitions
378
371
378
385
Display Commands
386
10 Preferences
Preferences Concepts and Definitions
Analysis Codes 436
Model Tolerance 437
Warning Messages 438
Hardware Rendering 438
Representing Geometry 438
Model Units 438
The Preferences Menu
Preferences Commands
Mapping Functions 444
439
441
11 Tools
The Tools Menu
482
Tools Commands
486
MSC.Fatigue 488
Laminate Modeler 489
Enterprise MVision (EMV) 490
Random Analysis 491
Analysis Manager 492
436
CONTENTS vii
Lists 493
Mass Properties 503
Beam Library 518
Named Regions 537
Model Contents 543
Properties Import 547
Load Tools 552
Model Variables 567
Element Quick Create 579
Property Data Plots 581
Mass Property Management 585
Configurations 602
Technical Operation 603
Reduced Mass/Stiffness 613
Model Unmerge 638
Experimental Data Fitting 644
Bolt Preload 647
Rotor Dynamics 650
Non-Structural Mass Properties 651
Rebar Definitions 652
Feature Recognition 655
Contact Bodies/Pairs... 657
Design Studies 661
Bar/Spring Force Moment 673
Bar End Loads 677
Max/Min Sorting 684
Shear Panel Plots 691
Explore Results 694
Result Plot Sets 695
Result Templates 714
Test Correlation (MSC.ProCOR) 725
User Define AOM 726
Pre-Release 727
730
Getting Started
Availability
731
732
733
Tree Control
734
736
Configuration
Search
Sort
737
738
739
Filter
740
Materials
741
Properties
744
Fields
746
LBCs
749
Contact
752
Load cases
Groups
Analyses
Results
735
755
757
761
762
Customization
765
13 Random Analysis
Introduction
768
Purpose 768
Features of MSC Random 768
Advantage over Utility version of MSC Random
Architecture of MSC Random 769
Limitations 770
769
774
CONTENTS ix
776
778
780
782
785
860
File Formats
The Neutral System Concept
884
926
924
868
869
929
935
Printing Options
Introduction
940
941
942
943
Hardware Setup
944
Mass Properties
Summary of Mass Properties
Overview 948
948
List Processor
Understanding the List Processor
Introduction 952
Geometry 953
Finite Elements 981
Miscellaneous 986
INDEX
952
945
Introduction to Patran
Patran Framework
3
6
1.1
Introducing Patran
Patran is an open software system, used primarily in mechanical engineering analysis. It is comprised of
the following components:
Engineering Modeling Functionalities
Extensive engineering capabilities, including:
Full set of geometric tools for creating, modifying, and parameterizing model geometry.
Extensive finite element modeling tools for creating and modifying analysis models. Automatic
1.2
Patran Framework
The open architecture of Patran calls for a number of special features to help you acquire input data,
manage models, and export analysis models and results. Among the most significant of these are:
CAD interfaces
File and group definitions
Viewport and display options
Patran Command Language (PCL) development
User Customization capabilities
Some of these features are activated through menu keywords, icons, and application windows. Others,
such as PCL development, utilize some more advanced programming know-how.
How Patran Imports Data
Patran accepts data from CAD system user files, Patran neutral files, and IGES files. Using one of
Patrans CAD Access Modules, you can import CAD geometry and topology directly into your database.
Once in your database, you can build upon or modify CAD geometry.
Managing Large Models in Patran
All project-related information is stored in files of various types and formats. The major file types that
are created or accessed during Patran operations are:
Database file (.db extension). Contains a complete record of all geometric entities, finite
element entities, properties, and analysis results associated with an Patran model.
Session file (.ses extension). Contains all database related commands and corresponding
specific database.
Miscellaneous files. Hardcopy files, Patran neutral files, IGES files, and others.
File management options include creating new databases, opening, saving, and closing existing
databases, and accessing external files.
Groups
A group is a collection of selected geometric or finite element entities brought together to simplify
working with a number of entities simultaneously. Groups can be created and dissolved, displayed or
hidden, transformed (e.g., rotated, mirrored), and have entities added or removed.
A special benefit of groups is evident in the design of symmetrical parts or assemblies. As an example,
if in the design of the front suspension system of an automobile the entities of the left front suspension
assembly are identified as a group, then the identical right front suspension assembly can be modeled by
a simple mirror transformation. Both groups can then be used in a complete vibration analysis to predict
dynamic response, stress, and fatigue life of the suspension components.
Viewports
A viewport is a named graphics window through which you look at a model.You may utilize a number
of viewports to visualize different phases of the project. For example, in one viewport you can show the
entire geometric model, in another you can magnify a small detail. Additional viewports may contain a
finite element model or annotated result displays.
Viewports are especially useful for presenting before and after pictures simultaneously. For
example, following a thermoelastic stress analysis you may choose to post three viewports to the screen,
the first to show the geometric model, the second the meshed model with applied thermal loads, and the
third to display a plot of the resulting stresses.
You can control how the model appears in a view, its orientation, scale, rendering style, the presence of
labels, the position and intensity of the light source, and other display features.
How Patran Exports Models
Patran can prepare input data in specific formats that comply with the requirements of a number of finite
element analysis codes. In addition to
MSC-provided codes (including the default, MSC Nastran), you can pick among several others
commercial codes as well as in-house proprietary analysis programs. While different analysis codes may
define components of a finite element model differently, Patran is capable to simply change the database
definitions of these components to suit the code you opt for.
Selectable analysis types include structural, thermal, and fluid dynamics.
Patran Command Language
Patran provides an environment into which proprietary in-house developed codes can be easily integrated
with the PCL.
User Customization
PCL enables you to automate repetitive tasks, establish individualized startup configurations, and create
new menus, icons, and forms. With PCL, you can readily integrate proprietary analysis codes developed
at your site into the Patran environment with the following results:
New analysis code names, as well as code-specific properties and functional assignments, will
proprietary program for analysis. Conversely, finite element models and analysis results created
with an in-house program can be loaded directly into the Patran database.
Database templates can be customized to suit individual requirements.
Mouse communication. Click on menu keywords, icons, and buttons to identify selections. Pick
and manipulate objects in viewports; resize, reposition, and iconify (make into an icon)
viewports; copy and paste text.
Keyboard communication. Use shortcuts to open menus and to accelerate keyword selections,
edit history list commands, enter special comments and commands on the command line.
1.3
Help>... 7
HTML Based Online Help
1.4
Help>...
Use the Help>... command to acquire the following help.
Opens a new Browser window and displays the entire contents of the
Help system.
PCL
Accesses all PCL Help with a separate contents list and index.
On Help
Technical Support
Reports the key highlights and describes all the new features for
Patran.
About Patran
Contains the version and legal notices for the Patran product software.
via WWW
Links you to the MSC Software website for information on key topics.
Context-Sensitive Help
To quickly access Help on any topic (form) from within Patran, simply press the F1 key. The appropriate
Help topic will appear in a new Browser window on your screen.
Help>...
Patran Workspace
Modeling Window
10
12
14
21
22
10
2.1
Modeling Window
The Patran workspace, or modeling window, is the area of the screen where you interactively perform all
Patran operations. The modeling window consists of two major sections, the Patran Main Form and the
graphics viewport.
Patran Main Form
The components of the Main Form are the Menu Bar, Tool Bar, Application Bar, History List, and
Command Line. The movable History List and Command Line windows are typically positioned below
the Graphics Viewport. The following is a partial display of the Main Form:
Applications Bar
Menu Bar
Tool Palettes
History List
Command Line
Graphics Viewport
The graphics viewport is a window where the geometric model, finite element model, and finite element
analysis results are displayed.
Origin Marker
Y
Z
12
2.2
File
Group
Viewport
Viewing
Display
Preferences
Tools
Help
Utilities
Tools
The Tools menu provides access to Patrans special functions (e.g. Mass Properties) as well as to optional
analysis modules that are available on your system.
Help
The Help menu retrieves online documentation for all Patran features and provides various operational
tips, such as keyboard shortcuts, mouse functions, as well as tutorial assistance.
Utilities
The Utilities menu provides easy access to various utilities available in Patran. The Utilities menu is
available by default on Patran startup form but a database must be opened before accessing any utility
from it.
14
2.3
To move a tool palette, click on its outer boundary and drag to any other part of the window.
You can create new icons and function definitions to add to the tool bar. Copy the tool bar definition file
p3toolbar.def from the installation directory into your home directory where you can make your
modifications. The new file will then be used whenever you start up Patran.
File>New
Brings up the New Database form where you can define a new
model.
File>Open
File>Save
Copy to
Clipboard
Undo
Abort
Reset
Graphics
Refresh
Graphics
16
Heart Beat
Interrupt button
Red--performing an operation that cannot be interrupted.
Fit View--resizes the view so that all model entities fit inside the viewport window.
Model Center-- sets the rotation center to the centroid of entities in the view.
18
Element Shrink-- Toggles the display of Element Shrink between ON and OFF.
Point (0D) Element Marker On/Off--toggles the display of Point (0D) elements.
Front View--Rotations: X = 0, Y = 0, Z = 0
20
2.4
Application Buttons
Geometry
Elements
Loads/BCs
Materials
Properties
Load Cases
Fields
Analysis
Sets analysis parameters, submits the analysis, and reads the output files.
Results
XY Plot
22
2.5
$?
$#
PCL comments.
Selecting Entities
33
43
24
24
3.1
The term widget is a programmers jargon; it refers to all buttons, switches, listboxes, spreadsheets,
etc. displayed in forms, as well as to the forms themselves. Patran is so designed that the term widget
should not appear except where it is unavoidable, such as when custom interfaces or environments are
created.
26
Apply Button
Auto Execute
Cancel Button
Data Box
Filter
OK Button
Output ID List
Reset Button
Scroll Bar
Switch Button
Toggle Button
Default Values
Spreadsheet
Apply Button
Apply
or
-Apply-
Implements all inputs and selections you specified in a form. The slight difference between the text of
the two buttons-- in the second one the word is offset by dashes--indicates a difference in their functions.
When you see the -Apply- button used in a form it means that:
This action is reversible--you can use Undo (System Tool Palette, 14) to reverse the operation.
this action activates a commit--saves the results of all actions performed (including the current
Closes a form and voids all inputs and changes you made just before canceling.
Coordinate Frame
Refer. Coordinate Frame
Coord 0
Allows you to enter the name of the coordinate frame in which the coordinate input is interpreted (for
more information on coordinate frames see Coordinate Frame (p. 27) in the Patran Reference Manual).
Databox
Databox label
Curve List
Many forms contain databoxes that accomodate a list of input data. The label identifies the type of data
that will be accepted in a particular databox. A blinking insertion bar in the data field indicates that the
focus is in the databox and it is ready to receive input. If the input involves entities on the screen, you can
pick the appropriate entities and the system will enter their name and ID number. Alternatively, you may
type or paste the required input data into the data field.
Default Values
Application forms often contain default values and settings. The types of defaults are:
fixed (global)-- automatically set for a new database
variable-- created during model construction
When you access a form for the first time, it will show the global default values. If you enter new defaults
or create new settings and invoke Apply, these will appear as defaults the next time you open the form.
Steps to modify a fixed default environment:
1. Open a new database.
2. Change all default settings as desired: colors, viewports, groups, analysis preference, named
views, etc.
3. Save the database under some name (e.g., my_template). Make note of the path of this new
file so that you can find it next time.
To apply the new default environment in a new database:
1. In the New Database form, select Change Template...
28
2. In the Change Template form, change the default path, if necessary, to wherever
my_template.db resides. Use the filter to locate it and select it from the database list.
3. Enter a new database name and pick OK. The new database will open in the
my_template.db environment.
Filter
Filter
A filter is used in applications where a list of selectable components may be longer than the number of
items that can be displayed in a listbox. With the filter you can isolate a single item or a group of several
items that comprise a subset of the list. For example, you may have defined a number of load cases, one
of them named Heavy. To access this load case (for example, to modify it), you dont need to scroll
through a long list to find its name in the listbox, instead, type heavy (entries are not case sensitive), press
the Filter button, and this load case will be selected.
You can use the following wildcard symbols:
* (any character string)
? (a single character)
If, in the above example three of the load cases are named Heavy100, heavy300, and heavy500, you can
enter h* and now the displayed list will be the subset that consists of the load cases whose name begins
with the letter h.
OK Button
OK
or
- OK -
The OK button performs almost exactly as the Apply button, except that it also closes the form.
Output ID List
Surface ID List
21
Output IDs
Node ID List
73
Element ID List
51
Output ID lists display the default ID number that will be assigned to the next entity of a given type.
However, you may enter any other number if you wish. If the number you specify is higher than the
default, numbering will begin at this new number. If you enter a lower number, you will be warned that
these entities exist and will be asked for permission to overwrite. You can specify any numbering
sequence, for example you can choose 44 68 77 and 92 for the next four entities. Spaces are used as
delimiters.
Reset Button
Reset
Reset
When you press this button, anything you changed in a form will return to its previous value.
Scroll Bar
End arrows scroll in the selected direction
Scroll bars appear below or at the right side of listboxes. They are used when the contents of the box are
too long or too wide to appear in their entirety.
Switch Button
Option 1
Option 2
Option 3
With the switch buttons you can select one option in a short list of options. The options are mutually
exclusive.
Toggle Button
Lights
A Toggle button is a switch that allows you to turn a particular option or selection ON or OFF. The label
identifies the option (e.g., Lights). The toggle switch operates in a press on/press off manner.
30
Spreadsheets
Tabular Data Input Spreadsheets
This type of spreadsheet is used to input data into a one-, two-, or three-dimensional table.
Value
1
2
3
4
5
6
7
8
9
OK
3. Press the Enter key. The input data will appear in the selected cell and the selection box will move
down one level.
Note:
Spreadsheets display at a default maximum size. If a larger size is required, look for a local
Options... menu to increase the setting.
DOFs (1)
UX
DOFs (1)
1.
UX
1.
44
UZ
Create Dependent u
Create Independentuu
uu
uu
Modify
Delete
Coefficient = 1
Auto Execute
Node List
Node 1
DOFs
UX
UY
UZ
Apply
Reset
Cancel
32
3.2
Selecting Entities
Most Geometry and Finite Element applications require that you select one or more entities displayed on
the screen. For example, if you want to create a mesh seed, the required selection is one or more curves,
or edges of a solid or a surface. Accordingly, the Select databox in the Elements Application form will
indicate that a list of curves must be the input to complete this action.
Curve List
If the insertion bar is not already blinking, you must click inside the blank form field before you can select
the entities.
Screen Picking
When you pick entities with the cursor, you can select them individually or pick several entities at the
same time. After selection has been completed, the system will write the names and ID numbers of the
selected entities into the databox that initiated the picking.
Some of the settings of screen picking, such as highlighting, criteria of entity inclusion in picked areas,
and the format of a Select Menu, are established in the Preferences >Picking menu (see
Preferences>Picking, 466).
Picking Single Entities
Depending on what you chose in Picking Preferences, an entity will be selected either when you click
anywhere on it or when you pick it near its centroid. With another preference you can ensure that entities
are highlighted as the cursor sweeps across them in order to make it easier to select the correct entity.
Picking Multiple Entities
To select a number of entities at the same time, you must surround them either with a rectangle or an
arbitrary polygon. The Preferences menu provides three options for delimiting entity selection:
all of the entity must lie within the enclosure
any portion of the entity may lie within the enclosure
only the centroid of the entity need to lie within the enclosure
34
B
Polygon Picking
The enclosure is in the shape of a polygon. Click the polygon icon in the Select Menu (see
Preferences>Picking, 466) pick the start point of the polygon (A), then drag the cursor and pick the next
point to set a new vertex of the polygon (B). As the lines of the polygon are formed, continue clicking
new vertices (C,D,E...) until you consider the polygon complete. Double-click at the last vertex (or return
to the starting point) to complete the polygon.
Another way of initiating the polygon pick is using the Ctrl key instead of picking the polygon icon. Press
and hold down this key while you click the left mouse button at a start point and all consecutive points
of the polygon. Double click to close the polygon.
Cycle Picking
Entity picks, whether single or multiple, may inadvertently catch entities you did not intend to select,
especially if several entities are close to one another. The system will make it easier to pick the correct
entity from a number of possible choices, provided that the auto execute feature is turned off. A form will
be displayed with the names of all possible selections. You can cycle through all choices until you pick
the desired entity.
Selection
Surface 3
Surface 2
Previous
Next
Control Sequence
Polygon Picking
Ctrl+LMB
Add
Shift+LMB
Reject
Ctrl+Shift+RMB
Replace
LMB
Select Menu
When you invoke a command that requires entity selection (e.g. Delete), the system will display a Select
Menu. A Select Menu consists of two sets of icons, the first set is common to all select operations, the
36
second set consists of icons specific to either geometry or FEM entity selections. A typical Select Menu
is shown below; the explanation of the Select icons will follow.
Polygon pick
Picking Icons
Select icons
Any Icon
The following entities are supported in the visible entity selection mode:
Geometry
FEM
Curves
Nodes
Elements
Solids
Surfaces
Faces of solids
Edges of surfaces and solids
Note:
When Visible Entity Picking is selected, the Rectangle/Polygon Picking (Multiple), 467
mode will pick any portion of the entity enclosed by the rectangle. The Enclose entire
entity and Enclose centroid modes are ignored.
Replace Pick--replaces a selected entity with the next entity you picked (default)
Add Pick--adds a selected entity to the list of entities already picked
Reject Pick--removes a selected entity from the list of entities already picked
38
Any Icon
This icon helps you control the entity picks in all select menus. If the action is associated with several
unlike entities, the icon will indicate that any geometric or finite element entity (but not both) is
selectable. For example to delete a solid, a curve, and two points, in the Geometry application you select
Delete>Any and the Any icon will consider all geometric entities relative to the enclosure you create.
If, however, you want to restrict the action to entities of a certain type only, you can specify the entity
type for your selection (for example Delete>Solid) and the Any selection will refer only to the selected
entity type (in this example to any solid). Assuming that the same four entities (solid, a curve, and two
points) are in the enclosure, just as before, this time only the solid will be deleted and the others will
remain untouched.
Go to Icons
When an action requires several levels of definition, secondary Select menus may be activated. For
example, when you rotate entities, you must define an axis of rotation. One of the ways of defining the
axis is by selecting its two endpoints (Axis and Vector Select Icons, 38). Therefore, when you select that
method of axis definition, the Point select icons will be displayed so that you can pick the appropriate
points. At the completion of this action you may want to return to the previous Select menu or to the
original Select menu that started all selections (for example, to select a geometric entity).
This icon will return you to the Select menu where you
started the action.
Go to Previous Menu
Icon
Selects the default coordinate frame and enters it in the Select databox.
Specifies a vector whose base is at the global origin and tip at an arbitrary point. Displays the
Point select icons to select this point.
Specifies a vector whose base and tip are both arbitrary points. Displays the Point select icons
to select both points.
Selects a node.
40
Selecting Curves
You will see these icons when you create new curves or when you need to select existing ones.
Selects a curve.
Selecting Solids
With these icons you can select solid geometry.
Selecting Surfaces
These icons are displayed for creating a surface or for selecting an existing surface.
Selects an edge-point on a
surface.
Selects an interior point on a
surface.
Selects a vertex of a surface.
Selects nodes
42
Selecting Elements
These icons are displayed whenever you are selecting elements or parts of elements.
3.3
44
File Commands
57
67
46
46
4.1
For more about importing Patran 2.5 Results Files, see Patran 2.5 Results Files, 46.
Startup Files
Patran relies on a set of required and optional external text files during the startup of a new session, as
follows:
The settings.pcl file, 47 is used to define a default environment for the Patran session. The environment
includes hardcopy parameter settings and operation of Patrans 3D driver.
The p3prolog.pcl and p3epilog.pcl Files, 54 are used to customize and automate PCL capabilities within
Patran, and to provide a way for customized forms and widgets to be created.
Startup Session Files, 54. There are a number of ways to customize automatic execution of user defined
session files, or to specify the file name of a new session file to be written to by Patran with its startup
session file feature.
For more information on these user defined customization files for Patran, continue onto the following
sections.
The settings.pcl file
Patran searches for and reads a file called settings.pcl at the beginning of each session. The
settings.pcl file contains parameter values which define the environment in which the session will
be run.
The search for this file begins in the default directory first, then moves to the home directory, then finally
to the delivery directory. If this file cannot be found, a new settings.pcl file will be created in the
default directory with a set of default parameter values.
If an existing settings.pcl file is found which contains a missing parameter value, a default value
will be assigned.
Many of the parameters may be changed during the Patran session using the available widgets and forms.
To ensure the Patran environment defined during the session is maintained, the values in the
settings.pcl file that were used at the start of the session will be added to or overwritten (unless the
found settings.pcl file was write protected).
48
All of the entries in settings.pcl are written in PCL and most have calls to the PCLs built-in
functions. The parameters of interest to most users are presented below. The default values are in
parentheses. For more information, please refer to File>Print (p. 223) in the Patran Reference Manual.
create_dup_geometry (3)
graphics_colors (150)
message_warning (3)
history window.
2 indicates that a warning bell should also be rung.
3 indicates that a modal form should be displayed as
VisibleHistoryItems (3)
ApplSwitchIsPopup (False)
Show_Icon_Help (True)
Save_Vis_History_Item_
Count (True)
50
p3team_graphics_
hardware (NO)
entity_picking_
cursor (holeangle)
select_menu_layout
(vertical)
select_menu_type (form)
"result_capture_filename","patran
.prt"
"result_quick_avg_domain", "All"
"result_quick_extrap_method",
"ShapeFunc"
"result_quick_transform",
"Default"
"result_quick_avg_method","Derive
Average"
NastranResultsOutput,XDB Only
52
"ResTmplAutoLoadOpenDb", TRUE
"ResTmplAutoLoadAllFiles",
TRUE
"result_dbopen_display", TRUE
Use_Pref_Elem_Test",
def_value
"prop_form_full_refresh
_limit", n_prop_limit
used.
Properties are not re-read from the database and the property
(command line) will cause a listbox refresh the next time the
Property/Create or Property/Modify form is opened.
54
modified using the UNIX setenv command or the Windows NT set command.
The following is a table of all hardcopy variables defined in Patran. Further explanation of the variable
values can be found in File>Print, 223:
Other Preference Environment Variables
Description
Duplicate
geometry creation
control
Preference Name
create_dup_bord
ered
Default
Possible Values
1
2
3
These interfaces are made up of the system start-up file interface, the command line interface (both of
which are described here) and the session file forms. See File>Session, 221 interface.
Startup using system files
Patran allows start-up files to control its initialization. In addition to other start-up and PCL commands,
the following two lines may be included:
sf_record_default( STRING init_rec_file, LOGICAL
record_rotations)
sf_play_default( STRING init_play_file, LOGICAL single_step)
These commands should only be placed in p3epilog.pcl. These commands select the initial files and
option modes. If these lines are not present, there is no default play file, patran.ses will be the default
record file (unless overridden later) and both options default to FALSE.
Recording session file initialization
The first line (sf_record_default) initializes the recording session file and form. The default
recording file (<init_record_file>) can either indicate no file to suppress the default file (e.g.,
specify an empty string: ), specify the file from its base name only (e.g., patran will use
patran.ses.xx) or specify a base name and an extension (e.g., new.ext will use
new.ext.xx). The <record_rotations> flag must be set to TRUE if rotation events are to be
written to the session file.
Playing session file initialization
The second line (sf_play_default) initializes the playing session file and form. The default playing
file (<init_play_file>) can either indicate no file, specify a file name as above or specify a file
with extension and version (e.g. temp.ses.01). It is highly recommended that either the no file or
file.extension.version form be used. Using one of the other forms may conflict with the
current recording session file name--usually resulting in an empty file being erroneously played. The
<single-step> flag must be set to TRUE if the user desires to view and/or modify each played line.
Startup from command line
Patran also allows you to specify a playback file and/or a record file on the command line. The UNIX
command line options are -sfp <filename> (session file play) and -sfr <file name>
(session file record). The use of these options supersedes their previous values as specified in the system
files (see above). Specifying either of these options with no file name cancels any default files called out
by the system files.
The example below would suppress the recording session file and play test.ses.03.
p3 -sfr -sfp test.ses.03
56
4.2
58
The File menu functionalities are described below in the order in which they appear in the menu.
60
New...
Displays the New Database dialog box in which you enter the name of
a new model. The form presents the default md_template.db
template file; if desired, you can specify another previously defined
and saved template file.
When a new database is created, a md_template.db file is copied from
the Patran delivery directory into the default directory. This file
contains specific analysis code definitions for all Patran application
preferences and modules (e.g., MSC Nastran, MSC.Marc, etc.). Thus,
when you create a model, you are accessing an explicit set of the
available analysis code definitions within the template file.
You may customize the md_template.db file to ensure that all
databases will reference certain specific definitions in the following
areas:
Materials--if your site has a set of materials that is more extensive
than the standard set, you can add this material information to the
new template database.
Elements--if you dont want certain element types appearing when
a new database is created, you can exclude those from the standard
Patran element library in the new template database.
Application preferences--you can eliminate from the new template
Open...
Displays the Open Database dialog box in which you can select the
name of an existing Patran database.
Set Working Directory to Database Location
62
Open Recent...
Allows you to select from a list of recently accessed database files. The
number of files visible is controlled by settings.pcl file environment
variable:
pref_env_set_integer("max_num_recent_files",num_files)
If this toggle is ON, selecting a file from the Recent Files listbox
will cause that database to be opened automatically with no need to
press the OK button. The form is then closed.
Maximum Recent Files
Change this value to view more or less files in the Recent Files
listbox.
The settings of these toggles and databox are written to the
If present in the settings.pcl file, the toggles and/or databox will be set
to the values found. When the File/Open, File/New or File/Open
Recent forms are closed, the values of these toggles and databox are
written to settings.pcl if this file is present and can be written to (not
read only).
Close
Save
Although Patran updates an open database after each operation, the last
update step is not saved to disk, it remains in memory only. The Save
command ensures that the most recent update is included when the
current state of the database is committed to disk.
Save a Copy...
Opens the Save a Copy form that enables you to save a copy of your
database under a new name.
Utilities
Reclaim...
Revert...
Rebuild...
64
Import...
Export...
Translates an open Patran database into an IGES file, STEP AP203 and
AP209, Parasolid xmt, or a Patran neutral file, based on the entire
model, specific entity types, or Patran groups.
SimXpert
SimManager
Publishes and retrieves Patran databases and other related analysis files
directly from within Patran with the SimManager client. Once logged
on, the user may publish and retrieve as well test connection and access
the Web Client. The server settings need to be set in order for the
SimManager client to communicate with the server. The following
variables need to be set:
SM_RICH_CLIENT_IC_HOST <host_name>
SM_RICH_CLIENT_IC_PORT <port number>
SM_RICH_CLIENT_IC_PROTOCOL <http or https>
SM_RICH_CLIENT_IC_WEBCONTEXT SimManager
RC_ROOT
JDK_PATH
APPS
ACTION_LOC
JARS_PATH
CLASSPATH
SCA_SYSTEM
SCA_RESOURCE_DIR
SCA_SERVICE_CATALOG
SCA_JAVA_COMP_PATH
SCA_JVM_CONFIG
RC_LIBRARY_PATHFor more information on using SimManager
please see the SimManager documentation. Client access to a
SimManager server via Patran is only supported on Windows
machines.
Session >
Play...
Executes a specified Patran session file (see Session File, 46) either in
its entirety or one command at a time for debugging or editing
purposes.
Record...
Creates a new file with a user-defined file name and records all
database related commands executed during the current Patran session
from the time this file was opened. The default patran.ses session
file will be generated as well.
Print...
Images...
66
Report...
Quit
Closes an open database, saves any changes made, and ends the active
session.
4.3
File Commands
The File Menu commands activate dialog boxes in which you interact with Patran. Although the
commands are specific to the file-related action you want to perform, dialog box entries that deal with
file names and types are common to several commands.
Look In
This text field displays the location where Patran starts looking for the various folders in which it can
create and manipulate databases, session files, and reports. The subordinate folders and existing database
names are also listed. If you dont remember where your files are located, move up and down the
hierarchy of all folders with the Windows icons, the Windows Explorer, or use Start>Find>Files or
Folders on your Desktop to select the correct path for your database search.
File Name
Enter a new name or select a name from the displayed list. This text field, as well as the Files of Type
field, also shows the default extension automatically assigned to different kinds of files (e.g., *.db, for
database file). If you enter a name that already exists, you will be asked whether you would like to delete
the existing database and create a new one.
Naming Conventions
Although Patran does not impose any limitations on file names, certain restrictions do exist, mainly due
to the naming requirements of various CAD systems and translators, as well as analysis codes. Therefore,
it is best to avoid spaces and other special characters from file names. Also, be aware, that some analysis
programs limit the number of characters allowed in a file name and may truncate a longer name to the
allowable length.
Files of Type
This text field shows the file type appropriate for the selected action, as well as the automatically assigned
file name extension.
68
File>New
File>New
The File>New command sequence activates the New Database dialog box.
In addition to the file name inputs that are required, two optional data entries are:
Change Template Button/Template Database Name
File>New 69
Creating a New File
Change Template
If you press this button the Database Template dialog box will display
all saved template database names. Select the template you want to
use. For more about templates, see New..., 60.
Modify Preferences
Turn this toggle on (4) and the New Model Preferences form will be
presented right after the new database is created. In this form you can
specify a tolerance value (see Global Model Tolerance, 459), the
analysis code you intend to use, and the type of analysis you want to
perform on the model.
Changing a Template
The Database Template allows you to select a a previously defined and saved template file that will be
used as the source when a new database is created.
70
File>New
Modifying Preferences
The New Model Preference form allows you to select those preferences that must be set at the beginning
of the modeling process to avoid invalid input and irreversible results.
File>New 71
Creating a New File
Tolerance
edge
topologically congruent solids--two solids that share the same
surface.
If you attempt to create an entity that would be coincident with
existing geometry, a system message will notify you that this entity
already exists and will ask you if you wish to create a duplicate.
When two surfaces appear to be topologically congruent but meshes
created on them do not match at their boundary, it is probably because
the global model tolerance was set too low at the time the surfaces
were created. If the geometry does connect but there are gaps greater
than the tolerance, it may be necessary to relax the tolerance. On the
other hand, too large tolerance may cause inaccuracies in the model.
The topology, or connectivity, of a model is determined when
geometry is created, imported, or accessed from a CAD system. Once
connectivity is set, you cannot modify it unless you delete the
geometry, change the tolerance, then re-create the geometry.
Global Model Tolerance can also be specified in the Patran Main
Forms Preferences menu.
Based on Model
Default
Uses the current setting of the global model tolerance defined in the
template database, normally .005.
72
File>New
Maximum Model
Dimension
Enter the approximate maximum model size if you selected the Based
on Model tolerance definition.
Analysis Code
Select the program you intend to use for the finite element analysis.
Analysis Type
File>Open 73
Opening an Existing File
File>Open
The File>Open command sequence activates the Open Database dialog box. Make sure you are
displaying the appropriate folder in which the database resides, then select the name of the database you
want to open.
74
File>Save a Copy
File>Save a Copy
Use this command to save a copy of your database under a different name.
If you turn this toggle on (4), the journal file associated with the
database will also copy to the new database. Note that the copied
journal file will still refer to the name of the original database; you
must edit the name to refer to the copied database.
Look in:
If you want to save the copy to a different folder, select the new folder.
File Name
File>Reclaim 75
Freeing up Unused Disk Space
File>Reclaim
The Reclaim utility frees unused disk space allocated to the currently open database. Normally you may
not need to use this feature, since the Reclaim process is executed automatically when you save or close
a database that contains a significant amount of free space, provided that the following two conditions
are met:
The database can be reduced by an estimated one megabyte or more.
The current database fragmentation is more than 5% of the size of the total database.
Important: When you reclaim database space, the files Undo history is deleted. However, once the
reclaim process is complete, the Undo capability will be reestablished after the next
committed action and the database will again maintain Undo states.
When you request to reclaim database space, you will receive the following a message:
Whether you proceed with the reclaim utility or not will depend on what is more valuable, the amount of
database space you can recover or retaining the Undo history of your file.
76
File>Revert
File>Revert
This utility erases all changes made during the current session and returns a database to the state in which
it existed when it was first opened.
The Revert utility is not automatically active. To make it available, you must do the following:
1. Select the Preferences menu in the Main Form.
2. Pick the keyword Global.
3. Click on the toggle in the selection box (4) Enable Revert Operation. This action will take effect
when you next open this database.
4. Close the database.
5. Open the file; revert will be available in the database. Proceed creating entities.
6. If you want to return to the original state of the database, click File>Utilities>Revert.
7. The following message will appear:
File>Rebuild 77
Rebuilding a Model from a Journal File
File>Rebuild
With this utility, you can rebuild a model created in Patran using a journal file. The journal file contains
a history of all user activity required to create the database, even if it spanned several separate modeling
sessions. Because it is a sequential text file of PCL instructions, it can be edited using a text editor.
This utility is available only if there is no open Patran file. When you invoke File>Utilities>Rebuild, the
Rebuild Database dialog box will display the list of journal files contained in the last-used folder (you
can search through other folders as well).
Select the journal file to run. Once a journal file is read and executed, the database will be completely
restored.
78
File>Import
File>Import
With the File>Import command you can bring in model or results data created outside of the current
database. If the imported object is specified as Model, the Import dialog box buttons and text boxes are
related to model import choices. Imported model files may come from a number of different sources,
therefore model data may be in Patran database format, Patran 2.5 neutral file format, MSC Nastran input
file format, or in one of several CAD formats.
Look in:
Shows the drive or folder where the search starts for the incoming
database. The text field below displays the folders and files where you
may locate this database.
File name
Files of type
Indicates the valid file type and assigned file name extension, unique
to the selected source of the imported file.
Source
File>Import 79
Importing Models and Results
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Options
Equivalence Options
80
File>Import
File>Import 81
Importing Models and Results
Spreadsheet Headings
Numbered Entity Offset Defaults
This frame provides building blocks for resolving conflicts between duplicate entity identification
numbers during the import process. The basis of the these building blocks is a count of successful
database imports called the Submodel.
Numbered Entity Offset Defaults
Increment
* Submodel
1
10000
= Default Offset
10000
Default Offset
Indicates the amount by which the ID numbers of the incoming entities of the corresponding type will be
incremented in the current database. A large offset makes it easier to group IDs for imported submodels
and organize the database. The Default Offset is the product of the Increment and the Submodel number.
Increment
An arbitrary offset increment you assign.
Submodel
The number of successful imports; this number is incremented after each subsequent import. If desired,
it can also be overridden by any arbitrary number.
Named Entity Prefix Defaults
This frame provides building blocks for resolving conflicts between duplicate entity names during the
import process.
Named Entity Prefix Defaults
Prefix
// Submodel
= Default Prefix
SM_
001_
SM_001_
Default Prefix
Indicates an alphanumeric prefix applied to incoming entity names. It may be used to organize the
database based on each imported submodel. The Default Prefix is a concatenation of the Prefix and the
Submodel number.
82
File>Import
Prefix
An arbitrary prefix that must start with a letter. The default, SM_, stands for submodel.
Submodel
The Submodel number, incremented after each successful import.
Duplicate Entity Merge Options
When entities in an incoming (secondary) database are of the same type and name as those that already
exist in the receiving (primary) database, you can resolve the duplication as follows:
Insert a prefix in front of the incoming entitys name and import it with that name.
Try to combine the two entities into one. If the two cannot be combined because of conflicting
File>Import 83
Importing Models and Results
will be added to the group in the primary database. A new group is created to contain all entities from the
imported database. This group is given the name specified by the entity prefix.
Duplicate Entity Merge Options:
Entities to Merge Upon Duplication
Material
Load/BC
Compare Names
Load Case
Element Property
Compare Names
Entities to Merge Upon
Duplication
Field
Group
DOF List
In these cells you specify the entities you want to merge if a duplicate
name is encountered. If you do not click the merge toggle (or if the
merge attempt fails), a prefix will be inserted in front of the name and
a new entity will be created to hold the data.
For those entities with a Compare Names toggle, click the ones that
must have duplicate names to merge. If this toggle is ON, the entities
in the primary and secondary databases must have the same name and
the same data to merge.
If the toggle is OFF, the entities in the receiving and imported
databases need only have duplicate data to merge. If a duplicate name
does exist in the primary database, the imported entity will merge with
it. If a duplicate name does not exist, the imported entity will merge
with the first alphanumeric entity found with duplicate data.
Significant Digits
0.234925E+08
0.234925E+08
Spreadsheet Cells
The cells in the spreadsheet identify the imported entities and specify certain characteristics.
84
File>Import
Import Column
Current Database Ranges
Import?
Point
All
MinimumID
1
MaximumID
250
ID Offset
10000
Name P
Not Us
In the Import column you select which entities of a given type are to be imported from the external
database (All, None or a List). Group membership provides additional control of entities. For entities that
can be placed in groups, if All or a List of groups is specified only those entities that are in the selected
groups will be imported. If None is specified for groups, group membership is not a consideration.
For example, if you select All for Elements, and All for groups, and if Element 100 is not in any group,
Element 100 will not be imported. However, if you pick All for Elements, and None for groups, Element
100, which is not in any group, will be imported.
Import Filter Options
If multiple cells from the column are selected at one time, the values for those cells are simply toggled
from All to None, or vice-versa.
File>Import 85
Importing Models and Results
If you select a single cell, a second dialog box will provide a set of options.
Entities to Import
With each listed entity type, you can choose to import all entities of a
give type, none of them, or those specified in an input list. If you set
the switch to Input, you enable the List databox and may input a list
manually.
<entity> List
Enter the desired list of entities. This label will vary according to the
entity type you selected (e.g., Curve List).
Preview Database. . .
Displays the Patran Database Preview form that shows the entities,
and their corresponding ID numbers, as contained in the import
database.
All
MinimumID
MaximumID
250
ID Offset
10000
Name P
Not Us
These columns show the range of identification numbers for the corresponding entity type in the current
(receiving) database. Seeing these numbers may help you decide what ID offset values are most
appropriate for that entity type.
86
File>Import
ID Offset Column
Current Database Ranges
Import?
Material
All
MinimumID
1
MaximumID
250
ID Offset
10000
Name P
Not Use
This column indicates the number by which the IDs of the incoming entities are to be incremented
relative to the entities of the corresponding type that exist in the current database.
File>Import 87
Importing Models and Results
Offset Options
If you select an ID Offset cell, a second dialog box will provide a set of options.
Offset Option
Offset Value
88
File>Import
All
MinimumID
Not Used
MaximumID
Not Used
ID Offset
Not Used
Name Prefix
SM_001_
This column shows the prefix that is to be applied to incoming entity names. If the merge toggle for the
corresponding entity type is ON, a prefix is applied only if the name duplicates the name of another entity
in the current database and the merge operation failed due to conflicting data. See Duplicate Entity Merge
Options, 82 for more details.
Prefix Option
Prefix Value
File>Import 89
Importing Models and Results
Equivalence Options
Equivalencing is a process in finite element modeling whereby all coincident nodes are reduced to a
single node. Two nodes are coincident if they are within a predetermined tolerance distance from each
other (the number of significant digits for the equivalence tolerance is set in the Import Options form, see
Significant Digits, 83). The change brought about when nodes are equivalenced is propagated throughout
all other FEM definitions, (element connectivity definitions, MPC equations, loads and boundary
conditions), geometry definitions, and groups.
ID Numbers
By default, the highest coincident node ID at a location in the secondary model will equivalence to the
highest coincident node ID in the primary model.
Loads and Boundary Conditions
If the LBC toggle in the Patran DB Import Options spreadsheet is OFF, secondary LBCs will not be
merged with primary LBCs. If this toggle is ON, there are two possibilities in merging loads and
boundary conditions, depending on whether identical LBCs exist in the current database and the import
database (two LBCs are considered identical if their types, set names, scale factors, LBC data, and
coordinate frames are all equal):
If a secondary LBC is identical to a primary LBC--the secondary LBC will be equivalenced to
the primary LBC and will no longer exist in the merged model. The application region of the
resultant LBC in the merged model will cover both the primary and secondary application
regions.
If a secondary LBC is not identical to any primary LBC--the secondary LBC will be embedded
into the merged model, its name will be prefixed if the same name is found among the primary
LBCs, and its application region and coordinate frame will be updated to the new IDs.
Discrete FEM Fields
Discrete FEM fields from different models are never considered to be equal, therefore, LBCs with data
referencing discrete FEM fields can be equivalenced with a special option in the Equivalence Options
dialog box that allows you to perform inter-model equivalencing of LBCs that reference discrete FEM
fields. Accordingly, two discrete FEM fields (not necessarily with the same name) must be combined into
one. Referenced by the resultant LBC, the combined discrete FEM field will contain all data from both
the primary and secondary FEM fields.
LBCs are categorized into vector loads (e.g., force), or scalar loads (e.g., pressure), and boundary
conditions (displacement). You can choose one of several equivalence options available for each
category to produce the data at the surviving nodes after nodal equivalencing. Note that these equivalence
options are only applied to the pairs of nodes being equivalenced. To be affected by the equivalence
options, both nodes in a pair must be listed respectively in the two discrete FEM fields being combined.
Other nodes in the two DFEM fields will be copied with updated IDs and their associated values will be
copied to the combined DFEM field, which inherits the name of the DFEM field from the primary model.
90
File>Import
Analysis CF at
Secondary Node
Analysis CF at
Equivalenced Node
Message
Level
Global
Global
Global
No
Local-1
Local-1
Local-1
No
Global
Warning
Local
No
Global
Warning
Global
Warning
Global
Warning
Local
No
Local-1
Warning
Local-2
Warning
Local-1
Warning
Fatal
Fatal
Fatal
File>Import 91
Importing Models and Results
92
File>Import
Equivalence
Nodes/Geometry
Tolerance Method
Tolerance Source
You can accept the tolerance value defined either in the current
database or in the import database, or you may choose to specify a new
value.
Equivalence DFEM
Loads/BCs/Props
This toggle controls whether discrete FEM fields are combined when
loads and boundary conditions or properties are merged. Two discrete
FEM fields referenced by duplicate LBCs or Properties (one in the
current model and another in the import) will be combined into one
discrete FEM field. If this toggle is ON (default), further items
pertaining to LBC equivalencing options are enabled.
DFEM Boundary
Conditions
Specify how vector loads are merged within a DFEM field. By default,
the loads in the primary model override the incoming secondary model
values. Optionally, the secondary values can be added to the existing
primary values.
Specify how scalar loads are merged within a DFEM Field. By default,
the loads in the primary model override the incoming secondary model
values. Optionally, the secondary values can be either added to the
existing primary values or merged with them.
File>Import 93
Importing Models and Results
invoked either from the Import dialog box or from the Import Filter Options form. If desired, you can
generate a named report file from the information displayed in the spreadsheet.
94
File>Import
File Formats, 883 provides more information about the neutral file system.
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Neutral Options
Brings up the Neutral Import Options form that enables you to select
the types of entities targeted for import.
File>Import 95
Importing Models and Results
Define Offsets...
96
File>Import
Assigning Offsets
Same for all entity types:
click on Offset, type the offset in the Input Offset Value data, press Enter, or
pick Automatic Offset to let the system assign offset automatically.
File>Import 97
Importing Models and Results
click on an entity, type the offset in the Input Offset Value data field, press Enter, or
select Automatic Offset.
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Brings up the Entity Selection form that enables you to select the types
of entities targeted for import.
98
File>Import
File>Import 99
Importing Models and Results
Define Offsets...
100
File>Import
Assigning Offsets
Same for all entity types:
click on Offset, type the offset in the Input Offset Value data, press Enter, or
pick Automatic Offset to let the system assign offset automatically
File>Import 101
Importing Models and Results
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Express Options
Brings up the Express Import Options form where you can select the
type and attributes of entities targeted for import.
102
File>Import
File>Import 103
Importing Models and Results
Import Preferences
Activates the Import Preferences dialog box in which you can specify
how certain geometric entities will be represented in the Patran
database.
Entity Types
Identifies the classes of geometric entities from which you can select.
Geometry Types
Specifies the various kinds of entities available within the entity class
you selected (for example, if the Entity Type you selected was Solid,
the Geometry Type may be Solid of Revolution)
Entity Colors
Entity Layers
All Layers
Layer Numbers
Turn All Layers OFF and identify the layers on which the imported
entities reside.
Group Classification...
Allows you to display the contents of the import file to inspect prior to
actually bringing it into your database.
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
EXPRESS file with _Ln appended. For example, if the EXPRESS file
name is test.model and there are two layers 1,2, then the two groups
will be named: test_L1 and test_L2. See Create Groups from Layers,
117 for additional information.
104
File>Import
Solid Representation
Enable Geometry Tracking If ON, a geometry tracking log file will be created to describe
geometric attributes of imported geometry.
Import Action
Import Geometry
Calculate Model
Processes the file to help determine the best tolerance for geometry
import.
Tolerance
File>Import 105
Importing Models and Results
106
File>Import
File>Import 107
Importing Models and Results
Group Name
Select the class of the imported geometric entities (e.g., Curve) whose
members will be added to the group.
Highlights the entities that belong the class selected above. Pick one,
several, or all to add to the group.
Display the Patran groups that have been defined for imported
entities.
108
File>Import
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
IGES Options
Brings up the IGES Import Options form that enables you to specify
the types and attributes of entities targeted for import.
IGES Entity
Number
IGES Entity
Number
100
Circular Arc
122
Tabulated Cylinder
102
Composite Curve
124
Transformation Matrix
104
Conic Arc
All Forms
106
Copious Data
126
128
130
Offset Curve
All Forms
108
Plane
File>Import 109
Importing Models and Results
IGES Entity
Number
IGES Entity
Number
Form 1
134
Node
Form 0
Unbounded Plane
136
Finite Element
110
Line
140
Offset Surface
112
141
Boundary
142
Curve on Surface
114
143
Bounded Surface
116
Point
144
Trimmed Surface
118
Ruled Surface
186
Manifold Solid-Prep
120
Surface of Revolution
190
Plane Surface
110
File>Import
File>Import 111
Importing Models and Results
Entity Types
Entity Attributes
Curve on Surface
Preferences
IGES file).
3D Curve--use real space representation (if exists in the IGES
file).
If trimmed surfaces import inaccurately, try alternating between 2D and
3D curve representation, provided that they both exist in the IGES file.
Invisible, Subordinate,
Pick any or all three to include the listed entity types in the import
process.
Color Filter...
Displays the Color Filter dialog box in which you can restrict entity
import based on color designations.
Layer Filter...
Displays the Layer Filter dialog box in which you can restrict entity
import based on layer designations.
Group Classification...
Activates a dialog box in which you can create new Patran groups for
placing imported entities.
Select Options...
Brings up the Options Form, where you can select translation parameters
for import.
Verify Boundary
Equivalence Edge
Vertices
112
File>Import
If this toggle is ON, the parasolid transmit file will be saved when a
Unigraphics-NX file is imported. This file will be assigned a.xmt_txt file
name extension.
File>Import 113
Importing Models and Results
IGES entities may refer to an IGES Color Definition Entity (Type 314)
that defines the color of entities.
All--import all entities that refer to the Color Definition Entity
None--exclude all entities that refer to the Color Definition Entity
Specify--enter the Color Definition Entities to import
114
File>Import
File>Import 115
Importing Models and Results
Group Name
116
File>Import
where the entities targeted for import reside in the CAD database.
Show IGES Groups
File>Import 117
Importing Models and Results
Options Form
You can select translation parameters for import or export on this form.
118
File>Import
Direct Way
Heal
Translate Hidden
File>Import 119
Importing Models and Results
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
CATIA Options
Brings up the CATIA Import Options form that enables you to select
the type and attributes of entities targeted for import.
Import to Parasolid
File Type
Specifies the type of the imported input file. This may be a CATIA V4
model file (.Model extension), a CATIA V5 part file (.CATPart
extension), a CATIA V5 product file (.CATProduct extension), or a
CATXPRES output file (.cat extension).
120
File>Import
File>Import 121
Importing Models and Results
122
File>Import
Import Geometry
The default, Import Geometry will import the geometry after the
Apply button is selected on the import form. The secondary toggle,
Import Preview will run the translator and provide a summary of
geometry and layer information without importing the geometry.
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Import Attributes
Entity Layers
All Layers
Layer numbers
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
CATIA file with _Ln appended. For example, if the CATIA file name
is test.model and there are two layers 1,2, then the two groups will be
named: test_L1 and test_L2. See Create Groups from Layers, 117 for
additional information.
Group Classification...
File>Import 123
Importing Models and Results
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters
or custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when a
CATIA file is imported. This file will be assigned a.xmt_txt file name
extension.
124
File>Import
File>Import 125
Importing Models and Results
126
File>Import
Import Geometry
The default, Import Geometry will import the geometry after the
Apply button is selected on the import form. The secondary toggle,
Import Preview will run the translator and provide a summary of
geometry and layer information without importing the geometry.
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Import Attributes
File>Import 127
Importing Models and Results
Example Scenario 1:
P1.CATPart with a Part ID of P1 containing two entities;
A feature named Loft.1 with a published name PUB_EDGE,
A feature named SURFACE_FEATURE.
128
File>Import
Example Scenario 2:
A CATProduct file with a product id of BLISKPROD contains a subproduct file with an instance name
of BLISKSUBPROD.1 and a CATPart file with an instance name of DAM3.1 that contains two
entities,
A feature named Blisk.1 with a published name BLISK_ONE,
A feature named Blisk.2 with a published name BLISK_TWO.
Layer numbers
File>Import 129
Importing Models and Results
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
CATIA file with _Ln appended. For example, if the CATIA file name
is test.CATPart and there are two layers 1,2, then the two groups will
be named: test_L1 and test_L2. See Create Groups from Layers, 117
for additional information.
Group Classification...
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters
or custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when a
CATIA file is imported. This file will be assigned a.xmt_txt file name
extension.
130
File>Import
In order to retrieve these attributes from the Patran database, there are two functions that may be used:
ps_get_body_string_attribute, 66 and ps_get_string_attribute (p. 67) in the PCL Reference Manual. For
examples of how these functions are utilized please see, ps_get_body_string_attribute, 17 and
ps_get_string_attribute (p. 18) in the PCL Reference Manual Examples.
File>Import 131
Importing Models and Results
132
File>Import
Once the CATIA V5 file is imported the tree is accessible as Patran heirarchical groups. For display
purposes, these groups can be turned on and off (posted and unposted).
File>Import 133
Importing Models and Results
134
File>Import
File>Import 135
Importing Models and Results
Solid Representation
Enable Geometry Tracking If ON, a geometry tracking log file will be created to describe
geometric attributes of imported geometry.
136
File>Import
Group Name
Select the type of imported geometric entities that will be added to the
group.
Entity Layers
All Layers
Layer numbers
Show Groups
Delete Groups
File>Import 137
Importing Models and Results
Group Name
Select the type of imported geometric entities that will be added to the
group.
Entity Layers
All Layers
Layer numbers
Show Groups
Delete Groups
138
File>Import
Group Name
Select the type of imported geometric entities that will be added to the
group.
Delete Groups
File>Import 139
Importing Models and Results
Import Preferences
In this dialog box you can specify your preferences on how to treat surfaces and solids, as well as
tolerances, when importing entities in the Patran database.
Solid Representation
Enable Geometry Tracking If ON, a geometry tracking log file will be created to describe
geometric attributes of imported geometry.
Import Action
Import Geometry
Calculate Model
Processes the file to help determine the best tolerance for geometry
import.
Tolerance
140
File>Import
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Pro/ENGINEER Options
Import to Parasolid
File Type
File>Import 141
Importing Models and Results
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
142
File>Import
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Group Classification...
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters
or custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when a
Pro/ENGINEER file is imported. This file will be assigned a .xmt_txt
file name extension.
File>Import 143
Importing Models and Results
144
File>Import
Import Preferences
Activates a dialog box in which you can specify how certain geometric
entities will be represented in the Patran database.
Entity Types
Identifies the classes of geometric entities from which you can select.
Material Import details:
Two values will be extracted from each part (if a material reference is
available):
Material name (a standard PTC part parameter) of type string
Material reference based on a user parameter named:
double)
poisson_ratio (a standard PTC material parameter of type double)
mass_density (a standard PTC material parameter of type double)
therm_exp_coef (a standard PTC material parameter of type
double)
therm_exp_ref_temp (a standard PTC material parameter of type
double)
therm_conductivity (a standard PTC material parameter of type
double)
File>Import 145
Importing Models and Results
146
File>Import
therm_exp_coef;
Reference Temperature (material word_id=1)=-
therm_exp_ref_temp;
Thermal Conductivity (material word_id=17) =-
therm_conductivity;
No modification or extension to the Patran database is required to
support this implementation.
Note: the Description will be created on-the-fly by the
sgm_ptc_access_v5 PCL function when the GEO file is read into
Patran.
The element property will be created with the following options:
Property Name = derived from Pro/E part name (similar to group
naming convention)
Material Name = material name associated with the Pro/E part
Application Region: Solid ID for corresponding Pro/E solid as
created in Patran
Element type and property option IDs are preference dependent.
File>Import 147
Importing Models and Results
Preference
Nastran
Marc
Abaqus
Ansys
Dytran
Patran Thermal
Element
71
71
71
71
12504
73
Type ID
25
25
25
25
Geometry Option ID
30
30
30
30
30
677
Condensation Option
ID
12540
Formulation Option
ID
Laminate Option ID
20
15
15
15
20
DOF
Preference
Patran 2 NF
LS-DYNA 3D
Pamcrash
SAMCEF
DEFAULT
Element
90
71
71
71
71
Type ID
25
25
25
25
Geometry Option ID
20
20
30
30
30
Condensation Option ID
11027
13402
Formulation Option ID
13451
Laminate Option ID
20
20
20
15
15
DOF
148
File>Import
Surface Types:
Lists the kinds of surfaces available for selection if the Entity Type you
picked is Solid or Surface.
These options are coupled with the File Type selection (in the Import
dialog box), to determine whether an intermediate file (.geo) will be
created and saved, and whether or not the Pro/ENGINEER database
will be loaded directly into the Patran database.
Save Geometry File (.geo)--create an intermediate (.geo) file
Load Database-- import data into Patran
Create Groups from Parts--if ON, a group will be created for:
each part in an assembly
each part that is not a component of an assembly
each .geo file created from an assembly--one group is created for
the part.
Surface Types
Lists the kinds of surfaces available for selection if the Entity Type
you picked is Solid or Surface.
These options are coupled with the File Type selection (in the Import
dialog box), to determine whether an intermediate file (.geo) will be
created and saved, and whether or not the Pro/ENGINEER database
will be loaded directly into the Patran database.
Save Geometry File (.geo)--create an intermediate (.geo) file
Load Database-- import data into Patran
Create Groups from Parts--if ON, a group will be created for:
each part in an assembly
each part that is not a component of an assembly
each .geo file created from an assembly--one group is created
File>Import 149
Importing Models and Results
The format of this file is used only by Patran ProENGINEER and it is not compatible with any other
Patran product or process.
Pro/ENGINEER File Types and Model Access Options
Pro/ENGINEER File
Type
Part
Model Access
Option
Load Database
Part
Part
Primitive Geometry
150
File>Import
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Brings up the Direct Mesh Options form that enables you to select the
type and topology of the mesh.
File>Import 151
Importing Models and Results
Mesh Type
Specifies the type of mesh that Direct Mesh creates; Tri, Tet, or Tri and
Tet.
Element Size
Element Topology
Mesh Offsets
152
File>Import
Unigraphics uses Parasolid to define geometry, however, Parasolid is also part of the geometric kernel of
Patran. Consequently, there is no need for translation when Unigraphics files are transmitted into Patran.
Note:
This is reflected in the File>Import menu that provides two different transfer methods for Unigraphics
files. The default import method is Direct Parasolid, where you select a Unigraphics part, Unigraphics
creates a Parasolid transmit file (with the extension .xmt_txt), and that file is imported. The second
method of import is Express Translation, where you select a Unigraphics part and an Express Neutral
file is created for import.
Current Group
Displays the current group into which the imported entities will be
placed. If a non-existent group name is entered, a new group with this
name will be created and made current.
File>Import 153
Importing Models and Results
Unigraphics Options
Import Format
154
File>Import
File>Import 155
Importing Models and Results
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Entity Layers
All Layers
Layer Numbers
Turn All Layers OFF and enter the layers on which the entities reside.
Group Classification...
Attribute Import
Displays the Attribute Import dialog box with options for importing
Unigraphics attributes.
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
Unigraphics file with _Ln appended. For example, if the Unigraphics
file name is test.prt and there are two layers 1,2, then the two groups
will be named: test_L1 and test_L2. See Create Groups from Layers,
117 for additional information.
Assembly Import
Verify Boundary
156
File>Import
If this toggle is ON, the parasolid transmit file will be saved when a
Unigraphics part file is imported. This file will be assigned a .xmt_txt
file name extension.
Attribute Import
The attribute import form is used to filter the attributes that will be imported into Patran.
Preview Attributes
You can inspect the entities and their attributes contained in a Unigraphics part targeted for import and
decide if any entities should be excluded from the import process.
Preview Components
You can inspect the component parts contained in a Unigraphics assembly targeted for import, in order
to selectively include parts in the import process.
File>Import 157
Importing Models and Results
Group Name
Select the type of imported geometric entities that will be added to the
group.
158
File>Import
Show Ug Groups...
Delete Ug Groups...
File>Import 159
Importing Models and Results
160
File>Import
Import Preferences
Activates a dialog box in which you can specify how certain geometric
entities will be represented in the Patran database.
Entity Types
Identifies the types of geometric entities from which you can select.
Entity Layers
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
Unigraphics file with _Ln appended. For example, if the Unigraphics
file name is test.prt and there are two layers 1,2, then the two groups
will be named: test_L1 and test_L2. See Create Groups from Layers,
117 for additional information.
File>Import 161
Importing Models and Results
Group Name
Select the type of imported geometric entities that will be added to the
group.
Delete Ug Groups...
162
File>Import
To import Unigraphics-NX geometry, select the Unigraphics-NX from the Source pull down list.
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Unigraphics-NX Options
File>Import 163
Importing Models and Results
Use the Import Options form to select the types and attributes of entities included in the imported
database.
164
File>Import
Import Geometry
The default, Import Geometry will import the geometry after the
Apply button is selected on the import form. The secondary toggle,
Import Preview will run the translator and provide a summary of
geometry and layer information without importing the geometry.
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Import Attributes
Entity Layers
All Layers
Layer numbers
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
Unigraphics-NX file with _Ln appended. For example, if the
Unigraphics-NX file name is test.model and there are two layers 1,2,
then the two groups will be named: test_L1 and test_L2. See Create
Groups from Layers, 117 for additional information.
Group Classification...
File>Import 165
Importing Models and Results
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters
or custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when a
Unigraphics-NX file is imported. This file will be assigned a.xmt_txt
file name extension.
166
File>Import
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
SolidWorks Options
File>Import 167
Importing Models and Results
168
File>Import
Import Geometry
The default, Import Geometry will import the geometry after the
Apply button is selected on the import form. The secondary toggle,
Import Preview will run the translator and provide a summary of
geometry and layer information without importing the geometry.
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Import Attributes
Entity Layers
All Layers
Layer numbers
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
SolidWorks file with _Ln appended. For example, if the SolidWorks
file name is test.model and there are two layers 1,2, then the two
groups will be named: test_L1 and test_L2. See Create Groups from
Layers, 117 for additional information.
Group Classification...
File>Import 169
Importing Models and Results
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters
or custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when a
SolidWorks file is imported. This file will be assigned a.xmt_txt file
name extension.
170
File>Import
File Name
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
Activates the Parasolid xmt Import Options form that enables you to
select the type and attributes of entities targeted for import.
File>Import 171
Importing Models and Results
172
File>Import
Import Geometry
The default, Import Geometry will import the geometry after the
Apply button is selected on the import form. The secondary toggle,
Import Preview will run the translator and provide a summary of
geometry and layer information without importing the geometry.
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Entity Layers
All Layers
Layer Numbers
Turn All Layers OFF and enter the layers on which the entities reside.
Group Classification...
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters
or custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
File>Import 173
Importing Models and Results
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added
to a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the
Parasolid file with _Ln appended. For example, if the Parasolid file
name is test.x_t and there are two layers 1,2, then the two groups will
be named: test_L1 and test_L2. See Create Groups from Layers, 117
for additional information.
Sew Sheet Bodies
Patran Sew
Verify Boundary
174
File>Import
CAD geometry is first exported in sat format. Next, Patran creates a Parasolid transmit (.xmt_txt)
file from that, finally the transmit file is imported through the Parasolid import function.
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
ACIS Options
Activates the ACIS Import Options form that enables you to select the
type and attributes of entities targeted for import.
See the current Patran Release Guide for currently supported version of the ACIS Geometric Modeler
and Parasolid. A summary of features and limitations follows.
File>Import 175
Importing Models and Results
Parasolid Entity
(PK entity types)
Remarks
body
PK_BODY_T
SHELL
PK_SHELL_T
FACE
PK_FACE_T
LOOP
PK_LOOP_T
COEDGE
PK_FIN_T
EDGE
PK_EDGE_T
VERTEX
PK_VERTEX_T
STRAIGHT
PK_LINE_t
ELLIPSE
PK_CIRCLE_t
If ellipse is circular
ELLIPSE
PK_ELLIPSE_t
PLANE
PK_PLANE_t
CONE
PK_CYL_t
If cone is cylindrical
CONE
PK_CONE_t
CONE
PK_BCURVE_t
If cone is elliptical
SPHERE
PK_SPHERE_t
TORUS
PK_TORUS_t
Spline Curves
exact_int_cur
PK_BCURVE_t
PK_BCURVE_t
exact_spl_sur
PK_BSURF_t
offset_spl_sur
PK_OFFSET_t
Offset surface
PK_BSURF_t
176
File>Import
File>Import 177
Importing Models and Results
Import Geometry
The default, Import Geometry will import the geometry after the Apply
button is selected on the import form. The secondary toggle, Import
Preview will run the translator and provide a summary of geometry and
layer information without importing the geometry.
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
All Layers
Group Classification
Model Units
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, meters, millimeters or
custom value units.
The default model units override value is the Patran geometry
preference value for "Geometry Scale Factor" which is 39.370079
(Inches).
If a different default value is desired when opening a new Patran
database, create a new template database by opening the default
template database delivered by Patran, change the Geometry Scale
Factor to the desired value, then save as the new template database.
Then when opening a new database to import geometry into from a
CAD System, it will use this value as the default model units for the
imported geometry.
178
File>Import
Create Groups from Layers Select the Create Groups from Layers button. A sub-menu appears.
If the Create Groups from Layers toggle is ON (Default), a Patran
Group is created for each Layer and all geometry on a layer is added to
a Patran Group. The group name(s) will be defined by the Group
Name Prefix provided by the user or if the user did not provide a
Group Name Prefix the group name(s) will be the prefix of the ACIS
file with _Ln appended. For example, if the ACIS file name is test.sat
and there are two layers 1,2, then the two groups will be named:
test_L1 and test_L2. See Create Groups from Layers, 117 for
additional information.
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when the
ACIS file is imported. This file will be assigned an .xmt_txt file name
extension.
File>Import 179
Importing Models and Results
Group Name
Group EntityLayers
Delete Groups
180
File>Import
structure information (STEP defined minimum subset) associated with the geometry imported
into Patran. Additionally, AP209 provides for analysis version control, which is fully associated
with design version control.
File>Import 181
Importing Models and Results
182
File>Import
In the Import dialog box, select STEP as the source of the imported database.
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
STEP Options
Import to Parasolid
File Type
Specifies the type of the imported input file. This may be a STEP 203
or 214 file or a STEP 209 file.
File>Import 183
Importing Models and Results
export. However, no user interface is provided to view this data and review its content or associativity to
the imported geometry entities. Prototypes of this functionality are being tested.
Important: STEP composite surface entity has no suitable entity in Patran, so it is not supported.
STEP currently does not support Patran Composite Trimmed Surfaces.
Not all AP203 and AP209 data model entities are supported. The following sections define the scope of
both AP data schemas coverage provided in this release.
Supported AP203 Import Entities
All AP203 Conformance Class representations (1-6) are supported.
Only the agreed upon minimum subset of Conformance Class 1 entities are supported.
Group-based geometry import is supported.
AP203 assembly is supported.
Assembly is imported in Patran and all the assembly instances are duplicated.
Group based Assembly import is supported.
184
File>Import
File>Import 185
Importing Models and Results
186
File>Import
File>Import 187
Importing Models and Results
188
File>Import
Currently, AP209 support is for the MSC Nastran Preference only. Specific coverage provided in this
release is listed below.
Entities
Features
Geometry
Configuration Control
Data
Support for import and export of nodes in the global coordinate system.
Elements
Materials
File>Import 189
Importing Models and Results
Entities
Regions
Features
Support for the element properties:
Surface Elements:
Membrane Stiffness, Bending Stiffness, Coupling Stiffness, Shear Stiffness
and Thickness.
Curve Elements:
Cross sectional area, Second Moment of Inertia, Torsional and Warping
Constant and Non-structural Mass.
Beam Cross Section Geometry and Beam Property Association.
Properties related only to MSC Nastran Preference are currently
supported.
Load Cases
Load Cases which have at least one of the supported LBCs are exported.
190
File>Import
Entities
Output Requests
Features
Support for Multiple Jobs.
Support for association of Analysis reports and Jobs.
Output Requests are supported only for MSC Nastran Jobs.
Results
Static analysis:
Results are supported for Elemental Stresses, Strains, and Nodal
Displacements.
Normal Modes Analysis:
Modes/Eigenvectors of normal modes and frequencies analysis results.
Support is available for only those Load Cases associated with a single
result Subcase.
Support for Analysis Report.
File>Import 191
Importing Models and Results
192
File>Import
Entity Types
Identifies the type of geometric entities from which you can select.
Geometry Preference
Solid Type
Specifies how solids will be represented in the database -- either as Brep or Parameterized Solids. The default is B-rep Solid. If you change
to Parameterized Solid, all 5 or 6 sided B-rep solids will be converted
into parameterized solids during import.
Group Classification...
Model Units
Select Options...
Verify Boundary
If this toggle is ON, the parasolid transmit file will be saved when a
STEP file is imported. This file will be assigned a .xmt_txt file name
extension.
File>Import 193
Importing Models and Results
Entity Types
Identifies the type of geometric entities from which you can select.
All Layers
Layer Numbers
Turns All Layers off. Enter the layers where the entities you want to
import reside.
194
File>Import
Group Classification...
Scale Factor
Brings up a dialog box in which you can override the model units
during import. The settings now include: inches, millimeters or custom
value units.
Load Database
File>Import 195
Importing Models and Results
Import Preferences
Activates a dialog box in which you can specify how certain geometric
entities will be represented in the Patran database.
Entity Types
Identifies the type of geometric entities from which you can select.
All Layers
196
File>Import
Layer Numbers
Turns All Layers off. Enter the layers where the entities you want to
import reside.
Group Classification...
Load Database
Imported Data
Use this pull-down list to select the types of data you wish to import.
File>Import 197
Importing Models and Results
Solid Representation
Enable Geometry Tracking If ON, a geometry tracking log file will be created to describe
geometric attributes of imported geometry.
198
File>Import
Import Action
Import Geometry
Calculate Model
Processes the file to help determine the best tolerance for geometry
import.
Tolerance
Group Name
Select the type of imported geometric entities that will be added to the
group.
File>Import 199
Importing Models and Results
Delete Groups...
Current Group
Displays the current group into which the imported entities will be
placed. If you enter a group name that does not yet exist, a new group
with this name will be created and made current.
STL Options
Brings up the STL Import Options form that enables you to specify the
types and attributes of entities targeted for import.
200
File>Import
Define Offsets...
File>Import 201
Importing Models and Results
Assigning Offsets
Same for all entity types:
click on Offset, type the offset in the Input Offset Value data, press Enter, or
pick Automatic Offset to let the system assign offset automatically.
202
File>Import
Importing Results
The File>Import command can also bring in results data created outside of the current database. If the
imported object is specified as Results, the Import dialog box buttons and text boxes are related to result
import choices. Imported result files may be in a variety of Patran formats.
Format
Current
Analysis Code
File>Import 203
Importing Models and Results
Zero Tolerance
Specify a tolerance value; a result with the absolute value less than this value will
be considered equal to zero.
This switch appears when importing element (.els) files. If neither of these are on,
the element result file is assumed to contain element centroid data. All results of a
particular element will be assigned to the centroid location. If Connectivity is ON,
Connectivity it is assumed that the element results file contains element nodal results (results at
each node for each element). The node ordering is assumed to be in the order of the
Ascending element connectivity and results assigned to the node locations accordingly. If
Node IDs Ascending Node IDs is ON, it is assumed that the element nodal results are in the
order of the node IDs in ascending order. The type of element is extracted, the actual
node connectivity determined and then the results are reordered in the order of the
element connectivty. The user must be aware of the type of data in the element
results files before turning this switch ON. Typical element result files nornally
only contain centroidal data. Element results files produced by MSC Nastran
fatigue analysis (.fef files) are .els files and the Ascending Node IDs switch should
be used.
Element node
results in order
of:
Element results files from an MSC Nastran fatigue analysis that correspond to the .fef file (which are .els
files) use the extension .tml and are automatically produced by the fatigue analysis if a .fef file is
produced so that you can select it as the template when importing via this mechanism.
204
File>Export
Exporting Files
File>Export
Exporting Files
With the File>Export command sequence you can transfer model data to use outside the current
database. Exported output may be in the form of Patran neutral files, or formatted as ACIS, Parasolid
xmt, IGES, and STEP files.
Exporting to a PATRAN 2.5 Neutral File
File Name/Type
Enter a new file name. The default file name extension is .out.
Format
The output file may be a PATRAN 2.5 neutral file, IGES format,
Parasolid xmt file, or STEP file.
Neutral Options
Activates the Neutral Export Options dialog box in which you select
exported entities and groups.
File>Export 205
Exporting Files
Activates the Neutral File Title form to enter a title for your file.
206
File>Export
Exporting Files
Entity Packets
Displays the names of all entity types that are candidates for export.
Select the packet(s) to send to the output file.
Existing Groups
Select the groups to transmit to the output file. Only those entities that
belong to a group will be exported, therefore this is a required
selection.
type 114 and 128 surfaces into Parametric BiCubic surfaces using the Edit,Surface,Refit
Geometry form to visualize the results. Then export a Patran 2 Neutral File by selecting
File>Export and setting the Format option to Neutral.
or
Turn ON the Exportable to Neutral File Geometry Preference and export a Patran 2 Neutral
File>Export 207
Exporting Files
File Name/Type
Enter a new file name. The default file name extension is .igs. For
multiple files, version numbers will be appended to the file name.
Format
IGES Options
Activates the IGES Export Options dialog box in which you define
the IGES file sections and select exported entities and groups.
Arc
Parametric Cubic
Composite Curve
Conic
Piecewise Linear
Point
Plane
Line
Line (110)
Parametric cubic
Line (110)
Parametric cubic
208
File>Export
Exporting Files
Cubic spline
Rational Bezier
MDC curve
CATIA curve
Parametric
Point
Point (116)
Ruled Surface
Cylinder
Cone
Torus
Surface of revolution
Tabulated cylinder
Bounded plane
Coordinate system
124
Type 1 - Rectangular
Form 10 - Cartesian
Type 2 - Cylindrical
Form 11 - Cylindrical
Type 3 - Spherical
Form 12 - Spherical
Nurb curve
Nurb surface
MDC surface
Fillet surface
CATIA surface
Extruded surface
Glide surface
File>Export 209
Exporting Files
Sphere
Parametric tricubic
Ordinary body
Solid of revolution
Solid 6face
Extruded solid
Glide solid
Extruded body
Tricubic net
Offset curve
Node
Node (134)
Finite Element
Offset surface
Trimmed surface
210
File>Export
Exporting Files
Start Section
Global Section
Entity Types
Displays the names of all entity types that are candidates for export.
Select the entities to send to the output file.
File>Export 211
Exporting Files
Entity Groups
Select the groups to transmit to the output file. Only those entities that
belong to a group will be exported, therefore this is a required
selection.
Specify what IGES point type will be created from Patran points.
Start Section
Global Section
Entity Types
Displays the names of all entity types that are candidates for export.
Select the entities to send to the output file.
Select Options...
212
File>Export
Exporting Files
File>Export 213
Exporting Files
File Type
File Name/Type
Enter a new file name. The default file name extension is .st.
Format
Select Options...
214
File>Export
Exporting Files
Currently, AP209 support is for the MSC Nastran Preference only. Specific coverage provided in this
release is listed below.
Entities
Features
Geometry
Configuration Control
Data
Support for import and export of nodes in the global coordinate system.
Elements
Materials
File>Export 215
Exporting Files
Entities
Regions
Features
Support for the element properties:
Surface Elements:
Membrane Stiffness, Bending Stiffness, Coupling Stiffness, Shear
Stiffness and Thickness.
Curve Elements:
Cross sectional area, Second Moment of Inertia, Torsional and Warping
Constant and Non-structural Mass.
Beam Cross Section Geometry and Beam Property Association.
Properties related only to MSC Nastran Preference are currently
supported.
Load Cases
Load Cases which have at least one of the supported LBCs are exported.
216
File>Export
Exporting Files
Entities
Output Requests
Features
Support for Multiple Jobs.
Support for association of Analysis reports and Jobs.
Output Requests are supported only for NASTRAN Jobs.
Results
Static analysis:
Results are supported for Elemental Stresses, Strains, and Nodal
Displacements.
Normal Modes Analysis:
Modes/Eigenvectors of normal modes and frequencies analysis results.
Support is available for only those Load Cases associated with a single
result Subcase.
Support for Analysis Report.
The following table shows attribute transfer from Parasolid to STEP AP214:
Parasolid Attribute
Remarks
SDL/TYSA_COLOUR
Color attribute
SDL/TYSA_NAME
Name attribute
File>Export 217
Exporting Files
Entity Types
Displays the names of all entity types that are candidates for export.
Select the packet(s) to send to the output file.
218
File>SimXpert
Session Files
File>SimXpert
SimXpert
Session Files
This menu item appears if you have a valid installation of SimXpert on your local
system and the environment variable MSC_SX_HOME is set pointing to the
installation directory of SimXpert. Selecting this option will launch SimXpert. If
you wish to export a current model to SimXpert, this can be done in the Analysis
application with the Action/Object/Method set to Analyze/Entire Model/Load
SimXpert in the MSC Nastran preference.
File>SimManager 219
Session Files
File>SimManager
Session Files
220
File>SimManager
Session Files
SimManager
Publishes and retrieves Patran databases and other related analysis files directly
from within Patran with the SimManager client. Once logged on, the user may
publish and retrieve as well test connection and access the Web Client. The server
settings need to be set in order for the SimManager client to communicate with the
server. The following variables need to be set:
SM_RICH_CLIENT_IC_HOST montecarlo
SM_RICH_CLIENT_IC_PORT 8000
SM_RICH_CLIENT_IC_PROTOCOL http
SM_RICH_CLIENT_IC_WEBCONTEXT SimManager
RC_ROOT
JDK_PATH
APPS
ACTION_LOC
JARS_PATH
CLASSPATH
SCA_SYSTEM
SCA_RESOURCE_DIR
SCA_SERVICE_CATALOG
SCA_JAVA_COMP_PATH
SCA_JVM_CONFIG
RC_LIBRARY_PATHFor more information on this, please see the Patran
Environment Variables (p. 46) in the Patran Installation and Operations Guide or
the SimManager documentation for more details. Client access to a SimManager
server via Patran is only supported on Windows machines.
File>Session 221
Session Files
File>Session
Session Files
A session file is a log of all database related commands and corresponding comments executed during a
work session. A single session file may contain commands that were used for more than one database.
The File>Session>Play command sequence executes a specified session file either in its entirety or one
command at a time for debugging or editing purposes.
File Name/Type
Select or type a file name. Session files are given a.ses.xx filename
extension, where xx is a number that shows where this session file is
in the sequential order of session files.
Single Step
Commit Commands
Stop
Stops playing the session file. After stopping, this button changes to
Resume. Press Resume to continue playing the session file.
222
File>Session
Session Files
File Name/Type
Record Rotations
Stop
Stops recording the session file. After stopping, this button changes to
Resume. Press Resume to continue recording the session file.
File>Print 223
Printing Patran Images
File>Print
The File>Print command sequence will send Patran images to a designated printer or to a specified print
file. Print setups and properties are unique to the operating system and to each printer, but several Patran
options exist that allow you certain control over the printed output.
224
File>Print
Printing on Windows
Print From
Print to File
File>Print 225
Printing Patran Images
Postscript Files
Although different Postscript printers can have different setups and defaults, the Postscript Driver
generally supports the options listed below. Defaults are shown in bold. If desired, defaults may be
overridden in the Printer Configuration File, p3_printers.def.
Option
Format
Background
Line Weight
Choices
Description
Black to White
White to Black
Color
White
Background is white.
Black
Background is black.
Actual
White
Black
Actual
Lines and Text are printed with the actual color. Color is
controlled by the Format option.
0.5 pts
226
File>Print
Option
Choices
Description
Text Scale
100%
Image Size
Fit on Page
As Is
Yes
No
Yes
No
Center
Draw Borders
File>Print 227
Printing Patran Images
Color EPS files will separate into the four process colors (CMYK) provided that the application can
produce separations. Non-color EPS files will separate onto the process black plate. There are no line
screen directives in the EPS file. Color EPS files placed in a document and sent to a non-color printer
will print in grayscale.
228
File>Print
Printing on UNIX
For running Patran in a UNIX environment, use the Print form to generate output of your Patran images.
Select the Viewport(s) and/or XY Window(s) to print. You can print multiple viewports
and windows on the same page or on separate pages. Invalid options are disabled
(e.g., Current XY Window is disabled if there are no XY Windows posted).
Print
Current Viewport
Available Printers
Postscript Default
PatranHard Default
CGM Default
HPGL Default
HPGL2 Default
Patran Hard to Postcript Default
Device
HP Laserjet 4Si
Driver
Postscript
Destination
lw11
Page Setup...
Options...
Apply
Cancel
More Help:
(Available Printers)
File>Print 229
Printing Patran Images
Page Setup
The Page Setup subform defines the paper size, margins, print orientation and number of copies to print.
The defaults on the form are a function of the Current Printer. This form reverts to the printers default
settings every time the printer is selected from the listbox on the Print form.
Print Control
Paper Size
Letter
Margins
Left
0.5
Right
0.5
Top
0.5
Bottom
0.5
Default Units
Inches
Print Orientation
Number of Copies
OK
Cancel
The OK button saves the choices. The Cancel
button resets the choices to those which existed
before the form was opened. Pressing the Apply
button in the main form causes an OK in this
form (if it is open).
Postscript Options
The Options subform defines Driver specific options. Shown below is a typical setting for a PostScript
laser printer. The options and defaults are unique to the current printer. They are defined in the Printer
Configuration File, 242. The form reverts to the printers default settings every time the printer is selected
230
File>Print
Print Control
Format
Black to White
Background
White
Black
Line Weight
0.25 pts
Text Scale
250%
Image Size
Fit on Page
Draw Borders
Yes
Print to File
uu
OK
Preview
Quality
Cancel
More Help:
Fit on Page scales the image so that it fits on the
Paper Size defined on the Page Setup form (less
margins). Or the image can be left unscaled (same as
the size on the screen) with the As Is option.
(Available Printers)
PatranHard File Options, 233
CGM Options, 234
HP-GL Options, 237
HP-GL/2 Options, 240
File>Print 231
Printing Patran Images
The Postscript Driver supports the following options. The default choice is shown in bold. Note that this
default can be overridden in the Printer Configuration File, 242.
Option
Format
Background
Line Weight
Choices
Description
Black to White
White to Black
Color
White
Background is white.
Black
Background is black.
Actual
White
Black
Actual
0.5 pts
Text Scale
100%
Image Size
Fit on Page
As Is
232
File>Print
Option
Center
Draw Borders
Choices
Description
Yes
No
Yes
No
File>Print 233
Printing Patran Images
Print Control
Color
Format
Background
White
Actual
Text Scale
250%
Image Size
Fit on Page
Draw Borders
Yes
Resolution(dpi)
Create new .hrd file
uu
OK
72
patran.hrd
Cancel
234
File>Print
CGM Options
Determines if the image is printed in color or black and white. In the latter case, the
spectrum colors can be optionally converted to a black to white or white to black
range.
Print Control
Format
Black to White
Background
White
Black
Text Scale
100 %
Image Size
Fit on Page
Draw Borders
Yes
Resolution(dpi)
72
Print to File
More Help:
OK
Cancel
(Available Printers)
Postscript Options, 229
PatranHard File Options, 233
File>Print 235
Printing Patran Images
Option
Format
Choices
Description
Black to White
White to Black
Color
White
Background is white.
Black
Background is black.
Actual
White
Black
Actual
Text Scale
100%
Image Size
Fit on Page
As Is
1.0
Background
Scale Factor
236
File>Print
Option
Center
Draw Borders
Resolution
Choices
Description
Yes
No
Yes
No
72
File>Print 237
Printing Patran Images
HP-GL Options
Determines if the image is printed in color or black and white. In the latter case, the
spectrum colors can be optionally converted to a black to white or white to black
range.
Print Control
Format
Black to White
Background
White
Black
Text Scale
100%
Image Size
Fit on Page
Draw Borders
Yes
Resolution(dpi)
72
Pen Mapping
Model No. & Version
7550A
Print to File
OK
Cancel
+ More Help:
(Available Printers)
Postscript Options, 229
PatranHard File Options, 233
CGM Options, 234
HP-GL/2 Options, 240
238
File>Print
Option
Format
Choices
Description
Black to White
White to Black
Color
White
Background is white.
Black
Background is black.
Actual
White
Black
Actual
Text Scale
100%
Image Size
Fit on Page
As Is
1.0
Background
Scale Factor
File>Print 239
Printing Patran Images
Option
Center
Draw Borders
Resolution
Pen Mapping
Choices
Description
Yes
No
Yes
No
72
240
File>Print
HP-GL/2 Options
Determines if the image is printed in color or black and white. In the latter
case, the spectrum colors can be optionally converted to a black to white or
white to black range.
Print Control
Format
Black to White
Background
White
Black
Text Scale
100%
Image Size
Fit on Page
Draw Borders
Yes
Resolution (dpi)
Output Format
7 Bit
LaserJet III
No
Opaque Mode
No
Cutter
Default
Print to File
OK
72
Pen Mapping
Rotation(deg)
Cancel
File>Print 241
Printing Patran Images
Option
Format
Choices
Description
Black to White
White to Black
Color
White
Background is white.
Black
Background is black.
Actual
White
Black
Actual
Text Scale
100%
Image Size
Fit on Page
As Is
Scale Factor
1.0
Center
Yes
No
Background
242
File>Print
Option
Draw Borders
Resolution
Choices
Yes
No
72
Pen Mapping
Output Format
Laserjet III
Opaque Mode
Cutter
Rotation
Description
8 bit
Yes
No
Yes
No
Default
Yes
No
File>Print 243
Printing Patran Images
The printer is named Engineering. It appears with this name in the Available Printers listbox in the Print
form. The Destination is lw9. The only Paper Size assigned is Letter. The default margins are 0.5 inch.
The output will be generated in a Black to White Format with a White Background. Lines & Text will
be Black. Note that these last three options will not appear on the form. The default Line Weight is 0.5 pts
and the default Text Scale is 100%. Two Image Size options (Fit on Page and As Is) will be available.
Borders will always be drawn. The remaining options will be assigned the system default values.
Rules for defining a printer are as follows:
1. Each Printer must have a unique name (duplicate printers are ignored). This option must be first.
The remaining options can be defined in any order.
2. Each printer must be assigned a valid Driver. Printers with invalid drivers are ignored.
3. The syntax to use is Option = ( Choice 1, Choice 2; Default ). Options are to be separated by
commas. Undefined options are ignored.
4. Choices must be contained within parentheses and be separated by commas. An optional default
can be declared at the end separated from the choices by a semicolon. Undefined choices are
ignored.
5. If the first choice is No Show, then this option will not appear on the form. Its value can be
preset with a default; otherwise, the system default will be used. This feature only applies to
Driver Specific options. The Printer Definition and Page Setup options are always displayed. If
all Driver Specific options are hidden, then the Options button on the main form will be disabled
(for the subject printer only).
6. The @ sign continues the printer definition on the next line.
7. Options not assigned will be given the system default.
The following table lists each option and its possible choices. The first section refers to the Printer
Definition options and the second to the Page Setup options. These are used by all drivers. Following this
244
File>Print
are Driver Specific options. System defaults for unspecified choices are shown in bold. Those options
that accommodate multiple choices (Option menu instead of a Databox) are also shown in bold.
Section 1
Printer Definition
Option
Choices
Printer
Device
Device description
Driver
CGM
HPGL
HPGL2
PatranHard File
Postscript
Destination
File>Print 245
Printing Patran Images
Section 1
Page Setup
Option
Page Size
Choices
Letter ( 8.5 x 11.0 )
Legal ( 8.5 x 14.0)
Tabloid ( 11.0 x 17.0 )
A ( 8.5 x 11.0 )
B ( 11.0 x 17.0 )
C ( 15.82 x 19.87 )
D ( 20.82 x 31.87 )
E ( 32.82 x 41.87 )
A0 ( 31.89 x 44.65 )
A1 ( 22.20 x 30.94 )
A2 ( 15,35 x 21.25 )
A3 ( 11.6929 x 16.5354 )
A4 ( 8.2677 x 11.6929 )
Roll 11 inch
Roll 24 inch
Roll 36 inch
Roll 44 inch
Left Margin
0.5 inch
Right Margin
0.5 inch
Top Margin
0.5 inch
Bottom Margin
0.5 inch
Orientation
Portrait
Landscape
Portraitflipped
Landscapeflipped
Number of Copies
246
File>Print
Section 1
Postscript Driver
Option
Format
Choices
Black to White
White to Black
Grayscale
Color
Background
White
Black
Actual
White
Black
Actual
Line Weight
0.5 pts
Text Scale
100%
Image Size
Fit on Page
As Is
Use Scale Factor
Scale Factor
1.0
Center
Yes
No
Draw Borders
Yes
No
Quality
Low
Normal
High
Color Model
RGB
CMYK
GCR
75%
File>Images 247
Create Graphic Images
File>Images
Images are graphic outputs of Patran models generated in a number of popular graphics file formats that
can be accessed on various computer platforms. Image files utilize specific compression techniques.
Outputs may be static images, animations, or 3D virtual models. The supported standard Internet
graphics formats are BMP, JPEG, MPEG, PNG, TIFF and VRML.
The playback of generated images is highly dependent on the hardware and software used for viewing.
Limitations, such as window size, color maps, file size, and the number of animation frames can affect
the quality of the display.
When you select File>Images, the Output dialog box allows you to pick the output format type.
248
File>Images
File Select
Filename
Default name is the current database name with the .bmp extension.
Optionally, you can supply a new file name complete with the
extension.
Overwrite
If you selected an existing bitmap file name, the new image will
overwrite the image that is currently in the file.
Increment
If you selected an existing bitmap file name, the new image will be
added to the image that is currently in the file.
Apply
File>Images 249
Create Graphic Images
However, with the Quality slide bar in the dialog box, you do have some control over the image
compression. If you set Quality to a higher value, the image file will be larger but the final appearance
of the image will be closer to the original.
File Select
Filename
Default name is the current database name with the .jpg extension.
You can enter a new name but keep the .jpg extension.
Overwrite
If you selected an existing file name, the new image will overwrite the
image that is currently in the file.
Increment
If you selected an existing file name, the new image will be added to
the image that is currently in the file.
Quality
Sets the relative quality of the image output. A value of 1.0 is the
highest quality (least compressed, largest file), and a value of 0
produces the lowest quality (most compressed, smallest file) output.
Apply
250
File>Images
record complex animation sequences, for example animate model translations and rotations, or analysis
results.
File Select
Filename
Default name is the current database name with the .mpg extension.
Optionally, you can supply a new file name complete with the
extension.
Overwrite
If you selected an existing file name, the new image will overwrite the
image that is currently in the file.
Increment
If you selected an existing file name, the new image will be added to
the image that is currently in the file.
Max. Frames
Apply
File>Images 251
Create Graphic Images
File Select
Filename
Default name is the current database name with the .png extension.
Optionally, you can supply a new file name complete with the
extension.
Overwrite
If you selected an existing file name, the new image will overwrite the
image that is currently in the file.
Increment
If you selected an existing file name, the new image will be added to
the image that is currently in the file.
Apply
252
File>Images
File Select
Filename
Default name is the current database name with the .tif extension.
Optionally, you can supply a new file name complete with the
extension.
Overwrite
If you selected an existing file name, the new image will overwrite the
image that is currently in the file.
Increment
If you selected an existing file name, the new image will be added to
the image that is currently in the file.
Apply
File>Images 253
Create Graphic Images
distributed using the World Wide Web and explored interactively by remote users. The current
specification, VRML 2.0, supports JAVA, sound, animation, and Javascript.
File Select
Filename
Default name is the current database name with the .wrl extension.
Optionally, you can supply a new file name complete with the
extension.
Overwrite
If you selected an existing file name, the new image will overwrite the
image that is currently in the file.
Increment
If you selected an existing file name, the new image will be added to
the image that is currently in the file.
Apply
254
File>Report
File>Report
The File>Report command enables you to write and print a report file that contains a summary of a
model, its node and element attributes, properties and results. You can control the format of the report
with options you select in the Report File Preferences form, and read the completed report file using any
word processor program (e.g. Notepad).
Open FIle
File Name
Enter a new file name (keep the .rpt extension), or select an existing
name if Append was selected.
Output Format
Activates the Report Format Preference dialog box in which you can
provide format specifications.
File>Report 255
Creating Report Files
The name of the report file is automatically entered from the File
Name input field.
Report Contents
application (Info will be Location, Distance or Attributes, respectively). The report will contain
all information you request, regardless of which object you pick.
Press the Write Report toggle--this will activate the Report File dialog box.
For creating a new report, enter a name in the File Name data box, complete with the .rpt
extension. To append information to an existing report, select its name in the folder/file field.
Click Apply in the left side of the dialog box and the right side entries will become available for
selection.
Modify the output format, if desired, then pick the type of data options you want to include in the
report.
Click Apply in the right side of the dialog box. The report will be generated.
To read the report, right click on its name in the file field and open it with a word processor
program.
256
File>Report
Real Numbers
Field Width/Number of
Decimals
Select the appropriate number with slide bar. The width of the field
must accommodate the total number of digits and the decimal point
contained in each field of the tabular report.
Integers
Spacing
File>Report 257
Creating Report Files
258
File>Report
260
270
300
260
5.1
Group Names
Groups, as well as several other database objects (e.g. viewports), are assigned names to differentiate
them from one another. In naming groups, you must conform to the following set of rules:
Uniqueness--each name must be unique.
Number of characters--name may not contain more than 31 characters.
Legal characters--the following characters are acceptable in names:
a through z
A through Z
0 through 9
-, _ , and .
Case sensitivity--upper and lower case letters are differentiated. For example, group_1 and
asm.wheel.left
Prefix
(geometry type)
Stem
(generic name)
Suffix
(modifier to generic name)
(modifiers to generic name)
(geom.type)
tip-top)
Group Membership
A group may consist of any combination of geometric and finite element entities. Other design features,
such as coordinate frames, materials, element properties, loads and boundary conditions, fields, and
analysis results cannot be categorized as group members even though they are associated with group
members.
Group Status
The status of a group may be:
current or not current
posted or unposted
target group
Current Group
The current group is the active and visible group that receives all newly created entities. Any group may
be selected as current, however only one group may be current at any given time. The name of the current
group is displayed as part of the Viewport Banner.
Each viewport has its own current group but the only active current group is that of the current viewport
(see also Current Viewport, 317).
Posted Group
Posted groups are the groups that are visible in a viewport. A current group is automatically posted, but
any number of additional groups may also be posted to the same viewport. A group may be posted to
more than one viewport.
Posting gives you the power of selectively displaying entities, since only those entities that are contained
in posted groups are visible in a viewport.
You can unpost any posted group but do not unpost the current group, or else you will not be able to see
the geometric and finite element entities as they are created.
Target Group
A group selected for action in certain commands (e.g., Group Translate).
Group Attributes
For each group you may specify a unique color and rendering style (e.g., smooth shaded), and display
entity labels. Although attributes can be assigned to groups in the Group Menu, for attribute definitions
you must look in the Display Menu (see The Display Menu, 385).
262
Important:
Group Transformations
Transformations are rigid body movements that treat a group as a single unit. These operations can
translate, rotate, mirror, scale, pivot, or reorient a large number of entities at the same time.
Implicit in a transformation process is the copy action. By default, in a transformation process the original
(target) group is copied and the resulting copy is transformed leaving the target group in its initial
position. As a result, a number of new entities are created while the originals are retained, unless you
specifically request that the original entities be deleted.
The operations of translation, rotation, and scaling allow you to iterate the transformation process by
entering a repeat count (n). In all of these actions, if the repeat count is greater than 1, the copies of the
target group are placed in the current group (new entities are always placed in the current group!).
However, you may choose the current group to be the same as the target group.
In these transformations you can either save the original group members or delete them, optionally
reusing the entity IDs of the deleted entities for the new members. Similarly, you may retain the original
target group or delete it, except when the target group and the current group are the same, in which case
the delete option is not selectable.
Translation
Translation is a linear transformation along an XYZ translation vector. The formula for translation is:
P n = P n 1 + T xyz
where:
Pn
Pn 1
T xyz
= the location of a point ( P 0 ) in the current group after the nth iteration.
= the location of the same point before the nth iteration.
= the translation vector.
Rotation
Rotation is an angular transformation around an axis. The formula for rotation is:
Pn = Pn 1 + ( o + r )
264
where:
Pn
Pn 1
= the location of a point ( P 0 ) in the current group after the nth iteration.
= the location of the same point before the nth iteration.
= an optional offset angle. The offset is valid only for the first rotation, for the second
iteration and beyond, o = 0 .
P1
r
Repeat Count = 2
Axis
P0
Radius
The plane of rotation is established by the Axis and the Radius. The axis is a vector that is normal to, and
intersects, the plane of rotation. The radius of rotation, a straight line in the plane of rotation, extends
from the location of point P0 to the point where the axis intersects the plane. See Rotating Points, Curves,
Surfaces, Solids, Planes and Vectors (p. 703) in the Geometry Modeling - Reference Manual Part 2 for
further information on entity rotation.
Scaling
This transformation proportionately scales the target group relative to a scaling origin ( S 0 ). The formula
for scaling is:
P n = P n 1 S xyz
where:
Pn
Pn 1
S xyz
= the location of a point ( P 0 ) in the current group, relative to the scaling origin,
after the nth iteration.
= the location of the same point before the nth iteration.
= the scaling factors in the X, Y, and Z directions.
Mirroring
Mirror transformation is a 180-degree rigid-body rotation of a group around a mirror plane. The formula
for mirroring is:
Pm = Pb
where:
Pm
= the distance, before transformation, of any point ( P 0 ) from the final mirror
plane, measured along an axis, normal to the final mirror plane.
Pb
= the distance, after transformation, of the same point from the final mirror
plane, measured along an axis, normal to the final mirror plane.
P
Pm
Radius = Pb
X
Offset
Modifying Orientation
This transformation moves a group from its original coordinate frame to a new coordinate frame. The
local position of the group with respect to the new coordinate frame will be the same as its local position
266
with respect to the original coordinate frame. This method provides a simple way to re-orient a group of
entities with respect to existing geometry.
Y
Y
Z
X
X
Z
(1)
(2)
Coordinate Frame 0
Coordinate Frame 2
Pivoting
This transformation performs the rigid-body rotation of a group through a plane defined by a pivot point
( P p ), a starting point ( P s ), and an ending point ( P e ).
The angle of rotation, , is the angle between the
the pivot point, P p .
In the diagram below, any point P a in a group is rotated around point P p through angle to produce the
corresponding point, P b in the pivoted group.
Ps
Pa
Radius
Pp
Pe
Pb
Repositioning
Modifying the position of a group involves simultaneous rigid-body translation and rotation. The
transformation is defined by mapping a set of three points in an original position to a set of three points
in a destination position. The transformation cannot be performed if either set of points lies in a straight
line.
Each three-point set defines a temporary coordinate frame. The positional and angular differences
between the two frames establish a translation vector and planar rotation angles, respectively. These are
then applied to all geometry.
P1d
P1o
Vt
P2d
P2o
P3d
P3o
P1d
P2d
P1o
(1)
P3d
P1d
P2o
P2d
P2o
P3d
P3o
P1o
P3o
(2a)
(2b)
P1d
P1o
P2d
P2o
P3o
P3d
(2c)
268
Vector
the group. Assigns LBCs to the newly transformed entities. New coordinate systems are created
and referenced by the new LBC sets.
Copy--copies, but does not transform, loads and boundary conditions and assigns them to the
Caution:
Loads that are normal to surface geometry and to 2D elements are not reversed when
mirror transformation is used, unless you pick the option to do so. These loads
maintain their directionality with respect to the entitys normal.
Properties
Along with the entities of a group, you may also transform properties assigned to the original group
members with one of the following options:
Transform--applies the same transformation to properties as the transformation applied to the
group and assigns them to the newly transformed entities. Material orientations, however, are
not transformed.
The Transform option is the only one that creates new property sets.
Copy--does not transform properties but adds the same property set to the newly transformed
entities. Therefore, when element properties with directionality, such as material orientation,
beam orientation, and beam offset are copied, their definition may not be correct for the new
entities.
Set Names
For each existing LBC set or Property Set referenced by entities in the current group, and for each repeat
count, a new LBC set or Property Set may be created with transformed entities. The names of the new
property sets are derived from the original set name; an extension is appended to the original name in the
form of .N, where "N" is an integer. The value of N is determined by searching all existing property sets
for the highest ".N" extension, and then incrementing it by 1.
Fields referenced by transformed LBC sets or property sets are not modified or extended. For LBC fields,
you must manually extend the field, for all other field types, you must ensure that the field applies in the
space of the newly transformed entities.
270
5.2
Menu Conventions
A menu item with ellipses (...) attached to it calls up a dialog box in which you enter further data.
Group
Create...
Post...
Modify...
Move/Copy...
Set Current...
Transform...
Delete...
Attributes...
The Group pulldown menu keywords lead to dialog boxes that initiate all group-related actions. Menu
functionalities are described below in the order in which they appear.
Create...
Post...
Modify...
Move/Copy...
Set Current...
Transform...
Delete...
Deletes a group, except the current group, and optionally deletes its
associated members from the database.
Attributes
Group>Create 271
Creating a New Group
Group>Create
The Group>Create command sequence displays the dialog box below. Assign a unique group name,
observing group naming conventions, then select entities designated for membership in the group.
272
Group>Create
Additional options include making the new group current, as well as unposting all other groups currently
posted.
Group>Create 273
Creating a New Group
Filter
Enter a unique new group name; (see Group Names, 260 for more
help).
Make Current
The new group is posted and any other posted groups are unposted.
Group Contents
Entity Selection
Displays the IDs of the entities as you select them for inclusion.
To select several entities, hold down the Shift key while picking the
next item.
Changing Actions
To change from one Group command to another, you may return to the Group menu and pick another
keyword, or alternately, click on the Action button in the current dialog box to display all action options,
then select the desired action. As the new action dialog box is opened, the previous one will be closed.
274
Group>Post
Group>Post
Group>Post 275
Posting and Unposting Groups
The Group>Post dialog box allows you to post or unpost one or more selected groups. Posted groups
are the groups that are visible in a viewport. A current group is automatically posted, but one or more
additional groups may also be posted to the same viewport. A group may be posted (visible) in more than
one viewport.
Current Viewport
Displays the names of all groups in the database. To post a group, click
on its name to highlight it; to unpost, click on a highlighted name to
unhighlight it.
To select several groups listed consecutively, hold the Shift key while
clicking the last item. To select several groups not listed consecutively,
hold the Ctrl key while clicking on each additional member.
276
Group>Modify
Modifying Groups
Group>Modify
Modifying Groups
With the Group>Modify command and dialog box you can modify the following group definitions:
Make a selected (target) group current.
Rename a selected group.
Add entities to a group.
Group>Modify 277
Modifying Groups
Displays a dialog box in which you can select a different target group.
Make Current
Rename
Enables you to enter a new name for the target group in a subordinate
dialog box.
278
Group>Modify
Modifying Groups
Selectable Members
When this toggle is not turned to ON, the entities that belong to the
group cannot be picked even though the group is displayed (default is
ON (4)).
Member List
Member List to
Add/Remove
Add
Press this button to complete the process of adding the selected entities
to the target group.
Remove
model database.
Group>Create>Add All Entities creates a new group that will contain all entities, including
entities to an existing group. Or, to add only certain orphan entities, enter their name and ID
number into the Member List to Add/Remove databox.
Group>Modify 279
Modifying Groups
280
Group>Modify
Modifying Groups
Renaming a Group
If you pressed the Rename... button in the Group Modify dialog box, you will see the subordinate dialog
box shown below.
Existing Names
Displays the names of existing groups. If you select a filter only those
groups that pass the filter criteria will be listed.
Rename As
Enter the new name that you want to give to the target group.
Group>Move/Copy 281
Moving and Copying Group Members
Group>Move/Copy
The Group>Move/Copy command and dialog box allows you to move or copy entities between groups.
From Group
To Group
Pick the destination group to where the entities are moved or copied.
Move
Removes selected entities from the source group and places them into
the destination group.
Copy
Copies selected entities from the source group into the destination
group.
Select Entities...
282
Group>Move/Copy
Select Entities
Geom. On
Geom. Off
Press Geom. Off to cancel the all selection. Note that an entity type
is selectable only if its toggle box is ON (4).
FEM On
FEM Off
From
From textboxes
Copy/Move
Displays the IDs of the entities selected for the copy or move
operation (the heading of Copy" or "Move" is based on the switch
you turned on in the parent form).
To pick entities:
toggle the entity type ON
select entities directly from the screen,
or
copy and paste entity names from the From Group textboxes to the
Move/Copy databoxes.
Group>Move/Copy 283
Moving and Copying Group Members
To
To textboxes
284
Group>Set Current
Making a Group Current
Group>Set Current
With the Group>Set Current command you can specify any group as the current group in the current
viewport.
Current Viewport
Displays the name of the current viewport (see Current Viewport, 317).
Group>Transform 285
Transforming Groups
Group>Transform
Transforming Groups
The Group>Transform dialog box directs you to various actions that allow you to translate, rotate,
mirror, scale, pivot, reposition, and modify the coordinate frame definition of groups.
Although some of the commands are specific to the transform action you select, certain dialog box entries
are common to all transformations.
Current Group
Displays the name of the active and visible current group. All new
entities are automatically associated with this group.
Target Group
Identifies the group targeted for the transformation action. The default
target group is the current group, however, you may designate any
another group as the target group.
Calls up a dialog box in which you can select a target group different
from the current group.
Loads/BCs
Properties
Translating Groups
286
Group>Transform
Translating Groups
The Group>Transform>Translate command sequence moves and copies a group linearly along an
XYZ translation vector.
Group>Transform 287
Translating Groups
Reference Coordinate
Frame
Translation Vector
When you click in this field, the Vector select icons will appear (see
Select Menu, 35). You may type in the X, Y, Z, components of a vector
or select a vector type from the selection menu then pick a vector of the
selected type in a viewport. Vector direction is reversed if Reverse
Direction is selected. Vector magnitude is calculated automatifically if
Auto Update Magnitude is selected (the default). If Vector Magnitude
is 0 or blank, magnitude is calculated from Direction Vector.
Repeat Count
288
Group>Transform
Translating Groups
Rotating Groups
The Group>Transform>Rotate command sequence performs angular transformations around an axis.
Group>Transform 289
Translating Groups
Reference Coordinate
Frame
Axis
When you click in this field, the Axis select icons will appear in the
Toolbar (see Select Menu, 35). Select the axis type (e.g., 2Point Axis),
then specify an axis of the selected type (e.g., select two points).
Rotation Parameters
Rotation Angle
Offset Angle
Repeat Count
290
Group>Transform
Translating Groups
Scaling Groups
The Group>Transform>Scale command sequence proportionately scales the target group relative to a
scaling origin ( S o ).
Group>Transform 291
Translating Groups
Reference Coordinate
Frame
Scale Origin
Specifies the coordinate location of the scaling origin. When you click
in this field, the Point select icons will appear in the Toolbar (see
Select Menu, 35). Enter a point location (global Cartesian coordinates,
Point ID, Vertex ID, or Node ID) or select a point type from the Select
Menu (e.g., Curve Intersect) then pick or construct a point of the
selected type in a viewport.
Scale Parameters
Coord. Frame Scale
Factors
Repeat Count
292
Group>Transform
Translating Groups
Mirroring Groups
The Group>Transform>Mirror command sequence performs a 180-degree rigid-body rotation of a
group around a mirror plane.
Group>Transform 293
Translating Groups
Specifies the plane that serves as the mirroring plane. When you click
in this field, the Plane select icons will appear in the Toolbar (see
Select Menu, 35). Enter the endpoint coordinates of the axis normal to
the mirror plane or select a plane type from the Select Menu (e.g.,
3Point Plane) then pick a plane of the selected type in a viewport (e.g.,
select three points).
Offset
Specifies the offset of the final mirror plane from the one previously
defined. The offset is a specified distance (positive or negative) along
an axis, normal to the selected mirror plane.
294
Group>Transform
Translating Groups
position of the group with respect to a new coordinate frame will be the same as its local position with
respect to the original coordinate frame. Thus the orientation of the group will change.
To Coordinate Frame
Group>Transform 295
Translating Groups
Pivoting Groups
The Group>Transform>Pivot command sequence performs rigid-body rotation of a group through a
plane defined by a pivot point ( P p ), a starting point ( P s ), and an ending point ( P e ).
Pivot Point
Center of rotation.
Starting Point
End Point
When you click in one of these fields, the Point select icons will appear in the Toolbar (see Select Menu,
35). Enter a point location (global Cartesian coordinates, Point ID, Vertex ID, or Node ID) or select a
point type from the Select Menu then pick or construct a point of the selected type in a viewport.
296
Group>Transform
Translating Groups
Repositioning Groups
The Group>Transform>Position command sequence performs simultaneous rigid-body translation
and rotation of a group. The transformation is defined by mapping a set of three points in an original
position to a set of three points in a destination position.
Original Position
Destination Position
When you click in one of these fields, the Point select icons will appear in the Toolbar (see Select Menu,
35). Enter a point location (global Cartesian coordinates, Point ID, Vertex ID, or Node ID) or select a
point type from the Select Menu then pick or construct a point of the selected type in a viewport.
Group>Delete 297
Deleting Groups
Group>Delete
Deleting Groups
Current Group
Filter
Enter one or more letters of the name then a wildcard (*). Press Filter
to list only the item(s) that pass the filter criteria.
298
Group>Delete
Deleting Groups
Highlight the group(s) you want to delete. The current group is never
listed here since it cannot be deleted.
note: If one of the groups listed here is the current group in any other
viewport, it still cannot be deleted until it is no longer a current group
in any viewport.
Delete Associated Members The members of the group you want to delete will be deleted from the
model even if those entities belong to other groups.
Group>Attributes 299
Assigning Attributes to Groups
Group>Attributes
With the Group>Attributes command you can assign named attributes to one or several groups (for
more information on named attributes, see Named Attributes, 383). The advantage of using this command
is that it allows you to assign display attributes to any number of groups.
300
Group>Attributes
5.3
Group>Attributes 301
Hierarchical Groups (Hgroups)
Unless a hierarchial group structure is created, the group structure is flat. All groups exist at the same
level:
Normal Group Structure
Group 1
Group 2
element_1
...
element_n
element_1
...
element_n
Group 3
element_1
...
element_n
Group 4
Group 5
element_1
...
element_n
element_1
...
element_n
Complex and large FEM data models are diffcult to handle in a flat structure.
Note:
By using the right mouse button (RMB) on a selected tree widget entity, a contextual menu
appears giving access to easily change Actions.
Organizing the data hierarchically establishes associations between groups that support performing
operations on more than one group at a time.
Subgroup
Group_2
H-Group C
Subgroup
Group_3
H-Group D
Group_4
H-Group E
Group_5
Subgroup
302
Group>Attributes
Establishing hierarchical groups, subgroups and element parent/child relationships provide a general tool
for subdividing large models. It allows the same operations to be performed on collections of groups, and
groups and their subgroups.
Each hierarchical group can contain only one Patran group.
Hierarchy groups contain pointers to real groups. By selecting parent groups for operations, the
operations can be performed on the elements in the group and subgroups, as well.
You can perform the following actions:
Create Hgroups. See Creating an Hgroup, 303.
Post Hgroups. See Posting an Hgroup, 309.
Modify Hgroups. See Modifying Group Hierarchies, 309.
Delete Hgroups. See Deleting Hgroups, 311.
Set Current an Hgroup as the current group. The current group is posted to the current viewport.
See Changing the Current Hgroup, 312.
Export or Import an entire group hierarchy. See Exporting and Importing Hgroup Trees, 312.
At any time, you can view the existing Hgroups and group hierarchy.
Group>Attributes 303
Hierarchical Groups (Hgroups)
Creating an Hgroup
Select the action Create on the Group Hierarchy form to display the Create Group form.
You use this form to create an association between a standard group and an Hgroup that will contain the
standard group. Assigning the Selection Group name identifies the standard group that is to be
associated with the Hgroup. You can either select a group from the list of groups displayed on the form
or you can enter the name of a standard group. The name you specify can identify an existing standard
group or it can be the name of a standard group that has yet to be created.
You can associate the same standard group with more than one Hgroup, but each Hgroup can be
associated with only one standard group.
As an example, assume the following very simple example where you want to create two Hgroups called
fem and geom. The fem Hgroup will be associated to a group containing all the finite elements of the
model and the geom Hgroup will be associated to a group containing all the geometry. In addition to that,
the fem and geom Hgroups will contain multiple sub Hgroups associated with groups containing only
portions of the fem or geom Hgroup entities, respectively.
304
Group>Attributes
selected, identify or enter the group and Hgroup names. (Do not click Apply at this point.) Type
in all_fem for the group name and fem for the Hgroup name.
Optionally, click the Group Member icon and add or define the element members of the
all_fem group. (Group members can be added at a later time if desired.) Press the All FEM, Add- button (not shown below). (Do not click Apply at this point either.)
Use the Parent icon to display and select the newly created group. Select the top level as the
parent: Group Hierarchy. Then click Apply. The Hgroup fem is created associated to the group
called all_fem, which contains all finite element entities.
For this example, Hgroups will be used to divide the FEM and Geometry into two groups.
Creating the fem Hgroup
select
Step 1
select
enter
press
Repeat the process for the Hgroup called geom associated to the group called all_geom.
Group>Attributes 305
Hierarchical Groups (Hgroups)
With the Group Hierarchy form displayed and the Action set to Create, and the Group icon
selected, identify or enter the group and Hgroup names. (Do not click Apply at this point.) Type
in all_geom for the group name and geom for the Hgroup name.
Optionally, click the Group Member icon and add or define the element members of the
all_geom group. (Group members can be added at a later time if desired.) Press the All
Geometry, -Add- button (not shown below). (Do not click Apply at this point either.)
Use the Parent icon to display and select the newly created group. Select the top level as the
parent: Group Hierarchy. Then click Apply. The Hgroup geom is created associated to the
group called all_geom, which contains all geometric entities of the model.
Creating the geom Hgroup
select
select
enter
press
306
Group>Attributes
The Group icon form to name the sub Hgroup and associated group.
The Group Member icon form to add information about the entity.
Use the Parent icon form to add the subelement to the Hgroup. First, select the parent Hgroup. Then, click
Apply on the Parent icon form. Continuing with the previous example, we would like to add a sub
Hgroup under the geom Hgroup to furthur refine the hierarchy. The geometry of the model contains two
surfaces. We will create two sub Hgroups under the geom Hgroup, each associated with one of the
surfaces of the model. Similarly we will create two sub Hgroups under the fem Hgroup each associated
with the elements of the particular surface. Thus if you post the fem Hgroup and all its sub Hgroups, you
will get all the fem posted and ikewise, with the geom Hgroup for posted geometry. If you select the sub
Hgroups for posting, then only those entities assicoated with them are posted.
With the Group Hierarchy form displayed and the Action set to Create, and the Group icon
selected, identify or enter the group and (sub) Hgroup names. (Do not click Apply at this point.)
Type in surface_1 for the group name and surface.1 for the (sub) Hgroup name.
Optionally, click the Group Member icon and add or define the element members of the
surface_1 group. (Group members can be added at a later time if desired.) Select Surface 1 from
the graphics screen and press the -Add- button under the Member List to Add/Remove . (Do not
click Apply at this point either.)
Use the Parent icon to display and select the newly created group. Select the geom level as the
parent. Then click Apply. The (sub) Hgroup surface.1 is created associated to the group called
surface_1, which contains just the entity Surface 1.
This operation can then be repeated for creating (sub) Hgroup surface.2, associated with group
surface_2, which contains entity Surface 2 where the Parent Hgroup is geom. The operation can then be
done two more times, once each for creating (sub) Hgroup FEM_surface.1 and FEM_surface.2,
associated with groups fem_surface_1 and fem_surface_2 each containing the finite element entities
associated to the two surfaces, respectively, and each having the fem Hgroup as their parent Hgroup.
Group>Attributes 307
Hierarchical Groups (Hgroups)
308
Group>Attributes
In this example, when both surfaces have been defined as subelements (sub Hgroups of the parent
Hgroup), the group hierarchy will look as follows:
Group>Attributes 309
Hierarchical Groups (Hgroups)
Posting an Hgroup
The following form is used to display all or parts of the hierarchy tree in the Viewport:
If Auto Post Subtree is checked on the form, all the selected groups and their subgroups and elements
get posted when Apply is clicked.
310
Group>Attributes
An additional icon, the Modify icon, is available on the Group Hierarchy form when the Action is
Modify and is used to perform the initial step of a modify operation.
Modify icon
Always start a modify hierarchical group operation by clicking the Modify icon.
For example, if the operation is to change a group name:
Click the Modify icon and select the Hgroup.
Click the Group icon and select the group.
Enter the new name.
Click Apply.
Group>Attributes 311
Hierarchical Groups (Hgroups)
Deleting Hgroups
The following form is used to remove the association between standard groups and Hgroups.
Use the checkboxes at the bottom of the form to scale the delete operation. You can delete the entire tree
by selecting Group Hierarchy.
Note that deleted items can be restored by:
Selecting the Undo option.
Using the Import form to recreate an exported tree.
312
Group>Attributes
on a different machine will restore the hierarchical relationships in an otherwise flat .bdf file.
Taking snapshots of hierarchical structures. You can restore a hierarchy to an earlier form after
Group>Attributes 313
Hierarchical Groups (Hgroups)
Use the following forms to export and import group hierarchy definitions. Use the Select Session File
option on the Export form to create a snapshot by assigning a name to and saving a hierarchy definition
as an export file. To import a saved session file, select the Select Session File option on the Import form.
314
Group>Attributes
Ch. 6: Viewports
Viewports
Viewport Commands
320
321
316
316
6.1
Viewport Names
Viewports are given names to differentiate them from one another. In naming a viewport, you must
conform to the following set of rules:
Uniqueness--each name must be unique.
Number of characters--name may not contain more than 31 characters.
Legal characters--the following characters are acceptable in names:
a through z
A through Z
0 through 9
-, _ , and .
Case sensitivity--upper and lower case letters are recognized. For example, top_view and
Viewport Status
The status of a viewport may be:
current (or not current)
posted (or unposted)
target viewport
Current Viewport
The current viewport is the viewport in which view commands are applied, titles are posted, and
postprocessing is performed. Only one viewport may be current at one time and only the current viewport
is updated when a model is viewed from a new angle or with new results and titles.
Posted Viewport
Posted viewports are the only viewports displayed on the screen. If a viewport is unposted it is hidden
from view.
You can hide any posted viewport but do not unpost the viewport to which the current group is posted,
or else you will not be able to see the geometric and finite element entities as they are created.
Target Viewport
The target viewport is a viewport selected for modifications. Any viewport can become the target
viewport, including the current viewport.
318
Origin Symbol--crosshairs that identify the global cartesian origin (0,0,0) location. While this
symbol is ON by default, it can be turned OFF (see Show Origin Symbol, 327).
Global Cartesian Coordinate Axes--the icon that represents the global Cartesian coordinate axes
is displayed in the viewports lower left corner. As the viewing plane is rotated, the orientation
of these axes will change to reflect the new position of the model. While this symbol is ON by
default, it can be turned OFF (see Show Global Axes, 327).
Local Coordinate Axes--the icon that represents the axes of a locally defined rectangular,
cylindrical, or spherical coordinate system (for more information on local coordinate systems,
see Coordinate Frames, 383 )
Tiling Viewports
Posted viewports can be tiled within the available screen area. Tiling scales viewports so that they are of
the same size and repositions them in rows and columns to fit the viewing area.
320
6.2
Viewport
Create...
Post...
Modify...
Delete...
Tile
The Viewport menu functionalities are described below in the order in which they appear.
Create...
Post...
Modify...
Delete...
Tile
6.3
Viewport Commands
The following is a detailed description of the commands and dialog boxes with which you create and
manage viewports.
322
Viewport>Create
Viewport>Create
With the Viewport>Create command sequence you can create and name new viewports.
Existing Viewports
Enter a unique new viewport name; (see Viewport Names, 317 for
more help).
Note that a newly created viewport automatically becomes the current viewport.
Viewport>Post 323
Posting and Unposting Viewports
Viewport>Post
The Viewport>Post dialog box allows you to post or unpost one or more selected viewports. Posted
viewports are the only viewports visible on the screen. The current viewport is automatically posted.
Post/Unpost Viewports
Displays the names of all viewports in the database. The name of the
current view is highlighted since it is automatically posted.
To post a viewport, click on its name to highlight it. When you select
a viewport for posting, all other viewports become unposted and their
names become unhighlighted.
To select several viewports listed consecutively, hold the Shift key
while clicking each item. To select several viewports not listed
consecutively, hold the Ctrl key while clicking.
Caution:
If you unpost the current viewport, it will not be shown on the screen. Neither will the
current group, which is posted to the current viewport (see Posted Group, 261).
Consequently, you will not be able to see new geometric and finite element entities as
they are created.
324
Viewport>Post
If you select a viewport other than the current viewport for posting, the current viewport will be unposted.
Patran will display the following warning message:
Viewport>Modify 325
Modifying Viewports
Viewport>Modify
Modifying Viewports
With the Viewport>Modify command and dialog box you can modify the following viewport
definitions:
Indetify the viewport targeted for modifications (the target viewport).
Make the new target viewport current.
Post/unpost groups to the target viewport.
Set the current group.
Apply a named view to the target viewport.
Rename the target viewport.
326
Viewport>Modify
Modifying Viewports
Current Viewport
Displays the Change Target Viewport dialog box in which you can
select a different viewport for modification.
Make Current
Post/Unpost Groups...
Displays a dialog box in which you can select one or more groups to
post or unpost (display or hide) in the target viewport.
Viewport>Modify 327
Modifying Viewports
Displays a dialog box in which you can select a group that will be the
current group in the target viewport.
Brings up the Apply Named View dialog box in which you can select
a previously defined and named view that will be displayed in the
target viewport.
Rename...
Displays a dialog box in which you can specify a new name for the
target viewport.
Attributes
Background Color
Background Effects
Range Name
Displays the name of the selected range (or the default range).
Change Range
If the toggle is ON (4), the crosshairs that identify the global cartesian
origin (0,0,0) location will be displayed in the target viewport. Default
is ON.
328
Viewport>Modify
Modifying Viewports
X,Y Location
Indicates the location of the upper left corner of a viewport. Note the
following:
Point (0 0) is at the upper left corner of the viewing area.
Positive X is toward the right, positive Y is toward the bottom
Returns the contents of the entire dialog box to their previously applied
state and values.
Viewport>Modify 329
Modifying Viewports
330
Viewport>Modify
Modifying Viewports
Filter
Minimizes the number of items that appear in the list (optional). You
may enter a combination of one or more characters and wildcards (*)
then press the Filter button. Only the item(s) whose name passes the
filter criteria will be listed in the text field.
Default is (*), meaning that all items will be listed.
Viewports
Lists the name of all existing viewports. Pick the viewport you want to
designate as the new target viewport.
Viewport>Modify 331
Modifying Viewports
Target Viewport
Displays the name of the target viewport in which the change will take
place.
Filter Specification
Minimizes the number of items that appear in the list (optional). You
may enter a combination of one or more characters and wildcards (*)
then press the Filter button. Only the item(s) whose name passes the
filter criteria will be listed in the text field.
Post/Unpost Group(s)
332
Viewport>Modify
Modifying Viewports
Filter Specification
Minimizes the number of items that appear in the list (optional). You
may enter a combination of one or more characters and wildcards (*)
then press the Filter button. Only the item(s) whose name passes the
filter criteria will be listed in the text field.
Existing Names
Displays the names of previously defined groups. Pick the group you
wish to specify as the current group in this viewport.
Current Group
The name of the newly selected current group will also appear in this
text field.
Note:
As an alternative to this command, you can simply click inside the viewport window to
specify it as the current viewport.
Viewport>Modify 333
Modifying Viewports
Target Viewport
Shows the name of the target viewport in which the named view will
be displayed.
Filter Specification
Minimizes the number of items that appear in the list that follows
(optional). You may enter a combination of one or more characters and
wildcards (*) then press the Filter button. Only the item(s) whose name
passes the filter criteria will be listed in the text field.
Named Views
334
Viewport>Modify
Modifying Viewports
Renaming a Viewport
If you pressed the Rename... button in the Viewport>Modify dialog box, you will see the subordinate
dialog box shown below.
Filter Specification
Minimizes the number of items that appear in the list (optional). You
may enter a combination of one or more characters and wildcards (*)
then press the Filter button. Only the item(s) whose name passes the
filter criteria will be listed in the text field.
Default is the wildcard (*), meaning that all items will be listed.
Existing Names
Rename As
Enter the new name that you want to give to the target viewport.
Viewport>Modify 335
Modifying Viewports
Color 1 / 2
Select the color of the background. If both colors are the same, a solid
backgroud of that color is displayed. If the two colors are different,
then a gradation/transition between the two colors is displayed based
on the Shading Syles.
Swap Colors
336
Viewport>Modify
Modifying Viewports
Shading Styles
Inside Out
Creates a shading from the middle out instead of top to bottom (or right
to left as the case may be).
Preview
Apply / Cancel
Press Apply to keep the effect and then Cancel to close the form.
Viewport>Modify 337
Modifying Viewports
Target Viewport
Displays the name of the target viewport in which the change will take
place.
Filter
Minimizes the number of items that appear in the list that follows
(optional). You may enter a combination of one or more characters
and wildcards (*) then press the Filter button. Only the item(s) whose
name passes the filter criteria will be listed in the text field.
Ranges
Displays the names of previously defined Ranges. Pick the range you
wish to use for results displays in the target viewport. The newly
selected name will also appear in the Viewport>Modify dialog box.
338
Viewport>Delete
Deleting Viewports
Viewport>Delete
Deleting Viewports
With the Viewport>Delete command sequence you can delete any number of viewports--except the
current viewport.
Current Viewport
Select a Viewport(s)
Displays the names of all existing viewports, with the exception of the
current viewport.
Pick the name of the viewport you want to delete.
To select several viewports listed consecutively, hold the Shift key
while clicking each item. To select several viewports not listed
consecutively, hold the Ctrl key while clicking.
Viewport>Tile 339
Tiling Viewports
Viewport>Tile
Tiling Viewports
With the Viewport>Tile command you can display a number of viewports in an ordered tiled
arrangement. Extents of viewports are changed so that each view is the same size and viewports are
positioned in rows and columns to fill the viewing area.
340
Viewport>Tile
Tiling Viewports
Introduction
342
343
346
342
7.1
Introduction
In Patran additional context-dependent functionality has been added to the right mouse button to reduce
the mouse travel required to manipulate the display or obtain simple model information.
Right Mouse Button (RMB) Display Control right click on an open area of the viewport to
perform operations such as: clean up the display or refresh the graphics, tile the viewport and
menus in the Patran window, or do a fit view to see the entire model
Right Mouse Button Viewport Control right click on an open area of the viewport to change
the change the model orientation, render style, reverse the background, or show the cycle picking
labels
Right Mouse Button Model Information right click on an entity to find information or
Note:
Right click on a node or element to obtain information such as location, attributes, verification
options or associations
Right click on a geometry entity to obtain information such as surface area, curve length or
arc dimension, and FEM association such as mesh seeds or associated nodes / elements
The right mouse button menu is completely customizable so you can add your favorite
viewport or display function to the menu. The procedure for customization is provided
later in this section.
7.2
Select a Node, Element or Geometric Entity, Right Click on it to See The Options
You can use the right mouse button in conjunction with the select filter to get information on FEM entities
without navigating the AOM menus. Clicking the right mouse button when over an entity will bring up
the RBM menu where you can choose from a long list of options.
344
Some of the options available from the right mouse button apply to individual entities, such as the
transform, modify, show or sweep options.
346
7.3
deactivated.
Label for the menu-item (optional)
Consider the case of adding a menu-item to set the color of all selected geometric entities. Lets name the
menu-item as AsmSetColor. Lets also specify the callback function as asm_set_color_cb ; condition
function as asm_set_color_cond; and the label as Set Color. Once selected the icon will take the user
to the same application menu form as earlier, thus there is no learning curve required.
There are 2 types of xml files. One containing the information regarding the menu layout and the
callback of menu-items. The other contains the resource related information for the menus and
menu-items. In the following example label only is used. Other things like icon can be easily
added later.
The file containing the definition (p3_user_menu.xml) starts with the tag <RMBMAP>. The one
<MENU>
<NAME>ASM_MENU</NAME>
<ADDMENUITEM>AsmSetColor</ADDMENUITEM>
</MENU>
<MENUITEM>
<NAME>AsmSetColor</NAME>
<CALLBACK>asm_set_color_cb</CALLBACK>
<CONDITION>asm_set_color_cond</CONDITION>
</MENUITEM>
Add the following in p3_user_menu_res.xml within the <RMBRESOURCEMAP> tags:
<MENUITEM>
<NAME>AsmSetColor</NAME>
<LABEL>Set Color</LABEL>
</MENUITEM>
Implement the callback function in any .pcl file (note the function signature):
FUNCTION asm_set_color_cb( sel_entities, entity_type )
STRING sel_entities[]
STRING entity_type[]
dump sel_entities
dump entity_type
END FUNCTION
Implement the condition function in any .pcl file(note the function signature):
FUNCTION asm_set_color_cond( sel_entities, entity_type )
STRING sel_entities[]
STRING entity_type[]
RETURN TRUE
END FUNCTION /* Activate this menu item */
Run Patran. Load the PCL file containing the callback and condition function definition using
!!input command in the Patran command window. Thus if you put the functions in the text
file test_rmb.pcl, you would type
!!input test_rmb.pcl
Once the functions are input (compiled), click on the RMB in the viewport to see that Set
Color was added at the bottom:
A slightly more complex example can be performed by replacing the name NoEntityMenu in the
<NAME>NoEntityMenu</NAME> line of the p3_user_menu.xml file with ASM_MENU. If you do this
and carry through with the rest of the example, you will find that the Set Color option will only appear
at the bottom of the RMB menu after you have selected multiple types of geometry.
The above examples show how you can add functionality to the RMB. The XML files that control the
default RMB menu are in the Patran installation directory under the rmb_menu subdirectory. You can
examine these files to see how the submenu structures are set up if you wish to create your own. You can
348
also modify these files to change the default behavior of the RMB, or even change the functions called
by the call backs.
New and more complex call back functions can also be created, however, these call back functions must
all have argument lists that follow the same format. Specifically they must use the format and arguments
identical to those of the example: two string variables as arguments. This means that there are no limits
on what the call back functions do as long as the argument list is matched.
Viewing a Model
Viewing Commands
354
356
350
350
8.1
Current View
Each viewport displays one independent view of a stationary model. The current view is the view most
recently defined for a viewport.
Named Views
If in a work session you rotated, zoomed, scaled, or clipped a view to show a particular aspect of your
model, you can preserve all your modifications with a named view that will be stored and ready to be
recalled at a later time or even in a different model (see Named Views in Viewports, 318). Additionally,
Patran provides several predefined standard engineering views (e.g., top_view) that you can utilize in any
viewport.
When naming a new view, remember that just as in naming groups or viewports, view names must
conform to the following set of rules:
Uniqueness--each name must be unique.
Number of characters--name may not contain more than 31 characters.
Legal characters--the following characters are acceptable in names:
a through z
A through Z
0 through 9
-, _ , and .
Case sensitivity--upper and lower case letters are recognized. For example, front_view and
Model Space
Model space is defined in the global X, Y, and Z rectangular coordinate system.
Screen Space
Screen space is defined by a projection planes X and Y coordinate system.
Screen Axes
Global Origin
Y
Observer
Position
Focal Point
Z
X
Z
Viewing Plane
Viewing Plane
The viewing plane lies in the plane of the screen and is the plane onto which the model is projected.
Window Center
The window center is at the center of the viewing plane.
Model Center
The model center is the geometric centroid of a viewports displayed geometric and finite element
entities.
Automatic Centering
The model center is recalculated each time an entity is added or removed, or each time a group is posted
or unposted. However, the focal point may be moved to coincide with the model center.
352
Fitting a View
Fitting a view moves and resizes the view of the model so that all model entities will fit inside the current
viewport window. The views rotational orientation will remain the same.
View Transformations
Transformations refer to the action of panning, rotating, and resizing a view in the current viewport.
Pan
Moves the window center left, right, up, or down in the current viewport as if a camera panned
over the model in the view.
Zoom
Makes the model appear larger (zoom in) or smaller (zoom out) in the viewport.
Rotate
the applicable icon to pan, zoom, or rotate a view. Accept a default transformation factor or
specify the desired rate by which the transformation will be performed.
Other Viewing menu commands--use one of the following Viewing menu commands:
Note:
Several shortcuts to some of the view control functionalities are also available via tool bar
icons (see also Mouse Function Tool Palette, 16 and Viewing Tool Palette, 17).
View Clipping
To clip a view, you make use of one or more planes to slice into the model at selected locations. Since
the geometry outside the clipping planes will be eliminated from view, with view clipping you can show
the inside of a model as well as create special sectional views. Z-axis clipping provides front and back
clipping planes that are parallel to the XY plane. In arbitrary clipping, you can define, orient, and place
your own clipping planes for specific clipped views.
Perspective Views
Perspective viewing makes surfaces that are farther from the position of an observer appear smaller.
Changing the observers position as well as the viewing plane location will modify perspective distortion.
View Parameters
Focal Point
The views origin, it is also the center of rotation when the view is rotated, the center for scaling, and the
perspectives center.
Window Center
The center of the viewing plane from where translation distances are measured.
Y
Focal
Point
Viewing Plane
Observers
Position
354
8.2
Viewing
Transformations...
Ctrl T
Fit View
Ctrl F
Select Center
Select Corners
Zoom (% of view)
Angles...
Custom...
View From/To...
Scale Factors...
Named View Options...
Clipping Perspective...
Arbitrary Clipping...
The Viewing menu functionalities are described below in the order in which they appear.
Transformations...
Displays graphic icons with which you can pan, rotate, and zoom a
view by selected incremental factors. Also provides a Fit View icon to
adjust the view of the model to be contained completely inside the
boundaries of the viewport.
Fit View
Moves and resizes the current view so that all model entities will fit
inside the current viewport window. The views rotational orientation
will remain the same.
Select Center
Select Corners
Zoom (% of view)
Angles...
View From/To...
Scale Factors...
Clipping/ Perspective...
Arbitrary Clipping...
356
Viewing>Transformations
Viewing Commands
8.3
Viewing Commands
The following is a detailed description of the commands and dialog boxes that manage and manipulate
views.
Viewing>Transformations
Transforming Views
With the icons of the View>Transformations dialog box you can pan, rotate, zoom, or fit the view in
the current viewport. Transformations are incremental, each mouse click will modify the view
orientation once by a predefined amount that you specify in the Options... dialog box.
Visually translates (pans) the model in the view left, right, up, or
down, by a selected incremental pan factor.
Viewing>Transformations 357
Transforming Views
Transformation Options
If you pressed the Options... button in the View>Transformations dialog box, you will see the
subordinate dialog box shown below.
Rotation
Displays the rotation angle in degrees. Each mouse click will rotate the
view of the model by that increment. Move the slidebar to the desired
angle value.
Model Relative
Screen Relative
358
Viewing>Transformations
Transforming Views
Pan Factor
Displays the panning rate in model units. Each mouse click will move
the view of the model by that increment. Move the slidebar to the
desired panning rate value.
Zoom Factor
Displays the zooming rate. Each mouse click will zoom the view of the
model at that rate. Move the slidebar to the desired zoom factor value.
Fit View
Fitting a view moves and resizes the view of the model so that all model entities will fit inside the current
viewport window. The views rotational orientation will remain the same (for automatic execution of Fit
View, see Automatic View Settings, 460).
Select Center
The Viewing>Select Center command is an alternative way of panning the model. Click an arbitrary
point in the viewport and the view will be repositioned with its window center at the selected point. Note
that if you picked a point in a viewport other than the current one, that viewport will automatically
become the current viewport.
Select Corners
Using the Viewing>Select Corner command, you can zoom to a cursor-defined rectangular area of the
current view of the model.
Move the cursor to a point at the edge of the area you wish to zoom (P1). This point becomes the first
corner of the rectangle. Click and hold down the left mouse button while dragging it to form the rectangle.
When the rectangle surrounds the desired area, release the mouse button at the opposite corner (P2). The
views center will reposition itself to the center of the rectangle, and the selected area will zoom to fill
the viewport.
Viewing>Transformations 359
Transforming Views
The viewport in which you select the corners will automatically become the current viewport.
P1
P2
360
Viewing>Zoom (% of View)
Zoom by a Specified Factor
Viewing>Zoom (% of View)
The Viewing>Zoom (% of View) command lets you specify the zoom rate numerically rather than using
the zoom icon and the slidebar.
Zoom Factor
Custom...
Enter a zoom factor in this subordinate dialog box if you want to use a zoom factor
other than those listed.
Viewing>Angles 361
Rotate by a Specified Angle
Viewing>Angles
Use the Viewing>Angles command when you want to enter very specific rotation angles that are not
easily set with the rotation slidebar, or when you want to control the axes about which the view is rotated.
Rotation Terminology
Model
The view is rotated about the global model axes. These stay fixed to
the model and rotate with the model.
Screen
The view is rotated about the screen axes. These are fixed to the screen
and never move.
Absolute
Relative
Rotation Angles
Unit of Rotation
The center of rotation is the focal point (see Observation Point, 363);
the only point that remains fixed during a view rotation. If the center
of rotation does not coincide with the model center, the center of the
model will move, and a portion of the model (or the entire model) will
move outside the viewport during rotation.
362
Viewing>Angles
list2+
Rotate the view as follows:
Rotation Method
Model Absolute
Rotation Angles
Action
The view is rotated from the global zero starting position, -30o, 10o, and 15o
about the global X, Y, and Z-axes, respectively.
Rotation Method--
Model Relative
Rotation Angles--
Action--
The view will be rotated from the current starting position, -30o, -5o, and 5o about the global X, Y, and Z-axes, respectively.
End result:
The new view will have rotated a total of -40o, 5o, and 10o from the global
staring position about the global axes.
Viewing>View From/To
The position of two points, the view origin, or focal point, and the observer position (see Observation
Point, 363) also influence the rotational orientation of a view.
In the Viewing> From/To dialog box, you can enter new coordinates for one or both of these points. If
you move either one--but not the other-- the view will be rotated. If the coordinates of both points are
changed by the same value, the view orientation remains unchanged.
Observation Point
Focal Point
The focal point is the views origin as well as the center of rotation
when the view is rotated. To change the focal point location, enter new
model space coordinate values.
Model Center
364
Viewing>Scale Factors
Scaling a View
Viewing>Scale Factors
Scaling a View
The Viewing>Scale Factors dialog box lets you enter specific scale factors to create a scaled view of the
model.
The scale factors are applied in the X and Y directions of screen space.
The center of scaling is the focal point.
Viewing>Named Views
With the Viewing>Named View Options command, you can create special views that can be named and
stored for later use. When a named view is applied in a selected viewport, the view of the model will
366
Viewing>Named Views
change to the same orientation, size, and clipping state defined for the named view. In this dialog box you
can also rename and delete existing named views.
Current Viewport
Lists all named views that exist in the database. Click on the view you
want to display in the selected viewport.
Create View...
Creates and saves a new named view. After you positioned, rotated,
and sized a view to achieve the effect you wanted, select this
command then specify a new, unique view name in the subordinate
dialog box.
Rename View...
Delete View...
368
Viewing>Clipping/Perspective
Clippped Views
Viewing>Clipping/Perspective
Clippped Views
Viewing>Clipping/Perspective 369
Clippped Views
With the Clipping part of this command, you can control the location of the Z-clipping planes visually,
as well as numerically in the dialog box.
Z Min/ Z Max
These show the extents of the view of the model in the positive and
negative Z direction.
Front/Back Clipping Planes These text boxes show the current position of the front and back
clipping planes. Enter new values to change the position of either or
both, then press Apply.
You can also change the Z-clipping plane location by simply dragging
the plane symbols to the left or to the right. The changes will apply to
the model immediately, clipping it according to the new distances.
The numerical values in the databoxes will update as well.
Note that the front clipping plane distance must be greater than the
back clipping distance, otherwise, the back clipping plane would end
up in front of the front clipping plane. If you enter wrong values, a
warning message will appear.
370
Viewing>Clipping/Perspective
Perspective Views
Viewing>Clipping/Perspective
Perspective Views
In the Perspective portion of the dialog box, you can modify the parameters of a perspective view,
namely the location of the viewing plane and the observer position.
Front Clipping
Plane
The distance between the viewing plane, which is normal to the Zaxis, and the focal point measured along the Z-axis. If this distance is
zero, the viewing plane intersects the Z-axis at the focal point. A
positive value places the viewing plane to the right of the focal point
while a negative value moves it to the left of the focal point.
Observer Position
Viewing>Clipping/Perspective 371
Perspective Views
The distance between the viewing plane and the observer position
controls the distortion caused by perspective viewing. A greater
distance will result in less distortion; as you decrease the distance the
distortion will increase.
Visual Positioning
372
Viewing>Arbitrary Clipping
Viewing>Arbitrary Clipping
The Viewing>Arbitrary Clipping dialog box accepts and displays all necessary information to create
and manipulate arbitrary, or user-defined clipping planes.
374
Viewing>Arbitrary Clipping
Post/Unpost Clipping
Planes
Create...
Creates a new clipping plane. Brings up a text box in which you can
enter the new name.
Delete...
If ON, the clipping plane will retain its orientation relative to the
model even when it is moved. When OFF, the orientation of the
clipping plane is relative to the screen.
Options
Incrementally rotates the clipping plane around its X or Y axis
clockwise or counterclockwise. You set the rotation angle in the
Rotate slide bar; each mouse click causes one rotation.
Incrementally translates the clipping plane along its normal. You set
the increment in model units in the Number of Units text box. Each
mouse click moves the plane once.
Direction
Location
376
Viewing>Arbitrary Clipping
Display Control
Display Commands
385
386
378
378
9.1
Display Modes
For controlling entity colors, labels, and render styles you must choose between two display modes:
Entity mode--targets entities according to entity type. For example, you may specify that
solids must be shaded and green-colored. This specification then will apply to all solids in the
database.
Group mode--targets entities according to group membership. For example, if Fender and
Wheel comprise two groups in a model, solids in the group called Fender may be rendered in
wireframe while those in Wheel may be shaded.
Display modes are global in nature; whichever you select will apply to the display in all visible
viewports.
Rendering Styles
While you are constructing a geometric or FEM model, it is not necessary to display solids and surfaces
in true-to-life photographic appearance. Such display would actually make it difficult to create certain
geometry, such as entities that define the interior of an object. In addition, it would take more time to
perform operations related to many display functions, such as view transformations.
Rendering is a tool that can change the display of solid or surface geometric and FEM entities for
visualization purposes. The basic rendering styles are wireframe and shaded, with additional options
within each of these styles.
Wireframe
In wireframe, the edges of solid and surface entities are displayed but faces appear transparent. To help
perceive surface contours, however, visualization lines can be drawn in all parametric directions. You can
control the number of lines depending on what it takes to improve visualization (see Number of Display
Lines, 392).
Wireframe/Accurate
This rendering style, used primarily when in group display mode, affords better visualization of a group
that appears in the same viewport with smooth shaded entities of other groups. This technique takes into
consideration changes in depth, therefore it is especially appropriate for showing how certain objects are
positioned behind one another.
Hidden Line
Hidden line rendering also displays the edges of solids and surfaces but the faces appear opaque, not
transparent. As a result, portions of an object that would be hidden from an observer are also hidden in
the display. In some cases this will result in a more realistic image of an object, especially in straightedged solids; for curved edges, however, it helps if you use visualization lines in the display.
380
Hidden Line/Accurate
This rendering combines the characteristics of Hidden Line and Wireframe/Accurate styles. It renders
hidden edges and faces invisible and also depicts the correct spatial order of objects.
Shaded/Flat
A compromise between smooth shading and wireframe or hidden line representation is flat shading.
Flat shading applies a series of shaded triangles of constant color to faces. Visual accuracy increases as
the number of triangles increases and the size of triangles decreases. The number and size of triangles is
governed by a calculated value called chordal tolerance.
Chordal Tolerance
Database definitions of even the most complex solid or surface objects are mathematically accurate, but
the exact graphical representation of curvatures in solids is, to some extent, at the expense of display
speed and computer resources. Therefore, the screen display of objects is somewhat less precise than the
mathematical data.
With the approximation technique used for creating the display, curved edges are replaced with a series
of straight line segments, or chords. The distance between a curve segment and its subtended chord is the
chordal deviation.
chordal deviation
d
chord
Chordal tolerance is calculated as the ratio of the chordal deviation and the length of the curve segment.
It is a user-controllable input that is entered as a display parameter. Bear in mind that while very small
chordal tolerance values produce smoother, more realistic displays, they may also cause the slowing
down of view-related operations.
Chordal Tolerance = 0.02
Shaded/Smooth
The most realistic display of models is the smooth shaded image. It renders surfaces and solids
realistically, in a smoothly shaded manner, as if a light were shining on the model. It only shows visible
faces and edges, and does not display those that are hidden from view.
382
edge will be drawn with two line segments; one from the first corner node to the midside node, and one
from the midside node to the second corner node.
QUAD8
Default
Similarly, the default number of display lines on the edges of a QUAD12, a cubic quadrilateral element
with two midside nodes, is three.
It must be emphasized that the display of line segments is strictly a visual tool and has no effect on the
mathematical formulation of elements.
Shrinking Entities
Shrinking is another display tool that can help improve visualization. It reduces the screen size of each
geometric or finite element entity separately by a user-selectable shrink factor, defined in model
percentage. For example, when you shrink adjacent solid components that initially touch one another,
they will become separated (each is individually shrunk by the shrink factor). You can then examine these
entities to be sure that each is geometrically correct. Similarly, you can shrink a FEM mesh to display
finite elements more distinctly within the geometric model.
Shrink action is global, it affects all entities in all viewports. Both geometric and FEM shrink are saved
in the database; if you apply shrink to a model and save it upon exiting, you will find the model in the
same saved shrink state when you open it again.
Titles
Especially useful for proposals or presentations, titles and other textual information enhance the display
of the model. Text is inserted into a selected viewport and is related to the viewport only, not to the model
nor to the view. Therefore, it remains in position through any view modification (e.g., view panning).
Each viewport may be annotated with different text and titles, however the same text may also be posted
to several viewports.
Coordinate Frames
Local coordinate frames are user-defined coordinate systems, generally created to help build specific
geometry and to evaluate localized results (see also Geometry Modeling, Chapter 3, p. 59). Their
symbols may be displayed or hidden, as desired.
Named Attributes
You can create a named attributes set to save certain changes you made to the geometry or FEM display.
The attributes in the set will then be available any time you work with the model, sparing you from
repeating the display changes.
Spectrums
In Patran, spectrum is a named, ordered set of colors, used for displaying analysis results. For example,
when stress analysis results are superimposed on a model, it is customary to use the colors in the red
family to indicate hot spots, or high stress areas, then transition toward the cool blue colors where
stresses are low. Spectrums, together with specific range and subrange definitions, interpret the colorcoding of result displays and the underlying numerical values.
Spectrum definition is global; the same spectrum is automatically used in all viewports where analysis
results are displayed.
Ranges
A range is a named collection of ordered subranges that attach numerical meaning to the displayed colors
according to result values. A subrange is generated when the full extent of analysis results (between
defined minimum and maximum values) is divided, automatically or manually, into smaller intervals
with specified starting and ending boundaries. Each subrange is paired with a color in the spectrum. In a
result plot, nodes and elements are shown in the color assigned to the subrange to which their analysis
results belong.
Thresholding cuts down the amount of data utilized for displayed analysis results. It may be used to
eliminate from the result plot those values that fall in the upper or lower extremes of the result range. An
even more important function of thresholding is the ability to delimit a narrow interval, with upper and
lower boundaries, in the vicinity of a particular result value that requires closer examination.
Ranges are not defined globally but linked to viewports. Using this feature, you can simultaneously
display results of multiple analyses (e.g., structural and thermal) with different range definitions in each
viewport.
384
Color Palette
For all color displays, Patran uses a color table of 16 colors. A named, ordered collection of the 16 colors
in various combinations makes up a Color Palette.
Several pre-defined color palettes exist, the one initially used in a new database is named
standard_colortable. You can modify the currently existing colors to create and store any number of new
color palettes in a database.
The first color in a color palette defines the viewport background color.
Color palettes are global in nature and will affect all viewports, therefore, only one color table can be
active at any one time.
Light Sources
The appearance of shaded surfaces is significantly affected by the nature of light that illuminates them.
You can experiment with some of the light-source control features to see which one will make the model
look even more realistic and visually pleasing.
Patran comes with several existing light source definitions, try them before you introduce new light
sources. If these do not produce the effect you are seeking, you can modify an existing light source or
create any number of new ones.
The characteristic features of light are color, intensity, direction, and the distance of the light source from
the object.
In Patran you can choose among the following types of light sources:
Ambient--a background light, typically used to provide low level lighting around the model.
Directional--directional light simulates the effects of sunlight. It is spread uniformly across a
surface and its intensity depends only on the direction of the light not on the distance between
the object and the light source.
Spot--spot light is typically controlled by the location of the light source as well as the direction
of the light. A characteristic feature of this light source is attenuation, the measure of influence
of the distance between the object and the light source on the intensity of light on the surface. At
attenuation = 0, distance has no significance, and spot light is effectively the same as directional
light.
9.2
Entity Color/
Label/Render...
Plot/Erase...
Highlight...
Geometry...
Finite Elements...
Named Attributes...
Coordinate Frames...
Titles...
Spectrums...
Ranges...
Color Palette
Shading...
Light Source...
386
Display>Entity Color/Label/Render
Display Commands
9.3
Display Commands
The following is a detailed description of the commands and dialog boxes that affect the appearance of
model entities in viewports.
Display>Entity Color/Label/Render
In these dialog boxes you specify rendering styles for solid and surface entities, control the colors
assigned to entities or groups, and turn entity labels on or off.
Entity Type
Specifies that actions in this command will target entities by type. The
selected rendering style will apply to all surfaces; similarly, colors and
label On/Off designations will affect all entities within a specific entity
class (e.g., all curves).
Group
Specifies that the actions of this command will target entities by group
designation. Displays a dialog box in which you define the rendering
style, color, and label On/Off choice as they apply to members of a
selected group.
Render Style
Shade Color
Sets the color of shaded solid and surface entities, if Shaded rendering
was selected. This color will not apply if the object is rendered in
wireframe.
In the Entity mode dialog box; turns labels on or off for all entities.
Show Labels
In the Group mode dialog box; turns labels on or off for all group
members.
Controls the size of entity labels. Note that the font size change can
take effect only if you specify Software Rendering Mode in the
Graphic Preferences Menu ( see Preferences, 435.).
388
Display>Plot/Erase
Display>Plot/Erase
With the Display>Plot/Erase command you can temporarily hide (erase) selected entities or redisplay
erased entities (plot).
Both Erase and Plot are global actions; erased entities are removed from every view and plotted entities
are restored to all views. Since erased entities are only hidden from display and not deleted from the
database, the results of the erase action will not be saved when you exit from the database.
Selected Entities
Lists entities selected for erasure. You can type entity IDs, select them
with the mouse (hold the Shift key for multiple selections), or use any
other select mechanism (see Selecting Entities, 33). The text in this
textbox is editable, you can delete any entity ID you did not intend to
include in the list.
Erase
Display>Plot/Erase 389
Erasing and Redisplaying Entities
Plot
Coord. Frames
Brings up the Coordinate Frames dialog box in which you can select
the local coordinate frame(s) you want to display or hide from view.
Posted Entities
Geometry Erase/Plot
FEM Erase/Plot
All Erase/Plot
390
Display>Highlight
Display>Highlight
Use the Display>Highlight command to call attention to specific entities or to locate certain entities by
their ID number. The default highlight color is red. If you want to change the default, you have to go to
the Preferences>Graphics command (see Preferences, 435).
Selected Entities
Lists the entities you selected for highlighting. Pick entities using any
of the select mechanisms (multiple pick with the Shift key, polygon
pick, etc. see also Selecting Entities, 33). Alternately, type the name
and ID number of entities. The text in this textbox is editable; you can
correct, add or delete any text.
Highlight
Performs the highlight action. You need to click this button only if you
entered entity IDs. If you picked entities with the cursor, they will
highlight immediately.
Clear All
Clears the highlights as well as the entries from the textbox, but leaves
the dialog box on the screen.
OK
Removes the highlights and the dialog box from the screen (pressing
the Enter key will have the same effect).
Display>Geometry 391
Modifying the Appearance of Geometric Entities
Display>Geometry
The Display>Geometry command lets you change certain display attributes of geometric entities. The
modified display features are saved upon exiting the model and will be recalled when you open the
database again.
392
Display>Geometry
Chordal Tolerance
Shows the selected chordal tolerance value that controls the precision
of the display of solid geometry (see Chordal Tolerance, 380).
Geometric Shrink
Show Parametric Direction Displays the location and orientation of the parametric axes of
geometric entities. This information may be essential in certain
geometric and finite element applications, for example, the parametric
directions of a surface determine the direction of element normals,
that in turn defines the positive direction of pressure loads on the
surface.
Show Free Faces
Shows free faces of solids. This feature is useful when you import
CAD geometry that might contain gaps that will prevent you from
creating acceptable meshes on the model.
Point Size
Controls the colors and label display of geometric entities. This dialog
is the same as in the command Display>Entity Color/Label/Render
(see Display>Entity Color/Label/Render, 386), except it applies only to
geometric entities. The two commands work together, the latest input
in either one will become the prevailing color definition and will show
up in both dialog boxes.
Coordinate Frames
Note:
You can save the first five of the geometry attributes in a named attribute set (see Named
Attributes, 383.
Display>Finite Elements
The Display>Finite Elements command can change certain display attributes of FEM entities. Modified
display features are saved when you save and exit the model, and will be recalled when you open the
database again.
394
Display>Finite Elements
FEM Shrink
Shows the model percentage by which the display of each FEM entity
will be shrunk. At default=0, no shrinking takes place.
Faces
A free face is an element face that is not shared by at least one other
element. When this toggle is on, only the free faces are displayed. This
too can help you verify the continuity of the finite element model.
Node Size
Controls the colors and label display of FEM entities. This dialog is
the same as in the command Display>Entity Color/Label/Render
(see Display>Entity Color/Label/Render, 386, except it applies only to
FEM entities. The two commands work together, the latest input in
either one will become the prevailing color definition and will show
up in both dialog boxes.
Coordinate Frames
Connector Attributes
Note:
You can save the first five of the FEM attributes in a named attribute set (see Named
Attributes, 383).
Display 2D Markers
Display 3D Markers
Scale
Unverified Connectors
The color that unverified connectors shall be displayed in. In the event
that the underlying model of a connector is changed (like a remesh),
then the connector will be flagged as Unverified, until it is re-verified.
Such connectors shall be displayed in an alternate color, defined here.
396
Display>Finite Elements
With this command you can control the display symbols for loads, boundary conditions, and element
properties.
398
Load/BCs
Element Properties
If you turn this OFF, but keep the Vectors on, the symbols will be
displayed but not the numerical values.
Vectors/Filters
Displays the Vector Attributes dialog box in which you can select the
length and color properties of display vectors. Optionally, you can also
stipulate that vectors be displayed according to some filtering
mechanism, e.g., if the numeric value they represent exceeds some
specified minimum.
Label Style
Displays the Label Style dialog box that provides options for the
display format of the numerical values of functional assignments.
Beam Display
Vector Attributes
In this dialog box you can designate length, color, and filtering characteristics for the vectors that
represent loads, boundary conditions, or certain element properties.
400
Vector Length
Constant Screen Relative/
Model Relative
The length of the vector symbols is constant. When you use this option
all vectors are of the same length; for example, a vector that represents
a 100 lb force will be just as long as the one that represents a 1,000 lb
force.
Vector lengths may be proportional either to the screen display or to
the dimensions of the model.
The length of the vector symbols is scaled. In this case, the vector that
represents the 1,000 lb force will be displayed as ten times the length
of the 100 lb force vector.
Vector lengths may be proportional either to the screen display or to
the dimensions of the model.
Scale Factor
Vector Coloring
Same for All
Vectors are shown in their actual direction in the colors specified in the
LBC/Elem. Properties dialog box.
Component
Colors
Select the display colors for vector components and the resultant
vector.
With this option you can reduce some screen clutter by displaying
only those vectors that are associated with values that meet some
boundary requirements.
Label Style
Label style refers to the display format of the numerical values attached to symbols. The range labels are
now styled independent from the plot's value labels. The range label color, font size, format (i.e. fixed,
exponential, integer) and number of significant digits can be controlled.
Label Format
Fixed
Exponential
Integer
Significant Figures
When using decimal or exponential format, you can specify the desired
number of significant figures either with the slider or by typing it in the
textbox.
402
Beam Display
This attribute controls the way beam elements of a mesh are displayed on the screen.
1D:Line
1D:Line + Offsets
Element shear centre axis and neutral axis are displayed as lines
including any offsets. The two axes are connected by a line at each end
of the beam. The neutral axis is designated by a marker at each end.
The default marker is a circle. The marker type and size can be
controlled by the Preferences>Graphics command.
2D:Mid-Span
2D:Mid-Span + Offsets
2D:Mid-Span + Offsets +
Equiv. I
404
2D:Mid-Span + Offsets +
Equiv. A
3D:Full Span
Beam section shape is displayed over the full span of elements. Offsets
are also drawn.
Notes:
In 3D options, the beam sections are rendered in the rendering style specified for the model
with the Display>Entity/Color/Label/Render command.
Equiv. I and Equiv A.: Displaying the Relative Size of a Beam:
The beam area (A) and two bending moments of inertia (Iyy, Izz) are used to determine an
equivalent rectangular bar section. The dimensions of the equivalent section are then used
to draw the section as a rectangular bar.
The "Equiv. A" and "Equiv. I" options indicate what property values are used to determine
the dimensions. "Equiv. A" uses only the area and ignores the moments of inertia. "Equiv.
I" uses the moments of inertia and the area if necessary.
"Equiv. A" Option. If the "Equiv. A" option is chosen, the technique for determining the
equivalent square bar dimension is based only on the area. The formula for the area of a
square section of width w is:
A = w2
Rule 1: Although it should not happen, if no area is input, no attempt will be made to
display an equivalent section.
Rule 2: If area is input, a square section will be drawn.
Example 1: A = 10
Use Rule 2
w = (10)1/2 = 3.162
"Equiv. I" Option. If the "Equiv. I" option is chosen, the technique for determining the
equivalent rectangular bar dimens ions is based on the moments of inertia and sometimes
406
the area. The well known formulea for area and bending moment of inertia for a
rectangular section of width w and height h are:
A = wh
Iyy = hw3/12
Izz = wh3/12
Since all 3 properties can only be satisfied by a given width and height if the properties are
indeed those of a rectangular section, additional rules must be applied.
Rule 1: Although it should not happen, if no area, Iyy or Izz is input, no attempt will be
made to display an equivalent section.
Rule 2: If only area is input, a square section will be drawn as with the "EquivA" option.
Rule 3: If both Iyy and Izz are input, a height and width that yield the input Iyy and Izz will
be computed. The area will be ignored.
Rule 4: If only Iyy or Izz and the area is input, a height and width that yield the input Iyy or
Izz and area will be computed.
Rule 5: Although it should not happen, if only Iyy or Izz are input, a square section that
yields the input Iyy or Izz will be computed.
Example 1: A = 10, Iyy and Izz undefined
Use Rule 2
w = h = (10)1/2 = 3.162
Example 2: A = 10, Iyy = 15, Izz = 30
Use Rule 3
Use Rule 4
Use Rule 5
Display>Named Attributes
Use the Display>Named Attributes command to create, rename, or delete a unique set of display
attributes that you wish to recall during other work sessions with the current model.
Lists the existing attributes set names. Two default sets, general and
simple already exist. After you create a new set, its name will appear
in this area. Pick the attribute set you want to use.
Current/New Set
If you pick an existing set, its name will appear here. To crate a new
Named Attribute set:
Delete the name in this textbox
Enter a new name
Press Create
Use various Display menu functions to select the attributes you
want to include in the set. All selections will be applied to the new
attribute set.
Rename
Delete
408
In the Display>Coordinate Frames dialog box you can select one or more previously defined local
coordinate frames for posting.
Post/Unpost Coordinate
Frame(s)
Lists the names and IDs of currently defined coordinate frames. Select
the coordinate frame you want to display, or post. For multiple
selections, hold down the Shift key to pick names listed consecutively,
or the Ctrl key to pick non-consecutive names.
Post/Unpost All
Select Coordinate Frame(s) Provides another way of selecting one or more coordinate frames for
posting. Type the ID of the coordinate frame or pick it with the cursor.
Use the Shift key for multiple selection.
Display>Titles 409
Adding Text to Viewports
Display>Titles
With the Display>Titles command you can create and modify titles and other text displayed in a
viewport.
Post/Unpost Titles
Lists defined titles. To insert existing text into the viewport, select the
text you want then pick the viewport in which it will be displayed. The
text will be placed at the upper left portion of the viewport. You can
drag it to any other part of the viewport, as long as the Titles dialog
box is on the screen.
Text cannot be dragged outside the viewport.
Target Title
This textbox will contain the text you want to create/insert or edit.
410
Display>Titles
Automatically displays the new text you typed as soon as you select
Create or press the Enter key.
Create
desired location.
Rename
Delete
Title Color
Assigns a color to the new text string. This selection will not affect the
titles already on the screen.
Font Size
Assigns a font size to the new text that you are creating. This selection
will not affect the titles already on the screen.
Display>Spectrums 411
Creating and Managing Spectrums
Display>Spectrums
With the Display>Spectrums command you can define new spectrums or modify existing ones for
displaying analysis results.
412
Display>Spectrums
Current Spectrum
Lists the names of all spectrums defined in the database and highlights
the currently used spectrum. Patran software comes with several
predefined spectrums.
Create
Number of Colors
Specifies the number of colors in the new spectrum; this number must
be between 3 and 16.
Because the minimum number of subranges is 2, the minimum number
of colors in a spectrum is 3 (number of subranges +1).
Note that after a spectrum has been created, the number of colors
cannot be modified.
Spectrum Attributes
Continuous Color
Interpolation Factor
The left-hand column is for defining the new spectrum, the right-hand
column is the standard color table. To change the definition of a color
button:
In the Spectrum column, pick the button you want to modify
In the Color Table, pick the color for the redefined spectrum color
Repeat for all colors you want to change.
Display>Ranges 413
Defining Ranges and Sub-ranges for Results Display
Display>Ranges
All of the data entered on the Range form is now stored in the Patran database. This is most useful for
customizing the range labels and for defining ranges that automatically update to fit the current results
data being plotted. You can choose from several different methods to generate the range intervals. Your
method choices and all associated data are stored in the Patran database. The results plotting tool then
uses these setting to regenerate the range intervals based on the current results data and the Method and
parameters you defined for the range.
The Display Ranges form shown below allows you to create and manage named range definitions that
associate numerical intervals to the colors of the current spectrum and are used to color code data in a
plot. The range labels are now styled independent from the plot's value labels. The range label color, font
size, format (i.e. fixed, exponential, integer) and number of significant digits can be controlled.
414
Display>Ranges
The options listed in the Action pull down menu located at the upper left corner of the Ranges form allow
you to set the forms operational mode. The operations are Create, Copy, Modify, Assign to Viewport, and
Delete.
Create allows you to create a new range definition.
Copy allows you to make a copy of an existing range definition, with a new name. This copy can
Viewport.
Display>Ranges 415
Defining Ranges and Sub-ranges for Results Display
Delete allows you to delete one or more existing range definitions. Each Action option is fully
Range Names
The options located in the Range Names frame allow you to specify
the name of the new range. You can either enter a new name into the
New Range name edit box or select an existing range name by
pressing the Existing Ranges button. If you select an existing range
name the Ranges form will be updated to show the definition of the
range you selected. This method us typically selected if you want to
use an existing range as the starting point for your new range creation.
You will need to change the selected range name if you do not want
the exiting range definition to be over written.
416
Display>Ranges
Data Methods
Data Methods define the algorithm that you would like to use to create
the range intervals.
Algorithms
Display>Ranges 417
Defining Ranges and Sub-ranges for Results Display
Delta: The Delta method requires you to enter the Number of Subranges, Start, and Delta values. The new range intervals will be created
beginning at the Start Value, having subinterval lengths of Delta size,
and will extend from the Start Value to an end value defined by the
product of the number of intervals and Delta length.
Cluster: Range intervals can be created using a Cluster Algorithm.
The steps the algorithm performs are described below:
1) The data is sorted in ascending order.
2) Starting with the minimum value the distance between it and the
next value is compared to the current Bin Size. The units of the Bin
Size and distance values are defined by the Bin Method, which can be
set to either Percent or Delta value units. If the distance is less than or
equal to the Bin Size the second value is contained in the first range
interval. If the distance is larger than the Bin Size the data value
defines the first data value to be included in the next range interval.
Step 2 is repeated using the initial value included in the new range
subinterval as the value to be compared with values that are greater
than it. This process stops when either the last data value is compared
and included in a range interval or the number of intervals exceeds the
Number of Sub-ranges values set by the user. If the number of subranges exceeds the Number of Sub-ranges than the process exits if
Failure Recovery is set to None.
If the Failure Recovery is set to Revert to Auto than the Number of
Sub-ranges is automatically increased to the number of sub-ranges
that are needed to map the data set into cluster sub-intervals.
418
Display>Ranges
Display>Ranges 419
Defining Ranges and Sub-ranges for Results Display
The Auto, Delta, and Delta Log Data Methods Algorithms allow you
to define Range Thresholds. Thresholding allows you to manually
define the size of the upper and lower range intervals. The remaining
intervals are located between these and defined by the Data Method
Algorithm you chose to use. A typical use of Thresholding is to
temporarily redefine the range to focus on a subset of result values to
determine where these occur with in the simulation model. The upper
and lower threshold values can be defined entering a result value or a
percent value. If a result value is entered then the lower and upper
intervals will be defined to have a length of minimum result value to
lower value and upper value to maximum result value respectively.
The Use Percentages toggle allows you to define the thresholds in
terms of the interval between the lower and upper range values before
thresholding. Negative Percent Values produce lower thresholds
below the lower range value. Percent Values greater than 100%
produce threshold values above the upper range value. Percent values
between 0% and 100% produce threshold values between the lower
and upper range values.
420
Display>Ranges
Attributes
Allow Overwrite: If turned off this option will not allow the ranges
definition to be modified when attributes of a tool that uses it are
changed. This is to prevent accidental overwriting of your range by an
auto-ranging result plot.
Force Result Update: This option must be used in conjunction with
the Allow Overwrite option. It causes the range definition to be
modified if the results value associated to a plot that uses the range is
changed. This toggle causes the range intervals to be recalculated
every time the range is used. It does not work in conjunction with the
Manual Data Method. For the other Data Methods (Auto, Delta,
Cluster and Delta Log) the Data Method, relevant data values and
thresholding settings have been saved in the Patran database. These
setting will be used to automatically regenerate the range intervals
based on the result data values being plotted each time.
Post When Used: This option causes the range to be posted to the
Viewport if a results tool that is posted in a Viewport references it.
Display>Ranges 421
Defining Ranges and Sub-ranges for Results Display
General Information
Concerning Range Labels
You can now customize Range labels. You can now control labels for
values inside and outside the range as well as labels for values that fall
with in the maximum to minimum range bounds but do not map to an
interval within the range. Any combination of these labels can be
toggled on/off. Range labels can now include prefix and suffix text
that can be applied to all subinterval labels. Custom labels can be
defined for any label by pressing in its Custom button. Once this is
done the label becomes editable by the user. The following sections
describe the four sections of the Range form that contain the range
label controls offered to the user.
422
Display>Ranges
Label Display
Label Display allows you to control the display of the To, Middle, and
From labels of each interval with in the range. For the Middle label
you can define a tolerance style format using the Tolerance option.
The choices of Tolerance are described below:
None: Standard label formatting is used.
+/- Delta: The label will appear as the middle value plus the value if
added and subtracted from the middle value would derive the
intervals From and To values respectively.
+/- Delta: The label will appear as the middle value plus a percent of
the middle value that if it were added or subtracted from the middle
would derive the intervals From and To values respectively.
From:To This option allows you to label the interval at its middle
location with the From and To values that define the extent of the
interval.
When the Use All Custom Labels button is pressed, labels that you
have not customized (i.e. the Custom button for the label is depressed)
will be turned on regardless of the state of its To/Middle/From toggle
button that globally turns on/off the labels at these range interval
positions.
Display>Ranges 423
Defining Ranges and Sub-ranges for Results Display
Label Controls
Reset All: If this button is pressed all the Custom buttons associated
to the labels will be turned off and the custom text you have entered
will be deleted.
Prefix/Suffix: If text is entered in these boxes it will globally appear
in the front and at the end of all labels that do not have their Custom
button turned on.
No Data: This edit box allows you to define text that will decorate the
range and spectrum interval used to show the regions of the model
where no analysis data is available.
Label Style
Label Style controls are used to define the format and color of the
range labels. The range labels are now styled independent from the
plots value labels. The range label color, font size, format (i.e. fixed,
exponential, integer) and number of significant digits can be
controlled.
424
Display>Ranges
No Matching Sub-range
The options included in this section of the form let you control a
special range interval that is used to represent result values that do not
belong to any of the range intervals. The various Use Sub-range
options are as follows.
Default: This option turns off the special No Matching Sub-range
interval. If results data exists that is not mapped to one of the range
intervals than the regions of the model that contain these values are
colored as follows. If the values exist beyond the ends of the range the
region of the model where these values exist is rendered with the end
spectrum color it exceeds. If the values are inside the minimum and
maximum bounds of the range than the no data color is used for model
rendering.
Start End: This options turns on the special No Matching Subrange interval. The Label edit box becomes active allowing you
define the label for this special range interval. If results data exists that
is not mapped to one of the range intervals than the regions of the
model that contain these values are colored as follows. If the values
exist beyond the ends of the range the region of the model where these
values exist is rendered with the end spectrum color it exceeds. If the
values are inside the minimum and maximum bounds of the range than
you are allowed to define the color that is used for their rendering.
First / Last / No Data: These options turn off the special No
Matching Sub-range interval. If results data exists that is not mapped
to one of the range intervals than the regions of the model that contain
these values are rendered with the first, last, or no data spectrum color
according to your selection of First, Last, or No Data.
Outside: This options turns on the special No Matching Sub-range
interval. The Label edit box becomes active allowing you define the
label for this special range interval. If results data exists that is not
mapped to one of the range intervals than the regions of the model that
contain these values are rendered with the color you have selected
Display>Ranges 425
Defining Ranges and Sub-ranges for Results Display
Copy
426
Display>Ranges
Assign to Viewport
Display>Ranges 427
Defining Ranges and Sub-ranges for Results Display
Delete
To delete an existing range definition just set the Ranges form Action
pull down option menu to Delete. Select the existing ranges you
would like to delete by first pressing the Existing Ranges button,
highlighting the range names you would like to delete, and then
pressing the Apply button at the bottom of the Existing Ranges form.
428
Display>Color Palette
Display>Color Palette
In the Display>Color Palette dialog box you can customize all colors used in the current database.
Lists the name of all Color Palettes that exist in the database and
highlights the currently used Color Palette. Patran provides the
following three default color tables: gray_scale, rgb_colortable and
standard_colortable.
Color Table
Displays the 16 colors of the current color palette. The color at the top
of the column determines the background color of viewport displays.
To change a color, click on the color chip then use one of the
modification methods to create the effect you want.
Lightness
Saturation
RGB
Use the slidebar to regulate the percentage of the red, green, and blue
contained in a color.
430
Display>Shading
Display>Shading
The Display>Shading command controls the way light interacts with surfaces displayed in shaded
rendering.
Display>Shading 431
Controlling the Appearance of Light on Surfaces
Texture
Transparency
Specular Reflection
Diffuse Reflection
Highlight Size
Specular Color
Specifies whether the color of the object or the color of the light source
will affect the color of the specular area.
432
Display>Light Source
Display>Light Source
With the Display>Light Source command you can create new light sources and control the light that
affects the shading of surfaces.
Lists all light sources defined in the database and highlights the
currently active (posted) light source(s). Pick the name of a light
source to post it. For multiple selections, hold down the Shift key to
pick consecutively listed items, use the Ctrl key for names not listed
consecutively.
Create
Delete
Direction
Displays the coordinates of the end point of the light direction vector.
Location
Displays the coordinates of the light source location (the start of the
light direction vector).
Color
Shows the color of light selected for the target light source.
Intensity
Controls the intensity of the light from low (0.0) to high (1.0).
434
Display>Light Source
Attenuation
10
Preferences
Preferences Commands
439
441
436
436
10.1
Analysis Codes
Analysis codes are the finite element programs you use to perform the analysis. Possible analysis codes
include MSC Nastran (default), MSC.Marc, MSC.Dytran, MSC.Patran Thermal, MSC Sinda,
ABAQUS, ANSYS 5, LS-DYNA3D, PAMCRASH, SAMCEF, PATRAN 2 NF. The analysis code you
pick here depends on what is available at your site. For more information, see the relevant preference
guide.
Preference Guides
Patran Interface to ABAQUS
Preference Guide
Finite element analysis codes have their own specific way of defining components of a FEM model and
of formatting analysis input and output data. Therefore, the code you select will also determine the
following:
available analysis type
element type, shape, and property definitions
Analysis Types
The analysis code you selected also determines which kind of finite element analysis can be accessed.
Structural, thermal, and fluid dynamics analyses are the most frequently used types available for most
analysis code applications.
Changing Analysis Codes
You can change the analysis code preference at any time during the modeling process. Keep in mind that
changing the analysis code changes; code-specific forms in the Analysis application, available analysis
types, element types, and element and material property definitions. If you decide to change the analysis
code, Patran will transfer as much code-specific data as possible to the new code according to the
Preference Mapping option you select.
Preference Mapping
Patran offers three mapping options each providing a unique level of conversion and user control.
1. Mapping Functions - Running a series of PCL commands, you can produce customized mapping
tables that you use when switching from one analysis code to another. These mapping tables
precisely define how element properties and material properties are translated from one particular
code to another.
2. Legacy Mapping - This option employs default mapping tables such that the most obvious data is
mapped to the new code and the more complex data is left untouched. Earlier versions of Patran
were limited to this default mapping.
3. No Mapping - Using this option the database remains unchanged when switching from one
analysis code to another. No mapping of any kind is done. The advantage to this option is that you
can change preferences, perhaps just to see what capabilities a code has, without changing the
model.
The mapping option you select will depend on the issues pertinent to your model and to the analysis
codes. For example: 1) do the fem entities (nodes, elements, mpcs) map over correctly; 2) are there
equivalent loads and boundary conditions, contact, material and element properties; 3) are there
equivalent analysis procedures, and will they convert correctly when you change the analysis preference?
Model Tolerance
Tolerance specifies the maximum distance within which two like entities (e.g., nodes), are said to be
coincident. Tolerance, being a global parameter, remains valid for both geometric and FEM construction.
The same tolerance value will apply to geometric entities imported in a CAD database.
438
Model tolerance may be specified as an absolute number (normally 0.005) or it may be based on the
maximum model size. In the latter case, the recommended tolerance is 0.05% of the expected maximum
model size. However, you may specify a different tolerance depending on how accurately the imported
geometry was constructed.
Warning Messages
Occasionally Patran issues a warning in conjunction with a command or entity selection. Warning
messages are output to the history window and to the session file and, by default, are also shown on the
screen. You may choose to sound just a warning bell rather than the screen display, or omit warning
notifications altogether.
Hardware Rendering
If your system is set up to access a hardware graphics device for graphics displays (The settings.pcl file,
47) you can choose to render shaded images through that device. Hardware generation of images
typically takes less time but, in general, software rendering is more accurate and even offers more display
options (e.g., texturing effects).
Representing Geometry
In earlier versions of Patran (e.g., PATRAN 2), curves, surfaces, and solids were created as parametric
cubic, bicubic, and tricubic geometry. An option in the Preferences Geometry dialog box enables you to
create parametric cubic geometry that can be exported to a neutral file.
Model Units
The vehicle that Patran uses to create solid geometry is a modeler named Parasolid. Parasolid assumes
model units in meters. Although Patran is unitless (dimensions can be interpreted in any unit system),
because of Parasolid, a scale factor is used when creating solid geometry ( see Parasolid Model Units,
173). The default scale factor is set in the Preferences menu.
10.2
Preferences
Analysis...
Global...
Graphics...
Mouse...
Picking...
Report...
Geometry...
Finite Element...
440
The Preferences menu functionalities are described below in the order in which they appear.
Analysis...
Selects the finite element analysis code and the type of analysis that
will be performed.
This form also specifies code-dependent suffixes attached to the
names of analysis input and output (results) files. These attachments
are required for identification by Patran file management and by
certain analysis code interfaces.
Global...
conditions exist.
Designates a previously defined coordinate frame as default for
model construction .
Selects the default construction plane within the specified
coordinate frame.
Sets the global tolerance value.
Graphics...
of shaded images.
Defines highlight colors to be used to identify entities selected for
Picking...
Report...
Geometry...
Finite Element...
Preferences>Analysis 441
Preferences Commands
10.3
Preferences Commands
The following is a detailed description of the commands and dialog boxes that manage global
preferences.
Preferences>Analysis
With the Preferences>Analysis command you specify the analysis code you will use to run the finite
element analysis calculations and select the kind of analysis you want to perform. Setting the Analysis
Preference activates code-specific definitions in the Patran database.
Analysis Code
Analysis Type
442
Preferences>Analysis
Displays the file name extension used by the analysis code to identify
a finite element input data file.
Displays the file name extension used by the analysis code to identify
a finite element result (output) data file.
Preferences>Analysis 443
Selecting/Changing the Analysis Code and Type
Preference Mapping
Mapping Functions
Using PCL generated mapping tables, you can convert many of the
complex parts of the code-specific model from one analysis code to
another. In particular, mapping functions allow for the mapping of
element and material properties.
Mapping functions do not include converting contact conditions or
analysis procedures. These parameters change so extensively from
one code to another that generic mapping procedures are not
possible. It is possible to write your own specific PCL functions that
would map contact conditions or analysis procedures from one
specific code to another specific code. These PCL functions can
then be attached in the mapping procedure.
444
Preferences>Analysis
Legacy Mapping
No Mapping
Mapping Functions
Patran uses mapping tables to convert code-specific definitions from one analysis code to another. These
mapping tables are specific to the old and new analysis codes and separate mapping tables are required
for material properties and element properties.
A limited number of mapping tables are included in the Patran delivery. These mapping tables have been
generated as part of included example problems or generated to map previously supported analysis
solvers over to currently supported solvers. For example, the mapping tables for mapping from the MSC
Nastran Preference to the MSC.Marc Preference are included and an example illustrates the full model
conversion between these solvers. In addition, you can access the MSC website under Product Updates
for the latest information on mapping tables.
Material property mapping tables and element property mapping tables are generated through separate
procedures that involve using spreadsheets to define translation instructions, converting spreadsheets to
PCL functions, then compiling those into the system to be executed during a preference change.
Once these mapping tables are generated they can be used repeatedly to switch between analysis codes.
Important: rocedure. Information in the Patran database that pertains to the old analysis code is
overwritten with information for the new analysis code.
Property Set Spreadsheets
The Property Set Spreadsheet is composed of four sections. The first section defines the analysis code
and type. The second section is a list of all the property sets defined for the specified analysis code and
type. Every row represents one of the possible Element Property Forms. The third section is a list of all
property words and IDs used for the given analysis code and type as well as whether the word is required,
the default type, possible types and allowable values. The last section shows the valid property words for
each property set.
Property set spreadsheets are tab-delimited files. You can open them in Excel to view and edit them.
There are two points to remember. First, the fields should be defined as text in order to keep large
Preferences>Analysis 445
Selecting/Changing the Analysis Code and Type
numbers from converting incorrectly. When opening the text file, Excel presents a form for converting
the data. Verify that Delimited is selected. Then hit Next and verify that Tab is the selected
delimiter. Then hit Next once more, select all the columns and choose Text as the Data Format.
Then hit Finish. The second point to remember is that spreadsheets read by Patran need to be tab
delimited text files. Therefore, when saved out of Excel, they need to be saved as text files rather than
Excel files. (The .xls file extension used above is just a convenient way to launch Excel.)
446
Preferences>Analysis
Preferences>Analysis 447
Selecting/Changing the Analysis Code and Type
4.
448
Preferences>Analysis
6.
Preferences>Analysis 449
Selecting/Changing the Analysis Code and Type
450
Preferences>Analysis
Preferences>Analysis 451
Selecting/Changing the Analysis Code and Type
5.
452
Preferences>Analysis
7.
The property mapping logic currently does not consider topology, linearity and directionality data.
Neither does it verify that materials mapped to laminate property sets are laminate materials. Further,
only the first DOF set value for each set of geometric, condensation, laminate, formulation options is
Preferences>Analysis 453
Selecting/Changing the Analysis Code and Type
considered in the Property Set Spreadsheets. This could pose some problems for logic accessing the
mapped element property set data, such as forward translators.
Invoking the PCL Function for Preference Switching
During a preference change, analysis specific functions are called. Two arguments are passed, the current
action ("add" or "remove") and the target Analysis Type. Consider a preference change from MSC
Nastran to MSC.Marc where the Analysis Type is "Structural." The following two preference functions
are called:
mscnastran_pref_control ( "remove", "structural" )
mscmarc_pref_control ( "add", "structural" )
Note that by convention, the function name is "codename_pref_control". Also note that this is a function
without a class, which means that you can potentially replace it with your own function.
If you have selected "Mapping Functions" in the Analysis Preference Panel, the MSC supplied
preferences make the following call during the "add" action.
mscmarc_mapping.go ( old_code, old_type, new_code, new_type )
In general, this class then calls MSC supplied mapping functions. However, you can override the
supplied mapping functions and provide your own.
For example, in the case of a preference change from MSC Nastran to MSC.Marc with "Mapping
Functions" chosen, the normal flow is
mscmarc_pref_control( "add", "structural" )
mscmarc_mapping.go ( "MSC Nastran", "Structural", "MSC.Marc",
"Structural" )
map_to_mscmarc.from_mscnastran ( "MSC Nastran", "Structural",
"MSC.Marc", "Structural" )
map_mscnastran_to_mscmarc.structural_materials ()
map_mscnastran_to_mscmarc.structural_elmt_props ()
map_mscnastran_to_mscmarc.structural_lbcs ()
map_mscnastran_to_mscmarc.structural_mpcs ()
map_mscnastran_to_mscmarc.structural_job_definitions ()
If you want to provide your own set of mapping functions, perhaps because none have been supplied by
MSC, that can be accomplished by telling the preference mapping class which function to use. This is
done with the following call
mscmarc_mapping.set_mapping_function ( "mscnastran",
"my_mapping_class.go" )
In this case, instead of calling "map_to_mscmarc.from_mscnastran", the "mscmarc_mapping.go"
function will call
my_mapping_class.go ( "MSC Nastran", "Structural", "MSC.Marc",
"Structural" )
Knowing the specific function calls that are made by the MSC supplied mapping functions, you can
augment or completely rewrite the mapping behavior. For example, if only the LBC's needed modifying,
454
Preferences>Analysis
your function "my_mapping_class.go" could call the "normal" mapping functions for materials, element
properties, mpcs and job definitions. And call your own function for LBCs. Thus,
my_mapping_class.go
map_mscnastran_to_mscmarc.structural_materials ( )
map_mscnastran_to_mscmarc.structural_elmt_props ( )
map_mscnastran_to_mscmarc.structural_mpcs ( )
map_mscnastran_to_mscmarc.structural_job_definitions ( )
my_mapping_class.do_the_lbcs ( )
The logical place to make the call to "mscmarc_mapping.set_mapping_function" would be in the
p3epilog.pcl file. But this call can be made anytime before a preference change is made. In addition, the
user would have to compile and add their plb to the system, again, most likely in the p3epilog file.
A little used but useful place to install this code on an enterprise basis would be in the "init.pcl" function
in "p3_home", probably just before the call to "p3epilog.pcl".
Using the General Function
Lets return to our example of mapping Abaqus property sets to MSC.Marc. Assume that the general
function is named map_abaqus_elmt_props_to_mscmarc. (This was defined in the Property Set
Mapping Spreadsheet.) Recall that a Point Mass property set maps to a Mass (MASS) property
set. Say an Initial Property Set Function Tag of Point Mass was specified in the Property Mapping
Spreadsheet for this source/destination property set combination. When an Abaqus Point Mass
property set is encountered during the mapping process, the following call is made:
map_abaqus_elmt_props_to_mscmarc ( Start Region Mapping,
Point Mass )
Also, lets assume we have defined a tag, Translational Mass for the Abaqus property word Mass
Magnitude. If the mapping process encounters a Point Mass property set with a Mass Magnitude
property word, then the mapping process first maps the word to the specified destination word (if any)
and then makes the following call:
map_abaqus_elmt_props_to_mscmarc ( Map Property Word,
Translational Mass )
As you can see the general function takes two arguments, a state and a tag. There are five possible calls:
Start Property Set Mapping, Blank Tag
Start Region Mapping, Initial Prop Set Function Tag
Map Property Word, Property Word Function Tag
End Region Mapping, Final Prop Set Function Tag
End Property Set Mapping, Blank Tag
The suggested structure of the general function is a switch on the state with switches on the specific tags.
For example:
FUNCTION general_function ( state, tag )
Preferences>Analysis 455
Selecting/Changing the Analysis Code and Type
STRING state[ ]
STRING tag[ ]
SWITCH ( state )
CASE ( Map Property Word )
CASE ( Start Region Set Mapping )
CASE ( End Region Set Mapping )
CASE ( Start Property Set Mapping )
CASE ( End Property Set Mapping )
END SWITCH
END FUNCTION
Now lets do something practical. The Abaqus Point Mass property set allows a single quantity for
Mass Magnitude. The MSC.Marc Mass (MASS) property set however defines mass in three
directions, Transl Inertia, X, Transl Inertia, Y and Transl Inertia, Z. Clearly when we map from
Abaqus to MSC.Marc, we want any Mass Magnitude to map to each of the three MSC.Marc property
words. Rather than handling this complexity in the Property Mapping Spreadsheet, we do it with the
general function.
Assume we have created a Property Word Function Tag for the Mass Magnitude property word in
the Abaqus Point Mass property set as described above. Our general function might look like the
following.
FUNCTION map_abaqus_elmt_props_to_mscmarc
STRING state[ ]
STRING tag[ ]
( state, tag )
INTEGER status
REAL mass
STRING word[32]
SWITCH ( state )
CASE ( Map Property Word )
SWITCH ( tag )
CASE ( Translational Mass )
$Recover the current Mass Magnitude value. Were
$assuming it is a real value and not a field.
word = "Mass Magnitude"
status = map_properties.get_active_src_word_rval ( word, mass,
datatype,
field_id )
$status = 0, if word is valid, exists and defined
$status = 1, if word is valid, exists, but is not a real
$status = 2, if word is valid but doesnt exist
$status = 3, if word is not valid for current property set
$status = 4, if a property set conversion is not active
IF( status == 0 ) THEN
$Create three MSC.Marc words using the Abaqus value
$Note that word definitions have to be specified exactly
$and they have to be valid for the destination property set.
456
Preferences>Analysis
Preferences>Global 457
Controlling Global Operational Parameters
Preferences>Global
458
Preferences>Global
Parameters defined in the Global Preferences dialog box affect operational characteristics and
geometric construction.
Session File
Selects whether or not a session file will be saved. Options are to save
after Patran completes, delete after Patran completes, or to be
prompted as to whether or not to save the session file.
Preferences>Global 459
Controlling Global Operational Parameters
Picks the type of feedback you receive whenever Patran needs to issue
a warning.
Default Construction Plane Specifies the default construction plane in the selected coordinate
frame.
Global Model Tolerance
Defines the maximum distance within which two like entities are said
to be coincident (default is 0.005).
460
Preferences>Graphics
Preferences>Graphics
In the Graphics Preferences dialog box you can stipulate certain view settings, specify the colors used
for highlighting, and select the shape, color, and size of markers, used in some geometric and FEM
procedures (e.g., node equivalencing).
If ON, automatically fits the view whenever new entities are created
and they fall outside the viewport.
Preferences>Graphics 461
Specifying Graphic Display Parameters
If ON, sets the background color for all existing viewports to the
Background Color setting.
Background Effects...
XY Color
All Existing XY Windows If ON, sets the background color for all existing XY viewports to the
Background Color setting.
Disable Auto Updates
If ON, the graphics display does not update after each operation. This
technique is particularly useful at times when you are performing a
number of operations but do not want to see the results of each interim
step.
Highlight Colors
Primary Color
Assigns the color that will be used for highlighting entities selected for
an operation.
Secondary Color
Error Color
462
Preferences>Graphics
Marker Options
Model Tree
Configuration...
Preferences>Mouse 463
Programming the Mouse for View Transformations
Preferences>Mouse
With the Mouse Preferences options you can program the middle mouse button to perform incremental
view transformation functions.
464
Preferences>Mouse
Pan X/Y
Zoom
Transform in Wireframe
Mouse Tracking
Spin Model
With the mouse button map set to one of the rotate functions, and this
toggle turned ON, you can spin the view of the model. When you press
the middle mouse button, the view will transform as expected, but you
can make it spin by releasing the button. The speed of rotation is
proportional to the speed with which you release the button.
Transformation Options
Brings up a subordinate dialog box in which you can set the rotation
angle increment, pan factor and zoom factor.
Preferences>Mouse 465
Programming the Mouse for View Transformations
Rotation
Model/Screen Relative
Pan Factor
Displays the panning rate. Each mouse movement will move the view
of the model by that increment.
Zoom Factor
Displays the zooming rate. Each mouse movement will zoom the view
of the model at that rate.
466
Preferences>Picking
Preferences>Picking
Many geometric and finite element operations require that you select one or several entities as the object
of some action. The Picking Preferences dialog box contains a variety of options for picking entities
with the mouse (for more information on interactive screen picking, see Screen Picking, 33).
Note:
The selections you make in this dialog box will not take effect immediately. After selecting
the parameters, exit Patran. The choices you made will be saved in a file (settings.pcl) that
will activate the new parameter settings when you restart Patran.
Preferences>Picking 467
Parameters of Interactive Screen Picking
Single Picking
Centroid
Picks the entity whose centroid is closest to the center of a pick box.
Entity
Rectangle/Polygon Picking
(Multiple)
These options apply when you select a number of entities at the same
time.
468
Preferences>Picking
Enclose centroid
Cycle picking form
If ON, the Select Menu will contain the icons to add, reject, and
replace a selection whenever a screen picking option is evoked.
Preselection Settings
Label Highlighting
Entity Highlighting
Controls the size of the marker that is highlighted when the cursor
passes over a point or a node.
Preferences>Report 469
Formats of Numerical Entries in Analysis Result Reports
Preferences>Report
The Preferences>Report command controls the format of numerical entries in reports that output finite
element analysis results.
Real Numbers
Floating Point
Scientific Notation
Field Width
Selects the width of the numeric field. This size must accommodate
all digits and the decimal point. In scientific notation the field width
takes on the maximum value.
Number of Decimals
Integers
Spacing
470
Preferences>Geometry
Preferences>Geometry
With the Geometry Preferences options you can specify the way parameterized curves and surfaces are
represented in the database. These preferences apply to geometry imported from an external source, as
well as to geometry created in the Patran system.
Import to Parametrized
Solid
Preferences>Geometry 471
Parameters for Representing Geometric Entities
With the options in this category, you can select the method by which
left-handed parameterization created by some hyperpatch construct or
transform methods is changed to right-handed parameterization.
This selection is important only when you are running session files (see
Session File, 46), because the hyperpatch origin location must be set
according to whether the session file came from Patran or PATRAN 2.
Patran
PATRAN 2
NURBS Accelerator
472
Preferences>Geometry
Preferences>Finite Element
474
Preferences>Finite Element
Setting FEM Parameters
Several parameters are defined in the Preferences>FEM dialog box. They are described in the table
below.
Controls the angle that determines whether a node will snap to a vertex
where the slope of a composite edge changes. If the angle of the slope
is greater than the specified edge snap angle, a node will snap to the
vertex when you create a mesh seed or a mesh. If, however, the angle
of the slope is less than the snap angle, no node will snap to this vertex.
Edge Snap Angle = 30o
You may realize that you need to change the Node/Edge Snap Angle
value after you have created a mesh seed on a composite edge and
discovered that no control point was placed on the vertex. If it is
important that a node be located there, you can invoke the
Preferences>FEM command and change the Node/Edge Snap Angle
so that it becomes less than the slope angle. When you press the Apply
button, the following will appear:
Select Yes and a mesh seed control point will snap to the vertex and the
mesh seed will be adjusted along the entire edge.
DFEM Field Equivalence
Options
Specifies which values of discrete FEM fields, that associate loads and
boundary conditions (LBCs) with nodes, will be associated with a
node that survived after coincident nodes have been equivalenced in
the finite element model.
476
Preferences>Finite Element
Setting FEM Parameters
Displace
Use Retained--use the value associated with the node retained after
equivalencing.
Add--use the sum of the values associated with each of the
equivalenced nodes.
Use Deleted--use the value associated with the node that was
Presents the same options for associating vector (e.g., force) values
with the node that survived the equivalencing process
Scalar
In addition to those already seen for vector field values, the option
exists to use the average of the two scalar values associated to the
equivalenced nodes.
Preference Specific Verify
Geometry/FEM LBC
Association
478
Preferences>Finite Element
Setting FEM Parameters
Check Adjacent Geometry This checkbox specifies whether adjacent geometry is checked when
associating LBCs to FEM that were applied to Geometry. Patran
always uses the node to geometry association determined by the
mesher to associate LBCs to element faces and edges. When adjacent
solids or surfaces have overlapping or duplicate faces or edges, an
element may be associated to one piece of geometry but some of its
nodes may be associated to an adjacent geometry. When this check is
turned on, element nodes associated to the adjacent geometry are
included in the LBC evaluation.
By default, adjacent geometry checking is turned on. The user can
change the default value to off by placing the following in the
settings.pcl file:pref_env_set_logical(
"fem_geo_lbc_adj_geo_check", FALSE )
Connection Elements
Preferences>Main Form
On UNIX platforms, the Preferences>Main Form options enable you to change the layout and
appearance of the Main form. The changes will not take effect until you restart Patran
Adds latest history line to be written at top of history list (history lines
scroll down). Defaults ON and allows last history line to be viewed
above viewport in default orientation. If using history list to enter PCL
commands or debug PCL functions, you may want to turn this OFF.
Latest history line will be displayed at bottom of history window and
will scroll up.
Allows any changes made during the current session to the vertical
height of the main form to be saved between sessions (Default is ON).
If turned OFF, the next session will startup ignoring any main form
height changes made during the present session.
480
Preferences>Main Form
11
Tools
482
Tools>MSC.Fatigue
Tools>Laminate Modeler
Tools>Random Analysis
491
Tools>Analysis Manager
492
Tools>List
Tools>Mass Properties
Tools>Beam Library
Tools>Regions
Tools>Modeling
Tools>Design Studies
Tools>Results
Tools>Pre-Release
488
489
493
503
518
537
542
661
672
727
726
490
482
11.1
Laminate Modeler
(p. 489)
Enterprise MVision...
(p. 490)
Random Analysis...
(p. 491)
Analysis Manager...
(p. 492)
List...
Create... / Boolean...
(p. 493)
Brings up a utility to create and manipulate entity lists with which you
can reference a number of entities for input in commands that
accommodate multiple entity selection. A boolean operation allows
for combining multiple lists.
Mass Properties...
(p. 503)
Beam Library...
(p. 518)
Regions...
(p. 537)
Modeling...(p. 542)
This cascade menu item lists a number of utilities available for aiding
in the modeling process. These are listed below.
Results...
(p. 672)
This cascade menu item lists a number of utilities available for aiding
in the post-processing of results data. These are listed below.
Pre Release
(p. 727)
Provides access to pre-release capabilities that have not yet been fully
validated.
Properties Import...
(p. 547)
Load Tools...
(p. 552)
484
Model Variables...
(p. 567)
Mass Property
Management...
(p. 585)
Tool to help engineers estimate the weight of a structure from its finite
element model and to fine tune the model weight distribution by
specifying mass factors for the model to modify its weight, and then
adding quantities of element nonstructural mass based on the factors.
Assembly...
(p. 585)
Experimental Data
Fitting...
(p. 644)
Bolt Preload...
(p. 647)
Easily create simulated bolts with this tool for use in MSC Nastran and
MSC.Marc Analysis Preferences only.
Rotor Dynamics...
(p. 650)
Rebar Definitions...
(p. 652)
NSM Properties...
(p. 651)
Feature Recognition...
(p. 655)
Contact Bodies/Pairs...
(p. 657)
Plots the bar end loads as calculated from the grid point and element
forces.
Max/Min Sorting...
(p. 684)
Permits sorting of results across multiple load cases based on a userspecified criteria.
Shear Panel Plots can be displayed either as the shear flow along all
four edges or the element average shear flow.
Explore...
(p. 694)
Results Templates...
(p. 714)
Test Correlation...
(p. 725)
486
11.2
Tools Commands
The following are detailed descriptions of the commands and dialog boxes that are referenced in the
Tools menu or references to the application documentation.
1. Tools>MSC.Fatigue
488
2. Tools>Laminate Modeler
489
491
5. Tools>Analysis Manager
492
6. Tools>List
490
493
7. Tools>List>Create
495
8. Tools>List>Boolean
501
9. Tools>Mass Properties
10. Tools>Beam Library
11. Tools>Regions
12. Tools>Modeling
503
518
537
542
543
547
552
567
579
581
585
602
647
650
651
652
655
671
672
657
662
638
644
673
677
684
613
694
695
39. Tools>Results>Templates
714
727
691
726
725
488
Tools>MSC.Fatigue
Tools>MSC.Fatigue
MSC.Fatigue
The MSC.Fatigue software application integrates finite element analysis and fatigue life estimation
techniques to perform fatigue calculations. Analysis results output includes full-color life contour plots
to provide rapid assessment of fatigue in critical areas. This selection only appears in the Tools pull down
menu if a license is available and the software is installed.
Selecting the Main Interface option will bring up the MSC.Fatigue user interface form. From this form
you can setup, submit, monitor, or abort a MSC.Fatigue analysis or access any of the various
MSC.Fatigue modules such as the Materials Database Manager (PFMAT) or Time History Database
Manager (PTIME). MSC.Fatigue enables you to perform subsequent fatigue calculations based on the
stress or strain results once you have completed a finite element analysis. Three standard fatigue analyses
are contained within the MSC.Fatigue module: Total life analysis based on the nominal stress life (S-N)
method, Crack initiation based on the local strain method, and Crack Growth based on linear elastic
fracture mechanics.
Complete documentation can be found in MSC.Fatigue Users Guide. Also see the MSC.Fatigue
Quickstart Guide.
Tools>Laminate Modeler
Laminate Modeler
The MSC.Laminate Modeler application aids the design, analysis, and manufacture of laminated
composite structures. It integrates various methods of simulating the manufacturing process (including
draping of fabrics) with simplified, more efficient ways of storing and manipulating data required for the
analysis of composite materials. This selection appears only if a license is available.
MSC.Laminate Modeler is a Patran module for aiding the design, analysis, and manufacture of laminated
composite structures. The functions available within MSC.Laminate Modeler allow you to visualize the
manufacturing process and estimate the quantity of material involved. Representative analysis models of
the component can be produced very rapidly to allow effective layup optimization. Finally, a ply book
and other manufacturing data can be produced.
Selecting Laminate Modeler from the Tools menu activates the Laminate Modeler module if installed and
licensed. For more information, see the MSC.Laminate Modeler Users Guide
490
Tools>Random Analysis
Random Analysis
Random Analysis is a random analysis software package used with MSC Nastran and Patran. It was
developed by field engineers at MSC Software to offer a fast, integrated random analysis solution and all
of Random Analysis capabilities and generated results are available from within the Patran environment.
To use this capability a software license must be available.
MSC.Random software technology is similar to the existing MSC Nastran random analysis capability. In
both packages, random analysis is treated as a data reduction procedure that is applied to frequency
response analysis, but with MSC Nastran, the output request for a random response can only be made
through the XYOUT module. This requires that you to prepare XYPLOT or XYPRINT entries for each
degree of freedom for nodal responses, and for each stress/force component for element responses. Even
for a small size model, you must prepare a large number of XYPLOT/XYPRINT entries. In addition, the
results that are calculated cannot be postprocessed from within Patran.
For more information on Random Analysis please see, Random Analysis (Ch. 13).
492
Tools>Analysis Manager
Managing Analysis Jobs
Tools>Analysis Manager
Analysis Manager
If installed and licensed, the Analysis Manager provides convenient and automatic submittal, monitoring,
control and general management of analysis jobs to local or remote networked systems. Primary benefits
of using the Analysis Manager are engineering productivity and efficient use of local and corporate
network-wide computing resources for finite element analysis.
The Analysis Manager has its own scheduling capability. If commercially available queueing software,
such as LSF (Load Sharing Facility) from Platform Computing Ltd. or NQS is available, then the
Analysis Manager can be configured to work closely with it.
Selecting Analysis Manager from the Tools menu activates the Analysis Manager module if licensed and
installed. For more information, see the Patran Reference Manual.
Tools>List 493
Entity List Operations
Tools>List
Lists
A list is a convenient way of referencing a number of entities for input in commands that accommodate
multiple entity selection. When you use a list, the listed entities are picked directly from the database,
rather than being cursor-selected in the graphics window.
Lists can be created of entities that either share some common attribute or are associated with a common
entity. For instance, an attribute-based list may contain elements that have the same material properties,
while an association-based list may be generated of nodes that are all located on the same edge.
An example where a list can be useful may be a finite element model in which you want to apply a nodal
displacement constraint to all nodes whose global x-coordinate is 2.0. Instead of picking a potentially
large number of nodes in the FEM application, you can first create a list to include the nodes that fit the
attribute criterion, then use the list for the constraint assignment.
Entity Types
Lists may contain either geometric or finite element entities.
Classification Methods
The criteria that determine an entitys inclusion in a list may be attribute or association.
Attribute
The Attribute method identifies a distinctive characteristic that is shared by all members of the list. In the
FEM application, a list of elements may be based on common element properties, material properties, or
analysis results (fringe values), and for a node list you can specify coordinate values as well as fringe
values. For a geometry list, on the other hand, you must cursor-select entities or enter their IDs, because
the list generator does not recognize any attributes that are common for geometric entities.
Association
With this method you can list a number of entities that are associated with one common entity or group.
For example, you may specify that the list include those geometric entities, e.g., points, that are located
at the same vertex, or on the same edge or face. The list of FEM entities, such as nodes, may be based
either on their association with a geometric entity (e.g., vertex) or a group, or with an FE entity, for
example an element edge.
Group Assignment
After you created a list, you can associate its members with an existing group or, alternately, assign them
to a newly created group.
494
Tools>List
Boolean Operations
You can create several lists and combine them, two at a time, into one comprehensive list, with one of
the Boolean operations:
Union--outputs a resultant list that contains all members of list A plus all members of list B.
Subtraction--outputs a resultant list obtained by subtracting the contents of one list from the
Intersection--outputs a resultant list obtained by finding members that are common to both list A
and list B.
Using Lists
List names are entered enclosed in single quotes (), because the list names (lista, listb, and listc) are
global PCL string variables and require special delimiters so that the List Processor can recognize them.
Tools>List>Create 495
Creating Lists
Tools>List>Create
Creating Lists
With the List>Create dialog box you establish a pick list of entities. The criteria for inclusion in the
list may be a common attribute that the entities possess (e.g., elements that have the same material
properties), or the association of the listed entities with one common entity (e.g., elements that are on the
same face).
Lists by Attributes
The nature of attributes that may be ascribed to entities depend primarily on whether they are geometric
or FEM entities.
Geometric Entities
For the purposes of lists, the only attribute of geometric entities is that they can be selected, either with
the cursor or by entering their names and ID numbers.
496
Tools>List>Create
Creating Lists
Model
Object
Method
Tools>List>Create 497
Creating Lists
Attribute
value or value range (e.g., elements with a von Mises stress result
value greater than 20,000psi.).
Property Set--entities are included if they share a common
property set.
Material--entities are included if they share the same material
property specifications.
Target List (A or B)
>
<
||
498
Tools>List>Create
Creating Lists
Tolerance
Enter a value (or accept the default) that determines how close the actual coordinate value or fringe value
must be to the specified range values so that the entity will be included in a list. For example, if the node
fringe value attribute is temperature, and the range is specified as F> 300 and Tol= 5, the list will include
all nodes for which the actual temperature result value was 295 degrees or higher.
Properties
If you are creating a list based on Property Set (element properties) or Material attributes, the dialog
box will contain the Existing Property Sets or Existing Materials textbox with the names of
previously defined element property sets or material properties. Pick the property set or material of
Tools>List>Create 499
Creating Lists
interest. When you press the Apply button, the list will comprise all elements to which the selected
properties or material is assigned.
A filtering mechanism helps you reduce a potentially long list by entering one or more letters of the name
of the desired property set.
Lists by Association
Association also depends on the nature of entities selected for the list. Geometric entities may be
associated with other geometric entities, whereas FEM entities may be associated either with other FEM
entities (e.g., nodes associated with the same element) or with geometric entities (e.g., nodes associated
with the same edge).
500
Tools>List>Create
Creating Lists
Target List
The list assembled in the List>Create dialog box will be entered in a List A or an identical List B form.
The listed entities may now be saved in the database as a group, added to another group, input into a select
databox in an application dialog box, or highlighted on the screen.
lista contents:
Displays the list that resulted from the List>Create operation. The
contents of this textbox are not editable.
Add to Group
Creates a new group for the listed entities or adds them to an existing
group.
Highlight
Clear
Previous
Restores the contents of the textbox to what it was before the current
list was applied.
Tools>List>Boolean 501
Boolean Operations on Lists
Tools>List>Boolean
With the Tools>List>Boolean command sequence you can combine two lists into one, using Boolean
operations.
Union--outputs a resultant list that contains all members of list A plus all members of list B.
Subtraction--outputs a resultant list obtained by subtracting the contents of one list from the
502
Tools>List>Boolean
Boolean Operations on Lists
Intersection--outputs a resultant list obtained by finding members that are common to both list A
and list B.
listc Contents
Clear
Add to Group
Creates a new group for the listed entities or adds them to an existing
group.
Replace A
Replace B
Highlight
Tools>Mass Properties
Mass Properties
The Tools>Mass Properties application enables you to calculate the mass properties of two-or threedimensional geometric and finite element models. The calculations extend to entire models or any of their
subregions. For an overview of the theoretical background of mass properties calculations, see Summary
of Mass Properties, 948.
The following mass properties are calculated and, if applicable, their symbols displayed:
mass and volume
center of gravity (CG)
inertia tensor at the origin of the reference frame
inertia tensor and principal inertias at the CG
radii of gyration corresponding to the principal inertias at the CG
principal directions for the inertia tensor at the CG.
The principal directions at the center of gravity may be presented in three different forms:
Three orthogonal unit vectors.
A triad of space-fixed rotation angles , , that rotate a reference frame into the principal
inertia frame.
In space-fixed rotation the coordinate frame in which the rotation takes place remains fixed.
The rotation angles represent a 3-2-1 (Z-Y-X) sequence.
The principal frame is obtained by the following rotations:
about the Z-axis by degrees
about the original Y-axis by degrees
about the original X-axis by degrees.
The X axis of the principal inertia frame corresponds to the largest principal inertia, and the
Y axis, to the next largest.
A triad of body-fixed rotation angles ( , , ) in a 3-1-3 (Z-X-Z) sequence.
In body-fixed rotation the coordinate frame in which the rotation takes place moves with each
prescribed rotation.
The principal frame is obtained by the following rotations:
about the Z axis by degrees
about the newly positioned X axis by degrees
about the newly positioned Z axis by degrees.
504
Tools>Mass Properties
Calculating Mass Properties
Where applicable, mass properties are calculated in both the reference Cartesian coordinate frame and in
a user-specified coordinate frame.
Output Options
For the results output of the mass properties calculations, you can request that Patran do one or all of the
following:
plot the principal axes at the center of gravity
create a coordinate frame aligned with the principal axes of inertia
write the results to a mass properties report file.
The principal axes are plotted in proportion to the magnitudes of the radii of gyration of the
corresponding principal inertias, as shown:
The newly created principal inertia coordinate frames will be assigned a coordinate frame ID that is the
next available in the database.
Report Files
Mass Properties report files are written in standard Patran report file format. In addition to mass
properties calculation results, these reports also list all included entities and all rejected entities.
Units
Mass properties are generated in units consistent with those used in the referenced geometry, element
properties, and material properties.
Mass Properties of Finite Element Models
Most mass properties calculations use the density, shell thickness, beam
cross-sectional area, non-structural mass, and concentrated mass values as defined in the Properties
application. If you do not want to use the given element property settings, Patran can override them; the
values of 1.0 will be assigned to density, thickness, or area, and 0.0 will be used for non-structural and
concentrated mass.
Non-structural mass and concentrated mass will be included in the calculations, but direct-input mass
matrices will not. Non-structural inertia will be ignored with no warning issued.
506
Tools>Mass Properties
Calculating Mass Properties
After mass properties calculations have been completed, the Mass Properties Report output will include
a list of all ignored or rejected entities.
Three-dimensional Models
With this default option, you can calculate mass properties for all entity types (0D, 1D, 2D, and 3D).
Two-dimensional Plane Stress and Plane Strain Models
In these models the following assumptions are made:
the model consists of coplanar zero-dimensional or two-dimensional entities.
the thickness of 2D elements is 1.0.
the modeling plane is the plane of the first 2D entity.
if there are no 2D entities, then the modeling plane will be the plane of the first three non-
colinear 0D entities. If a specified entity does not reside in this plane, it will be omitted from the
mass property calculations and will be listed as a rejected entity in the output report.
Two-dimensional Axisymmetric Models
An axisymmetric model may contain axisymmetric shells and concentrated masses (2D and 0D entities)
that lie in a specified modeling plane. If an entity is not in the modeling plane, it will be omitted from the
mass property calculations and listed as a rejected entity in the output report.
Masses assigned to concentrated mass elements in axisymmetric problems are treated as linear mass
densities. Patran calculates the mass of the equivalent 1D hoop by multiplying the input mass by 2r .
Similarly, the moments of inertia applied to concentrated masses in axisymmetric models are treated as
linear moments of inertia. The inertia tensor of the equivalent 1D hoop due to the input moments of
inertia is obtained by multiplying the input moments of inertia by 2r .
The 2D Axisymmetric option cannot be used to calculate mass properties of non-axisymmetric cyclicsymmetry models. These are treated as 3D models. Their mass properties will be calculated for the model
only, not for the entire structure that would be generated by prescribed rotational and reflective
transformations.
508
Tools>Mass Properties
Calculating Mass Properties
Dimension
Relative to Coordinate
Frame
Density/ Concentrated
Mass
Create Principal
Coordinate Frame
Region
Specifies the region for which mass properties calculations will apply.
selected entities.
510
Tools>Mass Properties
Calculating Mass Properties
Include
If you pick this option, property data may be defined either for
geometric entities or for FEM entities.
Both--both geometric and FEM entities may be selected.
Care must be taken with this option, because the calculated mass
may end up to be double the actual value if:
--both geometric and finite element entities occupy
the same space, and
--material and other properties (e.g., thickness)
are defined on the geometry.
Select Groups
If your selection for Region is Group, this databox will display the
names of existing groups. Pick the group(s) for which the mass
properties will be calculated.
A filter is also provided to reduce a potentially large number of entries
in the Select Group textbox.
If your selection for Region is Selected, this textbox will display the
names of entities as you select them.
Entity Selection
The title of the textbox will be appropriate to the entity type you
selected under Include (Geometry, FEM, Both).
Display Method
Summary
Mass properties are calculated for the entire region and a summary
512
Tools>Mass Properties
Calculating Mass Properties
summary spreadsheet, except that three rows of X,Y, Z components are now displayed for each group.
The name of the group is shown in the first column of the first row that contains information of that group.
For FEM entities, this spreadsheet will also contain additional columns to accommodate element
properties, such as element thickness, cross-sectional area, bar length, and property type. The N/A entry
in a cell indicates that the property is not applicable to that element (e.g., bar length for a plate element).
Inertia Tensor
Inertia Tensor at CG
The first three columns contain the inertia tensor at the center of
gravity in a user-specified coordinate frame. The last three columns
contain the inertia tensor at the CG in the reference Cartesian frame.
514
Tools>Mass Properties
Calculating Mass Properties
Principal Directions in
User-Specified Frame
2. Click the Write To Report File toggle and the Report File form will be displayed. Initially only
the left-side portion of the form will be active.
3. Select the appropriate folder and enter a name for the report file. Be sure that the .rpt extension is
included.
4. Press Apply, and the right-hand side of the form will now become selectable.
5. Pick Mass Properties in the Report Contents list and press Apply. The report file will be written.
If you havent completed all input required for mass properties calculations, skip step 5, return to the
Mass Properties dialog box, perform whatever needs to be done. Press Apply to write the report.
Active Report Files
Once a report file has been started, it will remain open throughout a work session, even if you selected
Cancel in the dialog box and closed the report file form. In fact, it will remain active even if you close
the current database and start a new one without quitting Patran.
Therefore, Steps 2-5 in the preceding discussion apply only if you have not yet generated a report file in
the current work session; the process will be slightly different if a report has been created already.
If you select the Write To Report File toggle in the Mass Properties dialog box and the Report File form
does not appear, that is an indication that a report file is already running even though the report form may
be hidden (removed from the screen with the Cancel button). If you now request that another set of data
be written to a report, the new information will be automatically appended to the already open report file.
516
Tools>Mass Properties
Calculating Mass Properties
To create a new report file (and close the one that is open), select File>Report and the Report File form
will be redisplayed. Follow steps 3-5 for creating a new report file.
You can find and read your report files in the Notepad application.
Rotation Angles
Space-fixed and body-fixed rotational angles (see Mass Properties, 503) are given in the Cartesian as
well as in a user-defined coordinate frame.
Rejected Entity List
Rejected elements are typically those for which the properties required for mass properties evaluation
have not been provided.
518
Tools>Beam Library
Using the Beam Library
Tools>Beam Library
Beam Library
Beam elements can be defined with a variety of cross sections. The beam library offers a number of
standard shapes as well as a means of defining your own arbitrary cross sections. In either case, you
can request that the dimensioned profile and its calculated section properties be shown after you have
entered all required dimensions or point coordinates. Optionally, you can also output a report file that
contains all boundary information.
Standard Shapes
Industry standard beam cross sections are presented in a tabular form; after you select an item, the
enlarged shape and its required dimensions will be displayed.
Standard-shaped cross sections may be constant or vary along the length of the beam. To create variable
sections, you must use one or more spatial fields for dimensions, as well as provide a location for
evaluation along the length of the beam. This may be defined either with XYZ coordinates or with a
parametric function.
Arbitrary Shapes
In addition to standard cross-sectional profiles, you can also create your own specific non-standard beam
cross sections by generating arbitrary boundary contours. A boundary must be a closed loop that consists
of straight line segments. The cross section may contain holes; these are generated by adding inner
boundaries to the shape definition. Because the first loop defines the outer boundary, all subsequent loops
must be located within the area enclosed by the first loop.
To define the cross section, you can
enter a series of input point coordinates
select a surface whose outline will be approximated by the boundary
provide a file from which the point coordinates may be selected.
Using a Surface
The arbitrary cross section is created by tracing the outline of an existing surface. The surface may be a
trimmed surface but not with any degenerated edges or duplicate edges. A number of points are sampled
on the surface boundary and their coordinates are placed in the spreadsheet. If the surface contains mesh
seeds, the points are sampled at the seeds.
Reading a File
The boundary is drawn utilizing points whose coordinates are contained in a file. To be able to read the
data and generate the profile, the format of the referenced file must be the same as the format of a Report
File that captures the point data of a manually created cross section.
Stress Recovery Points
When you define an arbitrary boundary, you can also specify up to four boundary points as stress
recovery points, at which you want to see stresses reported. Labeled with the letters C-F, these points may
typically be located at the points where cross- sectional changes occur.
Graphical User Interface
Using the beam library, you can select among a number of dimensioned standard beam cross sections or
define a new arbitrary cross-sectional shape. Once you have supplied the necessary dimensions for a
standard cross section--or sufficient information for an arbitrary shape-- you can request that the
dimensioned profile and its calculated section properties be shown. Optionally, you can also output a
report file that contains all boundary and section property information.
Using Calculated Beam Properties
You may calculate beam properties independent of the analysis preference. However, Patran does not
support direct access of calculated beam properties for all analysis preferences. If you are using an
analysis preference that does not support direct access to calculated beam properties, you will need to
input the generated properties by hand or calculate the beam properties first using a supported analysis
preference and then change analysis preferences.
520
Tools>Beam Library
Using the Beam Library
Action
Object
Method
Existing Sections
Shape Symbols
Shows the standard shape symbols. To browse through all the shapes,
press one of the arrows and the next (or previous) panel will be
displayed.
For a standard cross section, select one of the profiles. Its outline and
required dimensions will appear on the right side of the form. Fill in
all dimensions.
Lists the name of existing spatial fields that you may apply for one or
more dimensions if the cross section varies along the length of the
beam.
Calculate/Display
522
Tools>Beam Library
Using the Beam Library
524
Tools>Beam Library
Using the Beam Library
In the Beam Library dialog box, next to Object, click the button marked Standard Shape to reveal the
other option of Arbitrary Shape. Notice that the dialog box form will change; the symbols of standard
shapes will be gone and the right side of the form will contain several new input items.
Option
Input Data
Point
X Outer
Y Outer
Stress Rec
Arrows
Loop
Shows the number of the loop that you are generating. Loop 1 is the
outer loop, any subsequent loops are inner loops that define holes in
the profile. Up to eight loops may be created.
Insert Row/
To insert a new row of data into the spreadsheet, select the row below
where the new row will be placed and press Insert Row. The row above
it will become available for data input.
Delete Row
To delete a row from the spreadsheet, select the row and click the
Delete Row button.
Clear Boundary
Display Boundary
Draws the boundary loops. Loop points are numbered according to the
spreadsheet input.
Rotate/ Angle
Rotates the points on all loops about point 1 of the outer loop by the
angle you enter in the Angle databox.
526
Tools>Beam Library
Using the Beam Library
Because the loops of the cross-sectional boundary must consist of straight line segments, if a reference
surface has curved edges these will be substituted by straight lines. The deviation between a curved
segment and a straight line segment is called allowable curvature error; its default value is 0.05.
The endpoint coordinates of the line segments will be recorded in the spreadsheet as the boundary input
points. For a closer approximation--and a larger number of points--decrease the value of the curvature
error.
Once the data has been entered, there is no further connection between the surface and the section,
consequently you can edit the point coordinates as desired (e.g., round them up or down).
If the reference surface lies in the global XY, YZ, or XZ plane, the orientation of its boundary loops will
be defined in Coordinate Frame 0. If it is not in any principal plane, a temporary plane and coordinate
frame will be created as the edge points are recorded.
The two numbers in each line of the boundary loops data represent the X and Y coordinates of a point,
these will be entered into the spreadsheet. A blank line ends the loop. If there are several loops, each is
delimited by blank lines.
The Stress Recovery Points heading is followed by a line with up to four numbers that identify the
stress recovery points. The numbers correspond to the boundary loop points as they appear in the point
list starting with the first line (1) and not counting blank lines.
Stress Recovery Points
When you define an arbitrary boundary, you can also specify up to four boundary points as stress
recovery points, at which you want to see stresses reported. The procedure to identify these points is as
follows:
1. In the Point spreadsheet portion of the Beam Library dialog box, move the scrollbar to the right.
This will reveal the column with the heading Stress Rec (short for Stress Recovery).
2. In this column, click in the cell that is in the row of a point designated for stress recovery.
3. The Input Data databox will be replaced by the Stress Recovery options menu. Select a point
label (e.g., Point C).
4. Continue assigning additional points; points C through F can be selected. To eliminate a stress
recovery point, select None and the cell will be cleared. If you assign a label to a point and that
label is already in use, you will be asked if you wish to overwrite, or redefine, the stress recovery
point.
528
Tools>Beam Library
Using the Beam Library
5. When you press Calculate/Display, the profile will be drawn and the stress recovery points will
be labeled with the appropriate letters.
end point of the previous branch it is sometimes necessary to overlap branches. When this is required,
you enter a zero thickness for the overlapping branch.
Option
Input Data
Branch
Thickness
dx/ds
dy/ds
#Divs
530
Tools>Beam Library
Using the Beam Library
Insert Branch/
Delete Branch
To insert a new branch into the spreadsheet, select the branch below
where the new branch will be placed and press Insert Branch. The
branch above it will become available for data input.
To delete a branch from the spreadsheet, select the branch and click the
Delete Branch button.
Clear Branch
Display Branches
Curvature Error
You can define arbitrary sections with the Centerline method, press the Display Boundary button, and
then change the Method to Boundary Loops. The arbitrary shape from the centerline definition is also
stored as boundary loop data. At this point, if you press the Apply button, the beam section will be stored
as Boundary Loop arbitrary section as opposed to centerline data. Thus the centerline data can be used
directly in an MSC.Marc or MSC Nastran analysis, or can be converted to boundary loops and used in
other analysis code including MSC.Marc if property values are accepted and input.
Centerline Method Examples.
Two examples of how to create cross sections with the centerline method are shown below.
The first example is a irregular, upside-down T beam. This requires 3 branches, one of which overlaps
and receives a zero thickness. The X, Y, and thickness values are tabularized below for the beginning
(e.g., 1b) and end (e.g., 1e) of each branch. The actual boundary loop points are calculated and displayed
on the side of the plot. As long as the Method is set to Centerline, the data is stored as branch data. This
means that the MSC.Marc, and MSC Nastran analysis codes are the only ones that can take advantage of
this section. If however, you change the Method to Boundary Loops before pressing the Apply button,
then the section is stored as an arbitrary section with section properties calculated accordingly and all
other analysis codes that accept section properties can use this section. In this case the Centerline method
was used out of convenience if defining the section.
X
1b
1e
10
2b
10
2e
3b
3e
10
The second example is a D section with curvature. The X, Y, dx/ds, dy/ds and thickness values are
tabularized at the side of the plot. Two branches are defined. The slopes of the first branch are opposite
each other, thus indicating to the program a curvature for this branch. The D section looks bad when using
532
Tools>Beam Library
Using the Beam Library
the default curvature error. If you reduce this to say, 0.02 instead of the default 0.05, the D section looks
much better as shown below.
X
dx
dy
1b
0.1
1e
0.1
-1
2b
0.1
-1
2e
0.1
-1
534
Tools>Beam Library
Using the Beam Library
mass properties calculations; if you need more information please refer to (p. 515) of this manual.
Existing Sections
Lists existing cross sections. Select the one you want to change.
Rename Section As
Section Symbols
Shows cross section symbols. Pick the section you want to use to
replace the existing one.
Section Dimensions
536
Tools>Beam Library
Using the Beam Library
Location Specification
Options
Modifies the location where the field value will be evaluated. Enter
new coordinates, or select a new curve or beam element and move the
slider to define a new parametric location.
Existing Sections
Lists existing beam cross sections. Pick the section(s) you want to
delete.
Sections to Delete
Displays the name of the cross section(s) you selected for deletion.
Apply
Deletes the selected cross section(s) and remains in the Beam Library
application
Cancel
Cancels the delete action and exits the Beam Library application.
Tools>Regions 537
Define Named Application Regions
Tools>Regions
Named Regions
Named Regions are collections of entities that can be used as application regions for Loads and Boundary
Conditions as well as Element Properties. They are general like Groups, but differ in that they are not
used for display purposed and are restricted (like Application Regions) in that they can only contain one
topology type (1D, 2D, 3D). Some Applications, such as CATIA import, will automatically create these
named Regions making them a convenient way to define LBC or Element Property application regions.
Unlike Groups, where the entire entity must be in the group, Named Regions can be defined with only
portions of the entity defined such as the faces of a solid element or the edges of solid geometric entities.
538
Tools>Regions
Tools>Regions 539
Define Named Application Regions
Once a named Region is created it can be used on the Select Application Region form of a Load and
Boundary Condition or Element Property Set and in other select areas of Patran.
Selecting Entities for Named Regions
There are two modes for collecting entities for a named Region: Entities and Groups
The Entities option of Region Creation works almost exactly like Entity selection of Application Regions
only with Application Region selection there are pre-defined limits (defined by the application) on the
type of topology that may be selected. When creating Regions the user defines the topology using the
Target Entity Type pull-down menu. Regions can also be created using Regions to filter which entities
are selected.
The types of Regions that can be created (node, element, edge, face), correspond to the type of entities
required in the Application Region of the LBC or Element Property set, and also by the dimensionality
of the Application Region entities (0, 1, 2, or 3 D). Once these are selected the individual entities, or
group the entities belong to, can be selected on the Select Application Region form.
On the Select Application Region form the Regions can be created using the Entities option by selecting
FEM or geometry entities similar to what can be done on the LBC or Element Property forms. The select
menus are used to filter the types of entities that can be graphically selected from the graphics screen.
3D Entity Select
2D Entity Select
1D Entity Select
0D Entity Select
Element E
Face Select
Node Select
540
Tools>Regions
Tools>Regions 541
Define Named Application Regions
542
Tools>Modeling
Modeling Tools
Tools>Modeling
Modeling Tools
543
2. Tools>Modeling>Properties Import
3. Tools>Modeling>Load Tools
547
552
4. Tools>Modeling>Model Variables
567
579
581
585
602
9. Tools>Modeling>Assembly>Reduced Mass/Stiffness
10. Tools>Modeling>Assembly>Model Unmerge
11. Tools>Modeling>Experimental Data Fitting
12. Tools>Modeling>Bolt Preload
647
650
651
652
655
638
644
613
Tools>Modeling>Model Content
Model Contents
This is a simple utility to allow you to view the contents of a database. It is limited to finite element data
and gives information on the following entities (any entities not listed are not supported in this utility):
Groups
Coordinate Frames
Load Cases
Properties
Fields
Loads/BCs
Materials
Result Cases
Elements / Nodes / MPCs
The Model Contents tool creates a spreadsheet summary at three levels of resolution. The lowest level of
resolution is displayed in the main summary shown below. At this level, only the number of entities of a
particular type are displayed. A more refined summary is obtained by selecting any one of the main
category buttons or any one of the cells in the spreadsheet where the contents of each group are
summarized.
544
Tools>Modeling>Model Content
Viewing Model Contents
The general contents of the current database are summarized into different categories. A detailed listing
of all of the contents of any category may be obtained by selecting the button associated with that
category. Then another form displays giving an expanded summary.
If changes to the model are made while this form is visible it may be necessary to press the Update button
in order for the changes to be reflected in the form.
All data can be written to a file by clicking on the Write to File button. The data is written to a file called
smdl_modelstat.txt in the current working directory. This issues the following PCL command,
which only works properly when Patran is run in graphics mode (not batch) as it exercises the PCL form
widgets themselves, which are not active in batch mode.
smdl_modelstat.dump_model_info(val)
The input argument, val is set to TRUE when issued by this utility. If it is set to FALSE, the file will
not be written but the data will be dumped to the command line window and in the currently recording
session file. Note that there can be significant performance issues if you do this with a very large model
and is not recommended.
Groups
If the user selects a cell in the group summary contents spreadsheet under the column labeled Elements,
then a subordinate form is displayed. The format of the element summary depends on whether the Shape
or Type toggle is set in the main form. If a summary by Type is requested, then any MSC Nastran element
type not supported by the current Analysis Preference is listed as Other. If a cell in the group element
summary form is selected, a form is displayed giving a listing of all the element IDs for a particular
element type or shape. The user also has the ability to highlight the elements contained in the list box in
the current graphics viewport.
If the user selects a cell in the group summary contents spreadsheet under the column labeled Nodes, then
a form is displayed giving a listing of all the node IDs contained in the group. The user may either
highlight or un-highlight the nodes in the current graphics viewport. Similarly, selecting a cell in the
column labeled MPCs results in a similar form being displayed. To obtain a listing of the specific MPC
IDs associated with a given type, select any cell that has a nonzero count. Any MPC not recognized by
the current Analysis Preference will be listed as Unknown/Not Valid.
Properties Summary
If the Properties button is selected, then a form is displayed giving a detailed summary of all of the
property types contained in the model. The summary includes the property name as well as the property
type. Any property type not currently supported by current Analysis Preference will be classified as
Other.
Material Summary
If the Materials button is selected, then a form is displayed giving a detailed summary of all of the
material types contained in the model. The summary includes the material name as well as the type. Any
material type not currently supported by current Analysis Preference will be classified as Other.
Coordinate Frame Summary
If the Coord. Frames button is selected, then the following form is displayed giving a detailed summary
of all of the coordinate frames contained in the model. The summary includes the coordinate frame name
as well as the type.
Field Summary
If the Fields button is selected, then a form is displayed giving a detailed summary of all of the Patran
fields contained in the model. The summary includes the field name as well as the type.
546
Tools>Modeling>Model Content
Viewing Model Contents
Loadcase Summary
If the Load Cases button is selected, then a form is displayed giving a detailed summary of all of the load
cases contained in the model. The summary includes the load case name only. The contents of any load
case can be accessed by selecting the Load Cases application radio button located of the Patran main form
or under the Loads/BCs tab if running Patran with a GUI skin other than the classic mode.
LBC Summary
If the LBCs button is selected, then a form is displayed giving a detailed summary of all of the LBC types
contained in the model. The summary includes the LBC name, the type, as well as whether or not the
LBC is static or dynamic (i.e. time dependent). Any LBC type not currently supported by Patran will be
omitted. Any association to Load Cases is not accessible through the summary. Rather it may be obtained
by selecting the Load Cases application as explained above for loadcase summary.
Result Case Summary
If the Result Cases button is selected, then a form is displayed giving a detailed summary of all of the
Result Cases contained in the model. The summary includes the Result Case name only as well as
whether it contains static or dynamic (i.e., time dependent) results. The contents of any Result Case can
be accessed by running the Results application from the main Patran form.
Tools>Modeling>Properties Import
Importing Properties
Properties Import
To use the Properties Import feature you will need to create and select an input file. You will need to
decide how element properties will be named if new element properties are made.
Creation of a Property
The creation of a property requires all of the following fields. If one these fields (columns) is defined, all
must be defined, or an error will be issued. These fields are only used when creating new properties.
Note that all field headers and the data that follows on subsequent lines must be separated by the semicolon ";" delimiter. The last column must end with a ";" or it will not be recognized.
ELTYPEID, GEOOPTID, CONOPTID, FOROPTID, LAMOPTID,
DOFOPTID,
The value of those fields determines what type of property you are going to create.
When you create a "2D", "Shell", "Thin", "Homogenus", "Standard Formulation", or a "1D", "Beam",
"General Section", from the option menu, all six Property IDs must have data. The data for thickness or
materials is defined by the Patran internal ID for that property word. See the examples for information
on finding the proper IDs.
548
Tools>Modeling>Properties Import
Importing Properties
To create a property and import it using the properties import form, you will need to create a text file
(with .epi as the suffix) that has the following information (note that any line beginning with a "$" is
treated as a comment):
PNAME;
ELTYPEID;
GEOOPTID;
CONOPTID;
FOROPTID;
LAMOPTID;
DOFOPTID;
$Prop name
elem_type_
ID
geo_opt_ID
con_opt ID
for_opt ID
lam_opt_ID
dof_opt_ID
Shell;
51;
25;
35;
1;
1;
20;
Bar;
11;
2;
42;
1;
1;
20;
continued...
13;
36;
Material
M:Alum;
M:Steel;
4095;
1;
10;
11;
2;
APPRGN;
Thickness Y of NA
Area
I11
I22
Bar Or.
Elements
2;
E 1:9:2;
10;
10;
10;
1, 0, 0;
E 2:5;
Modification of a Property
If you want to modify a property, you will need to create a text file similar to the following:
PNAME
; 13
APPRGN
$Prop name
Material
Bar orientation
Element list
bar
;1, 0, 1.0
shell
; M:Alum
;E 1:10
The above example modifies the property bar to change the bar orientation to <1,0,1.0> and the
property shell to have the material Alum and an appregion of Elements 1 through 10.
Example Creation of a 2D shell
For example, if you would like to create a 2D shell, you would create an input file like this:
Example input file
PNAME
toto
The 2D shell data would show up as if the following session file had been played.
Example Session File
elementprops_modify( "toto", "toto", 51, 25, 35, 1, 1, 20, [13, 20, 36, 4037, 4111,
4118, 4119], [5, 9, 1, 1, 1, 1, 1], ["m:STEEL", "", "0.33000001", "", "", "", ""],
"Surface 1" )
The easiest way to find the ELTYPEID thru the DOFOPTID data is by looking at the session file. The
session file above corresponds to the input file above. Also, the IDs of the words for the data m:STEEL
and for the thickness 0.33 can also be derived from the same session file. The data you have entered is
found in the first and third arguments of the data array. The IDs for those pieces of data can be found
highlighted in the ID array below.
This is the ID array. The first and
third numbers (13 and 36) are the
material and thickness IDs
respectfully.
elementprops_modify( "toto", "toto", 51, 25, 35, 1, 1, 20, [13, 20, 36, 4037, 4111, 4118, 4119], [5, 9, 1,
1, 1, 1, 1], ["m:STEEL", "", "0.33000001", "", "", "", ""], "Surface 1" )
This is the data array. m.STEEL is the material
and the thickness is 0.33.
Example Modification of a Property
Modify a Property by adding a Real Likst or modifying the existing Real List by appending RL to the
beginning of the REAL LIST (0.,0.8,1.) as in the example below.
comment
PNAME
; 4061
PROP_BAR
;RL0.,0.8,1.
comment
; 13
; 1
; 10
; 11
; 6
101
; m:STEEL
; 1.1
; 10.1
; 1.1
;RV<1,0,1.1>
102
; m:STEEL
; 1.1
; 10.1
; 1.1
;RV<1,0,1.2>
The above example assumes that elements 101 and 102 are already associated to an element property.
The code then "expands" the element property for the elements, and modifies those expanded properties
to change the properties 13, 1, 10, 11 and 6. (Which are Material, Area, I11, 122 and Bar Orientation).
550
Tools>Modeling>Properties Import
Importing Properties
EID
4
Example 3
$ This file changes element 4 to have a thickness of 0.08 and a
$ mat of steel2
$ Elem ; material ; thickness
EID
; 13
; 36
4
; m:steel2 ; 0.08
Example 4
$ This file Creates a New Property
$ The elements from the APPRGN Column are assigned to the new
property
ELTYPEID
APPRGN
51
1:15:2 ;
Datatype Abbreviation
REAL SCALAR
RS
NODAL FIELD
NF
NODE ID
NI
SECTION DATA
SD
COORD ID
CI
13
; 36
m:mat1 ; 0.01 ; E
Datatype
Datatype Abbreviation
REAL LIST
RL
REAL VECTOR
RV
552
Tools>Modeling>Load Tools
Using Load Tools
Tools>Modeling>Load Tools
Load Tools
The Loads Tools utility allows users to create either Running Loads plots or perform Load Summations.
The Actions are grouped as follows:
Create (Region, Region Chain and Force)
Modify (Region or Region Chain)
Delete (Region or Region Chain)
Plot - Running Loads (LBCs, Load Cases, or Results)
Plot - Load Summation (LBCs, Load Cases, or Results)
Creation of Running Loads plots and Load Summations requires the identification of a section of the
model over which the plot is to be created. This section can be described using a Region, Region Chain
or on-the-fly through interactive node and element selection.
For example, visualizing resultant loads along the bending axis of a wing can be very helpful for
verifying that the correct loads have been applied to a model..
Load Summation provides a convenient method of summing the applied vehicle loads about a spatial
location.
Both Running Loads and Load Summation support the following kinds of external loads:
Forces and Moments
Pressure
Inertia
Distributed Edge Loads
The following picture illustrates the methodology behind the Running Load plots., often referred to as
SBMT (Shear, Bending, Moment, Torque) plots.
Chained region 1
Chained region 2
Z
Y
Z
5
10
15
20
25
30
10
-5
X
15
20
25
Sample XY Plot:
50
40
Air_Load_Mx
Moment
Fuel_Mx
30
Plotted together by
component, for this example
20
10
0
0
10
20
30
40
50
60
X Location
554
Tools>Modeling>Load Tools
Using Load Tools
Note:
The groups used to define a Region must contain the FEM node/elements of interest for the
Running Loads plots and should only contain FEM entities (no geometric entities). The
application regions of the selected loads (or loads in selected load cases) for a Running
Loads plot and the Regions should have the same entities. If these rules are not followed,
the plots may be difficult to interpret as some loads may be ignored in the calculation and
the user may be unaware.
Two or more Regions can be chained together and referenced as a Region Chain. A Region Chain can
describe Regions with a discontinuity at their intersections (i.e. two Regions that follow a wing spar
break). Region Chains can be referenced in Running Load plots.
To create a Region Chain over which to calculate Running Loads or do load Summation you must do the
following with the Action/Object set to Create/Region Chain.
1. Supply a new Region Chain Name in the data box.
2. Select the Existing Regions in the order in which they are to be plotted. You can always use the
Clear Selection button to remove the selected Regions from the Chained Regions list box and
start over.
Loads from a Chained Region are calculated from the maximum X of the last region in the chain back to
the minimum X of the first region in the chain. Loads from regions further out on the chain are added to
regions further in on the chain at the maximum X after they are transformed to the designated coordinate
system.
Use the Modify and Delete Actions to modify or delete existing Regions and Region Chains.
Create Equivalent Vector Force
The Create/Force functionality enables a user to create an equivalent force vector that is derived from
all of the nodal forces within any combination of existing load cases. The user has the ability to define
the load summation point where the equivalent force is applied as well as the region over which the load
summation is performed. The resultant force can either be used to replace the contents of an existing load
case or to create an entirely new load case.
To create an Equivalent Vector Force
1. Select one or more Load Case(s) which contain nodal forces.
2. Indicate the Load Disposition. This is whether a new Load Case is to be created or whether
existing data is to be replaced in the selected Load Case(s). Give a new, if a new Load Case is to
be created.
3. Supply an Output Coordinate Frame. The equivalent force vector will be defined in this
coordinate frame. The default is the global rectangular frame (Coord 0).
4. Define the Application Entities. These are the entities over which the load summation is
performed. You must ensure that the Load Cases selected have nodal loads that are applied to the
selected entities, else an equivalent force will not be created. Consequently, element based forces
such as pressures are ignored. So for example, if the application region of your force LBCs is
made up of nodes, select nodes. This is the most common. If it is made up of geometric points,
select geometric points.
5. Supply a Summation Point. This is the node or point location where the equivalent force will be
applied. Only a single node or location may be specified. Any additional locations will be ignored.
Plot Running Loads
To plot Running Loads, set the Action to Plot and the corresponding Method. The form layout is set up
so that the user sets up the plot in a logical order from the top of the form to the bottom. Several subforms
are also used to define the parameters of the plots to be generated. There is the optional choice of writing
this information to a report file.
After identifying that a Running Load plot is desired, the models nodes and elements must be identified
either by membership to a Region, Region Chain or Selected Entities.
After the parameters for the plot have been defined, choose Apply to produce the requested XY plots.
For these plots, the first region is plotted using its X coordinates directly. The next chained regions are
included by adding their X value onto the end. The origin of the second system locates its value in the
first coordinate system.
For example, suppose a first chained region is defined from X=5 to X=32, and the second chained
region covers X=-3 to X=23. The origin of the second chained region is located at X=29 in the first
coordinate system. Data from the first chained region occupies the graph from x=5 to x=32, and the
second chained region are plotted over x=26 to x=51, as shown above.
Follow these instructions for calculating Running Loads from LBCs, Load Cases, or Results quantities:
LBCs
1. Set the Target to either Selected Entities or a pre-defined Region or Region Chain.
2. Select the entities, or pre-defined Region or Region Chain. If Selected Entities is used, supply a
Coordinate Frame in which to calculate the running loads (default is Coord 0). The coordinate
system is already defined in the definition of a Region or Region Chain when using those options.
Note that running loads are calculated based on the X direction of the supplied coordinate system.
3. Select the LBCs that will be used in calculating the running loads. Be sure to select LBCs that are
defined on the selected entities or Regions / Region Chains, otherwise they will be ignored. One
or more Loads/Boundary Conditions can be integrated over a model to produce a Running Load
plot.
4. Set any Options... required. Please see the Plot Options section below that describes these
options. This option enables the user to produce more refined running loads plots.
5. If you want the XY data written to an file, turn ON the Output to Text File toggle and then use
the Select File Name... button to define a file name for the output.
6. If there are existing XY plots from previous running loads plot operations, you can delete them
before creating the new plot by clicking on the Delete Existing Plots... button.
7. Press the Apply button to create the plot. A plot will appear displaying the requested Running
Loads. The XY windows and curves are saved and can be further manipulated and plotted using
in the XY Plot application under the Results tab or XY Plot button in classic mode.
556
Tools>Modeling>Load Tools
Using Load Tools
LoadCases
For Running Loads plots follow the same sequence as for LBCs above. The only difference is that you
select Load Cases is step 3 above as opposed to LBCs. All applicable LBCs in the Load Cases will be
used in the Running Loads plot.
Results
For Running Loads plots follow the same sequence as for LBCs above. The only difference is that you
select Results Cases and corresponding Nodal Vector Results is step 3 above as opposed to LBCs. The
Results will be integrated over the Selected Entities, Region or Region Chain to product a Running Loads
plot.
Load Summation
To do a Load Summation, set the Action to Plot and the corresponding Method. The form layout is set
up so that the user sets up the plot in a logical order from the top of the form to the bottom. Several
subforms are also used to define the parameters of the plots to be generated. There is the optional choice
of writing this information to a report file.
After identifying that a Load Summation is desired, the models nodes and elements must be identified
either by membership to a Region or Selected Entities or the Entire Model. Follow these instructions for
calculating Running Loads from LBCs, Load Cases, or Results quantities:
LBCs
1. Set the Target to either Selected Entities the Entire Model or pre-defined Regions.
2. Select the entities, or pre-defined Regions if not summing over the entire model.
3. Select the LBCs that will be used in calculating the load summation. Be sure to select LBCs that
are defined on the selected entities or Regions, otherwise they will be ignored. One or more
Loads/Boundary Conditions can be summed over the model or selected entities.
4. Set any Options... required. Please see the Plot Options section below that describes these
options. This option enables the user to produce more refined load summations. The coordinate
system in which the load summation is displayed is set under this option. Default is the global
Coord 0.
5. Select a Reference Point about which to perform the Load Summation. This can be a finite
element node, a geometric grid point, or another other allowed definition of a point via the select
mechanism. The point is to be selected graphically from the graphics window or you can type in
something like Node 5 or Point 3 or an actual point in space such as [1.0 2.5 -3.2].
6. Press the Apply button to do the load summation. A spreadsheet will appear with the summary of
each selected load and their components. You may optionally save this data to a report file by
clicking on the Save button once the spreadsheet is displayed.
LoadCases
For Load Summation follow the same sequence as for LBCs above. The only difference is that you select
Load Cases is step 3 above as opposed to LBCs. All applicable LBCs in the Load Cases will be used in
the Load Summation and the component results displayed for each selected Load Case.
Results
For Load Summation follow the same sequence as for LBCs above. The only difference is that you select
Results Cases and corresponding Nodal Vector Results is step 3 above as opposed to LBCs. All selected
Results will be used in the Load Summation and the component results displayed for each selected
Results Case.
Plot Options
The following table explains the options on the Plot Options subordinate form for a Running Loads Plots
and Load Summations. This subform is accessed from the Running Loads main form and controls the
appearance of the XY plot (as well as the status of previously created plots) and load summations. Not
all widgets appear for both Running Loads and Load Summation. Only those that appear on the form are
applicable for the selected option.
Load Components
A default algorithm is used to convert pressures to concentrated loads or users may supply their own algorithms. See
Pressure to Load Algorithm below this table. This routine is
called anytime a pressure load needs to be converted to nodal
forces. The selected LBC must be of type pressure or the
Load Case must contain LBCs of type pressure. For Results,
only nodal results are allowed, so in this case, this routine is
ignored.
Evaluation Points
Coordinate System
558
Tools>Modeling>Load Tools
Using Load Tools
For a user-defined algorithm to appear on the pressure conversion algorithm form, several conditions
must be satisfied. First, a function that converts pressure loads to nodal loads must be created. This
function must have the exact arguments listed below.
classname.function_name ( xyz, pdata, nnodes, nforce )
This function must have the following input and output.
Input:
REAL(3, nnodes)
xyz
REAL(nnodes)
pdata
INTEGER
nnodes
REAL(3, nnodes)
nforce
INTEGER
<Return Value>
Output:
The PCL library .plb file containing the user created PCL function for pressure conversion must then
be read into Patran using the !!LIBRARY command. See the PCL and Customization Manual for details
on creating PCL functions and loading PCL libraries. Finally, the pressure conversion algorithm must be
registered on the form using the following PCL function.
load_tools_pressure_register.register_alg ( new_alg_name )
Register a new algorithm for element pressure to nodal forces conversions.
Input:
STRING[]
new_alg_name
Output:
None.
Running Loads Methodology
This section covers the theory and methodology behind the creation of Running Load (SBMT) plots.This
section also shows the overall mathematical procedure that is used to generate the data for these plots.
Regions
The first item to be defined is the region. The region consists of finite elements and a reference coordinate
system (see figure below)
z
Reference
Coord
System
Aft
Inboard
Outboard
Forward
y
X
Global
Coord
System
SBMT Region
All data reported on a Running Loads plot for this region is given in terms of the reference coordinate
system. The region covers a certain range of the reference coordinate system. This range is from the
minimum X axis value in the reference coordinate system of the FEM nodes in the region to the
maximum X axis value in the reference coordinate system of the FEM nodes in the region.
Region Chains
Region Chains may be defined. The Region Chain consists of an ordered list of regions. These regions
should be adjacent and attached pieces of structure for a Running Loads plot to give realistic results.
There are no checks in that prevents Region Chains from containing unattached pieces of structure.
RCS,
Chained SBMT region 1
Z
Y
RCS,
Chained SBMT region 2
Z
Y
X
X
Z
RCS,
Chained SBMT region 3
The procedure for generating the plot data consists of summing the loads from the maximum X axis
location in the last region in the chain back to the minimum X axis value of the first region in the chain.
These summed loads are known as running loads.
560
Tools>Modeling>Load Tools
Using Load Tools
Running loads are calculated at the evaluation points for each region. The number of points at which
applied loads are summed and reported is determined by the evaluation points box on the Plot Options
form. This number is the same for all of the regions. Loads applied to the model that lie within the X-axis
region of the specified coordinate system(s) are included in the running loads plot.
Planes / Evaluation points
for chained region 2
Planes / Evaluation points
for chained region 1
Chained
Region 2
1
Chained
Region 2
N
= Load point
= Evaluation point
The equations used to sum the loads together for an evaluation point are as follows.
loads
F x, eval =
loads
F x, i
i=1
F y, eval =
loads
F y, i
i=1
F z, eval =
F z, i
i=1
loads
M x, eval =
M x, i + F y, i Z i + F z, i Y i
i=1
loads
M y, eval =
M y, i + F x, i Z i + F z, i ( x i x eval )
i=1
loads
M z, eval =
M z, i + F x, i Y i + F y, i ( x i x eval )
i=1
To find the beginning running load (load at the maximum evaluation point) for a region, the running load
at the minimum evaluation point of the next region in the chain is transformed from the reference
coordinate system of the next region in the chain to the reference coordinate system of the current region
and then translated to the maximum evaluation point of the current region. If the region is the last region
in a chain then the beginning running load is zero for all terms.
For the reporting of region locations on the plots, the first region is plotted using its x coordinates directly.
The next chained region is included by adding their X value onto the end of this, with the origin of the
second system locating its value in the first coordinate system.
For example, a first chained region is defined from X=5 to X=32, and the second chained region covers
X=-3 to X=23. The origin of the second chained region is located at X=29 in the first coordinate
system. Data from the first chained region occupies the graph from x=5 to x=32, and the second chained
region is plotted over x=26 to x=51.
It is very likely that two adjacent regions contain identical nodes. Therefore, the code checks to see if
regions next to each other in a chain contain identical nodes and place forces attached to those nodes only
in the region appearing first in the list. This prevents double counting of the forces applied to these nodes.
This check is only done for adjacent regions in a chain. No check is done for duplicate elements, therefore
pressures applied to elements present in more than one region in an chain is summed twice in the running
load calculation.
562
Tools>Modeling>Load Tools
Using Load Tools
Z
1
Y
X
Z
Y
2
Region 1
Y
X
Region 2
X
X
Z 3 Y
Y
X
Region 3
Y
X
Region 4
The first step in generating an Running Loads plot is to decide how many individual integration regions
are required to cover all of the wing. In this example, three distinct integration regions with different
integration axes can be identified. To prepare the model to create these three Regions, the FEM and nodes
to be contained in each region must be put into groups and coordinate systems with x axes corresponding
to the desired integration axes.
Create Running Load Regions
After the model has been prepared, the Running Load regions may now be created. This is done from the
Load Tools form. Set the Action to Create and the Object to Region.
To create an Region:
1. Enter the name to be assigned to the region in the Region name box inner_wing,
outer_wing, and winglet for the three regions in this example.
model. Check to make sure that the correct elements are highlighted.
Press the OK button to accept the region definition.
After the Regions have been created, the individual Regions can be chained together to fully define the
integration axis. In general the order of the regions in an chain is from the root (where all of the load in
the wing is transferred to the fuselage) to the tip.
On the Running Loads form, set the Action to Create and Object to Region Chain.
To create a Region Chain:
1. Enter the name to be assigned to the chain in the chain name box.
2. Select the first Region inner_wing to be in the chain from the Regions listbox. The Region
should appear in the Chained Regions listbox.
3. Repeat step 2 for all other Regions to be included in the chain. Make sure that the order in the
Chained Regions listbox is inner_wing, outer_wing, and winglet.
4. Press the Apply button to create the chain.
Create a Running Loads Plot
After the Regions and Region Chain have been created, Running Load plots can be generated. From the
Running Loads form, set the Action to Plot, Object to Load Cases, Method to Running Loads, and
Target to Region Chain.
Creating a Running Loads plot
1. Select the Region Chain total_wing from the first listbox.
2. Select the Load Cases to be plotted from the Load Case(s) listbox. In this example the Load Case
containing all of the pressure loads on the wing is selected. A curve is generated for each item
selected on this form.
3. Open the Plot Options... form and turn OFF all but the Fz toggle of the components to be plotted.
4. Enter the number of evaluation points for each region in the Evaluation Points databox (20).
5. Indicate that Individually plotted curves is created on the same plot using the option menu under
the Multiple Curves Plotted label.
6. Using the option menu under Previously Created Curves, select As Is for any previously created
plots and press OK to close the form.
Tools>Modeling>Load Tools
Using Load Tools
Condition--Component--Region:
load case 1--Fz--inner wing
load case 1--Fz--outer wing
load case 1--Fz--winglet
0.
-15000.
-30000.
Force
564
-45000.
-60000.
-75000.
-90000.
-2.34
10.0
22.5
34.9
47.4
59.8
72.3
Mx
dx
My = Fx Fy Fz dy
Mz
dz
For pressure loads, the equivalent nodal loads must be calculated. The first step is to transform the
element face to a local coordinate system whose normal, the vector
of a vector from node1 to node 2, the vector
ux
uy
= v 1-2
y
uz
1-2
and
wx
.
ux
vx
.
ux
vy = wx wy wz uy
vz
uz
The transformation matrix, , is created from the direction cosines between the local system and the
global system. The nodal coordinates are then multiplied by the transformation matrix.
566
Tools>Modeling>Load Tools
Using Load Tools
The pressure load, like the displacements in an isoparametric finite element, is defined anywhere in the
element (or on the element face for 3D elements) by
n
q(u, v) =
qi i
i=1
where
q(u, v) = the spatial distribution of the pressure load in the local element coordinate system.
q i = the pressures at the nodes
i = the element interpolation functions.
The equivalent nodal forces are calculated from the exact integral evaluated using Gauss-Legendre
quadrature
M
q =
I = 1J = 1
where
Tools>Modeling>Model Variables
Model Variables
Model variables provide the foundation for design studies. They are the parameters, or properties, whose
magnitude will be modified in the process of performing iterative solutions. A variable may be a
dimension value, an element property (e.g., plate thickness), or a material property. This is a generic
utility for defining model variable. Any variables created using this module are generally available under
the Design Study module. Design variable can also be defined under the Design Study module and may
prove more convenient to only use that module. Variables are only used with design optimization and
therefor only accessible when the Analysis Preference is set to MSC Nastran.
Creating Model Variables
Variables defined for a geometric or finite element model fall into the following categories:
value--a non-specific attribute value associated with the model
568
Tools>Modeling>Model Variables
Defining Model Variables
Values as Variables
Action
Existing Variables
Variable Name
Names the new variable. The unique name may be a letter, a symbol,
or a text string, up to 32 characters long.
Description
Provides a space where you can describe the nature of the variable.
This optional entry is especially helpful if you used an abbreviation or
symbol for the name of the variable and may not remember in the
future what the intent was (for example, which dimension was
designated as L1?).
Analysis Value
Shows the initial value of the variable. Enter a real, scalar number.
570
Tools>Modeling>Model Variables
Defining Model Variables
Existing Variables
Variable Name
Names the new variable. The unique name may be a letter, a symbol,
or a text string, up to 32 characters long.
Description
Provides a space where you can describe the nature of the variable. If
no description is entered, Patran will create a description; it specifies
the names of the Property Set and Property Name from which the
variable was created.
Analysis Value
Shows the initial value of the variable. Enter a real, scalar number.
Dimension
These two entries act together as a filter that facilitates finding the
element property that will be designated as the variable. The search
will be limited to the properties associated with those elements for
which the named dimensionality and type apply.
Type
Select Property Set
Lists the names of the Property Sets defined for the designated
element type. Pick the set that contains the property you wish to
parameterize.
572
Tools>Modeling>Model Variables
Defining Model Variables
Existing Variables
Variable Name
Names the new variable. The unique name may be a letter, a symbol,
or a text string, up to 32 characters long.
Description
Provides a space where you can describe the nature of the variable. If
no description is entered, Patran will create a description; it will
identify the name of the element property set and specific element
property (e.g., Thickness) from which the variable was created.
Analysis Value
Shows the initial value of the variable. Enter a real, scalar number.
Type
This entry acts as a filter that facilitates finding the beam section for
which the variable is applied. The beam library will be searched for the
specified beam cross section type.
Lists the names of previously defined beam cross sections. Pick the
one that contains the property you wish to parameterize.
574
Tools>Modeling>Model Variables
Defining Model Variables
Existing Variables
Variable Name
Names the new variable. The unique name may be a letter, a symbol,
or a text string, up to 32 characters long.
Description
Provides a space where you can describe the nature of the variable. If
no description is entered, Patran will create a description; it will
identify the name of the material property set and specific element
property (e.g., Density) from which the variable was created.
Analysis Value
Shows the initial value of the variable. Enter a real, scalar number.
Category
This entry acts as a filter that facilitates finding the property that will
be designated as the variable. The search will be limited to the
material to which the category type applies (e.g., Isotropic).
Select Material
Lists the names of previously defined materials. Pick the material that
contains the property you wish to parameterize.
Select Materials by
Elements
Select by Elements
Selects the properties associated with elements you pick on the screen.
576
Tools>Modeling>Model Variables
Defining Model Variables
After you picked the variable(s) you want to verify, press Apply and the variable information will be
displayed in a spreadsheet.
Pick any of the properties and its description will appear in the lower left corner of the spreadsheet.
Lists all variables contained in the database. Pick the variable you want
to modify.
Variable Name
Description
Modified Value
Enter the new value you want to assign to the variable. All field values
and relationships that depend on the value of this parameter will be
updated when the new value is applied.
578
Tools>Modeling>Model Variables
Defining Model Variables
If a finite element property is defined as a function of a deleted variable, the current value will be used
for the property entry rather than leaving the property blank.
Select by Elements
Apply/Close
Pick Apply to complete the deletion. Pick Close to cancel the delete
action and exit from the application.
Note:
Element property values cannot be deleted or modified using the Quick Create
functionality. Quick Create can only reference previously created element properties.
Elements
To assign an existing Element Property set to any newly created elements, select a property using the
Existing ... button. If the Show Properties toggle is set ON, when an existing element property set is
selected, the appropriate Input Data form is presented. Element property values may not be altered. After
580
the Element Property set is selected, the Quick Create form is updated to reflect the currently selected
property set. If a property is not selected for automatic assignment to created elements, the main form
displays Property: None Selected. If elements are created and no existing Element Property set is
identified for automatic assignment, then the elements are simply created without reference to any
Element Property set.
Properties
This Object provides access to create Element Properties without having to access the Element Properties
application. Simply supply a Property Name, set the Dimension, Type, and other options as necessary.
Open the Input Properties form and input the data. Then press the Apply button. Unlike the Element
Properties application, no application region is provided. Only the property set and its data are created.
Plot types for element properties are analogous to those used for making XY plots of element results, but
the X variable is limited to some type of distance.
582
In this application, all location data that is put on the plots is for the centroid of the element. The distance
between elements is calculated between centroids. The X, Y, and Z locations reported on a plot are the
centroid components.
Scalar Element Property Data
If the scalar element property is the same for the entire element, then that data value is reported on the
Property Data Plot.
If the scalar element property is different for different nodes of the element, then the code warns the user
and calculate an average value. If a finite element Field is used to define the scalar element property, then
the code averages all of the node data together to obtain a value. If the Field is any other type, the code
evaluates the Field at the centroid location of the element and report this value on the plot. The functions
used to evaluate the field are the same ones used by Patran to evaluate Fields, as a result the interpolation
methods specified for the Field are used to evaluate that Field.
Limitations
1. Bar and beam properties, as defined using the Beam Section capabilities, are not supported.
Specifically, if the beam "Dimensions" option is used to derive the properties on-the-fly, these
may not be plotted. If, however, the beam "Properties" option is used to calculate beam properties
from a section definition, then these properties may be displayed. (If the beam properties are
grayed out on the Element Property - Input Data form, they may not be used for Property Data
Plots.)
2. Material properties are not supported.
3. Derived properties are not supported.
Example Of Usage
Visualizing the properties of elements verses a spacial variable can be helpful in verifying the simulation
model. This section gives an example of the usage of the properties vs. location plotting capabilities. This
example uses a simplified wing model to illustrate the use of the property XY plotting application.
The following figure shows the simplified wing model that was used for this example. This model has
varying thicknesses for the plate elements that make up the wing.
584
Thickness.
Press the OK button to close the subordinate form.
4. In the Selected Window databox enter the name of the window that the curves are plotted to
Thickness XY Plot.
5. Select the way curves currently in the Selected XY plot window are to be handled using the option
menu As Is.
6. Press the Apply button to generate the curve.
For this example, the above procedure is repeated, except in Step one X is selected instead of Dist. After
this is finished the XY plot should appear as follows:
Mass Property
Management
586
Set the Action to Create and Object to Mass Prop Region. Select the By
Groups method.
Group
Select the groups from which the mass properties regions are to be created in
the Group frame.
Description
Mass Factors
Enter the factors in the Mass Factors scroll frame. For each mass factor, select
the Enter Value option and enter the value of the factor in the databox. The
Parameter List option is available only if the Mass Properties function has
been customized by the user (see Mass Properties Customization and Mass
Factor Customization sections below). The date and time the factor is entered
are recorded automatically.
Apply
Select Apply to create the Mass Properties Region. The Mass Properties
Region always has the same name as the group from which it was created.
Set the Action to Create and Object to Mass Prop Region. Select the By
Selection method.
Mass Properties
Region
Enter the Mass Properties Region name in the Region Name databox.
Region Definition
Select the Region Definition button to display a subform which are used to
select the groups which are used to create the Mass Properties Region.
Groups
Select the groups which comprises the Mass Properties Region from the
Groups listbox in the Define Region subform. Select OK to accept the groups
selected.
Description
Mass Factors
Enter the Mass Factors in the Mass Factors scroll frame. For each mass factor,
select the Enter Value option and enter the value of the factor in the databox.
The Parameter List option is available only if the Mass Properties function has
been customized by the user (see Mass Properties Customization and Mass
Factor Customization sections). The date and time the factor was entered and
recorded automatically.
Apply
Mass Properties
Region
Region Definition
Select the Region Definition button to bring up a subform which allows you
to change the group or groups from which the region is created. Groups can
be added to or removed from the Mass Properties Region.
Mass Factors
Use the Mass Factors scroll frame to change the Mass Factors. For each mass
factor to be changed, select the Enter Value option and enter the new value of
the factor in the databox. The Parameter List option is available only if the
Mass Properties function has been customized by the user (see Mass
Properties Customization and Mass Factor Customization sections).
The date and time the factor was changed are recorded automatically. The
Mass Properties Region description cannot be changed.
Description
Apply
588
Mass Properties
Apply
Apply
Mass Properties
Region
Accept
Mass Properties
Region
Region Definition
Select the Region Definition button to bring up a subform which displays the
group from which the region is created.
Mass Factors
Use the Mass Factors scroll frame to view the Mass Factors. The date and time
the factor was created or changed are displayed
Requirements
Before using the Mass Properties Management function, the finite elements to which mass factors are
applied must be grouped into regions that share factors. Use the Groups functionality to do this. Material
density for all elements with factors must also be defined in the Materials application when defining
materials associated to the elements.
Before customizing the Mass Properties Management function, the user must program forms and
algorithms for parameter lists. A separate function is required for each type of mass factor. See below for
more information.
Example of Usage
The following example illustrates the basic usage of the Mass Properties Management function.
Figure 11-1 represents a section of a wing structure, that is constructed utilizing three spars. The elements
of the wing have been grouped based on the structural components modeled. This example concentrates
on spar number 3 (Figure 11-2 and Figure 11-3), that has been grouped as spar3. The spar has been
further broken down into upper and lower spar caps (Figure 11-4), grouped as spar3.capu and
spar3.capl, a spar web (Figure 11-5), grouped as spar3.web, and the effective portions of the
upper and lower skins (Figure 11-6), grouped as spar3.skinu and spar3.skinl. The remaining
spars are similarly grouped.
The goal of this example is to apply mass factors to these groups.
Figure 11-1
590
Figure 11-2
Spar Number 3
Figure 11-3
Spar Number 3
Figure 11-4
Figure 11-5
Spar 3 Web
592
Figure 11-6
594
Users Custom
Algorithm Class (AC)
INIT:
Alg name, - register
alg class
algorithm name
register_alg:
and class
- Place alg name,
alg class name
give_alg_names:
RC.give_alg_names
- obtain list of
.
algs in class
Done.
variable
Alg list,
num of algs
Figure 11-7
Custom
Algorithm Class (AC)
Figure 11-8
Alg name
give_lst_names:
RC.give_lst_names.
- Find class for
.
alg in registry
.
exec_func(AC,
.
give_lists)
.
.
.
.
.
.
.
.
.
Alg name,
.
.
latest
.
.
lists,
.
.
.
.
.
List of
.
lists,
Figure 11-9
Custom
Algorithm Class (AC)
give_lists:
- get latest list
of instances from
user data
- Register lists
RC.register_lst
596
RC.give_factor
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Done.
Figure 11-10
give_factor:
- Find alg in
registry
- Finds class AC in
registry
- Place instance in
class variable
exec_func(AC,
send_factors)
List
.
.
.
.
Factor
.
array,
.
.
.
.
send_factors:
- obtain instance
RC.give_param_list
- obtain factors
for instance
- send factors to
registry
Facto
The following example serves as a skeleton for a class a user would need to set up to define a new
algorithm. The functions listed are required and should perform the functions listed by the comment
portions of the code:
#include massprop_appstrings.p
#DEFINE CLASSNAME
user_algname
#DEFINE CLASSNAME_QUOTED "user_algname"
CLASS CLASSNAME
/*
* The algorithm data management class handles all work
* involved in storing and retrieving data associated with
* an algorithm and its associated parameter lists. It:
*
- registers its availability and associated factor
*
types in a registry class
*
- interacts with the GUI used to set up the parameter
*
lists to store and retrieve list instances
*
- calculates and stores mass factors at the request of
*
the mass region, via a "registry class"
*
- gives a list of available parameter lists, at the
*
request of the mass region via a "registry class"
*
- provides mass factors as requested
*/
FUNCTION init()
/*
* Purpose:
*
- Register algorithm in registry class:
*
- Register types of factors in registry class
*
- Create user data templates, if they dont exist
*
* Input:
*
(none)
* Output:
*
(none)
*
* Side Effects:
*
- Lets mass region GUI know that a new algorithm is
*
available, and will thus appear on the list of available
*
algorithms.
*
- Sets up templates for later data storage
*
* External Dependencies:
*
Need user data functions to store data
*
Need registry class to keep track of available
*
algorithms.
*
* General Description:
*
To be called in the init.pcl when starting up PATRAN,
*
or any other customized PATRAN initialization
*/
REGISTER_CLASSNAME.register_alg( @
/* algorithm name STRING */
algorithm_name, @
/* current class name STRING */
CLASSNAME_QUOTED)
REGISTER_CLASSNAME.register_asg( @
/* algorithm name STRING */
algorithm_name,@
/* factor types STRING ARRAY */
fact_types,@
/* number factor types INTEGER */ num_types)
IF( !template exists) ud_create_template(...)
END FUNCTION /* init */
/*
* A series of routines will follow here to manage the
* data, as needed by the GUI and the various templates
* associated with the algorithm. At minimum, this
* will include store,delete, and get functions for the
* parameter list.
*/
FUNCTION store_data
END FUNCTION /* store_data */
FUNCTION delete_data
END FUNCTION /* delete_data */
FUNCTION get_data
END FUNCTION /* get_data */
FUNCTION calculate_factors ()
/*
* Purpose:
*
- Needed only if it is necessary to be able to
*
initiate factor calculation from the mass region
*
form.
*
- Calculate massproperty factors
*
- Store factors in the parameter list used to
*
calculate them
598
*
* Input:
*
(none)
* Output:
*
(none)
*
* Side Effects:
*
- Modifies parameter list instance
*
* External Dependencies:
*
- Called by mass region class
*
- Calls routine in mass region class to get current
*
instance
*
* General Description:
* The calc factors function is called by the Mass Properties
* region when a factor is needed, using
* ui_exec_function(smdl_algname,"calculate_factors").
* It calls back to the Mass Properties region to get the
* name of the instance for which the factor is to be
* calculated, and then calls the algorithm to calculate
* the factors. It stores the factors in the parameter
* list once they are calculated.
*/
smdl_mass_region.give_current_instance(current_instance)
/*
* Calculate factors using whatever functions are needed.
* This can be done here or another call can be made.
*/
/*
*
*
*
*
*
*
*
*/
*
*
*
*
*
*
*
*/
The number and names of the mass factors displayed in the Mass Properties Management forms are set
by calls to the function smdl_uil_massprop_setup. Users may customize the mass factors by
writing their own function of the same name and reading it in so that it replaces the standard function.
The text of the standard function follows as a template for customization:
FUNCTION smdl_uil_massprop_setup(num_props,names)
$
$ Purpose:
$
Establish the number and names of mass factors
$
$ Input:
$
<none>
$
600
$
$
$
$
$
$
$
$
$
$
$
Output:
/* Number of mass factors */
/* Names of the mass factors */
INTEGER num_props
STRING names[]()
Side Effects:
External Dependencies:
General Description:
Notes:
Mass factor names must be 32 characters or fewer
INTEGER retval = 0
write("Initializing Mass Factor variables")
/*
* Change this number to increase the number of factors
* The maximum number of factors is 10
*/
num_props = 3
IF ( num_props <= 0 ) THEN
retval = -1
ELSE
sys_allocate_array(names,1,num_props)
/*
* The number
*/
names(1)
names(2)
names(3)
END IF
RETURN retval
END FUNCTION
The following are examples of subforms using the ability to assign factors by customized parameter list
calculations.
Select Algorithm
Available Algorithms
sheet_metal_part
machined_part
cast_part
Ok
Select List
Available Parameter Lists
rib 1
rib 2
skin
Assignment Type
Available Assignment types
Global
Lower Cap
Lower Skin
Upper Cap
Upper Skin
Web
Ok
Ok
602
Tools>Modeling>Assembly>Configurations
Configurations
Tools>Modeling>Assembly>Configurations
Configurations
Configurations
Overview
The Assembly and Configuration module is used during analysis to manipulate parts of a structure into
new positions without changing the original model. This can be used to analyze any structure with
moving components, such as an aircraft with control surfaces or an actuated arm on a back-hoe. The
transformations are performed automatically when a job is submitted and the results are viewed on the
undeformed model.
Procedure
1. Set the Action to Create and Object to Configurations
2. Define the configuration from: the group to be transformed, the load cases to be moved with it,
and how the transformation is to take place. Any intermediate structure MUST be a subset of the
group being transformed. Give it a name and select Apply. Repeat until you have created all the
configurations you need for your job.
3. From the Configurations form, set the Action to Associate and Object to Configurations
4. Link the configurations you have defined to the load cases by selecting the load case and then the
configurations associated with it. Use the switch labeled Configure Automatically to turn on and
off automatic manipulation of the model during job submittal. If the switch is disabled, a type of
check run is performed where all the appropriate subcases are formed, but none of the defined
configurations occur. Only one analysis job is submitted for this check run versus one for each
configuration if the switch is enabled. Select Apply to save the configuration to load case link and
the setting of the Configure Automatically switch.
5. Configuration of the model is performed on a copy of the database when the job is submitted. The
results are read back into the baseline model (initial configuration).
Requirements and Limitations
1. Configurations definitions can be defined using standard Patran. But to make an actual MSC
Nastran input deck of the configuration, Patran must be initiated with the -ifile init_sm.pcl
command flag such that Patran initiates in SuperModel mode. Then from the main SuperModel
menu, select Assembly and Analysis and the job must be submitted with the Submit Action in the
Analyze form.
2. If you are submitting a merged model, the configurations must be defined in the submodels that
have the rotating and/or translating pieces.
3. Any intermediate structure MUST be a subset of the group being transformed. The intermediate
structure connects the moving structure to the static structure (i.e., an actuator of a wing flap). It
also must be a single element, connecting the rotating structure to the parent structure; i.e. any
actuators must be modeled using a single bar element. There is currently no check to confirm
Tools>Modeling>Assembly>Configurations 603
Configurations
either of these circumstances. In addition, element properties of intermediate structure do not get
rotated along with the elements, so property definitions for the intermediate elements should be
valid for any position in the rotation plane. For example, when bar properties are defined, the
vector used to orient the beam should be parallel to the rotation axis.
4. Geometry in the intermediate structure is not reconnected along with the FEM. This makes the
model look different than what you would expect when you watch it move during an interactive
submittal, but does not affect the finite element run.
5. You must have the switch Configure Automatically toggled ON (from the Associate
Configuration action and object) for the configuration to be performed automatically.
6. The module does not currently have a capability to perform chained rotations, i.e. transformations
of parts of larger pieces that are themselves transformed. Examples of this would be a trim tab on
an airplane flap or a claw on the end of a rotating arm.
7. Loads and boundary conditions on rotating components MUST be carefully applied. LBCs
applied to the finite element mesh are correctly transformed. LBCs applied to the geometry, that
is not part of the transformed group, is not properly applied to the transformed finite element
mesh. In addition, the LBC set name used for the loads on the component must be unique so that
it does not get renamed during the merge.
8. Currently, the capability does NOT exist to preview the transformation. If you want to check the
transformation, you need to submit the job and watch it take place, or create a new model from
the MSC Nastran results file.
Technical Operation
When you submit a job through SuperModel (action Submit on the Analysis form), the configuration
module looks at the load cases for any associated configurations. Based on the configurations, a job is
created for the different combinations of configurations. For example, if you submit an analysis of an
airplane with the following subcases (load cases) and the listed associated configurations:
Load Case:
Takeoff
Landing
Pull up
Cruise 1
Cruise 2
Configs:
flaps_up
flaps_down
flaps_up
(none)
(none)
gear_down
gear_down
This is done because no two other load cases share common sets of configurations.
The configuration routines make a copy of the database before submitting the job and do all
manipulations in this copy. Instructions are sent to the Analysis Manager to read the results back into the
604
Tools>Modeling>Assembly>Configurations
Configurations
original (initial configuration) database when submitting the job for a full run. SuperModel requires
Analysis Manager when submitting full runs.
Component Transformation
The configuration module performs component transformation using the Group Transformation
functionality in Patran. The module uses settings in this function to delete the original group and use
original entity IDs where possible, and also transforms the Element Properties. You are given the option
to copy or transform Loads and Boundary Condition sets along with the group, as well as the opportunity
to specify those specific load sets that is affected. However, this is currently only valid for vector-type
loads, such as forces and moments.
Configuration Synchronization
If you have PCL functions to integrate with the configuration process, they must be registered. An
example of this would be a function to check the load balance on a model before and after transformation,
and to apply a corrective load to maintain the balance. Functions can be called both immediately before
and after the configuration. The following call is used to register those functions:
cgsa_submdl_sync_mgr.register
Function
Function called to register a function for execution. Execution will be performed via a ui_exec_function(user_class_name,
user_func_name)
Input:
STRING[]
when
STRING[]
user_class_name
STRING[]
user_func_name
Function to execute
<Return Value>
Output:
INTEGER
Because information cannot be passed when the configuration class calls your function, you must call
back to it to get information about the transformation. The following function can be used to get that
information.
Tools>Modeling>Assembly>Configurations 605
Configurations
cgsa_submdl_sync_mgr.get_config_info
Input:
None.
Output:
STRING[]
config_name
Name of configuration
STRING[]
group
STRING[]
method
STRING[]
params
STRING[]()
load_sets
INTEGER
num_load_sets
STRING[]
lbc_movement
STRING[]()
load_cases
INTEGER
num_load_cases
INTEGER
<Return Value>
In the routine from which you call this function, you should include the file jobdef_appstrings.p
and declare your arguments as follows:
STRING
config_name[MAX_CONFIG_NAME_LEN]
STRING
group[MAX_GROUP_NAME_LEN]
STRING
method[VIRTUAL]
STRING
params[VIRTUAL](TRANSFORM_PARAMS)
STRING
load_sets[MAX_LBC_NAME_LEN](VIRTUAL)
INTEGER
num_load_sets
STRING
lbc_movment[MAX_MOVE_LEN]
STRING
load_cases[load case_LEN]
If the jobdef_appstrings.p include file is not available, the following values may be used:
MAX_CONFIG_NAME_LEN
32
MAX_GROUP_NAME_LEN
32
TRANSFORM_PARAMS
6
MAX_LBC_NAME_LEN
32
MAX_MOVE_LEN
9
LOADCASE_LEN
80
606
Tools>Modeling>Assembly>Configurations
Configurations
The following form is used to create a new configuration, which must then be associated with a load case
to be performed.
For the intermediate structure to be reconnected after the configuration, select a group containing
elements connecting the transformed group to the rest of the structure. The intermediate structure MUST
be a subgroup of the target group being transformed, and also MUST be a single element connecting the
transformed structure to the parent structure. Properties for the element do not get transformed, therefore,
make sure that the property definition is either non-directional or is defined in such a way that it is still
correct after the transformation takes place. With bars, this can be done by making the vector used to
define the bar orientation parallel to the rotation axis.
The information defined for each transformation technique correlates to that required for the Patran
Group/Transform.
Tools>Modeling>Assembly>Configurations 607
Configurations
608
Tools>Modeling>Assembly>Configurations
Configurations
Deleting a Configuration
Tools>Modeling>Assembly>Configurations 609
Configurations
610
Tools>Modeling>Assembly>Configurations
Configurations
Example
Figure 11-11 shows an example on how to rotate the flap structure attached to the wingbox on the right
side of the model. The flap will be rotated down 10 degrees about the hinge line axis defined by points
(85, 80, 0) and (100, 80, 0).
Figure 11-11
Tools>Modeling>Assembly>Configurations 611
Configurations
612
Tools>Modeling>Assembly>Configurations
Configurations
If you submit the job interactively, you will be able to see the model transform to reflect the analyzed
configuration model for evaluation. Answers for the configured model are read back into the original
database (initial configuration). If you want to view the reconfigured model, you must create a new model
by reading the results and model information from the results file into an empty database.
Figure 11-12
Tools>Modeling>Assembly>Reduced
Mass/Stiffness
Reduced Mass/Stiffness
Reduced Mass/Stiffness
Assembly and configuration tools are commonly utilized in aerospace. Design studies often focus on
changes to a single component (i.e., aircraft wing) while the remaining components retain a constant
design (e.g., the fuselage, vertical tail, etc.). Each design study requires a structural analysis or analyses
to understand the effect of the changes. Depending on model sizes and computing costs, a high penalty
on throughput and costs can be realized by analyzing structure that does not change between design
studies. To increase throughput and potentially decrease computing costs, users may employ the reduced
stiffness and mass modeling technology.
Reduced stiffness and mass modeling can substantially decrease model analysis time by reducing the
total number of degrees of freedom. Reduced stiffness and mass models created from one or more
components can be used during analysis as a boundary condition to the attached structure. For example,
a stiffness matrix can be generated for an aircraft fuselage and subsequent design studies and re-analysis
of the wing model can use this reduced model as the boundary condition at its root and eliminate the need
and time necessary to redundantly analyze the fuselage structure.
Use of the reduced stiffness and mass models is similar to the MSC Nastran Superelement technology,
but more simplified. Less bookkeeping is associated with its use; however results cannot be recovered
from elements in the reduced structure.
A reduced stiffness matrix (RSM) represents the stiffness matrix of a component at degrees of freedom
specified by the user, and a reduced mass matrix (RMM) performs the same function for mass
information.
A set of user interface forms allow for the creation and inclusion of reduced stiffness and mass models
in an analysis. The actual RSM/RMM data is stored in physical files, named by the user. These
RSM/RMM files use (by default) the MSC Nastran OUTPUT4 format. However, the OP2 and DMIG file
format is also supported. A new entity is created and stored in the model database; its definition contains
all of the information needed to create and include RSM/RMM in subsequent models.
A reduced stiffness or mass matrix definition consists of an ordered list of degrees of freedom that are
contained in the stiffness/mass matrix, the filename containing the matrix, the type of matrix (stiffness or
mass), and the degrees of freedom map.
When a new RSM is created, Patran creates a model file, with the extension .gnl, and a companion file
with the extension .gnl.def.
RSM Procedure
This section discusses the procedure of first creating an RSM and then its subsequent usage. Brief
references to user interface forms are made, which are described in the following section. A detailed
example follows the user interface discussion.
614
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
The figure above can be used to discuss several key points with respect to RSM creation and usage.
Nodes 1-4 are always fixed. These are not required to be included in the boundary description of
the RSM; rather, the user must verify that the proper elements attached to these nodes are
included. Additionally, the clamped boundary condition must be included in the RSM analysis
job to permanently constrain these nodes.
Warning: While permanent constraints are supported, these are not always recommended as
node constraints such as rigid bars and multi-point constraints can introduce singularities into the
stiffness matrix. The most safe modeling technique is a free-free structure where nodes 1-4 are
included in the RSM boundary description and the clamped boundary condition is applied when
the RSM is included in an analysis with the adjacent structure. For more information on
inclusion of boundary conditions on a free-free structure, please see note 4 below.
Nodes 9 - 11 must be included in the RSM boundary description. The user is asked to define the
boundary description. Typically all 6 DOFs at each node are included. Multiple load conditions
are supported and must be included in the analysis where the RSM is attached to the adjacent
structure.
Nodes 5 - 9 have an applied, variable boundary condition. Therefore, these nodes must be
included in the RSM description. Typically all 6 DOFs at each node are included. Multiple
boundary conditions are referenced in the subsequent analysis where the RSM is attached to the
adjacent structure. If a static boundary condition is also present (like the clamped condition
shown above), the boundary condition for each analysis would include both the clamped and
variable condition, as shown above.
If multiple RSMs are to be created from an original database, steps 1 - 3 must be repeated
for each RSM. Step 1 can be performed for each RSM prior to the remaining steps. Steps 2
and 3 must be performed once for each RSM.
To create an RSM definition from a finite element model, as shown above, use the
following procedures.
1. Create a manual, type Write RSM.
2. Identify the boundary nodes in any order, along with their associated DOFs.
3. Specify whether the stiffness or stiffness and mass representation is to be created.
4. Identify a file name where the RSM data is to be stored.
To activate an RSM definition, or queue an RSM definition for a subsequent analysis job, use the
following procedures.
1. Activate an RSM by selecting it from the list of RSMs. This queues the RSM definition to be
included in the next analysis job, creating an RSM.
2. Only one RSM may be activated (queued) for creating in the analysis step.
To create an RSM from an RSM definition, use the following procedures.
1. Go to the Patran Analysis form. The action must be Analyze.
2. If a permanent boundary condition is to be included, select the appropriate Load Case. Only one
Load Case may be submitted for analysis.
3. If the RSM is to be created from a portion of a larger finite element model, select the appropriate
groups for analysis. For example, make the RSM Group current and then use the Current Group
option.
4. Submit the analysis. Three physical files are created and stored under the single logical file name
defined during the RSM definition phase.
To use an RSM in an analysis requires four steps:
1. Load the RSM into the opened adjacent structure database. Use the From File Method. An RSM
definition should only be loaded into one adjacent structure database; multiple references
results in an error condition.
616
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
defined tolerance. If the adjacent structure attach points have associated analysis coordinate
systems that are in conflict with the incoming RSM. The RSM analysis coordinate systems
overrides the adjacent structure definitions.
If nodes are not present in the adjacent structure database where the RSM connection points
in the next analysis job that contains the adjacent structure database.
To apply load and boundary conditions to RSMs, use the following procedures.
1. After the RSMs are either defined or activated in the adjacent structure database, the previously
identified boundary nodes are present. The node numbers are most likely be different than when
first defined because they are identified by spatial location and not physical node number.
2. Create load and boundary conditions definitions on the boundary nodes, as is customary in a
standard Patran modeling session. The associated Load Cases must be identified during analysis
job submittal.
To use one or more RSMs in an analysis, use the following procedures.
1. Go to the Patran Analysis form. The Analysis Action must be Analze.
2. Select the appropriate Load Cases.
3. Submit the analysis. Any activated RSMs in the submodels included in the analysis are used.
Recall from the above discussion, the most common method to first create an RSM definition is using
the Method Manual and Type Write. If this has been previously done, and for some reason the RSM
definition file (rsm_name.gnl.def) does not exist, reconstruct the RSM definition. Use the
following procedure when manually creating an RSM definition by using the option Type =
Read.
1. Set the RSM action to Create, Object to RSM Definition and Method to Manual.
2. Set the Type to Read.
3. Select the boundary nodes in sorted (ascending) order. Recall the selection order when creating
an RSM Definition using Type = Write was not important. The order is important after the RSM
exists because MSC Nastran sorts the nodes in ascending order prior to creation of the RSM file
and RSM Definition file.
4. For each selected node, identify the DOFs used in the original RSM definition.
5. Note that the analysis coordinate systems at each node must also correspond to those from the
original definition.
6. Select the original RSM file (rsm_name.gnl).
7. Create the RSM definition.
The user interface to the functionality described above is described in the following pages.
RSM User Interface
The Reduced Stiffness and Mass Modeling capability is accessible from the Tools pull down menu, as
shown below.
Create Reduced Stiffness and Mass Model Definition
To first create a reduced stiffness and mass model definition, set the Action to Create, Object to RSM and
Method to Manual. The other available Method is From File; this is used to load a previously created
RSM definition into its adjacent structure database; this is discussed later.
618
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
Note:
When the RSM Type is set to Write (create a new stiffness/mass matrix), the order of the
list of degrees of freedom and the mapping of the degrees of freedom is ignored (MSC
Nastran ASET cards are not order dependent). The order of the RSM/RMM created by
MSC Nastran are in increasing node ID, based on the matched nodes at the defined spatial
locations.
If an RSM definition file is lost, but the associated RSM file is present, the definition file can be
reconstructed. The following shows the Create/RSM/Manual form using the RSM Type Read.
Note:
When the RSM Type is set to Read, the degrees of freedom order and mapping are used to
determine the MSC Nastran DMIG card sequencing. The selected nodes must exactly
match the ascending order of the originally selected boundary nodes. Additionally, the
associated nodal DOFs and analysis coordinate system must exactly match the original
definitions.
The following form is used to define the DOF list associated with a RSM and appears when the DOF List
Definition button on the Create (and Modify) form is selected.
620
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
The following form appears when the Select Output (or Input) File button on the Create/RSM/Manual
form is selected. This form is used to select the input or output matrix filename for the RSM definition.
The RSM/RMM OP4 file by convention should have a .gnl extension. When entering a name for the
RSM/RMM input file the .gnl extension should be added by the user.
To use one or more RSMs in an analysis, they must be included in an adjacent structure database. The
method to include these previously constructed RSMs is described. Set the Action to Create, Object to
RSM Definition and Method to From File. Any new nodes and coordinate systems needed for the RSM
definition is automatically generated. The Create/From File form appears as follows:
A file browser form appears when the Select RSM Definition File button on the Create/RSM/From File
form is selected.
622
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
The Modify/RSM Definition form only allows for manual modification of a RSM definition.
The Delete form is used to remove RSM definitions from the database.
624
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
Activating an RSM is equivalent to queueing it up for use in the next analysis job submittal. Note that
when first creating an RSM (Manual, type Write), only one type Write RSM may be activated (queued)
for a subsequent analysis job, while multiple read type RSMs may be activated. Multiple RSMs may be
activated for actual use in an analysis.
The Activate RSM form appears as follows.
626
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
628
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
MSC Nastran has the ability to reduce a models stiffness and mass information to a specified set of
DOFs. These DOFs are specified in the MSC Nastran ASET cards. The reduced stiffness matrix
assembled at these DOFs (e.g., a fuselage model reduced to the DOFs where the wing is attached) can
be written out to a file. It is later read in and added to the stiffness matrix for an associated structure (e.g.,
the wing model) using DMIG cards and appropriate DMAP alters. This technique stores the minimum
information needed to account for the boundary conditions at the attachment. The analysis of the
following simplified portion of a canopy and fuselage illustrates the above discussion.
The goal with this model is to analyze the canopy separately from the fuselage. Loads and boundary
conditions include both symmetric and anti-symmetric cases, axial compression (symmetric) and up- or
down- bending (anti-symmetric about XY plane).
630
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
The fuselage model is created by itself in a database (See Figure 11-13). The boundary conditions are
applied only where they will not change. At the corner nodes (44, 48, 33, 11), where a constant boundary
condition meets a load or boundary condition that will change, no constraints should be applied. These
constraints will be applied in the canopy model. None of the loads will be applied to this model so they
can be changed when analyzing the canopy.
Figure 11-13
Fuselage Model
After the model has been created, the RSM must be created. This is done from the Create/RSM form.
To create an RSM:
1. Enter the RSM name fuselage in the RSM name box.
2. Select the Write toggle for the RSM Type.
3. Press the DOF List Definition button.
Select all of the DOF toggles.
Select the DOF coordinate system (Coord 0)
Select the nodes 1:11, 12, 23, 27, 34,38,39,43,44,48 to be added to the RSM definition. For
the Write RSM Type the order that the nodes appear in the list is ignored.
Press the Display Current List button and check that the correct locations have been selected.
The model should look like Figure 11-14.
Press the OK button to accept the DOF list.
Figure 11-14
4. Select the Stiffness Only toggle. If a dynamic analysis is to be performed, a mass representation
is also required.
5. Press the Select Output File button.
Input the name fuselage.gnl for the file to contain the RSM/RMM data. (In general this
632
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
7. Press OK to make selections for Write RSM to Create and close the form.
8. Confirm that the RSM fuselage appears in the Active Write RSM Definitons list box located on
the Active RSM Definition main form.
9. Press Apply to activate.
10. Press OK to make selection and close out form.
11. Confirm that the RSM fuselage appears in the Active Write RSM Definitions list box located on
the Activate RSM Definition main form.
12. Press Apply to enable activation.
Now that the RSM has been selected, an MSC Nastran job must be run to generate the RSM/RMM file.
This is done using the same procedure to run any job. The job must consist of only one subcase that
contains any boundary conditions and loads that are to be applied to the model. The solution sequence
must be SOL 101, if the RSM is to produce only a stiffness matrix, or SOL 103, if the RSM definition is
to produce both stiffness and mass matrices.
The canopy model is created by itself in a database. The boundary conditions are applied to the model as
needed. At node 29 the top symmetry conditions are applied and at node 44 right side symmetry
conditions are applied because these were not applied to the fuselage model at these nodes (see
Figure 11-15).
Figure 11-15
Canopy Model
After the model has been created, the RSM must be created. First, the order that the nodes appears in the
DOFs list must be determined. When a RSM/RMM file is created the order of the nodes in the file is
determined by the node numbering. The order is from the lowest node number to the highest node
number. When a RSM/RMM file is read in, this order must be maintained. To be able to read in the
RSM/RMM file correctly, the model that generated the RSM/RMM file must be compared to the model
that reads in the model. The order of the nodes in the new DOFs list is determined by matching the order
of the nodes in the original model to the corresponding nodes in the new model.
In this example the following correspondences between nodes are found:
Fuselage Model
Canopy Model
Fuselage Model
Canopy Model
node 1
node 34
node 27
node 1
node 2
node 35
node 28
node 2
node 3
node 36
node 29
node 3
634
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
Fuselage Model
Canopy Model
Fuselage Model
Canopy Model
node 4
node 37
node 30
node 4
node 5
node 38
node 31
node 5
node 6
node 39
node 32
node 6
node 7
node 40
node 33
node 7
node 8
node 41
node 34
node 31
node 9
node 42
node 38
node 8
node 10
node 43
node 39
node 30
node 11
node 44
node 43
node 15
node 12
node 33
node 44
node 29
node 23
node 32
node 48
node 22
The list gives the order that the nodes must be in for the canopy model to correctly read in the RSM/RMM
file. This order must be used when defining the RSM.
Now an RSM must be created. This is done from the Create RSM form.
To create a RSM:
1. Enter the name fuselage.
2. Select the Read toggle for the RSM Type.
3. Press the DOF List Definition button. (This brings up the Define DOF List Form.)
Select the all the DOF toggles.
Select the DOF coordinate system (Coord 0)
Select the nodes 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 33, 32, 1, 2, 3, 4, 5, 6, 7, 31, 8, 30,
15, 29, 22 to be added to the RSM Definition. For the Read RSM Type the order that the nodes
appear in the list must be the same as the order of the corresponding nodes in the RSM/RMM
file.
Press the Display Current List button and check that the correct nodes have been selected. The
6. Set the DOF mapping to the appropriate settings. When a RSM/RMM file is generated, the order
of the DOFs is UX, UY, UZ, RX, RY, RZ. This option lets you change this order. If the global
coordinate system is oriented the same way relative to the model in both the database that
generated the RSM/RMM file and the database that reads in the RSM/RMM file, then the DOF
mapping should be X to X, Y to Y, and Z to Z. If the orientation is not the same, then the mapping
needs to be different. For this example the mapping is X to X, Y to Y, and Z to Z.
7. Press the Apply button. This defines the RSM definition.
636
Tools>Modeling>Assembly>Reduced Mass/Stiffness
Reduced Mass/Stiffness
For this option, create the canopy model and all the nodes to be loaded or have Boundary conditions
applied to them. Do not create any of the isolated nodes that are part of the RSM and do not have LBCs
applied to them. These nodes are automatically created when the job is submitted to MSC Nastran. After
the canopy model is created, the RSM must be generated. This is done for the Create/From File form.
To create the RSM definition:
1. Enter the name fuselage.
2. Press the Select General Definition File button.
Select the RSM/RMM companion file generated previously, fuselage.gnl.def.
Press the OK button to accept this filename.
3. Set the DOF Axis mapping to the appropriate settings. When the RSM/RMM file is generated, the
order of the DOFs is UX, UY, UZ, RX, RY, RZ and the RSM/RMM companion file has the node
locations of the DOFs in the coordinates of the original model. This option lets you change the
orientation of the RSMs global axis relative to the models global axis that is reading it in. If the
global coordinate system is oriented the same way relative to the model in both the database that
generated the RSM/RMM file and the database that reads in the RSM/RMM file, then the DOF
Axis mapping should be X to +X, Y to +Y, and Z to+ Z. If the orientation is not the same, then
the mapping needs to be different. For this example the mapping is X to +X, Y to +Y, and Z to +Z.
4. Press the Apply button. This defines the RSM.
After the RSM is created, the nodes that were part of the RSM and not part of the canopy exists. The
boundary conditions shown in Figure 11-15 should be applied to the model.
Activate the RSM
After the RSM has been created, it must be selected for use in an analysis run. This is done from the
Activate RSM form.
To activate the RSM:
1. Press Change Current Activation to open the MSC Nastran Activation subform.
2. Set Activation Type to Read RSM.
3. Select the RSM fuselage from the list box.
4. Select the Options button.
5. Select the matrice to write as well as the format of the matrices. Note that these selections must
match the types and format of the matrices that are contained in the .gnl file when the general
element was created.
6. Press OK to make selections and close out the Options subform.
7. Press OK to make selections for the Read RSMs that are to be activated and to close the form.
8. Confirm that the RSM fuselage displays in the Active Read RSM Definiton list box located on
the Active RSM Definition main form.
If an analysis is run with the Current Group option, then all of the nodes that are contained in the DOF
lists of the activated RSMs must be part of the current group.
Use of Dynamic Reduction with RSM/RMM Files.
When a Normal Modes solution is run with the RSM/RMM file reference, Dynamic Reduction must be
disabled. The Perform Dynamic Reduction toggle on the Dynamic Reduction subform must be set to the
off position.
Selecting Output Matrices
For dynamic analyses, both mass and stiffness matrices must be requested. Failure to do so will result in
a Patran fatal error at the the time of model translation and generation of the Nastran bulk data file.
Note selection of which output matrices to read to write must be made on both the SuperModel RSM
definition main form as well as on the RSM Activation Options subform. Selecting both mass and
stiffness on the main form and stiffness only on the Options subform will result in only in stiffness
matrices being written or read.
638
Tools>Modeling>Assembly>Model Unmerge
Model Unmerge
Tools>Modeling>Assembly>Model Unmerge
Model Unmerge
Model Unmerge
The Model Unmerge functionality provides the tools needed to extract component models and their
associated results from a large structural model.
You should start with an empty database when extracting components from a larger model. The selected
component groups and result cases are stored in the new database. The model database is then closed and
the starting database containing the extracted groups and result cases remain open.
Procedure
The Model Unmerge functionality is available from the Tools/Modeling/Assembly pull down menu.
1. Start with an empty database when extracting components and results from a larger model.
2. Use the Select Source Database button to bring up the file selection form.
3. Select the model database from which the Unmerge is to be performed.
4. Select the groups or submodels to be extracted from the model.
5. Select the results to be extracted from the model.
6. Use the Apply button at the bottom of the form to initiate the Unmerge process. Any Patran results
postprocessing tools can now be applied on the component model extracted from the larger
structure.
Requirements and Limitations
The following are the current known requirements and limitations of Model Unmerge:
1. You must start with an empty database when extracting submodels or groups and results from a
model.
2. Results are extracted for only those entities which are members of the selected groups.
3. Freebody calculations performed at adjacent structure boundaries of the selected groups are
incorrect.
Description of User Interface Forms
The Model Unmerge functionality is accessible from the Tools/Modeling/Assembly pull down menu.
The form has a button to select the model database from which the extraction is to be made and listboxes
for the selection of the desired groups and result cases to be extracted.
The Model Unmerge main form contains a button that allows the user access to a file selection interface.
You must start with an empty database and select the model database from which the data is to be
extracted. The user can extract data by either group or by submodel. The user may also extract both model
and results data or just model data only as shown on the next page.
If only model data is being extracted, then the following form will be displayed.
640
Tools>Modeling>Assembly>Model Unmerge
Model Unmerge
Example
An analysis of an airplane wing model has been performed. This analysis contains different structural
groups and different results cases. You wish to generate a display of one results case applied to only one
portion of the model (the flap). To do this, you must extract the flap and the results for the desired case.
Figure 11-16
642
Tools>Modeling>Assembly>Model Unmerge
Model Unmerge
Figure 11-17
Flap Submodel
Figure 11-18
4. Press the Select Source Database... button to bring up the file selection form and select the
database from which the structural groups and results cases are to be extracted. Select OK.
5. Select the desired structural groups and results cases from the listboxes and press Apply. The
selected groups and results cases are placed into the empty starting database.
6. You may now generate the desired results display using only the selected structural groups and
results cases.
644
Tools>Modeling>Experimental
Data Fitting
5. If you have cross-sectional area reduction data in the third column, you can give it an optional
field name also. You need to define and specify that you have this data. Otherwise a third column
is detected and two fields are created. This results in a _C1 and _C2 being appended to the given
field name.
6. If for some reason the independent and dependent columns need to be interchanged, you can turn
this toggle ON. Check your imported fields before proceeding to ensure they are correct. This is
done in the Fields application.
7. When you press the Apply button, you will be taken to the second step. If you need to import more
than one file, you will have to reset the Action pull-down.
Select Test Data
Once the raw test data is imported, you must associate with a particular test type or mode by following
these steps:
1. Put the cursor in the data field of the appropriate type of test.
2. Select associated field from the Select Material Test Data listbox that should have a list of the
imported raw data fields.
3. Repeat this for each test you wish to include in the calculations (curve fit).
Keep in mind the following points and considerations when selecting test data:
1. Typical stress-strain data for Deformation Mode tests are referenced in the Primary column. If
you have volumetric data, these are entered in the Secondary column databoxes and are optional.
2. For Viscoelastic (time relaxation data), you must turn ON the ViscoElastic toggle. Only
viscoelastic curve fitting will be done in this case. To return to Deformation Mode, turn this toggle
OFF.
3. Damage models are not yet supported.
4. When you press the Apply button, you will be taken to the third step.
Calculate Properties
Once test data has been associated to a test type or mode the curve fit function is performed by following
these steps:
1. Select the material Model you wish to curve to fit. The available models will depend on the test
data selected in the previous step. Hyperelastic models will be available for deformation mode
test data. Viscoelastic models will be available for relaxation test data.
2. In general you will leave Use Test Data to All for hyperelastic models. If however you only want
the curve fit to use one of the deformation modes, you may set it here.
3. Press the Compute button. The coefficient values will be displayed in the Coefficients
spreadsheet.
4. To visually see the curve fit, press the Plot button. You may repeat the above four steps for as
many material models as you wish to curve fit.
646
5. Select an existing material or type in a New Material Name and press the Apply button to save
the material model as either a Hyperelastic or Viscoelastic constitutive model for use in a
subsequent analysis.
Keep in mind the following points and considerations when calculating properties:
1. The plots are appended to the existing XY Window until you press the Unpost Plot button. You
can turn the Append function ON/OFF under the Plot Parameters... form.
2. By default, all the deformation modes are plotted along with the raw data even if raw data has not
been supplied for those modes. This is very important. These additional modes are predicted for
you. You should always know your models response to each mode of deformation due to the
different types of stress states. For example, a rule of thumb for natural rubber and some other
elastomers is that the tensile tension biaxial response should be about 1.5 to 2.5 times the uniaxial
tension response.
3. You can turn ON/OFF these additional modes or any of the curves under the Plot Parameters
button as well as change the appearance of plot. More control and formatting of the plot can be
done under the XY Plot application on the Patran application switch on the main form.
4. Viscoelastic constitutive models are useless without a Hyperelastic constitutive model also. Be
sure your model has both defined under the same material name if you use viscoelastic properties.
5. You may actually change the coefficient values in the Coefficients spread sheet if you wish to see
the effect they have on the curve fit. Select one of the cells with the coefficient you wish to change,
then type in a new coefficient value in the Coefficient Value data box and press the Return or
Enter key. Then press the Plot button again. If you press the Apply button, the new values will be
saved in the supplied material name.
6. For viscoelastic relaxation data, the Number of Terms used in the data fit should, as a rule of
thumb, be as many as there are decades of data.
7. A number of optional parameters are available to message the data and control the curve fitting.
See the table below for more detailed descriptions.
For more information, see Experimental Data Fitting (p. 127) in the Marc Preference GuideChapter 1:
Overview.
Tools>Modeling>Bolt Preload
Bolt Preload
This modeling tool allows you to facilitate the creation of bolt preloads and the associated MPCs. This
tool can be used for both Marc and MSC Nastran analyses as well as others that recognize explicit MPC
definitions.
Regardless of which method is used, the following operations are done to create each bolt pre-load.
1. The mesh of the bolt is split at the designated cutting plane. This cutting plane is either designated
by the user or determined by the tool. Coincident nodes are created for element nodes above and
below the plane and the element connectivities are regenerated.
2. MPCs are created to connect the two sections above and below the determined cutting plane. The
coincident nodes created in the previous step are tied together via MPCs. Either Overclosure type
or Explicit MPCs are created. Marc analysis and MSC Nastran SOL 600 typically use
Overclosure types which other analysis solutions or code can use Explicit MPCs.
3. A control node is created and connected to each set of node pairs. A coordinate system is created
at the specified control node location which can be offset as required for visualization purposes
4. A load or displacement is applied for the pre-load in the local Y direction (axial bolt direction) or
the coordinate system created at the control node location.
5. Each bolt pre-load is named and stored in the database.
6. Undo, Show and Delete capabilities are available.
Three methods to help you define the bolt pre-loads are available. Each has some specific inputs required.
All have common inputs some specific inputs for each method as explained below:
Geometric based
This is by far the easiest and most intuitive method to use. A set of elements is selected that defines the
bolt. Based on the geometric dimensions and Patrans mass property utilities, the most likely axial
direction of the bolt is determined. The mesh is split at the center of the selected element set. If the
geometric properties of the selected element set does not distinctly determine the axial direction of the
bolt, the cutting plane may not be determined correctly and a strange cut will result. At least a two to one
axial versus width ratio is recommended.
Vector based
This method requires that you define a vector, the base of which determines the location of the cutting
plane, which is normal to the defined vector. The element set selected must have a layer or two or three
element both above and below the base of the defined vector plane.
648
Tools>Modeling>Bolt Preload
Bolt Modeling and Preloads
Element based
This method may be more advantageous for certain element types in that you select element faces (3D),
element edges (2D), or elements (1D) where you want the mesh split and the MPCs applied. For 3D
elements, this can be difficult as the graphics screen can get messy trying to select element faces,
especially TET elements. For 2D and 1D elements, this method is easy. The split will occur only for the
selected element entities, which may be problematic if you only select a portion of the cross section.
Each input is described in the table below:
Action
Create
Delete
Delete an existing bolt preload. You can select an existing named bolt
preload or if you are not sure which one you want, you can set the
Method to Control Node and select the control node. It will figure out
which bolt preload is associated to the selected control node. Note that
any entities created by the bolt preload are deleted unless those entities
are modified by the user to reference other entities in some way.
Warning message are issued in those cases and some of the entities
such as the coordinates will not be deleted.
Identify
Identify allows you to select a control node and the name of the bolt
preload is returned as an informational message.
Show
Object
Method
MPC Type
Select the type of MPC required. You may not be given a choice
depending on the Analysis Preference set. Overclosure is the desired
method for MSC.Marc and MSC Nastran SOL 400/600. Other MSC
Nastran solutions and other analysis codes need Explicit MPCs
defined. For MSC.Marc, Overclosure creates TYING type 69 and
Explicit creates SERVO LINKs. For MSC Nastran SOL 400/600,
MBOLTUS entry is created for Overclosure for Nastran versions less
than 2010 or a BOLT entry for Nastran 2010 or higher. In all other
cases, Explicit MPCs should be used.
Method = Geometric
Element List
Select a list of elements that sufficiently defines the bolt geometry. The
axial direction of the bolt should be longer than the lateral directions
in order for the algorithm to determine the proper axial direction of the
bolt. The cutting plane will be created at the center of the bolt as best
as possible based on the element connectivity. The control node offset
will be created from the location of the cutting plane.
Method = Vector
Bolt Axis
This is a required vector input to define the axial direction of the bolt.
Typically you only need to use the select mechanism to define a vector
using two nodes on the outside of the bolt. You can use any method
that the select mechanism allows to define a vector. You may enter a
vector in any way the is allowable with the select mechanism or you
can manually type between the < > brackets a valid three-component
translational vector, e.g., <0, 5, 2>. In this method, you can define any
direction to do the cut and apply the preload. Care should be taken in
that some strange cuts may results. This is the method to use if you
wish to use a non-axial bolt preload.
Element List
For this method, select enough elements above and below the base of
the Bolt Axis vector such that a proper cut can be made. Two or three
layers of elements above and below is usually sufficient. An error may
result or a bad looking cut may be had if not enough element above and
below are given.
Method = Elemental
Target Element Type
In this method, you must select the element dimensionality of the bolt:
1D bars, 2D elements, or 3D solids.
Application Region
The application region defines the actual location where the split is
made. For 1D beam/bar elements, you select a single element and the
split is made at the bottom node. For 2D (2D solid) elements, you
select element edges that define the cut. For 3D elements, you select
the element faces to define the cut. All the element edges or faces need
to be connected together in order for this method to create a proper cut.
Use the FEM application and do a Verify / Element / Boundary to ensure that the bolt tool properly cut
the bolt into two sections with coincident nodes between.
650
Tools>Modeling>Rotor Dynamics
Preparing for Rotor Dynamics
Tools>Modeling>Rotor Dynamics
Rotor Dynamics
The new rotordynamics capability provides you with a relatively simple method of performing the design
and analysis of structures with rotating components. The new rotordynamic capability can be used in
frequency response (direct and modal), complex modes (direct and modal), static, nonlinear transient,
and linear transient (direct only) analyses.
For more information on Rotor Dynamics, see the Building a Model / Rotor Dynamics in the MSC
Nastran Structural Users Guide.
Tools>Modeling>NSM Properties
652
Tools>Modeling>Rebar Definitions
Creating Rebar Definitions
Tools>Modeling>Rebar Definitions
Rebar Definitions
Creates 2D layered rebar definitions for use with the MSC.Marc and ABAQUS Analysis Preferences.
Discrete rebar models and general 3d layered rebar models are not supported. Rebar is actually an
element property definition for the Preferences, however this tool is used to automate the creation of
rebar layers and embed them into existing element meshes. This tool allows you to:
Create, modify, delete and visualize Rebar data definitions.
Support multiple rebar definitions, both isoparametric and skew type geometry.
Support rebar membrane elements in 2D solid (plane strain and axisymmetric) elements.
Create a customized mesh and automatically assign rebar properties to these elements.
Note:
The Rebar Definition tool supports automatic generation of rebar elements and
properties for 2D solid elements only. For rebar embedded into 3D solid elements, you
must manually create the elements (mesh) and assign properties in the Element
Properties application using 2D Rebar Membrane definition. You can also manually
create 1D Rebar Membrane elements without using this tool but this is less convenient.
For more information please see Rebar Definition Tool (p. 182) in the Marc Preference Guide.
Action
Create/Modify
Create and Modify are identical. The only difference is that Modify
requires you to pick an existing rebar definition before you can
proceed.
654
Tools>Modeling>Rebar Definitions
Creating Rebar Definitions
Delete
Show
Object/Type
Supply a name for the rebar layer and select a color. Or pick an
existing rebar from the Existing Rebar... button.
Curve List
Material
Area/Spacing/
Orientation
Supply the cross sectional area, the spacing and the orientation in
these data boxes. If you press one of the buttons here, it will ask you
to provide a spatial field definition of these of these properties as they
vary along the curve length.
Clear
Press the Clear button to clear the fields and start over.
Tools>Modeling>Feature Recognition
Feature Recognition
This feature works from parasolid geometry.
1. Select the entity type and entities of interest and set the controls.
2. Then right-mouse-click on the features you want to recognize (holes, chamfers, blends) in the tree
widget.
This populates the tree widget with the recognized features.
3. Right mouse click on the features to show, edit, or delete them.
The Parasolid Kernel will fail to edit or delete a feature if there is a topological dependency on other
geometry. Multiple features can be deleted as long as all dependent features have also been selected for
deletion in the same operation.
The propagation controls get passed to the feature recognition APIs to control the type of recognition. In
other words, if you select Chain option for Blends and do Interactive recognition then it will do the
recognition and then perform chaining so finally you will get Blend Chains. Each Blend Chain may be a
combination of several individual Blends. To recognize each blend individually you can select the Single
option.
Recognize
Automatic these options are not used. For automatic recognition these
options have been set to default values of Hole - Single, Chamfer - Chain,
Blend - Chain.
These options are valid for Recognize - Interactive only and respective
values get passed through the second argument in the recognition API.
> status = ifr_recognize_blends_list(entity_list,
propagation, topology, $entity_type,
$number_of_features)
Recognize Automatic
656
Tools>Modeling>Feature Recognition
Recognizing and Editing Geometric Features
Recognize Interactive
Tools>Modeling>Contact Bodies/Pairs...
Contact Bodies/Pairs...
This functionality creates Deformable Bodies, Rigid Bodies, and Contact Body Pairs.
It automatically creates contact body pairs by determining if two bodies are close enough to be
considered a body pair based on the user defined distance tolerance. The name of contact pair also gets
generated automatically by combining the names of two bodies with suffix as _pair. If the contact pair
name is more than 31 characters, then the contact bodies names are truncated followed by assignment of
internal body IDs with suffix _pair. In this it is made sure that the contact pair name is unique.
It creates both Contact Bodies and Pairs when the analysis preference is MSC.Nastran and only
Deformable Bodies when the analysis preference is MSC.Marc. For other analysis preferences this
functionality is not available.
658
Tools>Modeling>Contact Bodies/Pairs...
Creating Contact Bodies/Pairs
Option
Description
Create
Creates Body Pairs or Deformable Bodies. Deformable Bodies are described in the
next section.
Distance Tolerance
The value of tolerable distance between body boundaries. All exterior node positions
of body 1 are compared with exterior node positions of body 2, and if any distance is
less than Distance Tolerance a body pair is created.
All Bodies
If selected, creates pair between any two bodies, both rigid and deformable.
Deformable Only
Create From
The options to consider are, bodies in the Entire Model, only those in the Current
Group, Current Viewport, or by selecting bodies manually. If the Select Bodies
button is opted, a list box icon appears. Click it to get the list of bodies, it displays All
Bodies or Deformable Only based on the option selected on the form.
Here you can specify contact property set for the body pair. The options are:
Default: Sets dummy or default physical and geometrical contact properties to all
body pairs created.
Individual: Individual physical and geometrical contact property will be created and
set to each pair created.
Specify: You can select existing properties or specify new geometrical and physical
properties to all contact pairs created.
Apply
Defaults
Cancel
Note:
Automatic Contact Body Pair creation is based on the FEM data. Contact Body Pair will
not be created with a rigid body that is not meshed.
Deformable Bodies
Option
Description
Create
Creates Body Pairs or Deformable Bodies. Rigid Bodies can also be created
using the Geometry method.
Method
Connectivity
Element Type
Groups
Properties
Materials
660
Tools>Modeling>Contact Bodies/Pairs...
Creating Contact Bodies/Pairs
Option
Geometry
Description
This method creates deformable and rigid bodies from geometry in the
entire model, current viewport, or current group. Each set of similar
geometry (curve, surface, or solid) that is connected will create a body. The
application type will remain geometry. It does not have to be meshed at the
time of body creation.
Select Create Rigid Bodies check box if you want to create rigid bodies.
Only 1D and 2D type geometry is allowed for the rigid bodies.
Create From
Entities in the entire model, in the current view port, or in the current group
are considered in the creation process. For batch mode, only the entire
model is applicable. In cases where specific entities can be selected, such
as groups, materials, properties, the list box appears for selection and
filtering.
Elements
Apply
Defaults
Cancel
Note:
Tools>Design Studies
Design Studies
Design Studies
Finite element analysis is seldom conducted as a single-run operation; frequently the process goes
through several iterations. In each iteration the model may be tweaked, some dimensions or other
properties of the model modified, and the analysis repeated until an optimal design is attained.
As a simple example, you may run a linear static plane stress problem with a certain thickness assigned
to the elements. If the stress and displacement outcomes are well within the acceptable range, you may
decide to reduce the element thickness, thereby decreasing the weight of the object, and run the analysis
again. You may continue refining the model through several iterations, until the weight reaches a
desirable minimized value without compromising the stress or other criteria.
This procedure can be automated through a series of design studies and, ultimately, design optimization.
A design study is a named event in which you specify the following:
the objective of the design study and of optimization--what do you want to achieve through
multiple iterations of the analysis process? Although there may be a number of possible
objectives, in the majority of structural analysis problems the objective of optimization is to
minimize the weight of the model.
the parameters of the model--which dimensions or properties may vary in order to achieve the
optimal design?
the constraints placed on the design study--what condition is a limiting factor in the optimization
process? For example, in the plane stress problem cited before, as the plate thickness is reduced
to decrease the weight, the thickness value must not become so small as to cause the plate to
deform beyond a given acceptable limit.
Variables
Variables are those parameters, or properties, whose magnitude will be modified in the process of
studying the solutions that can improve the design. The variable may be some dimension, an element
property (e.g., plate thickness, beam cross-section), or a material property. To perform studies for the
purpose of improving and optimizing a design through iterative solutions, you must parameterize the
model, that is, identify and label variables and set up possible relationships between them.
When you define a model variable, a corresponding field may be created as well. This field is a linear
function of the variable and it becomes available throughout Patran. Thus, if desired, it can be used to
define additional model properties. Any changes made to the variable will also change the properties
dependent on the field.
662
Tools>Design Studies>Pre-Process
Creating Design Studies
Tools>Design Studies>Pre-Process
This tool is used in conjunction with analysis setup of MSC Nastran SOL 200 optimization analyses. To
successfully run a SOL 200 job you must setup a design study. Design studies are then selected when a
SOL 200 job is submitted from the Analysis application. Please see Optimize (Ch. 3) in the Patran
Interface to MSC Nastran Preference Guide.
Before you can initiate a design study, you have to:
consider the objective, or goal of the design study and of optimization. Although there may be a
number of possible objectives, in the majority of structural analysis problems the objective of
optimization is to minimize the weight of the model.
parameterize the model. Define the variable dimensions or properties that may change in order
Important: Note on topology optimization versus sizing optimization. There are two
mechanisms to set up a topology optimization run.
The first is through the Analysis form with the Action set to Optimize. The Customized
Solutions form is used to turn ON topology optimization and define constraints, objectives,
domains, and optimization controls. The mechanism is referred to as Quick Topology
Optimization.
The second is through the definition of a design study using this tool. All constraints,
objectives, responses, etc. are defined and collected into a design study. Both sizing and
topology can be mixed in the same design study. This is referred to as General Topology
Optimization.
Quick Topology Optimization supersedes General Topology Optimization. If you wish to use
General Topology Optimization, please ensure that you have turned OFF the customized
solution topology optimization in the Analysis | Optimize | Customized Solutions... form and
that you select the design study and the objective/constraint of interest from the Design Study
Select... and the Global Obj/Cosntr Select forms.
Action
Object
Provides a textbox where you can enter a name for a new design study.
The name may consist of any number of alpha-numeric characters.
special symbols and spaces are not acceptable.
664
Tools>Design Studies>Pre-Process
Creating Design Studies
Description
Make Current
Makes the selected design study current. Only those design parameter
values that originate in a current design study can be used to update
finite element model properties.
You can modify a design study even if it is not current (the toggle is
not on), but the parameter values of the model will not be updated.
Modifications to a design study that is not current will not affect a
current design study.
Displays the Design Variables dialog box where you can review and
modify design variables (see Design Variables, 664).
Design Objective
Displays the Design Objective dialog box (see Design Objectives, 668)
and allows you to associates them to a design study.
Design Constraints
Constraint Sets
Displays a dialog box where you can associate them to a design study.
Max/Min...
Displays a dialog box where you can associate them to a design study.
Apply/Close
Saves or discards input. The design study will be saved only if you
press Apply.
Design Variables
A design variable is a model variable that is used in a design study and in optimization. You create model
variables when you create a design variable or you can select an existing model variable to create the
design variable. When you press Design Variables in the Design Study dialog box, a spreadsheet will
display a summary of variables and their attributes. Because initially every model variable is also
considered a design variable, the spreadsheet will contain all variables defined in a database.
With the exception of the parameter names and their default initial values, all other data in the spreadsheet
may be modified.
The first column contains the name of the variable. Subsequent column headings and their contents are
as follows:
Design Variable
A YES entry in this column confirms that the model variable is also a
design variable. If a variable is not to be used in the design study, you
can deselect it by clicking on the word YES. All variable
information for this item will be removed, indicating that the variable
is not a design variable, even though it is listed in the spreadsheet. To
toggle back to YES, click in the field again.
You can pick several consecutive items in this column at the same time
by dragging the cursor down the column.
A button will then appear at the top of the spreadsheet to show that the
current status is YES. Click on YES, to display the choices, pick NO,
then press the Enter (or Return) key, and the items will be deselected.
The button also works in the reverse (NO to YES).
Analysis Value
Displays the value you assigned to the variable when you defined it.
This value cannot be changed here.
666
Tools>Design Studies>Pre-Process
Creating Design Studies
Design Value
If you specify a new design value, the original lower and upper
boundary values will no longer be valid. Therefore, you will see the
following message:
Press Yes to acknowledge the warning. The new value will be entered
in the Design Value category and one or more of the boundary values
will change accordingly.
Lower Bound
Displays the lowest value the design variable may assume during the
design study/design optimization process. By default, this boundary is
set to 10% below the base value. To change the boundary value, click
in the appropriate field then enter the new value in the Input New
Value textbox.
Upper Bound
Displays the highest value the design variable may assume during the
design study/design optimization process. By default, this boundary is
set to 10% above the base value. To change the boundary value, click
in the appropriate field then enter the new value in the Input New
Value textbox.
Move Limit
Defaults
Resets all entries to their original value. Keeps the dialog box on the
screen.
OK/Cancel
Runs
Displays the names of the result cases, or runs, that were output by
iteratively performing analysis with different values of the variables.
Design Cycles
Design Variables
Values
Displays the values of the design variables for a selected design cycle.
To apply the results of a particular cycle of an analysis run in the design study, pick the name of the Run
then pick a Design Cycle. The design variable values of that run and cycle will be shown. Press OK to
accept the new values. When the Design Variables spreadsheet is redisplayed, the variables will be
updated to the new values.
Design Responses
Design responses are objectives or constraints. If you define a design response, you can select it to be
used as either an Design Objective or a Design Constraint later on. You can also group them together
under a MaxMin definition. The information necessary to define a design response is the same as that for
an objective or constraint. See Design Objectives, 668 and Design Constraints, 669 below.
668
Tools>Design Studies>Pre-Process
Creating Design Studies
Design Objectives
The design objective is the goal of the optimization process.
The computation of total weight includes only elements with definable volume. Elements such as lumped
mass (CONM2) and distributed mass/unit length are excluded--in fact these are invariant during design
optimization.
Solution
Response
Existing Objectives
Min/Max
For some responses, you must select the component of interest such as
translational magnitude, invariant or individual component. You may
also be required to select a model location such as a node, element, or
a property set that contains the entities of interest where the objective
is to be monitored for optimization.
Examples objectives:
minimize the weight or volume of the structure
minimize the displacement at a particular location
maximize the buckling load
minimize the stress in a member
minimize the acceleration at a particular point at a particular frequency
Design Constraints
Design constraints provide certain restrictions, or limits, to ensure that as the optimization process
advances toward achieving the design objective, other design conditions do not become compromised.
As an example, you may decrease the cross-sectional area of a beam to minimize its weight, but not to
the extent where the axial stress generated in the beam increases beyond a specified value.
The nature of a design constraint depends, primarily, on the type of analysis solution you are performing.
In general, you define a constraint much the same way you define an objective except you give additional
information, the most important being the bounds in which the response must remain such as stress not
exceeding a particular value.
Displacements / Eigenvectors, Velocity, Acceleration, SPC Force
These constraints are valid for linear static, normal modes, frequency and transient response. Select a
translational (TX, TY, TZ) or rotational (RX, RY, RZ) displacement component and a location on the
model such as a node to apply the constraint. Alternatively, you may select Magnitude. The resultant will
automatically create an MSC Nastran DRESP2/DEQUATIN entry pair. In case of frequency and transient
response, you may also define the frequencies or time steps of interest and whether the responses of all
frequencies or time steps should be subject to some algebraic function such as summation, average, etc.
Upper and/or lower bound definitions of the constraint are required. These also can be defined per
frequency and/or time step. By default all frequencies and/or time steps are used.
Stress, Strain, Strain Energy & Force
These constraints are valid for linear static, normal modes, frequency and transient response. Select the
attributes of the constraint and the location on the model such as an element or a property set of the
entities of interest. Filters are available to easily select the dimensionality and correct property set. The
constraint responses can be subjected to a custom function such as determining the maximum or average
value. Upper and/or lower bounds must be set. For normal modes analysis you must specify the mode for
which this constraint is valid. For frequency and transient response, the constraints per frequency and/or
time step can be defined. Bt default all frequency and/or time steps are used.
Grid Point Force
Valid for linear statics and defined similarly to above constraints except a list of nodes and elements is
required.
670
Tools>Design Studies>Pre-Process
Creating Design Studies
Tools>Design Studies>Post-Process
After running a topology optimization analysis in SOL 200 of MSC Nastran, use the Action:
Read Results - to first import the new mesh from a jobname.des. This file is created by the
analysis run. Or import from a jobname.xdb file if PARAM,POST,0 is included in the input deck.
Display Results - to view the results of the optimization run. A shaded or fringe plot of element
density distribution is created. Each time a plot is created a new group is created (defined by the
user, default = HIGH_DES_GRPn) and used to post the results on the elements associated to the
result case selected. The target elements, when creating the element density plot, can be the
"Entire Model", only elements posted and visible in the "Current View", or elements with
selected "Properties". If you select "Current View" please be aware that when you make a plot,
a new group is created and posted. If you make a subsequent plot with different results, the
"Current View" is now the new group posted. To avoid an unexpected plot, make sure the group
or groups with the desired target elements are posted first. The one exception to this is if the
posted group is the same as the group to be created as listed on the form, then "Current View"
will not be used, but the previous set of posted groups.
FEM Smooth - to smooth the mesh. During this operation the elements are modified. A backup
database is created to preserve the original model in case you need to revert back to the original
model before smoothing.
672
Tools>Results
Results Tools
Tools>Results
Results Tools
This cascade menu provides access to the following results plotting or post-processing capabilities:
1. Tools>Results>Bar/Spring Forces
2. Tools>Results>Bar End Loads
677
3. Tools>Results>Max/Min Sorting
4. Tools>Results>Shear Panel Plots
5. Tools>Modeling>Explore
694
6. Tools>Results>Plot Sets
695
7. Tools>Results>Templates
673
684
691
714
8. Tools>Results>Test Correlation
725
Tools>Results>Bar/Spring Forces
678.1
1174.3
636.7
For Bar/Spring Forces and Moments, the Element Force Table produced during an MSC Nastran analysis
is required and therefore is accessible only for the MSC Nastran Preference. Make sure there is a
FORCE= case control entry in the MSC Nastran input deck. If the elements have properties, the XY
plane definition is used to determine the element directions. The positive results directions for the shear
forces and moments are according to the MSC Nastran convention, see below. If a value is negative, the
vectors are plotted in the positive directions with negative values.
v
xelem
Plane 1
yelem
wb
x
y
Grid Point GB
Plane 2
z
zelem
v1
yelem
wa
Grid Point GA
1a
Fx
a
v1
Plane 1
1b
v2
zelem
2a
x
a
v2
Fx
Plane 2
2b
674
Tools>Results>Bar/Spring Forces
Investigating Bar/Spring Force
The Bar/Spring Forces and Moments main form appears as shown here. Each widget option is explained
in the tables below.
Results Cases
Display Options
Controls the displacement of the vector base from the bar node. Offsets
the display from element nodes and element edges toward the element
center. 0.0 indicates the label will be plotted on the corners and 1.0
indicates all the labels will be plotted on the element centers.
Selection Method
Reset Graphics
Erases the Bar Forces Plot and the titles. The Auto Reset Graphics
toggle controls whether the graphics from the previous Bar Forces Plot
are automatically erased.
Display Options
Show
Display As
Options for the display of the force and/or moment are Component or
Resultant.
Display Values
Exponential/Fixed
The scale of the arrows can be either Constant or Scaled based on the
magnitude of the value. The Length parameter scales relative to the
screen dimensions if Constant and scales relative to the maximum
value and the screen dimensions if Scale Arrows is selected.
If the Hide Results Near Zero toggle is selected, results with an
absolute value of less than the Zero Tolerance are not displayed.
Values are plotted alongside the arrow. The format of the values is
controlled by selecting Exponential or Fixed and by specifying the
significant digits.
Significant Digits
Display Title
A sample component plot appears is shown here.
676
Tools>Results>Bar/Spring Forces
Investigating Bar/Spring Force
Figure 11-19
678
Results Cases
All of the Results Cases that exist in the current database are shown. If
the listbox is empty, then no results exist in the database. If the selected
results case does not have Grid Point Force data and Element Force
data, then press Apply to generate an error message explaining which
result type was missing. Only one result case may be selected and this
is highlighted.
Display Options
Press the Display Options button to display the following form in order
to enable further plot control.
Setting this toggle will result in all inplane shell forces being
incorporated in the calculation of bar end forces.
Selection Method
Controls whether the bar end loads are plotted on selected bar elements
or bar elements in selected groups.
Changing the Selection Method from the default Elements to Groups
replaces the select elements box with a list of groups. If a group is
selected that does not contain bar elements, a warning is displayed.
For the Elements Selection Method, if no bar or 2D elements are
selected, then all currently posted bars and 2D elements are selected
by default.
Reset Graphics
Clears all the Bar End Load plots from the current graphics viewport.
The Auto Reset Graphics toggle controls whether the graphics from
the previous Bar End Load plot is automatically erased.
Display Options
Plot Bar End Loads
Bar end load values may be enabled or disabled. If enabled, the color
of the labels can be controlled through a palette of available colors.
Load Label Position Shrink Offsets the display from element nodes and element edges toward the
element center. 0.0 indicates the label will be plotted on the corners
and 1.0 indicates all the labels will be plotted on the element centers.
Plot Shear Flow
Offsets the display from element nodes and element edges toward the
element center. 0.0 indicates the label will be plotted on the corners
and 1.0 indicates all the labels will be plotted on the element centers.
Format Type
Display Precision
Display Title
680
Requirements
There are certain requirements that must be met in order for the bar end forces to be plotted.
1. The MSC Nastran analysis must be run with GPFORCE=ALL and FORCE(SORT1, REAL,
BILIN)=ALL in the Case Control for all subcases. PARAM,POST,-1 must appear in the Case
Control or Bulk Data Section of the input file to ensure that the Grid Point Force Balance Table
is written to an OUTPUT2 file.
2. The existence of two results quantities in the database is required for the execution of the Bar End
Loads application. The name of these results can be seen in the Results application. They must
not be altered or deleted. The labels are:
Grid Point Forces, Elements
Bar Forces, Translational
Description of Calculations
Below is a simple model that is used to show a sample calculation. It is fixed on the left side and loaded
with 1000 lbs. force distributed to the 3 nodes on the right. All the elements are in the XY plane.
333.33
12
17
9
23
7
14
6
16
6
8
333.33
11
333.33
10
22
21
15
11
19
10
2
18
5
7
13
20
12
For the example calculations, Elements 12 and 20 are used. Element 20 is a quad element with membrane
properties. Element 12 is a bar element with CBAR properties.
(33.7346, 28.3195)
7
13.821
6.915
7
12
5
20
Direction Cosine
<0.765, 0.643, 0.0>
8.297
(22.4923,18.8797)
14.679
4
This Bar End Loads and Shear Panel Flow calculation requires the Grid Point Force data to be aligned
along the panel element edge. For each element node, a matrix of the direction cosines of the two adjacent
edges and the normal to those directions is inverted.
Direction Cosines
13
Inverted Matrix
Node 4
Node 4
5
7
0.0
1.316 -0.012
0.0
0.643 -0.999
0.0
0.846 -1.008
0.0
-1.0
0.0
20
0.0
12
0.0
0.0
-1.0
The inverted matrix is then multiplied by the Global Grid Point Force for that element at that node.
682
-378.4
207.9
3
184.0
GPF
GPF
Global
Aligned
1.316 -0.012
0.0
184.0
242.6
0.846 -1.008
0.0
-33.3
189.3
-124.3
0.0
-1.0
0.0
0.0
5 -50.4
13
Inverted Matrix
-93.5
287.8
20
0.0
12
-33.3
These transformed values are used for the remaining calculations in which Grid Point Force data is
required.
The Bar End Loads are calculated using the Bar Force loads from the results file. The Bar Force results
contain the element axial load values. The Grid Point Force for each end of the bar element is subtracted
from the axial load for each element. These become the bar end loads for that bar element.
-380.4
N2
BEL2 = -1096.6
684
Tools>Results>Max/Min Sorting
Max/Min Results Sorting
Tools>Results>Max/Min Sorting
Max/Min Sorting
The Max/Min Results Sorting postprocessing utilities permit sorting of results across multiple load cases
based on a user-specified criteria. The results of the sort are displayed on each element with the load case
and the maximum (or minimum) value. This utility is only accessible from the MSC Nastran Preference.
This utility enables the user to compare results obtained in other databases as well as across multiple
results cases. In addition, the user can sort results for either selected elements or nodes as well as by
groups or current viewport. Results obtained from any Max/Min sort may also be saved to a report file.
Select Results...
Select to specify which results for a Max/Min sort. You can select
results in any of the databases previously specified.
Controls...
After the results are specified, select to specify how the results of a
Max/Min sort are displayed.
Sort As:
Type of Max/Min sorting can be varied. Options include: MaxAlgebraic, Max-Absolute, and Min-Algebraic.
Select By:
Reset Graphics
Apply
Existing Databases
Add to List
You must manually add the databases to the select list box below.
686
Tools>Results>Max/Min Sorting
Max/Min Results Sorting
Selected Database
OK/Cancel
Selecting Results
If you choose Select Results on the main Max/Min Result Sorting form, the following menu displays.
Select which results cases to compare from either the current or multiple models as well as the specific
result type.
Only the results types that exist in all of the selected subcases for the
currently displayed model are listed. The selected result type is
expected to exist in all of the other databases selected for comparison.
If not, fatal error is issued and a comparison in not performed. You
MUST select the results case of the current database to get a list of
available results.
Position/Quantity
OK/Cancel
688
Tools>Results>Max/Min Sorting
Max/Min Results Sorting
Display Options
If Control was selected from the main Max/Min for, the Display Options form displays. In the Display
Options form, the user can change the default display properties of the Max/Min sorted results.
Format Type
Display Precision
Display Vectors
Varies the position and size of vectors when displaying vector results.
Set to display Results Titles in the Max/Min Sorted plots for the
current viewport.
Coordinate Transformation Select from one of the available options if you wish to transform the
results into a different coordinate system.
Result Positions
Max/Min Legend
The Critical Results Cases legend is presented to the user with all the Load Case names that satisfy the
Max/Min Sort criteria. The user may then select those results associated with particular Load Cases to
display in the graphics viewport. The default is to display the results associated with all critical load
cases.
This functionality is particularly useful if a large number of load cases satisfy the Max/Min Sort criteria,
but only a limited set are associated with the current region of the model. The extraneous information
may be disabled resulting in an uncluttered display of the key results of interest.
Filter
Select this to deselect all of the load cases contained in the list box.
You may use the databox to specify key characters to filter the list of
displayed result cases. The * is a wild card.
All Critical Load Cases satisfying the Max/Min sort criteria are
initially highlighted. Those that are not desired to appear in the display
may be un-highlighted. The numeric prefix in the result case label is
of the form: Database ID:Load Case ID.Subcase ID.
690
Tools>Results>Max/Min Sorting
Max/Min Results Sorting
Apply
Select Apply to enable any changes made by the user and these
changes immediately display in the viewport.
Done
Select Done to close out the form and enable changes made by the user
for any subsequent Max/Min plots.
Save To File
Select Save to File to save the contents of the Critical Results Cases
list box to a report file.
The results of the Max/Min Sort are displayed graphically on each selected element of the model. The
maximum (minimum) result for the selected elements or elements in the selected groups from the
selected load cases maybe displayed at either the element centroid, nodal or both positions. Nodal results
are always displayed at the nodes as shown below.
Max/Min Criteria.
G3
q2
q4
G2
q1
G1
692
Results Cases
Display Options
Press the Display Options button to display the following menu for
further plot control.
Selection Method
Reset Graphics
Clears all the shear planel plots from the current graphics viewport.
The Auto Reset Graphics toggle controls whether the graphics from
the previous shear panel plot is automatically erased.
Display Options
Label Position Shrink
Offsets the display from element nodes and element edges toward the
element center. 0.0 indicates that the label is plotted on the corners and
1.0 indicates all the labels are plotted on the element centers. This is
useful in differentiating the edge shears of adjacent elements.
Force or Stress
Offsets the display from element nodes and element edges toward the
element center. 0.0 indicates the label will be plotted on the corners
and 1.0 indicates all the labels will be plotted on the element centers.
Display Precision
Display Title
Below are a Shear Element Plot of forces with Plot Average Shear selected, a Shear Element Plot of
forces with Plot Edge Shear selected, and the same plot with Label Position Shrink offsets so the edge
shears on adjacent edges can be seen.
Requirements
To make a Shear Panel Plot, Element Forces must be requested when submitting the analysis. The shear
element results data is imported from the MSC Nastran results file, creating a result type of Shear Panel
Forces, Shear. The result contains four values for each Shear Panel element. The values represent the q1,
q2, q3, and q4 edge shears.
694
Tools>Modeling>Explore
Exploring Results Quantities
Tools>Modeling>Explore
Explore Results
MSC.Explore is a complementary module of Patran to enable rapid identification and visualization of
critical design results from MSC Nastran analyses. This is a single program with many capabilities.
MSC.Explore provides a new way of looking at MSC Nastran results across multiple load cases and
multiple result files instead of the traditional one-load-case at a time approach. MSC.Explore uses an
efficient GUI interface for selecting and viewing results. This single tool processes Static, Transient and
Frequency Response Analyses and produces web-based HTML and ASCII text output in addition to
graphical output.
Benefits
Using MSC.Explore has many advantages because it:
Comprises a single program with many capabilities that incorporates industry-wide methods and
expertise
Processes Static, Non-linear, Transient, and Frequency Response Analyses with one tool and
results files
Provides a low-cost, low-maintenance tool that avoids high-cost maintenance and development
of in-house code
Analyzes larger FEA model results using current hardware resources
Requires neither an additional translator program nor additional intermediate files which save
disk space
Produces output that is web-based HTML as well as ASCII report output.
This tool is only accessible via the MSC Nastran Preference. Access to the full documentation for
MSC.Explore can be found in a PDF file in the Patran installation directory (P3_HOME):
$P3_HOME/mscexplore_files/mscexlpore_documentation.pdf
Tools>Results>Plot Sets
696
Tools>Results>Plot Sets
Creating Plot Sets
Action
Create
The Create form shows the Plot Sets that exist in the Patran database.
With this form you can enter a new Plot Set name, description, and
toggle the overwrite button. The Plot Set names are limited to 79
characters but there is no limit to the size of the description you can
enter.
Copy
The Copy form shows the Plot Sets that exist in the Patran database.
With this form you can enter a new Plot Set name and its description.
If the name you have assigned is equal to an existing name, the new
Plot Set will replace it if the overwrite option has been selected. When
the apply button is pressed a new Plot Set will be generated and the
contents of the selected set will be copied to it. If you did not enter a
Plot Set description a warning message will appear. The warning does
not effect the creation of the Plot Set.
Edit
The Edit form shows the Plot Sets that exist in the Patran database. To
edit a Plot Set select it from the list and press the Edit button. When
the Edit button is pressed the Plot Set Edit Spread Sheet will appear.
For details on editing a plot set, please see, Editing a Plot Set Using the
Plot Set Spread Sheet, 697.
Import
With the Import form you can enter the name of the Plot Set file you
would like to import located in your current working directory or you
can select the Files... submenu to specify the complete path to the
file you would like to import. An option is present so you can over
write a Plot Set that exists in the Patran database. This toggle has
higher precedence than any overwrite flags specified in the imported
file.
Export
The Export form shows the Plot Sets that exist in the Patran database.
With this form you can choose one or more existing Plot Sets to
export. You may use the Files... button to select or enter the name
and path to the file that will receive the exported Plot Sets. You can
also just enter this information directly in the File Name data box. An
option is present to allow over writing an existing Plot Set file.
Delete
The Delete form shows the Plot Sets that exist in the Patran database.
To delete either single or multiple Plot Sets first select the Plot Set(s)
and then press the Apply button.
The Print form shows the Plot Sets that exist in the Patran database
that you can print to a JPEG file. The Preview Only toggle will
preview the plots contained in a Plot Set(s) within Patrans graphics
viewport(s) before printing them to JPEG files. With the Save Plots To
Db toggle you can persist the plot definitions within the Patran
database.
In the example shown above the Tee Model - Static Analysis plot set is empty. When plot sets are
created using the Create user interface you can enter the plot set name and a text description of the plot
set but not the contents of the plot set. The Edit user interface has been provided to allow you to define
the contents of your plot set.
698
Tools>Results>Plot Sets
Creating Plot Sets
To add a row to the plot set simply press the Add Row button. Once the Row Control sub form appears
change the Action to Add Row, enter a row name of your choice, select a Row Type, and finally press
the Apply button.
Here a Fringe Plot row type is being added to the spread sheet. After creating a second row of type,
Deform Plot, the spread sheet should appear as shown below.
The plot set now contains two Plot Type rows but the definition of these rows are incomplete. Plot Type
rows contain columns that represent the plots Results data, graphic Attributes, and Target entities. To
define the contents of a column cell just click on that cell. Shown below is an example of editing the
Results cell within the Fringe Plot row. Here a Result Case, Result Type, and Derived Value have been
selected within the Result Control submenu that appeared. Clicking the Apply button will accept the
selected values and close the Result Control form.
700
Tools>Results>Plot Sets
Creating Plot Sets
Similarly by selecting the Attributes cell within the Fringe Plot row the following Attributes Control sub
form will appear.
A fringe plots graphical attributes are defined by selecting an existing Fringe Result Template that has
been previously persisted in the Patran database. Any viewports, views, spectrums, or ranges that also
currently exist in the Patran database are shown in the various list boxes. You can choose one or more
selections from each list box. These selections will over-ride the definition that is contained in the
selected Fringe Result Template. Multiple selections from any of the list boxes will influence the number
of plots that will be created when you use the Plot Set Print functionality to preview or print the contents
of the Plot Set Spread Sheet. See Appendix B for a detailed discussion of the two types of Plot Iterators
that cause multiple plots to be rendered when multiple definitions of a plot attribute have been selected.
With the Attributes Row Control form you can add a plot name to the rows plot definition. By saving
the plot with a name you are able to post or modify this plot when using the Patran post processor. The
Print Filename edit box allows you to assign the path to and name of the image files that will be produced
when you run the completed spread sheet.
The final step to complete the definition of the fringe plot row is to enter the plot target definition. Shown
below is the Target Row Control sub form that appears when you select the Target cell in the row.
The Row Control form shown above allows you select multiple target definitions for your plot row thus
allowing you to create multiple plots from a single row relative to the number of target definitions you
702
Tools>Results>Plot Sets
Creating Plot Sets
have chosen. To create a target definition select the Create Target Definition button. The following
definition form will then appear.
Your choice of plot target types that you can create are those that are used within the Patran post processor
(e.g. Current Viewport, Elements, Groups, Properties, and Element Types). First select a target type using
the Target pull down menu. Next, select various choices that appear in the target types subordinate list
boxes. Shown below is an example where the user has created three target definitions using the Current
Viewport, Groups, and Elements options.
704
Tools>Results>Plot Sets
Creating Plot Sets
Once you press the OK button in the Row Input sub form the target definitions will appear in the Row
Control form. To complete the Plot Rows target definition you must select one or more of the target
definitions you have created and then press the Apply button as shown in the example below.
You must now perform similar operations for the Deform Plot row to complete its definition.
To create a combination plot all you need to do is add a new Plot Sheet row that is of type Combination,
and place that row above the plot type rows you desire to combine. To do this press the Add Row button,
set the Row Type to Combined Plot within the Row Control sub form that appears, and then press the
Apply button to cause the Combined Plot row to appear in the spread sheet.
When you create the Combined Plot row it will be added as the last row in the spread sheet. You now
must move the row above the plot type rows you want to combine (e.g. to row 1 position in our current
example) and then edit the Combined Plot rows data, setting the number of rows that you will combine
to 2. To move the row first select the Combined Plot rows Row Name cell. This will cause the selection
of option buttons to change at the bottom of the spread sheet. Select the Move Row option button. The
706
Tools>Results>Plot Sets
Creating Plot Sets
Row Control sub form that contains the various move options will appear. Select Beginning from the
Position option pull down menu as shown below.
Pressing the Apply button will cause the Combined Plot row to move to the row 1 position and the Fringe
and Deform plot rows to shift down one position. Next, select the Data cell in the Combined Plot row.
When the Row Control sub form appears enter 2 in the Number of Rows list box. This causes the
following two plot type rows to be used to form the combined plot.
Displaying the Contents of the Plot Set Spread Sheet
When you are finished configuring your plot set the Plot Set Print function gives you the capability to
preview your images before they are written to image files. To preview the contents of your plot set close
the Plot Set spread sheet by selecting the Done button then change the Action option on the main Results
Plot Sets form to Print. Select the Plot Set Definition to preview and the Preview Only radio button.
708
Tools>Results>Plot Sets
Creating Plot Sets
When the Apply button is pressed the Print Control submenu and the first image defined by the Plot Set
contents will appear as shown below.
If your Plot Set definition defines more than one plot press the Advance One Image button to advance to
the next plot. Pressing the RESUME button will cause Patran to quickly render the remaining plots
defined by your Plot Set. When you have finished reviewing the last Plot Set image the Print Preview sub
form will close and the Print function will try to return Patrans display back to its initial state before you
started the Plot Set preview as shown in the example below.
In the example we have been following above we defined a plot set that contained a single combined
fringe and deformed shape plot. With very few changes we can modify this example to produce several
plots with out adding another plot set row. In the example shown below the Plot Set is edited by selecting
Fringe Plot Results cell to cause the Results Row Control form to reappear. In addition to our initial
710
Tools>Results>Plot Sets
Creating Plot Sets
selection of the von Mises Derived Result all six stress components of the symmetric stress tensor have
been selected at both the Z1 and Z2 positions.
Our final edit will be to change the default Tuple iterator to the Product Iterator. This is done by selecting
the Data cell of the Combine Plot row to cause the Combine Plot Row Control sub form to appear. The
Iterator Type option is used to change to the desired Product Iterator type. See Appendix B for a detailed
discussion of the different Iterator Types. The changes we have just made will cause 14 combination plots
to be rendered. The Product Iterator forms the combination plots from the single displacement plot with
the 14 possible fringe plots.
712
Tools>Results>Plot Sets
Creating Plot Sets
by using the Plot Set row that contained the multiple selection from both Result Case and Layer
Locations list boxes. Examples that contain correct selection methods are described below.
Example 1: If you select multiple entries in either the Result Cases or Layer Locations list box and then
select the NONE option from the associated Combination Methods list box, multiple plots for the
different selections will be generated relative to the Iterator type you have defined in the Combination
Plot rows Data cell.
Example 2: If you select multiple entries in either the Result Cases or Layer Locations list box and then
select the NONE option from the associated Combination Methods list box, then the selected data sets
will be used to form a single data set whose entries are the point by point maximum of the data contained
within the selected data sets.
In the Result Row Control form shown to the right multiple Result Cases have been selected. When
multiple Result Cases are selected the Result Type entries that appear are the intersection of the results
types contained in the data sets identified by the selected Result Cases (for a selected Output Type).
Likewise, the Layer Location entries that appear are an intersection of the layer locations contained
within the data sets identified by the selected Result Types and Cases.
714
Tools>Results>Templates
Applying Results Templates
Tools>Results>Templates
Result Templates
Results Templates provide a convenient means of storing in the database collections of settings that you
can use to create plots, graphs and reports under the Results menu. Settings stored in Results Templates
are applied to the Results Display Attributes and Plot Options menu settings for the following results
tools: Deformation Plot, Fringe Plot, Marker Vector Plot, Marker Tensor Plot, Graph, and Report.
The Results Templates menu provides the ability to Create, Edit, Copy, Delete, Export, and Import results
templates and then a means to Apply the template values to the Results Display Attributes and Plot
Options menu settings. Once you Create and Apply a Results Template from the Tools menu, you can go
the Results menu and select the Use Templates option. For more information on the Use Templates
option, see Use Templates (p. 24) in the Results Postprocessing.
Patran can also be customized to automatically load into a new or opening database a set of predefined
Results Templates.
Applying Results Templates
The Apply To Form action takes values from the selected Results Template and sets them on the
corresponding Results Display Attributes and Plot Options forms. The corresponding Results form to
Create or Modify the same Object must already be displayed before the template values can be applied
to the Results Display Attributes and Plot Options forms. For example, before applying a Deformation
Tools>Results>Templates 715
Applying Results Templates
template to the Results forms, you need to display either the Create Deformation or Modify Deformation
results menu.
Object
Existing Deformation
Templates
Select an the existing template to apply. The list includes templates that
match the selected object.
716
Tools>Results>Templates
Applying Results Templates
Results Template. You can then use this Results Template to create more results tools (plots, graphs, and
reports) and be assured that they have the same attributes and options settings as the original.
Tools>Results>Templates 717
Applying Results Templates
Action
Create
Edit
Editing uses the Results Display Attributes and Plot Options forms to
display the Results Template Values when the Apply To Results
Forms button is clicked. The corresponding Results form to Create or
Modify the same Object must already be displayed before the template
values can be applied to the Results Display Attributes and Plot
Options forms. For example, before applying a Deformation template
to the Results forms, you need to display either the Create
Deformation or Modify Deformation results menu.
Go to the Results Display Attributes and Plot Options forms and
modify the settings as desired. Return to the Results Template Edit
form.
Clicking the Use Current Form Settings will cause the currently
selected results template to be modified according to the current
settings of the Results Display Attributes and Plot Options forms.
Copy
The New Template Name must be unique for its Object type
(Deformation, Fringe, etc.).
Delete
Object
718
Tools>Results>Templates
Applying Results Templates
Method
(for Creating Templates)
Use Tool Values extracts the Results Display Attributes and Plot
Options values that were stored in the database in a Results tool. Use
Form Values reads the Results Display Attributes and Plot Options
values directly from the Results forms. If you select Use Form
Values the corresponding Results form with the same Object must be
displayed before the template values can be read from the Results
Display Attributes and Plot Options forms.
Existing Deformation
Templates
Select an the existing template to use. The list includes templates that
match the selected object.
The New Template Name must be unique for its Object type
(Deformation, Fringe, etc.).
Template Description
The Template Description is optional. It lets you attach notes about the
results template to its database record. This can be helpful in keeping
track of your different results templates.
Tools>Results>Templates 719
Applying Results Templates
Overwrite Db Template
720
Tools>Results>Templates
Applying Results Templates
This button brings up the Results Template Spectrum & Range form.
Use this form to optionally select which color palette, spectrum and
range will be used for results plots using this template. You can also
use this form to store the exact definition of a color palette, spectrum
and/or range in the results template. Then, when this template is used
to create a result plot these definitions will be used to create the color
palette, spectrum and/or range for the plot. They will have the same
attributes and options settings as the original.
Tools>Results>Templates 721
Applying Results Templates
Action
Export
The export menu takes selected Results Templates from the database
and writes to the file the session commands that would create the same
database content. These commands can then be used to recreate the
exported results templates in other databases (see the Import menu), or
as a standard set to be loaded into new or opened databases (see Auto
Load Details section of document).
Import
722
Tools>Results>Templates
Applying Results Templates
Object
Existing Deformation
Templates
Files...
Overwrite File/
Overwrite Db Template
Tools>Results>Templates 723
Applying Results Templates
724
Tools>Results>Templates
Applying Results Templates
res_tmpl_set_force_overwrite(logical
force_over )
If force_over is true, this will take precedence above the overwrite argument to res_temp_create_over.
This can be useful in the auto load files. The force_over value is reset to FALSE when using the results
template forms, so you will need to call res_tmpl_set_force_overwrite(TRUE) again after doing anything
with the ui. It is best just to call it whenever you want force_over to be true and not worry about when it
gets unset.
The files processed during the automatic loading process will be logged to a file in the working directory
named ResTmplAutoLoadLog<random number>.ses and then this session will be played.
For more information see, The settings.pcl file (p. 47) in the Patran Reference Manual.
Tools>Results>Test Correlation
726
Tools>Pre-Release 727
Access to Pre-Release Functionality
Tools>Pre-Release
Pre-Release
These are items that are still under development but released for use by customers for evaluation and to
give feed back to MSC Software Corporation. They are not to be considered as production code and are
provided as-is.
728
Tools>Pre-Release
12
Introduction
Getting Started
Availability
Tree Control
Configuration
Search
Sort
Filter
Materials
Properties
Fields
LBCs
Contact
Load cases
Groups
Analyses
Results
Customization
730
12.1
Introduction
The Model Tree browser displays database entities on screen and perform actions to add, delete and
modify existing entities through the model tree. Not only can the database contents be viewed from the
tree structure, but by right clicking on the elements of the tree you can create, copy, paste, modify, or
delete those database entities and more easily navigate through different forms.
Easy visualizing, accessing, and manipulating of database entities through the model tree reduces
learning time, increases productivity and makes Patran more intuitive to use. The Model Browser Tree
is available on Windows and Linux platforms.
mmp
12.2
Getting Started
The Model Browser Tree (MBT) allows the user to quickly see what is in the current database in a userfriendly tree structure. Database entities refer to material definitions, property sets, LBC sets, load cases,
fields, geometry, meshes, groups, analysis jobs, results, geometry and meshes. In addition to right mouse
button manipulation of the entities in the tree structure, drag and drop capabilities will be used in some
cases to create associations and toggle buttons to show/hide entities on graphics model.
The MBT is preference-neutral, e.g. generic, and as possible (like the icon ribbons) but there are some
preference-specific aspects (like the ribbon icons).
Thus, MBT reduces the number of mouse clicks and saves the time while traveling to number of options.
This makes the Patran GUI more efficient and modern.
Figure 12-1
732
12.3
Availability
The Model Browser Tree is available on Windows and Linux platforms. Some functionalities and User
Interface are slightly different between the Windows and Linux. The Model Tree is supported on both
Skin and Classic mode on Windows platforms.
Select Show/Hide Model Tree button from ribbon bar to make Model Tree available after opening or
creating new Patran database.
Alternatively, the Model Browser Tree can also be posted or unposted with the use of command
toggleModelTree() in the Patran command window.
12.4
moves along with graphics viewport. The transparent model tree is always attached with the
current viewport. The dock-able tree can dock to the left or right of the Patran viewport and it
can also be a floating window.
Size The transparent tree is part of the graphics viewport and it resizes along with graphics
viewport. The dock able tree can be resized by dragging the border with mouse drag.
734
12.5
Tree Control
Tree widget displays database items/entities in tree hierarchy. This is model browser tree control with
below functionalities.
Tree item Each tree item will have
Text label
Icon
Tree node connecting line
Checkboxes or toggle button Toggle buttons will be available for those database entities
which supports post/unpost on the model view. Currently it is available with groups, LBCs and
results type of entities.
Pre-selection highlighting Tree item will highlights and change the cursor type (hand) while
defined for that node. For Material, Property, Fields, Group, Load case, and Results plot it will
display the Modify form. For Analysis it will display the Analyze form and for Result case it will
display the Create Result form.
Keyboard Delete Selecting a single or multiple items and then pressing the Delete key on
keyboard will bring up a delete confirmation form and on confirmation the selected items will be
deleted. Delete operation is valid only for child items, it will not delete parent node and a UI
error/warning will be displayed. This functionality is supported only on Windows platform and
will not work on Linux.
12.6
736
12.7
12.8
Configuration
Configuration window provides the different configuration options for Model tree and tree container.
Configuration settings and other state information (visibility, show transparent RMB option) are stored
and retrieved from the patran_conf.ini file. While loading Patran, if this file is present in current directory
then Patran loads the settings. Otherwise Patran searches the file in the HOME directory and then in the
P3_HOME location. If Patran does not find the file in these locations then it uses the above default values
and creates and/or updates the settings in the patran_conf.ini file in your current working directory when
you quit Patran.
738
12.9
Search
When this option is selected, a form will be displayed having edit control to specify search text and
next/previous buttons. The text specified is searched in the tree and shown if found otherwise error will
be reported. Search is case insensitive. You can search text forward or backward in the tree with Previous
and Next buttons.
12.10 Sort
There are two sorting methods supported to sort tree child items.
Alphabetical - Sort tree items in alphabetical order.
Creation order - Sort tree items in creation order.
Selecting same sorting method reverse sorting (ascending /descending) order. By default tree is generated
by its creation order and in ascending order. Only child items in the tree are sorted.
740
12.11 Filter
When this option is selected, a form with a list of available type entities appears in the MBT. Only
selected type entities will be shown in the tree. This feature enables you to determine which category of
entity appears in the Model browser tree.
12.12 Materials
Materials tree item lists all the available material types and corresponding materials. Right mouse click
on material tree item will show the popup menu. Selecting any menu option will bring up the
corresponding form. In skin mode, Materials tab will be selected and corresponding ribbon options
will be available to the user.
Figure 12-2
742
Figure 12-3
Figure 12-4
744
12.13 Properties
Properties tree item shows all the available property types and corresponding properties in the current
database. Right mouse click on any property item will show popup menu. Selecting any menu option will
bring up the corresponding form. In "skin" mode, Element Properties tab will be selected and
corresponding ribbon options will be available to the user.
Figure 12-5
Figure 12-6
Figure 12-7
746
12.14 Fields
Fields tree item shows all the available field types and corresponding fields. Right mouse click on any
field item will show popup menu. Selecting any menu option will bring up the corresponding form. In
"skin" mode, Fields tab will be selected and corresponding ribbon options will be available to the user.
Figure 12-8
Figure 12-9
748
Figure 12-10
12.15 LBCs
LBCs tree item shows all the available LBC types and corresponding loads and boundary conditions in
the currently opened database. Right mouse clickon any LBC item will show popup menu. Selecting any
menu option will bring up the corresponding form. In "skin" mode, Load/Boundary Conditions tab will
be selected and corresponding ribbon options will be available to the user. Each LBC tree items will have
additional toggle buttons to plot/erase markers for that particular LBC.
Figure 12-11
750
Figure 12-12
Figure 12-13
Figure 12-14
752
12.16 Contact
Contact tree item shows deformable bodies, rigid bodies, and body pairs in the current database. Right
mouse click on any contact item will show popup menu. Selecting any menu option will bring up the
corresponding form. In "skin" mode, Load/Boundary Conditions tab will be selected and
corresponding ribbon options will be available to the user.
Figure 12-15
Figure 12-16
754
Figure 12-17
Figure 12-18
756
Figure 12-19
Figure 12-20
12.18 Groups
Groups tree item shows all the available groups. Right mouse click on any group will show popup menu.
Selecting any menu option will bring up the corresponding form. Each group tree items has additional
toggle buttons to post or unpost particular group.
Figure 12-21
758
Figure 12-22
Figure 12-23
760
Figure 12-24
Figure 12-25
12.19 Analyses
Analyses tree item shows all the available simulation jobs in the current database. Right mouse click on
job item will show popup menu. Selecting any menu option will bring up the corresponding form.
Selecting delete will delete the selected jobs.
Figure 12-26
RMB Analyses
762
12.20 Results
Results tree item displays all the available result types and corresponding result cases. Right mouse click
on result plot or result cases item shows popup menu. Selecting any menu option will bring up the
corresponding form. In "skin" mode, Results tab will be selected and corresponding ribbon options will
be available to the user. For each result plot tree item will have additional toggle buttons to post or unpost
results on the graphics viewport for that particular results plot.
Figure 12-27
Figure 12-28
764
Figure 12-29
12.21 Customization
Right mouse button (RMB) popup menus for different entity types are configurable through xml files.
For more information, see: Right Mouse Button Customization, 346.
766
13
Random Analysis
Introduction
768
Appendix A
771
778
782
785
860
868
768
13.1
Introduction
Purpose
MSC Random is a random analysis software package for use with MSC Nastran and Patran. It was
developed by field engineers at MSC to offer a fast integrated random analysis solution from within the
Patran environment. All of MSC Randoms analysis capabilities and generated results are available from
within the PATRAN environment.
MSC Random software technology is similar to the existing MSC Nastran random analysis capability. In
both packages, random analysis is treated as a data reduction procedure that is applied to frequency
response analysis, but MSC Random offers additional capabilities and graphical interface.
The program uses the MSC Nastran XDB file from MSC Nastran frequency response analysis to calculate
the random responses. It calculates displacements, velocities, accelerations, SPCForce and MPCForce
for grids and stresses, forces and strains for elements as requested in the MSC Nastran case control data
section in the frequency response run. The program also creates a result file containing RMS responses that
will be automatically be imported into Patran for creating fringe plots of RMS response. A xy plot of PSDF
response, cumulative RMS, cross PSDF, relative PSDF or auto/cross correlation can also be created from
within Patran.
MSC Random is also designed to make it easier for engineers familiar with MSC Nastrans random
analysis capability to adapt quickly to this new procedure. MSC Random requires the same initial
frequency response run setup and the same random input format.
770
MSC Nastran
Figure 13-1
Limitations
1. Maximum number of output frequencies: 32,768.
2. Maximum Number of RANDPS entries: 250,000.
3. Maximum Number of TABRND1 entries: 250,000.
4. MSC Nastran elements supported CBAR, CBEAM, CROD, CONROD, CTUBE, CBEND,
CDAMP, CBUSH, CELAS, CQUAD4*, CQUAD8*, CQUADR*, CTRIA3*, CTRIA6*,
CTRIAR*, CSHEAR, CHEXA*, CPENTA*, CTETRA*.
*
13.2
772
are correlated or uncorrelated. The spectral densities due to all sources, considered independent, will be
combined into one set of outputs.
Figure 13-2
Theory
The application of frequency response techniques to the analysis of random processes requires that the
system be linear and that the excitation be stationary with respect to time. the theory includes a few
important theorems which will be reviewed. An important quantity in random analysis theory is the
autocorrelation function Rj(), of a physical variable, uj, which is defined by
R j ( ) = T lim
1 T
u j (t ) u j (t )dt
T 0
(13-1)
u2
Note that Rj(0) is the time average value of j , which is an important quantity in the analysis of
structural failure. The one-sided power spectral density Sj() of uj is defined by
2
S j ( ) = T lim
T
i t
u j (t )dt
(13-2)
It may be shown (using the theory of Fourier Integrals) that the autocorrelation function and the power
spectral density are Fourier transforms of each other. Thus, we define the autocorrelation function in
terms of frequency response functions
R j ( ) =
1
2
S j ( ) cos( ) d
(13-3)
from the mean-square theorem, the rms (root mean squared) magnitude, uj, is
u 2j = R j (0) =
1
S j ( )d
2 0
(13-4)
The expected value of the number of zero crossing with positive slope per unit time, or apparent
frequency, is a quantity of interest for fatigue analysis. This mean frequency, N0, can be found from the
power spectral density;
2
0
( / 2 ) S ( ) d
=
S ( )d
2
(13-5)
The mean frequency, N0, is thus the root mean square frequency, where the power spectral density is used
as a weighing function.
The transfer function theorem states that, if Hja() is the frequency response of any physical variable, uj,
due to an excitation source, Qa, which may be a point force, a loading condition or some other form of
excitation, i.e., if
u j ( ) = H ja ( ).Qa ( )
(13-6)
Where uj() and Qa() are the Fourier transforms of uj and Qa, then the power spectral density of the
response , is related to the power spectral density of the source, Sa(), by
774
S j ( ) = ( H ja ( ) . S a ( )
(13-7)
Eq 2-6 is an important result because it allows the statistical properties (e.g., the Auto-correlation
function) of the response of a system to random excitation to be evaluated via the techniques of frequency
response. Another useful result is that, if sources Q1, Q2, Q3, etc., are statistically independent, i.e., if the
cross-correlation function between any pair of sources
Rab ( ) = T lim
1 T
qa (t )qb (t ) d
T 0
(13-8)
is null, then the power spectral density of the total response is equal to the sum of the power spectral
densities of the responses due to individual sources. Thus
S j ( ) = S ja ( ) = H ja ( ) S a ( )
2
(13-9)
If the sources are statistically correlated, the degree of correlation can be expressed by a cross-spectral
density, Sab, and the spectral density of the response may be evaluated from
S j = H ja H *jb S ab
a
(13-10)
Rab ( ) = T lim
1 T
ua (t ) ub (t )dt
T 0
(13-11)
Where ua(t) and ub(t) can be displacement, velocity, acceleration or single-point force responses at the
same or different grid points; or stress, strain, and force components in the same of different elements.
The cross-correlation functions have the following relation
Rab ( ) = Rba ( )
(13-12)
The cross-power spectral density (cross-PSD) of ua(t) and ub(t) is defined as;
T
2 T
S ab ( ) = T lim ua (t )e i t dt ua (t )ei t dt
0
T 0
(13-13)
= 2 Rab ( )e i d
(13-14)
Rab ( ) =
1 +
S ab ( ) eiw d
4
(13-15)
The cross-PSD Sab() is a complex-valued function of angular frequency . The following relations hold
for the cross-PSDs.
*
Sab
( ) = Sab ( )
Sba ( )
(13-16)
Where Sab*() is the complex conjugate of Sab(). If we denote Sab() by its real and imaginary parts as
(R)
(I )
S ab ( ) = Sab
( ) + iSab
( )
(13-17)
From (2-15), we can see that Sab(R)() is an even function and Sab(I)() is an odd function of , i.e.
(R)
( R)
Sab
( ) = Sab
( )
(13-18)
(I )
(I )
Sab
( ) = Sab
( )
(13-19)
Rab ( ) =
1 ( R)
(I )
S ( ) cos( ) S ab
sin( ) d
2 0 ab
(13-20)
If the system is subject to multiple sources of excitation, the cross-PSD of responses ua(t) and ub(t) is
related to the PSDs of excitation sources by the frequency response function as
Sab ( ) = H aj ( ) H bk* ( ) S jk ( )
j
(13-21)
776
Where Haj() is the frequency response function of ua(t) corresponding to the excitation source Qj(t),
Hbk*() the complex conjugate of Hbk() , and Sjk() the cross-PSD of excitation sources when j k. If the
two different excitation sources Qj and Qk are not correlated, we have Sjk() 0.
The aforementioned equations of cross-PSDs and cross-correlation functions become the ones for autoPSDs and auto-correlation functions when ua(t) = ub(t).
The calculation of the cross-correlation function from 2-18 is carried out by numerical integration based
on the trapezoidal approximation.
1
u j ( i ) =
2
2
S
(
)
d
j
w1
, i = 1,2, , N(2-21)
i
(13-22)
=
2
S jk ( )
S jj ( ) S kk ( )
1 .0
(13-23)
MSC Random will check for the input and will print out the warning message in job-name.out file.
Figure 13-3
Ref 3 and 4 outline the method of calculating von Mises PSD response. Ref 3 discusses computing von
Mises PSD using Modal Approach whereas Ref 4 computes von Mises PSD directly from PSD-matrix
of stress tensor. The MSC Random uses the approach from Ref 4 since it is applicable to both Modal
Frequency Response Analysis and Direct Frequency Response Analysis.
778
13.3
User Interface
(Patran)
Random Analysis
(MSC.Random)
Figure 13-4
Frequency Response
Analysis
(MSC NASTRAN)
The frequency response and random analysis cycles will be discusses separately in following sections,
but they will be presented in the order that the random analysis process would typically proceed.
1. 1. In addition to the obvious finite element quality checks, also perform rigid body check (or
ground check) using GROUNCHECK (see MSC Nastran Quick Reference Guide, Case Control
Section).
2. Make sure the FEM refinement is adequate to capture all important modes throughout the
frequency range of interest. Verify this by running a modal analysis and evaluating the mode
shapes of key modes. This run should be made with identical boundary conditions the frequency
response run will use.
3. After you have performed the frequency response analysis, make sure the natural frequencies
match your modal analysis run.
Verifying the FEM is only one step in generating a quality frequency response analysis that is ready for
random analysis. The input loads, damping and number and spacing of output frequencies also have to
be verified. This is done by reviewing frequency response results. Response XYplots can be made to
verify there are enough output points to capture the response profile. The XY plot in Figure 13-5 shows
the responses from two different frequency response analyses of the same model. The curve with fewer
points predicted RMS results 23% higher than the curve with more points. This would have been much
worse if any important natural frequencies were skipped. Assuming at least all of the natural frequencies
are recovered, the random RMS results will usually error on the high side when inadequate numbers of
output frequencies are requested.
Figure 13-5
780
The iterative process of verifying the FEM and verifying the frequency response analysis cycle is
illustrated in Figure 13-6.
Figure 13-6
changes, such as damping, analysis frequencies, output requests and model properties will require rerunning the frequency response analysis and therefore feed back into the frequency response cycle, see
Frequency Response Analysis Cycle.
Figure 13-7
782
13.4
Output Files:
MSC Random produces various output files depending upon different action selected by user.
XY Plot:
Job_Name.log: Error Messages
Job_Name-xy.out: ASCII output files Input description and warning messages
Job_Name.xy: ASCII XY Plot output file. This file can be imported in to Excel Spreadsheet.
Note: All GRID responses are processed in Analysis Coordinate System. Element results are in
Element Coordinate System.
RMS Analysis:
Result_Name.log: Error Messages
Result_Name.out: ASCII RMS results output files
Result_Name.pat: Neutral result file that can be imported in to Patran database.
Note: All Grid RMS Fringe Plots/Results are in BASIC Coordinate System Element Results are
in Element Coordinate System.
In addition, MSC Random will create following input files.
Job_Name.inp: This files will be read by MSC Random executable (similar to .bdf or .dat file
created by Patran
Job_Name.rnd: User created or created by MSC Random Interface. This file contains the random
input descriptions.
Contents of output files:
Job_Name.xy: This file is similar to MSC Nastran XYPUNCH file. First Line describes the type of plot,
Elem/Node ID, Component/DOF and then followed by XY data representing Frequency Vs Result.
XYDATA,ACCE-PSDF:ID 92, Tx :RMS(*3.00) 5.05682E+04 Zero X-ing
3.32133E+02
1.00000000E+01 4.08137744E+03
1.06809082E+01 5.53827100E+03
1.11413689E+01 6.68424609E+03
1.13124104E+01 7.11009375E+03
1.16323595E+01 8.02400781E+03
1.18563261E+01 8.76009570E+03
....
....
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
* * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * *
*
*
*
MSC SOFTWARE
*
CORP
*
*
M S C . P a t r a n
*
*
Random Analysis
*
*
VERSION - 2007.0.0
*
*
*
*
* * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * *
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
User Input........
XDB:C:\barbela\Random\_Production\2005\doc\Examples\cylinder-1\base-x.xdb
RESPONSE:ACCE
LOG_LIN:LOG
FACTOR:3.0
RFILE:C:\barbela\Random\_Production\2005\doc\Examples\cylinder-1\Random.rnd
OPTION:RMS
** Finished Reading Input **
***
Result Multiplier :
No of Subcases
No of Frequencies
No of Randps
No of Tabrnd1
Integration Scheme
:
1
:
435
:
1
:
1
: Log-Log (to calculate RMS & Number of Zero Crossing)
3.000 ***
Schwarz's Inequality
<= 1.0 or Pjk * Conjg(Pjk) / (Pjj * Pkk) <= 1.0
of subcase J and K and
Subcase J and K
784
Grid_Id
Tx
Ty
Tz
Rx
Ry
Rz
( Zero X-ing)( Zero X-ing)( Zero X-ing)( Zero X-ing)( Zero X-ing)( Zero
X-ing)
1
6.57608E-04
2.30924E+04
0.00000E+00
0.00000E+00
2.58905E-05
8.98656E+03
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.69641E+03)(1.43129E+03)(1.84746E+03)
2
2.30924E+04 0.00000E+00 0.00000E+00 1.10007E+03 8.68984E+03
1.50619E+02
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.35119E+03)(1.42223E+03)(1.86314E+03)
3
2.30924E+04 0.00000E+00 0.00000E+00 2.07223E+03 8.13880E+03
1.78845E+02
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.35360E+03)(1.42746E+03)(1.85834E+03)
4
2.30924E+04 0.00000E+00 0.00000E+00 2.80963E+03 7.31220E+03
1.14604E+02
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.36068E+03)(1.43917E+03)(1.85221E+03)
5
2.30924E+04 0.00000E+00 0.00000E+00 3.17502E+03 6.23646E+03
4.71577E+01
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.35383E+03)(1.44905E+03)(1.84413E+03)
6
2.30924E+04 0.00000E+00 0.00000E+00 3.19763E+03 5.14193E+03
6.86768E+00
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.36159E+03)(1.47125E+03)(1.50072E+03)
7
2.30924E+04 0.00000E+00 0.00000E+00 2.79517E+03 4.08549E+03
2.65419E+01
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.35498E+03)(1.49633E+03)(1.82526E+03)
8
2.30924E+04 0.00000E+00 0.00000E+00 2.08432E+03 3.24476E+03
4.72351E+01
(9.74284E+02)(0.00000E+00)(0.00000E+00)(1.36012E+03)(1.53061E+03)(1.84444E+03)
Example Problems:
Instead of going through each form and every line item on the form, the usage of MSC Random and its
various capabilities will be demonstrated using few examples.
Three different examples will be considered.
1. Cylinder under base acceleration PSDF input in one direction only.
2. Table, modeled with all solid elements, subjected to three simultaneous acceleration base PSDF
Input in three directions.
3. Flat plate subjected to pressure and point load with Auto and Cross PSDF input.
13.5
786
PSDF Input;
G2/Hz
Frequency (Hz)
10
0.1
20
0.1
50
0.3
600
0.3
1500
0.12
2000
0.12
FEM Model
Create New Database
1. File / New
2. Enter File Name Cylinder
3. Click OK
788
1. Geometry
2. Create / Coord / 3Point
3. Type : Select Cylindrical
4. Apply
Create Curve
790
Create Surface
792
1. Elements
2. Create / Mesh Seed / Uniform
3. Select Number of Elements
4. Number: 36
5. Select Curve 1 & 2
6. Apply
1. Number: 60
2. Curve List Click on Surface 1:1
3. Apply
794
Create Mesh
796
Create Material
1. Material
2. Create / Isotropic / Manual Input
3. Enter Material Name alum
4. Input Properties
5. Enter Elastic Modulus (10.e6), Poissons Ratio(0.25) & Density(0.1)
6. Apply
1. Properties
2. Create / 2D / Shell
3. Property Set Name shell-prop
4. Click on Input Properties
5. On Input Properties Form Click on Mat Prop Name & select alum
6. Enter Thickness 0.05
7. Click on OK
798
1. Loads/BCs
2. Create / Displacement / Nodal
3. New Set Name: fixed-base
4. Click on Input Data
1. Tool Menu
2. Select Random Analysis
800
802
4. Click on Add Row This will add third row with Lin. Spread in Incr. Type column. See Ref
6, MSC Nastran Quick Reference Guide, volume 2 for more details on various frequency output
list (Freq, Freq1, Freq2, Freq3, Freq4, Freq5)
5. Click on Lin. Spread (3rd row, Incr. Type column)
6. Click on Drop Down Menu & Select Discrete (Freq) Need to add break points of PSD input.
Note: Always add all break points frequencies that define the PSD input curve. If there are more than
one PSD input curves, make sure to include all frequencies, which define all PSD input profiles, in output
list
Add few more rows and add additional frequencies as shown on next page.
G2/Hz
Frequency (Hz)
10
0.1
20
0.1
50
0.3
600
0.3
1500
0.12
2000
0.12
804
806
1. Click Apply This will create a message saying a Jobname base-x was created
2. Click OK
Now go to ANALYSIS form, select job base-x. If necessary modify/add additional analysis related
parameters. Make sure that you have selected Residual Vector Computation check box on Solution
Parameters form (Analysis | Solution Type | Solution Parameters | Residual Vector Computation). Then
either create the full analysis bdf file or run Nastran job through Patran. Once Nastran run is completed,
examine Nastran output file base-x.f06 and check for any warning/error messages. In addition to basex.f06, you will also see base-x.xdb file. This file contains the frequency response results.
1. Tool Menu
2. Select Random Analysis
808
1. Select XY plots
2. Click on Select XDB File
3. Select XDB file
4. Click Apply
810
G2/Hz
Frequency (Hz)
10
0.1
20
0.1
50
0.3
600
0.3
1500
0.12
2000
0.12
812
814
G /Hz
816
0.1
G2/Hz
0.01
10
100
1000
10000
G2/Hz
Frequency (Hz)
10
0.1
20
0.1
50
0.3
600
0.3
1500
0.12
2000
0.12
This PSDF plot confirms that the PSDF output at the base node is same as input. The total RMS input is
19.92 G. If Linear Integration scheme were chosen than total rms would be
SQRT [{(20-10)*0.1} + { (50-20)*(0.1+0.3)/2} + {(600-50)*0.3} + {(1500-600)*(0.3+0.12)/2} +
{(2000-1500)*0.12}] = SQRT (1.0 + 6.0 + 165 + 189 + 60) = 20.52 G
Random Analysis XY Plot (contd).
Get XYPlot for multiple nodes.
Click on Target Entity Icon.
818
Select Nodes 2029, 2140, 2222 and Select DOF 1 (X) and Click on Apply
Input Data
Export/Import
Target Entity
Curve Display Attribute: Modify Curve Style and Curve Color, Symbol Color & Size.
Graph Display Attribute: Use for customizing Title, Axes Scale, Custom Title as well formatting
820
Export/Import: Writes out XY raw data to an ASCII file in CSV (Comma Separated) format that
can be easily imported to Excel Spread Sheet. In Addition, MSC Random will also create an
ASCII file (job_name.xy) that can also be imported to Excel Spread Sheet
Random Analysis XY Plot (contd)
Cumulative RMS (CRMS)
1. Select XY Plots
2. Set Plot Type: CRMS (Cumulative RMS)
3. Click Target Entity Icon.
4. Select DOF 1 (X direction)
5. Select Node 2222
6. Click Delete Current XY Window to clear existing xyplot.
7. Click Apply
Once plot is created, experiment with various XY Plot option to change the scale, color etc.
822
Relative Displacement
1. Select XY Plot
2. Plot Type PSDF (Relative A-B)
3. Res. Type Displacement
4. Click on Delete Current XY Window to clear Display of any existing XY Plot.
5. Click on Target Entity Icon
6. Select First Node and DOF (Base Node 30 and DOF 1, X direction)
7. Select another node (Node 2222 and DOF 1, X direction)
8. Apply
824
1. Select XY Plot
2. Plot Type: Auto Correlation
3. Result Type: Displacement
4. Set Start Time 0.0, Ending Time 0.5 and Number of Increments 500
5. Click on Target Entity Icon
6. Select DOF 1 and Node 400 & 2222
7. Apply
826
828
830
13.6
10.00
0.18
10.00
0.15
15.00
0.18
34.90
0.15
15.10
0.10
35.00
0.25
30.00
0.10
55.00
0.25
30.10
0.22
55.10
0.15
100.00
0.22
300.00
0.15
100.10
0.12
300.10
0.08
1000.00
0.12
1000.00
0.08
1.00
G^2/Hz
832
0.10
G^2/Hz (X/Y)
G^2/Hz (Z)
0.01
10.00
100.00
1000.00
Frequency
834
BEGIN BULK
$
PARAM
POST
0
Param, Wtmass, .002589 $ (1/386.4 to convert WEIGHT unit
unit)
Param, Autospc, yes
$
Eigrl, 99, , 1000.
$
$ Damping 1% Critical - g = 2 * crit = 0.02
Tabdmp1, 33,
+, 0.1, 0.02, 10000., 0.02, Endt
$
Freq, 91, 15.0, 15.1,
30.0, 30.1, 100.0, 100.1
Freq, 91, 34.9, 35.0,
55.0, 55.1, 300.0, 300.1
Freq2, 91, 10.01, 999.99, 200
Freq4, 91, 10.0, 1000.0, 0.1, 1
$
RBE2
99999
99999
123
22561
22563
22646
22816
22818
23613
23778
24115
24117
24239
24628
24795
24797
25644
26635
26637
27156
27577
30217
30219
30232
Spc1,1,123456,99999
$
$ Input for X direction
$
Rload1, 51, 61, , , 31, , Acce
Spcd, 61, 99999, 1, 386.4
Tabled1, 31
+, 0.1, 1.0, 10000., 1.0, Endt
$
$ Input for Y direction
$
Rload1, 52, 62, , , 31, , Acce
Spcd, 62, 99999, 2, 386.4
$
$ Input for Z direction
$
Rload1, 53, 63, , , 31, , Acce
Spcd, 63, 99999, 3, 386.4
$
$ Rest of the model goes here.
to MASS
22725
24626
27158
Random Analysis
In this example, new feature will be used to read Random Input Profile using Existing Randps File.
Random Input is defined as Sjk(f) = (X + iY) G(f)
RANDPS
SID
SID
TID
TID
Remarks:
For Auto Spectral Densities, J=K, X must be >0.0 and Y must be 0.0
For Cross Spectral Densities, in general, two entries are required with same SID. One entry defines the
real part (X<>0.0, Y=0.0) and second one with imaginary part (X=0.0, Y<>0.0) See example 3 for
usage.
Existing Randps file is an ASCII file created by any text editor or any other source. It contains the
random input description. The input consists of two type of entries 1) RANDPS and 2) TABRND1. Both
entries are described in MSC Nastran Quick Reference Guide (QRG) see Ref 6. MSC Nastran supports
various input format such as Double Filed, Tab or Comma delimited input, etc. MSC Random on other
hand supports only Small Field (Fixed Field) or comma delimited file. Following is acceptable input file
for this problem.
$
Randps,99, 1, 1, 1.0, 0.0, 11
Randps,99, 2, 2, 1.0, 0.0, 12
Randps,99, 3, 3, 1.0, 0.0, 13
$
$ Random Input in X direction
Tabrnd1, 11, Log, Log
+, 10.0, 0.18, 15.0, 0.18, 15.1,
+, 30.1, 0.22, 100.0, 0.22, 100.1,
+, Endt
$
$ Random Input in Y direction
Tabrnd1, 12, Log, Log
+, 10.0, 0.18, 15.0, 0.18, 15.1,
+, 30.1, 0.22, 100.0, 0.22, 100.1,
+, Endt
$
0.10, 30.0,
0.10
0.12, 1000.0, 0.12
0.10, 30.0,
0.10
0.12, 1000.0, 0.12
$ Random
Tabrnd1,
+, 10.0,
+, 55.1,
+, Endt
$
Input in Z direction
13, Log, Log
0.15, 34.9, 0.15, 35.0, 0.25, 55.0,
0.25
0.15, 300.0, 0.15, 300.1, 0.08, 1000.0, 0.08
The Input shown above is based on the Random Input Profile defined below.
PSD INPUT X,Y direction
Frequency
G2/Hz (X/Y)
10.00
0.18
10.00
0.15
15.00
0.18
34.90
0.15
15.10
0.10
35.00
0.25
30.00
0.10
55.00
0.25
30.10
0.22
55.10
0.15
100.00
0.22
300.00
0.15
100.10
0.12
300.10
0.08
1000.00
0.12
1000.00
0.08
1.00
G^2/Hz
836
0.10
G^2/Hz (X/Y)
G^2/Hz (Z)
0.01
10.00
100.00
Frequency
1000.00
1. From Patran Tool Menu, Select MSC Random and set Action: XY Plots
2. Click on Select XDB File
3. Select XDB File on Select MSC Nastran XDB Form
4. Click Apply
838
1. Select XY Plots
840
1. Select Random Analysis from TOOL menu and set ACTION: RMS Analysis
2. Select Stress on Main Form and
3. Apply
842
Wait for MSC Random to finish the RMS analysis. Once the RMS Analysis is finished, the RMS Stresses
will be imported in to Patran Database.
844
13.7
846
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
Random Input:
Autospectra Pressure Load
Autospectra - Corner
Force
Frequency
PSI^2/Hz
Frequency
lb^2/Hz
Frequency
Real Part
Imaginary
Part
10.0
0.10
10.0
0.50
10.0
-0.099619
0.007816
20.0
0.10
20.0
0.50
20.0
-0.099619
0.043579
30.0
1.00
30.0
2.50
100.0
-0.498097
0.043579
100.0
1.00
100.0
2.50
500.0
0.070711
-0.070711
500.0
0.10
500.0
2.50
1000.0
0.000001
-0.000001
1000.0
0.10
1000.0
1.00E-06
40
848
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
Random Analysis
Auto Pressure
Auto-Force
After creating all required PSD Input Field, create PSD input profile and then create PSDF XY Plot for
various response quantities.
850
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
1. From Tool Menu, Select MSC Random and set Action: XY Plot
2. Click on Select XDB File and select freq-plate.xdb file
3. Click on PSD Input.
4. Change Random Input Method to Combine Cases
852
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
100.000,
100.000,
500.000,
500.000,-
854
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
4. Apply
856
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
7. Apply
858
Example 3: Plate - Subjected to Pressure and Point Load with Cross Spectrum Input
3. Apply. Once MSC Random finished the background processing, RMS results will be imported
in to Patran Database.
4. Click on Patran Result Menu
5. Set Action to Create and Object to Quick Plot
6. Select Acceleration Result in Tz (Translation, Z) direction
7. Apply
Following Similar Procedure, Create Fringe Plots for RMS Von-Mises Stresses
References
1. Random Analysis with Coupled Excitations, sec 6.5, MSC Nastran Advanced Dynamic
Analysis Users Guide.
2. Random Response Analysis, sec 3.4, MSC Nastran 2004 Release Guide.
3. Segalman, D.J., C.W. Fulcher, G.M. Reese, and R.V. Field, Jr., An Efficient Method for
Calculating RMS Von Mises Stress in a Random Vibration Environment, Proceedings of the
16th International Modal Analysis Conference, Santa Barbara, CA, pp. 117-123.
4. X. Pitoiset, A. Preumont, A. Kernilis , Tools for a Multiaxial Fatigue Analysis of Structures
Submitted to Random Vibrations, Proceedings European Conference on Spacecraft Structures
Materials and Mechanical Testing Braunschweig, Germany, 4-6 November 1998 (ESA SP-428,
February 1999)
5. Francois Charron, Louis Donato and Mark Fontaine , Exact Calculation of Margin of Safety for
Frequency Response Analysis Stress Results using Yielding or Failure Theories, 1993 MSC
Worlds Users Conference, May 24-28, 1998, Arlington, VA. .
6. MSC Nastran Quick Reference Guide.
860
13.8
Appendix A
Frequency Response Analysis Setup for Example 3 was prepared using text editor. Same example is
repeated here, however using two different interfaces available within Patran. The core Patran Interface
will require more steps since it is more generic to all types of dynamic analysis (transient and frequency
response) whereas the interface within MSC Random is custom tailored for frequency response analysis
using unit input at all excited frequencies and will satisfy most needs.
Problem Definition:
In both cases, it is assumed that basic FEM model is created with all Material and Physical Properties.
FEM Model:
862
Hz. Assign Field Name: Damping, Click OK on Define Damping Table form
864
Create Output Frequency List: Click on Adv. Freq. Output and fill out output frequencies in
Define Frequencies Form. Click OK on Define Frequencies form and return to main menu.
866
Click on Apply, MSC Random will create following message, click OK.
868
13.9
870
872
874
Change Current Load case to Force_Loadcase and repeat procedure for Unit Force at tip
876
878
Specify all solution (output) frequencies. Make sure to define same output frequencies for all
subcases.
Change Modal Damping to Crit. Damp (CRIT)
Specify 2% Damping from 0.1 to 2000 Hz
Click OK on all forms and return Subcases Form and click on Output Request (see Next Page)
Type
For Strain Output, make sure to select either plane-curv or fiber
In MSC Random Interface, same set of output frequencies, damping, output request, applies to all load
cases, whereas in Patran Interface, output request, output frequency list, and damping need to be
specified for all load cases even if they are same.
Repeat All option on Subcase Form for second subcase, Force_Loadcase..
i.e. Output Frequencies, Damping (subcase parameter form) and all output requests.
880
and then Force_Loadcase. This is required since Random Input will refer to Subcase 1 as
Pressure Load.
Click OK and return to main form
Click Apply. MSC Nastran input file freq-plate will be created. See partial listing of input on
next page.
ENDDATA
7.
882
File Formats
IGES File
884
885
924
926
929
884
A.1
A.2
analysis model.
The neutral file is organized into small packets of two or more card images. Each packet contains the
data for a fundamental unit of the model, such as the coordinates and attributes of a specific node or the
definition of a specific finite element. The formats of the various data packets are not text for any
particular analysis program, and that is the basis for the term neutral.
Neutral File Packet Types Supported in Patran, 887 list all data packet types (if present) in the neutral
file. Each data packet type is identified by a number. Individual packets within a given type are written
in order of increasing ID number.
The most common use of the neutral file is to output a finite element
model for analysis. In this application, the neutral file is read by an
application interface which converts Patran model data into the required
input format for a particular analysis program. A typical example is the
PATNAS interface which translates neutral file data into a bulk data
deck for input to Nastran.
886
Sub-Structuring
Database Editing
Since the neutral file can be written in card image form, it can be edited
using an interactive editor. This capability can be useful for making
minor changes to your model data before analysis translation.
Archive Model
Packet Description
Import
Export
25
File title
26
Summary data
Import
Export
Packet Description
Node data
Element data
Material properties
Element properties
Coordinate frames
Distributed loads
Normal Pressures
Node forces
Node displacements
10
Node temperatures
11
Element temperatures
12
DOF lists
13
Mechanism entities
14
MPC data
15
888
Type Number
Packet Description
16
17
Convection coefficients
18
19
Viewfactor Data
21
Import
Export
X
Named components
22
23
*This nodal data packet (22) and the corresponding element counterpart (23) can be used in
place of packets 1 and 2, respectively. However they are not recognized by default and you must
use the PCL function, neutold_write_old_toggle(), before exporting/importing inorder
for them to be recognized Using this command toggles between the two different types (with
geometry association or without).
Geometry Model Packets
Type Number
Import
Export
Grid data
32
Line data
33
Patch data
34
Hyperpatch data
36
Data-line data
37
Data-patch data
38
Data-hyperpatch data
39
48
40
LIST card
41
DATA card
31
Packet Description
Packet Description
GFEG table for a line
Import
Export
CFEG table
Packet Description
46
Primitive data
47
99
Import
Export
890
Header Card
Format
IT
ID
IV
KC
IT
Packet Type
ID
IV
KC
N1 to N5=
(I2,8I8)
N1
N2
N3
N4
N5
The header card is followed by KC data card images. The meaning of the header variables for each
packet type plus the content and format of its data cards are presented in PATRAN 2.5 Neutral File
Contents and Format, 891. The packet types are listed in the order of their appearance (if present) in the
neutral file.
Header Card
25
Format
ID
IV
(I2,8I8)
KC
Format
(20A4)
h3
h3
Header Card
26
Format
ID
IV
KC
(I2,8I8)
N1
N2
ID=0 n/a
N1=Number of Nodes
IV=0 n/a
N2=Number of Elements
KC=1
N3=Number of Materials
N3
Format
DATE
TIME
VERSION
DATE
TIME
VERSION
N4
N5
892
Header Card
1
ID
Format
IV
(I2,8I8)
KC
ID=Node ID
IV=0 n/a
KC=2
Data Card 2
Format
ICF
NDF
GTYPE
CID
Data Card 1
X
Format
Z
(3E16.9)
PSPC
Header Card
2
ID
Format
IV
KC
(I2,8I8)
N1
N2
ID=Element ID
IV=Shape (2 = bar, 3 = tri, 4 = quad, 5 = tet, 7 = wedge, 8 = hex)
KC=1 + (NODES + 9)/10 + (N1 +4)/5(for text files)
N1=Number of associate data values
N2=ID of node in XY-plane (bar only)
Data Card 1
NODES
Format
CONFIG
CEID
1, 2, 3=Material Orientation angles (for bars, these values are the coordinates of a point in the bar
XY-plane)
*Config is used to specify the element type needed to interpret the element data in Packet Type 04.
Data Card 2
Format
(10I8)
LNODES
LNODES=Element corner nodes followed by additional nodes (for bars, two additional values beyond
the last node contain pin flags*).
* Pin Flags are not currently supported.
Data Card 3
Format
(5E16.9)
ADATA
ADATA=Associate data values (For bars, these are coordinates of the bar ends if offset from end
nodes).
894
Header Card
3
ID
Format
IV
KC
(I2,8I8)
N1
ID=Material ID
IV=Material type* (1-13)
KC=20 + (N1 +4)/5(for text files)
N1=Number of associate ply data values
Data Card 2
Format
(5E16.9)
DATA
DATA=96 Material property constants**
Data Card 3
Format
(5E16.9)
ADATA
ADATA*=Associated ply data values (thicknesses, orientation angles, material IDs.)
*ADATA will not be present if N1 is 0.
*Material Types:
1Isotropic
4TIS option
11HAL option
22D anisotropic
5TAN option
12LLAM option
33D orthotropic
6-73D anisotropic
13MIX option
2Density ()
896
Header Card
4
ID
Format
IV
KC
(I2,8I8)
N1
N2
N3
N4
ID=Property IDN1*=Shape
IV=Material IDN2=Nodes
KC=(N4 + 4)/5N3*=Configuration
N4=Number of data fields
* Definition of applicable element type (see Packet Type 02)
Data Card
Format
DATA
DATA=Property data for the defined element type as required by the
analysis program. (1 to 5 property fields per record in 16 character fields.)
Header Card
5
Format
ID
IV
(I2,8I8)
KC
ID=Coordinate frame ID
IV=Coordinate type (1 = rectangular, 2 = cylindrical, 3 = spherical)
KC=4 (for text files)
Data Card 1 to 4
A1
A2
A3
B1
Format
B2
B3
C1 C2
C3
R(1,1)
(5E16.9)
R(2,1)......R(3,3)
A1, A2, A3
B1, B2, B3,
898
Header Card
6
ID
Format
IV
(I2,8I8)
KC
ID=Element ID
IV=Load Set ID
KC=1 + NPV + 4)/5(for text files)
Data Card 1
6
LTYPE
Format
EFLAG
CFLAG
NODE(8)
Data Card 2 to KC
Format
(5E16.9)
PDATA
PDATA=Non-zero load components *
* Define NC=Number of ICOMP flags on (=1)
NN=Number of NODE flags on (=1)
Then, the number of PDATA entries:
NPV=NC*(EFLAG + NN*GFLAG)
Order of PDATA is as follows:
1. NC load values at centroid of loaded region (if EFLAG = 1).
2. NC load values at each corner node on the loaded region (if GFLAG = 1).
The NODE flags correspond to the LNODES nodes in Packet type 02.
NFE
Header Card
7
Format
ID
IV
(I2,8I8)
KC
ID=Node ID
IV=Load Set ID
KC=1 + (NDW +4)/5(for text files)
Data Card 1
CID
Format
(I8, 6I1)
ICOMP(6)
CID=Coordinate frame ID
ICOMP=6 force component flags (0 or 1)
Data Card 2 to KC
Format
FDATA
FDATA=Non-zero force components
NDW = Sum of ICOMP(I), I=1,6
(5E16.9)
900
Header Card
8
ID
Format
IV
(I2,8I8)
KC
ID=Node ID
IV=Constraint set ID
KC=1 + (NDW +4)/5(for text files)
Data Card 1
CID
Format
(I8, 6I1)
ICOMP(6)
CID=Coordinate frame ID
ICOMP=6 displacement component flags (0 or 1)
Data Card 2
Format
FDATA
FDATA=Non-blank displacement components (may be 0.0)
NDW = Sum of ICOMP(I), I=1,6
(5E16.9)
Header Card
10
ID
Format
IV
KC
(I2,8I8)
N1
N2
Data Card 1
TEMP
TEMP=Temperature value
Format
(E16.9)
902
Header Card
11
ID
Format
IV
KC
(I2,8I8)
N1
N2
Data Card 1
TEMP
TEMP=Temperature value
Format
(E16.9)
Header Card
14
ID
Format
IV
KC
(I2,8I8)
NT
NDT
ID=MPC ID
IV=MPC SID
KC=2 + (NT +1)/2(for text files)
NT=Total number of terms(Right side of equation)
NDT=Number of dependent terms(Implicit MPC)
Data Card 1
DN
IN
Format
(3A12)
TYPE
Data Card 2
NID
DOF
Format
(2I8, E16.9)
CO
NID=Dependent node ID
DOF=Dependent degree-of-freedom
C0=Constant term
Data Card 3
NID(I),
DOF(I),
Format
CO(I),
2(2I8, E16.9)
I = 1, NT
U0 = U1 C1 + U2 C2 + U3 C3 + + Un Cn + C0
where U i is specified by NID(I) and DOF(I) and C i is specified by C(I).
904
Header Card
15
ID
Format
IV
KC
(I2,8I8)
N1
N2
Data Card 1
HEAT
HEAT=Heat flux value
Format
(E16.9)
Header Card
16
Format
ID
IV
KC
(I2,8I8)
N1
ID=Element ID
N2
N3
N3 = Dimension code
0 No heat flux dimension
1 HEAT is per unit length
2 HEAT is per unit area
3 HEAT is per unit volume
Data Card 1
NFLAG
Format
Format
(5E16.9)
NODE(8)
NFLAG=Node flag (0 or 1)
NODE=8 element node flags (0 or 1)
906
Header Card
17
Format
ID
IV
KC
(I2,8I8)
N1
N2
Data Card 1
NFLAG
Format
Format
(5E16.9)
NODE(8)
NFLAG=Node flag (0 or 1)
NODE=8 element node flags (0 or 1)
Data Card 2
CONV(5)
CONV=Convection coefficient values*
Header Card
18
Format
ID
IV
KC
(I2,8I8)
N1
N2
Data Card 1
NFLAG
Format
Format
(5E16.9)
NODE(8)
NFLAG=Node flag (0 or 1)
NODE=8 element node flags (0 or 1)
Data Card 2
EMIS(5)
EMIS=Convection coefficient values*
908
Header Card
18
ID
Format
IV
KC
(I2,8I8)
N1
N2
Data Card 1
NODE1
NODE2
Format
CVSID
OBSTR
(6I8,2X,8I1)
DYN
SURF
NODE(8)
Header Card
21
Format
ID
IV
(I2,8I8)
KC
ID=Component number
IV=2 times the number of data pairs
KC=1 + (IV + 9)/10 (for text files)
1 + (IV + 509)/510(for binary files)
Data Card 1
Format
(A12)
NAME
NAME=Component Name
Data Card 2
NTYPE(1)*
Format
ID(1)
NTYPE(2)
(10I8)
ID(2)
........
NTYPE(5)
(NTYPE(i), ID(i)) =Data pairs defining type and ID number of each item in this
(I = 1, IV/2)component.
*NTYPE meanings:
1grid#
8quadrilateral
2line
9tetrahedron
3patch
11wedge
4hyperpatch
12hexahedron
5node
19coordinate frame
6bar
22multi-point constraints
7triangle
NTYPEs 6-12 may have 100 or 200 added to the basic NTYPE. The number of hundreds
is usually the number of midside nodes.
ID(5)
910
Header Card
49
ID
Format
IV
(I2,8I8)
KC
ID=Node ID
IV=0 n/a
KC=2
Data Card 1
X
Format
(3E16.9)
Data Card 2
ICF
GTYPE
Format
NDF
CONFIG
PSPC
GTYP
GID
This nodal data packet (22) and the corresponding element counterpart (23) can be used in place of
packets 1 and 2, respectively. However they are not recognized by default and you must use the PCL
function, neutold_write_old_toggle(), before exporting/importing inorder for them to be recognized Using this command toggles between the two different types (with geometry association or
without).
Header Card
50
ID
Format
IV
KC
(I2,8I8)
N1
N2
GTYP
GID
ID=Element ID
IV=Shape (2 = bar, 3 = tri, 4 = quad, 5 = tet, 7 = wedge, 8 = hex)
KC=1 + (NODES + 9)/10 + (N1 +4)/5(for text files)
N1=Number of associate data values
N2=ID of node in XY-plane (bar only)
GTYP = Associated Geometry entity type (1=Vertex, 2= Curve, 3=surface, 4=solid)
GID = Geometry Entity ID
Data Card 1
NODES
Format
CONFIG
CEID
1, 2, 3=Material Orientation angles (for bars, these values are the coordinates of a point in the bar
XY-plane)
*Config is used to specify the element type needed to interpret the element data in Packet Type 04.
Data Card 2
Format
(10I8)
LNODES
LNODES=Element corner nodes followed by additional nodes (for bars, two additional values beyond
the last node contain pin flags*).
* Pin Flags are not currently supported.
This elemental data packet (23) and the corresponding nodal counterpart (22) can be used in place
of packets 2 and 1, respectively. However they are not recognized by default and you must use the
PCL function, neutold_write_old_toggle(), before exporting/importing inorder for them to
be recognized Using this command toggles between the two different types (with geometry association or without).
912
Data Card 3
Format
(5E16.9)
ADATA
ADATA=Associate data values (For bars, these are coordinates of the bar ends if offset from end
nodes).
Header Card
31
ID
Format
IV
(I2,8I8)
KC
ID=Grid ID
IV=0 not/applicable
KC=1
Data Card 1
X
Format
Z
(3E16.9)
914
Header Card
32
ID
Format
IV
(I2,8I8)
KC
ID=Line ID
IV=0 not/applicable
KC=3(for text files)
Data Card 1 to
3
B(1,1),
B(2,1)
Forma
t
B(3,1)
(5E16.9/5E16.9/2E16.9,2I8)
.....
B(4,3)
IG1
IG2
Header Card
33
ID
Format
IV
(I2,8I8)
KC
ID=Patch ID
IV=0 not/applicable
KC=10(for text files)
Data Card 1 to 10
B(1,1),
B(2,1)
Format
B(3,1)
9(5E16.9/5), 3E16.9/2E16.9,4I8
.....
B(16,3)
IG(4)
916
Header Card
34
ID
Format
IV
(I2,8I8)
KC
ID=Hyperpatch ID
IV=0 not/applicable
KC=40(for text files)
Data Card 1 to 40
B(1,1),
B(2,1)
Format
B(3,1)
38(5E16.9/), 3E16.9/,8I8
.....
B(64,3)
IG(8)
Packet Types 42, 43 or 44: GFEG Table for Line, Patch or Hyperpatch 1
(when created from a GFEG command)
Header Card
IT
Format
ID
IV
(I2,8I8)
KC
N1
N2
IT=42, 43, or 44
ID=Line, patch or hyperpatch ID
IV=Number of nodes contained in region
KC=5 +IV (for text files)
N1=1 (signifies this packet is 2.0 format)*
* This parameter is not currently used.
Header Card
IDELTA
Format
N1
N2
MAXMAG
IFACE
Data Card 2
Format
1The
918
Data Card 3
Format
(3E16.9)
Format
(3E16.9)
Format
STRTCH
STRTCH(3)=Mesh ratios
Data Card 4
AUXC
AUXC=Auxiliary mesh constants
Data Card 5
IDUM(8)
IOLD
NACTUL
Data Cards 6 to KC
XI(3)
NFLAG
Format
NID
Node data
XI(3)=Real parametric coordinates in 1, 2 and 3 directions
of parent line, patch or hyperpatch
NFLAG=Flag word
NID=Node ID number
+ if specified by user,
- if assigned by Patran
Packet Type 42, 43 or 44: GFEG Table for Line, Patch or Hyperpatch
(when created from a MESH command)
Header Card
IT
ID
Format
IV
KC
(I2,8I8)
N1
N2
IT=42, 43, or 44
ID=Line, patch or hyperpatch ID
IV=Number of nodes contained in region
KC=5 +IV(for text files)
Data Card 1
NL1
NL2
Format
NL3
NL4
(I0I8)
NL5
IFACE
Data Card 2
Format
920
Data Card 3
Format
(3E16.9)
STRTCH
STRTCH=Mesh ratios for edges 1, 2 and 3
Data Card 4
Format
(3E16.9)
STRTCH
STRTCH=Mesh ratios for edge 4 and 3 direction (followed by one word
reserved for future use)
Data Card 5
Format
IDUM(8)
IOLD
NACTUL
Data Cards 6 to KC
XI(3)
NFLAG
Format
NID
Node data
XI(3)=Real parametric coordinates in 1, 2 and 3 directions
of parent line, patch or hyperpatch
NFLAG=Flag word
NID=Node ID number
+ if specified by user,
- if assigned by Patran
Data Card 1
LPH
ID
Format
LSHAPE
(6I8)
DGFLAG
MINID
MIAXID
Data Card 2
NDIM
LSHAPE
Format
NODES
ICONF
(6I8)
LPH
ID
LPROP
NPROP
922
Data Card 2 to KC
Format
(10I8)
LCON(10)
LCON(10)=Element data (NELS records with NDIM words per second)
Words 1 through NODEs = Element Nodes*
Word NDIM=Element ID number
+ if specified by user
- if assigned by Patran
*These are local node ID numbers corresponding to record numbers in the associated GFEG table.
Header Card
45
ID
Format
IV
KC
(I2,8I8)
N1
N2
Header Card
99
ID
ID=0 not/applicable
IV=0 not/applicable
KC=1
Format
IV
(I2, 8I8)
KC
924
A.3
Session files can be recorded from current models. Session files are
designed to contain any combination of comments, PCL (PATRAN
Command Language), executable statements and most ASM NOODL
commands. Each command entered into the command line either directly
by the user (e.g., keyboard input, history recall) or indirectly (commands
indicated as events of interest by applications) are recorded.
Session files are text files that may contain PCL statements or NOODL
commands. No single physical line may exceed 256 characters. The
logical line length limit is 7000 characters.
Session files are designed to support the PCL comment marker ($). In
addition, there are two special cases of comments that are written to a
session file. Any comment lines that do not contain one of these two
special comment markers will be written unchanged to the recording
session file. None of these lines are executable, but may have varying
results during playback of a session file and the recorded session file.
System comments ($#)
Patran writes out certain comments using the system comment marker.
These include messages about session file start and end information.
When a session file is read, any lines with this marker are ignored and not
displayed in the history window or recorded in the recording session file.
A user can enable and disable the writing of these comments using the
PCL built-in command verbose.
Message responses ($?)
The execution of certain statements may require a response from the
message facility. This marker is used to indicate a line is a message
response. On playback, if a response is required, the system first attempts
to satisfy it from these stored message responses. If a response is
encountered in a session file but not required, it is ignored. All valid or
unneeded message responses are preserved; wrong responses are deleted.
The form of a message response is as follows:
$? <response> <msg number> <partial text of
message>
Any line that has a message number (<msg number>) value of -1 will
match any message number.
Journal File
A journal file contains, a listing of the commands in all the session files
ever created, since the creation of the database. Although the format of
the journal file is identical to the session file, a separate session file is
created each time the database is opened, while the single journal file is
only appended. The journal file is used as input to the rebuild database
utility. See File>Rebuild, 77 for more information.
926
A.4
IGES File
The Initial Graphics Exchange Specification (IGES) is a mechanism for the digital exchange of database
information among present day CAD systems. Its history has seen a rapid development of capability,
formalization into an ANSI standard, widespread implementation across the vendor community and
substantial commitments for production use. Engineering drawings, 3-D wireframe and surfaced part
models, printed wiring product descriptions, finite element mesh descriptions, Constructive Solid
Geometry (CSG), B-Rep Solid Geometry, and process instrumentation diagrams are addressed by the
IGES standard. This is the level of technology embodied by IGES and by present generation CAD
systems.
IGES was developed by the IGES/PDES Organization and is supported by the U.S. Department of
Commerce, National Institute of Standards and Technology (NIST) in Gaithersburg, Maryland.
Concepts of Product Definition
The requirements for a common data communication format for product definition can be understood in
terms of todays CAD/CAM environment. Traditionally, engineering drawings and associated
documentation are used to communicate product definition data. Commercial interactive graphics
systems, originally developed as aids to producing these two-dimensional drawings, are rapidly
developing sophisticated three-dimensional solid modeling. In parallel, extensive research work is being
conducted in advanced geometric modeling techniques (e.g., parametric representations and solid
primitives) and in CAM applications utilizing product definition data in manufacturing (e.g., NC
Machining and computer-controlled coordinate measurement). The result is rapid growth of CAD/CAM
applications, allowing exchange of product definition data, which usually employ incompatible data
representations and formats. In addressing this compatibility, the IGES specification is concerned with
needs and capabilities of current and advanced methods of CAD/CAM product definition development.
Product definition data may be categorized by their principal roles in defining a product. An example of
such a categorization is presented in Figure A-1. The IGES specification specifies communications
formats (information structures) for subsets of the product definition:
Administrative
Product Identification
Product Structure
Design/Analysis
Idealized models
Basic Shape
Geometric
Topological
Processing Information
Presentational Information
Figure A-1
928
reside in another file. Typical non-geometry entities for drawing definition, annotation, and dimensioning
are the view, drawing, general note, witness line, and leader. Typical non-geometry entities for attributes
and groupings are the property and the associativity entities.
A file consists of five or six sections: Flag (in the case of the binary or compressed ASCII form), Start,
Global, Directory Entry, Parameter Data, and Terminate. A file may include any number of entities of
any type as required to represent the product definition. Each entity occurrence consists of a directory
entry and a parameter data entry. The directory entry provides an index and includes descriptive attributes
about the data. The parameter data provides the specific entity definition. The directory data are
organized in fixed fields and are consistent for all entities to provide simple access to frequently used
descriptive data. The parameter data are entity-specific and are variable in length and format. The
directory data and parameter data for all entities in the file are organized into separate sections, with
pointers providing bidirectional links between the directory entry and parameter data for each entity. The
specification provides for groupings whose definitions will be found in a file other than the one in which
they are used.
Each entity defined by the file structure has a specific assigned entity type number. While not all are
assigned at this time, entity type numbers 0000 through 0599 and 0700 through 5000 are allocated for
specific assignment. Entity type numbers 0600 through 0699 and 10000 through 99999 are for
implement-defined (i.e., macro) entities.
Some entity types include a form number as an attribute. The form number serves to further define or
classify an entity within its specific type.
The entity set includes a provision for associativities and properties. The Associativity Entity provides a
mechanism to establish relationships among entities and to define the meaning of the relationship. The
Property Entity allows specific characteristics, such as line widening, to be assigned to an entity or
collection of entities. Each entity format includes a structure for an arbitrary number of pointers to
associativities and properties. The file structure provides for both predefined associativities and
properties to be included in the specification and unique definitions which will be defined by the
implement.
A.5
930
Record N+3:
Parameter
Description
h3
SUBTITLE1
SUBTITLE2
NNODES
MAXNOD
DEFMAX
NDMAX
NWIDTH
DX(N),
RX(N),
RZ(N)
NODID
DX
DY
DZ
RX
RY
RZ
Text Version
Record 1:
Record 2:
Record 3:
Record 4:
Record 5 to n+4:
h3
NNODES, MAXNOD, DEFMAX,
E15.6, 2I9)
NDMAX, NWIDTH
SUBTITLE1
SUBTITLE2
NODID, (DATA(J), J=1, NWIDTH)
(5E13.7))
(80A1)
(2I9,
(80A1)
(80A1)
(I8,
932
Binary Version
Record 1:
Record 2:
Record 3:
Record 4:
Record 5:
.
Record N+3:
Parameter
Description
h3
SUBTITLE1
SUBTITLE2
NNODES
MAXNOD
DEFMAX
NDMAX
NWIDTH
NODID
DATA
ger)
Text Version
Record 1:
Record 2:
Record 3:
Record 4:
Record 5 to n+4:
Note:
h3
NNODES, MAXNOD, DEFMAX,
E15.6, 2I9)
NDMAX, NWIDTH
SUBTITLE1
SUBTITLE2
NODID, (DATA(J), J=1, NWIDTH)
(5E13.7))
(80A1)
(2I9
(80A1)
(80A1)
(I8,
TITLE, NWIDTH
SUBTITLE1
SUBTITLE2
ID, NSHAPE, (DATA(J), J=1, NWIDTH)
ID, NSHAPE, (DATA(J), J=1, NWIDTH)
Parameter
Description
h3
SUBTITLE1
SUBTITLE2
NWIDTH
ID
NSHAPE
DATA
934
Text Version
Record 1:
Record 2:
Record 3:
Record 4:
Record 5 to n+4:
h3
NWIDTH
SUBTITLE1
SUBTITLE2
ID, NSHAPE, (DATA(J), J=1,NWIDTH)
(6E13.7))
(80A1)
(I5)
(80A1)
(80A1)
(2I8, /,
.00500058
4
.1492715E+05-.3057466E+03 .2852407E+01-.5369175E+01 .0000000E+00
.1488886E+05-.8247605E+04-.8088444E+04 .3114060E+03 .2852407E+01
.0000000E+00-.5445350E+04 .8186974E+04 .0000000E+00 .2237059E+04
4
.1174489E+05 .2986205E+03-.3140930E+03 .2887558E+03 .0000000E+00
.1023987E+05-.2068523E+04-.6511836E+04-.1064728E+03-.3140930E+03
.0000000E+00-.2860119E+04 .5766014E+04 .0000000E+00 .1683378E+04
4
.3225449E+04-.2815713E+04-.3211482E+03-.1085647E+04 .0000000E+00
.1125793E+05 .1245072E+05 .7406104E+03 .3047678E+04-.3211482E+03
.0000000E+00 .4397110E+04 .1319897E+05 .0000000E+00 .1379138E+04
Parameter
TITLE, NWIDTH
SUBTITLE1
SUBTITLE2
ID(1), STAT(1), (DATA(J), J=1, NWIDTH)
ID(1), STAT(2), (DATA(J), J=1, NWIDTH)
ID(1), STAT(n), (DATA(J), J=1, NWIDTH)
ID(2), STAT(1), (DATA(J), J=1, NWIDTH)
ID(2), STAT(2), (DATA(J), J=1, NWIDTH)
ID(2), STAT(m), (DATA(J), J=1, NWIDTH)
ID(N), STAT(1), (DATA(J), J=1, NWIDTH)
ID(N), STAT(2), (DATA(J), J=1, NWIDTH)
ID(N), STAT(k), (DATA(J), J=1, NWIDTH)
Description
h3
SUBTITLE1
SUBTITLE2
NWIDTH
ID
STAT
1.).
STAT(1)
Should always be 0.
STAT(m), STAT(n), and STAT(k)
Should always be 1.
DATA
Note:
936
A results template file is required for each PATRAN 2.5 results file type to be imported. You can create
or customize your own results template file.
The structure of the results template file is as follows:
Keyword
Data Type
Allowable Value
Description
Column number where
translation key is found, or
0 if no translation key is
required.
KEYLOC
integer
TYPE
character string
KEY
integer
COLUMN
integer
1, 3 or 6
Column numbers to be
translated.
PRI
character string
Character string up to
80 characters in length.
SEC
character string
Character string up to
80 characters in length.
Secondary label
definition. This will
appear in the Select
Results box of the
Results Display form.
CTYPE
character string
Type of element
coordinate frame
(required if TYPE is
vector or tensor).
1:
2:
3:
4:
5:
KEYLOC = <value>
TYPE= <value>
KEY = <value> (required if KEYLOC does not equal zero.)
COLUMN = <value(s)>
PRI = <value>
Example 1
Example 2
KEYLOC = 0
TYPE = SCALAR
COLUMN = 11
PRI = Stress
SEC = von Mises
TYPE = TENSOR
COLUMN = 25, 26, 27, 28, 29, 30
PRI = Stress
SEC = Components
CTYPE = ELEM
TYPE = END
KEYLOC = 19
TYPE = SCALAR
KEY = 67
COLUMN = 11
PRI = Stress
SEC = von Mises
TYPE = SCALAR
KEY = 33
COLUMN = 11
PRI = Stress
SEC = von Mises
TYPE = TENSOR
KEY = 67
COLUMN = 25, 26, 27, 28, 29, 30
PRI = Stress
SEC = Components
CTYPE = ELEM
TYPE = TENSOR
KEY = 33
COLUMN = 15, 16, 0, 18, 0, 0
PRI = Stress
SEC = Components
CTYPE = ELEM
TYPE = END
column
column
column
column
column
column
15
16
27
18
29
30
and 25 represents
and 26 represents
represents the ZZ
and 28 represents
represents the YZ
represents the ZX
The keys used in Example 2 are for a CHEXA element (element type 67) and a CQUAD4 element
(element type 33), as defined in the Overview (p. 1) in the Patran Interface to MSC Nastran Preference
Guide.
938
Printing Options
Introduction
940
Hardware Setup
941
942
943
944
945
940
B.1
Introduction
There are numerous ways to produce a hardcopy of your workstation screen, from platform-specific
programs that create a bit-mapped image to photographing the screen. One of the available methods is
the Print utility provided with Patran. It is designed to be flexible and easy to use.
Patran provides user control over creating hardcopy output from within the Print forms. Refer to
File>Print, 223 for a description of these forms. The device-dependent hardcopy file varies depending on
the specific hardcopy device requirements. Refer to Device-dependent Hardcopy File, 941.
B.2
PatranHard Default
CGM
HPGL
HPGL/2 Default
PatranHard to PostScript
Default
942
B.3
If you frequently experience problems with large plot files that hang up
your terminal or cannot be plotted in their entirety, you may need
additional memory. Contact your hardware supplier for more information
on how to determine if more printer/plotter RAM is necessary.
Pen Plotters
The order your pens are placed in the carousel can affect your plot output.
Refer to your HPGL or HPGL/2 users guide for more information.
Printer/Plotter
Hardware Settings
Most plotters and some printers have front panels that allow you to control
the printer/plotter settings. Please refer to your printer/plotter manual for
information on how to modify these settings.
B.4
Bad Hardware
Connection
Verify that the connection between the workstation and the printer/plotter
is valid. This can be done by submitting another plot to be printed/plotted.
Usually the printer/plotter vendor provides a small test program which
can serve as a check.
Wrong Printer/Plotter
Destination
Network Problems
Hardware Memory
Hardware Problems
The manual for your printer/plotter may contain additional information to help you diagnose any
problems.
944
B.5
Hardware Setup
There are numerous ways to set up printers/plotters so that the four Patran hardcopy drivers (HPGL,
HPGL-2, CGM and PostScript) can communicate with the hardware. The most common ways are:
Laser Printer
Spooler
Plotters
lp (HP700 platform)
lpr (Solaris/SGI/Digital UNIX/IBMRS6K/Windows NT)
Destination
cat
Destination
Again, keep in mind that your setup could be very different from the above. Your system administrator
should be able to assist Patran users with printer/plotter setups for your computer environment.
B.6
HPGL
HP DraftPro
HP DraftPro DXL
HP DraftPro EXL
HP 7475, 7220, 7440, 7470, 7550, 7570, 7580, 7585, 7586, 7595, 7596,
9872
HP Design Jet (HP 7586 emulation only)
HPGL/2
HP 7600 Series Model 355, 255, 250, 240D and 240E with HP C1643A
upgrade
HP DraftMaster MX, RX, and SX
HP DraftMaster I & II with HP 17658A upgrade
HP 7550 Plus
HP PaintJet XL with optional HP-GL/2 cartridge
HP DesignJet
CGM
946
PatranReference Manual
Mass Properties
948
948
PatranReference Manual
Summary of Mass Properties
C.1
Newly created principal inertia coordinate frames are assigned the next available coordinate frame ID in
the database. Mass Properties report files are written in standard Patran report file format. Each Mass
Properties report contains all of the mass properties along with a list of all included entities and a list of
all rejected entities.
The densities, shell thicknesses, beam cross-sectional areas, non-structural mass, and concentrated mass
values used to calculate mass properties come from element property definitions by default, but you can
override the element property records by using 1.0 for densities, thicknesses, and areas; and using 0.0 for
non-structural mass and concentrated mass. The mass properties are generated in units that are consistent
with those used in your referenced geometry, element properties, and material properties. For the entity
display method, the actual plate thickness, areas, and bar length will be displayed regardless of the
Thicknesses/Areas/NSM setting. If no properties exist for an element then a value of -- will be
displayed if the Thickness/Areas/NSM menu is set to unity.
All offsets are ignored. Mass property calculations are based on the assumption that all element offsets,
including beam, shell, and concentrated mass offsets, are zero. If a referenced entity has an offset, a
warning is issued. Non-structural mass is included in the calculation, while non-structural inertia is
ignored without a warning. Constant and variable-thickness plates and shells are supported. General
beams and rods with constant or variable cross-sectional areas are supported, but only tapered beams with
constant cross-sectional areas are supported. Furthermore, beams defined using cross-sectional
dimensions instead of section properties (e.g., I-beams requiring the input of web and flange dimensions)
are supported. Concentrated masses are supported, but direct-input mass matrices are not. Composite
materials are supported. If a composite property such as laminate thickness is defined in both the element
property record and in the material record, then the value in the element property record will be used.
Material densities defined with fields are not supported. If you are not sure whether an entity is supported,
you can put it into a new group containing no other entities and attempt to generate mass properties for
that group. Patran will then tell you if that entity is supported.
Mass properties for shells are calculated by treating the thickness as a weighting function and assuming
that all mass lies in the surface of the shell. Likewise, beam mass property calculations treat the crosssectional area as a weighting function with all mass assumed to lie in the locus of the 1D beam. Thus the
mass properties calculated for these entities differ slightly from those based on the corresponding 3D
solids.
If you specify that your Mass Properties Region includes only Geometry, and you further specify that
densities, concentrated masses, thicknesses, or areas are to be taken from Element Property records, then
those records must be defined on the geometry and not on the FEM entities within the geometry. If,
however, you change the Mass Properties Region to include only FEM entities, then any needed Element
Property records may be defined on either the FEM entities themselves, or the geometry containing the
FEM entities.
Field defining thickness, cross-sectional area, and non-structural mass are taken into detailed analysis.
For a geometry entity in the mass property region, a field property is integrated over the entity regardless
of the propertys value type. For a FEM entity, a field property is evaluated at the centroid of the entity
if the propertys value type is real scalar, and is integrated over the entity if the propertys value type is
element nodal. Discrete FEM fields are supported only for real scalar properties of FEM entities.
Patran attempts to treat all entities as though they are consistent with the selected analysis model type,
regardless of the element type of the entitys element property record. For example, if a surface is
assigned an element property record corresponding to that of a non-axisymmetric shear panel, and the
surface is subsequently referenced for a 2D axisymmetric mass property calculation, Patran will calculate
the mass properties for the solid of revolution generated by that surface as long as it can find the
properties it needs to do the calculation (and as long as the surface lies in the user-specified modeling
plane). In this case it only needs to find the density defined in the material referenced by the element
property record.
Naturally, however, all entities are removed from the user-specified region that are geometrically
inconsistent with the analysis model type. Two entities that are geometrically inconsistent with 2D
950
PatranReference Manual
Summary of Mass Properties
Axisymmetric analyses, for example, are surfaces that do not lie in the axisymmetric modeling plane, and
solids. Entities lacking a needed property such as density are also discarded. Upon completion, the user
receives a warning if any specified entities were ignored. The warning includes a list of all rejected
entities.
Mass Properties for 3D Models
The 3D Analysis Type option is the default choice, and it is the only Analysis Type option that does not
exclude any entities based on their dimensionality, i.e., all 0D, 1D, 2D, and 3D entities can be included.
This is the only option that supports display on a per group or per entity basis.
Mass Properties for 2D Axisymmetric Models
The 2D Axisymmetric option is used to generate the mass properties of the 3D body given the 2D
axisymmetric model. It is intended for axisymmetric shells, solids, and concentrated masses.
Accordingly, only 0D, 1D and 2D entities may be included. Specified entities not lying in the
axisymmetric modeling plane are omitted from the mass property calculations and added to the output
list of rejected entities. Masses assigned to concentrated mass elements in axisymmetric problems are
treated as linear mass densities. Patran calculates the mass of the equivalent 1D hoop by multiplying the
input mass by 2r. Likewise, the moments of inertia applied to concentrated masses in axisymmetric
models are treated as linear moment of inertia densities. The inertia tensor of the equivalent 1D hoop due
to the input moments of inertia is obtained by multiplying the input moments of inertia by 2r. The
careless use of input product of inertia terms in axisymmetric concentrated mass elements can result in
calculated mass properties that are not axisymmetric.
The 2D Axisymmetric option cannot be used to calculate the mass properties of non-axisymmetric cyclic
symmetry models. These are supported in 3D mode only, in which case the mass properties are calculated
for the model only, and not for the entire structure which would be generated by the prescribed rotational
and reflective transformations.
Mass Properties for 2D Plane Stress and 2D Plane Strain Models
The 2D Plane Stress and 2D Plane Strain options include coplanar 0D and 2D entities only. The 2D
entities are assumed to have unit thickness. The modeling plane is assumed to be the plane of the first 2D
entity. If there are no 2D entities, then it is assumed to be the plane of the first three non-collinear 0D
entities. Specified entities not lying in this plane are omitted from the mass property calculations and
added to the output list of rejected entities.
List Processor
952
952
D.1
Wherever white space is necessary to separate two items from one another, the list
processor will accept any number of blank characters, commas, or slashes without
distinction.
Geometry
Points
Referring to points which already exist in the database
The simplest form of point selection yields pick lists which refer to points that already exist in the Patran
database. The syntax for this form can be described symbolically as follows:
<pointInDatabaseList>
::=
<pointKW>
<pointLabelList>
::=
::=
<int>
<digit>
<throughKW>
<byKW>
::=
::=
::=
::=
Table D-1
Meaning
Pt1
Point 1.
Point 1 2 3
Points 1, 2, and 3.
Point 1:2 Gr 3
Points 1, 2, and 3.
G1T9B2
Points 1, 3, 5, 7, and 9.
Grid 1,3/5,7,9
Points 1, 3, 5, 7, and 9.
Grid 1 Pt 3:5:2 / G7 G9
Points 1, 3, 5, 7, and 9.
Referring to points which exist as the vertexes of other entities which exist in the database
Patran allows applications to use points in a topological context for any operation where points are valid.
That is, if it is more convenient to refer to points in their vertex context to edges or faces, Patran will
allow it. The syntax for using this form can be described symbolically as:
<pointTopologicallyInDatabaseList>
::=
<curveVertexList>
::=
{ <curveVertexList> } 0:n {
<surfaceVertexList> } 0:n {
<solidVertexList> } 0:n
<curveKW>
<singleToplogicalIndentLabelList>
{
<singleToplogicalIndentLabelList>
} 0:n
954
<surfaceVertexList>
::=
<solidVertexList>
::=
<curveKW>
<singleTopologicalIndentLabelList>
::=
::=
<surfaceKW>
::=
<doubleTopologicalIndentLabelList>
::=
<solidKW>
::=
<tripleTopologicalIndentLabelList>
::=
<int>
<digit>
::=
::=
<throughKW>
<byKW>
::=
::=
Table D-2
<surfaceKW>
<doubleTopologicalIndentLabelList>
{
<doubleTopologicalIndentLabelList>
} 0:n
<solidKW>
<tripleTopologicalIndentLabelList>
{
<tripleTopologicalIndentLabelList>
} 0:n
Curve | Crv | C | Line | Li | L
<int>.<int> | <int> <throughKW>
<int>.<int> | <int> <throughKW>
<int> <byKW> <int>.<int>
Surface | Surf | Srf | C | Patch |
Pa | P
<int>.<int>.<int> | <int>
<throughKW> <int>.<int> .<int> |
<int> <throughKW> <int> <byKW>
<int>.<int>.<int>
Solid | Sld | Sl | Hyperpatch |
Hpat | Hp | H
<int>.<int> .<int>.<int> | <int>
<throughKW>
<int>.<int>.<int>.<int> | <int>
<throughKW> <int> <byKW>
<int>.<int>.<int>.<int>
{ + | - } 0:1 { <digit> } 1:n
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
9
: | T | Through
: | B | By
Meaning
Curve 1.1
Vertex 1 of curve 1.
Surface 1:10:3.1.2
Referring to points by referring to finite element nodes which exist where a point is to
be located
Point lists can also be formed by the selection mechanism from finite element nodes which already exist
in the Patran database. Any application which uses the point list to gather [X Y Z] geometry for further
processing, rather than for label or ID information, will accept point lists which coerce values from the
finite element node definitions. The syntax for this form is described symbolically as:
<pointFromNodeInDatabaseList>
::=
<nodeKW> <nodeLabelList> {
<nodeLabelList> |
<pointFromNodeInDatabaseList> } 0:n
<nodeKW>
::=
Node | Nde | N
<nodeLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-3
Meaning
Node 20:30
The locations of nodes 30, 28, 26, 24, 22, 20, 29, 27, 25,
23, and 21 will be used as the [X Y Z] for an application
requesting [X Y Z] information.
956
mechanism yields points with a Z coordinate of zero, while the desired point has a non-zero Z coordinate.
The syntax for this type of pick list can be described symbolically as:
<pointImmediateXyzList>
::=
<float>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
Table D-4
Meaning
[1 2 3]
[1 2 3] [4 5 6] [7 8 9]
Points at x=1, y=2, z=3; x=4, y=5, z=6; x=7, y=8, z=9
will be used as the [X Y Z] for an application requesting
[X Y Z] information.
one may decide to directly input the specific [X Y Z] necessary for correct geometry generation. The
syntax for this type of pick list can be described symbolically as:
<pointImmediateList>
::=
<xPortion>
::=
<yPortion>
::=
<zPortion>
::=
<float>
::=
<pointLabel>
::=
<int>
<nodeLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
Table D-5
Meaning
[x1/yn2/100]
958
found, an error is returned. In the case of multiple intersections, the first solution found is used. The
syntax for this type of expression is diagrammatically described as:
<2CurvePointExpression>
::=
<constructKW> <2CurvePointKW>
<curveGeometryExpression>
<curveGeometryExpression>
constructKW
::=
Construct | Co | Make
<2CurvePointKW>
::=
<curveGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<curveExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry | Geo
<curveExpression>
::=
<curveInDatebaseExpression> |
<curveConstructionExpression>
<curveInDatabaseExpression>
::=
<curveByDatabaseLabelExpression> |
<surfaceEdgeExpression> |
<solidEdgeExpression>
<curveByDatabaseLabelExpressi
on>
::=
<curveKW> <curveLabel>
<curveKW>
::=
<curveLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<surfaceEdgeExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<solidEdgeExpression>
::=
<solidKW><solidLabel>.<solidFace>.
<solidFaceEdge>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<curveConstructionExpression>
::=
<2PointCurveExpression> |
<2SurfaceCurveExpression>
Note:
960
expression, if no intersections are found, an error is returned. In the case of multiple intersections, the
first solution found is used. The syntax for this type of expression is diagrammatically described as:
<curveSurfacePointExpression>
::=
<constructKW>
<curveSurfacePointKW>
<curveGeometryExpression>
<surfaceGeometryExpression>
constructKW
::=
Construct | Co | Make
<curveSurfacePointKW>
::=
CurveSurfacePoint
<curveGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW>
( <curveExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry |
Geo
<curveExpression>
::=
<curveInDatebaseExpression> |
<curveConstructionExpression>
<curveInDatabaseExpression>
::=
<curveByDatabaseLabelExpression> |
<surfaceEdgeExpression> |
<solidEdgeExpression>
<curveByDatabaseLabelExpression>
::=
<curveKW> <curveLabel>
<curveKW>
::=
<curveLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
9
<surfaceEdgeExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<solidEdgeExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFac
eEdge>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<curveConstructionExpression>
::=
<2PointCurveExpression> |
<2SurfaceCurveExpression>
<surfaceGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW>
( <surfaceExpression> ) )
<surfaceExpresion>
::=
<surfaceInDatebaseExpression> |
<surfaceConstructionExpression>
<surfaceInDatabaseExpression>
::=
<surfaceByDatabaseLabelExpression>
| <solidEdgeExpression>
<surfaceByDatabaseLabelExpression> ::=
<surfaceKW> <surfaceLabel>
<surfaceConstructionExpression>
<2CurveSurfaceExpression>
Note:
Table D-6
::=
Meaning
Co CurveSurfacePoint (Eval GeometryDef A point at the intersection of the 3rd edge of the 2nd
(Solid 1.2.3)) (Evaluate GeometryDefinition face of solid 1 with surface 4 will be used for an
(Surface 4))
application requesting [X Y Z] information for a
point.
Referring to points defined by the closest approach of a point to a curve
Patran allows applications to work with points defined by the closest approach of a point to a curve, as
well as using a single point selection. The use of this type of expression can cut down on unnecessary
construction geometry, which will be quite beneficial to clarity in the model definition phase. A user
must tell the selection mechanism that she wishes to select a point via the point closest approach to a
curve mechanism, select a curve and a point (by any of the available selection mechanisms) and allow
the system to evaluate the resulting expression. This expression, while somewhat verbose, is quite
962
general in its ability to conform to user expectations for robustness. The syntax for this type of expression
is diagrammatically described as:
<PointCurvePointExpression>
::=
<constructKW> <pointCurvePointKW>
<pointGeometryExpression>
<curveGeometryExpression>
constructKW
::=
Construct | Co | Make
<pointCurvePointKW>
::=
PointCurvePoint
<pointGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<pointExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry |
Geo
<pointExpression>
::=
<pointInDatebaseExpression> |
<pointConstructionExpression>
<pointInDatabaseExpression>
::=
<pointByDatabaseLabelExpression> |
<curveVertexExpression> |
<surfaceVertexExpression> |
<solidVertexExpression>
<pointByDatabaseLabelExpressio
n>
::=
<pointKW> <pointLabel>
<pointKW>
::=
<pointLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<curveVertexExpression>
::=
<curveKW> <curveLabel>.<curveVertex>
<curveKW>
::=
<curveLabel>
::=
<int>
<curveVertex>
::=
<int>
<surfaceVertexExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>.<surfaceE
dgeVertex>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<surfaceEdgeVertex>
::=
<int>
<solidVertexExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFaceEdg
e>.<solidFaceEdgeVertex>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<solidFaceEdgeVertex>
::=
<int>
<pointConstructionExpression>
::=
<2CurvePointExpression> |
<pointCurvePointExpression> |
<pointSurfacePointExpression> |
<curveSurfacePointExpression>
<curveGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<curveExpression> ) )
<curveExpresion>
::=
<curveInDatebaseExpression> |
<curveConstructionExpression>
<curveInDatabaseExpression>
::=
<curveByDatabaseLabelExpression> |
<surfaceEdgeExpression> |
<solidFaceEdgeExpression>
<curveByDatabaseLabelExpressio
n>
::=
<curveKW> <curveLabel>
<surfaceEdgeExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>
<solidFaceEdgeExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFaceEdg
e>
<curveConstructionExpression>
::=
<2PointCurveExpression> |
<2SurfaceCurveExpression>
Note:
Table D-7
Meaning
Construct PointCurvePoint (Evaluate Geo A point at the closest approach of point 1 to curve 2
(Point 1)) (Evaluate Geo (Curve 2))
will be used for an application requesting [X Y Z]
information for a point.
964
Table D-7
Meaning
general in its ability to conform to user expectations for robustness. The syntax for this type of expression
is diagrammatically described as:
<pointSurfacePointExpression>
::=
<constructKW> <pointSurfacePointKW>
<pointGeometryExpression>
<surfaceGeometryExpression>
constructKW
::=
Construct | Co | Make
<pointSurfacePointKW>
::=
PointSurfacePoint
<pointGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<pointExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry |
Geo
<pointExpression>
::=
<pointInDatebaseExpression> |
<pointConstructionExpression>
<pointInDatabaseExpression>
::=
<pointByDatabaseLabelExpression> |
<curveVertexExpression> |
<surfaceVertexExpression> |
<solidVertexExpression>
<pointByDatabaseLabelExpression>
::=
<pointKW> <pointLabel>
<pointKW>
::=
<pointLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<curveVertexExpression>
::=
<curveKW>
<curveLabel>.<curveVertex>
<curveKW>
::=
<curveLabel>
::=
<int>
<curveVertex>
::=
<int>
<surfaceVertexExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>.<surfa
ceEdgeVertex>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<surfaceEdgeVertex>
::=
<int>
<solidVertexExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFace
Edge>.<solidFaceEdgeVertex>
<solidKW>
::=
966
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<solidFaceEdgeVertex>
::=
<int>
<pointConstructionExpression>
::=
<2CurvePointExpression> |
<pointCurvePointExpression> |
<pointSurfacePointExpression> |
<curveSurfacePointExpression>
<surfaceGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<surfaceExpression> ) )
<surfaceExpresion>
::=
<surfaceInDatebaseExpression> |
<surfaceConstructionExpression>
<surfaceInDatabaseExpression>
::=
<surfaceByDatabaseLabelExpression>
| <solidFaceExpression>
<surfaceByDatabaseLabelExpressio
n>
::=
<surfaceKW> <surfaceLabel>
<solidFaceExpression>
::=
<solidKW> <solidLabel>.<solidFace>
<surfaceConstructionExpression>
::=
<2CurveSurfaceExpression>
Note:
Table D-8
Meaning
Curves
Referring to curves which already exist in the database
The simplest form of curve selection yields pick lists which refer to curves that already exist in the Patran
database. The syntax for this form can be described symbolically as follows:
<curveInDatabaseList>
::=
<curveKW>
::=
<curveLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-9
Meaning
C1
Curve 1.
Curve 1 2 3
Curves 1, 2, and 3.
Curve 1:2 Li 3
Curves 1, 2, and 3.
L1T9B2
Curves 1, 3, 5, 7, and 9.
Line 1,3/5,7,9
Curves 1, 3, 5, 7, and 9.
Curves 1, 3, 5, 7, and 9.
968
Referring to curves which exist as the edges of other entities which exist in the
database
Patran allows applications to use curves in a topological context for any operation where curves are valid.
That is, if it is more convenient to refer to curves in their edge context to faces, Patran will allow it. The
syntax for using this form can be described symbolically as:
<curveTopologicallyInDatabaseList>
::=
{ <surfaceEdgeList> } 0:n {
<solidEdgeList> } 0:n
<surfaceEdgeList>
::=
<surfaceKW>
<singleToplogicalIndentLabelList>
{
<singleToplogicalIndentLabelList>
} 0:n
<solidEdgeList>
::=
<solidKW>
<doubleTopologicalIndentLabelList>
{
<doubleTopologicalIndentLabelList>
} 0:n
<surfaceKW>
::=
<singleTopologicalIndentLabelList>
::=
<solidKW>
::=
<doubleTopologicalIndentLabelList>
::=
<int>.<int>.<int> | <int>
<throughKW> <int>.<int> .<int> |
<int> <throughKW> <int> <byKW>
<int>.<int>.<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-10
Meaning
Surface 1.1
Edge 1 of surface 1.
Hpat 1:10:3.1.2
970
to user expectations for robustness. The syntax for this type of expression is diagrammatically described
as:
<2PointCurveExpression>
::=
<constructKW> <2PointCurveKW>
<pointGeometryExpression>
<pointGeometryExpression>
constructKW
::=
Construct | Co | Make
<2PointCurveKW>
::=
2PointCurve
<pointGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<pointExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry |
Geo
<pointExpression>
::=
<pointInDatebaseExpression> |
<pointConstructionExpression>
<pointInDatabaseExpression>
::=
<pointByDatabaseLabelExpression> |
<curveVertexExpression> |
<surfaceVertexExpression> |
<solidVertexExpression>
<pointByDatabaseLabelExpression>
::=
<pointKW> <pointLabel>
<pointKW>
::=
<pointLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<curveVertexExpression>
::=
<curveKW> <curveLabel>.<curveVertex>
<curveKW>
::=
<curveLabel>
::=
<int>
<curveVertex>
::=
<int>
<surfaceVertexExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>.<surfac
eEdgeVertex>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<surfaceEdgeVertex>
::=
<int>
<solidVertexExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFaceE
dge>.<solidFaceEdgeVertex>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<solidFaceEdgeVertex>
::=
<int>
<pointConstructionExpression>
::=
<2CurvePointExpression> |
<pointCurvePointExpression> |
<pointSurfacePointExpression> |
<curveSurfacePointExpression>
Note:
Table D-11
Meaning
972
verbose, is quite general in its ability to conform to user expectations for robustness. The syntax for this
type of expression is diagrammatically described as:
<2SurfaceCurveExpression>
::=
<constructKW> <2SurfaceCurveKW>
<surfaceGeometryExpression>
<surfaceGeometryExpression>
constructKW
::=
Construct | Co | Make
<2SurfaceCurveKW>
::=
2SurfaceCurve
<surfaceGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW>
( <surfaceExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry
| Geo
<surfaceExpression>
::=
<surfaceInDatebaseExpression> |
<surfaceConstructionExpression>
<surfaceInDatabaseExpression>
::=
<surfaceByDatabaseLabelExpression>
| <solidFaceExpression>
<surfaceByDatabaseLabelExpression>
::=
<surfaceKW> <surfaceLabel>
<surfaceKW>
::=
<surfaceLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
9
<solidFaceExpression>
::=
<solidKW> <solidLabel>.<solidFace>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<surfaceConstructionExpression>
::=
<2CurveSurfaceExpression>
Note:
The syntax for <2CurveSurfaceExpression> may be found under the appropriate heading
in this section.
Table D-12
Meaning
Construct 2SurfaceCurve (Evaluate Geo A curve defined by the intersection between surface 1
(Surface 1)) (Evaluate Geo (Surface 2)) and surface 2 will be used for an application requesting
the geometry of a curve.
Make 2SurfaceCurve (Ev Geo (S1.2))
(Ev Geo (P2))
<pointCurveUOnCurveExpression>
::=
<curveKW>
::=
<curveLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<uKW>
::=
<uValue>
::=
<float>
<float>
::=
Table D-13
Meaning
Curve 1 (u 0)
Curve 1 at u = 0.0.
L1 (u .5)
Curve 1 at u = 0.5.
Crv 1 (U 1.000)
Curve 1 at u = 1.0.
974
Surfaces
Referring to surfaces which already exist in the database
The simplest form of surface selection yields pick lists which refer to surfaces that already exist in the
Patran database. The syntax for this form can be described symbolically as follows:
<surfaceInDatabaseList>
::=
<surfaceKW> <surfaceLabelList> {
<surfaceLabelList> | <surfaceInDatabaseList>
} 0:n
<surfaceKW>
::=
<surfaceLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-14
Meaning
S1
Surface 1.
Surface 1 2 3
Surfaces 1, 2, and 3.
Surface 1:2 Pa 3
Surfaces 1, 2, and 3.
P1T9B2
Surfaces 1, 3, 5, 7, and 9.
Patch 1,3/5,7,9
Surfaces 1, 3, 5, 7, and 9.
Surfaces 1, 3, 5, 7, and 9.
Referring to surfaces which exist as the faces of other entities which exist in the
database
Patran allows applications to use surfaces in a topological context for any operation where surfaces are
valid. That is, if it is more convenient to refer to surfaces in their face context to solids, Patran will allow
it. The syntax for using this form can be described symbolically as:
0:n
<surfaceTopologicallyInDatabaseList>
::=
{ <solidFaceList> }
<solidFaceList>
::=
<solidKW>
<singleToplogicalIndentLabelList> {
<singleToplogicalIndentLabelList> }
0:n
<solidKW>
::=
<singleTopologicalIndentLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8
| 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-15
Meaning
Solid 1.1
Face 1 of solid 1.
Hpat 1:10:3.1
976
its ability to conform to user expectations for robustness. The syntax for this type of expression is
diagrammatically described as:
<2CurveSurfaceExpression>
::=
<constructKW> <2CurveSurfaceKW>
<curveGeometryExpression>
<curveGeometryExpression>
constructKW
::=
Construct | Co | Make
<2CurveSurfaceKW>
::=
2CurveSurface
<curveGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<curveExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry |
Geo
<curveExpression>
::=
<curveInDatebaseExpression> |
<curveConstructionExpression>
<curveInDatabaseExpression>
::=
<curveByDatabaseLabelExpression> |
<surfaceEdgeExpression> |
<solidEdgeExpression>
<curveByDatabaseLabelExpression>
::=
<curveKW> <curveLabel>
<curveKW>
::=
<curveLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<surfaceEdgeExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<solidEdgeExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFace
Edge>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<curveConstructionExpression>
::=
<2PointCurveExpression> |
<2SurfaceCurveExpression>
Note:
Table D-16
Meaning
978
quite beneficial to clarity in the model definition phase. The syntax for this type of expression is
diagrammatically described as:
<pointSurfaceUVOnSurfaceExpression>
::=
<surfaceKW>
::=
<surfaceLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8
| 9
<uKW>
::=
<uValue>
::=
<float>
<float>
::=
<vKW>
::=
<vValue>
::=
<float>
Table D-17
Meaning
Surface 1 (u 0) (v 0)
P1 (u .5) (v .5)
Solids
Referring to solids which already exist in the database
The simplest form of solid selection yields pick lists which refer to solids that already exist in the Patran
database. The syntax for this form can be described symbolically as follows:
<solidInDatabaseList>
::=
<solidKW> <solidLabelList> {
<solidLabelList> | <solidInDatabaseList> }
0:n
<solidKW>
::=
<solidLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-18
Meaning
Solid 1
Solid 1.
Solid 1 2 3
Solids 1, 2, and 3.
Solid 1:2 Hp 3
Solids 1, 2, and 3.
H1T9B2
Solids 1, 3, 5, 7, and 9.
Hpat 1,3/5,7,9
Solids 1, 3, 5, 7, and 9.
Solids 1, 3, 5, 7, and 9.
980
to conform to user expectations for robustness. The syntax for this type of expression is diagrammatically
described as:
<2SurfaceSolidExpression>
::=
<constructKW> <2SurfaceSolidKW>
<surfaceGeometryExpression>
<surfaceGeometryExpression>
constructKW
::=
Construct | Co | Make
<2SurfaceSolidKW>
::=
2SurfaceSolid
<solidGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW>
( <solidExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry
| Geo
<surfaceExpression>
::=
<surfaceInDatebaseExpression> |
<surfaceConstructionExpression>
<surfaceInDatabaseExpression>
::=
<surfaceByDatabaseLabelExpression
> | <solidFaceExpression>
<surfaceByDatabaseLabelExpression>
::=
<surfaceKW> <surfaceLabel>
<surfaceKW>
::=
<surfaceLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8
| 9
<solidFaceExpression>
::=
<solidKW> <solidLabel>.<solidFace>
<solidKW>
::=
<solidLabel
::=
<int>
<solidFace>
::=
<int>
<surfaceConstructionExpression>
::=
<2CurveSurfaceExpression>
Note:
The syntax for <2CurveSurfaceExpression>, may be found under the appropriate heading
in this section.
Table D-19
Meaning
Finite Elements
Referring to nodes in the database
Node selection yields pick lists which refer to nodes that already exist in the Patran database. The syntax
for this form is described symbolically below:
<nodeList>
::=
<nodeKW>
::=
Node | Nde | N
<nodeLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-20
Meaning
N1
Node 1.
Node 1 2 3
Nodes 1, 2, and 3.
Nodes1, 2, and 3.
N1T9B2
Nodes 1, 3, 5, 7, and 9.
Node 1,3/5,7,9
Nodes 1, 3, 5, 7, and 9.
Nodes 1, 3, 5, 7, and 9.
982
<elementList>
::=
<elementKW> <elementLabelList> {
<elementLabelList> | <elementList> } 0:n
<elementKW>
::=
<elementLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-21
Meaning
E1
Element 1.
Element 1 2 3
Elements 1, 2, and 3.
Element 1:2 El 3
Elements, 2, and 3.
E1T9B2
Elements 1, 3, 5, 7, and 9.
Element 1,3/5,7,9
Elements 1, 3, 5, 7, and 9.
Elements 1, 3, 5, 7, and 9.
<elementByAttributeList>
::=
<elementAttributeKW> <elementLabelList> {
<elementLabelList> | <elementList> } 0:n
<elementAttributeKW>
::=
<basicElementAttributeKW>
{<elementNodeCount>} 0:1
<basicElementAttributeKW>
::=
elementNodeCount
::=
<int>
<elementLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-22
keyWord
Order
Edges
GE
GEL
linear
GEQ
quadratic
GEC
cubic
GE0D
GE1D
GE1DL
linear
GE1DQ
quadratic
GE1DC
cubic
GE2D
GE2DL
linear
GE2DQ
quadratic
GE2DC
cubic
GE3D
GE3DL
linear
GE3DQ
quadratic
984
Table D-22
keyWord
Dimension
Order
Edges
GE3DC
cubic
Bar
Tria
Quad
Tet
Wedge
Hex
12
Table D-23
Meaning
Quad 1t#
Quad4 1t#
Hex27 101:199:2
GE3D 1:#.2.1
<mpcList>
::=
<mpcKW>
::=
MPC
<mpcLabelList>
::=
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<throughKW>
::=
: | T | Through
<byKW>
::=
: | B | By
Table D-24
Meaning
MPC1
MPC 1.
MPC 1 2 3
MPCs 1, 2, and 3.
MPCs, 2, and 3.
MPC1T9B2
MPCs 1, 3, 5, 7, and 9.
MPC 1,3/5,7,9
MPCs 1, 3, 5, 7, and 9.
MPCs 1, 3, 5, 7, and 9.
986
Miscellaneous
Referring to a coordinate frame
The selection mechanism generates a simple pick list for coordinate frames for the list processor to work
with. Its syntax is:
<coordinateFrame>
::=
<coordinateFrameKW> <coordinateFrameLabel>
<coordinateFrameKW>
::=
<coordinateFrameLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
Table D-25
Meaning
Coord 0
Coordinate frame 0.
CoordinateFrame 10
F3
Coordinate frame 3.
<coordinateFrameAxis>
::=
<coordinateFrameKW>
<coordinateFrameLabel> .
<coordainateFrameAxisNumber>
<coordinateFrameKW>
::=
<coordinateFrameLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<coordinateFrameAxisNumber>
::=
1 | 2 | 3
Table D-26
Meaning
Coord 0.2
Coord 1.3
Coord 10.1
988
complexity, such as the intersection of two lines being the base of an axis with the closest approach of a
point to a surface being the tip.
<2PointAxisExpression>
::=
<constructKW> <2PointAxisKW>
<pointGeometryExpression>
<pointGeometryExpression> | {
<pointInDatabaseExpression>
<pointInDatabaseExpression> }
constructKW
::=
Construct | Co | Make
<2PointAxisKW>
::=
2PointAxis
<pointGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<pointExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry | Geo
<pointExpression>
::=
<pointInDatebaseExpression> |
<pointConstructionExpression>
<pointInDatabaseExpression
>
::=
<pointByDatabaseLabelExpression> |
<curveVertexExpression> |
<surfaceVertexExpression> |
<solidVertexExpression>
<pointByDatabaseLabelExpre
ssion>
::=
<pointKW> <pointLabel>
<pointKW>
::=
<pointLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<curveVertexExpression>
::=
<curveKW> <curveLabel>.<curveVertex>
<curveKW>
::=
<curveLabel>
::=
<int>
<curveVertex>
::=
<int>
<surfaceVertexExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>.<surfaceEdge
Vertex>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<surfaceEdgeVertex>
::=
<int>
<solidVertexExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFaceEdge>.
<solidFaceEdgeVertex>
<solidKW>
::=
<solidLabel>
::=
<int>
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<solidFaceEdgeVertex>
::=
<int>
<pointConstructionExpressi
on>
::=
<2CurvePointExpression> |
<pointCurvePointExpression> |
<pointSurfacePointExpression> |
<curveSurfacePointExpression>
Note:
Table D-27
Meaning
{Point 1 Point 2}
{Point 1 2}
{S1.1.1 G2}
990
the origin of the coordinate frame as the base of the vector, and defines the tip using the direction cosines
of the transformation matrix.
<coordinateFrameVector>
::=
<coordinateFrameKW>
<coordinateFrameLabel> .
<coordainateFrameAxisNumber>
<coordinateFrameKW>
::=
<coordinateFrameLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<coordinateFrameAxisNumber>
::=
1 | 2 | 3
Table D-28
Meaning
Coord 0.2
Coord 1.3
Coord 10.1
mechanism and list processor, points may be defined with arbitrary complexity, such as the intersection
of two lines being the base of an axis with the closest approach of a point to a surface being the tip.
<2PointVectorExpression>
::=
<constructKW> <2PointVectorKW>
<pointGeometryExpression>
<pointGeometryExpression>
constructKW
::=
Construct | Co | Make
<2PointVectorKW>
::=
2PointVector
<pointGeometryExpression>
::=
( <evalKW> <geometryDefinitionKW> (
<pointExpression> ) )
<evalKW>
::=
Evaluate | Eval | Ev
<geometryDefinitionKW>
::=
GeometryDefinition | GeometryDef |
GeoDefinition | GeoDef | Geometry | Geo
<pointExpression>
::=
<pointInDatebaseExpression> |
<pointConstructionExpression>
<pointInDatabaseExpression>
::=
<pointByDatabaseLabelExpression> |
<curveVertexExpression> |
<surfaceVertexExpression> |
<solidVertexExpression>
<pointByDatabaseLabelExpres
sion>
::=
<pointKW> <pointLabel>
<pointKW>
::=
<pointLabel>
::=
<int>
::=
<int>
{ + | - } 0:1 { <digit> } 1:n
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<curveVertexExpression>
::=
<curveKW> <curveLabel>.<curveVertex>
<curveKW>
::=
<curveLabel>
::=
<int>
<curveVertex>
::=
<int>
<surfaceVertexExpression>
::=
<surfaceKW>
<surfaceLabel>.<surfaceEdge>.<surfaceEdge
Vertex>
<surfaceKW>
::=
<surfaceLabel
::=
<int>
<surfaceEdge>
::=
<int>
<surfaceEdgeVertex>
::=
<int>
<solidVertexExpression>
::=
<solidKW>
<solidLabel>.<solidFace>.<solidFaceEdge>.
<solidFaceEdgeVertex>
<solidKW>
::=
<solidLabel>
::=
<int>
992
<solidFace>
::=
<int>
<solidFaceEdge>
::=
<int>
<solidFaceEdgeVertex>
::=
<int>
<pointConstructionExpression>
::=
<2CurvePointExpression> |
<pointCurvePointExpression> |
<pointSurfacePointExpression> |
<curveSurfacePointExpression>
Note:
Table D-29
Meaning
<vectorByDisplacementExpression>
::=
<xDisplacement>
::=
<float>
<yDisplacement>
::=
<float>
<zDisplacement>
::=
<float>
<float>
::=
<pointLabel>
::=
<int>
<nodeLabel>
::=
<int>
<int>
::=
<digit>
::=
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
Table D-30
Meaning
<1 2 3>
<1 0 0>
994
Index
Patran Reference Manual
IND
EX
Index
database
freeing unused space, 63
databases
closing, 63
creating, 60
opening, 61
rebuilding
, 63
reverting, 63
saving, 63
Deformable Bodies, 659
design studies, 661, 662, 671
displacement results files, 929
display
color configurations, 384
menu, 12
properties, 383
Ease-of-use enhancements
Hierarchical groups, 300
element force, 673, 677
Element Quick Create, 579
element results files, 933
Enterprise MVision, 490
EPS files, 232
experimental data fitting, 644
Explore, 694
exporting models, 64
IGES files, 207
Patran 2.5 Neutral files, 204
STEP files, 213
express neutral files, 101
file types
hardcopy file, 46
IGES file, 46
journal file, 46
PATRAN 2.5 results files, 46
PATRAN 2.5 results template files, 935
PATRAN database, 46
files
p3epilog.pcl, 54
p3prolog.pcl, 54
session, 54
settings.pcl, 47, 54
template database, 56
focal point, 353
force results files, 929
functional assignments, 6
geometry
direct geometry integration, 2
grid point force balance, 677
group
attributes, 261
current, 261
membership, 261
menu, 12
modify, 276
names, 260
posted, 261
status, 261
target, 261
transformations, 262
Groups, hierarchical, 300
hardcopy
CGM, 941
device-dependent, 941
HP-GL, 941
HP-GL/2, 941
postscript, 941
printers/plotters, 942
setup, 944
supported hardware, 945
Hierarchical groups, 300
INDEX 997
p3epilog.pcl file, 54
p3epolog.pcl file, 47
p3prolog.pcl file, 47, 54
page setup, 229
Parasolid (xmt) files, 170, 173
PATRAN 2.5 neutral file, 93
Patran 2.5 neutral files, 204
PATRAN 2.5 results files, 929
Patran 2.5 Results Files, 46
PATRAN command language, 4
PCL
PATRAN command language, 4
playing session file initialization, 55
postprocessing
max/min sort, 684
postscript, 229, 941
postscript files, 225, 226
preferences
analysis, 4, 436, 437, 441
finite element, 473
geometry, 470
global, 457
graphics, 460
menu, 12
mouse, 463
picking, 466
report, 469
print
CGM, 234
HP-GL, 237
HP-GL/2, 240
postscript, 229
printer configuration file, 242
printing
page setup, 229
UNIX, 228
Windows NT, 224
printing images, 65
Pro/ENGINEER files, 140
properties, 383
Properties Import, 547
Property Data Plots, 581
quitting, 66
undo, 222
Unigraphics files, 151
Unigraphics-NX, 162
User Defined AOM, 726
view
automatic centering, 351
clipping, 355
clipping perspective, 355
clipping plane, 353
clipping/capping, 352
coordinate system, 351
focal point, 353
menu, 12
model space, 350
named views, 355
observer position, 353
screen space, 350
select corners, 355
viewing plane, 353
viewport menu, 12
window center, 353
zoom, 355
viewing plane, 353
viewport, 4, 11, 12, 316
menu, 12
zoom, 355