Part1 Basic Functions

Return C O N T E N T S
MSC.Patran Reference Manual

MSC.Patran Reference Manual,
Part 1: Basic Functions Part 1: Basic Functions
CHAPTER
1
Introduction to ■ Introducing MSC.Patran, 2
MSC.Patran ■ MSC.Patran Framework, 3
■ Using MSC.Patran for Engineering Analysis, 5
■ HTML Based Online Help, 6
❑ Help>..., 6
- Context-Sensitive Help, 6
2
MSC.Patran ■ Modeling Window, 8
Workspace ■ The Menu Bar, 10
❑ Menu Bar Keywords, 10
■ The Tool Bar, 11

❑ System Tool Palette, 11
❑ Mouse Function Tool Palette, 13
❑ Viewing Tool Palette, 14
❑ Display Tool Palette, 15
❑ Model Orientation Tool Palette, 16
❑ Labeling and Sizing Tool Palettes, 17
■ The Applications Bar, 18

❑ Application Buttons, 18
■ History Window and Command Line, 19
3
Entering and ■ Forms, Widgets, and Buttons, 22
Retrieving Data ❑ Commonly Used Widgets, 23
❑ Spreadsheets, 27
- Tabular Data Input Spreadsheets, 27
- Multiple Data Input Spreadsheets, 28
■ Selecting Entities, 29
❑ Screen Picking, 29
❑ Select Menu, 31
- Common Select Icons, 31
- Entity Filter Icons, 33
- Axis and Vector Select Icons, 33
❑ Geometry Select Icons, 35
❑ FEM Select Icons, 37
■ The List Processor, 38
4
Working with Files ■ File Types and Formats, 40
❑ Startup Files, 41
- The settings.pcl file, 41
- The p3prolog.pcl and p3epilog.pcl Files, 46
- Startup Session Files, 47
- The Template Database File (template.db), 47
■ The File Menu, 49
■ File Commands, 53
❑ File>New, 54
- Changing a Template, 55
- Modifying Preferences, 55
❑ File>Open, 58
❑ File>Save a Copy, 59
❑ File>Reclaim, 60
❑ File>Revert, 61
❑ File>Rebuild, 62
❑ File>Import, 63
- Importing an MSC.Patran Database, 64
- Importing PATRAN 2.5 Neutral Files, 76
- Importing MSC.Nastran Input Files, 79
- Importing Express Neutral Files, 82
- Importing IGES Files, 88
- Importing CATIA Files, 96
- Importing Euclid 3 Files, 109
- Importing I-DEAS Files, 111
- Importing Pro/ENGINEER Files, 115
- Importing CADDS 5 Files, 122
- Importing Unigraphics Files, 125
- Unigraphics Import Options for Express Translation, 129
- Importing Parasolid (xmt) Files, 131
- Importing ACIS (sat) Files, 134
- Importing STEP Files, 138
- Importing STL Files, 153
- Importing VDA Files, 156
- Importing Results, 160
- Exporting to a PATRAN 2.5 Neutral File, 162
❑ File>Export, 162
- Exporting a Parasolid Transmit File, 165
- Exporting to IGES Files, 167
- Exporting to STEP Files, 172
❑ File>Session, 176
- Printing on Windows NT, 178
❑ File>Print, 178
- Printing on UNIX, 181
- BMP Images Output, 197
❑ File>Images, 197
- JPEG Images Output, 198
- MPEG Images Output, 199
- PNG Images Output, 200
- TIFF Images Output, 201
- VRML Images Output, 202
❑ File>Report, 203
- Report Format Preferences, 205
- Report File Output, 205
5
All About Groups ■ Group Concepts and Definitions, 208
❑ Group Names, 208
❑ Group Membership, 208
❑ Group Status, 209
❑ Group Attributes, 209
❑ Creating and Managing Groups, 209
❑ Group Transformations, 210
■ The Group Menu, 217

❑ Menu Conventions, 217
❑ Group>Create, 218
❑ Group>Post, 220
❑ Group>Modify, 221
❑ Group>Move/Copy, 225
❑ Group>Set Current, 227
❑ Group>Transform, 228
❑ Group>Delete, 237
❑ Group>Attributes, 238
6
Viewports ■ Viewport Concepts and Definitions, 240
❑ Viewport Names, 240
❑ Viewport Status, 241
❑ Viewport Display Attributes, 241
❑ Viewports and Groups, 241
❑ Named Views in Viewports, 242
❑ Common Viewport Features, 242
❑ Tiling Viewports, 242
■ The Viewport Menu, 243

■ Viewport Commands, 244
❑ Viewport>Create, 244
❑ Viewport>Post, 245
❑ Viewport>Modify, 246
❑ Viewport>Delete, 255
❑ Viewport>Tile, 256
7
Viewing a Model ■ View Concepts and Definitions, 258
❑ Current View, 258
❑ Named Views, 258
❑ Model Space, 258
❑ Screen Space, 258
❑ Viewing Coordinate System Parameters, 258
❑ Fitting a View, 259
❑ View Transformations, 259
- View Clipping, 260
❑ Perspective Views, 260
❑ View Parameters, 260
■ The Viewing Menu, 262
■ Viewing Commands, 264
❑ Viewing>Transformations, 264
❑ Fit View, 265
❑ Select Center, 266
❑ Select Corners, 266
❑ Viewing>Zoom (% of View), 266
❑ Viewing>Angles, 267
❑ Viewing>View From/To, 269
❑ Viewing>Named Views, 270
❑ Viewing>Scale Factors, 270
❑ Viewing>Clipping/Perspective, 272
❑ Viewing>Clipping/Perspective, 273
❑ Perspective Views, 273
❑ Managing the Parameters of Perspective Viewing, 275
❑ Viewing>Arbitrary Clipping, 275
8
Display Control ■ Display Concepts and Definitions, 280
❑ Global and Local Display Features, 280
❑ Display Modes, 280
❑ Rendering Styles, 280
❑ Finite Element Display, 283
❑ Erasing and Plotting Entities, 284
❑ Shrinking Entities, 284
❑ Titles, 284
❑ Coordinate Frames, 285
❑ Named Attributes, 285
❑ Spectrums, 285
❑ Ranges, 285
❑ Color Palette, 285
❑ Light Sources, 286
■ The Display Menu, 287

■ Display Commands, 289
❑ Display>Entity Color/Label/Render, 289
❑ Display>Plot/Erase, 290
❑ Display>Highlight, 292
❑ Display>Geometry, 292
❑ Display>Finite Elements, 294
❑ Display>LBC/Element Property Attributes, 297
❑ Display>Named Attributes, 302
❑ Display> Coordinate Frames, 303
❑ Display>Titles, 304
❑ Display>Spectrums, 306
❑ Display>Ranges, 307
❑ Display>Color Palette, 313
❑ Display>Shading, 315
❑ Display>Light Source, 316
9
Preferences ■ Preferences Concepts and Definitions, 320
❑ Analysis Codes, 320
- Analysis Types, 320
- Changing Analysis Codes, 320
❑ Model Tolerance, 321
❑ Warning Messages, 321
❑ Hardware Rendering, 321
❑ Representing Geometry, 321
❑ Model Units, 322
■ The Preferences Menu, 323

■ Preferences Commands, 325
❑ Preferences>Analysis, 325
- Changing the Analysis Preference, 326
❑ Mapping Functions, 327
- Material Property Mapping Tables, 328
- Element Property Mapping Tables, 330
❑ Preferences>Global, 338
❑ Preferences>Graphics, 339
❑ Preferences>Mouse, 340
❑ Preferences>Picking, 342
❑ Preferences>Report, 345
❑ Preferences>Geometry, 346
❑ Preferences>Finite Element, 348
❑ Preferences>Main Form, 351
10
Tools ■ Tools Concepts and Definitions, 354
❑ Lists, 354
- Entity Types, 354
- Classification Methods, 354
- Group Assignment, 355
- Boolean Operations, 355
- Using Lists, 355
❑ Mass Properties, 356
- Output Options, 356
- Report Files, 357
- Units, 357
- Mass Properties of Finite Element Models, 357
- Mass Properties and Elements, 357
- Weight Factors, 358
- Mass Properties and Fields, 358
- Mass Properties and Materials, 358
- Analysis Model Types and Mass Properties, 358
❑ Beam Library, 360
- Standard Shapes, 360
- Arbitrary Shapes, 360
❑ Design Studies and Design Optimization, 362
- Design Studies, 362
- Variables, 362
❑ Results Templates, 362
❑ Rebar Definitions, 363
❑ MSC.Fatigue, 363
❑ MSC.Laminate Modeler, 363
❑ MSC.Patran Analysis Manager, 363
■ The Tools Menu, 364
■ Tools Commands, 366
❑ Tools>List>Create, 366
- Creating Lists, 366
❑ Tools>List>Boolean, 371
❑ Tools>Mass Properties, 372
- Defining the Region for Mass Properties Calculation, 374
- Displaying Mass Property Results, 375
- Reporting Mass Properties Results, 379
❑ Tools>Beam Library, 382
- Using Calculated Beam Properties, 382
- Creating Standard Beam Cross Sections, 383
- Creating Arbitrary Beam Cross Sections Using Boundary Loops, 386
- Creating Arbitrary Beam Cross Sections Using Centerlines, 390
- Reporting Beam Section Data, 395
- Modifying Beam Cross Sections, 396
- Deleting Beam Cross Sections, 397
❑ Tools>Model Variables, 397
- Creating Model Variables, 397
- Displaying Model Variables, 403
- Modifying Model Variables, 404
- Deleting Model Variables, 405
❑ Tools>Design Studies, 405
- Creating Design Studies, 406
❑ Tools>Results Templates, 435
- Applying Results Templates, 435
- Creating and Managing Results Templates, 436
- Exporting and Importing Results Templates, 440
- Loading Results Templates in a MSC.Patran Database, 441
❑ Tools>Rebar Definitions, 443
- Creating Rebar Definitions, 444
❑ Tools>MSC.Fatigue, 445
❑ Tools>Laminate Modeler, 446
❑ Tools>Analysis Manager, 446
❑ Tools>Rotor Dynamics, 446
❑ Tools>Experimental Data Fitting, 446
❑ Tools>PreRelease, 449
- Midplane Meshing, 449
- Parametric Modeling, 449
- Connector, 450
- Feature Recognition, 450
A
File Formats ■ The Neutral System Concept, 454
■ The Neutral File, 455
❑ Neutral File Applications, 455
❑ Neutral File Format, 457
- Neutral File Types, 457
- Neutral File Packet Types Supported in MSC.Patran , 457
- PATRAN 2.5 Neutral File Contents and Format, 460
■ Session File/Journal File, 479
■ IGES File, 481
■ PATRAN 2.5 Results Files, 483
❑ Displacement or Force Results Files, 483
- Sample Displacement/Force Results Data File, 484
❑ Nodal Results Files, 485
❑ Element Results Files, 486
❑ Beam Results Files, 488
- Sample Beam Results File, 488
B
Printing Options ■ Introduction, 490
■ Device-dependent Hardcopy File, 491
■ Additional Information for Printers/Plotters, 492
■ If Your Plot Does Not Turn Out as Expected, 493
■ Hardware Setup, 494
■ Supported Hardware for MSC.Patran Hardcopy, 495
C
Mass Properties ■ Summary of Mass Properties, 498
❑ Overview, 498
INDEX ■ MSC.Patran Reference Manual, 501

Part 1: Basic Functions
MSC.Patran User’s Guide, Part 1: Basic Functions
CHAPTER
Introduction to MSC.Patran
Return
1
■ HTML Based Online Help
■ MSC.Patran Framework
■ Using MSC.Patran for Engineering Analysis

PART 2
Basic Functions
1.1 Introducing MSC.Patran

MSC.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 meshing techniques for one-, two-, and three-dimensional (solid)
geometries.
• Loads, boundary conditions (LBCs), and material properties associated directly with
geometry models as well as FEM models.
Direct Geometry Access. CAD geometry access without transformation, associativity with
corresponding MSC.Patran FEM entities, inclusion of standard data exchange formats (e.g.,
IGES).
Analysis Modules. Integrated analysis capabilities for structural, thermal, fatigue, and other
types of mechanical analysis.
Analysis Preferences. Linkage to commercial analysis solvers and proprietary in-house

codes, all functions, definitions, properties, and code forms adapted to solvers.
Result Visualization and Reporting. Deformed shape, fringe plot, and X-Y plot displays,
ability to filter output data by selected properties (e.g., material), facility of combining, scaling,
or sorting result information by time step, frequency, temperature or spatial location,
sophisticated reporting capabilities in user-defined format and sorting sequence.
PATRAN Command Language (PCL). Scripting language for customization, task

automation, and variance and design sensitivity studies.
MSC.Mvision. Integrated materials database.
Online Help/Documentation. Topical and context-sensitive help for all interactive features,
functions, and applications, hypertext links throughout the online system for instant
information retrieval.
CHAPTER 1 3
1.2 MSC.Patran Framework

The open architecture of MSC.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 MSC.Patran Imports Data. MSC.Patran accepts data from CAD system user files, Patran
neutral files, and IGES files. Using one of MSC.Patran’s 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 MSC.Patran. All project-related information is stored in files of

various types and formats. The major file types that are created or accessed during MSC.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 MSC.Patran
model.
• Session file (.ses extension). Contains all database related commands and
corresponding comments executed during a work session.
• Journal file ( .jou extension). Contains all database related commands executed to
create a 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.
PART 2
Basic Functions
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 MSC.Patran Exports Models. MSC.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
commercial codes, such as ANSYS and ABAQUS, as well as in-house proprietary analysis
programs. While different analysis codes may define components of a finite element model
differently, MSC.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. MSC.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 MSC.Patran environment
with the following results:
• New analysis code names, as well as code-specific properties and functional
assignments, will appear on appropriate forms.
• Finite element models created in an MSC.Patran database can be extracted and
transferred to a proprietary program for analysis. Conversely, finite element models
and analysis results created with an in-house program can be loaded directly into the
MSC.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.
CHAPTER 1 5
1.3 Using MSC.Patran for Engineering Analysis

The major steps of modeling and analysis involve the following MSC.Patran application
processes:
Geometry. MSC.Patran provides a complete set of tools to build, modify, and parameterize
geometric entities of a model. In addition, MSC.Patran can operate directly on geometry you
created in various CAD systems or imported via IGES geometry files.
Finite Element Modeling. MSC.Patran’s mapped or automatic meshing algorithms generate

both uniform and non-uniform finite element meshes. Mesh control parameters are applied to
edges of surfaces, solids, or curves, as well as to interior points and curves.
Functional Assignments. Functional assignments is a collective term for applied loads,

boundary conditions, element properties, and material properties. These can be applied either
to the finite element model or directly to the geometric model. The advantage of being able to
associate functional assignments, for example loads, with a geometric model is that you can
experiment with any number of meshing configurations without the need to reapply loads each
time you change the mesh.
Analysis. MSC.Patran provides flexibility and tight integration with a number of finite element
analysis codes.
Postprocessing. Postprocessing capabilities include visualization of the deformed model,

various color plot displays, X-Y curve outputs, and results animation. Numerical results data
can be combined, scaled, and sorted by time step, frequency, temperature or spatial location. For
example, you can request the display of the resulting von Mises stresses between 15,000 psi and
30,000 psi at 154 Hz in the second mode of vibration. The Insight application condenses raw
numerical data into extensive sophisticated graphical tools and displays for complete accurate
interpretation of results.
PART 2
Basic Functions
1.4 HTML Based Online Help

MSC.Patran employs a HTML based system in which Help topics are displayed through your
web browser.
Help>...
Use the Help>... command to acquire the following help.
Contents and Index 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 Provides additional details on using MSC.Patran Help and
navigating the contents.
Technical Support Directs you in obtaining the technical support you might
need.
What’s New in Reports the key highlights and describes all the new features
MSC.Patran for MSC.Patran.
About MSC.Patran Contains the version and legal notices for the MSC.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 MSC.Patran, simply press the F1 key.
The appropriate Help topic will appear in a new Browser window on your screen.
MSC.Patran Reference Manual, Part 1: Basic Functions
CHAPTER
MSC.Patran Workspace
2
■ Modeling Window
■ The Menu Bar
■ The Tool Bar
■ The Applications Bar
■ History Window and Command Line

PART 2:
Basic Functions
2.1 Modeling Window

The MSC.PATRAN workspace, or modeling window, is the area of the screen where you
interactively perform all MSC.Patran operations. The modeling window consists of two major
sections, the MSC.Patran Main Form and the graphics viewport.
MSC.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
Command Line History List

CHAPTER 2 9
Graphics Viewport
The graphics viewport is a window where the geometric model, finite element model, and finite
element analysis results are displayed.
box_beam.db - default_viewport- default_group - Entity
Origin Marker
Y Global Coordinate Frame
Z X
PART 2:
Basic Functions
2.2 The Menu Bar

The items in the menu bar control the parameters of various system tasks. Each menu keyword
activates a drop-down menu that displays additional commands and actions. The menu bar
keywords are shown below:
File Group Viewport Viewing Display Preferences Tools Insight Help

Control
Menu Bar Keywords

The following is a brief explanation of the keywords that appear in the Menu Bar. The
functionalities covered in each drop-down menu are detailed in later chapters.
File. The File menu provides access to the many different files used in MSC.Patran. File
manipulation functionalities include database management, import and export processes,
session file handling, hardcopy creation, and session exiting.
Group. The Group menu enables you to create named groups of selected geometric or finite
element entities with common characteristics. Grouping makes it possible to visually
differentiate sets of entities from one another, as well as to perform various tasks on a number
of like entities at the same time. With the Group menu you can also modify, transform, or
dissolve groups.
Viewport. A viewport is a named graphics window through which you look at a model. You
may define any number of independent views of different extent and location and each may
contain the model, or a portion of the model, in a specific position and display size. The
Viewport menu serves to create, modify, and delete viewports.
Viewing. The Viewing menu manages the position, orientation, and sizing of the view of a
model in selected viewports.
Display. The Display menu commands control visualization features such as colors, labels, and
highlights of model entities in viewports.
Preferences. The Preferences menu sets the global parameters for a model’s definition and
appearance.
Tools. The Tools menu provides access to MSC.Patran’s special functions (e.g. Mass Properties)
as well as to optional analysis modules, including MSC.Fatigue, and MSC.Laminate Modeler,
provided that they are available on your system.
Insight Control. With the Insight menu you can activate sophisticated graphical tools to
interpret, visualize, and animate numerical results of the finite element analysis process.
Help. The Help menu retrieves online documentation for all MSC.Patran features and provides
various operational tips, such as keyboard shortcuts, mouse functions, as well as tutorial
assistance.
CHAPTER 2 1
2.3 The Tool Bar

The tool bar consists of a series of movable tool palettes. Each tool palette is a set of related icons
that represent often-used functions in a particular application area. Based on their roles, you can
identify the following tool palettes:
• System Tool Palette
• Mouse Function Tool Palette
• Viewing Tool Palette
• Display Tool Palette
• Model Orientation Tool Palette
• Labeling and Sizing Tool Palette
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 MSC.Patran.
System Tool Palette

The icons in the System Tool palette represent the functions that have system-wide application
regardless of where you are in a project.
File>New Brings up the New Database form where you can define a new model.
File>Open Brings up the Open Database form where you pick an existing database.
File>Save Saves the database with its current name and location.
Print Creates a hardcopy file to print or plot.
Copy to Copies the image in the current viewport onto the clipboard
Clipboard
Undo Reverses the last command that added, modified, or deleted entities.
Note: You cannot reverse an undone operation by depressing the Undo icon a
second time.
PART 2:
Basic Functions
Abort Stops the operation in progress. Depending on the operation, the following will
happen:
During a plot: The graphic imaging process will suspend immediately, leaving
a partially displayed image. To restart the plot operation, press the “Refresh
Graphics” icon.
During meshing: All completely meshed regions will remain intact. The last
geometric region whose meshing was interrupted will not be meshed.
During geometry construction: The operation will terminate after the current
entity is constructed.
During session file playback: When a playback is in progress, the interrupt
icon is available. If an interrupt is confirmed, session file playback will pause and
the session file play form will appear. A command interrupted message will be
written to the currently recording session file.
Reset Removes fringe plots, titles, highlighting, and deformed shape plots.
Graphics
Note: This button acts on all posted viewports if the Display mode is set to
Entity Type. However, if the display is in Group mode, only the groups
posted in the current window will be affected.
Refresh Redisplays the contents of the screen.

Graphics
Heart Beat Color-coded indicator that shows the current status of MSC.Patran.
• White--waiting for user input
• Blue--performing an operation that can be stopped with the Interrupt
button
• Red--performing an operation that cannot be interrupted.
CHAPTER 2 1
Mouse Function Tool Palette

With the icons in this palette you can set the middle mouse button to perform incremental
rotation, translation, and zoom actions of a view of the model.
Mouse Rotate XYZ--rotate around the X and Y axes.
Mouse Rotate Z--rotate around the Z axis.
Mouse Translate X--translate in the X and Y directions.
Mouse Zoom--zoom in and out of the screen.

PART 2:
Basic Functions
Viewing Tool Palette

The icons in this palette provide shortcuts to controlling the orientation, sizing, position, and
visualization methods of a model’s view in a viewport.
View Corners--zooms in on a cursor-defined rectangular area.
Fit View--resizes the view so that all model entities fit inside the viewport window.
View Center--moves the window’s center to a cursor picked location.
Rotation Center--selects a view’s rotation center (point, node or screen position).
Model Center-- sets the rotation center to the centroid of entities in the view.
Zoom Out--incrementally zooms out from the model by a factor of two.
Zoom In--incrementally zooms in on the model by a factor of two.

CHAPTER 2 1
Display Tool Palette

The icons in this palette provide easy access to visualization tools that enable you to improve the
appearance of models.
Wireframe--renders the model in wireframe style.
Hidden Line--renders the model in hidden line style.
Smooth Shaded--renders the model in smooth shaded style.
Show Labels--plots all entity labels.
Hide Labels--erases all entity labels.

PART 2:
Basic Functions
Model Orientation Tool Palette

Each icon in this palette enables you to quickly display a standard engineering view of the
model.
Front View--Rotations: X = 0, Y = 0, Z = 0
Rear View--Rotations: X = -180, Y = 0, Z = -180
Top View--Rotations: X = 90, Y = 0, Z = 0
Bottom View--Rotations: X = -90, Y = 0, Z = 0
Left Side View--Rotations: X = 0, Y = 90, Z = 0
Right Side View--Rotations: X = 0, Y = -90, Z = 0
Isometric View 1--Rotations: X = 23, Y = -34, Z = 0
Isometric View 2--Rotations: X = 23, Y = 56, Z = 0
Isometric View 3--Rotations: X = -67, Y = 0 Z =-34
Isometric View 4--Rotations: X = -157, Y = 34, Z = 180

CHAPTER 2 1
Labeling and Sizing Tool Palettes

These icons activate functions that help enhance the display of your model. Two of the icons
(Plot/Erase and Label Control) call up additional icons and application forms.
Plot/Erase--displays the Plot/Erase form and a sub-palette for picking entities
Label Control--displays the Label Control sub-palette for picking entities
Point Size--toggles the display size of geometric points to 1 or 9 (pixels)
Node Size--toggles the display size of nodes to 0 or 9 (pixels)
Display Lines--toggles the number of display lines to 2 or 0 (no lines)

PART 2:
Basic Functions
2.4 The Applications Bar

The movable Applications bar consists of application buttons that activate specific forms for data
input. For your convenience, the buttons are arranged left-to-right in the same order that you
would use them to build and analyze a model. However, once the database is created, you can
access these buttons in any order.
Application Buttons
Geometry Creates and manipulates geometric entities.

Elements Creates and manipulates nodes, elements, and meshes.
Loads/BCs Creates and manipulates loads and boundary conditions.
Materials Defines and modifies material properties, associates materials with a model.
Properties Specifies element properties for a finite element model.
Load Cases Creates and modifies load cases for a model.
Fields Defines and modifies variations in element and material properties and
LBCs.
Analysis Sets analysis parameters, submits the analysis, and reads the output files.
Results Processes result files and specifies result data display characteristics.
Insight Creates tools used for result display manipulation and refinement.
XY Plot Manages the appearance of XY windows and the XY plot displays of analysis
results.
CHAPTER 2 1
2.5 History Window and Command Line

The History Window displays the history list, a sequential recording of commands used while
building the model. It may also contain error messages and comments.
The Command Line allows you to enter command text manually. Additionally, the command
line displays system messages and accommodates history commands for editing.
Command Line Comments

Comments in the history list begin with the “$” sign. Types of comments that may appear are:
$? System generated responses and questions.

$# Informational messages that provide feedback about a previously executed command.
$ PCL comments.
PART 2:
Basic Functions
CHAPTER
Entering and Retrieving Data
3
■ Forms, Widgets, and Buttons
■ Selecting Entities
■ The List Processor

PART 2
Basic Functions
3.1 Forms, Widgets, and Buttons

In MSC.Patran, you enter geometric and finite element data in a number of designated standard
input forms. Similarly, analysis result output information is retrieved via selecting various
options in specific output forms. Whenever you select a menu keyword or application button,
the appropriate menu action form or application form will be activated. In some applications a
secondary subordinate form may be displayed for entering aditional input.
All forms contain certain simple elements, such as data boxes, buttons, switches, scroll bars, lists,
and other widgets, making it easy to input information by selecting items with the cursor and
minimizing the need for manual data entry.
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. MSC.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.
A typical application form is shown below:

CHAPTER 3 2
Commonly Used Widgets

The following is a summary of some of the most often used widgets and their functionalities:
• Apply Button • Auto Execute

• Cancel Button • Coordinate Frame Input Box
• Data Box • Default Values
• Filter • OK Button
• Output ID List • Reset Button
• Scroll Bar • Spreadsheet
• Switch Button • Toggle Button
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 (p. 11)) to reverse the
operation.
• this action activates a commit--saves the results of all actions performed (including the
current one) since the last time the database was saved.
Conversely, if a form contains an “Apply” button without the dashes, the action of that
application cannot be undone and it does not commit previous actions to the database. After
either Apply action, the form stays open for further inputs.
Auto Execute
Auto Execute
When the Auto Execute switch is ON, the Apply button is executed automatically when all
required parameters are entered on the input form.
Auto Execute is useful if immediate results are desirable. However, if you want to be more
cautious and double check all inputs before executing a command, turn this function OFF by
clicking in the box.
Cancel Button
Cancel
Closes a form and voids all inputs and changes you made just before canceling.
PART 2
Basic Functions
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 Frames (p. 59) in the
MSC.Patran Reference Manual, Part 2: Geometry Modeling).
Databox
Databox label Curve List
Blinking insertion bar
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...
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.
CHAPTER 3 2
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 don’t 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 Output IDs

21 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.
PART 2
Basic Functions
Scroll Bar
End arrows scroll in the selected direction

Center scroll bar for large moves
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.
CHAPTER 3 2
Spreadsheets
Tabular Data Input Spreadsheets
This type of spreadsheet is used to input data into a one-, two-, or three-dimensional table.
1D Scalar Table Data
Input Data
Data
X Value
1
2
3
4
5
6
7
8
9
OK
To enter or modify data:

1. Select an independent (X) or dependent variable (Value) cell in the Data field. The
selected cell will be highlighted.
2. Enter the desired value in the Input Data box.
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.
PART 2
Basic Functions
Multiple Data Input Spreadsheets

Some spreadsheets are more complex. The spreadsheet below is actually a combination of two
spreadsheets and allows multiple data item inputs.
Dependent Terms (1)
Nodes (1) DOFs (1)
74 UX
Independent Terms (No Max)
Coefficient Nodes (1) DOFs (1)
1. 6 UX
1. 44 UZ
◆
◆ Create Dependent ◆ Modify
◆
◆ Create Independent ◆
◆ Delete
Coefficient = 1
Auto Execute
Node List
Node 1
DOFs
UX
UY
UZ
Apply Reset Cancel
To create new entries:

1. Pick one of the Create toggles to specify which spreadsheet will receive the input.
2. Enter the desired values in the data boxes.
3. Press Apply.
To modify or delete entries:
1. Click in the cell whose content you want to modify or delete.
2. Select Modify or Delete.
3. The contents of the entire row in which the cell is located will be displayed in the list
box and data input box.
4. Select the item you want to modify (or delete).
5. Click Apply.
CHAPTER 3 2
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
Insertion bar
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 (p. 342)).
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
Rectangle Picking (default). The enclosure is rectangular in shape. Click and hold down the
left mouse button at a screen point corresponding to one corner of the rectangle (A), drag the
mouse to the opposite corner (B), then release the button.
A
B
PART 2
Basic Functions
Polygon Picking. The enclosure is in the shape of a polygon. Click the polygon icon in the
Select Menu (see Preferences>Picking (p. 342)) 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.
A B
E D
Note: After the selection is complete, the default for the enclosure shape will always return
to rectangle.
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
Selecting non-existent geometry. You can pick geometry that does not actually exist in the
database but is recognized nevertheless. An example would be a curve defined by the
intersection of two surfaces.
CHAPTER 3 3
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 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
Entity filter icons

Go-to icons
Visible entity ON/OFF toggle
Common Select Icons

Whenever a command invokes the Select menu, the following icons will always be displayed:
• Visible Entity Toggle • Select icons

• Polygon Pick icon • “Any” Icon
Visible Entity Picking
In certain applications you may want to restrict entity selection to only those parts of the model
that would be visible in a hidden or shaded mode. In that case, you can specify visible entity
picking with the icon at the beginning of the select menu. This icon toggles the visible entity
picking function ON or OFF.
It is not required that the model be rendered in hidden or shaded style, and all the other entity
picking processes remain unchanged when the visible entity toggle is turned ON.
The following entities are supported in the visible entity selection mode:
Geometry FEM
• Curves • Nodes
• Points and vertices of geometry • Elements
• Solids • Edges of shell and solid elements
• Surfaces • Faces of solid elements
• Faces of solids
• Edges of surfaces and solids
PART 2
Basic Functions
Polygon Pick Icon

To select a number of entities at the same time, you must surround them either with a rectangle
or an arbitrary polygon. The default is a rectangle; you must pick the polygon icon to opt for a
polygon enclosure.
Picking Icons. When you pick an entity, its name is entered in the select databox. By default, if
you follow with another entity pick, the previous selection will be canceled and the second
selection will replace the first. This is called Replace Pick. However, with the Add Pick icon
option, further selections do not replace existing ones but are added to the selection list. Lastly,
the Reject Pick option allows you to remove a previously selected entity from the entity list in
the Select databox.
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
“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.
CHAPTER 3 3
“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 (p. 33)).
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).
Go to Root Menu This icon will return you to the Select menu where you started the
Icon action.
Go to Previous The role of this icon is similar to the Go to Root Menu icon, except
Menu Icon that it returns you to a previously selected menu in a multi-level
definition. (the previously selected Select Menu may or may not
be the root menu).
Entity Filter Icons

The icons in this category help you identify coordinate systems frames, specify vectors and axes,
and define or restrict the selection of geometric and finite element entities.
Axis and Vector Select Icons

These select icons are displayed whenever you need to define an axis of rotation or a vector of
translation.
The numbers on the three Principal Axis Icons icons refer to principal axes 1, 2 and 3. Depending
on your selection of a coordinate frame, these are:
• X, Y, and Z axes in a cartesian coordinate frame
• Radius, Theta, and Z definitions in a cylindrical coordinate frame
• Radius, Phi, and Theta definitions in a spherical coordinate frame
PART 2
Basic Functions
Principal Axis Icons
Selects principal axis “1” of a predefined coordinate frame.
Selects principal axis “2” of a predefined coordinate frame.
Selects principal axis “3” of a predefined coordinate frame

In a cylindrical coordinate system: In a spherical coordinate system:
AXIS 1 ⇒ Positive X direction (θ = 0) AXIS 1 ⇒ r = 1.0, θ = 0, φ = 90
AXIS 2 ⇒ r = 1.0, θ = 90, Z = 0 AXIS 2 ⇒ r = 1.0, θ = 90, φ = 90
AXIS 3 ⇒ Positive Z direction AXIS 3 ⇒ r = 1.0, θ = 90, φ = 0
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.
CHAPTER 3 3
Geometry Select Icons

Whenever geometric entities must be selected, several geometry icons will be displayed.
Selecting Points
The following icons enable you to select a point whether it is an existing entity or just a position
in space.
Selects a point. Selects a node.
Selects a vertex of a curve, Selects the intersection of a curve

surface, or solid. and a surface.
Selects the intersection of two Selects a position on a surface.

curves.
Selects a point on a curve closest Selects any X, Y screen position.

to an off-curve point. The Z-value will be zero.
Selecting Curves
You will see these icons when you create new curves or when you need to select existing ones.
Selects a curve. Defines a straight curve between

two end-points.
Selects an edge of a surface or Creates a curve using an existing

solid. curve and two points on the curve.
Creates a curve where two

surfaces intersect.
Selecting Solids
With these icons you can select solid geometry.
Selects any solid. Selects a solid that is interpolated

between two surfaces.
Selecting Surfaces
These icons are displayed for creating a surface or for selecting an existing surface.
Selects any surface. Selects a trimmed surface
Creates a surface interpolated Selects the face of a solid.

between two curves (ruled
surface.
PART 2
Basic Functions
Selecting Vertices for Decomposed Surfaces

These icons are displayed to help you pick vertices that define a new surface when a trimmed
surface is decomposed into three- and four-sided surfaces. (See Decomposing Trimmed
Surfaces (p. 255) in the MSC.Patran Reference Manual, Part 2: Geometry Modeling).
Selects an edge-point on Selects an interior point Selects a vertex of a

a surface. on a surface. surface.
CHAPTER 3 3
FEM Select Icons

Whenever FEM entities must be selected, one or more of these icons will be displayed.
Selecting Nodes
This icon appears whenever you need to pick a node.
Selects nodes
Selecting Elements
These icons are displayed whenever you are selecting elements or parts of elements.
Selects a point element. Selects a triangular element.
Selects a beam element. Selects a quad element.
Selects any 2D element. Selects any solid element.
Selects a tetrahedral element. Selects a hex element.
Selects a wedge element. Selects an element edge.
Selects an element face. Selects an element with free edges
Selects an element with free faces. Restricts selection to elements only.

PART 2
Basic Functions
3.3 The List Processor

The names and ID numbers of the entities you picked are entered into the databox of the
application form that initiated the selection. The resulting character string, or pick list, is then
translated into the appropriate format and processed according to the active command.
The part of the software that is in charge of interpreting the contents of select databoxes so that
they could be converted to actions is called the list processor. Whether the character strings are
supplied by the graphics system (when you select entities), or typed or pasted in the databox,
the list processor puts them into the correct syntax so that all of the MSC.Patran application
programs will understand their meaning.
Examples of pick list syntax are:
Node 9 18
Elm 1 4 5 8
Quad 4
hpat 10
Surface 1.2
If you intend to do your own programming for MSC.Patran applications, you need to familiarize
yourself with the requirements of the list processor. For further information please refer to
Creating Lists (p. 366).
CHAPTER
Working with Files
4
■ File Types and Formats
■ The File Menu
■ File Commands
PART 2
Basic Functions
4.1 File Types and Formats

In MSC.Patran, all project-related information is stored in files of various types and formats. The
following is a brief description of the major file types that are created or accessed during
MSC.Patran operations:
MSC.Patran Database. This file contains the data that define your geometric and finite
element model, as well as all analysis results. Databases are binary files that are automatically
assigned a.db file name extension (e.g., test.db). This extension must remain with the file name.
3
Session File. 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. Session files are given a.ses.xx filename extension,
where xx is a number that shows the position of this session file in the sequential order of session
files (e.g., test.ses.01= the first session file). MSC recommends that you maintain the.ses
extension, although this is not a strict requirement.
Journal File. A journal file contains all database related commands executed while creating a
specific model. A journal file spans all sessions required to complete a model. Journal files are
assigned a .jou extension (e.g., test.db.jou).
Hardcopy File. A hardcopy file is a generic file named patran.hrd that is used as an
intermediate step to creating an output file for specific print drivers, such as HP-GL and CGM.
Patran Neutral File. The Patran Neutral file is a specially formatted file that contains Patran 2.5
model information. The neutral file provides a means of importing and exporting model data.
IGES File. IGES (Initial Graphics Exchange Specification) files are ANSI standard formatted
files that make it possible to exchange data among most commercial CAD systems.
MSC.Patran supports a fixed line length ASCII file format, where the entire file is partitioned
into lines of 80 characters in length, beginning with the first character in the file.
Patran Results File (or Patran Flat File). If an Application Preference, such as
MSC.Patran ABAQUS, cannot locate or access the MSC.Patran database to read in model and/or
results data, the interface will write the corresponding database commands to a file called the
Patran results file or the Patran flat file. This may occur when the interface is executed on a
platform that is incompatible with the platform used to run MSC.Patran (see Accessing the
MSC.Patran Database (Ch. 8) in the PCL and Customization manual).
PFEA 2.5 Results File. This is the binary results file generated by P/FEA 2.5. The P/FEA 2.5
results file usually has a.res file extension.
Patran 2.5 Results Files. The three formats of Patran 2.5 results files that can be imported into
MSC.Patran are:
• Element results file (.els)
• Nodal results file (.nod)
• Displacement results file (.dis)
For more about importing Patran 2.5 Results Files, see PATRAN 2.5 Results Files (p. 483).
CHAPTER 4 4
Working with Files
Startup Files
MSC.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 (p. 41) is used to define a default environment for the MSC.Patran session.
The environment includes hardcopy parameter settings and operation of MSC.Patran’s 3D
driver.
The p3prolog.pcl and p3epilog.pcl Files (p. 46) are used to customize and automate PCL
capabilities within MSC.Patran, and to provide a way for customized forms and widgets to be
created.
Startup Session Files (p. 46). 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
MSC.Patran with its startup session file feature.
For more information on these user defined customization files for MSC.Patran, continue onto
the following sections.
The settings.pcl file

MSC.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 MSC.Patran session using the available
widgets and forms. To ensure the MSC.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).
All of the entries in settings.pcl are written in PCL and most have calls to the PCL’s 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. 179) in the MSC.Patran
Reference Manual, Part 1: Basic Functions.
Integer variables set using pref_set_env_integer()

create_dup_geometry (3) Controls the creation of duplicate geometry:
• 1 creates duplicate geometry automatically.
• 2 never creates duplicate geometry.
• 3 asks user for permission before creation.
PART 2
Basic Functions
graphics_colors (150) Number of colors allocated in the colormap.

message_warning (3) Warning message options include:
• 1 indicates that the message should be written to the
history window.
• 2 indicates that a warning bell should also be rung.
• 3 indicates that a modal form should be displayed as
well as writing the message to the history window.
3
Real variables set using pref_set_env_real()
hc_letter_ht (0.8) (HPGL & HPGL/2 only)
VisibleHistoryItems (3) Number of history lines to be displayed in the main form.
Also can be controlled by dragging the main form border.
Logical variables set using pref_set_env_logical()

SmallScreen1Layout (False) True causes MSC.Patran initial menu/viewport
configuration to be automatically sized for small monitor
screens. Avoids truncation of certain MSC.Patran forms.
ApplSwitchIsPopup (False) True causes the application switches to be removed from
the main form and displayed as a popup menu. This is also
controlled by the Preferences Forms... pulldown form.
Show_cycle_picking_form True causes the cycle picking form to be displayed. This is
(True) also controlled from the Preferences Forms...form.
Show_Icon_Help (True) True causes the popup help to be displayed when the
cursor is placed on an icon.
Save_Vis_History_Item_ True causes the number of displayed history lines to be
Count (True) saved between sessions.
String variables set using pref_set_env_string()

graphics_fullcolor Full color mode or lookup mode. Options include “YES” and NO”.
(“NO”) “YES” will use full-color color processing techniques. “NO” will
use lookup or color table color processing techniques.
graphics_hardware Hardware graphics device or software graphics device. Options
(“NO”) include “YES” and “NO.” “YES” will use the local graphics system
of the host. “NO” will use the software graphics device, X
Windows.
graphics_refresh Automatically refresh exposed areas of the viewport on machines
(“NO”) without backing store.
CHAPTER 4 4
Working with Files
insight_graphics_ Graphics device for the Insight application. Options include

hardware (“NO”) “YES” and “NO.” “YES” will use the local graphics system of the
host. “NO” will use the 3D driver. For more information on which
graphics options are supported for Insight, see Using the
mscsetup Utility (p. 34) in the MSC.Patran Installation and
Operations Guide.
INTERBASE_TMP_DIR Directory used by interbase to store temporary data.
(“/tmp”)
p3team_graphics_ Graphics device for the MSC.Patran TEAM application. Options
hardware (“NO”) include “YES” and “NO.” “YES” will use the local graphics system
of the host. “NO” will use the software graphics device, X
Windows.
entity_picking_ Selects the shape of the cursor when in entity picking mode.
cursor (holeangle) Controlled by the Preferences Picking... form. Options include
“holeangle”, “+hole”, “xhole”, “+” and “x”.
select_menu_layout Selects the orientation of the select menu from either vertical or
(vertical) horizontal. Horizontal selection is ignored if select menu is used as
a popup, below. Options include “vertical” and “horizontal.”
select_menu_type Selects whether the select menu automatically appears as a form
(form) or is controlled as a popup by assigning to a key (Key must be
selected using the Preferences Key Map form). Options include
“form” and “popup”.
String variables set using pref_env_set_string()

"ResTmplAutoLoadDirOrder","1, This parameter alters the top directory search order
3,2,4" when looking for Results Templates to Auto load in a
database. The default order is “1,2,3,4.” Permutations of
the integers permute the directory hierachical search
order. The default order is none, ., $HOME, and
$P3_HOME. Thus, the above example will cause
$HOME to be searched before the current directory (.).
"result_capture_filename","pa This settings parameter sets the default report filename
tran.prt" used in the Results application when writing reports
"result_quick_avg_domain", All is the default that is used if nothing is set, or if
"All" invalid values are given. Valid values are: All, Material,
Property, EType, Target, Element
"result_quick_extrap_method", ShapeFunc is the default that is used if nothing is set, or
"ShapeFunc" if invalid values are given. ShapeFunc, Average,
Centroid, Max, Min, AsIs.
"result_quick_transform", This settings parameter sets the default coordinate
"Default" transformation method for Quick Plots in the Results
application. Valid values are: Default, Global, CID,
ProjectedCID, None, Material, ElementIJK
PART 2
Basic Functions
"result_quick_avg_method","De This settings parameter sets the default averaging

riveAverage" method for Quick Plots in the Results application. Valid
values are: DeriveAverage, AverageDerive, Difference,
Sum
“NastranResultsOutput”,”XDB This parameter sets the default results output type for
Only” the MSC.Nastran preference. The default is “XDB and
Print” if this parameter is not specified. Valid values
are:
3 XDB Only
XDB and Print
OP2 Only
OP2 and Print
Print Only
None
Logical variables set using pref_env_set_logical()

"ResTmplAutoLoadNewDb", Enables the automatic loading of Results Templates for new
TRUE databases. Setting this parameter to FALSE disables the
automatic loading and is the default.
"ResTmplAutoLoadOpenDb", Enables the automatic loading of Results Templates when
TRUE opening existing databases. Setting this parameter to
FALSE disables the automatic loading and is the default.
"ResTmplAutoLoadAllFiles", Finds all matches when searching for the Results Template
TRUE initialization session file. Setting this parameter to FALSE
causes the usual pattern of behavior of stopping when the
first matching file is found in the directory search
hierarchy. FALSE is the default.
"result_dbopen_display", Any posted result plots displayed when a database is
TRUE closed are redisplayed when reopened. This is the default.
If plots are not to be displayed run a database is opened,
then set this parameter to FALSE.
“Use_Pref_Elem_Test", Logical variable designed for utilizing MSC.Nastran
def_value element checks from within MSC.Patran.
If this variable is set to TRUE, some of the Finite Element
Verification functions will be the exact check that is run by
MSC.Nastran. This will be indicated by the different icon.
CHAPTER 4 4
Working with Files
Integer variables set using pref_env_set_integer()

"result_loadcase_abbreviate", 10Result Case names, when multiple subcases (time
steps, load steps, etc.) exist, are displayed in an
abbreviated form if there are more than the
specified number of subcases. This condenses the
number of Result Case items displayed in listboxes
in the Results application.
"prop_form_full_refresh_limit", If the number of properties in the database exceeds
n_prop_limit n_prop_limit, the following form behavior changes
will occur:
• Newly created properties will be added to the
bottom of the listbox. The listbox position will not
change.
• Renamed properties will replace the old property
at the same position in the listbox regardless of
the sort and filter settings.
• To force a refresh of the listbox, the filter button
may be used.
• Properties are not re-read from the database and
the property listbox is not refreshed each time the
Property/Create or Property/Modify form is
opened. All of the standard methods (
elementprops_create(), elementprops_modify(),
elementprops_delete(), elementprops_expand(),
elementprops_compress() ) for modifying
properties on the database will cause a signal to
re-read the database and refresh the listbox if
they are performed while the properties form is
closed. However, any direct db calls to modify
properties will not. Therefore, if direct db type of
operations are performed, the property form will
become out of sync with the database. To re-sync,
the database must be closed and reopened. Also,
switching the Property form Action to Delete,
Compress or Expand and then back to Create or
Modify triggers a database re-read. This same
behavior occurs in V2001.
• Opening the Property/Delete or Compress forms
causes a listbox refresh the next time the
Property/Create or Modify form is opened.
Otherwise switching between Property/Create
or Property/Modify forms is fast.
• Creating or Modifying properties from a session
file (command line) will cause a listbox refresh
the next time the Property/Create or
Property/Modify form is opened.
PART 2
Basic Functions
Preference Environment Variables for Hardcopy. The following is a table of preference

environment variables displayed in settings.pcl. The environment variables are used with the
MSC.Patran hardcopy drivers: PostScript, HPGL and HPGL/2. These variables can be modified
in a number of ways in MSC.Patran:
• They are displayed as widgets on the hardcopy forms. Please refer to File>Print
(p. 179) for information on how to access these forms in MSC.Patran.
• They are displayed in the settings.pcl file, which can be modified with any text
editor.
3 • They are also read as environment variables. These hardcopy environment variables
may be modified using the UNIX setenv command or the Windows NT set command.
The following is a table of all hardcopy variables defined in MSC.Patran. Further explanation of
the variable values can be found in File>Print (p. 179):
Other Preference Environment Variables
Environment
Preference Name Default Possible Values
Variable Name
Duplicate geometry create_dup_ P3_CREATE_DUP_ 3 1
creation control geometry GEOMETRY 2
3
Interbase temp file INTERBASE_TMP_DIR TMP /tmp /tmp2
directory /users/home
MSC.Patran p3animation_ none NO NO
ANIMATION graphics_hardware YES
hardware acceleration
option
The p3prolog.pcl and p3epilog.pcl Files

The files p3prolog.pcl and p3epilog.pcl are read during the initialization of MSC.Patran. The
p3prolog.pcl file allows the user to predefine PCL variables and to pre-compile PCL files or
functions. The p3epilog.pcl file is used to create user defined or customized widgets.
The p3prolog.pcl and p3epilog.pcl files may be added to the default directory (where
MSC.Patran will be executed from), or to the home or login directory.
The p3prolog.pcl file is one of the first PCL files to be read by the MSC.Patran system during
startup. While it is a standard PCL file, the PCL entries contained in this file should not reference
any of the standard built-in PCL functions since MSC.Patran has not yet been initialized when
this file is read.
The p3epilog.pcl file is one of the last PCL files to be read by the MSC.Patran system during
startup. Since most PCL applications have been initialized by the time this file is read, PCL calls
may, in general, include PCL application calls. The p3epilog.pcl file would contain PCL calls
that create user defined forms and widgets.
For an example of how p3epilog.pcl is used to create customized widgets, please refer to
Example: Creating a Simple Customized Menu and Form (p. 230) in the PCL and
Customization.
CHAPTER 4 4
Working with Files
Startup Session Files

During the startup of MSC.Patran, you may define a default play and record session file. The
session file user interface consists of three different levels of interfaces where each level can
supersede the previous one. 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 (p. 177) interface.
Startup using system files. MSC.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. MSC.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
The Template Database File (template.db)

As documented in Basic Functions, new MSC.Patran databases are not empty. When a new
database is created, a template.db file is copied from the MSC.Patran delivery directory into the
default directory, and is used as the new database file.
The template.db file contains specific analysis code definitions for all MSC.Patran Application
Preferences and Modules (e.g., ABAQUS, MSC.Nastran, etc.). Thus, when constructing a model,
users have available the choices of accessing a specific set of any supported analysis code
definitions within the template.db.
PART 2
Basic Functions
However, the template.db file may be customized for specific material and element definitions,
as well as customizing for only those MSC.Patran Application Preferences or Modules that you
are licensed to run.
For example, if your site has a set of materials that is more extensive than the standard set of
materials, you can add the specific material information to the template database. This would
ensure that all subsequent MSC.Patran databases created would reference the customized
template.db file, and it would contain the additional material definitions.
Similarly, specific element types can be removed from the standard MSC.Patran element library
3 in the template database, and the removed element types would not appear for users that
reference the modified template.db file during the creation of the new database.
Refer to the MSC.Patran Installation and Operations Guide for more information on
configuring the template.db file.
CHAPTER 4 4
Working with Files
4.2 The File Menu

The File menu displays the commands that create and manage MSC.Patran files.
Menu Conventions
A menu key word with ellipses (...) attached to it will call up an additional form in which you
enter further data.
If a menu key word is followed by an expression containing the abbreviation Ctrl, this item can
also be accessed by an accelerated keyboard shortcut. For example, for File>New, the menu
shows Ctrl N. This means that, if desired, you can activate this command by pressing the Ctrl
(Control) key and the designated letter key (N) simultaneously instead of clicking File and then
the New keyword.
The File menu functionalities are described below in the order in which they appear in the menu.
File
New... Ctrl N
Open... Ctrl O
Close Ctrl W
Save Ctrl S
Save a Copy Reclaim...
Utilities Revert...
Rebuild...
Import...
Export...
Session Play...
Record...
Print...
Images...
Report...
Quit Ctrl Q
PART 2
Basic Functions
New... Displays the New Database dialog box in which you enter the name
of a new model. The form presents the default template.db template
file; if desired, you can specify another previously defined and
saved template file.
When a new database is created, a template.db file is copied from
the MSC.Patran delivery directory into the default directory. This
file contains specific analysis code definitions for all MSC.Patran
3 application preferences and modules (e.g., ABAQUS,
MSC.Nastran). 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 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 don’t want certain element types appearing
when a new database is created, you can exclude those from the
standard MSC.Patran element library in the new template
database.
• Application preferences--you can eliminate from the new
template database those applications and modules that your
site is not licensed to run.
For more information on configuring the template.db file, please
refer to the MSC.Patran Installation and Operations Guide.
Open... Displays the Open Database dialog box in which you can select the
name of an existing MSC.Patran database.
Close Closes an open database without exiting MSC.Patran. Saves all
changes made to the database during the current session.
Save Although MSC.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... Reclaims unused space allocated to the current database. Note that
when you reclaim database space the file’s Undo history will be
deleted.
• Revert... Returns a database to the state in which it existed when it was first
opened (provided that the Revert Operation has been enabled; see
Preferences>Global (p. 338)). Changes made during the current
session will be lost.
CHAPTER 4 5
Working with Files
• Rebuild... Executes a selected journal file (see Journal File (p. 40)) to re-create
an MSC.Patran database. The rebuilt database remains open and
allows you to continue to work on the model. This command is
useful when the original database is either lost or not accessible
(e.g., the database is archived or resides on a different computer
platform).
Import... Enables you to bring in model or results data created outside of the
current database. Model data may be in MSC.Patran database
format, Patran 2.5 neutral file format, MSC.Nastran input file
format, CAD format, or Standard Data Exchange format. Import
recognizes the following CAD formats:
• CATIA
• EUCLID 3
• I-DEAS
• Pro/ENGINEER
• CADDS 5
• Unigraphics
• Parasolid
• ACIS
Import results from a MSC.Patran Results Flat file, P/FEA Results
file or a PATRAN 2.5 Results file (Element, Nodal or Displacement
Results file).
• Importing Results
Import recognizes the following Standard Data Exchange formats:
• STEP AP203 and AP209
• Express Neutral STL
• IGES
• VDA
Export... Translates an open MSC.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 MSC.Patran groups.
Session >
• Play... Executes a specified MSC.Patran session file (see Session File
(p. 40)) 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
MSC.Patran session from the time this file was opened. The default
patran.ses session file will be generated as well.
PART 2
Basic Functions
Print... Sends the image of one or all viewports and/or XY plot windows to
a designated printer or creates a hardcopy file in order to print or
plot at a later time. Certain printing options are functions of the
available printers and print drivers.
Images... Creates graphical outputs of model displays in a variety of popular
graphics file formats, including interactive Internet-ready
animations.
3 Report... Creates a printable text file that contains MSC.Patran model

summary information, node and element attributes, properties and
results.
Quit Closes an open database, saves any changes made, and ends the
active session.
CHAPTER 4 5
Working with Files
4.3 File Commands

The File Menu commands activate dialog boxes in which you interact with MSC.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 MSC.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 don’t remember where
your files are located, move up and down the hierarchy of all folders with the Windows icons,
the Windows NT 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 MSC.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.
PART 2
Basic Functions
File>New Creating a New File
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
• Modify Preferences checkbox
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... (p. 50).
Modify Preferences Turn this toggle on (✔) 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 (p. 339)), the analysis code you intend to use, and
the type of analysis you want to perform on the model.
CHAPTER 4 5
Working with Files
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.
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.
PART 2
Basic Functions
Tolerance Tolerance specifies the maximum distance within which two like
entities (e.g., points), are said to be coincident. Tolerance is a
global parameter, that is, it affects the entire modeling process.
Entity coincidences and congruences:
• coincident points--two points separated by a distance less
than or equal to the tolerance
• coincident curves--distance between all points of two
3 curves is less than or equal to the tolerance
• connected curves--two curves share the same endpoints
• coincident surfaces--distance between all points of two
surfaces is less than or equal to the tolerance
• topologically congruent surfaces--two surfaces that share
the same 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 MSC.Patran
Main Form’s Preferences menu.
• Based on Calculates the tolerance based on the expected maximum model
Model size. Recommended tolerance is .05% of the expected maximum
model size, however, you may specify a different tolerance
depending on the accuracy of the geometry construction.
• Default Uses the current setting of the global model tolerance defined in
the template database, normally .005.
Maximum Enter the approximate maximum model size if you selected the
Model Dimension Based on Model tolerance definition.
CHAPTER 4 5
Working with Files
Analysis Code Select the program you intend to use for the finite element
analysis.
Analysis Type Select the type of analysis you will perform on the model.
Your selection of an analysis code, as well as the analysis type,
will affect all aspects of the finite element modeling process,
since analysis codes have their own unique definitions for
element types, MPC types, and all other FEM entities and
properties.
If you decide to change the analysis code or the analysis type
preference during the modeling process, you may lose the data
that apply only to the previous preference settings. Therefore, to
keep analysis-specific data from being lost, it is best to specify
the analysis code and the analysis type at the beginning of the
modeling session.
Analysis Code and Analysis Type can also be defined in the
MSC.Patran Main Form’s Preferences menu.
PART 2
Basic Functions
File>Open Opening an Existing File
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.
3
CHAPTER 4 5
Working with Files
File>Save a Copy Saving a Copy of a Database
Use this command to save a copy of your database under a different name.
Save Journal File If you turn this toggle on (✔), the journal file associated with
Copy Also 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 Enter a new name for the copied database.
PART 2
Basic Functions
File>Reclaim Freeing up Unused Disk Space
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.
3 Important: When you reclaim database space, the file’s 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.
CHAPTER 4 6
Working with Files
File>Revert Reverting to the Original Database
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 (✔) 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:
8. Select Yes or No to complete the action.

PART 2
Basic Functions
File>Rebuild Rebuilding a Model from a Journal File
With this utility, you can rebuild a model created in MSC.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 MSC.Patran file. When you invoke
File>Utilities>Rebuild, the Rebuild Database dialog box will display the list of journal files
3 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.
CHAPTER 4 6
Working with Files
File>Import Importing Models and Results
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 MSC.Patran database format, Patran 2.5
neutral file format, MSC.Nastran input file format, or in one of several CAD formats.
Common Items in Import Dialog Boxes

A number of items in the Import dialog box are common to all model import functions
regardless of the imported file’s origin and will appear in all model import dialog boxes.
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 Select the name of the file you want to import.
Files of type Indicates the valid file type and assigned file name extension,
unique to the selected source of the imported file.
Source Identifies the software application used to create the
imported model.
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 Although this item is dependent on the source file origin, it
generally leads to a spreadsheet or a form that displays
application-specific information about imported entities.
PART 2
Basic Functions
Importing an MSC.Patran Database

When you import an MSC.Patran database, the Import form contains the common import
functions and two additional options, specific to MSC.Patran:
Equivalence Allows you to select methods and conditions for merging

Options coincident nodes.
Preview MSC.Patran Displays a list of the number of entities and their ID
Database specifications in the database targeted for import.
3
MSC.Patran DB Import Options
This selection presents a multipurpose spreadsheet that provides extensive information about
how to manage incoming database entities.
CHAPTER 4 6
Working with Files
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 = Default Offset
10000 1 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.
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 entity’s name and import it with that name.
• Try to combine the two entities into one. If the two cannot be combined because of
conflicting properties, issue a warning and resort to the option above.
In some cases, the merge operation is not actually merging incoming and existing data. For
example, if a material is already present in the receiving database and a material with the same
name and properties exists in the imported database, the material definition in the primary
database is retained, and that from the secondary database is discarded.
PART 2
Basic Functions
Groups, however, are not likely to have identical properties. If the incoming database contains
a group with the same name as one that exists in the receiving database, the entities from the
imported database 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 Real Number Equality Criteria
Material Load/BC Field 3
3 Compare Names Load Case Group Significant Digits
0.XXXE+-YY
Element Property DOF List

Compare Names
Entities to Merge In these cells you specify the entities you want to merge if a
Upon Duplication 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.
Real Number This criteria is used to determine whether two real properties
Equality Criteria (scalar or vector components) are close enough in value to be
Significant Digits assumed equal.
To determine near-equality, compare digits of the two
numbers in normalized exponential form, from left to right
(discarding leading zeroes) up to the specified number of
significant digits. For example, for Significant Digits = 3, the
following are considered equal:
0.234516E+08 0.234925E+08
But, the following are not:
0.233925E+08 0.234925E+08
CHAPTER 4 6
Working with Files
Spreadsheet Cells
The cells in the spreadsheet identify the imported entities and specify certain characteristics.
Import Column
Current Database Ranges

Import? MinimumID MaximumID ID Offset Name Prefix
Point All 1 250 10000 Not Used
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.
If you select a single cell, a second dialog box will provide a set of options.
PART 2
Basic Functions
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).
3 Preview MSC.Patran Displays the MSC.Patran Database Preview form that shows
Database. . . the entities, and their corresponding ID numbers, as
contained in the import database.
Minimum ID and Maximum ID Columns

Point All 1 250 10000 Not Used
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.
ID Offset Column

Material All 1 250 10000 Not Used
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.
CHAPTER 4 6
Working with Files
Offset Options
If you select an ID Offset cell, a second dialog box will provide a set of options.
Offset Option Pick one of the following:

• Default--from the Default Offset databox (see
Numbered Entity Offset Defaults (p. 65)).
• Auto--if the offset value is set to Auto, the IDs are offset
starting at the current maximum ID plus 1. (MSC.Patran
sets the default to Auto, unless the
db_import_auto_offset environment parameter is
changed).
• Input--allows you to enter any offset value in the
databox.
Offset Value Enter the desired offset value.
PART 2
Basic Functions
Name Prefix Column

Material All Not Used Not Used Not Used SM_001_
This column shows the prefix that is to be applied to incoming entity names. If the merge toggle
3 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 (p. 65) for more details.
Prefix Option Pick one of the following:

• Default--from the Default Prefix databox (see Named
Entity Prefix Defaults (p. 65)).
• Input--allows you to enter any prefix value in the
databox.
Prefix Value Enter the desired prefix value, starting with a letter.
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 (p. 66)). 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.
CHAPTER 4 7
Working with Files
Loads and Boundary Conditions. If the LBC toggle in the MSC.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.
PART 2
Basic Functions
Analysis Coordinate Frame Merge Rule. During nodal equivalencing the analysis coordinate
frame at a surviving node is determined by a rule that takes into account the analysis coordinate
frames and the boundary conditions at both the primary and secondary node being
equivalenced. The following table shows this rule for various coordinate frames (CF) and
boundary condition definitions (BC).
Analysis CF at Analysis CF at Analysis CF at Message

Primary Node Secondary Node Equivalenced Node Level
3 Global Global Global No
Local-1 Local-1 Local-1 No
Global without BCs Local without BCs Global Warning

Global without BCs Local with BCs Local No
Global with BCs Local without BCs Global Warning
Global with BCs Local with BCs Fatal
Local without BCs Global without BCs Global Warning

Local without BCs Global with BCs Global Warning
Local with BCs Global without BCs Local No
Local with BCs Global with BCs Fatal
Local-1 without BCs Local-2 without BCs Local-1 Warning

Local-1 without BCs Local-2 with BCs Local-2 Warning
Local-1 with BCs Local-2 without BCs Local-1 Warning
Local-1 with BCs Local-2 with BCs Fatal
CHAPTER 4 7
Working with Files
Equivalence Options Dialog Box
Equivalence Specify whether nodes and/or geometry are to be

Nodes/Geometry equivalenced as they are imported (both are ON by default).
Only items that are common between the current database
(primary model) and the import database (secondary model)
are considered for equivalencing. If duplicate items are
found within either model but none of those are duplicated in
the other model, no action will be taken. In other words, only
inter-model equivalencing is performed, as opposed to
inner-model equivalencing.
Tolerance Method Tolerance method applies to nodal equivalencing only.
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.
PART 2
Basic Functions
Equivalence DFEM This toggle controls whether discrete FEM fields are
Loads/BCs/Props combined when loads and boundary conditions or properties
are merged. Two discrete FEM fields referenced by duplicate
• Combine
LBCs or Properties (one in the current model and another in
DFEM Fields
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 Specify how boundary conditions are merged within a
3 Boundary DFEM field. By default, the boundary conditions in the
Conditions primary model override the incoming secondary model
values. Optionally, the secondary values can be added to the
existing primary values.
• DFEM Vector Specify how vector loads are merged within a DFEM field.
Loads 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.
• DFEM Scalar Specify how scalar loads are merged within a DFEM Field.
Loads 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.
CHAPTER 4 7
Working with Files
MSC.Patran Database Preview

In the MSC.Patran Database Preview form you can view the number of entities of each type
contained in the import file database and the ID range (minimum & maximum) for each entity
type. This form may be 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.
PART 2
Basic Functions
Importing PATRAN 2.5 Neutral Files

Neutral files provide a means for importing and exporting model data. You can import one or
more neutral files into an MSC.Patran database. If more than one neutral file is read into a
database, the entity IDs of each consecutive imported model must be offset to avoid conflict. The
offsets may be defined either manually or automatically (see Entity Label Offset Definition
(p. 76)).
File Formats (p. 453) provides more information about the neutral file system.
3
current.
Neutral Options Brings up the Neutral Import Options form that enables you
to select the types of entities targeted for import.
CHAPTER 4 7
Working with Files
Neutral File Import Options

In this form you can select the entity types (packets) you want to import.
Define Offsets... Select this button if the likelihood of entity ID duplication

exists (e.g., when several neutral files are imported). It will
activate the Entity Label Offset Definition form in which
you can specify offsets to avoid conflicting IDs.
PART 2
Basic Functions
Entity Label Offset Definition

In this form you can specify entity ID offsets in order to avoid conflicts arising from duplicate ID
numbers.
Options for Entity Selection

• All entity packets offset the same way
• Each entity packet offsets differently
Options for Offset Definition
• Automatic--system obtains the next available ID in the database
• Manual--you specify the offset value
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.
Unique value to each entity type:
• click on an entity, type the offset in the Input Offset Value data field, press Enter, or
• select Automatic Offset.
CHAPTER 4 7
Working with Files
Importing MSC.Nastran Input Files

While MSC.Nastran input files are used primarily to pass information into the MSC.Nastran
FEA solver, they can also be imported into MSC.Patran. You can import several files, however if
duplicate entity IDs exist, the IDs of each consecutive model must be offset to avoid a conflict
(see MSC.Nastran Entity Label Offset Definition (p. 79)).
current.
MSC.Nastran Brings up the Entity Selection form that enables you to select
Options the types of entities targeted for import.
PART 2
Basic Functions
MSC.Nastran Input File Options

In this form you can select the entity types (packets) that will be included in the imported
database.

exists (e.g., when several MSC.Nastran files are imported). It
will activate the Entity Label Offset Definition form in
which you can specify offsets to avoid conflicting IDs.
CHAPTER 4 8
Working with Files
MSC.Nastran Entity Label Offset Definition

numbers.

Assigning Offsets
• pick Automatic Offset to let the system assign offset automatically
PART 2
Basic Functions
Importing Express Neutral Files

Express neutral files are intermediate files created during a Unigraphics or CV CAD Model
Access process. You can obtain these files at any time and on any platform enabling you to access
CAD geometry on systems where otherwise this may not be possible.
current.
Express Options Brings up the Express Import Options form where you can
select the type and attributes of entities targeted for import.
CHAPTER 4 8
Working with Files
Express Neutral File Import Options

In this form you can select the types and attributes of entities included in the imported database.
Import Preferences Activates the Import Preferences dialog box in which you can
specify how certain geometric entities will be represented in
the MSC.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 Provides a color filter to further differentiate entities selected
for import.
PART 2
Basic Functions
Entity Layers
• All Layers If ON, all entities are import candidates, regardless of layer
assignment.
• Layer Numbers Turn All Layers OFF and identify the layers on which the
imported entities reside.
Group Brings up a dialog box in which you specify group
Classification... assignments for imported entities.
3 Preview Allows you to display the contents of the import file to inspect
Express File... prior to actually bringing it into your database.
CHAPTER 4 8
Working with Files
Express 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 MSC.Patran database.
Trimmed Surface Specifies how four-edged faces of trimmed surfaces will be

Type represented in the database (simply trimmed or general
trimmed).
Solid Solids may appear in boundary representation (B-rep Solids)
Representation or as a collection of constituent surfaces. The Parameterized
Solid option allows B-rep solids, whose faces are biparametric
surfaces, to be automatically converted to triparametric
solids.
Enable Tolerance If OFF (default), global model tolerance is calculated based
Prompt on the expected maximum model size (see Global Model
Tolerance (p. 339)), without prompting for a response.
Enable Geometry If ON, a geometry tracking log file will be created to describe
Tracking geometric attributes of imported geometry.
Import Action
• Import Executes geometry import.
Geometry
• Calculate Model Processes the file to help determine the best tolerance for
Tolerance geometry import.
PART 2
Basic Functions
Preview Express File

You may get an advanced look at the type and number of entities contained in the file you want
to import. Select the appropriate folder and file name to display this file.
3
CHAPTER 4 8
Working with Files
Express Neutral Group Classification

Creates new MSC.Patran groups and enters imported entities into these groups based on entity
attributes.
Group Name Enter a group name.

Group Entity Select the class of the imported geometric entities (e.g., Curve)
Types whose members will be added to the group.
Group Geometry Highlights the entities that belong the class selected above.
Types Pick one, several, or all to add to the group.
Group Entity Filter imported entities by color. For example, having
Color selected Curve before, click Red and only red-colored curves
will be imported.
PART 2
Basic Functions
Group Entity • All--select all entities regardless of layer assignments

Layers
• Layer numbers--Toggle All Layers OFF and enter the
layer number(s) where the imported entities reside in
the CAD database
Show Express Display the MSC.Patran groups that have been defined for
Groups imported entities.
Delete Express Delete MSC.Patran groups defined for imported geometry.
3 Groups
Importing IGES Files

IGES (Initial Graphics Exchange Specification) files are ANSI standard formatted files that make
it possible to exchange data among most commercial CAD systems.
current.
IGES Options Brings up the IGES Import Options form that enables you to
specify the types and attributes of entities targeted for import.
CHAPTER 4 8
Working with Files
IGES Entities Supported for Import

The following table lists the name and number of IGES entities that you can import into
MSC.Patran.
Table 4-1
IGES IGES
Entity IGES Entity Type Entity IGES Entity Type
Number Number
100 Circular Arc 122 Tabulated Cylinder
102 Composite Curve 124 Transformation Matrix
104 Conic Arc All Forms
106 Copious Data 126 Rational B-Spline Curve
All Forms 128 Rational B-Spline
Surface
108 Plane 130 Offset Curve
Form 1 Positive Bounded Plane 134 Node
Form 0 Unbounded Plane 136 Finite Element
110 Line 140 Offset Surface
112 Parametric Spline Curve 141 Boundary
142 Curve on Surface
114 Parametric Spline 143 Bounded Surface
Surface
116 Point 144 Trimmed Surface
118 Ruled Surface 186 Manifold Solid-Prep
120 Surface of Revolution 190 Plane Surface
PART 2
Basic Functions
IGES Import Options

In this form you can select the types and attributes of IGES entities targeted for import.
Entity Types Identifies the geometric or finite element entities you can import.
Entity Attributes
• Curve on Stipulate your preference as to how trimming curves should be
Surface represented on trimmed surfaces:
Preferences • Per IGES File--as defined by IGES file preference.
• 2D Curve--use parametric space representation (if exists in the 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.
CHAPTER 4 9
Working with Files
• Invisible, Pick any or all three to include the listed entity types in the import
Subordinate, process.
and Annotation
Entities
• Color Filter... Displays the Color Filter dialog box in which you can restrict entity
import based on color designations.
• Level Filter... Displays the Layer Filter dialog box in which you can restrict entity
import based on layer designations.
Group Activates a dialog box in which you can create new MSC.Patran groups
Classification... for placing imported entities.
Preview IGES File... Select an IGES file to preview.
PART 2
Basic Functions
IGES Entity Color Filter

In this form you can select entities for import based on their color designation.
Color Definition IGES entities may refer to an IGES Color Definition Entity
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
CHAPTER 4 9
Working with Files
IGES Entity Level Filter

In this form you can identify the layer(s) that contain the entities you want to import via IGES.
Optionally, you can specify that entities on all layers should be imported.
PART 2
Basic Functions
IGES Group Classification

This dialog box enables you to create new MSC.Patran groups and enter imported entities into
these groups based on entity attributes.

Group Entity Select the class of the imported geometric entities (e.g.,
Types Composite Curve) whose members will be added to the group.
Group Entity Filter entities by color. For example, having selected Composite
Color Curve, click Red to import only red-colored composite curves.
Layers
• Layer numbers--Toggle All Layers off and enter layer
numbers where the entities targeted for import reside in
the CAD database.
Show IGES View all groups defined for imported IGES entities.
Groups
Delete IGES Delete groups defined for imported IGES entities.
Groups
CHAPTER 4 9
Working with Files
Show IGES Groups. This form shows the names of all groups defined for entities imported
from an IGES, CADDS 5, or Unigraphics database. When you pick a group name, the Group
Classification form will display the list of entity types, colors, and levels that have been assigned
to this group.
Delete IGES Groups. In this form you can selectively delete groups that contain entities
imported from IGES, CADDS 5, or Unigraphics databases.
Exporting IGES Surface Data to a Patran 2 Neutral File

Through the Patran 2 Neutral File Translator, you can export IGES type 114 and 128 surfaces as
“Parametric BiCubic” surfaces. For information on converting IGES surface data into Parametric
BiCubic Patches, see Exporting IGES Surface Data as Parametric BiCubic Surfaces (p. 165).
PART 2
Basic Functions
Importing CATIA Files

In the Import dialog box, select CATIA as the source of the imported database.You may directly
import a CATIA model or you can choose to run MSC.GS-Mesher which will create a mesh and
then import that mesh into an MSC.Patran database.
Importing a CATIA Model

To import CATIA V4, CATIA V5, or CATXPRES geometry, select the block icon on the CATIA
Import form.
3
Geometry Import Select the block icon (UNIX only) to import CATIA geometry. To import
Icons a mesh, see Importing MSC.GS-Mesher Meshes from a CATIA Model
(p. 107).
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 If ON, CATIA V4 models are imported in a Parasolid geometry format.
CATIA V5 models will always be imported in Parasolid format and
CATXPRES models will not be imported in Parasolid format.
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).
CHAPTER 4 9
Working with Files
Import Options for CATIA V4 Parasolid Format

If you are importing a CATIA V4 model with the Import to Parasolid option turned ON, the
resulting geometry format will be Parasolid. Use the Import Options form to select the types and
attributes of entities included in the imported database.
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.
Import NoShow If on, CATIA V4 entities that are classified as “NoShow” will
Entities be imported.
PART 2
Basic Functions
Entity Layers
• All Layers If on, all geometry will be imported regardless of whether or
not the geometry is on layers.
• Layer numbers Specify which layers in CATIA V4 to import geometry from.

trimmed).
3
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.
Default model units override value is the Patran Preference
value for “Geometry Scale Factor.”
Sew Sheet Bodies
• Patran Sew Instructs MSC.Patran to sew together sheet bodies using
MSC.Patran Sewing software.
• Verify Boundary The Verify Boundary command is similar to the
Verify/Surface/Boundary command in MSC.Patran.
Equivalence Edge If this toggle is ON, topological vertices will be equivalenced
Vertices during import.
Save Transmit File 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.
CHAPTER 4 9
Working with Files
Import Options for CATIA V5 Parasolid Format

If you are importing a CATIA V5 model with the Import to Parasolid option turned ON, the
To retrieve the CATIA V5 attributes, please see,

ps_get_body_string_attribute (p. 45) and
ps_get_string_attribute (p. 46) in the PCL Reference
Manual, Volume 1: Function Descriptions.
For examples of how these functions are utilized
please see, ps_get_body_string_attribute (p. 21)
and ps_get_string_attribute (p. 23) in the PCL
Reference Manual, Volume 2: Examples.
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.
Attribute Types MSC.Patran will create a string attribute and attach it to geometry
associated with a CATIA V5 publication, feature name, or publication
and Feature Name by selecting "Publication", "Feature Name", or both.
If you unselect both "Publication" and "Feature Name", no attributes
will be created.
PART 2
Basic Functions
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.
Selecting “Feature Name” option will result in:
attribute syntax: Part_ID;feature_name
3 The geometry associated with the feature “Loft.1” will have an attribute with the string
"P1;Loft.1" and the geometry associated with the feature “SURFACE_FEATURE” will have an
attribute with the string:
"P1;SURFACE_FEATURE".
Selecting “Publication” option will result in:

attribute syntax: Part_ID;publication_name
The geometry associated with the publication “PUB_EDGE” will have an attribute with the
string "P1;PUB_EDGE".
Selecting both “Feature Name” and “Publication” will result in:
attribute syntax: Part_ID;publication_name;feature_name
The geometry associated with the feature “Loft.1” will have an attribute with the string
"P1;PUB_EDGE;Loft.1" and the geometry associated with the feature “SURFACE_FEATURE”
will have an attribute with the string "P1;SURFACE_FEATURE".
CHAPTER 4 1
Working with Files
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.
Selecting “Feature Name” option will result in:
attribute syntax:
Product_ID\SubProduct_Instance_Name\Part_Instance_Name;feature_name
The geometry associated with the features “Blisk.1” and “Blisk.2” respectively will have an
attribute with the string:
"BLISKPROD\BLISKSUBPROD.1\DAM3.1;Blisk.1"
"BLISKPROD\BLISKSUBPROD.1\DAM3.1;Blisk.2"
Selecting “Publication” option will result in:
attribute syntax:
Product_ID\SubProduct_Instance_Name\Part_Instance_Name;publication_name
The geometry associated with the publications “BLISK_ONE” and “BLISK_TWO” respectively
will have an attribute with the string:
"BLISKPROD\BLISKSUBPROD.1\DAM3.1;BLISK_ONE"
"BLISKPROD\BLISKSUBPROD.1\DAM3.1;BLISK_TWO"
Selecting both “Feature Name” and “Publication” will result in:
attribute syntax:
Product_ID\SubProduct_Instance_Name\Part_Instance_Name;publication_name;feature
_name
The geometry associated with the features “Blisk.1” and “Blisk.2” and publications
“BLISK_ONE” and “BLISK_TWO” respectively will have an attribute with the string:
"BLISKPROD\BLISKSUBPROD.1\DAM3.1;BLISK_ONE;Blisk.1"
"BLISKPROD\BLISKSUBPROD.1\DAM3.1;BLISK_TWO;Blisk.2"
Entity Layers
• All Layers If on, all geometry will be imported regardless of whether or not the
geometry is on layers.
• Layer numbers Specify which layers in CATIA V5 CATPart or CATProduct to import
geometry from.
Trimmed Surface Specifies how four-edged faces of trimmed surfaces will be represented
Type in the database (simply trimmed or general trimmed).
Group Brings up a dialog box in which you specify group assignments for
Classification... imported entities.
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.
PART 2
Basic Functions
Sew Sheet Bodies

• Patran Sew Instructs MSC.Patran to sew together sheet bodies using MSC.Patran
Sewing software.
Equivalence Edge If this toggle is ON, topological vertices will be equivalenced during
Vertices import.
3 Save Transmit File 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.
In order to retrieve these attributes from the Patran database, there are two functions that may
be used:
ps_get_body_string_attribute (p. 45) and ps_get_string_attribute (p. 46) in the PCL Reference
Manual, Volume 1: Function Descriptions. For examples of how these functions are utilized please
see, ps_get_body_string_attribute (p. 21) and ps_get_string_attribute (p. 23) in the PCL
Reference Manual, Volume 2: Examples.
CHAPTER 4 1
Working with Files
Import Options for CATIA V4

If you are importing a CATIA V4 model with the Import to Parasolid option turned OFF, the
resulting geometry format will not be Parasolid. Use the Import Options form to select the types,
layers, and attributes of entities included in the imported database.
Import Preferences Activates a dialog box in which you can specify how certain geometric
entities will be represented in the MSC.Patran database.
All Layers If ON, all entities are import candidates, regardless of layer assignment.
Layer Numbers Turns All Layers off. Enter the layers where the entities you want to
import reside.
PART 2
Basic Functions
Import Options for CATXPRES

If you are importing a CATXPRES model, the resulting geometry format will not be Parasolid.
Use the Import Options form to select the types and attributes of entities included in the
imported database

trimmed).
Solid Representation Solids may appear in boundary representation (B-rep Solids)
or as a collection of constituent surfaces. The Parameterized
solids.
Enable Tolerance If OFF (default), global model tolerance is calculated based on
Prompt the expected maximum model size (see Global Model
CHAPTER 4 1
Working with Files
Group Classification for CATIA V4 Parasolid Format

One or several MSC.Patran groups may be created to accommodate imported CATIA model
entities. When using a Parasolid format, groups are defined by entity type.

Group Entity Select the type of imported geometric entities that will be
Types added to the group.
Entity Layers
Show Groups View all groups defined for imported CATIA entities.
Delete Groups Delete groups defined for imported CATIA geometry.
PART 2
Basic Functions
Group Classification for CATIA V5 Parasolid Format

entities. When using a Parasolid format, groups are defined by entity type.

Entity Layers
CHAPTER 4 1
Working with Files
Group Classification for CATIA V4/CATXPRES Files

entities. Group membership may be based on both entity type and layer assignment.

Layers
• Layer numbers--toggle All Layers off and enter the
layer(s) where the imported entities reside in the CAD
database
PART 2
Basic Functions
Import Preferences

trimmed).
solids.
Import Action
Geometry
CHAPTER 4 1
Working with Files
Importing MSC.GS-Mesher Meshes from a CATIA Model

Selecting the mesh icon on the CATIA Import form runs MSC.GS-Mesher to create a mesh that
can be imported into MSC.Patran.
To utilize this option, you must have the following software products installed on the machine
where MSC.Patran 2003 is installed: CATIA V4 (UNIX), MSC.GS-Mesher 2002v2, and
MSC.Nastran Preference.
Import
Object: Model
Filter
/user/smith/*.model Source: CATIA
Directories CATIA V4 Models

/smith/. [ ]
/smith/..
/smith/.fminit2.0
/smith/Exercises
/smith/Mail Current Group
/smith/Part_2_basic_functions
/smith/Part_4_FEM default_group
GS-Mesher Options...
Import File
File Type
CATIA V4 Model
-Apply- Filter Cancel
Geometry Import Selecting the mesh icon runs MSC.GS Mesher on a CATIA
Icons model to create and import a mesh.
current.
GS-Mesher Options Brings up the GS-Mesher Options form that enables you to
select the type and topology of the mesh.
File Type Specifies the type of the imported input file. On UNIX, CATIA
V4 .model files are supported.
PART 2
Basic Functions
MSC.GS-Mesher Import Options

Use the MSC.GS-Mesher Import Options form to define the parameters of the imported mesh.
Mesh Type Specifies the type of mesh that MSC.GS-Mesher creates; Tri,
Tet, or Tri and Tet.
Element Size Specifies the element size either by instructing MSC.Patran to
calculate the element size or by defining the
Maximum/Minimum element size. If you define a
Maximum, the minimum will be calculated as 10% of the
maximum. This value may be overridden.
Element Topology Defines the topology of the elements created during the
meshing process.
Mesh Offsets Enables you to define offset values if multiple meshes are
being imported.
CHAPTER 4 1
Working with Files
Importing Euclid 3 Files

In the Import dialog box, select Euclid 3 as the source of the imported database.
current.
Euclid 3 Options Brings up the Euclid 3 Import Options form that enables you
to specify the types and attributes of entities targeted for
import.
Import Options for EUCLID 3

In this dialog box specify your preferences on how to treat surfaces and solids, as well as
tolerances, when importing entities in the MSC.Patran database.
PART 2
Basic Functions

trimmed).
solids.
CHAPTER 4 1
Working with Files
Importing I-DEAS Files

In the Import dialog box, select I-DEAS as the source of the imported database.You may directly
import an I-DEAS model or you can choose to run MSC.GS-Mesher which will create a mesh and
then import that mesh into an MSC.Patran database.
Importing an I-DEAS Model

To import an I-DEAS Model, select the block icon on the I-DEAS Import form.
Geometry Import Select the block icon to import I-DEAS geometry. To import a
Icons mesh, see Importing MSC.GS-Mesher Meshes from an I-
DEAS Model (p. 113).
current.
I-DEAS Options Brings up the I-DEAS Import Options form that enables you
to select the type and attributes of entities targeted for import.
PART 2
Basic Functions
Import Options for I-DEAS

Use this form to select the types of entities included in the imported database and to direct the
handling of the imported entities.
select.
trimmed).
units during import. The settings now include: inches, meters,
millimeters or custom value units.
Sew Sheet Bodies
CHAPTER 4 1
Working with Files

Save Transmit Files If this toggle is ON, the parasolid transmit file will be saved
when an I-DEAS file is imported. This file will be assigned a
.xmt_txt file name extension.
Importing MSC.GS-Mesher Meshes from an I-DEAS Model

Selecting the mesh icon on the I-DEAS Import form runs MSC.GS-Mesher to create a mesh that
can be imported into MSC.Patran.
where MSC.Patran 2003 is installed: I-DEAS 8-9, MSC.GS-Mesher 2002v2, and MSC.Nastran
Preference.
Geometry Import Selecting the mesh icon runs MSC.GS Mesher on an I-DEAS
Icons model to create and import a mesh.
current.
PART 2
Basic Functions

meshing process.
being imported.
CHAPTER 4 1
Working with Files
Importing Pro/ENGINEER Files

In the Import dialog box, select Pro/ENGINEER as the source of the imported database.You
may directly import a Pro/ENGINEER model or you can choose to run MSC.GS-Mesher which
will create a mesh and then import that mesh into an MSC.Patran database.
Importing a Pro/ENGINEER Model

To import a Pro/ENGINEER Model, select the block icon on the Pro/ENGINEER Import form.
Geometry Import Select the block icon to import Pro/ENGINEER geometry. To

Icons import a mesh, see Importing MSC.GS-Mesher Meshes
from a Pro/ENGINEER Model (p. 120).
current.
Pro/ENGINEER Activates the Pro/ENGINEER Import Options form that
Options enables you to select the type and attributes of entities
targeted for import.
Import to Parasolid If ON, Pro/ENGINEER models are imported in a Parasolid
geometry format.
File Type Select the type of Pro/ENGINEER file you are importing.
PART 2
Basic Functions
Import Options for Pro/ENGINEER Parasolid Format

If you are importing a Pro/ENGINEER model with the Import to Parasolid option turned ON,
the resulting geometry format will be Parasolid. Use this form to select the types of entities
included in the imported database and to direct the handling of the imported entities.
select.
Type represented in the database (simply trimmed or general trimmed).
Group Brings up a dialog box in which you specify group assignments
Classification... for imported entities.
Sew Sheet Bodies
CHAPTER 4 1
Working with Files

when a Pro/ENGINEER file is imported. This file will be
assigned a .xmt_txt file name extension.
Import Options for Pro/ENGINEER

If you are importing a Pro/ENGINEER model with the Import to Parasolid toggle turned OFF,
use this form to select the types of entities included in the imported database, as well as set an
option for accessing and loading the model.
PART 2
Basic Functions
Import Preferences Activates a dialog box in which you can specify how certain
geometric entities will be represented in the MSC.Patran
database.
Entity Types Identifies the classes of geometric entities from which you can
select.
Surface Types Lists the kinds of surfaces available for selection if the Entity
Type you picked is Solid or Surface.
3 Model Access These options are coupled with the File Type selection (in the
Options 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
MSC.Patran database.
❏ Save Geometry File (.geo)--create an intermediate (.geo) file
❏ Load Database-- import data into MSC.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 each component part
• each .geo file created from a single part--one group is
created for the part.
MSC.Patran ProENGINEER Intermediate .geo File (Primitive Geometry)

MSC.Patran ProENGINEER creates and uses an intermediate ASCII (text) formatted file (with
the assigned extension of .geo) to temporarily store Pro/ENGINEER geometric data of a part or
assembly file. MSC.Patran ProENGINEER uses the .geo file to load the accessed geometry into
an open MSC.Patran database. The format of this file is used only by MSC.Patran ProENGINEER
and it is not compatible with any other MSC.Patran product or process.
CHAPTER 4 1
Working with Files
Pro/ENGINEER File Types and Model Access Options
Pro/ENGINEER Model Access

Result of Setting Combination
File Type Option
Part Load Database Apply these two selections together to:
• run Pro/ENGINEER
• create the intermediate .geo file
• load the geometry into the
MSC.Patran database
• delete the .geo file.
Part Save Geometry File Apply these two selections together to:
(.geo)
Load Database
• load the geometry into the
MSC.Patran database
• save the .geo file.
Part Save Geometry File Apply these two selections together to:
(.geo)
• not load the geometry
Primitive Save Geometry File Apply these two selections together to:
Geometry (.geo)
• not run Pro/ENGINEER (the .geo
Load Database file has already been created)
Create Groups from • load the geometry from the .geo
Parts file into the MSC.Patran database
• if an Assembly, create groups from
parts
Executing MSC.Patran ProENGINEER From Pro/ENGINEER (p3_proe)

MSC.Software Corporation provides a script file called p3_proe that allows you to start up
Pro/ENGINEER and access MSC.Patran ProENGINEER through Pro/ENGINEER’s internal
menus (for more information, see Accessing Geometry Using MSC.Patran ProENGINEER
(p. 55) in the MSC.Patran Reference Manual, Part 2: Geometry Modeling).
PART 2
Basic Functions
Importing MSC.GS-Mesher Meshes from a Pro/ENGINEER Model

Selecting the mesh icon on the Pro/ENGINEER Import form runs MSC.GS-Mesher to create a
mesh that can be imported into MSC.Patran.
where MSC.Patran 2003 is installed: Pro/ENGINEER 2000i2-2001, MSC.GS-Mesher 2002v2, and
MSC.Nastran Preference.
Geometry Import Selecting the mesh icon runs MSC.GS Mesher on a

Icons Pro/ENGINEER model to create and import a mesh.
current.
CHAPTER 4 1
Working with Files

meshing process.
being imported.
PART 2
Basic Functions
Importing CADDS 5 Files

In the Import dialog box, select CADDS 5 as the source of the imported model database.
current.
CADDS 5 Activates the CADDS 5 Import Options form that enables you
Options to select the type and attributes of entities targeted for import.
CHAPTER 4 1
Working with Files
Import Options for CADDS 5

In this form you can select the types and attributes of entities included in the imported database.
database.
select.
All Layers If ON, all entities are import candidates, regardless of layer
assignment.
Layer Numbers Turn All Layers OFF and enter the layers on which the
entities reside.
PART 2
Basic Functions
CADDS 5 Group Classification

One or several MSC.Patran groups may be created to accommodate imported
CADDS 5 model entities. Group membership may be based on both entity type and layer
assignment.

Group Entity Types Select the type of imported geometric entities to add to the
group.
Group Entity Layers • All--selects all entities regardless of layer assignments.
• Layer numbers--turn All Layers off and enter the
layer(s) where the imported entities reside in the
CADDS 5 database.
Show CADDS 5 Display all groups defined for imported CADDS 5 entities.
Groups
Delete CADDS 5 Delete groups defined for imported CADDS 5 entities.
Groups
CHAPTER 4 1
Working with Files
Importing Unigraphics Files

In the Import dialog box, select Unigraphics as the source of the imported model database.
Unigraphics uses Parasolid to define geometry, however, Parasolid is also part of the geometric
kernel of MSC.Patran. Consequently, there is no need for translation when Unigraphics files are
transmitted into MSC.Patran.
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.
will be placed. If a non-existent group name is entered, a new
group with this name will be created and made current.
Unigraphics Activates the Unigraphics Import Options form that enables
Options you to select the type and attributes of entities targeted for
import.
Transfer Method • Direct Parasolid--Unigraphics creates a parasolid
transmit file (with the extension .xmt_txt), then that file
is imported into the MSC.Patran database.
• Express Translation--an express neutral file is created
and imported.
PART 2
Basic Functions
Unigraphics Import Options for Direct Parasolid

In this dialog box you can select the types and attributes of entities included in the imported
database
All Layers If ON, all entities are import candidates, regardless of layer assignment.
Layer Numbers Turn All Layers OFF and enter the layers on which the entities reside.
Type in the database (default is general trimmed, optionally you can change to
simply trimmed).
Attribute Import Displays the Attribute Import dialog box with options for importing
Unigraphics attributes.
CHAPTER 4 1
Working with Files
Assembly Import If Preview Components is ON, a dialog box will display the names of
the components in a Unigraphics assembly model. This list can be used
to selectively import assembly components.
Sew Sheet Bodies
• Unigraphics If Unigraphics Sew is ON, Unigraphics Sheet Bodies will be modified
Sew on import to enable Unigraphics Sewing software to equivalence or sew
together adjacent edges of the sheets. This is to avoid “cracks” along
adjacent surface edges.
• Verify The Verify Boundary command is similar to the
Boundary Verify/Surface/Boundary command in MSC.Patran.
Equivalence Edge If this toggle is ON, topological vertices will be equivalenced during
Vertices import.
Save Transmit If this toggle is ON, the parasolid transmit file will be saved when a
File 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 MSC.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.
PART 2
Basic Functions
Unigraphics Group Classification

One or several MSC.Patran groups may be created to accommodate imported Unigraphics
model entities. Group membership may be based on both layer assignment and entity type.

Group Entity • All--selects all entities regardless of layer assignments.
Layers
• Work Layer--selects entities from the currently active
layer.
• Layer numbers--turn All Layers OFF and identify
Unigraphics database.
Show Ug Display all groups defined for imported Unigraphics entities.
Groups...
Delete Ug Delete groups defined for imported Unigraphics entities.
Groups...
CHAPTER 4 1
Working with Files
Unigraphics Import Options for Express Translation

In this dialog box you can select the types and attributes of entities included in the database
imported via the Unigraphics express translation method.
database.
Entity Types Identifies the types of geometric entities from which you can
select.
Entity Layers • All--selects all entities regardless of layer assignments
layer
• Layer numbers--enter layer(s) where the imported
entities reside
PART 2
Basic Functions
Unigraphics Group Classification for Express Translation

One or several MSC.Patran groups may be created based on both entity type attributes.

Group Entity • All--selects all entities regardless of layer assignments
Layers
layer
Unigraphics database
Show Ug Groups... Display all groups defined for imported Unigraphics entities.
Delete Ug Groups... Delete groups defined for imported Unigraphics entities.
CHAPTER 4 1
Working with Files
Importing Parasolid (xmt) Files

Another way of importing a Unigraphics model is to use Parasolid xmt as the source of direct
import. This file can also originate from any system using Parasolid as its geometry kernel.
current.
Parasolid xmt Activates the Parasolid xmt Import Options form that enables
Options you to select the type and attributes of entities targeted for
import.
PART 2
Basic Functions
Import Options for Parasolid

In this dialog box you can select the types and attributes of entities included in the database.
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.
select.
assignment.
Layer Numbers Turn All Layers OFF and enter the layers on which the
entities reside.
CHAPTER 4 1
Working with Files

Type represented in the database (default is general trimmed,
optionally you can change to simply trimmed).
Model Units Displays the Model Units form in which you specify the
modeling units for the parasolid model.
Sew Sheet Bodies
• Patran Sew If MSC.Patran Sew is ON, Unigraphics Sheet Bodies will be
equivalenced or sewn together using MSC.Patran Sewing
software.

PART 2
Basic Functions
Parasolid Model Units

Parasolid assumes model units in meters, and has an overall model size limit of a 1000 meter
cube. In the Model Units form you can override the default units in the transmit file to either
inches, millimeters, or a custom unit (default is None, meaning no override). If a custom value is
desired, a scale factor entered into the databox will be used to calculate the appropriate unit
value.
Importing ACIS (sat) Files

Geometry models from ACIS-based CAD systems can be imported directly into MSC.Patran.
CHAPTER 4 1
Working with Files
CAD geometry is first exported in “sat” format, next. MSC.Patran creates a Parasolid transmit
(.xmt_txt) file from that, finally the transmit file is imported through the Parasolid import
function.
current.
ACIS Options Activates the ACIS Import Options form that enables you to
select the type and attributes of entities targeted for import.
ACIS access in MSC.Patran is based on ACIS® 11.0 Geometric Modeler and Parasolid® Version
14.1. A summary of features and limitations follows.
Converting ACIS Entities to Parasolid Entities
ACIS Parasolid Entity

Remarks
Entity Classes (PK entity types)
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 If ellipse is not circular
PART 2
Basic Functions
PLANE PK_PLANE_t
CONE PK_CYL_t If cone is cylindrical
CONE PK_CONE_t If cone is not cylindrical
CONE PK_BCURVE_t If cone is elliptical
SPHERE PK_SPHERE_t
TORUS PK_TORUS_t
3
Spline Curves
exact_int_cur PK_BCURVE_t Exact bspline curve
All other kinds PK_BCURVE_t The corresponding edges may
(e.g. surf_int_cur, be tolerant in Parasolid.
int_int_cur, ...)
Spline surfaces
exact_spl_sur PK_BSURF_t Exact bspline surface
offset_spl_sur PK_OFFSET_t Offset surface
All other kinds PK_BSURF_t The corresponding edges may
(e.g. pipe_spl_sur, be tolerant in Parasolid
skin_spl_sur ...)
CHAPTER 4 1
Working with Files
Import Options for ACIS

In this dialog box you can select the types and attributes of entities included in the database.
Group Classification Displays a dialog box in which you specify group assignments for
imported entities.
Type in the database (default is general trimmed, optionally you can change to
simply trimmed).
Sew Sheet Bodies
• Patran Sew If MSC.Patran Sew is ON, Sheet Bodies will be equivalenced or sewn
together using MSC.Patran Sewing software.
Scale Factor Displays the Scale Factor form with ACIS file model unit information.
PART 2
Basic Functions
ACIS Group Classification

One or several MSC.Patran groups may be created to accommodate imported ACIS model
entities. Group membership is based on entity type.

Group Entity Types Select the type of imported geometric entities to add to the
group.
Show Groups Display all groups defined for imported ACIS entities.
Delete Groups Delete groups defined for imported ACIS entities.
CHAPTER 4 1
Working with Files
Importing STEP Files

ISO 10303 STEP (Standard for the Exchange of Product Model Data) is the standard that
provides a complete, unambiguous definition of the physical and functional characteristics of a
product throughout its life cycle. The standard has been created by a team of international
experts from disciplines such as aerospace, automotive, shipping, process plants,
CAD/CAE/CAM, academia, and government.
STEP Application Protocols (AP) AP203 and AP209 are used to support the design/analysis
integration problem, typified by a requirement to share and exchange version controlled
geometric shape and associated analysis information in an iterative environment. AP203
provides geometry and configuration controlled design data, and AP209 extends this to include
analysis (FEM/FEA) and composites.
A variety of existing standards have been widely used as a means to exchange geometry data
and FEM data between various companies and commercial software products (both CAD and
CAE), including IGES for geometry (curves and surfaces only). However, today’s product
designs and procedures require far more information than can be captured individually and
independently. Fully associated and version controlled configuration management, product
structure, geometry (including both nominal and idealized shapes, as well as solids), finite
element model (FEM) and finite element analysis (FEA) results data must now be shared and
exchanged between CAD/CAE products and environments. STEP AP203 and AP209 standards
are capable of capturing this expanded data coverage requirement.
For additional information about STEP AP203 on the World Wide Web, see
http://pdesinc.aticorp.org. For additional information about STEP AP209 on the World Wide
Web, see http://pdesinc.aticorp.org/pilots/engineering.html.
Benefits. The ability to design, simulate and collaborate on a product model in an extended
enterprise of many companies and engineering disciplines requires a standard for describing
both geometry data (AP203 and AP209) and FEM/FEA simulation data (AP209). The STEP
standards supported by MSC.Patran provide the following extended import/export/archiving
benefits:
• Support for Solids (B-rep) export. Previously, only IGES export of geometry was
available, which does not support solids.
• Support for SDRC geometry import (including solids) via STEP. Previously, only IGES
import of geometry was available.
• Provides a standard-based mechanism to exchange CAD/CAE data between
engineering companies with different CAD/CAE processes/tools.
• Provides a standard for long term CAD/CAE data archiving.
• Provides for the import/export of CAD generated configuration management and
product structure information (STEP defined minimum subset) associated with the
geometry imported into MSC.Patran. Additionally, AP209 provides for analysis
version control, which is fully associated with design version control.
Accessing STEP Libraries. STEP import and export is developed as an independent shared
library, and is not included on the Version 9 CD. Future major releases of MSC.Patran will have
STEP included on the CD.
Downloading and Installing. The STEP libraries are available from the MSC.Mechanical
Solutions Web site. The following support URL will contain the link to download instructions:
http://www.mechsolutions.com/support/software_updates/
PART 2
Basic Functions
For more information on STEP support availability, visit the MSC.Mechanical Solutions Web site
at: www.mechsolutions.com.
Licensing. STEP AP203 requires an MSC.Patran STEP AP203 Access license. STEP AP209
requires an MSC.Patran STEP AP209 Access license. For more information, contact your
MSC.Software account representative.
In the Import dialog box, select STEP as the source of the imported database.
current.
STEP 203/209 Brings up the STEP 203/209 Import Options form that enables
you to select the type and attributes of entities targeted for
import.
Import to Parasolid Converts STEP geometry into Parasolid geometry format.
File Type Specifies the type of the imported input file. This may be a
STEP 203 or STEP 209 file.
CHAPTER 4 1
Working with Files
STEP Entities Supported for Import

Presently, only the MSC.Nastran Preference in MSC.Patran is supported for the FEM/FEA data
imported from or exported to AP209 files.
Imported STEP Conformance Class 1 data (minimum subset of configuration management,
product structure, approvals, etc.) associated with imported geometry, is maintained and
replicated for STEP file 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 MSC.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.
PART 2
Basic Functions
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 MSC.Patran and all the assembly instances are duplicated.
3 • Group based Assembly import is supported.
• Names of Geometric Entities are preserved using CATIA CAD association.
Class 1: Configuration Management Entities (Minimum Subset)

APPLICATION_CONTEXT
APPLICATION_CONTEXT_ELEMENT
APPLICATION_PROTOCOL_DEFINITION
APPROVAL
APPROVAL_DATE_TIME
APPROVAL_PERSON_ORGANIZATION
APPROVAL_ROLE
APPROVAL_STATUS
CALENDAR_DATE
ORDINAL_DATE
WEEK_OF_YEAR_AND_DAY_DATE
APPLIED_CC_DESIGN_APPROVAL
APPLIED_CC_DESIGN_DATE_AND_TIME_ASSIGNMENT
APPLIED_CC_DESIGN_PERSON_AND_ORGANIZATION_ASSIGNMENT
APPLIED_CC_DESIGN_SECURITY_CLASSIFICATION
COORDINATED_UNIVERSAL_TIME_OFFSET
DATE_AND_TIME
DATE_TIME_ROLE
LOCAL_TIME
PRODUCT_CONTEXT( or MECHANICAL_CONTEXT )
ORGANIZATION
PERSON
PERSON_AND_ORGANIZATION
PERSON_AND_ORGANIZATION_ROLE
PRODUCT
PRODUCT_CATEGORY
PRODUCT_DEFINITION
PRODUCT_DEFINITION_CONTEXT (or DESIGN_CONTEXT)
PRODUCT_DEFINITION_FORMATION_WITH_SPECIFIED_SOURCE
PRODUCT_DEFINITION_RELATIONSHIP
PRODUCT_DEFINITION_SHAPE
PRODUCT_RELATED_PRODUCT_CATEGORY
PROPERTY_DEFINITION
SECURITY_CLASSIFICATION
SECURITY_CLASSIFICATION_LEVEL
NEXT_ASSEMBLY_USAGE_OCCURRENCE
SHAPE_REPRESENTATION
SHAPE_DEFINITION_REPRESENTATION
SHAPE_ASPECT
CHAPTER 4 1
Working with Files
Class2: Geometrically Bounded Surface Shape Representation

Mapped Item
Axis2_Placement_3d
B_spline surface
Rectangular Trimmed Surface
Curve Bounded Surface
Spherical, Toroidal Surface
Swept Surface
Circle, Ellipse
Trimmed Curve
Composite Curve
Curve Replica, Offset Curve 3d, Offset Curve 2d, SeamCurve
Surface Curve
Boundary Curve, Outer Boundary Curve, Composite Curve Segment
Class 2: Geometrically Bounded Wireframe Shape Representation

Geometric Curve Set
Axis2_Placement_3d
Points
Circle
Ellipse
Polyline
Trimmed curve
Class 3: Edge Based Wireframe Shape Representation

Edge Based Wireframe Model
Axis2_Placement_3d
Edge Curve
Vertex Point
Line, Circle, Ellipse, B_Spline_Curve
Parabola, Hyperbola
Vertex Geometry (only cartesian point supported)
Class 3: Shell Based Wireframe Shape Representation

Shell Based Wireframe Model
Axis2_Placement_3d
Edge Loop
Edge Curve
Line, Circle, Ellipse, B_Spline_Curves
Vertex Geometry (only cartesian point supported)
PART 2
Basic Functions
Class 4: Manifold Surface Shape Representation

Shell Based Surface Model
Axis2_Placement_3d
Open shell, Closed Shell
Connected Face Set, Face Surface, Oriented Face
Elementary Surfaces
Spherical, Conical, Toroidal, Plane, Cylindrical
Bounded Surfaces
3 B_Spline_Surfaces
Swept Surface
Surface of Linear Extrusion
Edge loop
Edge Curve
Parabola, Hyperbola, SeamCurve
Class 5: Faceted B-Rep Shape Representation

Faceted Brep
Axis2_Placement_3d
Face_Surface
Planar Surfaces
Edge Loop
Edge Curves
Parabola, Hyperbola, SeamCurve
CHAPTER 4 1
Working with Files
Class 6: Advanced B-Rep Shape Representation

Manifold Solid Brep
Next Assembly Usage Occurrence
Mapped Item
Axis2_Placement_3d
Brep with voids
Advanced Face
Swept Surface
Surface of Linear Extrusion
Surface of Revolution
Edge Loop
Edge Curve
Oriented Edges
B_spline_surface_with_knots
Rational_bspline_surface
Cylindrical surface
Conical Surface
Toroidal Surface
Plane
Quasi uniform surface
Line
Circle
Uniform Surface
Uniform Curve
Ellipse
B spline curve with knots
Quasi uniform curve
Rational bspline curve
Bezier Surface and Curve
Spherical Surface
Parabola, Hyperbola
Seam Curve
PART 2
Basic Functions
Supported AP209 Import Entities

AP209 is a major Application Protocol of STEP (ISO 10303) for composite and metallic structural
analysis and related design. The MSC.Patran AP209 translators (both import and export)
support three major CAD/CAE data types:
• Geometry (nominal shape and idealized shape)
• FEM/FEA (linear static and modes/eigenvectors)
• Configuration Management data
3 Currently, AP209 support is for the MSC.Nastran Preference only. Specific coverage provided in
this release is listed below.
Entities Features
Geometry Geometry data comprising Curves, Surfaces and Solids are exported,
imported, from geometrically bounded surface shape representations
and/or advanced-Brep shape representations. Assemblies are also
supported. Association of Geometry data to Configuration Management
data is maintained when exported. AP209 translation supports all of the
AP203 geometry types.
Configuration Support for Configuration Management data conforming to agreed
Control Data upon STEP minimum subset.
FEM/FEA Data Support for import and export of nodes in the global coordinate system.
Nodes
Elements Support for the following Element types:
Volume Elements:
Hexahedral elements:
HEX8, HEX9, HEX20, HEX21, HEX26, HEX27, HEX32&HEX64
Pentahedral elements:
WEDGE6, WEDGE15 & WEDGE24
Tetrahedral elements:
TET4,TET10&TET16
Surface Elements:
Quadrilateral elements:
QUAD4,QUAD5,QUAD8, QUAD9,QUAD12&QUAD16
Triangular elements:
TRI3,TRI4,TRI6&TRI9
Curve Elements:
BAR2,BAR3&BAR4
Materials Support for Isotropic, Orthotropic and Anisotropic Materials with linear
constituent model.
CHAPTER 4 1
Working with Files
Entities Features
Regions 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.
Loads and Point Loads: At Nodal positions.
Boundary Pressure Loads: Element Uniform and Element Varying Pressure Loads
Conditions are supported for loads applied on faces of Volume Elements and
(LBCs) and Surface Elements.
MPCs Distributed Loads: Element Uniform and Element Varying Distributed
Loads are supported for loads applied on Curve Elements.
Single Point Constraints: Nodal Displacements.
Multi Point Constraints: Only Explicit MPCs are supported.
Support for constant value LBCs.
LBCs: Associated with at least one Load Case are only exported.
Load Cases Load Cases which have at least one of the supported LBCs are exported.
Output Support for Multiple Jobs.
Requests 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.
PART 2
Basic Functions
Import Options for STEP AP203 Parasolid Format

If you are importing a STEP AP203 model with the Import to Parasolid option turned ON, the
select.
trimmed).
Sew Sheet Bodies
CHAPTER 4 1
Working with Files

when a STEP file is imported. This file will be assigned a
Import Options for STEP AP203

The STEP AP203 Access Filter appears when importing a STEP AP203 model with the Import to
Parasolid toggle turned OFF. Use this form to access entities based on a combination of entity
type and the layer on which entities reside.
select.
assignment.
Layer Numbers Turns All Layers off. Enter the layers where the entities you
want to import reside.
PART 2
Basic Functions

Load CCI Data If ON, loads Configuration Control Data (Class 1).
3 value for “Geometry Scale Factor.”
Sew Sheet Bodies Instructs MSC.Patran to sew together sheet bodies using
MSC.Patran software.
Load CCI Data If ON, loads Configuration Control Data (Class 1).
Import Options for STEP AP209

The STEP AP209 Access Filter allows the access of entities based on a combination of entity type
and the layer on which entities reside.
CHAPTER 4 1
Working with Files
database.
select.
assignment.
Layer Numbers Turns All Layers off. Enter the layers where the entities you
want to import reside.
Imported Data Use this pull-down list to select the types of data you wish to
import.
PART 2
Basic Functions
STEP AP209 Import Preferences


trimmed).
solids.
Import Action
Geometry
CHAPTER 4 1
Working with Files
STEP AP203/AP209 Group Classification

One or several MSC.Patran groups may be created to accommodate imported STEP model
entities. Group membership may be based on both entity type and layer assignment.

Group Entity • All--selects all entities regardless of layer assignments
Layers
Unigraphics database
Show Groups... Display all groups defined for imported STEP entities.
Delete Groups... Delete groups defined for imported STEP entities.
PART 2
Basic Functions
Importing STL Files

In the import dialog box, select STL as the source of the imported database.
current.
STL Options Brings up the STL Import Options form that enables you to
CHAPTER 4 1
Working with Files
STL Import Options

In this form you can select the entity types (packets) you want to import.

exists (e.g., when several neutral files are imported). It will
activate the Entity Label Offset Definition form in which
you can specify offsets to avoid conflicting IDs.
PART 2
Basic Functions
Entity Label Offset Definition

numbers.

Assigning Offsets
• pick Automatic Offset to let the system assign offset automatically.
CHAPTER 4 1
Working with Files
Importing VDA Files

In the import dialog box, select VDA as the source of the imported database.
current.
VDA Options Brings up the VDA Import Options form that enables you to
PART 2
Basic Functions
VDA Import Options

The filter for VDA allows the access of entities based on a combination of entity type and the
layer on which entities reside.
select.
Type represented in the database (default is general trimmed,
optionally you can change to simply trimmed).
Sew Sheet Bodies
• Patran Sew If MSC.Patran Sew is ON, Unigraphics Sheet Bodies will be
equivalenced or sewn together using MSC.Patran Sewing
software.
CHAPTER 4 1
Working with Files


when a STEP file is imported. This file will be assigned a
PART 2
Basic Functions
Model Units
Parasolid assumes model units in meters, and has an overall model size limit of a 1000 meter
cube. In the Model Units form you can override the default units in the transmit file to either
inches, millimeters, or a custom unit. If a custom value is desired, a scale factor entered into the
databox will be used to calculate the appropriate unit value.
The default Model Unit Override value is None for:

• Unigraphics
• Parasolid xmt
CHAPTER 4 1
Working with Files
The default Model Unit Override value is the Patran Preference value for “Geometry Scale factor
for:
• “Import to Parasolid”
CATIA
Pro/ENGINEER
STEP AP203
• I-DEAS
• ACIS
• VDA
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 MSC.Patran formats.
Format Select the format of the imported results file.

Current Analysis Indicate the current analysis code preference.
Code
Zero Tolerance Specify a tolerance value; a result with the absolute value less
than this value will be considered equal to zero.
PART 2
Basic Functions
Template for PATRAN 2.5 Import Results

This window appears if the selected format is one of the PATRAN 2 files (see Patran 2.5 Results
Files (p. 40) for more information about result files).
3
CHAPTER 4 1
Working with 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, formatted as IGES files,
Parasolid xmt files, or 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.
PART 2
Basic Functions
Neutral Export Options

In this dialog box you can select the entity types (packets) and groups that are to be output via
the PATRAN 2.5 neutral file.
Neutral File Title Activates the Neutral File Title form to enter a title for your
file.
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.
CHAPTER 4 1
Working with Files
Neutral File Title

Accept the default or enter a new title; this will become a Neutral File Title Card (Packet Type
25).
Exporting IGES Surface Data as Parametric BiCubic Surfaces

The “Patran 2 Neutral File Translator” can export IGES type 114 and 128 surfaces as “Parametric
BiCubic” surfaces. For example, the “Patran 2 Neutral File Translator” automatically converts an
IGES 128 surface entity into a “BiCubic Patch Network”, and then exports a Patran Neutral File
that contains the individual patches (Parametric BiCubic Surfaces) that make up the Patch
Network.
To convert existing IGES surface data into Parametric BiCubic Patches, you need to first import
an IGES file into MSC.Patran, and then either:
• Turn ON the “Exportable to Neutral File” Geometry Preference and interactively refit the
IGES 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 by selecting File>Export and setting the Format option to “Neutral”.
PART 2
Basic Functions
Exporting a Parasolid Transmit File

To export database entities to an Parasolid Transmit file, select Parasolid xmt format in the
Export dialog boxes.
File Name/Type Enter a new file name. The default file name extension is .xmt.
Format Select Parasolid xmt to create an output file.
Parasolid xmt Activates the Parasolid xmt Options dialog box in which you
Options select exported entities and groups.
CHAPTER 4 1
Working with Files
Parasolid xmt Export Options

In this dialog box you can select the entity types (packets) and groups that are to be output via
the Parasolid xmt file.
Entity Types Displays the names of all entity types that are candidates for
export. Select the packet(s) to send to the output file.
Parasolid Version for Select the version for export.
Export
PART 2
Basic Functions
Exporting to IGES Files

To export database entities to an IGES file, select IGES format in the Export dialog box.
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 Select IGES to create an output file in IGES format.
IGES Options Activates the IGES Export Options dialog box in which you
define the IGES file sections and select exported entities and
groups.
CHAPTER 4 1
Working with Files
Geometric Entity Types and their Supported IGES Equivalents
Table 4-2
Geometric Entity Type IGES Entity Type( #)

Arc Circular Arc (100)
Parametric Cubic Circular Arc (100)
Composite Curve Composite Curve (102)
Conic Conic Arc (104)
Piecewise Linear Copious Data (106)
Point Copious Data (106)
Plane Unbounded Plane (108)
Line Line (110)
Parametric cubic Line (110)
Parametric cubic Parametric Spline Curve (112)
Piecewise cubic polynomial curve Parametric Spline Curve (112)
Cubic spline Parametric Spline Curve (112)
Rational Bezier Parametric Spline Curve (112)
MDC curve Parametric Spline Curve (112)
CATIA curve Parametric Spline Curve (112)
Piecewise rational polynomial curve Parametric Spline Curve (112)
Bicubic patch network Parametric Spline Surface (114)
Parametric Parametric Spline Surface (114)
Point Point (116)
Ruled Surface Ruled Surface (118)
Cylinder Surface of Revolution (120)
Cone Surface of Revolution (120)
Torus Surface of Revolution (120)
Surface of revolution Surface of Revolution (120)
Tabulated cylinder Tabulated Cylinder (122)
Bounded plane Tabulated Cylinder (122)
Coordinate system 124
Type 1 - Rectangular Form 10 - Cartesian
Type 2 - Cylindrical Form 11 - Cylindrical
Type 3 - Spherical Form 12 - Spherical
Nurb curve Rational B-Spline Curve (126)
Nurb surface Rational B-Spline Surface (128)
Rational Bezier network Rational B-Spline Surface (128)
MDC surface Rational B-Spline Surface (128)
MDC parent surface Rational B-Spline Surface (128)
Fillet surface Rational B-Spline Surface (128)
Generalized Coons surface Rational B-Spline Surface (128)
Cylindrical Spline surface Rational B-Spline Surface (128)
CATIA surface Rational B-Spline Surface (128)
PART 2
Basic Functions
Table 4-2 (continued)
Geometric Entity Type IGES Entity Type( #)

Piecewise rational polynomial surface Rational B-Spline Surface (128)
Curve interpolating surface Rational B-Spline Surface (128)
Extruded surface Rational B-Spline Surface (128)
Glide surface Rational B-Spline Surface (128)
Sweep normal surface Rational B-Spline Surface (128)
3 Sphere Rational B-Spline Surface (128)
MDC sculptured surface Rational B-Spline Surface (128)
Parametric tricubic Rational B-Spline Surface (128); 1 per face
Ordinary body Rational B-Spline Surface (128); 1 per face
Surface interpolating solid Rational B-Spline Surface (128); 1 per face
Solid of revolution Rational B-Spline Surface (128); 1 per face
Solid 6face Rational B-Spline Surface (128); 1 per face
Extruded solid Rational B-Spline Surface (128); 1 per face
Glide solid Rational B-Spline Surface (128); 1 per face
Sweep normal solid Rational B-Spline Surface (128); 1 per face
Extruded body Rational B-Spline Surface (128); 1 per face
Tricubic net Rational B-Spline Surface (128); 1 per face
Offset curve Offset Curve (130)
Node Node (134)
Finite Element Finite Element (136)
Offset surface Offset Surface (140)
Trimmed surface Trimmed Surface (144)
Ordinary trimmed surface Trimmed Surface (144)
CHAPTER 4 1
Working with Files
IGES Export Options
Start Section Displays the IGES File Start Section form.

Global Section Displays the IGES File Global Section dialog box.
Entity Types Displays the names of all entity types that are candidates for
export. Select the entities to send to the output file.
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.
IGES Point Type Specify what IGES point type will be created from
MSC.Patran points.
PART 2
Basic Functions
IGES File Start Section

In this form you can enter any text to serve as an introduction to the IGES export file. Optionally,
you may accept the default text.
IGES File Global Section Parameters

In this dialog box you enter certain file parameters. All default values may be modified.
CHAPTER 4 1
Working with Files
Exporting to STEP Files

To export database entities to an STEP file, select STEP format in the Export dialog box.
STEP 203/209 Options Brings up the STEP 203/209 Export Options form that enables
you to select the type and attributes of entities targeted for
export.
Export Through Specifies the type of the exported output file. This may be a
Parasolid File Type STEP 203 or STEP 209 file.
PART 2
Basic Functions
Supported AP203 Export Entities

• Curves, Surfaces, and Solids.
• Name of imported Geometric entities preserved using CATIA CAD association.
• Exports MSC.Patran Geometry entities as either Class 2: Geometrically bounded
surface shape representation, or Class 6: Advanced B-Rep shape representation.
• All imported Class 1: Configuration Management data and its associations to
geometry.
3
CHAPTER 4 1
Working with Files
Supported AP209 Export Entities

AP209 is a major Application Protocol of STEP (ISO 10303) for composite and metallic structural
analysis and related design. The MSC.Patran AP209 translators (both import and export)
support three major CAD/CAE data types:
• Geometry (nominal shape and idealized shape)
• FEM/FEA (linear static and modes/eigenvectors)
• Configuration Management data
Currently, AP209 support is for the MSC.Nastran Preference only. Specific coverage provided in
this release is listed below.
Entities Features
Geometry Geometry data comprising Curves, Surfaces and Solids are exported,
imported, from geometrically bounded surface shape representations
and/or advanced-Brep shape representations. Assemblies are also
supported. Association of Geometry data to Configuration Management
data is maintained when exported. AP209 translation supports all of the
AP203 geometry types.
Configuration Support for Configuration Management data conforming to agreed
Control Data upon STEP minimum subset.
FEM/FEA Data Support for import and export of nodes in the global coordinate system.
Nodes
Elements Support for the following Element types:
Volume Elements:
Hexahedral elements:
HEX8, HEX9, HEX20, HEX21, HEX26, HEX27, HEX32&HEX64
Pentahedral elements:
WEDGE6, WEDGE15 & WEDGE24
Tetrahedral elements:
TET4,TET10&TET16
Surface Elements:
Quadrilateral elements:
QUAD4,QUAD5,QUAD8, QUAD9,QUAD12&QUAD16
Triangular elements:
TRI3,TRI4,TRI6&TRI9
Curve Elements:
BAR2,BAR3&BAR4
Materials Support for Isotropic, Orthotropic and Anisotropic Materials with linear
constituent model.
PART 2
Basic Functions
Entities Features
Regions 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
3 Constant and Non-structural Mass.
Beam Cross Section Geometry and Beam Property Association.
Properties related only to MSC.Nastran Preference are currently
supported.
Loads and Point Loads: At Nodal positions.
Boundary Pressure Loads: Element Uniform and Element Varying Pressure Loads
Conditions are supported for loads applied on faces of Volume Elements and
(LBCs) and Surface Elements.
MPCs Distributed Loads: Element Uniform and Element Varying Distributed
Loads are supported for loads applied on Curve Elements.
Single Point Constraints: Nodal Displacements.
Multi Point Constraints: Only Explicit MPCs are supported.
Support for constant value LBCs.
LBCs: Associated with at least one Load Case are only exported.
Load Cases Load Cases which have at least one of the supported LBCs are exported.
Output Support for Multiple Jobs.
Requests 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.
CHAPTER 4 1
Working with 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 Plays back the session file one line at a time.
Commit Commits (saves) the database before each command is
Commands executed. This prevents an Undo from canceling an entire
session file.
Stop Stops playing the session file. After stopping, this button
changes to Resume. Press Resume to continue playing the
session file.
Effect of “Undo” in Session Files

When commands are canceled by Undo, the corresponding lines in the session file are deleted
and an undo message is recorded. The built-in commit (LOGICAL) determines if each command
played from a session file is committed. If FALSE (default), an entire session file playback may
be undone. If TRUE, only the last session file command may be undone.
PART 2
Basic Functions
Recording a Session File

When you invoke the File>Session>Record command sequence, a new file will be created that
records all database related commands executed during the current MSC.Patran session from
the time this file was opened. The default patran.ses session file will be generated as well.
File Name/Type Enter a new file name. The extension .ses will be added
automatically.
Record Rotations Records each incremental rotation of your model in the
session and journal files.
Stop Stops recording the session file. After stopping, this button
changes to Resume. Press Resume to continue recording the
session file.
CHAPTER 4 1
Working with Files
File>Print Printing MSC.Patran Images
The File>Print command sequence will send MSC.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 MSC.Patran options exist that allow you certain control over the printed
output.
Printing on Windows NT
Print From Select Viewport(s) and/or XY Window(s) to print. You can

print one or several viewports and windows on the same
page. Invalid options are disabled (e.g., if there are no XY
Windows posted, the Current XY Window option will be
disabled).
One Viewport If this toggle is ON, only a single viewport will be printed on
per page a page.
Print to File Toggle this ON if you do not wish to print immediately but
want to save the output to a file for later use. The following
form will be superimposed on the Print dialog box, listing the
available print file options.
PART 2
Basic Functions
Postscript Files
3 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 Choices Description

Format Black to White Converts spectrum colors to a black-to-white range.
The range starts at 90% black and decreases to 5%
black. Shaded colors are converted from RGB (Red-
Green-Blue) to gray.
White to Black Converts spectrum colors to a white-to-black range.
Shaded colors are converted from RGB to gray.
Color Color output is created with either an RGB or CMYK
color model.
Background White Background is white.
Black Background is black.
Actual Background is printed with the actual color. Color is
controlled by the Format option.
Lines & Text White Lines and Text are white.
Black Lines and Text are black.
Actual Lines and Text are printed with the actual color. Color
is controlled by the Format option.
Line Weight 0.5 pts The Line Weight correlates a one-pixel line width on
the screen to the line width on output. Most lines are
one pixel wide. XY plot curves, however, can be of
varying line thickness. Markers are drawn with half
of the Line Weight.
Unit may be inch, cm, mm, pica, or point. If no unit is
supplied, inches are assumed
(1 inch = 6 picas; 1 inch = 72 points).
Text Scale 100% Text scale and image scale may be independent of one
another. Both “%” and “percent” are supported. If
“None” is entered instead of a percentage, all text will
be deleted.
CHAPTER 4 1
Working with Files

Image Size Fit on Page The image is scaled so that it fits inside the margins of
the selected Paper Size. Scaling is proportional and
the image is optionally centered.
As Is The image is printed at the same size as shown on the
screen. It is optionally centered.
Center Yes The image is centered on the page. The centering area
is (page size) - (margins). Centering is performed after
scaling, if any.
No The image is placed in the upper left corner of the
page. Left is relative to a rotation generated by the
Orientation selection.
Draw Yes Draw a border around the image that represents the
Borders edge of the viewport or the XY window.
No Do not draw the border.
Encapsulated Postscript (EPS) Files

The purpose of creating Encapsulated Postscript Files is to place them in a document that you
want to print at a later time. In the document, EPS files can be scaled, rotated, or clipped. Typical
applications that utilize these files are word processors and page layout programs. Unlike
postscript files, EPS files cannot be sent to a printer directly.
EPS files created by MSC.Patran are text files, therefore they can be transferred easily between
various operating systems. There are file naming conventions, however, that must be followed.
PC programs will recognize files with the suffix .eps as Encapsulated Postscript Files and will
display them in file selection menus presented when graphic images are placed. Note that the
suffix is not case sensitive.
Macintosh programs will also recognize files with the suffix .EPS as Encapsulated Postscript
Files, provided that the Macintosh File Type is “TEXT.” This usually happens as a byproduct of
transferring files to a Macintosh. The EPS file can be arbitrarily named if the File Type is “EPSF.”
The File Type can be changed with a Resource Editor or certain Disk Utilities. Note that the File
Type is case sensitive. The suffix is not.
PATRAN EPS files do not contain a “preview.” Therefore, a gray box will appear when the EPS
file is placed in a document. On systems running Display Postscript, the application may
interpret the EPS file and build a preview on the fly. Although these previews are not always
precise, the file will print as expected.
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.
PART 2
Basic Functions
Printing on UNIX
For running MSC.Patran in a UNIX environment, use the Print form to generate output of your
MSC.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).
3 Print
Current Viewport
Select the Current Printer. The list of Available Printers is
defined by the Printer Configuration File (p. 194). This
Available Printers file can be system wide but is usually user specific. You
Postscript Default can set a default printer specifying the MSC.Patran
PatranHard Default environment variable primary_printer in the
CGM Default settings.pcl file. Example: pref_env_set_string
HPGL Default (“primary _printer”, “printer_name”), where printer_name
HPGL2 Default corresponds to the right hand side of the Printer variable
Patran Hard to Postcript Default defined by the Printer Configuration File (p. 194).
Device HP Laserjet 4Si

These items reflect the definition of the current
printer. You cannot change the Device or Driver on
Driver Postscript
the form, but you can change the printer’s
destination.
Destination lw11
Subordinate form appears when this button is pressed.

Page Setup... Options on this form will change with the current
printer.
Options...
Subordinate form with the Driver specific options will
appear when this button is pressed. Selections will
change with the current printer.
Apply Cancel
Will generate an output file and either spool it to the

printer or save it in the current directory.
☞More Help:
(Available Printers)
• Postscript Options (p. 184)
• PatranHard File Options
(p. 187)
• CGM Options (p. 188)
• HP-GL Options (p. 190)
• HP-GL/2 Options (p. 192)
CHAPTER 4 1
Working with Files
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
printer’s default settings every time the printer is selected from the listbox on the Print form.
Print Control
Choices change with the current printer. For
Paper Size Letter possible paper sizes see the Printer
Configuration File (p. 194).
Margins
Left 0.5 Right 0.5
Margins can be specified in the following units:
Top 0.5 Bottom 0.5 inches, cm, mm, picas and points. If no units are
specified, inches are assumed. The default
Default Units Inches margins are a function of the current printer.
Print Orientation
Print Orientation options and the default orientation

are set for each printer. Note that the margins are
relative to the orientation. That is, the Left Margin is
Number of Copies 1 on the left following the rotation (if any) of the
image.
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).
PART 2
Basic Functions
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 (p. 194). The form reverts to the printer’s default
settings every time the printer is selected from the listbox on the Print form.
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.
3
Print Control
You can control the color of the Background and
Black to White the Lines & Text independently of the Format.
Format
Valid options are White, Black and Actual.
Background White
Correlates the one pixel line width on the screen
Lines & Text Black to a line width on output. Valid units are inches,
cm, mm, picas and points. Note that there are
Line Weight 0.25 pts 6 picas per inch and 72 points per inch.
Text Scale 250%

You can scale the text independently of the
Image Size Fit on Page
image. Enter a percentage. Text can be deleted
Draw Borders Yes from the output by entering “None” in this
databox.
If Draw Borders is “Yes,” a box will be drawn

◆ Print to File around the image indicating the edge of the
◆
◆ Create EPS File viewport or XY window.
OK If the Print to File and Create EPS File toggles are

Preview
Quality Cancel
OFF, the output is spooled to the destination
shown on the main form. Otherwise, either a
postscript file or an encapsulated postscript file is
The OK button saves the choices. The Cancel
saved in the local directory. See How to Use EPS
button resets the choices to those which existed
Files (p. 186).
before the form was opened. Pressing the Apply
button in the main form causes an OK in this form
(if it is open).
“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. ☞More Help:
(p. 187)
CHAPTER 4 1
Working with Files
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 (p. 194).

Format Black to White Converts spectrum colors to a black to white range.
black. Shaded colors are converted from rgb to gray.
White to Black Converts spectrum colors to a white to black range.
Shaded colors are converted from rgb to gray.
Color Color output is created with either an RGB or CMYK
color model.
Actual Background is printed with the actual color. The
color will be controlled by the Format option.
Actual Lines and Text are printed with the actual color. The
Line Weight 0.5 pts The Line Weight correlates a one pixel line width on
the screen to a line width on output. Most lines are
one pixel wide. XY plot curves, however, can have
varying line thicknesses. Markers are drawn with
half of the Line Weight.
Units can be inches, cm, mm, picas or points. If no
units are supplied, inches are assumed. Note that
there are 6 picas per inch and 72 points per inch.
Text Scale 100% Text can be scaled independently of image scaling.
Both “%” and “percent” are supported. All text will
be deleted if “None” is entered, instead of a
percentage.
Image Size Fit on Page The image is scaled so that it fits inside the margins
of the selected Paper Size. Scaling is proportional and
is the page size less the margins. Centering is
performed after scaling, if any.
page. Remember that the left is relative to the
rotation caused by the Orientation selection.
PART 2
Basic Functions

Draw Borders Yes Draw a border around the image that represents the
edge of the viewport or XY window.
How to Use EPS Files
3 Encapsulated Postscript Files are intended to be placed in a document which will later be
printed. These files cannot be directly sent to a printer. Once placed, the EPS files can be scaled,
rotated, and clipped. Typical applications that support these files are word processors and page
layout programs.
Since the EPS files created by MSC.Patran are text files, they can be easily transferred between
various operating systems. There are file naming conventions that must be followed.
PC programs will recognize files with the suffix .EPS as Encapsulated Postscript Files. That is,
they will be visible in the file selection menus presented when graphic images are placed. Note
that the suffix is not case sensitive.
Macintosh programs will recognize files with the suffix .EPS as Encapsulated Postscript Files.
When transferring files to the Mac, the Macintosh file type must be “TEXT.” The EPS file can be
arbitrarily named if the File Type is “EPSF.” The File Type can be changed with a Resource
Editor or certain Disk Utilities. Note that the File Type is case sensitive. The suffix is not.
MSC.Patran EPS files do not contain a “preview.” Therefore, a gray box appears when the EPS
file is placed in a document. On systems running Display Postscript, the application may
interpret the EPS file and build a preview. These previews are not always precise, however, they
will print as expected.
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. Note that color EPS files placed in a document and
sent to a non-color printer will print in grayscale.
CHAPTER 4 1
Working with Files
PatranHard File 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 Color
Image resolution (dots per inch). You can control the color of the Background
Background White and the Lines & Text independently of the
Format. Valid options are White, Black and
Lines & Text Actual Actual.
Text Scale 250% You can scale the text independently of the
image. Enter a percentage. Text can be
Image Size Fit on Page deleted from the output by entering “None” in
this databox.
Draw Borders Yes
Resolution(dpi) 72 around the image indicating the edge of the
viewport or XY window.
◆ Create new .hrd file
Image resolution (dots per inch).
◆
◆ Append to existing .hrd. file
File Name: patran.hrd.01

Print to File
Filename patran.hrd
OK Cancel
“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.
☞More Help:
PART 2
Basic Functions
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 You can control the color of the

Background and the Lines & Text
3 Background White independently of the Format. Valid options
are White, Black and Actual.
Lines & Text Black

Text Scale 100 % image. Enter a percentage. Text can be
deleted from the output by entering “None”
Image Size Fit on Page in this databox.
Draw Borders Yes If Draw Borders is “Yes,” a box will be

drawn around the image indicating the edge
of the viewport or XY window.
Resolution(dpi) 72

Print to File
☞More Help:
OK Cancel (Available Printers)
“Fit on Page” scales the image so that it fits on the Paper (p. 187)
Size defined on the Page Setup form (less margins). Or the • HP-GL Options (p. 190)
image can be left unscaled (same as the size on the screen)
with the As Is option.

Color Color output is created with an RGB color model.
CHAPTER 4 1
Working with Files

percentage.
Use Scale Factor Use the Scale Factor setting. The image is optionally
centered.
Scale Factor 1.0 The Scale Factor is only used if Image Size is set to
“Use Scale Factor”. The value “1.0” means that the
output is the same size as that shown on the screen.
page. Remember that the left is relative to the rotation
caused by the Orientation selection.
Resolution 72 Choose the resolution for imaging the graphics for
hardcopy.
PART 2
Basic Functions
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

3 You can control the color of the Background and
the Lines & Text independently of the Format.
Background White Valid options are White, Black and Actual.
Lines & Text Black

image. Enter a percentage. Text can be deleted
Text Scale 100%
from the output by entering “None” in this
databox.

Draw Borders Yes
around the image indicating the edge of the
viewport or XY window.
Resolution(dpi) 72

Pen Mapping
Model No. & Version 7550A Allows specification of HP pens to be used to

represent MSC.Patran colors. For example:
0111225433333333 indicates that HP pen 0 will
Print to File be used for the background; pen 1 will be used for
MSC.Patran colors 1 through 3; HP pen 2 for
MSC.Patran colors 4 and 5; HP pen 5 for
MSC.Patran color 6; HP pen 4 for MSC.Patran
OK Cancel color 7; and HP pen 3 for MSC.Patran colors 8
through 15. (Note that for this example, 16 colors
are being mapped.)
“Fit on Page” scales the image so that it fits on the

Paper Size defined on the Page Setup form (less ☞More Help:
margins). Or the image can be left unscaled (same (Available Printers)
as the size on the screen) with the “As Is” option. • Postscript Options (p. 184)
Note: Refer to Printing on UNIX (p. 182) for a list of supported HP- (p. 187)
GL plotter model numbers, model versions and paper size. • CGM Options (p. 188)

CHAPTER 4 1
Working with Files

percentage.
Image Size Fit on Page The image is scaled so that it fits inside the margins
of the selected Paper Size. Scaling is proportional and
centered.
page. Remember that the left is relative to the
rotation caused by the Orientation selection.
hardcopy.
Pen Mapping The default mapping is color 1 to pen 1, color 2 to pen
2, and so on up to 16 pens. For example,
0111.223344447777 will map color 1 to pen 0 (no
drawing), colors 2, 3 and 4 to pen 1. Colors 5 and 6 to
pen 3, etc.
PART 2
Basic Functions
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
You can control the color of the
Format Black to White
Background and the Lines & Text
independently of the Format. Valid
3 Background White options are White, Black and Actual.
Lines & Text Black
image. Enter a percentage. Text can be
deleted from the output by entering “None” in
Text Scale 100% this databox.
Image Size Fit on Page If Draw Borders is “Yes,” a box will be drawn
around the image indicating the edge of the
Draw Borders Yes viewport or XY window.
Resolution (dpi) 72 Image resolution (dots per inch).
Pen Mapping Creates a 7-bit format file for communication

channels that cannot support 8-bit data.
Output Format 7 Bit
This option must be enabled when a HP-
GL/2 Laserjet III plotter has been specified
LaserJet III No
as the destination plotter (requires special
initialization).
Opaque Mode No
If this option is enabled, the hardcopy images
will be plotted with underlying images
Cutter Default obscured by images in front.
Rotation(deg) 0
Controls the paper cutter found on some HP-
GL/2 plotters. The Cutter Default option
allows the panel setting on the plotter to
Print to File determine if the cutter is to be used.
The plot may be rotated by specifying the

OK Cancel number of degrees: 0 (default), 90, 180 or 270
degrees.
Allows specification of HP pens to be used to represent MSC.Patran colors. For example:

0111225433333333 indicates that HP pen 0 will be used for the background; pen 1 will be
used for MSC.Patran colors 1 through 3; HP pen 2 for MSC.Patran colors 4 and 5; HP pen
5 for MSC.Patran color 6; HP pen 4 for MSC.Patran color 7; and HP pen 3 for MSC.Patran
colors 8 through 15. (Note that for this example, 16 colors are being mapped.)
“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.
Note: All databox values are preference environment variables that may be
permanently changed in the p3_printers.def file. Refer to Printer
Configuration File (p. 194) for more information.
CHAPTER 4 1
Working with Files

percentage.
centered.
page. Remember that the left is relative to the rotation
caused by the Orientation selection.
hardcopy.
PART 2
Basic Functions

Pen Mapping The default mapping is color 1 to pen 1, color 2 to pen
2, and so on up to 16 pens. For example,
0111.223344447777 will map color 1 to pen 0 (no
drawing), colors 2, 3 and 4 to pen 1. Colors 5 and 6 to
pen 3, etc.
Output Format 7 bit Creates ASCII output file.
3 8 bit Creates binary output file.
Laserjet III Yes The destination device is a HP-GL/2 LaserJet III.
No The destination device is not a HP-GL/2 LaserJet III.
Opaque Mode Yes Images will be plotted with underlying images
obscured by images in front.
No Images will be plotted with underlying images
showing through transparently.
Cutter Default Uses plotter’s cutter default setting.
Yes Enables plotter’s cutter function.
No Disables plotter’s cutter function.
Rotation 0, 90°, 180°, 270° Rotates the plotter’s coordinate system
counterclockwise by the amount chosen about the
plotter-unit coordinate region.
Printer Configuration File

Printers are configured with the p3_printers.def file, which is found in the pcl search path.
Each printer must be assigned a valid “driver”. Driver Specific options need not be displayed in
the Options form, yet they can still have a user defined default. For options with a set of choices,
the choices can be limited to a subset. Note that this file is read only when MSC.Patran is started
up.
For example, the following lines will define a postscript printer.
Printer = Engineering
Device = HP LaserJet 4M
Driver = Postscript
Destination = lw9
Paper Size = Letter
Left Margin = 0.5
Right Margin = 0.5
Top Margin = 0.5
Bottom Margin = 0.5
Format = No Show; Black to White
Background = No Show; White
Lines & Text = No Show; Black
Line Weight = 0.5 pts
Text Scale = 100%
Image Size = Fit on Page, As Is
Draw Borders = No Show; Yes
CHAPTER 4 1
Working with Files
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 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 Option Choices

Printer Definition Printer User assigned name
Device Device description
Driver CGM
HPGL
HPGL2
PatranHard File
Postscript
Destination Valid UNIX printer
PART 2
Basic Functions

Page Setup Page Size 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” )
3
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 1
CHAPTER 4 1
Working with Files

Postscript Driver Format Black to White
White to Black
Grayscale
Color
Background White
Black
Actual
Lines & Text White
Black
Actual
Line Weight 0.5 pts
Text Scale 100%
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%
PART 2
Basic Functions
File>Images Creating Graphic Images
Images are graphic outputs of MSC.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
3 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.
BMP Images Output

This option will produce an image file of the current viewport in Windows BMP bitmap format.
BMP is a commonly used file format on IBM PC-compatible computers. BMP files can also refer
to the OS/2 bitmap format, which is a strict superset of the Windows format.
File Select Use this option to navigate to the desired folder and file.
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 Save the image file in the specified destination folder.
CHAPTER 4 2
Working with Files
JPEG Images Output

JPEG (Joint Photographic Experts Group) identifies and discards “extra” data, meaning
information beyond what the human eye can see. This compression also economizes the way
data is stored. Because JPEG discards data, the algorithm is considered “lossy”, that is, when an
image has been compressed and decompressed it will have lost some data and may not be
identical to the original image.
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 Use this option to navigate to the desired folder or file.
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.
PART 2
Basic Functions
MPEG Images Output

MPEG (Moving Picture Experts Group) is a family of international standards used for coding
audio-visual information in a digital compressed format. Using the Start/Pause/Stop
capabilities enables you to record complex animation sequences, for example animate model
translations and rotations, or analysis results.
Filename Default name is the current database name with the .mpg
Max. Frames Set the maximum number of animation frames generated.
Start (1), Pause (2), and Stop (3) buttons to control animation
file recording.

CHAPTER 4 2
Working with Files
PNG Images Output

The PNG (Portable Network Graphics) format is useful for image editing and for storing
intermediate stages of an image file. PNG's advantage is that its compression is fully lossless,
furthermore, it supports up to 48-bit truecolor or 16-bit grayscale, therefore, quality will not be
degraded after the image is restored and saved again.
Filename Default name is the current database name with the .png
PART 2
Basic Functions
TIFF Images Output

TIFF (Tagged-Image File Format) is used to exchange image files between different applications
and different computer platforms. TIFF is a lossless image format.
Filename Default name is the current database name with the .tif
CHAPTER 4 2
Working with Files
VRML Images Output

With VRML (Virtual Reality Modeling Language) images you can capture 3D objects and create
interactive simulations that incorporate animation, motion physics, and real-time, multi-user
participation. VRML images and scenes can be displayed on another user's computer screen, or
distributed using the World Wide Web and explored interactively by remote users. The current
specification, VRML 2.0, supports JAVA, sound, animation, and Javascript.
Filename Default name is the current database name with the .wrl
PART 2
Basic Functions
File>Report Creating Report Files
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 • New--create a new report file

• Append--open an existing report file to add new data.
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.
Report File Name The name of the report file is automatically entered from the
File Name input field.
Report Contents Select the data you want to include in the report file.
CHAPTER 4 2
Working with Files
To generate a Report File:

• First, you have to point the report writer to the Elements or Geometry application in
order to collect the content information. Therefore, in the Menu Bar, click the Elements
or Geometry icon.
• In the Finite Element or Geometry application box, for Action select Show.
• For Object you can pick either nodes or elements for Elements and Point for the
Geometry 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.
PART 2
Basic Functions
Report Format Preferences
Real Numbers Select the format of displayed numerical data.

Field Width/Number Select the appropriate number with slide bar. The width of the
of Decimals field must accommodate the total number of digits and the
decimal point contained in each field of the tabular report.
Integers Select the number of integers expected in the numbers
contained in the tabular report.
Spacing Select the number of spaces between columns in the tabular
report.
Report File Output

The following is the beginning portion of a simple report file:
CHAPTER 4 2
Working with Files
PART 2
Basic Functions
3
CHAPTER
All About Groups
5
■ Group Concepts and Definitions
■ The Group Menu

PART 2
Basic Functions
5.1 Group Concepts and Definitions

A group is a named collection of selected geometric or finite element entities. The primary
purpose of grouping entities within a larger model is to create easily manageable subsets that
can be visually isolated for various modeling and post-processing tasks.
A model may contain any number of groups, and any entity may be associated with more than
one group. When an entity is added to or removed from a group, other groups will not be
affected.
Groups become permanent members of a model’s database. A group, named default_group,
exists in any new database; until you define and activate new groups, all new entities
automatically become members of this group.
The defining features of a group are:
• Name
• Member entities
• Status
• Attributes
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 Group_1 are regarded as two distinct groups.
• Optional prefixes and suffixes--a prefix and/or suffix added to a stem name can make
it easier to manage named objects. For example:
asm.wheel.left
Prefix Stem Suffix

(geometry type) (generic name) (modifier to generic name)
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.
CHAPTER 5 2
All About Groups
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 (p. 241)).
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 (p. 287)).
Creating and Managing Groups

Creating Groups
A group, named default_group, automatically exists in any new model. Initially, all new entities
become members of this group as they are added to the database.
After you make a new group with the Create option in the Group menu, new entities will
become members of this group. You can also move any existing entity into a newly defined
group.
Adding Group Members

The Group menu affords several different ways of assigning additional members to a group
(Modify, Move/Copy, Transform).
Entities contained in imported CAD files may be sent to existing groups or you may create new
groups to receive them.
PART 2
Basic Functions
Removing Group Members

The same Group menu actions can also be used to terminate membership in a group. Note that
even if an entity is removed from its group it will still remain in the MSC.Patran database, unless
you specify otherwise.
A removed entity that is not assigned membership in another group becomes an orphan and
cannot be displayed until it becomes a member of another group.
Transforming Groups
Group transformations allow you to translate, rotate, and otherwise modify the position of a
large number of entities in a single step. Several transformations, e.g., rotation, allow repeated
iterations as well.
Deleting Groups
When a group is deleted, or dissolved, its former members remain in the model database unless
you specifically request to delete them.
Note that the current group of a viewport cannot be deleted.
Important: If a deleted group contains nodes associated with elements or
multipoint constraints not in the group, these nodes will be retained in
the database even if you choose to delete the rest of the group members.
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
CHAPTER 5 2
All About Groups
where:
P n = the location of a point ( P 0 ) in the current group after the nth iteration.
P n – 1 = the location of the same point before the nth iteration.
T xyz = the translation vector.
Rotation
Rotation is an angular transformation around an axis. The formula for rotation is:
Pn = Pn – 1 + ( θo + θr )
where:
P n = the location of a point ( P 0 ) in the current group after the nth iteration.
θ o = an optional offset angle. The offset is valid only for the first rotation, for the second
iteration and beyond, θ o = 0 .
θ r = the rotation angle.
P2
P1
Repeat Count = 2
θr
θr
Axis
θo
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. 619) in the
MSC.Patran Reference Manual, Part 2: Geometry Modeling 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
PART 2
Basic Functions
where:
P n = the location of a point ( P 0 ) in the current group, relative to the scaling origin, after
the nth iteration.
Sxyz = 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:
P m = the distance, before transformation, of any point ( P0 ) from the final mirror plane,
measured along an axis, normal to the final mirror plane.
P b = the distance, after transformation, of the same point from the final mirror plane,
measured along an axis, normal to the final mirror plane.
Selected Mirror Plane--is any arbitrary plane in model space.

Final Mirror Plane--is a plane offset from the selected mirror plane by a specified distance along
an axis, normal to the selected mirror plane.
Radius of Rotation--is a straight line of length P b that is normal to the final mirror plane, and
extends from the selected point ( P 0 ) to the point of intersection with the final mirror plane.
In the example illustrated below, the selected mirror plane is the Y-Z plane of the global cartesian
coordinate system. Thus, the offset, radius, and distances Pb and P m are measured along the X-
axis, which is normal to the Y-Z plane.
Selected Mirror Plane (Y-Z)

Final Mirror Plane
Y
P’ 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 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.
CHAPTER 5 2
All About Groups
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 P p P s and P p P e vectors. The center of rotation
is 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
θ Pe
θ Pb
Pp
PART 2
Basic Functions
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.
P1o
P2d Vt
P1d
P3d P2o
P3o
(1)
P2d
P1d P3d
P1o P2o
P2d P3o P2o
P3d P2d P3o
P1d P1d
P2o P1o P1o
P3o P3d
(2a) (2b) (2c)
Repositioning is performed as follows:

1. Translation: The translation vector, V τ is defined between the original position of Point
1 ( P1o ) and the destination position of Point 1 ( P 1d ).
2. Rotation:
1.
•Two vectors are drawn; one between the original position points P 1o and P 2o
( P 1o P 2o ) and one between P1o and P3o ( P 1o P 3o ).
•Two additional vectors, P 1d P 2d and P 1d P 3d , are drawn between the three

destination position points ( P1d to P 2d ) and ( P 1d to P 3d ).
•The two angles, one between P 1o P 2o and P 1d P 2d and the second between
P 1o P 3o and P 1d P 3d , establish planar rotation angles for the
transformation.
2. Vector P 1o P 2o is rotated into vector P 1d P 2d .
3. Vector P 1o P 3o is rotated into vector P 1d P 3d .

CHAPTER 5 2
All About Groups
Transforming Loads, Boundary Conditions, and Properties
Loads and Boundary Conditions. Loads and boundary conditions (LBCs) assigned to
original entities may be transformed with a group, using one of three options:
• Transform--applies the same transformation to loads and boundary conditions as that
applied to 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 newly transformed entities.
• None--does not assign loads and boundary conditions to transformed entities.
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 entity’s normal.
PART 2
Basic Functions
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.
• None--does not assign properties to transformed 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.
CHAPTER 5 2
All About Groups
5.2 The Group Menu

The Group menu provides the commands that create and manage groups and their attributes.
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... Creates a new group and automatically posts it for display.

Post... Posts (or unposts) existing groups to the current viewport.
Modify... Provides several functions to change a selected group’s
definition, including renaming the group, making it current,
and adding to or removing entities from it.
Move/Copy... Moves or copies members of one group to another.
Set Current... Selects a group to be current for the current viewport.
Transform... Transforms members of a group to create and add new
entities in a different configuration. LBCs and element
properties associated with the original entities may also be
transformed.
Delete... Deletes a group, except the current group, and optionally
deletes its associated members from the database.
Attributes Assigns display attribute sets to one or more groups.
PART 2
Basic Functions
Group>Create Creating a New Group
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. Additional options include making the new group current, as well as unposting all
other groups currently posted.
Filter Using a filter helps you reduce the number of items displayed in a
potentially long list. Consequently, it takes less time to search for
an item (see Forms, Widgets, and Buttons (p. 22)). By default, all
items contained in a list will be displayed since the default filter is
the wild card (*). To specify a filter, either enter the full name of the
desired item or type one or more letters in the name followed by a
wildcard. After you pressed the Filter button to activate it, only the
item(s) that pass the filter criteria will be included in the list.
Existing Group Displays the names of previously defined groups for your
Names information. The name of the current group is highlighted.
New Group Name Enter a unique new group name; (see Group Names (p. 208) for
more help).
CHAPTER 5 2
All About Groups
Make Current Default is ON (✔). Makes the new group the current group.
Unpost All Other The new group is posted and any other posted groups are
Groups unposted.
Group Contents Provides several options for selecting entities to become group
members. Click the Add Entity Selection button then select
entities to include in the new group. Additional options include
adding all geometric entities, all FEM entities, all orphan entities,
or even adding all entities.
Entity Selection Displays the ID’s 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.
PART 2
Basic Functions
Group>Post 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 Identifies the current viewport in which you post the group.
Select Groups Displays the names of all groups in the database. To post a
to Post 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.
CHAPTER 5 2
All About 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.
• Remove entities from a group.
Target Group to Identifies the group targeted for modification. Although the
Modify default target group is the current group, you may designate
any another group as the target group.
Change Displays a dialog box in which you can select a different
Target Group target group.
Make Current Makes the target group the current group.
Rename Enables you to enter a new name for the target group in a
subordinate dialog box.
PART 2
Basic Functions
Selectable When this toggle is not turned to ON, the entities that belong
Members to the group cannot be picked even though the group is
displayed (default is ON (✔)).
Member List Lists the member entities of the group by name and ID.
Member List to Displays IDs of the entities as you select them for adding to
Add/Remove or removing from the group.
To add entities, select from the screen or type in entity IDs. To
remove entities, you can pick them from the Member List
textbox.
To select several entities, hold the Shift key and click the next
item.
Add Press this button to complete the process of adding the
selected entities to the target group.
Remove Press this button to complete the process of removing the
listed members from target group. The membership of these
entities in other groups will not be affected.
If the removed entity is not a member of any other group, it
becomes an orphan and will not be visible until it has been
added to a group.
Adding Orphan Entities to Groups

One of the following command sequences can add orphaned entities to a group:
• Group>Create>Add All Orphans creates a new group that will contain all orphans in the
model database.
• Group>Create>Add All Entities creates a new group that will contain all entities,
including orphaned entities, from the model database.
• Group>Modify>Add use the All Geometry, All FEM, or All Entities option to add orphan
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.
Changing the Target Group

CHAPTER 5 2
All About Groups
If you pressed the Change Target Group... button in the Group>Modify dialog box, you will
see the subordinate dialog box shown below. Pick the name of the group you would like to select
as the new target group.
Renaming a Group
PART 2
Basic Functions
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.
CHAPTER 5 2
All About Groups
Group>Move/Copy Moving and Copying Group Members
The Group>Move/Copy command and dialog box allows you to move or copy entities between
groups.
From Group Pick the source group to which the entities currently belong.
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... Displays the Entity Selection form.
PART 2
Basic Functions
Select Entities
Geom. On Press Geom. On to be able to pick all geometric entity types.

Geom. Off Press Geom. Off to cancel the “all” selection. Note that an
entity type is selectable only if its toggle box is ON (✔).
FEM On Press FEM On to be able to pick all FEM entity types.
FEM Off Press FEM Off to cancel the “all” selection.
From Name of the From Group as selected in the parent form.
“From” textboxes Textboxes display the current members of the From Group.
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.
To Name of the To Group as selected in the parent form.
“To” textboxes Display the current members of the To Group.
CHAPTER 5 2
All About Groups
Group>Set Current Making a Group 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 (p. 241)).
Set Current Group Pick the group you want to designate as the current group.
PART 2
Basic Functions
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 (for
more information about these operations, see Group Transformations on page 210).
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.
Change Calls up a dialog box in which you can select a target group
Target Group... different from the current group.
Delete Generally, in a transformation process the original (target)
Target Group group is copied and the resulting copy is transformed
leaving the target group in its initial position. You can,
however, request that only the copy(s) be retained and the
target group be deleted, provided that the target group is not
the same as the current group, since the current group cannot
be deleted.
Group deletion ends the association of group members with
one another but does not remove the entities themselves
from the database, unless you specify otherwise (see below).
However, an entity not associated with any group becomes
an orphan and will not be visible on the screen until it joins a
group again.
Delete Original Deletes original entities that belonged to the target group.
Members
• Use Original IDs Assigns the names and ID numbers of deleted original
entities to the new ones obtained through transformation.
Loads/BCs Loads and boundary conditions associated with transformed
entities may be transformed or copied. Alternately, you may
choose not to assign any loads and boundary conditions to
transformed entities.
Properties Properties associated with transformed entities may be
transformed or copied. Alternately, you may choose not to
assign any properties to transformed entities.
Translating Groups
CHAPTER 5 2
All About Groups
The Group>Transform>Translate command sequence moves and copies a group linearly along
an XYZ translation vector.
Reference Specifies the coordinate frame referenced by the translation

Coordinate Frame process. When you click in this field, the Coordinate Frame
select icons will appear in the Toolbar (see Select Menu
(p. 31)). Enter the ID of a previously defined coordinate frame
(the ID of the global coordinate frame is Coord 0) or select a
coordinate frame type from the Select Menu then pick a
frame of the selected type in a viewport. The selected
reference frame must be Cartesian; curvilinear frames are not
accepted.
Translation Vector When you click in this field, the Vector select icons will
appear in the Toolbar (see Select Menu (p. 31)). 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.
Repeat Count Specifies the number of translated copies you wish to create
(default=1).
Rotating Groups
PART 2
Basic Functions
The Group>Transform>Rotate command sequence performs angular transformations around

an axis.
Reference Specifies the coordinate frame referenced by the rotation process. When
Coordinate Frame you click in this field, the Coordinate Frame select icons will appear in
the Toolbar (see Select Menu (p. 31)). Enter the ID of a previously
defined coordinate frame (the ID of the global coordinate frame is
Coord 0) or select a coordinate frame type from the Select Menu then
pick a frame of the selected type in a viewport. The selected reference
frame must be Cartesian; curvilinear frames are not accepted.
Axis When you click in this field, the Axis select icons will appear in the
Toolbar (see Select Menu (p. 31)). 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 Specifies the angle of rotation ( θ r ) in degrees.
Default = 90o CW. A minus sign indicates counterclockwise rotation.
CHAPTER 5 2
All About Groups
• Offset Angle Specifies an angle of offset ( θ o ), if any, in degrees.

Default= 0o. A minus sign indicates a CCW offset angle.
• Repeat Count Specifies the number of rotated copies you wish to create (default=1).
Scaling Groups
The Group>Transform>Scale command sequence proportionately scales the target group

relative to a scaling origin ( S o ).
PART 2
Basic Functions
Reference Specifies the coordinate frame referenced by the scaling

Coordinate Frame process. When you click in this field, the Coordinate Frame
select icons will appear in the Toolbar (see Select Menu
(p. 31)). Enter the ID of a previously defined coordinate
frame (the ID of the global coordinate frame is
CoordinateFrame 0) or select a coordinate frame type from
the Select Menu then pick a frame of the selected type in a
viewport.
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 (p. 31)). 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 Specifies the scaling factors applied to the group in the X, Y,
Factors and Z directions (if scale factor = 1, there is no change).
Repeat Count
Specifies the number of scaled copies you wish to create
(default=1).
Mirroring Groups
CHAPTER 5 2
All About Groups
The Group>Transform>Mirror command sequence performs a 180-degree rigid-body rotation

of a group around a mirror plane.
Define Mirror Plane Specifies the plane that serves as the mirroring plane. When
Normal you click in this field, the Plane select icons will appear in the
Toolbar (see Select Menu (p. 31)). 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).
PART 2
Basic Functions
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.
Reverse Curves Modifies the contained curves and surfaces by reversing the
and Surfaces corresponding parametric direction and normals. See
Reversing a Curve (p. 448) and Reversing Surfaces
(p. 501) in the MSC.Patran Reference Manual, Part 2: Geometry
Modeling.
Beam and shell finite elements will also be reversed if this
toggle is on. Solid finite elements will always be reversed
(regardless of toggle setting) to avoid negative volume.
Modifying Group Orientation
The Group>Transform>Mcoord command sequence moves a group from its original

coordinate frame to a new coordinate frame. As a result of simultaneous rigid-body translation
and rotation, the local 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.
CHAPTER 5 2
All About Groups
From Specifies the coordinate frame in which the group is currently

Coordinate Frame defined. The default ID of the From Coordinate Frame is the
active coordinate frame. Coord 0 is the ID of the global
coordinate frame.
To Specifies the coordinate frame in which a copy of the group
Coordinate Frame will be created. When you click in this field, the Coordinate
Frame select icons will appear in the Toolbar (see Select
Menu (p. 31)). Enter the ID of a previously defined
coordinate frame or select the icon of the coordinate frame
type then pick a frame of the selected type.
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 ( Ps ), and an ending point ( P e ).
Pivot Point Center of rotation.

Starting Point Current position of any point in the group ( P s ).
End Point Final position of the same point in the pivoted group ( P e ).
When you click in one of these fields, the Point select icons will appear in the Toolbar (see
Select Menu (p. 31)). Enter a point location (global Cartesian coordinates, Point ID, Vertex ID,
PART 2
Basic Functions
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.
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 Specify the current position of three non-colinear points in

the group.
Destination Specify the final desired position (non-colinear) of the same
Position three points in the final group.
When you click in one of these fields, the Point select icons will appear in the Toolbar (see Select
Menu (p. 31)). 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.
CHAPTER 5 2
All About Groups
Group>Delete Deleting Groups
The Group>Delete command deletes one or several group definitions.
Current Group Name of the current group in the current viewport.

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.
Select Group(s) Highlight the group(s) you want to delete. The current group
To Delete 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 The members of the group you want to delete will be deleted
Members from the model even if those entities belong to other groups.
PART 2
Basic Functions
Group>Attributes Assigning Attributes to Groups
With the Group>Attributes command you can assign named attributes to one or several groups
(for more information on named attributes, see Named Attributes (p. 285)). The advantage of
using this command is that it allows you to assign display attributes to any number of groups.
CHAPTER
Viewports
6
■ Viewport Concepts and Definitions
■ The Viewport Menu
■ Viewport Commands
PART 2
Basic Functions
6.1 Viewport Concepts and Definitions

Viewports are named graphics windows through which you look at a model. You can define as
many viewports as you need to help visualize different aspects of a model. For example, as an
effective way of showing the results of finite element analysis, one viewport may contain the
original geometric model with applied loads and boundary conditions, while in a second
viewport you can display the distorted model and color plots of stresses generated by the
applied loads.
You can control the size and location of viewports, perhaps making selected viewports larger--
and more prominent--than others, or you can request that the viewports be tiled, in which case
all visible viewports are scaled to the same size and repositioned in rows and columns to fit the
viewing area.
Viewport definitions are stored in the MSC.Patran database. A viewport, named
default_viewport, is automatically created in a new database, with a graphics area that is initially
blank.
The defining characteristics of a viewport are:

• Name
• Status
• Display attributes
• Current group and posted groups
• Named views in viewports
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:
CHAPTER 6 2
Viewports
a through z
A through Z
0 through 9
-, _ , and .
• Case sensitivity--upper and lower case letters are recognized. For example, top_view
and Top_view are regarded as two distinct views.
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.
Viewport Display Attributes

Display attributes are a set of display parameters defined for each viewport. Display parameters
include:
• Viewport size and location
• Display of viewport titles and annotations
• Display of coordinate axes and origin symbol
• Color bar display status and assigned range
Viewports and Groups

A viewport may contain any number of groups that are posted, or selected for display. Posting
or unposting of groups in a target viewport will not affect the posted groups in other viewports.
A group may be posted to more than one viewport at a time.
Only one group can be the current group in a viewport, however in each viewport you can
designate a different group as the current group.
PART 2
Basic Functions
Named Views in Viewports

Named views are views that you can create with the Viewing menu and store for later use (The
Viewing Menu (p. 262)). When a named view is applied to a selected posted viewport, the
current view will change according to the parameter values of the named view.
Common Viewport Features

Certain common display features provide visual information about a number of viewport
attributes and are common to all viewports. Some features are automatically displayed and must
remain on the screen, while the visibility of others can be controlled.
❏ Top Banner--a posted viewport’s top banner automatically displays the following:
• Model database name
• Viewport name
• Current group name
• Display method--by group or by entity type
new.db- default_viewport- default_group- entity
❏ 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
(p. 248)).
❏ Global Cartesian Coordinate Axes--the icon that represents the global Cartesian
coordinate axes is displayed in the viewport’s 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 (p. 248)).
❏ 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 (p. 285) )
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.
CHAPTER 6 2
Viewports
6.2 The Viewport Menu

The Viewport menu provides the commands that create and manage viewports and their
attributes.
Menu Conventions
A menu item with ellipses (...) attached to it will call up an additional menu form in which you
enter further data.
Viewport
Create...
Post...
Modify...
Delete...
Tile
The Viewport menu functionalities are described below in the order in which they appear.
Create... Creates a new viewport and makes it the current viewport.

Post... Posts or unposts viewports for display.
Modify... Provides several functions that change viewport definitions,
such as viewport name, size, or location, current viewport
selection, and visualization control.
Delete... Deletes selected viewports (except the current viewport).
Tile Resizes and repositions posted viewports to fit within the
available screen area.
PART 2
Basic Functions
6.3 Viewport Commands

The following is a detailed description of the commands and dialog boxes with which you create
and manage viewports.
Viewport>Create Creating a New Viewport
With the Viewport>Create command sequence you can create and name new viewports.
Existing Viewports Displays the names of previously defined viewports for your
information. The name of the current viewport is
highlighted.
New Viewport Name Enter a unique new viewport name; (see Viewport Names
(p. 240) for more help).
Note that a newly created viewport automatically becomes the current viewport.
CHAPTER 6 2
Viewports
Viewport>Post Posting and Unposting Viewports
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 Displays the names of all viewports in the database. The

Viewports 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 (p. 209)). Consequently, you will not be able to see
new geometric and finite element entities as they are created.
PART 2
Basic Functions
If you select a viewport other than the current viewport for posting, the current viewport will be
unposted. MSC.Patran will display the following warning message:
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.
• Modify the attributes of the target viewport.
CHAPTER 6 2
Viewports
Current Viewport Displays the name of the viewport you specified as current.
Target Viewport to Displays the name of the viewport you selected for
Modify modification.
Change Target Displays the Change Target Viewport dialog box in which
Viewport... you can select a different viewport for modification.
Make Current Makes the newly specified target viewport the current
viewport.
Post/Unpost Displays a dialog box in which you can select one or more
Groups... groups to post or unpost (display or hide) in the target
viewport.
Set Current Group... Displays a dialog box in which you can select a group that
will be the current group in the target viewport.
Apply Named Brings up the Apply Named View dialog box in which you
View... can select a previously defined and named view that will be
displayed in the target viewport.
PART 2
Basic Functions
Rename... Displays a dialog box in which you can specify a new name
for the target viewport.
Attributes Allows you to control various display attributes assigned to
the target viewport.
Range Name Displays the name of the selected range (or the default
range).
Change Range Ranges have an important role in displaying finite element
analysis results. The name of the default range table is
standard_range. This command brings up a dialog box in
which you can select a previously defined and named range
table to assign to the target viewport.
Show Spectrum Bar If the toggle is ON (✔), the spectrum color bar will be
displayed. Default is OFF.
Show Viewport If the toggle is ON (✔), the viewport legend will be
Legend displayed. Default is OFF.
Show Global Axes If the toggle is ON (✔), the global coordinate axes will be
displayed in the lower left corner of the target viewport.
Default is ON.
Show Origin Sym- If the toggle is ON (✔), the crosshairs that identify the global
bol cartesian origin (0,0,0) location will be displayed in the target
viewport. Default is ON.
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 of the viewing area.
• Distances are in inches.
To change the location of a viewport do one of the following:
• Enter new numerical values to locate the upper left
corner of the target view
• With the cursor in the top banner, drag the viewport
anywhere in the viewing area. Note that in the dialog
box, the X, Y Location input display will update only
after you click Viewport>Modify again.
CHAPTER 6 2
Viewports
X,Y Size Indicates the X and Y dimensions (in inches) of the target
viewport.
To change the dimensions of the viewport do one of the
following:
• Enter new numerical values to specify new dimensions.
• With the cursor at one of the edges or at one of the
corners of the viewport, drag the viewport boundaries.
Note that in the dialog box, the X, Y Size display will
update only after you click Viewport>Modify again.
Reset Returns the contents of the entire dialog box to their
previously applied state and values.
Changing the Target Viewport

If you pressed the Change Target Viewport... button in the Viewport>Modify dialog box, you
will see the subordinate dialog box shown below.
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.
PART 2
Basic Functions
Posting and Unposting Groups in a Viewport

If you pressed the Post/Unpost Groups... button in the Viewport>Modify dialog box, you will
see the subordinate dialog box shown below. Here you can select the group(s) that will be visible
(posted) in a particular viewport.
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
Post/Unpost Displays the names of existing groups. To post a group, click
Group(s) on its name to highlight it. When you select a group for
posting, all other groups become unposted and their names
become unhighlighted.
To select several groups listed consecutively, hold the Shift key
while clicking each item. To select several groups not listed
consecutively, hold the Ctrl key while clicking.
CHAPTER 6 2
Viewports
Defining the Current Group in a Viewport

If you pressed the Set Current Group... button in the Viewport>Modify dialog box, you will see
the subordinate dialog box shown below. Here you can specify which group will be current in
the target viewport.
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.
PART 2
Basic Functions
Applying a Named View to a Viewport

If you pressed the Apply Named View... button in the Viewport>Modify dialog box, you will
see the subordinate dialog box shown below. You can then select a previously defined named
view (see Viewing a Model (p. 257)) to be displayed in the target viewport.
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 Displays the names of existing named views. To apply a
named view, click on its name to highlight it. The view of the
model in the target viewport will then change to the named
view as requested.
CHAPTER 6 2
Viewports
Renaming a Viewport
If you pressed the Rename... button in the Viewport>Modify dialog box, you will see the
Default is the wildcard (*), meaning that all items will be
listed.
Existing Names Displays the names of existing viewports. If you specified a
filter, only those viewports that pass the filter criteria will be
listed.
Rename As Enter the new name that you want to give to the target
viewport.
PART 2
Basic Functions
Changing the Spectrum Range Designation

If you pressed the Change Range... button in the Viewport>Modify dialog box, you will see the
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.
CHAPTER 6 2
Viewports
Viewport>Delete Deleting Viewports
With the Viewport>Delete command sequence you can delete any number of viewports--except
the current viewport.
Current Viewport Displays the name of the 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.
PART 2
Basic Functions
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.
CHAPTER
Viewing a Model
7
■ View Concepts and Definitions
■ The Viewing Menu
■ Viewing Commands
PART 2
Basic Functions
7.1 View Concepts and Definitions

Views let you to present a model in various orientations in their respective viewports. One view
may display the full three-dimensional model, while others may depict it from different angles
or show enlarged details of important features. With the Viewing menu you can pan, zoom,
rotate, clip, and resize views.
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
(p. 242)). Additionally, MSC.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:
a through z
A through Z
0 through 9
-, _ , and .
• Case sensitivity--upper and lower case letters are recognized. For example, front_view
and Front_view are regarded as two distinct views.
A database may contain any number of uniquely named views.
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 plane’s X and Y coordinate system.
Viewing Coordinate System Parameters

The viewing coordinate system of a viewport is defined as follows:
• The origin is at the viewport’s focal point.
• The positive X direction points to the screen’s right edge.
• The positive Y direction points vertically.
CHAPTER 7 2
Viewing a Model
• The Z-axis is normal to the viewport window, the positive Z direction is pointing
outward according to the right-hand rule.
Y Global Axes
Screen Axes
Global Origin
Y
Observer
Position Focal Point
Z
X
Z
X
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 viewport’s 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.
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 view’s 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
PART 2
Basic Functions
Makes the model appear larger (zoom in) or smaller (zoom out) in the viewport.
• Rotate
Rotates the view around selected global or screen axes.
All transformations can be implemented one of three ways:
• The Viewing>Transformations command (see Viewing>Transformations on
page 264)--click 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:
Panning--Select Center (p. 266)
Zooming--Select Corners, and Zoom% (p. 266)
Rotating--Angles (p. 267) and View From/To (p. 269)
• “Mouse method”--program the middle mouse button to execute one of the
transformations (see Preferences>Mouse (p. 340)).
Note: Several shortcuts to some of the view control functionalities are also
available via tool bar icons (see also Mouse Function Tool Palette (p. 13)
and Viewing Tool Palette (p. 14)).
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 observer’s position as well as the viewing plane location will modify
perspective distortion.
View Parameters
Focal Point. The view’s origin, it is also the center of rotation when the view is rotated, the
center for scaling, and the perspective’s center.
CHAPTER 7 2
Viewing a Model
Window Center. The center of the viewing plane from where translation distances are
measured.
Focal
Point
Viewing Plane
Z Observer’s
Position
Front Clipping Plane

Model
Back Clipping Plane Visible portion of the model
with Z- clipping and perspective
Viewing Plane Distance. The distance from the focal point to the viewing plane.
Observer Position Distance. The distance from the focal point to the observer’s position.
Front and Back Clipping Plane Distances. The distances from the focal point to the front and
back Z-axis clipping planes.
PART 2
Basic Functions
7.2 The Viewing Menu

The commands of the Viewing menu control the orientation, sizing, position, and visualization
methods of views in viewports.
Menu Conventions
A menu item with ellipses (...) attached to it will call up an additional dialog box in which you
enter or select further data.
If a menu item is followed by an expression containing the abbreviation Ctrl, this item can also
be accessed by an accelerated keyboard shortcut. For example, to activate the
Viewing>Transformations command with the shortcut, press the Ctrl (Control) key and the
lower case letter key (t) simultaneously.
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 view’s
rotational orientation will remain the same.
Select Center Pans a view by moving its center to a cursor picked location.
Select Corners Zooms in on a cursor-defined rectangular area of the view.
Zoom (% of view) Specifies a zoom factor, expressed as a percentage of the
normal fit view area, for viewing the model.
Angles... Rotates a view by specific angles about the X, Y, and Z axes of
either the global or screen coordinate system.
CHAPTER 7 2
Viewing a Model
View From/To... Rotates a view by moving the view origin or by modifying

the location of an observation point.
Scale Factors... Changes the projected size of a model in the view by using
specific scale factors.
Named View Applies an existing named view in a selected viewport.
Options... Creates new named views, and renames or deletes existing
named views.
Clipping/ Controls the parameters for clipping and perspective
Perspective... viewing.
Arbitrary Clipping... Creates, modifies, and deletes user-defined clipping planes.
Also enables or disables (posts/unposts) selected clipping
planes.
PART 2
Basic Functions
7.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”.
Visually rotates the model in the view around the X, Y, or Z

axis clockwise or counterclockwise by a selected incremental
rotational angle.
Visually increases or decreases the size of the model in the

view by a selected zoom factor.
Fits the view of the model inside the viewport boundaries.
Transformation Options
CHAPTER 7 2
Viewing a Model
If you pressed the Options... button in the View>Transformations dialog box, you will see the
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 The rotation takes place about global axes.
Screen Relative The rotation takes place about screen axes.
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 view’s rotational orientation will remain the same (for
automatic execution of Fit View, see Automatic View Settings (p. 339)).
PART 2
Basic Functions
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 view’s center will reposition itself to the center of the rectangle, and the
selected area will zoom to fill the viewport.
The viewport in which you select the corners will automatically become the current viewport.
P1
P2
Viewing>Zoom (% of View) Zoom by a Specified Factor

CHAPTER 7 2
Viewing a Model
The Viewing>Zoom (% of View) command lets you specify the zoom rate numerically rather
than using the zoom icon and the slidebar.
Zoom Factor The zoom factor is expressed as a percentage of the fit view size.
Custom... Enter a zoom factor in this subordinate dialog box if you
want to use a zoom factor other than those listed.
Viewing>Angles Rotate by a Specified Angle

PART 2
Basic Functions
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 The view is rotated relative to the zero (unrotated) position.
Relative The view is rotated relative to the current view position.
Rotation Angles The angle of rotation may be positive or negative around the
respective axis (follow the right hand rule).
Unit of Rotation The unit of rotation is degree, the allowable range is ±180o.
Center of View The center of rotation is the focal point (see Observation
Rotation Point (p. 269)); 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.
Example
Rotate the view as follows:
Rotation Method-- Model Absolute
Rotation Angles-- -30.0 10.0 15.0
Action-- The view is rotated from the global zero starting position,
-30o, 10o, and 15o about the global X, Y, and Z-axes, respectively.
CHAPTER 7 2
Viewing a Model
Next, rotate the view again as follows:

Rotation Method-- Model Relative
Rotation Angles-- -10.0 -5.0 -5.0
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 Moving the Observer and Origin Positions
The position of two points, the view origin, or focal point, and the observer position (see
Observation Point (p. 269)) 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 The observation point, or observer position, represents the

location of a person viewing the model in a perspective view.
To change the observer position, enter new model space
coordinates for the observation point.
PART 2
Basic Functions
Focal Point The focal point is the view’s 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 The model center is the geometric centroid of a viewport’s
displayed geometric and finite element entities. If you
changed the Focal Point coordinates in the dialog box, this
button will return the focal point to the model center. The
observer position will also change accordingly, in order to
maintain the same view rotation.
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.
Screen Scale The scale factors are applied in the X and Y directions of
Factors screen space. The center of scaling is the focal point.
Model Scale The scale factors are applied in the X, Y, and Z directions of
Factors model space. The center of scaling is the focal point.
Viewing>Named Views Creating and Manipulating Named Views

CHAPTER 7 2
Viewing a Model
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 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 Displays the name of the current viewport.

Select Named View 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.
PART 2
Basic Functions
Rename View... Renames a selected named view. Select the existing view to
be renamed and enter a new name in the subordinate dialog
box.
Delete View... Deletes a selected named view. You may confirm or cancel
your request to delete a named view:
Viewing>Clipping/Perspective Clippped Views

CHAPTER 7 2
Viewing a Model
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 These text boxes show the current position of the front and
Clipping Planes 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.
Viewing>Clipping/Perspective Perspective Views

PART 2
Basic Functions
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.
Back Clipping Plane Front Clipping Plane
Model along the Z-axis
View Plane The distance between the viewing plane, which is normal to
Distance the Z-axis, 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 The distance between the focal point and the location of an
observation point, measured along the Z-axis.
CHAPTER 7 2
Viewing a Model
Managing the Parameters of Perspective Viewing

Controlling The distance between the viewing plane and the observer
Distortion 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 You can control distortion visually by dragging the screen
symbols of the view plane and the observer to the left or to
the right. With each position change the perspective view of
the model will update immediately. Continue until the
desired effect is achieved. Note that the numerical values in
the data boxes will be modified as the respective symbols are
repositioned.
Guidelines for When entering numerical values for these parameters, use
View Plane Distance the following considerations:
and
• The observer position must be a non-zero positive
Observer Position
number.
• The distance of the observer position from the focal
point must be greater than the model tolerance ( see
Global Model Tolerance (p. 339)). If you enter an
unacceptable value, a warning message will be
displayed.
• The observer position distance must be greater than the
view plane distance, otherwise, the view plane would
end up behind the observer. If you enter an
unacceptable value, a warning message will be
displayed.
Viewing>Arbitrary ClippingCreating and Managing User-defined Clipping

Planes
PART 2
Basic Functions
The Viewing>Arbitrary Clipping dialog box accepts and displays all necessary information to
create and manipulate arbitrary, or user-defined clipping planes.
Post/Unpost Lists all previously defined arbitrary clipping planes; the

Clipping Planes currently posted (active) clipping planes are highlighted.
Click on a clipping plane to post it; click on a highlighted
(posted) clipping plane to unpost it.
The maximum number of clipping planes posted at any one
time is six (use the Ctrl key while picking multiple entries).
CHAPTER 7 2
Viewing a Model
Target Clipping The clipping plane affected by all modifications

Plane (e.g. rotation). To change the target plane from the one
displayed, click the button to show all selectable planes then
pick the new target plane.
Create... Creates a new clipping plane. Brings up a text box in which
you can enter the new name.
Delete... Deletes a selected clipping plane.
Clipping Plane Additional clipping plane features:
Attributes
Move If ON, the clipping plane will retain its orientation relative to
with Model the model even when it is moved. When OFF, the orientation
of the clipping plane is relative to the screen.
Display The plane icon consists of:
Direction Icon
• a rectangle in the orientation defined in the Options
below
• X and Y directional axes
• the plane’s normal represented by a directional arrow.
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 As an alternative to rotating the clipping plane with the
rotation icon, you can enter a new vector to change the
direction of the clipping plane normal. Note that if you do
use the rotation icon, the components of the normal vector
will automatically update in this text box.
Location As an alternative to moving the clipping plane with the
translation icon, you can enter the model coordinate location
of the clipping plane. Note that if you do use the icon to
move the plane, the location coordinates will automatically
update in this text box.
PART 2
Basic Functions
CHAPTER
Display Control
8
■ Display Concepts and Definitions
■ The Display Menu
■ Display Commands
PART 2
Basic Functions
8.1 Display Concepts and Definitions

Display functionalities are tools that help improve certain visual aspects of models. Examples of
display capabilities include the shaded rendering of solid models for more realistic appearance,
the shrinking of finite elements for easier recognition, and the creation of special colors for more
accurate analysis result interpretation.
It must be emphasized, however, that display controls are only instruments of visualization and
have no effect on fundamental analysis operations. The use of the commands in the Display
menu is generally based on personal preferences.
Global and Local Display Features

Global display features affect all viewports. As an example, the Erase feature, that temporarily
hides entities, is defined globally. If an entity is erased, it is erased from all viewports of the
model.
Local display features apply only to a selected viewport, thus inputs can vary from viewport to
viewport. For example, a title inserted in one viewport will not appear in another, thus you can
create distinct text inputs in each viewport.
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 (p. 293)).
CHAPTER 8 2
Display Control
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 straight-edged solids; for curved edges, however, it helps if you use visualization
lines in the display.
PART 2
Basic Functions
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
true curved edge

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 Chordal Tolerance = 0.002 Chordal Tolerance = 0.0002
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.
CHAPTER 8 2
Display Control
Finite Element Display

The rendering and display methods used for solid and surface objects are also applied to finite
element models. Just as in solid geometry, an approximation technique is used in FEM to reduce
the time it takes to display the model. The approximation, which affects only higher order
elements, may make the display of a model somewhat less precise.
Quadratic or cubic elements are most often used to mesh objects with curved faces because,
being nonlinear, they adhere more accurately to the definition of curved contours. The database
contains the precise mathematical definitions of these elements, but in the display of the finite
element model their curved edges are approximated with a series of straight line segments. The
chordal distance between the curved element edge and the approximating lines is inversely
proportional to the number of line segments, and if a very smooth realistic display is desired,
you can opt for a high number of lines. In a large FEM model, however, you may notice that
certain processes, especially the ones that require a change in the view display, become more
time-consuming.
PART 2
Basic Functions
The default number of line segments displayed on an element edge is the number of segments
required to connect the nodes that define the element edge. Take as an example a QUAD8, a two-
dimensional, eight-noded, quadratic quadrilateral element with one midside node on each edge.
The display of each 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 Number of Line Segments on Edge = 6
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.
Erasing and Plotting Entities

Erasing selected geometric or finite element entities makes them temporarily invisible. Plotting
redisplays erased entities. Erasure and plotting are global actions; erased entities are removed
from every view, likewise, plotted entities will be restored to every view. Because 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.
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.
CHAPTER 8 2
Display Control
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 MSC.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 color-coding 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.
Color Palette
For all color displays, MSC.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.
PART 2
Basic Functions
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.
MSC.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 MSC.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.
CHAPTER 8 2
Display Control
8.2 The Display Menu

The commands of the Display menu help organize and enhance the appearance of a model.
Menu Conventions
A menu item with ellipses (...) attached to it will call up an additional menu form in which you
enter further data. For more information on using the Display menu forms see Entering and
Retrieving Data (p. 21).
Display
Entity Color/Label/Render...
Plot/Erase...
Highlighting...
Geometry...
Finite Elements...
Load/BC/Elem.Props...
Named Attributes...
Coordinate Frames...
Titles...
Spectrums...
Ranges...
Color Palette...
Shading...
Light Sources...
The Display menu functionalities are described below in the order in which they appear.
Entity Color/ Controls colors assigned to entities or groups, turns entity

Label/Render... labels on or off, and defines rendering styles of solid and
surface entities.
Plot/Erase... Determines which entities of a model are visible. Erase hides
selected entities from view, Plot redisplays erased entities.
Erase and Plot are global actions that affect the display of all
viewports the same way.
Highlight... Provides a visual accent to a display by changing the color of

selected entities. Highlighting also helps locate entities
specified by entity IDs--a feature especially useful in a
complex model.
Geometry... Controls display attributes that help visualize geometric
entities.
Finite Elements... Controls display attributes that help visualize finite element
entities.
PART 2
Basic Functions
Load/BC/ Manages the visibility, colors, and label parameters of the

Elem. Props... symbols associated with loads, boundary conditions, and
element properties.
Named Attributes... Creates and manages named attribute sets.
Coordinate Frames... Displays or hides symbols of previously defined local
coordinate frames.
Titles... Adds text to viewports.
Spectrums... Generates and manages spectrums and their attributes.
Ranges... Defines ranges, subranges, and thresholds.
Color Palette Establishes customized color tables.
Shading... Sets parameters that affect the shading of a model.
Light Source... Controls lighting attributes, such as the type and position of
a light source and the intensity of light that illuminates
model surfaces.
CHAPTER 8 2
Display Control
8.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 Enhancing the Appearance of Entities
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 Displays a pop-up menu in which you can select a rendering
method.
PART 2
Basic Functions
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.
Entity Type Only in Entity mode, it assigns colors to entities by type.
Colors and Labels Specifies whether or not labels will be displayed on an entity
class.
To change the default color shown for an entity type:
• Click the color chip next to the entity type. This will
bring up the “Color Select” form with all available
colors.
• In this form, pick a new color for the entity type.
To specify that entities of a particular type should have their
labels displayed, click in the label toggle (✔).
Show/Hide All In the Entity mode dialog box; turns labels on or off for all
Entity Labels entities.
Show Labels In the Group mode dialog box; turns labels on or off for all
group members.
Label Font Size 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
(p. 319).).
Display>Plot/Erase Erasing and Redisplaying Entities
With the Display>Plot/Erase command you can temporarily “hide” (erase) selected entities or
redisplay erased entities (plot).
CHAPTER 8 2
Display Control
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 ID’s,
select them with the mouse (hold the Shift key for multiple
selections), or use any other select mechanism (see Selecting
Entities (p. 29)). The text in this textbox is editable, you can
delete any entity ID you did not intend to include in the list.
Erase Erases the entities contained in the entity list.
Plot Redisplays erased entities contained in the entity list.
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 Erases or plots all geometric entities.
Erase/Plot
FEM Erases or plots all FEM entities.
Erase/Plot
All Erases or plots all entities.
Erase/Plot
PART 2
Basic Functions
Display>Highlight Highlighting Selected Entities
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 (p. 319)).
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
(p. 29)). 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 Modifying the Appearance of Geometric Entities

CHAPTER 8 2
Display Control
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.
Number of Specifies the number of display lines used to help visualize

Display Lines solids or surfaces in Wireframe or Hidden Line rendering
(see Hidden Line (p. 281)). By default, the number of display
lines = 0, meaning that only the entity’s boundaries are
shown.
Chordal Tolerance Shows the selected chordal tolerance value that controls the
precision of the display of solid geometry (see Chordal
Tolerance (p. 282)).
Geometric Shrink Shows the model percentage by which the display of each
geometric entity will be reduced. At default = 0, no shrinking
takes place.
Show Parametric Displays the location and orientation of the parametric axes
Direction 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.
PART 2
Basic Functions
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 Increases or decreases the display size of geometric points to
aid visualization.
Colors and Labels 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 (p. 289)), 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 Posts or unposts symbols of previously defined local
coordinate frames.
Note: You can save the first five of the geometry attributes in a named attribute set (see
Named Attributes (p. 285).
Display>Finite Elements Modifying the Appearance of FEM Entities

CHAPTER 8 2
Display Control
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.
Number of Line Defines the number of line segments used to approximate the
Segments per Edge curvature of element edges. Default=0, which is to be
interpreted as accepting the minimum number of line
segments needed to connect the nodes located on each edge
(number of midside nodes plus one).
FEM Shrink Shows the model percentage by which the display of each
FEM entity will be shrunk. At default=0, no shrinking takes
place.
Show Only Free
Edges A free edge is a boundary edge of an element that is not
shared by at least one other element. When this toggle is on,
only free edges are displayed. This display tool can help you
verify whether there are any discontinuities in the finite
element model.
PART 2
Basic Functions
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 Increases or decreases the display size of nodes to aid
visualization.
Colors and Labels 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 (p. 289), 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 Posts or unposts symbols of previously defined local
coordinate frames.
Note: You can save the first five of the FEM attributes in a named attribute set (see
Named Attributes (p. 285)).
CHAPTER 8 2
Display Control
Display>LBC/Element Property Attributes Symbols for Loads, Boundary Conditions,

and Element Properties
With this command you can control the display symbols for loads, boundary conditions, and
element properties.
Load/BCs Controls of load and boundary condition symbols. To change

a default color, click on the color chip, then pick the desired
color in the color table.
Element Properties Controls element property symbols.
Show on FEM Only Functional assignments, such as loads, boundary conditions,
and element properties may be applied either directly to
geometry or to the finite element model. By default, all
symbols are displayed and positioned at the entities to which
they had been applied. If this toggle is on, only those symbols
are displayed that represent loads, boundary conditions, or
element properties applied to FEM entities.
PART 2
Basic Functions
Show LBC/ Certain loads and boundary conditions, and some element
El. Property Vectors properties are vector entities and their symbols are directed
arrows. Generally, their numerical values are also displayed.
If you turn this option OFF, both the vectors and the numbers
will be turned OFF.
Show LBC/ If you turn this OFF, but keep the Vectors on, the symbols
El. Property Values 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 Presents various options for identifying and displaying beam
elements.
Display Pin DOFs If ON, displays the degrees of freedom of the pinned
connection.
Display If ON, displays the degrees of freedom assigned to a spring
Spring DOFs element.
CHAPTER 8 2
Display Control
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.
Vector Length
Constant - The length of the vector symbols is constant. When you use
Screen Relative/ this option all vectors are of the same length; for example, a
Model Relative 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.
Scaled - The length of the vector symbols is scaled. In this case, the
Screen Relative vector that represents the 1,000 lb force will be displayed as
Model Relative 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 Enter a scale factor to be used when the vectors are scaled.
PART 2
Basic Functions
Vector Coloring
Same for All Vectors are shown in their actual direction in the colors
specified in the LBC/Elem. Properties dialog box.
Component This option displays the X, Y, and Z components of the
vectors in the colors defined in this dialog box.
Colors Select the display colors for vector components and the
resultant vector.
LBC/El. Prop. Filter With this option you can reduce some screen clutter by
displaying only those vectors that are associated with values
that meet some boundary requirements.
• None--display all vectors (default).

• Show Between Min/Max--only display the vectors
whose associated value falls between a lower and upper
boundary.
• Show Below Max--only display the vectors whose
associated value is below a specified maximum.
• Show Above Min--only display the vectors whose
associated value is above a specified minimum.
CHAPTER 8 3
Display Control
Label Style
Label style refers to the display format of the numerical values attached to symbols.
Label Format
Fixed The numbers are displayed in a decimal format.
Exponential The numbers are displayed in exponential format.
Integer The numbers are displayed as integers.
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.
Beam Display
This attribute controls the way beam elements of a mesh (e.g., on the edge of a plate) are
displayed on the screen.
1D:Line Elements are drawn as lines. Element properties (defined in

the Properties application), such as offsets and beam section
shape, are not displayed.
1D:Line + Offsets Elements are drawn as lines. Offsets are also displayed.
PART 2
Basic Functions
2D:Mid-Span Beam section shape is displayed at the mid-span location of

each beam element.
2D:Mid-Span Beam section shape is displayed at the mid-span location of

+ Offsets each beam element. Offsets are also shown.
3D:Full Span Beam section shape is displayed over the full span of
elements.
3D:Full Span Beam section shape is displayed over the full span of
+ Offsets elements. Offsets are also drawn.
Note: In 3D options, the beam sections are rendered in the rendering style specified for the
model with the Display>Entity/Color/Label/Render command.
Display>Named Attributes Creating and Managing Named Attribute Sets

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.
CHAPTER 8 3
Display Control
Select Current Set 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 Renames a selected attribute set.
Delete Deletes a selected attribute set.
Display> Coordinate Frames Displaying User-defined Coordinate Frames

In the Display>Coordinate Frames dialog box you can select one or more previously defined
local coordinate frames for posting.
PART 2
Basic Functions
Post/Unpost Lists the names and IDs of currently defined coordinate

Coordinate Frame(s) 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 Displays all coordinate frames, or removes all coordinates
from the screen.
Select Coordinate Provides another way of selecting one or more coordinate
Frame(s) 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 Adding Text to Viewports
With the Display>Titles command you can create and modify titles and other text displayed in
a viewport.
CHAPTER 8 3
Display Control
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.
Post New Title Automatically displays the new text you typed as soon as
you select Create or press the Enter key.
Create Inserts text in a selected viewport. To create new text or title:
• Enter the new text in the Target Title textbox
• Press Enter or select Create
• ONce displayed in the viewport, drag the new text to
the desired location.
Rename Lets you edit textual information. To change text already on
the screen:
• Click on the text you want to edit; the text will be
entered in the Target Title textbox.
• Press Rename. The Rename dialog box will appear.
• Enter the new text and press Apply.
Delete Deletes text from the screen.

• Click on the text you want to delete; the text will be
entered in the Target Title textbox.
• Press Delete. The following message will appear:
• Press Yes to confirm.

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.
PART 2
Basic Functions
Display>Spectrums Creating and Managing Spectrums
With the Display>Spectrums command you can define new spectrums or modify existing ones
for displaying analysis results.
CHAPTER 8 3
Display Control
Current Spectrum Lists the names of all spectrums defined in the database and
highlights the currently used spectrum. MSC.Patran software
comes with several predefined spectrums.
Create Creates a new spectrum by placing the colors in the standard
spectrum in a different order. When you press this button, a
subordinate dialog box will appear in which you can specify
the new spectrum attributes.
Number of Colors Specifies the number of colors in the new spectrum; this
number must be between 3 and 16. To choose the number of
colors, calculate the number of subranges in the range of
result data (see also “Number of Sub-Ranges” p. 309) then
add one color. The additional color is a no-data color and is
used only to set the background color of viewports.
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 Displays the color bar in the viewport as a continuum of
colors without the separation lines.
Interpolation Factor Controls interpolation between any two colors in a
continuous-display spectrum. The default value of 2.0,
representing quadratic interpolation, is generally acceptable.
Spectrum/ The left-hand column is for defining the new spectrum, the
Color Table 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 Creating Ranges and Subranges for Results Display

PART 2
Basic Functions
The Display>Ranges command creates and manages a named, ordered set of subranges that
attach numeric values to the colors in the spectrum used to display analysis results.
Target Range Lists all ranges defined in the database and highlights the
target range. This is the range targeted for modifications.
Assign Target Range Attaches a selected target range to the current viewport.
to Viewport
CHAPTER 8 3
Display Control
Create Creates a new Range. When you press this button, a

subordinate dialog box will appear in which you can specify
the attributes of the new range.
Number of Enter the desired number of subranges; this number must be

Sub-Ranges between 2 and 15. After a range has been created, the number
of subranges cannot be modified.
Data Method
Semi-Auto Creates contiguous subranges by subdividing the range of
results between the Start and End values into a specified
number of evenly spaced sets.
Start Establishes the lower limit of the result range. Use the Fit
Results option to obtain this value from the results file, or
type a desired starting value to start the range above the
actual minimum.
End Establishes the upper limit of the result range. Use the Fit
Results option to obtain this value from the results file, or
type a desired ending value to end the range below the actual
maximum.
Fit Results Obtains the Start and End values from the analysis result file.
Semi-Auto Generates contiguous subranges beginning at the Start value
(Delta) and adding a specified increment. The end boundary of one
subrange becomes the starting boundary of the next. Delta
may be a positive or negative number.
Start Enter the starting value of the first subrange.
Delta Enter the increment that will be added to the starting value of
each subrange to obtain its upper limit.
PART 2
Basic Functions
From From, From/To, and Middle are “manual” methods of

creating discrete subranges of unequal extent. When you
select either of these options, a Spreadsheet Input databox
will appear where you enter the desired value for a selected
subrange boundary.
With the From option you can create contiguous subranges

with arbitrary boundary values. You specify the lower
boundary (From) value of each subrange and upper
boundaries will be calculated so that the To value of one
subrange matches the From value of the following subrange.
Thus, overlapping or gapping will not occur between
subranges. Mean values (Middle) of subranges are also
calculated.
“From” Procedure:
4. In the spreadsheet in the dialog box, click the first cell of
the From column.
5. In the Spreadsheet Input databox, type the desired lower
limit of the subrange, followed by Enter. The number will
now also appear in the selected spreadsheet cell.
6. Continue entering From values until all cells are filled.
7. Press Calculate. Upper boundaries (To) as well as mean
values (Middle) of subranges will be calculated, and all
values will be displayed in the spreadsheet.
From/To Use the From/To option to create discrete subranges with
arbitrary boundary values. With this method you select both
the lower boundary (From) and the upper boundary (To)
values of each subrange. From and To values need not be
matched and “holes” may be created between subranges.
Mean values (Middle) of subranges will be calculated.
“From/To” Procedure:
the From column.
2. In the Spreadsheet Input databox, type the lower limit of
the subrange followed by Enter. The number will now
appear in the selected spreadsheet cell.
3. Repeat steps 1 and 2, selecting the To column instead of
From, and entering the desired upper limit of the
subrange in the Spreadsheet Input databox.
4. Continue entering From and To values until all cells are
filled.
5. Press Calculate. Mean values of subranges will also be
calculated and all values will be displayed in the
spreadsheet.
CHAPTER 8 3
Display Control
Middle With the Middle option you can create contiguous subranges
defined by their mean values. You specify the mean (Middle)
value of each subrange and lower and upper boundaries will
be calculated so that the To value of one subrange matches
the From value of the following subrange.
“Middle” Procedure:
the Middle column.
2. In the Spreadsheet Input databox, type the desired mean
value of the subrange followed by Enter. The number will
now also appear in the selected spreadsheet cell.
3. Continue entering Middle values until all cells are filled.
4. Press Calculate. The upper and lower limits of subranges
will be calculated and all values will be displayed in the
spreadsheet.
Thresholding Thresholding lets you magnify results within a smaller subset
(threshold) of a range while temporarily ignoring data
outside the boundaries of the threshold. Because ranges are
associated with viewports, with this functionality you can
create viewports that, for example, display in greater detail a
“spike” in the results, or others in which the highest and/or
lowest extremes of the result data are disregarded.
Once you have established the threshold boundaries, all
values outside these boundaries will be placed in the first
and/or last subrange and assigned a single color value. Thus
the remaining subranges and colors can be distributed over a
reduced span and each subrange can cover a smaller extent of
result values, allowing a closer observation of local result
changes.
Thresholding can be used only with one of the semi-
automatic data methods,
PART 2
Basic Functions
Thresholding Options
None No thresholding takes place.

Start Use the Start option when you want to disregard a portion of
the starting result range. For example, if analysis results
range from high (Start) to low (End), and you want the
display to ignore the high extremes, set the Start threshold
boundary below the Start value of the full range. The
meaningful display of subrange colors will begin here (all
results beyond this value are placed in one subrange and
given a single color).
Procedure:
1. Select Semi-Auto data method, enter the Start and End
bounding values of the entire range of interest (or use Fit
Results). Alternately, pick Semi-Auto (Delta) and enter
the Start and Delta values.
2. In the Thresholding section, select Start. The Start textbox
will be displayed.
3. Enter the result value that defines the starting boundary
of the threshold.
4. Press Calculate.
The extents of the first subrange (0) will be from the Start
value of the full data range to the Start value of the threshold.
As a result, each remaining subrange will cover a narrower
extent of result values than if no thresholding was selected.
CHAPTER 8 3
Display Control
End Use the End option when you want to disregard some result
values that fall into the ending result range. If, as in the
previous example, analysis results range from high (Start) to
low (End), but now you want the display to ignore the low
extremes, set the End threshold boundary above the End
value of the full range.
Procedure:
Results).
2. In the Thresholding section, select End. The End textbox
will be displayed.
3. Enter the result value that defines the ending boundary of
the threshold.
4. Press Calculate.
The last subrange will extend from the End value of the
threshold to the End of the full data range. Thus, each
preceding subrange will cover a narrower range of result
values than if no thresholding was selected.
Start/End Use the Start/End option when you want to concentrate on
result values that fall into a range within a specified upper
and lower boundary. Set the Start and End boundaries at
values below the high and above the low values of the full
range.
Procedure:
Results).
2. In the Thresholding section, select Start/End. Both the
Start and the End textboxes will be displayed.
3. Enter the result value that defines the starting boundary
of the threshold.
4. Enter the result value that defines the ending boundary of
the threshold.
5. Press Calculate.
The extents of the first subrange (0) will be from the Start
value of the full data range to the Start value of the threshold.
The extents of the last subrange will be from the End value of
the threshold to the End of the full data range.
All data values beyond these boundaries will be displayed in
a single color.
Display>Color Palette Creating and Managing Color Configurations

PART 2
Basic Functions
In the Display>Color Palette dialog box you can customize all colors used in the current
database.
Current Color Lists the name of all Color Palettes that exist in the database
Palette and highlights the currently used Color Palette. MSC.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.
Color Table You can choose between two methods of modifying colors:
Modifications
• HLS--creates and fine tunes a color based on its three
perceptual attributes, hue, lightness, and saturation.
• RGB--Creates new colors by varying the amount of red,
green, and blue they contain.
CHAPTER 8 3
Display Control
Hue Hue is an attribute of color that can be perceived as moving

through the spectrum as it extends around the color wheel,
proceeding clockwise from red (0o) through yellow, green,
blue, then back to red (360o). The range of the slider is 360o.
Lightness Lightness is an attribute of color that measures the amount of
transmitted or reflected light and controls the intensity of a
selected hue. It ranges from 0 to 1, where 0 makes all hues
appear close to black and 1 brings colors close to white.
Saturation Saturation controls the vividness of a color. At a saturation of
0 a color is dull and grayish, at higher saturation values
colors become brighter.
RGB Use the slidebar to regulate the percentage of the red, green,
and blue contained in a color.
Display>Shading Controlling the Appearance of Light on Surfaces
The Display>Shading command controls the way light interacts with surfaces displayed in
shaded rendering.
PART 2
Basic Functions
Texture Gives a textured appearance to surfaces. For smooth surfaces

the texture = 0, a value of 1.0 on the slidebar makes the
surface look rough.
Transparency Controls the amount of light that passes through a shaded
object. If transparency = 0, no light passes through and the
object is opaque, at a value of 1.0 the object becomes totally
transparent.
Specular Reflection Sets the degree of light reflection in an object’s specular region,
the area of the surface that is normal to the light source. If this
value = 1, all light will be reflected in the specular region.
Diffuse Reflection Controls the degree of reflection throughout the surface of
the whole object. At higher values more of the surface area
will be lighted. If this setting is low and the specular
reflection is high, the object will appear brightly lit where the
light is normal to the surface then the light will dissipate all
over the surface.
Highlight Size Illustrates the relative sizes of specular regions on surfaces.
Specular Color Specifies whether the color of the object or the color of the
light source will affect the color of the specular area.
Display>Light Source Managing the Illumination of Surfaces

CHAPTER 8 3
Display Control
With the Display>Light Source command you can create new light sources and control the light
that affects the shading of surfaces.
Post/Unpost Lists all light sources defined in the database and highlights
Light Sources 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.
Target Light Source Identifies the light source selected for modifications.
Create Creates a new, named light source. Displays a subordinate
dialog box, in which you enter the name and select the type
of the light source.
PART 2
Basic Functions
Delete Deletes a selected light source.

Light Source
Attributes
Move with Model If this toggle is on the light source maintains its orientation
relative to the model even if the view undergoes
transformations., such as panning or rotation.
Show Direction IconIf this toggle is on the cone-shaped symbol of
the light source will be drawn at its specified
location. The light originates at the tip of the
cone and travels out at the base in the direction
aligned with the cone’s axis of symmetry.
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).
Attenuation Applied to spot lights only, it controls the change in intensity
based on the distance of the light source from the object.
Opposing Light When displaying surface entities, for each posted light source
Sources an opposing light source is created to illuminate those faces
whose surface normals point away from the light source.
CHAPTER
Preferences
9
■ Preferences Concepts and Definitions
■ The Preferences Menu
■ Preferences Commands
PART 2
Basic Functions
9.1 Preferences Concepts and Definitions

Preferences establish parameters that affect an entire modeling and analysis process. Whenever
you start a new database, the New Model Preferences dialog box is displayed in which you can
set certain initial parameters for the model (for more information, see Modifying Preferences
(p. 55)). As you continue your work, you can specify additional preferences in the areas of
graphic displays, geometric construction, and finite element modeling and analysis. Some
options you choose in the Preferences menu are applied immediately, others, however will not
take effect until after you exited the current work session and restarted MSC.Patran.
Several preferences have their equivalents in specific application commands where you can
override the preferenced parameter. The override, however, will apply to that one instance only,
for subsequent operations the parameter will return to its default value as defined in the
Preferences menu. For example, the Preferences menu establishes a default construction plane.
In the course of building a model, however, you may select a different construction plane for
placing a circle. Once the circle has been created, the construction plane will revert to its
Preferences menu default. If all later geometry is to be located relative to the newly selected
construction plane, consider changing the default in the Preferences menu.
Analysis Codes
Analysis codes are the finite element programs you use to perform the analysis. Possible analysis
codes include MSC.Nastran (default), MSC.Marc, and various MSC.Patran analysis codes, such
as Thermal, FEA, and Dytran. Additionally, ABAQUS, ANSYS, LS-DYNA3D, PAMCRASH, and
SAMCEF may also be accessible. The analysis code you pick here depends on what is available
at your site (for obtaining a list of available codes, see The PATRAN Command Language
(PCL) Introduction (Ch. 2) in the PCL and Customization Manual).
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
• material property definitions
• applicable loads and boundary conditions
• code-specific forms in the Analysis application.
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, MSC.Patran will transfer as much code-specific data as
possible to the new code according to the Preference Mapping option you select.
CHAPTER 9 3
Preferences
Preference Mapping
MSC.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 MSC.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, mpc’s) 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.
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 MSC.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 (p. 41)) 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 MSC.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.
PART 2
Basic Functions
Model Units
The vehicle that MSC.Patran uses to create solid geometry is a modeler named Parasolid.
Parasolid assumes model units in meters. Although MSC.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 (p. 136)). The default scale factor is set in the Preferences
menu.
CHAPTER 9 3
Preferences
9.2 The Preferences Menu

The commands of the Preferences menu define global parameters that affect the entire modeling
and analysis process.
Menu Conventions
A menu item with ellipses (...) attached to it calls up an additional dialog box in which you enter
further data.
Preferences
Analysis...
Global...
Graphics...
Mouse...
Picking...
Report...
Geometry...
Finite Element...
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 MSC.Patran
file management and by certain analysis code interfaces.
PART 2
Basic Functions
Global... Specifies the following globally significant parameters.

• Enables or disables the “revert” operation.
• Provides options for the display of warning messages
when certain conditions exist.
• Designates a previously defined coordinate frame as
default for model construction (see also Geometry
Modeling, Chapter 3, p. 59).
• Selects the default construction plane within the
specified coordinate frame (see also Geometry
Modeling, Chapter xx).
• Sets the global tolerance value.
Graphics... Controls certain graphic display parameters:
• Manipulates view settings (fits views, locates view
centers).
• Specifies whether hardware rendering will be used for
the display of shaded images.
• Defines highlight colors to be used to identify entities
selected for an operation and to identify entities
associated with an error condition.
• Selects the type, size, and color of markers used in
geometry and in FEM (e.g., in equivalencing).
Mouse... Programs the middle mouse button to perform view
transformations, such as rotation, pan, or zoom.
Picking... Controls the way entities may be selected from the screen.
Report... Specifies the format of numerical entries in the results output
file.
Geometry... Selects the convention followed in representing geometric
entities and some of their attributes in the database.
Finite Element... Controls certain meshing characteristics and attributes
associated with equivqlnced nodes.
CHAPTER 9 3
Preferences
9.3 Preferences Commands

The following is a detailed description of the commands and dialog boxes that manage global
preferences.
Preferences>Analysis Selecting/Changing the Analysis Code and Type
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 MSC.Patran database.
Analysis Code Specifies the analysis program used for analyzing the model.
Analysis Type Identifies the type of analysis that will be performed.

Input File Suffix Displays the file name extension used by the analysis code to
identify a finite element input data file.
Output File Suffix Displays the file name extension used by the analysis code to
identify a finite element result (output) data file.
PART 2
Basic Functions
Changing the Analysis Preference

If you elect to change the analysis code during the modeling process, the Analysis Preference
form will include options for mapping code-specific data from the original analysis code to the
new analysis code.
Preference Mapping
Mapping Using PCL generated mapping tables, you can convert many of the
Functions 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.
Legacy Mapping Legacy Mapping converts the most obvious code-specific definitions
such as, elements types, and basic loads and boundary conditions, to
the corresponding definitions in the new analysis code. The more
complex parts of the model such as, mpcs, shell thicknesses, material
orientations, and nonlinear material models are not converted.
No Mapping Selecting the No Mapping option leaves your database unchanged
when switching to a new analysis code. This option may be
appropriate when simply evaluating the capabilities of alternative
analysis codes, or in a case where your model contains very generic
model definitions.
CHAPTER 9 3
Preferences
Mapping Functions
MSC.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 MSC.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: Always create a backup copy of your database before beginning the preference
mapping procedure. Information in the MSC.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 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 MSC.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.)
PART 2
Basic Functions
Material Property Mapping Tables

The following steps are used to do material property mapping.
Generating a Material Property Mapping Table

1. Create Materials Spreadsheets for Source/Destination Analysis Codes
Prior to changing the Analysis Preference, type in the command (on the command line):
map_materials.generate_leaflist( )
Change the Analysis Preference and repeat the command above.(You may have to restart
MSC.Patran.)
This command generates three files, or leaflists, in the working directory:
1. CodeATypeMaterials - used to generate the mapping table.
2. CodeATypeMaterials.xls - spreadsheet used to define actual mapping.
If switching from ABAQUS Structural to MSC.MARC Structural, these commands would

generate: “AbaqusStructuralMaterials.xls,” and “MarcStructuralMaterials.xls.”
2. Create Pairs of Source/Destination Material Sets
For each material model in the original code (CodeA) enter a corresponding Leaf Number
(from Code B) that designates what the material model will be translated to in the new code
in the 3rd column, labeled “Maps To Leaf.”
3. Create the Materials Mapping Spreadsheet

Type in the PCL Command (all one line):
map_materials.map_materials(“CodeATypeMaterials”,
”CodeBTypeMaterials”,”CodeAtoCodeBMaterials.xls”)
This command generates the file CodeAtoCodeBMaterials.xls.
CHAPTER 9 3
Preferences
Generating a Material Property Mapping Table

4. Map Material Sets
For each material property, enter the Leaf Numbers from CodeA in the column labeled Old
ID. Selecting which input data boxes should be mapped from Code A to Code B is up to
your judgement and experience.
5. Converting the Mapping Spreadsheet into a PCL Function

Enter the PCL Command:
map_materials.Convert_To_PCL(“CodeAtoCodeBMaterials.xls”,”CodeAtoCodeBMater
ials”)
This generates a file named: CodeAtoCodeBMaterials.pcl. Remember, Code A and Code B
are the exact preference names (without spaces or decimals).
6. Compile the PCL Function
!!COMPILE CodeAtoCodeBMaterials.pcl INTO CodeB.plb
You may choose to test the compilation prior to compiling the .pcl into the CodeB.plb using
the command:
!!COMPILE CodeAtoCodeBMaterials.pcl INTO test.plb
PART 2
Basic Functions
Element Property Mapping Tables

The following steps are used to create element property maps.
Generating a Element Property Mapping Table

1. Create Property Set Spreadsheets for Source/Destination Analysis Codes
Prior to changing the Analysis Preference, type in the command (on the command line - all
one line):
map_properties.create_property_spreadsheet(“Code”,”Type”,
”Filename.xls”)
The “Code” and “Type” are case sensitive with the full name with decimals included and
should be entered exactly as they appear on the Analysis Preference form, for example
“MSC.Marc” and “Structural.” However “Filename.xls” can be whatever you want to
name your property spreadsheet such as “MarcStructuralProps.xls.”
Now, change the Analysis Preference to what you want to map to or from and repeat the
command above.
Keep track of whatever you name the spreadsheet as you will be needing this later.
CHAPTER 9 3
Preferences

2. Create Pairs of Source/Destination Property Sets
A property set is defined by the following information: a dimension, an element type, five
element options (geometric, condensation, laminate, formulation, and dof set), a topology,
two material rules (directionality i.e., materials category and linearity i.e., constitutive
model) and a set of property words. It is this data that is shown in the second section of the
“Property Set Spreadsheet” with the following exceptions. The topology and material rules
are not shown, and only one of the possible dof set element options is shown.
The first and most tedious part of creating a property set mapping is to match “Source”
property sets with “Destination” property sets. You will note that the first two columns in
the “Property Set Spreadsheets” (in the property set and property word sections) are
“Source” and “Destination”. The “Destination” column is just a count for identification. A
mapping pair is created by entering one or more source property set counters in the
“Source” column.
For example, when mapping Abaqus to MSC.Marc consider the first two Abaqus property
sets, which are “Point Mass” and “Rotary Inertia.” In MSC.Marc, translational and
rotational mass are defined by the “Mass” property set. Therefore, we want to translate all
Abaqus “Point Mass” and “Rotary Inertia” property sets to MSC.Marc “Mass” property
sets. This is done, by entering “1,2” in the “Source” column in the MSC.Marc “Property Set
Spreadsheet” on the line containing the “Mass” property set (which happens to be the first
one). This says source property sets 1 and 2 map to destination property set 1.
PART 2
Basic Functions

3. Map Property Words
Property words with the same IDs map automatically, regardless of the name. (The name is
just an analysis code specific label.) Property words with different IDs but the same
meaning (represent the same physics) are mapped like property sets. The counter for the
source word is entered in the “Source” column of the destination spreadsheet. For example,
Abaqus has two thickness definitions, “Shell Thickness -- ID 1080” and “Membrane
Thickness -- ID 1081”. These two words should map to the MSC.Marc property word
“Thickness -- ID 36”. This is done by entering “72,73” in the “Source” column in the
MSC.Marc “Property Set Spreadsheet” on the line containing “Thickness – ID 36” (which is
the 26th property word). So we have mapped source property word 72 and 73 to destination
property word 26.
CHAPTER 9 3
Preferences

4. Create the Property Set Mapping Spreadsheet
Type in the PCL Command:
map_properties.create_mapping_spreadsheet(“Filename1.xls”,”Fil
ename2.xls”,”CodeATypetoCodeBTypeProps.xls”)
This spreadsheet shows each pair of source and destination property sets along with their
source and destination property words. This block of data defines how the data will map.
The first two lines of each block show the source and destination property set name, element
type and element options. Following this are the source and destination property word
maps. At this point, the mapped words include words with identical IDs and words that
have been specifically mapped.
Not all source property words will map. (In this case, the corresponding cell in the
“Destination” column is blank.) If the data cannot be used by the destination Analysis Code,
it can be ignored. It will remain in the database, but will not be visible to the user. However,
queries for element property data by forward translators, etc. will have to account for
property words that are “unknown” to that Analysis Code. This is also true for unmapped
property sets.
5. Make Additional Mappings
Some property words may not map in a general way. For example, you may want a
property word to map only for a specific property set. In this case, you can paste the
destination word into the appropriate cell next to the source word. Note that the spelling of
the property word and the accompanying ID must be accurate. The double hyphen is used
as a delimiter and is therefore also important.
If a complex translation is required, the general function can be used. See the section below
describing the use of the general function.
Conflicts
There are possible conflicts with acceptable data types or data values. For example, the
source Analysis Code allows either a real or a real nodal field to define a specific property
word but the destination Analysis Code only allows a real. Let’s assume we have one of
these property sets to convert and a real nodal field has been used for this property word.
By default, the field will be stored. This can be overridden by entering “No” in the column
labeled “Store Incorrect Datatype”. Likewise, if the source Analysis Code does not impose
a limit on a specific property word, but the destination Analysis Code does, the data will be
mapped unless directed otherwise. As mentioned above, queries for element property data
by forward translators, etc. will have to account for this inconsistent data. An easy way to
identify these inconsistencies is to do a “Modify” (with no changes) on each property set
after the mapping is done. Any data consistency problems will be flagged by Patran by an
error or warning message.
PART 2
Basic Functions

6. Defining General Function Tags
The property mapping capability provides access to the mapping process via a specified
function. This function is declared in the “Property Set Mapping Spreadsheet” in the cell to
the right of the cell containing “GENERAL FUNCTION”. If a general function is specified
and it exists, it will be called at several points in the process. Specifically, it is called at the
beginning and end of the entire property mapping process, at the beginning and end of each
“source” property set and following each “source” property word, provided that a “tag”
has been specified. (The “tag” is not required for the two calls at the beginning and end of
the entire property mapping process.)
You’ll note in the “Property Set Mapping Spreadsheet” following each source and
destination property set pair are cells containing “Initial Property Set Function Tag” and
“Final Property Set Function Tag”. If data is entered in the cell to the right of the cell
containing “Initial Property Set Function Tag”, then when this specific source property set
is encountered in the database, the general function is called and is passed the current state
add the specified tag.
This function can then perform whatever actions are required including calling back to the
“map_properties” class for current data on the property set in hand. (See below for a list of
available functions.) Note that if no “Point Mass” property sets exist in the database, this call
will not be made.
Likewise, if a “Property Word Function Tag” is provided and that source word is
encountered, the general function is called. Note that these tags are specified in the column
to the right of the “Destination Word” column in the “Property Mapping Spreadsheet”.
Also note that “Property Word Function Tags” can only be specified for “Source Words”.
7. Converting the Mapping Spreadsheet into a PCL Function
Type in the PCL Command:
map_properties.create_final_map("CodeATypetoCodeBTypeProps.xls",
"CodeATypetoCodeBTypeProps.pcl",”FunctName”)
Recall that Code A and Code B are the exact preference names (without spaces or
decimals). “FunctName” is the name of the function that will be called to do the property
mapping.
For the ABAQUS to MARC Change, this command generates the PCL file,
“abatomarcprops.pcl” which contains the function “abatomarcprops.”
This function consists of the spreadsheet data loaded into pcl variables, which are then
passed to the element property mapping logic. This function needs to be compiled and
made accessible to MSC.Patran. The suggested location is the analysis plb, which in this
case is “mscmarc.plb.”
Note: 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 considered in the “Property
Set Spreadsheets”. This could pose some problems for logic accessing the mapped
element property set data, such as forward translators.
CHAPTER 9 3
Preferences
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, 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 ( )
PART 2
Basic Functions
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

Let’s 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, let’s 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 )
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
CHAPTER 9 3
Preferences
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 ( state, tag )
STRING state[ ]
STRING 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. We’re
$ 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 doesn’t 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.
word = "Transl Inertia, X"
map_properties.create_dest_word_rval ( word, mass, datatype, field_id)
word = "Transl Inertia, Y"
word = "Transl Inertia, Z"
END IF
END SWITCH
CASE ( “Start Region Set Mapping” )
CASE ( “End Region Set Mapping” )
CASE ( “Start Property Set Mapping” )
CASE ( “End Property Set Mapping” )
END SWITCH
END FUNCTION
PART 2
Basic Functions
Preferences>Global Controlling Global Operational Parameters
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 MSC.Patran completes, delete after
MSC.Patran completes, or to be prompted as to whether or
not to save the session file.
Enable Revert Controls the use of the File>Revert command (see
Operation File>Revert (p. 61)). If ON, the revert operation will be
enabled. This selection does not have immediate
consequences; to have it take effect, you must exit the current
work session then reopen the database.
Warning Message Picks the type of feedback you receive whenever MSC.Patran
Options needs to issue a warning.
CHAPTER 9 3
Preferences
Default Coordinate Selects an existing coordinate frame as the default.

Frame
Default Construction Specifies the default construction plane in the selected
Plane coordinate frame.
Global Model Defines the maximum distance within which two like entities
Tolerance are said to be coincident (default is 0.005).
Preferences>Graphics Specifying Graphic Display Parameters
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).
Automatic View
Settings
Auto Extend If ON, automatically fits the view whenever new entities are
created and they fall outside the viewport.
Auto Fit View If ON, automatically fits the view after any view rotation.
Hardware Rendering If ON, rendering will utilize a hardware device.
PART 2
Basic Functions
Disable Auto If ON, the graphics display does not update after each
Updates 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 Identifies a second color in case the primary highlight color is
already in use.
Error Color Selects a color to highlight entities associated with an error
condition.
Marker Options Picks the type, color, and size (in pixels) of markers.
Preferences>Mouse Programming the Mouse for View Transformations
With the Mouse Preferences options you can program the middle mouse button to perform
incremental view transformation functions.
CHAPTER 9 3
Preferences
Middle Mouse Button

Map
Rotate X/Y Rotates the view about the global or screen X and Y axes.
• About X
move the mouse up to rotate clockwise
move the mouse down to rotate counterclockwise.
• About Y
move the mouse right to rotate clockwise
move the mouse left to rotate counterclockwise.
Rotate Z Rotates the view about the global or screen Z axis.
move the mouse right to rotate clockwise
move the mouse left to rotate counterclockwise.
Pan X/Y Pans the view in the screen X or Y direction.
move the mouse left or right to pan left or right
move the mouse up or down to pan up or down.
Zoom Zoom the view of the model in (enlarge) or out (reduce).
move the mouse left to zoom in
move the mouse right to zoom out.
Transform in If ON, view transformations are performed in wireframe
Wireframe even if the model is rendered in shaded or hidden line mode.
Transform with EdgesIf ON, and the toggle above is OFF, view transformations are
performed in shaded mode and solid edges are shown.
Mouse Tracking This parameter is meaningful in hardware graphics mode
only. If ON, partial redraws will be created as rendering tries
to catch up to the mouse motion (in software graphics mode
this happens automatically).
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 Brings up a subordinate dialog box in which you can set the
Options rotation angle increment, pan factor and zoom factor.
PART 2
Basic Functions
Rotation Displays the rotation angle in degrees. Each mouse

movement will rotate the view by that increment.
Model/Screen Rela- Selects whether the rotation axis specified is to be interpreted

tive as a global axis or a screen axis.
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.
Preferences>Picking Parameters of Interactive Screen 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 (p. 29)).
Note: The selections you make in this dialog box will not take effect immediately. After
selecting the parameters, exit MSC.Patran. The choices you made will be saved in a
file (settings.pcl) that will activate the new parameter settings when you restart
MSC.Patran.
CHAPTER 9 3
Preferences
Single Picking These options apply when you select single entities.
Centroid Picks the entity whose centroid is closest to the center of a
“pick box”.
Entity Picks the entity at which the cursor is pointing.
Entity Picking In entity picking mode, selects the shape of the cursor. In
Cursor centroid picking mode the cursor always remains an arrow.
Rectangle/Polygon These options apply when you select a number of entities at
Picking (Multiple) the same time.
Enclose entire entityAn entity is selected only if it is totally inside the selection
rectangle or polygon.
Enclose any portion An entity is selected even if it is only partially inside the
of entity selection rectangle or polygon.
Enclose An entity is selected only if its centroid is inside the selection
centroid rectangle or polygon.
PART 2
Basic Functions
Cycle picking form In entity picking mode:

lists the names of two or more entities that overlap at the
place the cursor is touching. You can then accept the
highlighted selection, or pick the entity you wanted to
target.
In centroid picking mode:

lists all entities whose centroid lies near the point where
the cursor is touching.
Horizontal Select If ON, the Select Menu (Picking Filters) will be horizontally
Menus placed. Note that this is one of those parameters that will
take effect only in the next MSC.Patran work session.
Show Picking Icons 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 These options control the highlighting of entities prior to
selection as the cursor passes over them.
Label Highlighting If ON, entity labels will be highlighted along with the
entities.
Entity Highlighting If ON, entities will be highlighted as the cursor passes over
them.
Node/Point Marker Controls the size of the marker that is highlighted when the
Size cursor passes over a point or a node.
CHAPTER 9 3
Preferences
Preferences>Report Formats of Numerical Entries in Analysis Result Reports
The Preferences>Report command controls the format of numerical entries in reports that
output finite element analysis results.
Real Numbers
Floating Point Outputs result data in floating point format.
Scientific Notation Outputs result data in scientific notation format.
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 Deci- Defines the number of decimal digits in a numerical entry. In
mals scientific notation format, this number defaults to the
maximum value.
Integers Selects the number of integers the numerical entries may
contain in the tabular output.
Spacing Selects the number of spaces between numerical entries in
the tabular output.
PART 2
Basic Functions
Preferences>Geometry Parameters for Representing Geometric Entities
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 MSC.Patran system.
Exportable to If ON, curves, surfaces, and solids will be created as

Neutral File parametric cubic geometry.
Solid Origin Location 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 (p. 40)), because the
hyperpatch origin location must be set according to whether
the session file came from MSC.Patran or PATRAN 2.
MSC.Patran The origin location will be determined according to
MSC.PATRAN convention.
PATRAN 2 The origin location will be determined according to
PATRAN 2 convention.
NURBS Accelerator If ON (default), NURBS (Non-Uniform Rational B-Spline)
curves and surfaces will be converted to piecewise
polynomials without introducing any approximations. This
format accelerates evaluation of geometry and provides
increased performance.
CHAPTER 9 3
Preferences
Auto Update Solid If ON (default), the mesh, loads, and boundary conditions
Mesh/LBC applied on a solid model will automatically update after you
performed a Boolean operation or other editing applications,
namely edge blend, imprint, or shelling.
If you turn this parameter OFF, the update action becomes a
selectable item in the Geometry>Edit>Solid command
dialog boxes for the above editing functions.
Geometry Scale Because the model unit of Parasolid geometry is meter, a scale
Factor factor is applied to MSC.Patran geometric extents so that
they can be expressed in the appropriate Parasolid
dimensions. The default scale factor is 39.37, the equivalent
of one meter in inches. Other possible scale factors are:
If you select Customize, an arbitrary scale factor must be

entered into the Geometry Scale Factor databox.
Note that when importing Unigraphics (see Importing
Unigraphics Files (p. 127)) and Parasolid files (see
Importing Parasolid (xmt) Files (p. 133)), an existing scale
factor in those files may override this global parameter.
PART 2
Basic Functions
Preferences>Finite Element Setting FEM Parameters
Two sets of parameters are defined in the Preferences>FEM dialog box. The first is the so-called
node/edge snap angle that controls whether a node will snap to a vertex where a composite edge
of a surface changes its slope. With the other set of parameters you specify the way values of
discreet FEM fields, that associate loads and boundary conditions (LBCs) with nodes, are treated
after coincident nodes have been equivalenced in the finite element model.
CHAPTER 9 3
Preferences
Node/Edge Snap Controls the angle that determines whether a node will snap to a vertex
Angle 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
Slope Angle > 30o Slope 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 Specifies which values of discrete FEM fields will be associated with a
Equivalence Options node that “survived” after coincident nodes have been equivalenced.
PART 2
Basic Functions
Displace Presents various options for associating displacement values with the
surviving node.
• 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 deleted during the equivalencing process.
Vector Presents the same options for associating vector (e.g., force) values with
the node that survived the equivalencing process
Scalar Presents various options for associating scalar values (pressures and
temperatures) with the node that survived the equivalencing process.
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 By default, proximity checking is turned on. Each of these settings is
Association saved in the database and are restored each time the database is
opened.
Additional Geometry to FEM Evaluation Check
Uncheck this box if you do not wish to use the Edge Length Tolerance
or Elem Face/Surface Normal Angle Tolerance
Edge Length The proximity check is measured in percent of the average edge length
Tolerance (0-100%) of the element face in question. The element edge lengths are
computed, averaged and then factored by a percentage that may vary
from 0% to 100%. If the node or centroid is within this distance of the
loaded geometry solid face, the point is accepted. The default value is
set to 20%.
Elem Face/Surface Normal Angle Tolerance (0-90 Deg)
The angle may vary from 0 to 90 degrees and the default is 30 degrees.
Check Adjacent Turn this check box ON or OFF to turn proximity checking ON or OFF.
Geometry
CHAPTER 9 3
Preferences
Preferences>Main Form Controlling the Appearance of the 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 MSC.Patran
Main Form Preferences

Add latest history line at top
Popup applications switch

(default: right mouse button)
Small screen layout
Save visible history line count
Close
Add Latest History Adds latest history line to be written at top of history list
Line (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.
Popup Applications Causes application switch to be removed from Main form
Switch (allowing a larger viewport) and displayed as a popup. As a
default, this is mapped to the right mouse button and can be
activated by clicking almost anywhere in a MSC.Patran form
or in the history list on the Main form. This will not activate
with the cursor on the menu bar, the toolbar, on an icon or in
a select databox. Try several locations to see the best places
for using this option.
Small Screen Layout Causes initial orientation of Main form and viewport to fit
better on a small computer screen so that forms do not
extend off the screen.
Save Visible History Allows any changes made during the current session to the
Line Count 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.
PART 2
Basic Functions
CHAPTER
Tools
10
■ Tools Concepts and Definitions
■ The Tools Menu
■ Tools Commands
PART 2
Basic Functions
10.1 Tools Concepts and Definitions

The Tools menu commands provide easy access to a number of self-contained add-on
MSC.Patran features, as well as to some specialized application modules, all of which are
optionally purchased items and require their own software licenses.
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 entity’s 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.
CHAPTER 10 3
Tools
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.
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 contents of
another list.
• 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.
PART 2
Basic Functions
Mass Properties
The MSC.Patran Mass Properties module is a tool with which you can calculate the mass
properties of geometric and finite element models. The process may be applied to an entire
model or to any of its subregions. For an overview of the theoretical background of mass
properties calculations, see Summary of Mass Properties (p. 498).
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:
1. about the Z-axis by γ degrees
2. about the original Y-axis by β degrees
3. 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:
1. about the Z axis by γ degrees
2. about the newly positioned X axis by β degrees
3. about the newly positioned Z axis by α degrees.
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 MSC.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.
CHAPTER 10 3
Tools
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 MSC.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,
MSC.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.
Mass Properties and Elements

Mass properties can be calculated for the following element types:
• constant and variable-thickness plates and shells
• general beams and rods with constant or variable cross-sectional areas
• tapered beams with constant cross-sectional areas
• beams defined not with section properties but with cross-sectional data,
for example, I-beams with given web and flange dimensions.
Mass property calculations are based on the assumption that all beam and shell element offsets,
as well as concentrated mass offsets, are zero. If an entity with an offset is referenced, a warning
message will appear.
PART 2
Basic Functions
Weight Factors
Mass properties of shell elements are calculated by treating the thickness as a weighting factor
and assuming that all mass lies in the surface of the shell. Similarly, when calculating the mass
properties of beam elements, the cross-sectional area enters as a weighting factor with all mass
assumed to lie in the locus of the one-dimensional beam.
Consequently, mass properties calculated for these entities will be slightly different from those
calculated for corresponding 3D solids.
Mass Properties and Fields

For geometric entities, field properties (e.g., cross-sectional area) are integrated over the entity
regardless of the property’s value type. For FEM entities, a field property is evaluated at the
centroid of the entity if the value type of the property is real scalar, and is integrated over the
entity if the value type is element nodal.
Discrete FEM fields can be used only for real scalar properties of FEM entities.
Mass Properties and Materials

MSC.Patran can calculate mass properties of models made of composite materials. If a composite
property, such as laminate thickness, is defined both as an element property and as a material
property, the element property value will be used.
Material densities defined with fields cannot be used for mass property calculations.
Analysis Model Types and Mass Properties

When mass properties are calculated, it is assumed that all entities in a model conform to the
selected analysis model type. If an entity is geometrically inconsistent with the analysis type, it
will not be considered for the mass properties calculations. For example, if the analysis model is
“2D Axisymmetric”, a surface that does not lie in the axisymmetric modeling plane will be
rejected.
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.
CHAPTER 10 3
Tools
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. MSC.Patran calculates the mass of the equivalent 1D hoop by multiplying the
input mass by 2πr . 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 2πr .
The “2D Axisymmetric” option cannot be used to calculate mass properties of non-axisymmetric
cyclic-symmetry 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.
PART 2
Basic Functions
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.
CHAPTER 10 3
Tools
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.
PART 2
Basic Functions
Design Studies and Design Optimization

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.
Design Studies
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 MSC.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.
Results 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.
CHAPTER 10 3
Tools
Rebar Definitions
With the Rebar Definitions application you can create and display Abaqus beam shapes in
MSC.Patran
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.
MSC.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.
MSC.Patran Analysis Manager

The MSC.Patran Analysis Manager provides convenient and automatic means to submit,
monitor, control, and perform all other management tasks required by analysis jobs running
either locally or on remote networked systems.
PART 2
Basic Functions
10.2 The Tools Menu

The commands of the Tools menu invoke various self-contained add-on MSC.Patran features, as
well as the specialized application modules.
Menu Conventions
A menu item with ellipses (...) attached to it calls up an additional dialog box in which you enter
further data.
The Tools menu functionalities are described below in the order in which they appear.
List Creates and manipulates lists with which you can reference a
number of entities for input in commands that accommodate
multiple entity selection.
Mass Properties Calculates mass properties either of entire geometric and
finite element models or of their subregions. Displays
graphic symbols related to mass properties and outputs
report files and summary spreadsheets.
Beam Library Creates and manages dimensioned cross section shapes to be
associated with beam elements. Calculates section properties
for any selected beam cross section.
Model Variables Creates and manages variable parameters to be used in
design studies and design optimization.
Design Study Creates and manages design study cases in which the
functions necessary for design optimization are defined.
MSC.Fatigue Invokes the MSC.Fatigue application module.
Results Templates Creates and manages templates that store collections of
settings for displaying, plotting and reporting analysis
results.
CHAPTER 10 3
Tools
Results Plot Sets Creates and manages templates that store collections of
settings for displaying, plotting and reporting analysis
results.
Rebar Definitions Creates and displays Abaqus beam shapes in MSC.Patran.
MSC.Laminate Implements the MSC.Laminate Modeler application.
Modeler
MSC.Patran Calls up the MSC.Patran Analysis Manager.
Analysis Manager
Rotor Dynamics Opens the Rotor Dynamics form. Only available when
MSC.Nastran is set as the analysis type.
Experimental Data Used to curve fit experimentally derived raw elastomeric
Fitting material data and fit a number of material models to the data.
Pre Release Provides access to pre-release capabilities in MSC.Patran.
PART 2
Basic Functions
10.3 Tools Commands

The following is a detailed description of the commands and dialog boxes that are referenced in
the Tools menu.
Tools>List>Create Creating Lists
The Tools>List process provides access to the commands with which you can generate and
manipulate lists.
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.
Attributes of FEM Entities. Common attributes of FEM entities include sharing one or more
coordinate location values (applies to nodes only), material properties, element properties
(applies to elements only), or analysis result values.
CHAPTER 10 3
Tools
Model Specifies the model definition, Geometry or FEM, that

defines the type of selectable objects.
Object Identifies the entity types to be include in the list. The entity
designations displayed when you press this button depend
on the Model type you selected.
Method Selects the criteria by which an entity’s inclusion in the list
will be determined (Attribute or Association).
PART 2
Basic Functions
Attribute Names the possible common attributes that determine which

entities will be included in the list.
• Select --entities are included as they are selected
with the cursor or their names and IDs
are entered in the textbox.
• Coord Value --entities are included if one, two, or three
of their coordinates are equal, greater
than, or less than a given value, or fall
between specified upper and lower
boundaries.
• Fringe Value --entities are included if they share a
specified result 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 Places the resulting list in a form titled “List A” or “ListB”.
(“A” or “B”)
Coordinate Value/Coordinate Frames

If you are creating a list based on nodal coordinate values, you can specify any predefined
coordinate frame in which the coordinate values will be read. Because a coordinate frame may
be rectangular, cylindrical, or spherical, the dialog box entries may be X, Y, Z; R, T, Z; or R, T, P.
In cylindrical and spherical coordinate frames the tolerance values will be in degrees.
Range Specifications and Tolerances

If the attribute you have selected is either a coordinate value or a fringe value, additional options
include specifying how the value range will be calculated as well as a tolerance within which these
values must fall.
Specifying the Range. The dialog box will display the following range specification options
symbols:
•= the attribute must equal a certain value.
•> the attribute’s value must be greater than a specified number.
•< the attribute’s value must be less than a specified number.
• || the attribute’s value must be between two given boundary limits.
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.
CHAPTER 10 3
Tools
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 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).
PART 2
Basic Functions
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.
Remove from Group Removes listed entities from a group.
CHAPTER 10 3
Tools
Highlight Highlights listed entities on the screen.

Clear Removes all listed entities from the contents box.
Previous Restores the contents of the textbox to what it was before the
current list was applied.
Tools>List>Boolean Boolean Operations on Lists
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
contents of another list.
• Intersection --outputs a resultant list obtained by finding members

that are common to both list A and list B.
‘listc’ Contents Displays the list that resulted from the Boolean operation.
Clear Removes all listed entities from the contents box.
PART 2
Basic Functions
Add to Group Creates a new group for the listed entities or adds them to an
existing group.
Remove from Group Removes listed entities from a group.
Replace A Transfers the contents of List C to List A.
Replace B Transfers the contents of List C to List B
Highlight Highlights listed entities on the screen.
Tools>Mass Properties Calculating Mass Properties
The Tools>Mass Properties application enables you to calculate the mass properties of two-or
three-dimensional geometric and finite element models. The calculations extend to entire
models or any of their subregions.
The numerical results of mass properties calculations are output in a spreadsheet along with an
optional graphic display of certain related symbols, such as the principal axes in the center of
gravity. In addition, you can request that the results be written in a formatted report file.
CHAPTER 10 3
Tools
Dimension Selects the dimensionality of the analysis

model. Models may be defined as two-
dimensional or three-dimensional.
• 3D--this model may include elements of all dimensions.

Mass properties of 1D and 2D elements are calculated
with cross-sectional areas and element thicknesses
specified as element properties.
• 2D axisymmetric--this model may contain 0D, 1D, and
2D elements (concentrated masses, shells, and
2D-solids)
• 2D plane stress and 2Dplane strain--these models can
consist of only 0D and 2D elements.
Define Region Displays a secondary dialog box in which you can specify the
geometric or finite element model, or a portion of the model,
for which the mass properties will be calculated.
Relative to Selects the coordinate frame in which the mass properties are
Coordinate Frame calculated. The coordinate frame must be rectangular.
Density/ Controls applicable density and mass values.
Concentrated Mass
• Use Element Properties (default)
applies the density specified for the element material
and the mass entered as element property.
• 1.0/0.0
overrides the defaults with a density value of 1.0
and a mass value of 0.0.
Thicknesses/Areas/ Specifies additional element properties.
NSM For three-dimensional models and 2D axisymmetric models
you can use previously defined element properties. For plane
stress and plane strain models, however, thickness and area
default to 1.0 and non-structural mass defaults to 0.0.
Plot Principal Axes Displays the principal axes at the center of gravity.
at CG
Create Principal Creates a coordinate frame that is aligned with the principal
Coordinate Frame axes of inertia.
Write to Report File Writes the calculation results to a formatted report file.
Mass Properties Redisplays the spreadsheet that contains the last calculated
Display mass properties.
PART 2
Basic Functions
Defining the Region for Mass Properties Calculation

When you pick the Define Region button, the following form will appear; in it you can specify
the geometric or FEM entities for which the mass properties are calculated.
Region Specifies the region for which mass properties

calculations will apply.
• Group--mass properties are calculated for the region

defined by a selected group of entities.
• All--mass properties are calculated for all the
appropriate included entities on the screen.
• Selected--mass properties are calculated for a region
defined by selected entities.
CHAPTER 10 3
Tools
Include Specifies the type of entities that can be included in the

selected region. Inclusion options are:
• Geometry--only geometric entities may be selected.
With this option, property data used for calculations must be
associated with the model geometry.
• FEM--only FEM entities may be selected.
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.
Geometric If your selection for Region is Selected, this textbox will
Entity List/ display the names of entities as you select them.
The title of the textbox will be appropriate to the entity type
Finite Element you selected under Include (Geometry, FEM, Both).
Entity List/
Entity Selection
Display Method Specifies how mass properties are calculated and displayed.
• Summary • Mass properties are calculated for the entire region and
a summary of the results is displayed in the spreadsheet
or report file.
• Group • Mass properties are calculated for selected group(s) and
are displayed for each group in the spreadsheet and
report file.
• Entity • Mass properties are calculated for selected entity(s) and
are displayed for each entity in the spreadsheet and
report file.
Displaying Mass Property Results

After mass properties have been calculated the results will be displayed in a spreadsheet. The
format and contents of the spreadsheet will depend on what you selected in the following dialog
box entries:
• Region (in the Define Region form)--Group, All, Selected (see Region (p. 374))
PART 2
Basic Functions
• Display Method (also in the Define Region form)--Summary, Group, Entity (see
Summary Display Method (p. 376))
• Display Option (in the spreadsheet)--mass, CG, inertia tensors, etc.
Summary Display Method
This display is applicable to all three region definitions (Group, All, Selected). The spreadsheet
displays the summary of mass properties calculated for an entire model, for a group, or for a
region made up of selected entities. The column headings are determined by the display option
you select in the spreadsheet (e.g., “Mass, CG, Principal Inertias). Certain columns consist of
three rows, these show the X, Y, and Z component of the property listed at the top of the column.
CHAPTER 10 3
Tools
Group Display Method

This display is applicable when the region is defined either as All or Group. The spreadsheet
displays the mass properties calculated for selected groups. The column and row definitions are
the same as in the 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.
Entity Display Method

This display is applicable only when the region is defined with the “Selected” option and you
select individual elements for the calculation. In the spreadsheet, the row definitions are the
same as in the summary spreadsheet, except that a three-row output (X,Y, Z components) is now
displayed for each element, and the first column of the first row of each also contains the name
of the element.
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).
PART 2
Basic Functions
Mass, CG, Principal The first six columns are:

Inertias, and Others 1. Center of gravity (CG) in the Cartesian coordinate
frame
2. CG in a user-specified coordinate frame
3. Principal inertias at the CG in decreasing order
4. Corresponding radii of gyration
5. Mass
6. Volume.
Inertia Tensor Columns 1, 2, and 3 contain the inertia tensor in a user-
specified coordinate frame relative to the coordinate frame
origin. The last three columns contain the inertia tensor in the
reference Cartesian frame relative to its origin.
Inertia Tensor The first three columns contain the inertia tensor at the center
at CG of gravity in a user-specified coordinate frame. The last three
columns contain the inertia tensor at the CG in the reference
Cartesian frame.
CHAPTER 10 3
Tools
Principal Directions in • Columns 1-3

User-Specified Frame three mutually orthogonal principal direction unit
vectors at the CG, given in a user-specified coordinate
frame in the order of decreasing principal inertias;
• Column 5
triad of 3-2-1 space fixed angles (see also on Mass
Properties (p. 356)) that rotate a user-specified
coordinate frame into the principal inertia frame at the
CG;
• Column 6
the triad of 3-1-3 body-fixed angles (see also on Mass
Properties (p. 356)) that rotate the user-specified frame
into the principal inertia frame at the CG.
Principal Directions in • Columns 1-3
Ref. Cartesian Frame three mutually orthogonal principal direction unit
vectors at the CG, given in the reference Cartesian frame
in the order of decreasing principal inertias;
• Column 5
triad of 3-2-1 space-fixed angles (see Mass Properties
(p. 356)) that rotate the reference Cartesian frame into
the principal inertia frame at the CG;
• Column 6
triad of 3-1-3 body-fixed angles (see Mass Properties
(p. 356)) that rotate the reference Cartesian frame into
the principal inertia frame at the CG.
Reporting Mass Properties Results

Mass Properties reports are written in standard MSC.Patran report file format. A report will
contain all calculated mass properties, a list of included entities, and a list of rejected entities.
Follow these steps to output a Mass Properties report:
1. Complete all input in the Mass Properties dialog box
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.
PART 2
Basic Functions
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 haven’t 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 MSC.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.
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.
CHAPTER 10 3
Tools
Report File Comments
Center of Gravity. Center of Gravity coordinates are presented in Cartesian, as well as in a

user-defined coordinate frame.
PART 2
Basic Functions
Principal Inertia Quantities. Principal inertias and corresponding radii of gyration are listed in
descending order.
Inertia Tensor in Coordinate Frame. These inertia tensor components, in both the Cartesian
and a user-defined coordinate frame, are given relative to the origin of their respective
coordinate frame.
Inertia Tensor at CG. These inertia tensor components, in both the Cartesian and a user-
defined coordinate frame, are given at the center of gravity.
Principal Direction Vectors. The principal direction vectors, given in both the Cartesian and a
user-defined coordinate frame, are listed in the order of decreasing principal inertia. Each set of
the three principal direction vectors forms an orthogonal matrix.
Rotation Angles. Space-fixed and body-fixed rotational angles (see Mass Properties (p. 356))
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.
Tools>Beam Library Using the Beam Library
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,
MSC.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.
CHAPTER 10 3
Tools
Creating Standard Beam Cross Sections

When you select Tool>Beam Library, the following dialog box form will appear:
Action Creates, modifies, or deletes a beam cross section shape.

Object Selects Standard or Arbitrary for the shape definition.
Method Regardless of the analysis preference, you can only select
standard shapes supported by MSC.Nastran or MSC.Dytran.
Existing Sections Lists the names of previously defined beam cross sections.
New Section Name Specifies the name of the new beam cross section.
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.
PART 2
Basic Functions
Spatial Scalar Lists the name of existing spatial fields that you may apply
Fields for one or more dimensions if the cross section varies along
the length of the beam.
Calculate/Display Displays the dimensioned cross section along with calculated
section properties and symbols.
Write to Report File Outputs section properties to a formatted report file.
Cross Section Display

After entering the required dimensions, press Calculate/Display to calculate beam properties
and display the following information.
Variable Cross Sections

If you selected one or more spatial fields for dimensions, MSC.Patran recognizes that the beam
cross section will vary and the dialog box will display additional items to provide a location for
evaluation along the length of the beam. This location is defined either with a parametric
function or with XYZ coordinates.
CHAPTER 10 3
Tools
Spatial Scalar Lists the name of existing spatial fields that you
Fields may apply for one or more dimensions if the
cross section varies along the length of the beam.
To enter the field value, first click in the
dimension databox then pick the field name.
Location Specification Options:
• Select an Entity and a Parametric Evaluates the variable dimension at a
Location (C1) parametric location of the beam. Move the slider
to the appropriate position between End A
(0.000) and End B (1.000).
• Specify an XYZ Coordinate
Evaluates the variable dimension at a location
specified by XYZ coordinates.
PART 2
Basic Functions
Select a Beam or Curve Identifies the beam element, curve, or edge

or along which the cross section varies. Click in the
textbox and select the entity or enter its ID.
Coordinate If you picked the Specify an XYZ Coordinate
option, the textbox heading changes to
Coordinate. Enter the coordinates of the location
where the cross section is to be evaluated.
Creating Arbitrary Beam Cross Sections Using Boundary Loops

Arbitrary beam cross sections are generated with boundary contours or centerlines. Boundary
contours are closed loops made 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.
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.
CHAPTER 10 3
Tools
Option Shows the available methods for creating arbitrary profiles:

• Input Points--enter loop point coordinates
• Select Surface--trace the outline of a selected surface
• Read File--obtain point coordinates from a file.
Input Data Textbox where you enter point coordinates.

Point Displays a spreadsheet for point information. Points are
numbered consecutively.
• X Outer X coordinate of a point in the outer (first) loop.
• Y Outer Y coordinate of a point in the outer (first) loop.
• Stress Rec Label of a stress recovery point.
Arrows Moves to a higher or lower loop number.
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
Delete Row row below where the new row will be placed and press Insert
Row. The row above it will become available for data input.
To delete a row from the spreadsheet, select the row and click
the Delete Row button.
Clear Boundary Deletes all input from the spreadsheet.
Display Boundary Draws the boundary loops. Loop points are numbered
according to the spreadsheet input.
Rotate/ Rotates the points on all loops about point 1 of the outer loop
Angle by the angle you enter in the Angle databox.
Using the Input Points option:

1. Click in the first X Outer cell.
2. Enter the X coordinate of the point in the Input Data textbox, press the Enter (or Return)
key. The value will be placed in the selected spreadsheet cell.
3. Click in the first Y Outer cell.
4. Enter the Y coordinate of the point in the Input Data textbox, press the Enter (or Return)
key.
5. Continue entering points to define the loop. The maximum number of points you can
specify in a loop is 150. When you press Calculate/Display to create the section, the
loop will be automatically closed even if the last point you entered does not coincide
with the first.
PART 2
Basic Functions
6. To create a hole in the cross section, press the up arrow to begin Loop 2. The
spreadsheet headings will be X Inner and Y Inner.
7. Continue entering hole boundaries as desired.
Using the Select Surface Option:

The inputs in the Select Surface dialog box will control the number of points that define the loop
of the cross sectional profile and will also determine how closely the cross section will follow the
boundaries of the surface.
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.
CHAPTER 10 3
Tools
Using the Read File Option

To read in the loop point coordinates from a file, the file must be in the same format as the last
two sections of the Report File titled Boundary Loops and Stress Recovery Points. Any other text
preceding the "Boundary Loops" heading will be ignored.
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.
PART 2
Basic Functions
5. When you press Calculate/Display, the profile will be drawn and the stress recovery
points will be labeled with the appropriate letters.
Creating Arbitrary Beam Cross Sections Using Centerlines

Arbitrary Shape using the Centerline method uses a set of branches that define the cross section
of any shape. Each branch has a beginning point and an end point. The next branch beginning
point is the previous branch ending point. Each branch has a beginning thickness and an end
thickness, beginning slope and end slope, and a even number of divisions that define the stress
recovery points. If the slopes are left blank, straight lines are assumed between begin and end
point. If the number of divisions is left blank, two is assumed, which gives three stress recovery
points per branch. The begin and end points and thicknesses at the begin and end points are
CHAPTER 10 3
Tools
required. Since each branch beginning point is the same as the 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 Displays the only available option: Input Branches.

Input Data Textbox where you enter X and Y coordinates.
Branch Displays a spreadsheet for branch information. Branches are
numbered consecutively.
•X X coordinates of the beginning and end points.
•Y Y coordinates of the beginning and end points.
• Thickness Beginning and ending thickness for each branch.
• dx/ds Beginning and ending slope in the X direction.
• dy/ds Beginning and ending slope in the Y direction.
• #Divs Number of divisions for each branch.

PART 2
Basic Functions
Insert Branch/ To insert a new branch into the spreadsheet, select the branch
Delete 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 Deletes all input from the spreadsheet.
Display Branches Draws the branches. Branches are numbered according to the
spreadsheet input.
Curvature Error The allowable Curvature Error will determine the number of
straight line segments used to approximate a curve.
Note: 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 analysis or converted to boundary loops and used in MSC.Nastran or other
analysis code including MSC.Marc if property values are accepted and input.
CHAPTER 10 3
Tools
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 only the MSC.Marc analysis code 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 Y t
1b 0 0 1
1e 10 0 2
2b 10 0 0
2e 5 0 0
3b 5 0 3
3e 5 10 1
PART 2
Basic Functions
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 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 Y t dx dy
1b 0 0 0.1 1 0
1e 0 1 0.1 -1 0
2b 0 1 0.1 0 -1
2e 0 0 0.1 0 -1
CHAPTER 10 3
Tools
Reporting Beam Section Data

If you pressed Write to Report File in the Beam Library dialog box, a report will be output about
the beam cross section you created. The procedure and the caveat are the same as in writing
report files for mass properties calculations; if you need more information please refer to (p. 380)
of this manual.
PART 2
Basic Functions
Modifying Beam Cross Sections

You can change all data you used to define a beam cross section.
Existing Sections Lists existing cross sections. Select the one you want to
change.
Rename Section As Displays textbox for entering a new name.
Section Symbols Shows cross section symbols. Pick the section you want to
use to replace the existing one.
Section Dimensions Displays existing dimensions. Edit dimensions as desired.
Spatial Scalar Lists existing fields. To associate a dimension with a field,
Fields click in the dimension databox then pick the field name.
Location Modifies the location where the field value will be evaluated.
Specification Enter new coordinates, or select a new curve or beam
Options element and move the slider to define a new parametric
location.
CHAPTER 10 3
Tools
Deleting Beam Cross Sections

To delete a beam cross section, in the Beam Library dialog box next to Action select Delete.
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>Model Variables Creating and Managing 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.
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
for example, a dimension.
• property--an element property, for example, element thickness
• material--a material property, for example, density.
• beam dimension--a selected dimension in a previously defined beam cross section, for
example, the inner diameter of a tube.
PART 2
Basic Functions
Values as Variables
Action Lists the action that can be performed. In

addition to creating new variables, you can also
show (verify), modify, and delete existing
variables.
Existing Variables Displays the names of previously defined 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.
Create If ON, creates a field for the model variable.
Referencing Field
CHAPTER 10 3
Tools
Element Properties as Variables

variable. If no description is entered, MSC.Patran will create
a description; it specifies the names of the Property Set and
Property Name from which the variable was created.
number.
Dimension These two entries act together as a filter that facilitates
Type 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.
PART 2
Basic Functions
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.
Select Psets by Selects a Property Set associated with an element you pick on
Elements the screen (this can be helpful if you do not remember the
pairing of property sets and elements).
Select Property Displays a specific property contained in the named Property
Name Set.
Beam Dimensions as Variables

CHAPTER 10 4
Tools
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.
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.
Select Beam Lists the names of previously defined beam cross sections.
Section Pick the one that contains the property you wish to
parameterize.
Select Beams Selects a beam cross section associated with an element you
by Elements pick on the screen (this can be helpful if several beam
elements exist each with their own cross sections and you do
not remember which name goes with which element).
Select Beam Lists all dimensions pertaining to the named beam section.
Dimension Select a beam dimension which will become the variable.
PART 2
Basic Functions
Material Properties as Variables

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.
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).
CHAPTER 10 4
Tools
Select Material Lists the names of previously defined materials. Pick the
material that contains the property you wish to parameterize.
Select Materials Selects a material associated with an element you pick on the
by Elements screen (this can be helpful if you do not remember which
material goes with which element).
Select Property Selects a specific property contained in the named material
Name definition. Also enters its current value into the Analysis
Value textbox.
Displaying Model Variables

With the Model Variables>Show command you can display and verify any or all variables and
their values.
Select Variables Displays all previously defined variables. Pick one or several
to Show to show in detail.
Select by Elements Selects the properties associated with elements you pick on
the screen.
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.
PART 2
Basic Functions
Modifying Model Variables

In this dialog box you can modify the initial value of a variable as well as the description attached
to it. The names of variables cannot be changed.
Select Variable Lists all variables contained in the database. Pick the variable
to Modify you want to modify.
Variable Name Displays the name you selected. This name cannot be
changed.
Description Displays the original description that you can edit or replace.
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.
CHAPTER 10 4
Tools
Deleting Model Variables

When you delete a model variable, all fields and other properties associated with it will be
deleted from the database.
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 Variables Lists all variables contained in the database. Pick one or more
to Delete variables that you want to delete.
Select by Elements Select an element whose property is a variable that you want
to delete.
Apply/Close Pick Apply to complete the deletion. Pick Close to cancel the
delete action and exit from the application.
Tools>Design Studies Creating Design Studies
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 to achieve the optimal design.
• decide the constraints to place on the design. Define the condition that is considered as
a limiting factor in the optimization process.
PART 2
Basic Functions
Creating Design Studies
Action Lists the action that can be performed.

Note that with Create you can also modify a design study.
Object Displays the object of the action.

Current Design Shows the name of the current design study.
Study
Existing Design StudyDisplays the names of existing design studies. Pick the name
of an existing design study if you want to modify it.
Design Study Name 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.
Description Provides a textbox where you can enter a detailed
description of the design study.
CHAPTER 10 4
Tools
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.
Design Study Setup
• Design Displays the Design Variables dialog box where you can
Variables review and modify design variables (see Design Variables
(p. 407)).
• Design Displays the Design Objective dialog box (see Design
Objective Objective (p. 410)).
• Design Displays the Design Constraints dialog box where you can
Constraints create or modify design constraints (see Design Constraints
(p. 410)).
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. 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.
PART 2
Basic Functions
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.
Design Value Provides a field where the value of a design variable will be
placed, if you define one that is different from the value of
the model variable.
When you click in this field, a
textbox appears at the top of the
spreadsheet. Type a new value
then press Enter (or Return).
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.
CHAPTER 10 4
Tools
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 Specifies the change allowed in a design variable in each
design cycle. Default is 1.0, the equivalent of 100%.
Design Cycle Select Calls up the Design Cycle Select dialog box.
Defaults Resets all entries to their original value. Keeps the dialog box
on the screen.
OK/Cancel OK accepts all variables. Cancel closes the form.
Design Cycle Select

In this dialog box you can update the design variables in the study with the solution values
output by the solver and stored in the results database.
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 Presents the list of design cycles (subcases).
Design Variables Shows the 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.
PART 2
Basic Functions
Design Objective
Design objective is the goal of the optimization process. Currently, the only available option for
design objective is the goal of minimizing the entire weight of the model.
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.
At the present time (MSC.Patran2001) none of the items in this dialog box are selectable for a
modified input.
Solution Displays “Global”; presently the only choice for the extent of
optimization. The objective of minimizing the weight extends
globally, that is, for the entire structure.
Response Displays “Weight”; presently the only choice for the goal of
optimization is minimizing the weight.
Existing Objectives Displays “Total Weight”; the predefined--and presently the
only--name of the objective function.
Min/Max Displays “minimize”; currently the only action that the
optimizer is enabled to perform on the response entity.
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. At the present time, the available options are linear static and normal modes.
CHAPTER 10 4
Tools
Constraints for Linear Static Solutions

In linear static analysis the constraint responses may be displacements, stresses, strains, forces,
composite stresses, composite strains, composite failure, element strain energy, total strain
energy, and grid point force.
Displacement as Constraint
Create/Delete Choose to Create or Delete design contraints.

Action Specifies Create or Delete. With the Create action you can
also modify existing constraints.
Solution Names the type of analysis you are running. The options are
Linear Static, or Normal Modes.
Response Displays the type of attribute that may be selected as a
constraint.
PART 2
Basic Functions
Existing Constraints Lists the names of all constraints previously defined for the
current design study.
Constraint Name Names the current constraint. Provides a default name with a
prefix that is based on the response type (for displacements
the name will begin with “DISP”). If desired, you may
replace the default name with any other name.
To modify a constraint, pick its name here.
Constraint Region Identifies the domain over which the constraint will be
applied. The only applicable domain for displacements is the
finite element model, more specifically, the nodes in the
model.
Select Node Provides a textbox for node selection. Pick nodes
individually, screen-select a number of nodes, or type in
node IDs.
Displacement Shows the components of the displacement constraint. Select
Component a translational (TX, TY, TZ) or rotational (RX, RY, RZ)
displacement component. Alternatively, you may select
Magnitude, the resultant displacement, that will
automatically create an MSC.Nastran DRESP2/DEQUATIN
entry pair.
Lower Bound/ Displays textboxes where you can enter the lowest and
Upper Bound highest acceptable values of the constraint.
The upper bound value must be higher than the lower bound
value.
Do not enter zero for either bound value. Either provide a
non-zero value or leave the field empty.
CHAPTER 10 4
Tools
Stress as Constraint
Constraint Name Displays the default name which begins with the prefix
“STRESS”.
Constraint Region Provides two choices for the domain over which the
constraint will be applied. You may select the entire finite
element model or restrict the selection to certain elements for
which a set of properties has been previously defined.
Therefore the options are FEM and PSET (property set).
If you pick PSET, a databox will display the names of existing
selectable properties. Alternately, you can pick the elements
to which the property has been assigned.
Element Dimension/ Displays the options for element dimensionality and type.
Element Type Pick the attributes that apply to the elements in your model.
Whatever you select for dimension (1D, 2D, or 3D) will
dictate what the selections are in the element type box.
The nature of further options available in the remainder of
the dialog box depends on what you select for these two
attributes.
Select Finite Element Pick the finite elements for which the constraints apply.
PART 2
Basic Functions
Stress Component Identifies the stress component whose value acts as the
constraint. The contents of the options form will vary,
depending on the selected element dimensionality and type.
Examples of Stress Component Options:
Beam (1D) Plate/Shell (2D) Solid Element (3D)
Location on Specifies the location of the stress constraint on the element.

Element
• 1D beam, bar, or bend elements--either end of the
element.
Other 1D elements--option is not applicable
• 2D plates and shells:
• 3D solid elements--corners or center.

Upper Bound highest acceptable values of the constraint.Keep in mind that
the upper bound value must be higher than the lower bound
value.
CHAPTER 10 4
Tools
Strain as Constraint
All items in this dialog box are the same and require the same input as those in the dialog box
for stress design constraints.
PART 2
Basic Functions
Force as Constraint
CHAPTER 10 4
Tools
Element Dimension/ Displays the options for element dimensionality and type. Pick these
Element Type attributes as they apply to the elements in your model.
Whatever you select for dimension (1D or 2D) will dictate what the
selections are in the element type box. The nature of further options
available in the remainder of the dialog box depends on what you select
for these two attributes.
Force Component Identifies the force component whose value acts as the constraint. The
contents of the options form will vary, depending on the selected
element dimensionality and type.
Examples of Force Component Options:
Beam (1D) Plate/Shell (2D) Shear Panel (2D)
Location Specifies the location of the force constraint on the element.

on Element
• 1D beam, bar, or bend elements--either end of the element.
Other 1D elements--option is not applicable
• 2D plates and shells--element corners or center.
• 2D solid elements--element corners or edges.
Lower Bound/ Displays textboxes where you can enter the lowest and highest
Upper Bound acceptable values of the constraint.
Keep in mind that the upper bound value must be higher than the
lower bound value.
PART 2
Basic Functions
Composite Stress/ Composite Strain as Constraint
Stress/Strain Identifies the stress or strain component whose value acts as

Component the constraint.
Upper Bound highest acceptable values of the constraint. Keep in mind that
the upper bound value must be higher than the lower bound
value.
CHAPTER 10 4
Tools
Composite Failure as Constraint
Failure Index Identifies the stress or strain component whose value acts as the
constraint.
Upper Bound acceptable values of the constraint. Keep in mind that the upper bound
value must be higher than the lower bound value.
PART 2
Basic Functions
Element Strain Energy as Constraint
CHAPTER 10 4
Tools
Total Strain Energy as Constraint
PART 2
Basic Functions
Grid Point Force as Constraint

CHAPTER 10 4
Tools
Solution Names the type of analysis you are running. The options is Linear
Static.
Response Displays the type of attribute that may be selected as a constraint.
Existing Constraints Lists the names of all constraints previously defined for the current
design study.
Constraint Name Names the current constraint. Provides a default name with a prefix
that is based on the response type (for Grid Point Forcesthe name will
begin with “GPFORCE”). If desired, you may replace the default
name with any other name.
Grid Point Force Type The type of Grid Point Force constraints.
Standard Standard Grid Point Force constraints.
(GPFORCE)
Extend Extend Grid Point Force constraints.
(GPFORCP)
Select Grid Point Provides a textbox for node selection. Pick nodes individually,
screen-select a number of nodes, or type in node IDs.
Force Component The components of the grid point force. Multiple components can be
selected.
The upper bound value must be higher than the lower bound value.
Do not enter zero for either bound value. Either provide a non-zero
value or leave the field empty.
PART 2
Basic Functions
Frequency Constraints for Normal Modes

In modal analysis the possible constraint responses are frequency, eigenvector, stress, strain,
force, element strain energy, and total strain energy.
Frequency Mode The identification number of the mode shape that supplies the
Number frequency constraint.
Lower Bound/ For modal analysis the unit of boundary values is Hertz (Hz.). Keep in
Upper Bound mind that the upper bound value must be higher than the lower bound
value.
Even if the frequency constraint must equal a certain boundary value,
do not enter the same upper and lower bounds. Make them slightly
different to allow the optimization solver some freedom.
CHAPTER 10 4
Tools
Eigenvector Constraints for Normal Modes

Solution Names the type of analysis you are running. The options are Linear
Static, or Normal Modes.
Response Displays the type of attribute that may be selected as a constraint.
PART 2
Basic Functions
Existing Constraints Lists the names of all constraints previously defined for the current
design study.
Constraint Name Names the current constraint. Provides a default name with a prefix
that is based on the response type (for displacements the name will
begin with “DISP”). If desired, you may replace the default name
with any other name.
Mode Number The identification number of the mode shape that supplies the
eigenvector constraints.
Contraint Region Identifies the domain over which the constraint will be applied. The
only applicable domain for Eigenvectors is the finite element model,
more specifically, the nodes in the model.
Select Node Provides a textbox for node selection. Pick nodes individually,
screen-select a number of nodes, or type in node IDs.
Displacement Shows the components of the displacement constraint. Select a
Component translational (TX, TY, TZ) or rotational (RX, RY, RZ) displacement
component. Alternatively, you may select Magnitude, the resultant
displacement, that will automatically create an MSC.Nastran
DRESP2/DEQUATIN entry pair.
The upper bound value must be higher than the lower bound value.
Do not enter zero for either bound value. Either provide a non-zero
value or leave the field empty.
CHAPTER 10 4
Tools
Stress Constraints for Normal Modes

PART 2
Basic Functions
Stress Component Choose the stress component that you want to constrain.

on Element
value.
CHAPTER 10 4
Tools
Strain Constraints for Normal Modes

PART 2
Basic Functions
Stress Component Choose the stress component that you want to constrain.

on Element
value.
CHAPTER 10 4
Tools
Force Constraints for Normal Modes

PART 2
Basic Functions
Force Component Choose the force component that you want to constrain.

on Element
value.
CHAPTER 10 4
Tools
Element Strain Energy Constraints for Normal Modes

value.
PART 2
Basic Functions
Total Strain Energy Constraints for Normal Modes

Mode Number The number of the mode shape that supplies the constraint.
value.
CHAPTER 10 4
Tools
Tools>Results Templates Creating and Applying Results 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. 22) in the MSC.Patran Reference
Manual, Part 6: Results Postprocessing.
MSC.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 template to the Results forms, you need to display either the Create
Deformation or Modify Deformation results menu.
Object Defines the Results tools to which the Template will be applied.
Existing Deformation Select an the existing template to apply. The list includes templates that
Templates match the selected object.
PART 2
Basic Functions
Creating and Managing Results Templates

Use the Create, Copy, Edit, and Delete actions on the Results Templates form to obtain Results
Display Attributes and Plot Options values from a Result Tool, and then use those values to
create and manage a 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.
CHAPTER 10 4
Tools
Action
• Create Accesses the settings of the Results Display Attributes or Plot Options
on a Results form and creates a template. You have the choice of “Use
Tool Values” or “Use Form Values.” Selecting “Use Form Values”
requires that the corresponding Results form to Create or Modify the
same Object already displayed before the template values can be read
from the Results Display Attributes or Plot Options forms. For example,
before creating a Deformation template using the Results forms, you
need to display either the Create Deformation or Modify Deformation
results menu and set the Attributes and Options menu items to the
desired settings.
• 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 Deletes an existing template.
Object Defines the Results tool to which the template will

apply.
Method “Use Tool Values” extracts the Results Display

(for Creating Attributes and Plot Options values that were stored
Templates) 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 Select an the existing template to use. The list includes templates that
Templates match the selected object.
PART 2
Basic Functions
New Template Name 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.
Select Deformation Selects the Deformation Tool to use for the Results template.
Tool
CHAPTER 10 4
Tools
Overwrite Db If the “Overwrite Db Template” toggle is set and the database already
Template has a results template of this type and name, it will be overwritten or
replaced with the new results template values.
Spectrum & Range ... 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.
PART 2
Basic Functions
Exporting and Importing Results Templates

Once you have created a Results Template it can be exported for use with other MSC.Patran
databases. Likewise existing Results Templates, perhaps generated from another database, can
be imported.
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 The Import menu prompts you to select an existing Results
Template to import into the database.
Object Defines the Results tool to which the
template will apply.
Existing Deformation Select an the existing template to export. The list includes
Templates templates that match the selected object.
CHAPTER 10 4
Tools
Set Overwrite Flag The “Set Overwrite Flag” toggle controls whether or not to
overwrite existing results templates of the same name and type
when the file is later imported or used for template initialization
at database open or new database creation. Setting the toggle
turns ON overwrite.
Files... Browses and selects a Results Template to import.
Overwrite File/ When exporting, the “Overwrite File” toggle controls whether the
Overwrite Db export file will be overwritten or appended to if it already exists.
Template Setting the toggle causes it to be overwritten, while if it is not set,
the export will append to the end of the file if the file already
exists.
When importing, the “Overwrite Db Template” toggle controls
whether a preexisting results template of this type and name will
be overwritten or replaced with the new results template values.
Loading Results Templates in a MSC.Patran Database

MSC.Patran can be configured so that when you create a new database and/or open an existing
database, a predefined set of Results Templates will be loaded into the database. In the case of
loading on opening an existing database, MSC.Patran can be configured to replace or keep
existing templates with the same name and tool type as those in the predefined set.
The easiest way to create this predefined set of Results Templates is to create them first in
MSC.Patran and then use the Results Templates Export menu to export them to a file. This file
can then be used as the set of predefined Results Templates. You can also alter the contents of
this file with any text editor.
To enable the automatic loading of Results Templates for new databases, you need to place the
following command in your settings.pcl file.
pref_env_set_logical( "ResTmplAutoLoadNewDb", TRUE )
Setting the above to false disables the feature and is the default setting.
To enable the automatic loading of Results Templates when opening existing databases, you
need to place the following command in your settings.pcl file.
pref_env_set_logical( "ResTmplAutoLoadOpenDb", TRUE )
Setting the above to false disables the feature and is the default setting.
When enabled, MSC.Patran will look for a session file, which it will play immediately after
opening a new or existing db as the case may be and the preferences above are set TRUE. This
session file should contain the builtin commands to create the desired standard results templates
The default name of the template initialization session file is res_tmpl_init.ses. It is searched for
in the current directory, then your home directory, and finally in the p3_home directory. The
first found is used and no additional directories are searched.
You may control the initialization file name and directory searches with two environment
variables, "RES_TMPL_DEF_FILE_NAME" and "RES_TMPL_DEF_PATH_NAME”. If either or
both are set, they will be searched first, before the default search described in the previous
paragraph.
The RES_TMPL_DEF_PATH_NAME environment variable may also be a relative path.
PART 2
Basic Functions
The full order of search is top_path // env_path_name // env_file_name, where top_path is "",
"./" $HOME//"/", and $P3_HOME//"/" in that order and repeats for each possible
combination of env_path_names and env_file_names. env_path_name is first the value of the
environment variable RES_TMPL_DEF_PATH_NAME, if set, and then "" and repeats for each
possible value of env_file_name. env_file_name is first the value of the environment variable
RES_TMPL_DEF_FILE_NAME, if set, and then "res_tmpl_init.ses". Searching stops as soon as a
match is found and that found file is used for the initialization.
Note that RES_TMPL_DEF_PATH_NAME and RES_TMPL_DEF_FILE_NAME are system
environment variables (similar to P3_HOME) and are set with the setenv system command, not
the pref_env_set_string(…) Patran command.
Note that the initialization file may play other session files and can do all manner of
sophisticated hierarchical processing as you may wish to have it do.
Instead of the above search for files stopping when it finds its first match, you can have to find
all matches by placing the following in your settings.pcl file.
pref_env_set_logical( "ResTmplAutoLoadAllFiles", TRUE )
True causes auto load to load ALL the files it finds in the various directories. False (default)
causes the usual Patran behavior of stopping when the first matching file is found in the
directory search hierarchy.
You can also alter the top directory search order with this command in your settings.pcl file.
pref_env_set_string( "ResTmplAutoLoadDirOrder", "1,3,2,4" )
The default order is "1,2,3,4". Permutations of the integers permute the directory hierachical
search order. The default order is none, ., $HOME, and $P3_HOME. Thus, the above example
will cause $HOME to be searched before the current directory (.).
To force your standard Results Templates to be loaded when opening an existing database,
regardless of whether there are Results Templates of the same type and name already in that
database use this builtin function.
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. 41) in the MSC.Patran Reference Manual,
Part 1: Basic Functions.
CHAPTER 10 4
Tools
Tools>Rebar Definitions Creating Rebar Definitions
Creates 2D layered rebar definitions for use with the MSC.Marc Analysis Preference. Discrete
rebar models and general 3d layered rebar models are not supported. Rebar is actually an
element property definition for the MSC.Marc Preference, 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. 108) in the MSC.Marc Preference
Guide.
PART 2
Basic Functions
Creating Rebar Definitions

Use the Tools>Rebar Definitions command to Create, Modify, Delete, and Show rebar
definitions.
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.
• Delete Delete simply allows you to delete existing rebar definitions.
• Show The Show action allows you to graphically visualize rebar

property data set.
Object/Type Only 2D Layers are supported.
Existing Rebar or Supply a name for the rebar layer and select a color. Or pick
Rebar Name an existing rebar from the Existing Rebar... button.
CHAPTER 10 4
Tools
Curve List All rebar layer definitions must be associated to a geometric

curve. This curve must be placed on top (in the xy plane) of a
2D solid mesh for axisymmetric or plane strain elements.
These elements should already have properties assigned to
them.
Material Select an existing material that defines the rebar material
properties from the Material... button. The name will be filled
in the data box below the button.
Area/Spacing/ Supply the cross sectional area, the spacing and the
Orientation 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.
When a rebar layer is created it does a number of things:

1. First elements are created along the length of the curve. These elements are created
such that nodes are placed at locations where the curve intersects element edges of the
existing 2D mesh. You can think of the Rebar Definition tool as a specialized mesher.
2. A group with these nodes and elements by the same name as the rebar layer is created.
3. The elements for the rebar layer are assigned 1D rebar membrane properties. The Type
and Option in the Element Properties application are determined by the continuum
element types through which the rebar passes. This requires that the continuum
element have properties assigned them before the rebar evaluation otherwise an error
is issued. The list of continuum elements through with the layer passes plus the
associated properties become part of the property set.
For more information on using Rebar Definitions with the MSC.Marc Analysis Preference and
for examples of Rebar applications, see the MSC.Marc Preference Guide.
Tools>MSC.Fatigue Invoking the MSC.Fatigue Application Module
Selecting the Fatigue 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 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.
PART 2
Basic Functions
Tools>Laminate Modeler Invoking the MSC.Laminate Modeler Application Module
MSC.Laminate Modeler is a MSC.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. For
more information, see the MSC.Laminate Modeler User’s Guide
Tools>Analysis Manager Invoking the MSC.Patran Analysis Manager

Application Module
The MSC.Patran 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. For
more information, see the MSC.Patran Analysis Manager User’s Guide.
Tools>Rotor Dynamics Invoking the MSC.Patran Analysis Manager

Application Module
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 MSC.Patran MSC.Nastran Preference
Guide, Volume 1: Structural Analysis
Tools>Experimental Data Fitting Experimental Data Fitting for MSC.Marc

Analysis Preference
This tool is used to curve fit experimentally derived raw elastomeric material data and fit a
number of material models to the data. This data can then be saved as constitutive hyperelastic
and/or viscoelastic models for use in an MSC.Marc analysis. The operation of curve fitting is
done in three basic steps corresponding to the actions in the Action pull-down menu.
1. Import the Raw Data - data is read from standard ASCII files and stored in MSC.Patran
in the form of a field (table).
2. Select the Test Data - the fields from the raw data are associated to a test type.
CHAPTER 10 4
Tools
3. Calculate the Properties - the curve fit is done to the selected test data; coefficients are
calculated based on the selected material model; curve fit is graphically displayed and
the properties can be saved as a constitutive model for a later analysis.
Import Raw Data. You can import the raw materials data by following these steps:
1. Enter a New Field Name - this is the name of the raw data table as it will be stored in
MSC.Patran as a material field.
2. Select the Independent Variable - this is defaulted to Strain but could be any of Strain,
Time, Frequency, Temperature, or Strain Rate.
3. Select the File and press the Apply button.
Keep in mind the following points and considerations when importing raw data:
1. You can skip any number of header lines in the raw data file by setting the Header
Lines to Skip widget.
2. You may edit the raw data file after selecting it by using the Edit File... button. The
editor is Notepad on Windows platforms and vi on UNIX platforms unless you change
the environment variable P3_EDITOR to reference a different editor. The editor must
be in the user’s path or the entire pathname must be referenced.
3. Raw data files may have up to three columns of data. By default the first column of data
is the independent variable value. The second column is the measured data, and the
last column can be the area reduction or volumetric data. More than three columns is
not accepted. If the third column is blank, the material is considered incompressible.
4. The data may be space, tab, or comma delimited.
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.
PART 2
Basic Functions
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.
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 model’s 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 MSC.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. 74) in the MSC.Marc Preference Guide.
CHAPTER 10 4
Tools
Tools>PreRelease Tools Available as Pre Release Features
The MSC.Patran development team is dedicated to improving all aspects of this product in order
to satisfy your needs for effective and efficient simulation assessment. We introduce and
develop our projects in accordance to the needs and demands expressed to us by our customers.
Many such projects were initiated and included in the recent releases of our software. You can
access all pre-release items under Tools/Pre Release menu in MSC.Patran. The true intent for
making these tools available for your use is to assess the level of interest generated by our
customers for the benefits they experience through the use of these items. Particular attention is
made to ensure proper feedback is collected and incorporated in further development of the
most popular items. Similarly, items that generate low interest and provide little benefit to a
large group of our customers will be discontinued and deleted from the list. If you have any
feedback about the Pre Release features in MSC.Patran, please contact your Customer support
or account representative. Please keep in mind that some of these items are based on technology
that has been licensed or purchased from other companies. As such, MSC.Software reserves the
right to discontinue the free use of any of the pre-release tools and offer them in a modular
format with appropriate licensing fees.
For additional information regarding each of the Pre Release features listed below, see
MSC.Patran 2004 at a Glance.
Midplane Meshing
A new capability is being introduced for creation of a mid-plane finite element representation
for a thin walled solid. This tool is a mesh-based method for direct mid-plane mesh creation,
without the need to create any mid-plane geometry entities. It is well suited to solid models of
thin components, which are stamped. Most automotive parts that are made from stamping sheet
metals can be meshed using this technology.
This mesh tool can complement the newly introduced geometry based mid-surface extraction
utility. This finite element based function is sometimes able to create a mid-plane mesh from the
solid parts where geometry based methods fail, or produce geometry needing interactive
cleanup.
This technology is limited to solids that do not have T-sections. Solids that have T-sections can
be broken into pieces that do not have T-sections which can then be midplane-meshed.
Parametric Modeling
Parametric Modeling enables you to define an extensive array of variables, macros, and outputs
that can be used to expedite the modeling process.
Variable types can be integer, real, or string and arrays of those types. A new variable can be
established by simply typing in a name, setting its type and giving it a current value. An optional
description can also be added. New variables can also be defined using other variables and any
of the extensive collection of available functions in MSC.Patran. Variable names can then be used
in any other MSC.Patran form and are denoted by enclosing the name in the back tick symbol,
as was the case for global variables. Upon completion of a modeling step, it can be seen in the
session file that the variable name is provided along with its default value and a reference to an
external file where subsequent different values can be set. When re-played, MSC.Patran will
look for that file, read its contents to determine if there is a new value for the variable and if so,
use that value instead of the default.
PART 2
Basic Functions
In addition to creating variables during the modeling process, you can create response variables
once you have completed an analysis. Using Response variables you can search through and
manipulate the results of analysis to define meaningful metrics for export to an external file.
Examples of such metrics might be maximum Von Mises stress in one previously defined group
or material region or maximum strain in the fiber direction of a particular composite material,
or any number of other criteria that can be developed based on the results coming back from the
analysis code.
Macros operate on existing variables, macros and outputs. You can multiply two real variables
to make a macro and then use that macro in a second macro. When the underlying variables
change values, the macros change values. You can operate on single elements of an array, but
not the entire array, because macros only return a single value. You can also use string variables
in macros. But only valid pcl operations are allowed. You cannot, for example, use a string
variable in a multiplication, unless you first convert the string to a valid integer or real (which
can be done within the macro). If you create an illegal operation (multiply a string variable, for
example), you will have to go to the delete form and delete the offending macro in order to
defeat the ensuing and persistent pcl traceback.
Output variable types include nodal or element scalar, vector or tensor quantities. Results may
be sorted by maximum, minimum, absolute maximum or absolute minimum value. Sorting may
be based on element or node ID, all entities in a graphics window, all in a user defined group,
material ID or property ID. Results can be sorted to designated ply for composite materials. Mass
properties can also be output with this form. The form changes based on selections made and
only those parts of the overall analysis results applicable to those choices are allowed as further
choices. Thus, the user is made aware of all the factors affecting his specification of output.
Connector
MSC.Nastran 2001 introduced a new type of structural connectivity element called spot weld
(CWELD & PWELD). The purpose of this formulation is to represent the behavior of weld type
structural connections and small fasteners (e.g.: row of rivets). Prior to the introduction of this,
accurate modeling of fasteners has been difficult and error prone with the conventional
modeling tools available. However, the new MSC.Nastran spot weld element overcomes these
modeling difficulties by representing appropriate load transfers associated with these types of
physical connectivity. MSC.Nastran spot weld entities automatically manage singularities, rigid
body invariance, and differing mesh densities, while ensuring accurate results.
Use the Connector tool to easily create the CWELD element, and corresponding PWELD
property entries. You can import an external file that contains all relevant connection data and
MSC.Patran will generate MSC.Nastran CWELD and PWELD entries automatically.
Additionally, the newly created connection elements can also be plotted, erased, modified and,
deleted with MSC.Patran just as easily.
Feature Recognition
The Feature Recognition tool enables you to select a solid in your model and then ask for certain features
to be automatically recognized by MSC.Patran. The Feature Recognition Tool support the following fea-
ture types:
• Circular Hole features.
This module provides recognition of hole features in the input model. It recognizes
circular features. It can recognize circular holes which may be blind or thru.
• Transition features.
CHAPTER 10 4
Tools
• Blends
Two types of blends are recognized – constant radius blends and variable radius
blends.
• Chamfers
The chamfer feature recognizes two attributes which are its slope heights.
Feature Recognition may be automatic or interactive. Using the automatic option, you select the
solid from which the features are to be recognized from the viewport and the corresponding
features for which recognition was called is recognized. In case of transition features automatic
recognition recognizes all the features with chaining. Using the interactive option, you pick the
face list from the viewport and only those features which contain the selected faces are
recognized.
Limitations
Only one feature type can be recognized and worked on at a time. For example, if you have
recognized holes, then recognize blends in the same MSC.Patran session, the feature modeler
will replace the hole features with the newly recognized blend features for you to work on. All
previous edits to the model by editing hole parameters or deleting holes will be saved however.
Solids whose geometry source is Parasolid is the only type supported for Feature Recognition.
PART 2
Basic Functions
MSC.Patran Reference Manual, Part 1: Basic Functionsr
APPENDIX
File Formats
A
■ The Neutral System Concept
■ The Neutral File
■ Session File/Journal File
■ IGES File
■ PATRAN 2.5 Results Files

PART 2
Basic Functions
A.1 The Neutral System Concept

The “neutral system” is a communication link to computer programs developed outside of
MSC.Software Corporation. Neutral system information flow is bi-directional; that is, data can
be transmitted from MSC.Patran's database to the outside and data can be transmitted from
outside into MSC.Patran's database.
APPENDIX A 4
File Formats
A.2 The Neutral File

The key element of the neutral system is the “neutral file.” The neutral file may contain:
• An analysis model.
• A geometry model.
• A conceptual solid model.
• Any or all of the models plus the GFEG and CFEG tables relating the geometry model
to the 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 MSC.Patran (p. 457) 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.
Neutral File Applications

There are many uses for the neutral file; some are obvious, others are more subtle. The
applications of which we know are described briefly in the following paragraphs. If you find an
additional use, please let us know about it.
Finite Element The most common use of the neutral file is to output a finite element
Model Output model for analysis. In this application, the neutral file is read by an
application interface which converts MSC.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 MSC.Nastran.
Geometry Model It is also possible to output a neutral file containing mathematical
Output definitions of a geometry model. Points, parametric cubic curves,
parametric bi-cubic surfaces, and parametric tri-cubic solids are the only
geometry forms which can be written to a neutral file. This information
can then be accessed by programs that perform such functions as
automated drafting or preparation of tapes for numerically controlled
milling machines.
Finite Element Through the use of an “inverse translator”, an existing finite element
Model Input model in the form of an input deck for a particular analysis program can
be input to MSC.Patran. Once in the MSC.Patran database, the model
can be displayed interactively, modified if necessary, and even output to
a different analysis program if desired.
Geometry Model Dependent upon your particular engineering application, it may be cost
Input effective to input part of your problem's geometry via the neutral file
rather than the keyboard. This is especially true if points defining your
geometry can be computed using relatively simple algorithms. In this
case, rather than calculating coordinates of points and typing them into
MSC.Patran by hand, try writing a short computer program to compute
the coordinates and output them to a file in neutral file format.
PART 2
Basic Functions
Sub-Structuring One of the most effective techniques for modeling a large, complex
structure is to break it up into its component parts. Each component part
is separated by identifying the finite element node locations at each
interface. Then, each part can be modeled as a separate sub-structure
independent of the other parts.
If modeling time is critical, the various sub-structures can be modeled
simultaneously by different individuals.
Sub-Structuring An important point here is that each modeler can use MSC.Patran's
(continued) default ID number assignments for his nodes, elements and geometry
items without having to worry about later conflict with other sub-
structures.
When each sub-structure is finished, it will be written into its own
neutral file. Then, one by one, the individual sub-structure neutral files
will be read into a single database. As each sub-structure neutral file is
read, its ID numbers will be offset from those already present in the
database.
The offsets can be specified, or MSC.Patran will determine them
automatically.
Using nodal equivalencing, the duplicate nodes at the common
boundaries can be combined to form a continuous model. See The
Equivalence Action (Ch. 9) in the MSC.Patran Reference Manual, Part 3:
Finite Element Modeling for more information.
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 Since neutral files are upwardly compatible from release to release, it is
safe to store them in the neutral file format over long periods of time.
Files can be kept on tape and archived for future reference.
APPENDIX A 4
File Formats
Neutral File Format

All information in the neutral file is contained in small units referred to as “data packets”. Each
data packet consists of a one card header record followed by one or more cards containing the
data for a fundamental entity of the database such as a specific node, element, line or patch.
Neutral File Packet Types Supported in MSC.Patran (p. 457) 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.
Neutral File Types

Neutral files created by PATRAN Plus release 2.5 may be in either text (default) or binary format.
In MSC.Patran, only the text file format is supported for import and export.
Neutral File Packet Types Supported in MSC.Patran
Type Number Packet Description Import Export

25 File title X X
26 Summary data X X
Finite Element Model Packets

1 Node data X X
2 Element data X X
3 Material properties X X
4 Element properties X X
5 Coordinate frames X X
6 Distributed loads Normal X
Pressures
7 Node forces X X
8 Node displacements X X
9 Bar element initial displacements
10 Node temperatures X X
11 Element temperatures X
12 DOF lists
13 Mechanism entities
14 MPC data X X
15 Nodal heat source X X
16 Distributed heat source X
PART 2
Basic Functions

17 Convection coefficients X X
18 Radiation emissivity values
19 Viewfactor Data
21 Named components X X
Geometry Model Packets

31 Grid data X X
32 Line data X X
33 Patch data X X
34 Hyperpatch data X X
36 Data-line data
37 Data-patch data
38 Data-hyperpatch data
39 Field data (coefficient format)
48 Field data (PCL format)
40 LIST card
41 DATA card
GFEG/CFEG Table Packets

42 GFEG table for a line X
❏ Created by a GFEG command
❏ Created by a Mesh command
43 GFEG table for a patch X
44 GFEG table for a hyperpatch X
45 CFEG table X
APPENDIX A 4
File Formats
Trimmed Surface Solid Model Packets

46 Primitive data
47 Primitive face data
99 End of file flag X X
PATRAN 2.5 Neutral File Packet Header

The header card for each data packet contains the following information:
Header Card Format (I2,8I8)

IT ID IV KC N1 N2 N3 N4 N5
IT = Packet Type
ID = Identification number. A “0” ID means not applicable
(n/a)
IV = Additional ID. A “0” value means not applicable (n/a).
KC = Card Count (number of data cards after the header)
N1 to N5= Supplemental integer values used and defined as needed
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 (p. 460). The packet types are listed in the order of their
appearance (if present) in the neutral file.
PART 2
Basic Functions
PATRAN 2.5 Neutral File Contents and Format
Packet Type 25: Title Card

25 ID IV KC
ID=0 Not applicable
IV =0 Not applicable
KC=1
User Title Card Format (20A4)
TITLE
TITLE = Identifying title may contain up to 80 Characters
Packet Type 26: Summary Data

26 ID IV KC N1 N2 N3 N4 N5
ID=0 n/a N1=Number of Nodes
IV =0 n/a N2=Number of Elements
KC=1 N3=Number of Materials
N4=Number of Element Properties
N5=Number of Coordinate Frames
Summary Data Card Format (3A4, 2A4, 3A4)
DATE TIME VERSION
DATE = Date neutral file was created
TIME = Time neutral file was created
VERSION = MSC.Patran release number
APPENDIX A 4
File Formats
Packet Type 01: Node Data

1 ID IV KC
ID = Node ID
IV = 0 n/a
KC= 2
Data Card 2 Format (I1, 1A1, I8, I8, I8, 2X, 6I1)
ICF GTYPE NDF CONFIG CID PSPC
ICF* = Condensation flag (0 = unreferenced)
GTYPE = Node type
NDF* = Number of degrees-of-freedom
CONFIG= Node configuration
CID = Coordinate frame for analysis results
PSPC* = 6 permanent single point constraint flags 0 or 1
* These parameters are not currently used.
Data Card 1 Format (3E16.9)
X Y Z
X = X Cartesian Coordinate of Node
Y = Y Cartesian Coordinate of Node
Z = Z Cartesian Coordinate of Node
PART 2
Basic Functions
Packet Type 02: Element Data

2 ID IV KC 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 Format (I8, I8, I8, I8, 3E16.9)
NODES CONFIG PID CEID θ1 θ2 θ3
NODES = Total number of nodes
CONFIG*= Element configuration
PID = Property ID (+) or material ID (-)
CEID = Congruent element ID
θ1, θ2, θ3=Material Orientation angles (for bars, these values are the coordinates of a point
in the bar X”Y-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.
ADATA
ADATA†= Associate data values (For bars, these are coordinates of the bar ends if offset
from end nodes).
†ADATA will not be present if N1 is zero
APPENDIX A 4
File Formats
Packet Type 03: Material Properties

3 ID IV KC 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
DATA = 96 Material property constants**
ADATA
ADATA*= Associated ply data values (thicknesses, orientation angles, material ID’s.)
*ADATA will not be present if N1 is 0.
*Material Types:
1 Isotropic 4 TIS option 11 HAL option
2 2D anisotropic 5 TAN option 12 LLAM option
3 3D orthotropic 6-73D anisotropic 13 MIX option
**Material Property Constants.
1 Reference temperature (T) 36 0 = Not applicable
2 Density (ρ) 37-57 21 material stiffness matrix terms (C11,
3 Total thickness (laminate materials only) C12, C13, C22, C23, C33, C44, C45, C46,
C55, C56, C66, C14, C15, C16, C24, C25,
4 Number of plies (laminate material only) C26, C34, C35, C36)
5 Offset (laminate materials only) 58-63 6 2D membrane stiffness matrix terms
6 Structural damping coefficient (GE) (A11, A12, A13, A22, A23, A33)
7 Density(ρ) ✳ Specific heat (CP) 64-69 6 2D bending stiffness matrix terms
8 Option = material type (D11, D12, D13, D22, D23, D33)
9-14 6 Thermal expansion coefficients (α11, 70-78 9 2D membrane/bending coupling
α22, α33, α12, α23, α31) terms (B11, B12, B13, B21, B22, B23, B31,
B32, B33)
15-20 6 Thermal conductivities (K11, K12, K13,
79-81 Stress limits for tension, compression,
K22, K23, K33)
and shear (ST, SC, SS)
21-26 2D thermal stress resultants for 1-degree
82 Emissivity
temperature rise
(N1, N2, N12, M1, M2, M12) 83-88 Not applicable at present
27-35 9 engineering material properties (E11, 89 Reserved
E22, E33, v12, v23, v31, G12, G23, G31) 90-91 Not applicable at present
PART 2
Basic Functions
Packet Type 04: Element Properties

4 ID IV KC N1 N2 N3 N4
ID = Property ID N1*= Shape
IV = Material ID N2 = Nodes
KC = (N4 + 4)/5 N3*= Configuration
N4 = Number of data fields
* Definition of applicable element type (see Packet Type 02)
(6X,AX,6X) for Character Data,
Data Card Format (E16.9) for Numeric Data
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.)
Packet Type 05: Coordinate Frames

5 ID IV KC
ID = Coordinate frame ID
IV = Coordinate type (1 = rectangular, 2 = cylindrical, 3 = spherical)
KC = 4 (for text files)
Data Card 1 to 4 Format (5E16.9)
A1 A2 A3 B1 B2 B3 C1 C2 C3 R(1,1) R(2,1)......R(3,3)
A1, A2, A3
B1, B2, B3, Coordinates of 3 points defining the coordinate frame.
(See Chapter 9, .Cord - Coordinate Frame Directives.)
C1, C2, C3,
R 3 x 3 rotation matrix to transform coordinates from this frame to the
global rectangular frame.
APPENDIX A 4
File Formats
Packet Type 06: Distributed Loads

6 ID IV KC
ID=Element ID
IV =Load Set ID
KC=1 + NPV + 4)/5(for text files)
Data Card 1 Format (I1, I1, I1, 6I1, 8I1, I2)
6 LTYPE EFLAG CFLAG ICOMP(6) NODE(8) NFE
LTYPE=Load type (0 = line. 1 = surface)
EFLAG=Element flag (0 or 1)
CFLAG=Node flag (0 or 1)
ICOMP=6 load component flags (0 or 1)
NODE=8 element node flags (0 or 1)
NFE=Edge number 1-12) or face number (1-6)
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.
PART 2
Basic Functions
Packet Type 07: Node Forces

7 ID IV KC
ID=Node ID
IV =Load Set ID
KC=1 + (NDW +4)/5(for text files)
Data Card 1 Format (I8, 6I1)

CID ICOMP(6)
CID=Coordinate frame ID
ICOMP=6 force component flags (0 or 1)
Data Card 2 to KC Format (5E16.9)
FDATA
FDATA=Non-zero force components
NDW = Sum of ICOMP(I), I=1,6
Packet Type 08: Node Displacements

8 ID IV KC
ID=Node ID
IV =Constraint set ID
KC=1 + (NDW +4)/5(for text files)
Data Card 1 Format (I8, 6I1)

CID ICOMP(6)
CID=Coordinate frame ID
ICOMP=6 displacement component flags (0 or 1)
FDATA
FDATA=Non-blank displacement components (may be 0.0)
NDW = Sum of ICOMP(I), I=1,6

APPENDIX A 4
File Formats
Packet Type 10: Node Temperatures

10 ID IV KC N1 N2
ID=Node IDN1=Data flag1: TEMP is temp value
IV =Temperature set ID0: TEMP is dummy value
KC=1N2*=User function
* This parameter is not currently used.
Data Card 1 Format (E16.9)
TEMP
TEMP=Temperature value
Packet Type 11: Element Temperatures

11 ID IV KC N1 N2
ID=Element IDN1=Data flag1: TEMP is temp value
IV =Temperature set ID0: TEMP is dummy value
KC=1N2*=User function ID
TEMP
TEMP=Temperature value
PART 2
Basic Functions
Packet Type 14: MPC Data

14 ID IV KC 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 Format (3A12)
DN IN TYPE
DN=Dependent name ID (not used)
IN=Independent name ID (not used)
TYPE=MPC or your own type name (maximum of 12 characters)
entered in option field of MPC ADD command.
Data Card 2 Format (2I8, E16.9)
NID DOF CO
NID=Dependent node ID
DOF=Dependent degree-of-freedom
C0=Constant term
Data Card 3 Format 2(2I8, E16.9)
NID(I), DOF(I), CO(I), I = 1, NT
First NDT terms are dependent otherwise, terms are independent
NID(I)=Node ID
DOF(I)=degree-of-freedom
C0(I)=Constant coefficient
The form of the MPC equation is assumed to be:
U0 = U1 C + U2 C2 + U3 C3 + … + Un Cn + C0
1
where U i is specified by NID(I) and DOF(I) and C i is specified by C(I).

APPENDIX A 4
File Formats
Packet Type 15: Nodal Heat Source

15 ID IV KC N1 N2
ID=Node IDN1=Data flag1: HEAT is heat flux value
IV =Heat Flux Set ID0: HEAT is dummy value
KC=1N2*=User function ID
HEAT
HEAT=Heat flux value
Packet Type 16: Distributed Heat Source

16 ID IV KC N1 N2 N3
ID=Element ID N3 = Dimension code
IV =Heat Flux Set ID 0 No heat flux dimension
KC=1 + (NN + 4)/5 (for text files) 1 HEAT is per unit length
2 (for binary files) 2 HEAT is per unit area
3 HEAT is per unit volume
N1=Data flag
1: HEAT is a heat flux value
0: HEAT is dummy value
N2=User function ID
Data Card 1 Format (I1, 1X, 8I1)
NFLAG NODE(8)
NFLAG=Node flag (0 or 1)
Data Card 2-KC Format (5E16.9)
HEAT(5)
HEAT=Distributed heat flux values*
*If N1 is zero, HEAT = 0.0 (dummy value). Otherwise:

If NFLAG = 0, one HEAT value
If NFLAG = 1, NN HEAT values
where NN = number of NODE flags on(= 1). The NODE flags correspond to the LNODES
corner nodes in Packet 02.
PART 2
Basic Functions
Packet Type 17: Convection Coefficients

17 ID IV KC N1 N2
ID=Element IDN1=Data flag1: CONV is a convection coefficient value
IV =Convection coefficient set ID
KC=1 + (NN + 4)/5 (for text files)0: CONV is dummy value
N2*=User function ID
NFLAG NODE(8)
CONV(5)
CONV=Convection coefficient values*
*If N1 is zero, CONV = 0.0 (dummy value). Otherwise:

If NFLAG = 0, one CONV value
If NFLAG = 1, NN CONV values
where NN = number of NODE flags on(= 1) The NODE flags correspond to the LNODES
APPENDIX A 4
File Formats
Packet Type 18: Radiation Emissivity Values

18 ID IV KC N1 N2
ID=Element IDN1=Data flag
IV =Convection coefficient set ID1: EMIS is a emissivity value
0: EMIS is dummy value
KC=1 + (NN + 4)/5 (for text files)
N2=User function ID
NFLAG NODE(8)
EMIS(5)
EMIS=Convection coefficient values*
*If N1 is zero, EMIS = 0.0 (dummy value). Otherwise:

If NFLAG = 0, one EMIS value
If NFLAG = 1, NN EMIS values
where NN = number of NODE flags on(= 1). The NODE flags correspond to the LNODES
Packet Type 19: Viewfactor Data

18 ID IV KC N1 N2
ID=Element IDN1=Not used
IV =Enclosure IDN2=User function ID
KC=1
Data Card 1 Format (6I8,2X,8I1)
NODE1 NODE2 CVSID OBSTR DYN SURF NODE(8)
NODE1=First Reference Node ID
NODE2=Second Reference Node ID
CVSID=Convex Surface ID
OBSTR=Non-obstruction Flag
(0 = potential obstruction, 1 = non-obstruction)
DYN=Dynamic Flag (0 or 1)
SURF=Surface (0 = top, 1 = bottom)
NODE(8)=8 element node flags (0 or 1)

PART 2
Basic Functions
Packet Type 21: Named Components

21 ID IV 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
NTYPE(1)* ID(1) NTYPE(2) ID(2) ........ NTYPE(5) ID(5)
(NTYPE(i), ID(i)) =Data pairs defining type and ID number of each item in this
(I = 1, IV/2)component.
*NTYPE meanings:
1 grid 8 quadrilateral
2 line 9 tetrahedron
3 patch 11 wedge
4 hyperpatch 12 hexahedron
5 node 19 coordinate frame
6 bar 22 multi-point constraints
7 triangle
NTYPEs 6-12 may have 100 or 200 added to the basic NTYPE. The
number of hundreds is usually the number of midside nodes.
Packet Type 31: Grid Data

31 ID IV KC
ID=Grid ID
IV =0 not/applicable
KC=1
X Y Z
X,Y,Z=Cartesian coordinates of Grid
APPENDIX A 4
File Formats
Packet Type 32: Line Data

32 ID IV KC
ID=Line ID
KC=3(for text files)
Data Card 1 to 3 Format (5E16.9/5E16.9/2E16.9,2I8)
B(1,1), B(2,1) B(3,1) ..... B(4,3) IG1 IG2
B(I,J)=4 x 3 matrix of geometric format line coefficients
IG1, IG2=End point grid ID’s
Packet Type 33: Patch Data

33 ID IV KC
ID=Patch ID
Data Card 1 to 10 Format 9(5E16.9/5), 3E16.9/2E16.9,4I8
B(1,1), B(2,1) B(3,1) ..... B(16,3) IG(4)
B(I,J)=16 x 3 matrix of geometric format patch coefficients
IG=4 corner grid ID’s
Packet Type 34: Hyperpatch Data

34 ID IV KC
ID=Hyperpatch ID
Data Card 1 to 40 Format 38(5E16.9/), 3E16.9/,8I8
B(1,1), B(2,1) B(3,1) ..... B(64,3) IG(8)
B(I,J)=64 x 3 matrix of geometric format hyperpatch coefficients
IG=8 corner grid ID’s
PART 2
Basic Functions
Packet Types 42, 43 or 44: GFEG Table for Line, Patch or Hyperpatch 1
(when created from a GFEG command)

IT ID IV 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)*
Header Card Format (I8, 3I8, I8, 5I8)
IDELTA N1 N2 N3 MAXMAG IFACE
IDELTA*=Integer parametric mesh increment
N1, N2, N3*=Number of nodes in ζ1, ζ2 and ζ3 directions
MAXMAG*=Maximum magnification power
IFACE*=Face degeneracy flags (faces 1 through 5)
Data Card 2 Format (I8, I8, 7X, 1A1, 7I8)
IFACE NCONDF NGTYPE NDF NCONF GCID PS NGDAT ISTMID ICFLAG
IFACE*=Face degeneracy flag (face 6)
NCONDF*=Condensation flag (0 = unreferenced)
NGTYPE*=Node type
NDF*=Number of degrees-of-freedom
NCONF*=Configuration number
GCID*=Analysis coordinate frame ID
PS*=Permanent single point constraint
NGDATA*=Pointer to auxiliary data
ISTMID*=Location of first added midnode
IGFLAG=Type of GFEG table: 0 = table created by GFEG
STRTCH
STRTCH(3)=Mesh ratios
AUXC
AUXC=Auxiliary mesh constants
Data Card 5 Format (8I8, I8, I8)
IDUM(8) IOLD NACTUL
IDUM(8)=Reserved for future use
IOLD=Table format flag (for database conversion)
NACTUL=Number of existing nodes
1
The format of the GFEG tables changed with Patran release 2.0.
APPENDIX A 4
File Formats
Data Cards 6 to KC Format (3E16.9, I8, I8)

XI(3) NFLAG 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 MSC.Patran
Packet Type 42, 43 or 44: GFEG Table for Line, Patch or Hyperpatch
(when created from a MESH command)

IT ID IV 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)*

Data Card 1 Format (I0I8)
NL1 NL2 NL3 NL4 NL5 IFACE
NL1,..NL4=Number of elements on edges 1 through 4
NL5=Number of elements through thickness (for hyperpatch)
IFACE*=Face degeneracy flags (faces 1 through 5)
Data Card 2 Format (I8, I8, 7X, 1A1, 7I8)
IFACE NCONDF NGTYPE NDF NCONF GCID PS NGDAT ISTMID ICFLAG
IFACE*=Face degeneracy flag (face 6)
NCONDF*=Condensation flag (0 = unreferenced)
NGTYPE*=Node type
NDF*=Number of degrees-of-freedom
NCONF*=Configuration number
GCID*=Analysis coordinate frame ID
PS*=Permanent single point constraint
NGDATA*=Pointer to auxiliary data
ISTMID*=Location of first added midnode
IGFLAG=Type of GFEG table: >0 = table created by GFEG
PART 2
Basic Functions

STRTCH
STRTCH=Mesh ratios for edges 1, 2 and 3
STRTCH
STRTCH=Mesh ratios for edge 4 and ζ3 direction (followed by one word
reserved for future use)
Data Card 5 Format (8I8, I8, I8)
IDUM(8) IOLD NACTUL
IDUM(8)=Reserved for future use
IOLD=Table format flag (for database conversion)
NACTUL=Number of existing nodes
Data Cards 6 to KC Format (3E16.9, I8, I8)
XI(3) NFLAG 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,
APPENDIX A 4
File Formats
Packet Type 45: CFEG Table

LPH ID LSHAPE DGFLAG MINID MIAXID
LPH=Type of region (2=line, 3=patch, 4=hyperpatch)
ID=ID of line, patch, or hyperpatch
LSHAPE=Element shape (2=bar, 3=tri, 4=quad, 5=tet, 7=wedge, 8=hex)
DGFLAG*=Degenerate element flag (1 indicates one or more degenerate
elements are present in this CFEG)
MINID=Minimum element ID
MAXID=Maximum element ID
NDIM LSHAPE NODES ICONF LPH ID LPROP NPROP
NDIM=Number of words per element record
LSHAPE=Element shape
NODES=Number of nodes per element
ICONF*=Element configuration
LPH=Type of region
ID=ID of region
LPROP*=Property ID flag (0 = PID, 1 = MID)
NPROP*=Property ID (+ = PID, - = MID)
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
*These are local node ID numbers corresponding to record numbers in the associated
GFEG table.
PART 2
Basic Functions
Packet Type 99: End of Neutral File

45 ID IV KC N1 N2
ID=CFEG sequence number
IV =Number of elements contained in region (NELS)
KC=2 + ((IV * NDIM) + 9)/10
N1*=Reserved
Header Card Format (I2, 8I8)
99 ID IV KC
ID=0 not/applicable
KC=1
APPENDIX A 4
File Formats
A.3 Session File/Journal File

Figure 1-1
Justification for A session file serves a variety of purposes. A session file is a compact
Session Files method of storing an entire model or just individual operations; it
contains no database. A session file is a text file containing a series of
directives (e.g., PCL commands) to be executed. These directives can be
used to re-create a model from scratch, be a transaction log for review
and/or modification, used as a macro/subprogram for performing a
sequence of commands repetitively, or support site and/or project
customization. In addition, MSC.Patran can process most ASM
NOODL’s contained in PATRAN 2.5 session files.
Recording Session Session files can be recorded from current models. Session files are
Files 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 File Names By convention, session files are named “<file>.ses”. The first portion
<file> is a user selectable base file name. The second portion, “ses”, is
the standard session file extension. In addition, a file revision is
appended to all session files. Session files created by MSC.Patran have
revision numbers that are either specified manually or generated
automatically. If a session file name is supplied without any extension
(indicated by the presence of a “.” in the file name), the standard
extension “.ses” is automatically appended.
Revision numbers are at least 2 digits long (starting with “01”) to
facilitate the listing of session files in increasing numerical order.
Note: Revisions greater than “99”are not listed in numerical order on the
forms.) Automatically generated revision numbers are always created as
one (1) greater than the highest existing revision number. Gaps in
revision numbers are not automatically filled in by the system.
For recording session file, the supplied name is checked for existence. If
this file does exist, then a new revision (starting with “01”) is created.
In order to play a session file, the supplied name is also checked for
existence. If this file does not exist, then the highest existing revision of
this file is used. If no revision exists, then no file is played.
PART 2
Basic Functions
Session File Session files are text files that may contain PCL statements or NOODL
Contents 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 ($#)
MSC.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 (p. 62) for more information.
APPENDIX A 4
File Formats
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 today’s 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 1-2. 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
Augmenting Physical Characteristics
• Dimensions and Tolerances
• Intrinsic Properties
Processing Information
Presentational Information
Figure 1-2 Categories of Product Definition

PART 2
Basic Functions
Concepts of the File Structure. A format to allow the exchange of a product definition
between CAD/CAM systems must, as a minimum, support the communication of geometric
data, annotation, and organization of the data. The file format defined by the IGES specification
treats the product definition as a file of entities. Each entity is represented in an application-
independent format, to and from which the native representation of a specific CAD/CAM
system can be mapped. The entity representations provided in the specification include forms
common the CAD/CAM systems currently available and forms which support the system
technologies currently emerging.
The fundamental unit of data in the file is the entity. Entities are categorized as geometry and
non-geometry. Geometry entities represent the definition for the physical shape and include
points, curves, surfaces, solids, and relations which are collections of similarly structured
entities. Non-geometry entities typically serve to enrich the model by providing a viewing
perspective in which a planar drawing may be composed and by providing annotation and
dimensioning appropriate to the drawing. ! entities further serve to provide specific attributes
or characteristics for individual entities or groups of entities and to provide definitions and
instances for groupings of entities. The definitions of these groupings may 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.
APPENDIX A 4
File Formats
A.5 PATRAN 2.5 Results Files

All results obtained from an external analysis code (other than the P/FEA module) were written
to one of five different types of PATRAN 2.5 -compatible results files in order to be processed by
PATRAN 2.5: a DISPLACEMENT, FORCE, NODAL, ELEMENT, or BEAM Results File.
In this section, we will outline the formats of the various results file types. The information
contained in this section can be used to write translators for your own in-house analysis codes
or for test data.
Displacement or Force Results Files

Displacement results files are a special case of the NODAL RESULTS FILES described in Nodal
Results Files (p. 485). Displacement results files contain the displacements calculated by the
analysis code at the node points. There are usually 6 columns in a displacement result file. The
first 3 are the X, Y and Z components of translation and the second 3 are the X, Y and Z
components of the rotation at the nodes. A single column of a displacement results file can be
used for contouring. For example, to contour the Y-component of displacement. MSC.Patran
will also postprocess the first 3 columns to contour the resultant displacement and/or to provide
deformed mesh plots. Displacement or rotations vector plots can also be generated.
Force results files have the same format as displacement results files. The only difference
between the two is that a force file contains the forces and moments at nodes instead of
displacements and rotations. Force results files can be used to generate force or moment vector
plots. For example, reaction forces are commonly displayed this way. Weld element results are
also calculated from the results in a force results file containing node force balances.
Most Analysis Model translators create a different DISPLACEMENT or FORCE RESULTS FILE
for each load case. If you desire to write your own results translator from your own in-house
analysis program, you should load the results in the scheme mentioned above: X, Y, Z
translations or forces followed by X, Y, and Z rotations or moments.
MSC.Patran will interpret the X, Y, and Z values of displacement, force, rotation, or moment in
the coordinate system defined in the associated Patran 2.5 Results Files (p. 40).
Both a binary and a text version of displacement and force results files are supported in
MSC.Patran. The format of the file will be automatically determined before reading in the data.
PART 2
Basic Functions
Sample Displacement/Force Results Data File

Binary Version
Record 1: TITLE, NNODES, MAXNOD, DEFMAX, NDMAX, NWIDTH
Record 2: SUBTITLE1
Record 3: SUBTITLE2
Record 4: NODID(1), DX(1), DY(1),DZ(1),RX(1),
RY(1),RZ(1)
Record 5: NODID(2), DX(2), DY(2), DZ(2), RX(2),
RY(2),RZ(2)
Record N+3: NODID(N), DX(N),DY(N),DZ(N),RX(N),

RY(N), RZ(N)
Parameter Description
TITLE 80A1 title stored in an 80 word real or integer array

(1 character per word).
SUBTITLE1 Same format as TITLE
NNODES Number of nodes (integer)

MAXNOD Highest node ID number (integer)
DEFMAX Maximum absolute displacement (real)
NDMAX ID of node where maximum displacement occurs (integer)
NWIDTH Number of columns after NODID for displacement information (integer)
(usually = 3 for DX, DY, DZ or 6 for DX, DY, DZ, RX, RY, RZ)
NODID Node ID number (integer)
DX X displacement or force component (real)

DY Y displacement or force component (real)
DZ Z displacement or force components (real)
RX X rotation or moment component (real)
RY Y rotation or moment component (real)
RZ Z rotation or moment component (real)
Text Version
Record 1: TITLE (80A1)
Record 2: NNODES, MAXNOD, DEFMAX, (2I9, E15.6, 2I9)
NDMAX, NWIDTH
Record 3: SUBTITLE1 (80A1)
Record 5 to n+4: NODID, (DATA(J), J=1, NWIDTH) (I8, (5E13.7))
APPENDIX A 4
File Formats
Nodal Results Files

Nodal results files contain the results quantities that have been calculated at the node points. Up
to 200 columns of results quantities can be stored for each node. MSC.Patran will process a single
column of a nodal results file at a time and use that data to produce contour plots. MSC.Patran
allows nodal results files to be used for element color-coding by averaging the data at the
elements. Nodal results files can also be used for vector plotting and x-y plotting.
Most analysis model translators create a different nodal results file for each load case. Each of
the MSC supported translator documents contains a table listing the type of results stored in
each column. If you desire to write your own results translator from your own in-house analysis
program, you must document the results contained in each column of the results file. A user can
then process a particular column knowing that the required results quantity was put in that
column by the translator.
Both a binary and a text version of nodal results files are supported in MSC.Patran. The format
of the file will be automatically determined before reading in the data.
Binary Version
Record 1: TITLE, NNODES, MAXNOD, DEFMAX, NDMAX, NWIDTH
Record 2: SUBTITLE1
Record 3: SUBTITLE2
Record 4: NODID(1), (DATA(J), J = 1, NWIDTH)
Record 5: NODID(2), (DATA(J), J = 1, NWIDTH)
.
Record N+3: NODID(N), (DATA(J), J=1, NWIDTH)

(1 character per word).
NNODES Number of nodes (integer)
MAXNOD Highest node ID number (integer)
DEFMAX Maximum absolute displacement (real)
NDMAX ID of node where maximum displacement occurs (integer)
NWIDTH Number of columns after NODID for nodal information (integer)
NODID Node ID number (integer)
DATA Result quantities organized by column index (real)
Text Version
Record 2: NNODES, MAXNOD, DEFMAX, (2I9 E15.6, 2I9)
NDMAX, NWIDTH
Record 5 to n+4: NODID, (DATA(J), J=1, NWIDTH) (I8, (5E13.7))
Note: MAXNOD, DEFMAX, NDMAX can be set to zero unless it is a displacement results.
PART 2
Basic Functions
Sample Nodal Results Data File

2 2 0 0 10
TITLE1
SUBTITLE 2
1 +2.42755E+00 +2.93590E+00 +1.55693E+00 +1.01315E+00 +4.32207E-01
+1.08574E+00 +3.02910E+00 +3.80189E+00 +3.39958E-01 +1.63880E+00
2 +1.14613E+00 +2.32387E+00 +2.76658E+00 +7.53095E-01 +5.10357E-01
+2.12205E+00 +4.33402E+00 +4.41597E+00 -5.84647E-01 +1.74512E+00
Element Results Files

Element results files contain the elemental results quantities for each Analysis Model element
analyzed. Up to 200 columns of results quantities can be stored for each element. MSC.Patran
will process a single column of an element results file at a time and use that data to color code
elements. Element results files can be used for contouring; however, the data read from the
element results file will be averaged at the nodes in order to be able to produce contour plots.
Element results can also be used for x-y plot data generation.
Most Analysis Model translators create a different ELEMENT RESULTS FILE for each load case.
Each of the MSC supported translator documents contains a table listing the type of results
stored in each column. If you desire to write your own results translator from your own in-house
analysis program, you must document the results contained in each column of the results file. A
user can then process a particular column knowing that the required results quantity was put in
that column by the translator.
Both a binary and a text version of element results files are supported in MSC.Patran. The format
of the file will be automatically determined before reading in the data.
Binary Version
Record 1: TITLE, NWIDTH
Record 2: SUBTITLE1
Record 3: SUBTITLE2
Record 4: ID, NSHAPE, (DATA(J), J=1, NWIDTH)
Record 5: ID, NSHAPE, (DATA(J), J=1, NWIDTH)
.
Record n+3: ID, NSHAPE, (DATA(J), J=1, NWIDTH)
Record n+4: ID = 0 or end-of-file
(1 character per word)
SUBTITLE1 (same format as TITLE)
NWIDTH Number of columns of data stored in the file (integer)

ID Element identification number (integer)
NSHAPE Essential shape code (BAR = 2, TRI = 3, QUAD = 4, TET = 5,

PYR = 6, WEDG = 7, HEX = 8; integer)

APPENDIX A 4
File Formats
Text Version
Record 2: NWIDTH (I5)
Record 5 to n+4: ID, NSHAPE, (DATA(J), J=1,NWIDTH) (2I8, /, (6E13.7))
Sample Element Results File

19
STRESS/STRAIN AT TIME: .00500058
1 4
.1483126E+05 .1492715E+05-.3057466E+03 .2852407E+01-.5369175E+01 .0000000E+00
.9919469E+04 .1488886E+05-.8247605E+04-.8088444E+04 .3114060E+03 .2852407E+01
-.5369175E+01 .0000000E+00-.5445350E+04 .8186974E+04 .0000000E+00 .2237059E+04
.3357410E+04
2 4
.6935732E+04 .1174489E+05 .2986205E+03-.3140930E+03 .2887558E+03 .0000000E+00
.6226875E+04 .1023987E+05-.2068523E+04-.6511836E+04-.1064728E+03-.3140930E+03
.2887558E+03 .0000000E+00-.2860119E+04 .5766014E+04 .0000000E+00 .1683378E+04
.2535498E+04
3 4
-.8141948E+04 .3225449E+04-.2815713E+04-.3211482E+03-.1085647E+04 .0000000E+00
-.1638833E+04 .1125793E+05 .1245072E+05 .7406104E+03 .3047678E+04-.3211482E+03
-.1085647E+04 .0000000E+00 .4397110E+04 .1319897E+05 .0000000E+00 .1379138E+04
.2083729E+04
PART 2
Basic Functions
Beam Results Files

BEAM RESULTS FILES are a special type of element results file used to process data at various
stations along beam elements. The file contains the elemental results quantities for up to 20
stations along each Analysis Model beam element. Up to 200 columns of results quantities can
be stored for each element station. MSC.Patran will process individual columns of an element
results file to create an x-y plot of the distribution of the results along a beam or a set of beams.
Most Analysis Model translators create a different BEAM RESULTS FILE for each load case.
Each of the MSC supported translator documents contains a table listing the type of results
stored in each column. If you write your own results translator from your in-house analysis
program, you must document the results contained in each column of the results file. A user can
then process a particular column knowing that the required results quantity was put in that
column by the translator.
Only the binary version of beam element results files is supported in MSC.Patran.
Sample Beam Results File

Binary Version
Record 1: TITLE, NWIDTH
Record 2: SUBTITLE1
Record 3: SUBTITLE2
Record 4: ID(1), STAT(1), (DATA(J), J=1, NWIDTH)
Record 5: ID(1), STAT(2), (DATA(J), J=1, NWIDTH)
.
Record n+3: ID(1), STAT(n), (DATA(J), J=1, NWIDTH)
Record n+4: ID(2), STAT(1), (DATA(J), J=1, NWIDTH)
Record n+5: ID(2), STAT(2), (DATA(J), J=1, NWIDTH)
.
Record n+m+3: ID(2), STAT(m), (DATA(J), J=1, NWIDTH)
Record n+m+4: ID(N), STAT(1), (DATA(J), J=1, NWIDTH)
Record n+m+5: ID(N), STAT(2), (DATA(J), J=1, NWIDTH)
.
Record n+m+k+3 ID(N), STAT(k), (DATA(J), J=1, NWIDTH)
(1 character per word)

NWIDTH Number of columns of data stored in the file (integer)
ID Beam element identification number (integer)
STAT Fractional station along the beam (real between 0. and 1.).
STAT(1) Should always be 0.
STAT(m), STAT(n), and STAT(k) Should always be 1.
Note: A maximum of 20 stations is allowed for each beam.

APPENDIX A 4
File Formats
PATRAN 2.5 Results Template Files

As mentioned above, a set of results template files (xxxx.res_tmpl) is provided in the
MSC.Patran delivery which map information from the PATRAN 2.5 results file for MSC.Patran.
The specified results template file is used during the import of the PATRAN 2.5 results file.
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

KEYLOC integer 1 to the maximum Column number where translation
number of columns in key is found, or 0 if no translation
the results file, or key is required.
zero.
TYPE character string scalar, vector, tensor, If scalar, vector or tensor, TYPE is
or END. the dimension of the results
quantity. If END, TYPE indicates
the end of the template file.
KEY integer Any value found in Value of translation key (required if
the column indicated KEYLOC does not equal zero). This
by KEYLOC. is often an element type number.
COLUMN integer 1, 3 or 6 Column numbers to be translated.
PRI character string Character string up to Primary label definition. This will
80 characters in appear in the “Select Results” box of
length. the Results Display form.
SEC character string Character string up to Secondary label definition. This will
80 characters in appear in the “Select Results” box of
length. the Results Display form.
CTYPE character string global, nodal, elem, Type of element coordinate frame
user, matl, ply, edge (required if TYPE is vector or
or curve. tensor).
The template file is organized in the following manner:

Line 1: KEYLOC = <value>
Line 2: TYPE= <value>
Line 3: KEY = <value> (required if KEYLOC does not equal zero.)
Line 4: COLUMN = <value(s)>
Line 5: PRI = <value>
Line 6: SEC = <value>
Line 7: CTYPE=<value> (required if TYPE is vector or tensor.)
Lines 8 through n - 1: Repeat lines 2 through 7 as many times as
required.
Line n: CTYPE = END
PART 2
Basic Functions
Two examples of a results template file are presented below. Example 1 shows a template file for
a results file that does not require the use of an element type key. Example 2 uses the element
type key to import results for two different types of MSC.Nastran elements from an element
results file (.els) generated by the PATRAN 2.5 MSC.Nastran translator (naspat).
Example 1 Example 2
KEYLOC = 0 KEYLOC = 19
TYPE = SCALAR TYPE = SCALAR
COLUMN = 11 KEY = 67
PRI = Stress COLUMN = 11
SEC = von Mises PRI = Stress
TYPE = TENSOR SEC = von Mises
COLUMN = 25, 26, 27, 28, 29, 30 TYPE = SCALAR
PRI = Stress KEY = 33
SEC = Components COLUMN = 11
CTYPE = ELEM PRI = Stress
TYPE = END 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
where:
column 15 and 25 represents the XX component of stress
column 16 and 26 represents the YY component of stress
column 27 represents the ZZ component of stress
column 18 and 28 represents the XY component of stress
column 29 represents the YZ component of stress
column 30 represents the ZX component of stress
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 MSC.Nastran Preference Guide (p. 1) in the MSC.Patran
MSC.Nastran Preference Guide, Volume 1: Structural Analysis.
APPENDIX
Printing Options
B
■ Introduction
■ Device-dependent Hardcopy File
■ Additional Information for Printers/Plotters
■ If Your Plot Does Not Turn Out as Expected
■ Hardware Setup
■ Supported Hardware for MSC.Patran Hardcopy

PART 2
Basic Functions
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 MSC.Patran. It is designed to be flexible and
easy to use.
MSC.Patran provides user control over creating hardcopy output from within the Print forms.
Refer to File>Print (p. 178) 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 (p. 491).
APPENDIX B 4
Printing Options
B.2 Device-dependent Hardcopy File
Postscript Default This will translate a file into a device-specific file called ps.plt. This
file consists of commands which have been translated into the
PostScript language. The PostScript driver will support gray scale or
256 colors, depending on the hardcopy parameter setup and/or the
type of printer to which the device-specific file is sent.
PatranHard Default Produces a patran.hrd file which cannot be sent to a printer.
CGM This will generate and translate a temporary patran.hrd file into a
device specific file called cgm.plt. This file consists of commands which
have been translated to conform to the Computer Graphics Metafile
Standard.
HPGL This will generate and translate a temporary patran.hrd file into an
hpgl.plt device-specific file. This file consists of commands which
have been translated into the Hewlett-Packard Graphics Language.
HPGL/2 Default This will generate and translate a temporary patran.hrd file into a
device-specific file called hpgl2.plt. This file consists of commands
which have been translated into the Hewlett-Packard/2 Graphics
Language. The HPGL-2 Graphics Language is a new standard for
sending information to HPGL-2 plotters. It uses a new data compacted
feature to shorten transmission time, and new high level HPGL-2
commands for maximum efficiency. All new plotters sold by
Hewlett-Packard support the HPGL-2 language.
PatranHard to Post- This will translate a patran.hrd file into a device-specific file called
Script Default ps.plt. This file consists of commands which have been translated into
the PostScript language. The PostScript driver will support gray scale
or 256 colors, depending on the hardcopy parameter setup and/or the
type of printer to which the device-specific file is sent.
PART 2
Basic Functions
B.3 Additional Information for Printers/Plotters
Internal Memory 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 Most plotters and some printers have front panels that allow you to control
Hardware Settings the printer/plotter settings. Please refer to your printer/plotter manual for
information on how to modify these settings.
APPENDIX B 4
Printing Options
B.4 If Your Plot Does Not Turn Out as Expected

There are a number of reasons why your plot may not appear at your printer/plotter. Some of
these reasons could be:
Bad Hardware Con- Verify that the connection between the workstation and the
nection 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/Plot- Ensure that the destination defined in the hardcopy form is valid. By
ter Destination checking the hardware connection above, you will also be checking the
destination. Submitting a test program is highly recommended to verify
your setup.
Network Problems Sometimes network connections can be blamed for hardcopy plots not
being submitted to the desired printer/plotter. If possible, attempt to
bypass the network when submitting a test plot to eliminate the network
as a possible source of error.
Hardware Memory Usually printers/plotters come with enough RAM for most plots to be
plotted satisfactorily. If you consistently produce very large plots (device-
specific hardcopy file is 1.5 Mb or more) you may need to upgrade the
printer/plotter internal memory. Please consult your printer/plotter
manufacturer for more information.
Hardware Problems Submitting a test plot can also determine if your printer/plotter
hardware is the problem. Sometimes turning the hardware OFF and ON
can solve the problem.
The manual for your printer/plotter may contain additional information to help you diagnose
any problems.
PART 2
Basic Functions
B.5 Hardware Setup

There are numerous ways to set up printers/plotters so that the four MSC.Patran hardcopy
drivers (HPGL, HPGL-2, CGM and PostScript) can communicate with the hardware. The most
common ways are:
Laser Printer Black and White or Color.

Spooler
Plotters Electrostatic, Inkjet, Pen
Parallel (Centronix) Preference
Serial (RS-232-C) Preference
Modular Preference (HP only)
For any type of communications setup, you will need to know:

1. Command to submit your device-specific hardcopy file to the hardware
2. Name of device (destination)
At MSC, we have the following setup (your setup may differ):
Laser Printers
Submit Command lp (HP700 platform)
lpr (Solaris/SGI/Digital UNIX/IBMRS6K/Windows NT)
Destination • Multiple destinations are setup in
/etc/printcap and /usr/spool.
• Destinations in Windows NT are setup in the Printer Setup menu.
Example: lpr -Plw2 ps.plt.01
Plotters
Submit Command cat
Destination Name of serial or parallel port on the workstation that is connected to the
plotter.
Example: cat hpgl2.plt.01 > /dev/ttya
Again, keep in mind that your setup could be very different from the above. Your system
administrator should be able to assist MSC.Patran users with printer/plotter setups for your
computer environment.
APPENDIX B 4
Printing Options
B.6 Supported Hardware for MSC.Patran Hardcopy
PostScript Laser Printers (e.g., Tektronix Phaser II Pxi)
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 Any device conforming to the CGM protocol.

PART 2
Basic Functions
APPENDIX
Mass Properties
C
■ Summary of Mass Properties
PART 2
Basic Functions
C.1 Summary of Mass Properties

Overview
The Mass Properties forms provide the capability to calculate mass properties for all or any part
of a model. Both FEM and geometric entities are supported, as are most of the widely used
analysis model types. These include 2D Axisymmetry, 2D Plane Stress, 2D Plane Strain, and 3D.
The primary Mass Properties form is accessed from the Tools menu which is located on the main
form.
MSC.Patran generates a complete set of mass properties for the user-specified region and
outputs all data to a spreadsheet. This set includes the mass and volume, the center of gravity
(CG), the inertia tensor at the origin of the reference frame, the inertia tensor at the CG, the
principal inertias at the CG, the radii of gyration corresponding to the principal inertias at the
CG, and the principal directions for the inertia tensor at the CG. The principal directions at the
CG are given in three forms: (1) as three orthogonal unit vectors, (2) as a triad of space-fixed
rotation angles in a 3-2-1 sequence, and (3) as a triad of body-fixed rotation angles in a 3-1-3
sequence. Where applicable, the mass properties are provided in both the reference Cartesian
frame and in the user-specified coordinate frame. For the special case of displaying mass
properties on an individual element basis, additional output of plate thickness, plate surface
area, bar area, bar length, and the property type name (ie. Stan. Membrane (CQUAD4)) are
given. Output options include the graphical display of the principal axes, the creation of a
coordinate frame aligned with the principal axes (except for display by entity mode), and the
creation of a report file. The principal axes are plotted in proportion to the magnitudes of the
radii of gyration of the corresponding principal inertias, as shown below:
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 MSC.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-
APPENDIX C 4
Mass Properties
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. MSC.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 cross-sectional 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 property’s value type. For a FEM entity, a field property is evaluated
at the centroid of the entity if the property’s value type is real scalar, and is integrated over the
entity if the property’s value type is element nodal. Discrete FEM fields are supported only for
real scalar properties of FEM entities.
MSC.Patran attempts to treat all entities as though they are consistent with the selected analysis
model type, regardless of the element type of the entity’s 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, MSC.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 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.
PART 2
Basic Functions
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. MSC.Patran calculates the mass of the equivalent 1D hoop by multiplying the input
mass by 2πr. 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 2πr. 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.
5
I N D E X
MSC.Patran Reference Manual
Part 1: Basic Functions
I N D E X
MSC.Patran
Reference
Manual
Part 1: Basic
A design studies, 405
displacement results files, 483
Functions ACIS (sat) files, 134 display
analysis manager, 446 color configurations, 285
applications menu, 10
mass properties, 498 properties, 285
automatic centering, 259
E
B element results files, 486
beam library, 382 EPS files, 185
beam results files, 488 Euclid 3 files, 109
boolean lists, 371 experimental data fitting, 446
exporting models, 51
IGES files, 167
C Parasolid (xmt) Transmit files, 165
Patran 2.5 Neutral files, 162
CADDS files, 122
STEP files, 172
CATIA files, 96
express neutral files, 82
CGM, 187, 491
clipping, 263
clipping perspective, 263
clipping plane, 261 F
color configurations, 285 feature recognition, 450
command line comments, 19 file commands, 53
connector, 450 file formats
coordinate system, 258 IGES file, 481
creating lists, 366 journal file, 479
current viewport, 241 neutral file, 455
session file, 479
file menu, 10
D file types
hardcopy file, 40
database
IGES file, 40
freeing unused space, 50
journal file, 40
databases
MSC.Patran FEA results file, 40
closing, 50
PATRAN 2.5 results files, 40
creating, 50
PATRAN database, 40
opening, 50
PATRAN flat file, 40
rebuilding
, 51
reverting, 50
saving, 50
INDEX
files importing models, 51

p3epilog.pcl, 46 ACIS (sat) files, 134
p3prolog.pcl, 46 CADDS 5 files, 122
session, 47 CATIA files, 96
settings.pcl, 41, 46 Euclid 3 files, 109
template database, 47 Express neutral files, 82
focal point, 260 I-DEAS files, 111
force results files, 483 IGES files, 88
functional assignments, 5 MSC.Patran databases, 64
Parasolid (xmt) files, 133
PATRAN 2.5 neutral files, 76
G Pro/ENGINEER files, 115
STL files, 153
geometry
Unigraphics files, 125
direct geometry integration, 2
importing modesl
group
Parasolid (xmt) files, 131
attributes, 209
importing results, 51
current, 209
membership, 208
menu, 10
modify, 221 J
names, 208 journal file, 40, 479
posted, 209
status, 209
target, 209 L
transformations, 210
laminate modeler, 446
list processor, 38
H
hardcopy M
CGM, 491
mass properties, 372, 498
device-dependent, 491
midplane meshing, 449
HP-GL, 491
model space, 258
HP-GL/2, 491
model variables, 397
postscript, 491
MSC.Fatigue, 445
printers/plotters, 492
MSC.Patran, 2
setup, 494
MSC.Patran database, 64
supported hardware, 495
HP-GL, 189, 491
HP-GL/2, 191, 491
N
named views, 263
I neutral file, 40, 455
neutral system, 454
I-DEAS files, 111
nodal results files, 485
IGES file, 40, 481
IGES files, 88, 167
image files, 52
O
observer position, 261
INDEX 5
P R
P/FEA 2.5 results file, 40 rebar definitions, 443
p3epilog.pcl file, 46 reclaim database space, 50
p3epolog.pcl file, 41 recording session file initialization, 47
p3prolog.pcl file, 41, 46 refresh icon, 12
page setup, 182 reports, 52
parametric modeling, 449 results templates, 435
Parasolid (xmt) files, 131, 133 rotor dynamics, 446
Parasolid (xmt) Transmit files, 165
PATRAN 2.5 neutral file, 76
Patran 2.5 neutral files, 162 S
PATRAN 2.5 results files, 483
screen space, 258
Patran 2.5 Results Files, 40
select corners, 262
PATRAN command language, 4
session file, 51, 479
PATRAN results files, 40
session files, 47
PCL
settings.pcl file, 41
PATRAN command language, 4
hardcopy preferences, 46
playing session file initialization, 47
startup files, 41
postscript, 183, 491
STEP files, 172
postscript files, 179, 180
importing, 138
pre release tools, 449
STL files, 153
preferences
analysis, 4, 320, 325
finite element, 348
geometry, 346 T
global, 338 template database file, 47
graphics, 339
menu, 10
mouse, 340 U
picking, 342
undo, 176
report, 345
Unigraphics files, 125
print
CGM, 187
HP-GL, 189
HP-GL/2, 191
postscript, 183
printer configuration file, 193
printing
page setup, 182
UNIX, 181
Windows NT, 178
printing images, 52
Pro/ENGINEER files, 115
properties, 285
Q
quitting, 52
INDEX
V
view
automatic centering, 259
clipping, 263
clipping perspective, 263
clipping plane, 261
clipping/capping, 260
coordinate system, 258
focal point, 260
menu, 10
model space, 258
named views, 263
observer position, 261
screen space, 258
select corners, 262
viewing plane, 261
viewport menu, 10
window center, 261
zoom, 262
viewing plane, 261
viewport, 3, 9, 10, 240
menu, 10
W
window center, 261
Z
zoom, 262

Part1 Basic Functions

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Part1 Basic Functions

Hochgeladen von

Copyright:

Verfügbare Formate

Return C O N T E N T S

MSC.Patran Reference Manual

■ The Tool Bar, 11

■ The Applications Bar, 18

■ History Window and Command Line, 19

■ The Group Menu, 217

■ The Viewport Menu, 243

■ The Display Menu, 287

■ The Preferences Menu, 323

INDEX ■ MSC.Patran Reference Manual, 501

■ Using MSC.Patran for Engineering Analysis

1.1 Introducing MSC.Patran

Engineering Modeling Functionalities. Extensive engineering capabilities, including:

Analysis Preferences. Linkage to commercial analysis solvers and proprietary in-house

PATRAN Command Language (PCL). Scripting language for customization, task

MSC.Mvision. Integrated materials database.

1.2 MSC.Patran Framework

Managing Large Models in MSC.Patran. All project-related information is stored in files of

Patran Command Language. MSC.Patran provides an environment into which proprietary

1.3 Using MSC.Patran for Engineering Analysis

Finite Element Modeling. MSC.Patran’s mapped or automatic meshing algorithms generate

Functional Assignments. Functional assignments is a collective term for applied loads,

Postprocessing. Postprocessing capabilities include visualization of the deformed model,

1.4 HTML Based Online Help

■ The Menu Bar

■ The Tool Bar

■ The Applications Bar

■ History Window and Command Line

2.1 Modeling Window

MSC.Patran Main Form

Applications Bar Menu Bar Tool Palettes

Command Line History List

box_beam.db - default_viewport- default_group - Entity

Y Global Coordinate Frame

2.2 The Menu Bar

File Group Viewport Viewing Display Preferences Tools Insight Help

Menu Bar Keywords

2.3 The Tool Bar

System Tool Palette

Print Creates a hardcopy file to print or plot.

Refresh Redisplays the contents of the screen.

Mouse Function Tool Palette

Mouse Rotate XYZ--rotate around the X and Y axes.

Mouse Rotate Z--rotate around the Z axis.

Mouse Translate X--translate in the X and Y directions.

Mouse Zoom--zoom in and out of the screen.

Viewing Tool Palette

View Corners--zooms in on a cursor-defined rectangular area.

View Center--moves the window’s center to a cursor picked location.

Rotation Center--selects a view’s rotation center (point, node or screen position).

Zoom Out--incrementally zooms out from the model by a factor of two.

Zoom In--incrementally zooms in on the model by a factor of two.

Display Tool Palette

Wireframe--renders the model in wireframe style.

Hidden Line--renders the model in hidden line style.

Smooth Shaded--renders the model in smooth shaded style.

Show Labels--plots all entity labels.

Hide Labels--erases all entity labels.

Model Orientation Tool Palette

Rear View--Rotations: X = -180, Y = 0, Z = -180

Top View--Rotations: X = 90, Y = 0, Z = 0

Bottom View--Rotations: X = -90, Y = 0, Z = 0

Left Side View--Rotations: X = 0, Y = 90, Z = 0

Right Side View--Rotations: X = 0, Y = -90, Z = 0