

Patran 2019

Release Guide
Corporate Europe, Middle East, Africa
MSC Software Corporation MSC Software GmbH
4675 MacArthur Court, Suite 900 Am Moosfeld 13
Newport Beach, CA 92660 81829 Munich, Germany
Telephone: (714) 540-8900 Telephone: (49) 89 431 98 70
Toll Free Number: 1 855 672 7638 Email: [email protected]
Email: [email protected]

Japan Asia-Pacific
MSC Software Japan Ltd. MSC Software (S) Pte. Ltd.
Shinjuku First West 8F 100 Beach Road
23-7 Nishi Shinjuku #16-05 Shaw Tower
1-Chome, Shinjuku-Ku Singapore 189702
Tokyo 160-0023, JAPAN Telephone: 65-6272-0082
Telephone: (81) (3)-6911-1200 Email: [email protected]
Email: [email protected]

Worldwide Web
www.mscsoftware.com

Support
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

Disclaimer
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with the
terms of such license.
MSC Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended
to be exhaustive or to apply to any particular engineering problem or design. MSC Software Corporation assumes no liability or
responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein.
User Documentation: Copyright 2019 MSC Software Corporation. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of MSC Software Corporation is prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from MSC Software suppliers.
Additional terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms
and conditions and/or notices may be set forth in documentation and/or at http://www.mscsoftware.com/thirdpartysoftware (or successor
website designated by MSC from time to time).
The MSC Software Logo, MSC, MSC Nastran, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered trademarks
of MSC Software Corporation in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group. SAMCEF is a
trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of Livermore Software
Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned subsidiary of ANSYS Inc. ACIS is a
registered trademark of Spatial Technology, Inc. ABAQUS, and CATIA are registered trademark of Dassault Systemes, SA. FLEXlm
and FlexNet Publisher are trademarks or registered trademarks of Flexera Software. PostScript is a registered trademark of Adobe
Systems, Inc. PTC and Pro/ENGINEER are trademarks or registered trademarks of Parametric Technology Corporation or its
subsidiaries in the United States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of Siemens
Product Lifecycle Management, Inc. All other brand names, product names or trademarks belong to their respective owners.
Revision 0. February 18, 2019

P3:V2019:Z:Z:Z:DC-REL-PDF
Documentation Feedback
At MSC Software, we strive to produce the highest quality documentation and welcome your feedback. If you have
comments or suggestions about our documentation, please write to us at [email protected].
Please include the following information with your feedback:
 Document name
 Release/Version number
 Chapter/Section name
 Topic title (for Online Help)
 Brief description of the content (for example, incomplete/incorrect information, grammatical errors, information
that requires clarification or more details and so on.)
 Your suggestions for correcting/improving documentation
You may also provide your feedback about MSC Software documentation by taking a short 5-minute survey at:
http://msc-documentation.questionpro.com.

Note: The above mentioned e-mail address is only for providing documentation specific feedback. If you have
any technical problems, issues, or queries, please contact Technical Support.
Contents
Patran Release Guide

Contents

1 Patran 2019 at a Glance

Key Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported OS/Hardware Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Supported CAD Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Known limitations in current release: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Supported Analysis Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 General Enhancements
Insight Ported to QT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Enhanced HDF5 Results Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Maximum/Minimum Load Case Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SuperGroup Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Contact Model Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Enhanced Group Mirror Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Crash Reporting System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Nastran File Import and Results Format Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Write Stored Precision (Nastran BDF Files). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Index
vi Patran Release Guide
 Chapter 1: Patran 2019 at a Glance.
MSC Nastran Implicit Nonlinear (SOL 600) User’s GuidePatran Release Guide

1 Patran 2019 at a Glance


Key Highlights 2
 Supported OS/Hardware Platforms 3

Supported CAD Access 4

Supported Analysis Preferences 6
 Technical Support 7
2 Patran Release Guide
Key Highlights

Key Highlights

General Enhancements
The following general enhancements have been implemented in this version. Please see Chapter 2 for details
on each.
 Insight Ported to QT, 9
 Enhanced HDF5 Results Support, 10
 Maximum/Minimum Load Case Tracking, 11
 SuperGroup Support, 16
 Contact Model Checking, 18
 Enhanced Group Mirror Support, 21
 Crash Reporting System, 24
 Nastran File Import and Results Format Support, 25
 Write Stored Precision (Nastran BDF Files), 26
 Chapter 1: Patran 2019 at a Glance 3
Supported OS/Hardware Platforms

Supported OS/Hardware Platforms

Vendor Description
Windows For information on Operating Systems and Hardware support, please see Microsoft Windows
Requirements (p. 63) in the Patran Installation and Operations Guide
Linux For information on Operating Systems and Hardware support, please see Linux Requirements
(p. 76) in the Patran Installation and Operations Guide.

For a complete description of these configurations, see Required Hardware & Software Configurations (Ch. 5) in the
Patran Installation and Operations Guide.

Important: 1. Patran 2019 complies with IPv6 specification with the following exception:

 Analysis Manager (expected to be compliant in a subsequent release)

2. The Classic version of Patran has been discontinued from this release. Patran 2019 is
available only in the latest QT (QT5) framework with the following exceptions:

 Classic Fatigue forms have not been updated to QT.

 DTFatigue forms have not been upgraded to the latest version of QT and are still in the
old version (QT3).
3. To meet user expectations and maintain Patran current with the latest technology, the
following features of Patran 2019 may not be available in future releases. Please plan
accordingly.

 Express Neutral Files import/export

 IGES, STEP AP203/209, VDA, CATIA, and UG models import/export via non-
Parasolid mechanism, meaning the following features and corresponding licenses will no
longer work:
• PA_IGES_Access
• PA_AP203_Access
• PA_AP209_Access
• PA_VDA_Access
• PA_CATIA_Access
• PA_UG_Access
Import and export via the Parasolid mechanism will remain and may be the only method
for import and export of the above mentioned CAD file formats.
4 Patran Release Guide
Supported CAD Access

Supported CAD Access

The following CAD systems are supported using the new CAD import methods.

Windows Linux
ACIS Up to R27 Up to R27
CATIA V4 All 4.xx All 4.xx
CATIA V5 R10 to R28 R10 to R28
IGES 3, 5, 5.2, 5.3 3, 5, 5.2, 5.3
Pro/ENGINEER / Creo (.prt/.asm) WF 4, WF5, to Creo 5 WF 4, WF5, to Creo 5
SolidWorks Up to 2018 Up to 2018
STEP 203, 209, 214 203, 209, 214
Unigraphics NX 5.0, 6.0, 7.0, 7.5, 8.0, NX 5.0, 6.0, 7.0, 7.5, 8.0.
9.0, 10, 11, 12 9.0, 10, 11, 12
Parasolid 30.1 30.1

Known limitations in current release:

1. Occasionally closed surfaces are not converted to solids on import of IGES, ACIS, and CATIA V4.
Instead of solids, surfaces are imported.
2. There is no support for import of nodes/elements from IGES files using the “Import to Parasolid”
toggle.
3. Export of IGES files may result in loss of some surfaces/solids - not all entities are exported.
4. Some IGES and Pro/ENGINEER parts import unexpected surfaces.
5. Some IGES, STEP, and ACIS parts import a broken or incomplete model.
6. The global element length (GEL) that gets set and used during import is different than previously
supported import methods.
7. Certain files may import using the default import method but may not import using other (non-
default) methods or vice-versa (using the “Import to Parasolid” toggle).
8. Editing/updating features using automatic feature recognition leads to different geometry as
compared to previously supported import methods.
9. Mid-surfaces are different compared to previously supported import methods.
10. The naming of groups is different than previous supported import methods for all CAD geometry
types.
11. Unigraphics (UG) parts containing defined features do not recognize features like the deprecated UG
import in Patran.
 Chapter 1: Patran 2019 at a Glance 5
Supported CAD Access

12. Take care as there may be a mismatch of the native CAD geometry units and Patran model units,
with no informative message.
13. Exported files that are subsequently imported back into Patran may not contain the same exact
entities as sometimes solids are imported as surfaces.
14. CATIA V5 import notes:
• Hidden entities are imported by default. Turn OFF the "Import Attributes" option on the Catia
Options form if this is not desired.
• Import of hidden entities may make the model appear "zoomed out."
• Only Entities from the Master Workspace are imported.
• Planes are ignored and not imported.
• Occasionally axes import as curves.
6 Patran Release Guide
Supported Analysis Preferences

Supported Analysis Preferences

Solver Platforms Solver Version
MSC Nastran*† All 2019.0
Marc All 2019.0
Dytran All 2018
Flightloads‡ All 2019
Thermal All 2019
Fatigue All 2019
MSC Sinda All 2017.1
LS-DYNA3D All 971
PAMCRASH All 1995 / 1997
Abaqus(.odb) All 6.14
ANSYS** All 16.2

* MSC Nastran has discontinued support of i4 databases. All output results produced by MSC
Nastran 2017 or later are only available as i8 databases (DBALL/MASTER). Support for
result access via DBALL/MASTER file has been discontinued. Result access through
Output2 (PARAM,POST,1), XDB, and HDF5 should be used as an alternative with HDF5
as the standard default.
†MSC Nastran 2017 and higher does not convert INTEGER input to REAL if entered as an
integer in a real input field. Instead, a fatal message is issued. To bypass this, specify system
cell NASTRAN SYSTEM(444)=9 as first line in the FMS section. It is recommended that
users import input files that run through MSC Nastran with no fatal errors. When importing
files with this system cell, no fatal messages are issued due to integer to real conversion. In
general, when importing detects a FATAL error message, Patran issues this message:
Problem detected while importing the MSC.Nastran input file using
SOL nifimp_v22
‡AlocalFldsNastranCommand and MSCP_LOCAL_FLDS_NASTRAN_CMD environment
variables for setting the path for MSC.Flightloads executables on Windows and Linux
respectively, are invalid from Patran 2017 release. Although the variables still appear in
P3_TRANS.INI file, changing their value will not affect the default path.
**Results access is enhanced to ANSYS 16.2 (results import is frozen at ANSYS 8.1).
 Chapter 1: Patran 2019 at a Glance 7
Technical Support

Technical Support
For technical support phone numbers and contact information, please visit:
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

Support Center (http://simcompanion.mscsoftware.com)

The Support Center provides technical articles, frequently asked questions and documentation in a single
location.

Online Resources (www.mscsoftware.com)

MSC Software corporate site with information on the latest events, products and services for the
CAD/CAE/CAM marketplace.
 Chapter 2: General Enhancements. MSC Nastran Implicit Nonlinear (SOL 600) User’s GuidePatran
Release Guide

2 General Enhancements


Insight Ported to QT 9
 Enhanced HDF5 Results Support 10

Maximum/Minimum Load Case Tracking 11

SuperGroup Support 16
 Contact Model Checking 18

Enhanced Group Mirror Support 21

Crash Reporting System 24
 Nastran File Import and Results Format Support 25
 Write Stored Precision (Nastran BDF Files) 26
 Chapter 2: General Enhancements 9
Insight Ported to QT

Insight Ported to QT
In Patran 2017, a new graphical user interface (GUI) was introduced based on the cross-platform
development framework called QT, thus providing Patran with the same look-and-feel on both Windows and
Linux machines. Unfortunately at that time, not all Patran functionality was made available, specifically the
results postprocessing application called Insight. This release now features a fully functional Insight
application under the QT framework.
Insight is accessed from the Results tab in “Skin” mode by clicking on the Insight icon:

Or in “Classic” mode by clicking on the Insight icon on the top level application switch:

Shown below is an Insight contour plot of plastic strains on a crushed pipe specimen:
10 Patran Release Guide
Enhanced HDF5 Results Support

Enhanced HDF5 Results Support

A number of new results are available from the HDF5 database file that can be requested from an MSC
Nastran run. Additional results that can now be accessed from Patran include:
 Nodal Nonlinear Force
 End Load Results for elements CBAR, CBEAM, CQUAD4, CQUAD8, CQUADR, CROD,
CSHEAR, CTRIAR, CTRIA3, and CTRIA6
 Failure Index and Strength Ratio for composite elements CQUAD4, CQUAD8, CTRIA3, and
CTRIA6
 Nonlinear Stresses for CQUAD4, CQUADR, CTRIA3, and CTRIAR
 And, the Contact results listed in the following table:

Primary Secondary Patran Output

Name Name Result Type Association Request Nastran Output Request
Contact Check Distance Scalar Nodes Check Contact
Model
Contact Check Translational Vector Nodes Check Contact
Model BCONCHK=RUN/STOP*
Contact Translational Vector Nodes Check Contact
Adjustment Model & Enable
Initial Contact

*Contact Adjustment is only available for postprocessing when ICOORD=1 on BCONPRG

(geometric contact property) bulk data entry for the respective contact body pairs.
 Chapter 2: General Enhancements 11
Maximum/Minimum Load Case Tracking

Maximum/Minimum Load Case Tracking

Enhancements to the Results application for extraction of Maximums and Minimums (MaxMin) across
results cases/layers have been implemented in this release to make the results more meaningful. In addition
to simply extracting MaxMin results, the actual Maximums or Minimums of the derived comparison value
are retained and load case tracking results are retained to indicate to the user from which load case (result
case) the MaxMins occur. For complete details, please see Derived Results (p. 227) in Results Postprocessing.
The functionality is accessed from the Results application with the Action/Object/Method set to
Create/Results/Maximum (or Minimum).

The process for this operation is as follows:

1. The user selects the result cases and/or the layers across which the MaxMin results should be
extracted.
2. A new result case and subcase name are given if requested, otherwise the default presented to the user
is used.
3. A single result is selected such as Displacements, Translational, or Stress Tensor. The MaxMin
extraction is done on this selected result type.
12 Patran Release Guide
Maximum/Minimum Load Case Tracking

4. Layers are selected if the MaxMin extraction should also be considered across multiple result layers
such as top and bottom of shell elements or composite layers.
5. A comparison Quantity is selected. This is only necessary if the selected result is a vector or tensor.
Vector and tensor results need to be reduced down to a single scalar quantity for MaxMin comparison
purposes. Only a scalar quantity can be compared for the MaxMin extraction operation.
6. Any other operations for the MaxMin extraction are set on the Plot Options mode of this form, which
may include coordinate transformations, averaging and extrapolation methods, algebraic vs. absolute
comparisons.
7. The Apply button is pressed.
The following results are created in the new Result case that now contains the MaxMin results:
 The Extracted MaxMin Result: the main result that is computed takes on the same name as the
originally selected result with the same primary and secondary names. (Note: if results are complex
an “*” is appended to the secondary name). For example if Displacements, Translational is the result
from which to perform the MaxMin extraction, the new MaxMin result case also contains
Displacements, Translational. This result contains the actual Maximum (or Minimum) as extracted
from all the originally selected result cases. It does NOT contain the actual derived value that was
used as the comparison value for the MaxMin extraction. If the original result selected contains
vectors at nodes, then the new result continues to contain vectors at nodes. Scalars remain scalars,
vectors remain vectors, and tensors remain tensors. If the originally selected results was nodal,
elemental, or element nodal, the new result remain nodal, elemental, or element nodal also. The new
result only contains that scalar, vector, or tensor that was extracted from the MaxMin result case
based on the comparison quantity derived. Also, this result is always NON-LAYERED (only one
layer) since each layer of the originally selected results was treated as a separate result case in the
MaxMin result. So the MaxMin extraction when multiple layers are selected always give the
MaxMin from the layers as well as the result cases. Also it is imperative to understand that creating
plots using this MaxMin extracted result should always use the same Quantity derivation, averaging
domain/method, extrapolation, and coordinate transformation that was used to extract these results.
Otherwise the plots may be meaningless or, at best, confusing!
 The Derived MaxMin Result: if requested, the actual derived quantity is also saved. This result
contains the actual MaxMin values of the derived quantity used for the MaxMin comparison. So for
example, if tensor result cases were selected, and the comparison quantity was von Mises, then this
result would contain scalar MaxMin von Mises values as derived from the original results. For nodal
and element centroidal results, if you plot these results you get exactly the same results as if you
plotted the MaxMin Extraction result above, provided you plot the result using the same Quantity
derivation. For element nodal results, a plot of the derived result versus the original results (using the
same Quantity derivation) will differ due to the averaging domain/extrapolation. As the model
fidelity becomes better and better, these differences converge to the same plot. Examples are given
below. Also this result is optional. The toggle on the Plot Options form for Save Derived Results
must be turned ON.
 The Load Case Indicator Results: A load case and result case in the context of MaxMin extraction
mean the same thing. To know which result case the MaxMin occurs at any given location (node,
element) on the model, one only needs to display these results. Multiple load case indicator results
occur based on the nature of the originally selected result cases and layers. At a minimum, a result
 Chapter 2: General Enhancements 13
Maximum/Minimum Load Case Tracking

indicating the result case index is created to understand from which load/results case the MaxMin
occurs. If multiple layers are selected for the MaxMin extraction, a result case indicating which layer
contains the MaxMin is also created. And a new result is created for each global variable associated
with the originally selected result cases. For instance, if a modal analysis is considered, a global
variable for the mode number and another for the frequency are associated with each originally
selected result case. Plotting these results then indicates which mode and/or at which frequency the
MaxMin occurs. Other global variables that may be available depending on the analysis type are
time steps, load steps, eigenvalues, among others.
The Primary name of these new load/result case indicator results takes on the comparison criteria and the
Secondary name takes on the global variable name or the layer/result case index. For example, if the extraction
criteria were Maximum, algebraic comparison, and von Mises (of a tensor), then the Primary name is:
MaxAlgVONM. And, if an available global variable is Frequency and the results are from shell element layers,
the resulting new load/result case indicator results are shown here plus the derived and extracted result:

The following is an example of MaxMin extraction of nodal results. Note that the fringe plot of the extracted
results (Magnitude in this case) is exactly the same as the fringe plot of the derived results, which one would
expect since the results exist purely at the nodes. The third plot below shows a marker plot indicating the
result cases from which the MaxMin occurs at each node of the model. Marker or Cursor plots are the most
appropriate plot forms to use to visualize or extract this information. Result case seven (7) appears to be the
result case where most of the Maximums occurs across the model for this particular analysis.
14 Patran Release Guide
Maximum/Minimum Load Case Tracking

For elemental results where results exist only at the element centers, one would also expect results similar to
nodal results where the extracted and derive result plots are identical as only one result per element exists.
However for elemental results where multiple results exist per element (typically called element nodal results),
the extracted results plot and the derived results plot can differ due to nodal averaging. It is important to
understand this so as to avoid confusion and misunderstanding of what these plots mean.
The extracted result plot contains the extracted results based on the comparison quantity and criteria. But the
extracted results are the original results (scalar, vector, tensor) from the result case at which the Maximum or
Minimum occurs. The extracted results are NOT the actual comparison quantities. The derived results ARE
the actual comparison quantities. So when plotting the extracted results, nodal averaging still occurs, which
has the tendency to show something less than or more than the actual MaxMin at any particular node
location. For this reason MaxMin extraction of element nodal results should be done with None set as the
Averaging Domain.
 Chapter 2: General Enhancements 15
Maximum/Minimum Load Case Tracking

So in the plots above, only nodes with no surrounding element contributions compare directly to the derived
results plot. Note that the actual maximum is the same on the range but the range itself is slightly different.
The derived plot is the true MaxMin plot as the true maximum at each node has been retained due to all
element contributions. The bottom marker plot then shows from which result case the actual MaxMin
occurs.
16 Patran Release Guide
SuperGroup Support

SuperGroup Support
Patran has a simple ability to create a group of groups. A group of groups is called a SuperGroup.
SuperGroups are typically used simply for the ease of posting and unposting a number of groups in a single
operation rather than selecting all the groups of interest. SuperGroup creation and manipulation is accessible
from the Groups pull down menu off of the main Patran menu bar.

SuperGroups can also contain other SuperGroups (nested).

 Chapter 2: General Enhancements 17
SuperGroup Support

In addition to the creation, modification, posting, and unposting of these SuperGroups, for the MSC Nastran
analysis preference, the analysis can be performed over the entire model, on a selected group, or now, a
selected SuperGroup. A switch on the form allows the user to select Groups or SuperGroups. If
SuperGroup(s) is selected, the Group mode of the form shows which groups of the selected SuperGroups are
actually selected. If the Groups mode is used and the selected groups make up a defined SuperGroup, then
the SuperGroup(s) mode of the form shows that or those SuperGroups as selected also.

Analysis is then done on only the finite elements defined by the selected Groups or SuperGroups.
18 Patran Release Guide
Contact Model Checking

Contact Model Checking

New contact model checking features have been added to MSC Nastran recently and Patran now supports
the majority of these features. To access these model checking features one simply needs to turn ON the Check
Contact Model toggle for any of the standard solution sequences 101-200, and 400 under the Contact
Controls form in the Analysis application for SOLs 101 and 400 or the Solution Parameters form for other
solutions (Optimization Parameters form for SOL 200).

When the toggle is ON, Patran writes the following Case Control to the MSC Nastran input deck depending
on whether the analysis is set to Full Run, Analysis Deck, or Check Run: BCONCHK = RUN/STOP

BCONCHK = RUN BCONCHK = STOP

 Chapter 2: General Enhancements 19
Contact Model Checking

For Full Run, the MSC Nastran job does the contact model check and then continues on to run the full
contact analysis. For Check Run, the MSC Nastran job stops after the contact model check has completed
allowing the user to then view the contact model check results before deciding to run the full analysis. If set
to Analysis Deck, BCONCHK=RUN is written but no analysis is submitted. Only the input deck is created.
The contact model checking automatically produces an HDF5 result output file. There is no need for the
user to request an HDF5 file. The contact model checking produces that following additional contact output
that is available for postprocessing. See also the section on Enhanced HDF5 Results Support, 10 earlier.

Contact Check, Distance

This is the shortest (scalar) distance between the nodes of contact body pairs that come into contact within
a defined distance checking tolerance. Any nodes outside of the distance tolerance are not checked and
therefore have no distance data to plot. So only the portions of the model for each contact pair within this
tolerance have data. This is a signed scalar value associated to nodes. A negative values indicates penetration
of the contact body pair at that node. Zero implies the bodies are just touching on their surface at that node.
And naturally, a positive value indicates a gap. Shown below is a fringe plot.

Contact Check, Translational

This is the shortest (vector) distance between the nodes of contact body pairs that come into contact within
a defined distance checking tolerance. This result is X, Y, and Z components in the global coordinate system
of the previously discussed result: Contact Check, Distance. It is possible to plot the magnitude of these
components to obtain the same result as the Contact Check, Distance. However what the previous result
indicates that this one does not, is the penetration or gap status as the magnitude of this result is always
positive.
20 Patran Release Guide
Contact Model Checking

Contact Adjustment, Translational

If contact body pairs have the initial stress free adjustment set (ICOORD=1 on the BCONPRP entry), then
the actual relative displacements necessary for all slave nodes are output in order to achieve a stress free initial
contact condition. The relative displacements of all nodes of the affected contact body pairs are output and
can be plotted as deformation or fringe plots or any other plot types that make sense.
 Chapter 2: General Enhancements 21
Enhanced Group Mirror Support

Enhanced Group Mirror Support

In the last release, the capability to mirror group entities was significantly enhanced. This release completes
this functionality for the mirroring of Element and Material Properties and Loads and Boundary Conditions
(LBCs) defined by PCL fields. The functionality is accessible through the Group/Transform menu.

Figure 2-1 The Group/Transform Menu - with Mirror Highlighted

When this capability is exercised against selected groups, all the entities of those groups are mirrored across a
mirror plane, creating a mirror image of the group, including all LBCs, material directions, composite ply
angles, and LBCs. The mirror transformation of properties and LBCs in the previous release works fine in all
cases except when the property or LBC is defined by a PCL function due to the difficulty of mirroring the
PCL function itself.
What is done now for LBCs (and Element/Material Properties) that are define with a PCL function is that
the PCL function is evaluated at the original locations of the selected group(s). A new discrete FEM field is
then created with the elements or nodes of the mirrored group. The corresponding mirrored elements or
nodes are then assigned the evaluated PCL values from their original locations. If the PCL function is a scalar,
the scalar evaluation is used straightway. If the PCL function is a vector, the resulting evaluated vector is
mirrored to the new element or nodal locations. Thus a true mirror of the property or LBC is maintained.
For example, here is a property (thickness) that is defined by a PCL function as the summation of the physical
X and Y location of each node. If the PCL function is not mirrored, then the mirror of the thickness is
incorrect if the original PCL function is used to define the thickness in the mirrored elements/nodes. Only
22 Patran Release Guide
Enhanced Group Mirror Support

evaluating the function at the original locations and assigning those values to the mirrored elements via a
discrete FEM field allows for a true mirror of the thickness properties onto the mirrored elements.
Here is a plot of the nodal thicknesses from the property set plate and the mirrored property set plate.3. Note
the symmetric plot indicating the thicknesses were mirrored correctly.

Property set plate defines its thickness with PCL function pcl. The function is defined as ‘X+‘Y coordinate
locations.

The mirrored group is defined with mirrored property set plate.3 and the thickness property references
discrete FEM field pcl.n.3, which was derived from the original PCL function, pcl, evaluated at the original
 Chapter 2: General Enhancements 23
Enhanced Group Mirror Support

node locations and mapped to the newly mirrored node locations, thus maintaining a true mirror of the
thicknesses on the mirrored group.
24 Patran Release Guide
Crash Reporting System

Crash Reporting System

A new crash reporting system is introduced in this version, which is meant to help MSC Software make the
Patran application as robust as possible.
The crash reporting system is supported on both Windows and Linux platforms. When Patran crashes, it
shows the following message and records the information about abnormal termination in diagnostic files.
Diagnostic files are not created if Patran becomes unresponsive due to resource shortages, secondary
application crashes, and in certain un-handled circumstances such as large memory issues or security
problems.
To report such defects, users are requested to describe the scenarios and steps to reproduce the crash in a
separate document and send with the generated diagnostic (.dmp) file to the MSC Technical Support Team.
This information is critical for MSC to identify the root cause and fix the application as appropriate.

Windows:

Linux:
On Linux platforms, crash related messages are recorded in the console output terminal with a similar
message:
"Warning: Patran has stopped working and exported diagnostic information to current directory
(.dmp file). Please include this file when reporting this issue to MSC Technical Support at:
http://www.mscsoftware.com/support/contacts
Note: This file contains no details of your model, only details regarding what Patran was doing
when it stopped working.
 Chapter 2: General Enhancements 25
Nastran File Import and Results Format Support

Nastran File Import and Results Format Support

Nastran input files, including Aeroelastic input files for Flightloads, are now imported using the i8 Nastran
Toolkit.
Support for result access via DBALL/MASTER file has been discontinued. Result access through Output2
(PARAM,POST,1), XDB, and HDF5 should be used as an alternative with HDF5 as the standard default.
Model data import continues to be supported directly by reading the input file itself.

Note: Using i8 Nastran Toolkit for importing data might increase RAM usage.

The following table lists supported results in i4 and i8 modes:

Results Model Data Both

i4 i8 i4 i8 i4 i8
HDF5 NO YES NO YES NO NO
XDB YES YES YES YES YES YES
OLD OP2
(PARAM,POST,-1) YES NO YES NO YES NO

Master/DBALL Support discontinued

NEW OP2
(PARAM,POST,1) YES YES NO NO NO NO
26 Patran Release Guide
Write Stored Precision (Nastran BDF Files)

Write Stored Precision (Nastran BDF Files)

The following toggle has been placed (or restored) on the Translation Parameters form in the Analysis
application for the MSC Nastran Preference. If this toggle is ON, then on creation of a Nastran bulk data file
(BDF), the translator attempts to write the precision as stored in memory based on the Precision Control
settings. In other words or as an example, if a grid point’s coordinate values are requested to a precision of 10
digits to the right of the decimal point, then 10 precision digits are written as long as:
1. The Precision Digits for Grids is set to 10
2. The internal storage of the number is double precision (some numbers such as material and element
properties are stored in single precision). Grid locations and coordinates system are stored as double.
3. The Card Format is set to either or large. Small field card format does not allow for more than eight
(8) characters, thus only six (6) precision digits are allowed at a maximum.
4. There actually are 10 digits of precision for the numbers being written.

If the toggle is OFF, then all internal numbers are treated as floats (single precision) and a maximum of six
(6) digits of precision is used even if the Card Format is set to large. Precision digit settings above six (6) are
ignored in this case. It is not recommended to turn this toggle OFF unless there is a good reason to do so.
 MSC.Fatigue Quick Start Guide

Index
Patran Release Guide

A K
Abaqus, 6 key highlights, 2
ACIS, 4
Index analysis, 16 L
ANSYS, 6 limitations, 4
LS- DYNA3D, 6
C
CAD Access, 4 M
CATIA, 4 Marc, 6
contact, 18 MASTER, 6
Maximums/Minimums, 11
D mirror, 21
DBALL, 6 model checking, 18
Dytran, 6 MSC Fatigue, 6

E N
enhancements, 2 Nastran, 6

F O
fatigue, 6 Operating systems, supported, 3
Flightloads, 6 Output2, 6

G P
Grid Point Force (GPFORCE), 9 PAMCRASH, 6
Group Mirror, 21 Parasolid, 4
groups, 16 precision, 26
Pro/ENGINEER, 4
H
Hardware, 3 R
HDF5, 6 results, 9, 10, 25
HDF5 Support, 10
highlights, 2 S
Sinda, 6
I Solid Works, 4
IGES, 4 STEP, 4
SuperGroups, 16
Supported OS levels/Hardware Platforms, 3
28 Patran Release Guide

T
Thermal, 6

U
Unigraphics, 4

X
XDB, 6