+ All Categories
Home > Documents > MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001...

MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001...

Date post: 17-Apr-2018
Category:
Upload: hoangdang
View: 229 times
Download: 0 times
Share this document with a friend
72
MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes
Transcript
Page 1: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

M S C . M a r c 2 0 0 1 a n d M S C . M a r c M e n t a t 2 0 0 1

Version 2001

Release Notes

Page 2: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Corporate MSC.Software Corporation2 MacArthur PlaceSanta Ana, CA 92707Telephone: (714) 540-8900FAX: (714) 784-4056

EuropeMSC.Software GmbhAm Moosfeld 1381829 München, GERMANYTelephone: (49) (89) 431 9870Fax: (49) (89) 436 1716

Asia PacificMSC.Software CorporationEntsuji-Gadelius Building2-39, Akasaka 5-chomeMinato-ku, Tokyo 107-0052, JAPANTelephone: (81) (03) 3505-0266Fax: (81) (03) 3505-0914

Worldwide Webwww.mscsoftware.com

DISCLAIMER

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 2001 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.

This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this document, in whole or in part, without the prior written consent of MSC.Software Corporation is prohibited.

MSC and MSC. are registered trademarks and service marks of MSC.Software Corporation. NASTRAN is a registered trademark of the National Aeronautics and Space Administration. MSC.NASTRAN is an enhanced proprietary version developed and maintained by MSC.Software Corporation. MSC.PATRAN is a registered trademark of MSC.Software Corporation.

MSC.Nastran for Windows includes a licensed version of FEMAP from Enterprise Software Products, Inc. a subsidiary of Structural Dynamics Research Corporation. Portions of FEMAP and related documentation are derived from GHS3D software under license from INRIA, other portions are copyrighted by and are the property of Electronic Data Systems Corporation, and Spatial Technology Inc. Windows is a trademark of Microsoft Corporation. DXF is a trademark of Autodesk, Inc. Parasolid is a trademark of Electronic Data Systems Corporation. All other products are identified by the trademarks of their respective companies or organizations

MA*2001*Z*Z*Z*DC-REL

Page 3: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

C O N T E N T SMSC.Marc 2001 and MSC.Marc Mentat 2001 Release Notes

Contents ■ List of the New Functionalities, 2

■ Description of the New Functionalities, 3

■ References to Examples of the New Functionalities, 40

■ List of Defects Fixed in Release, 41

■ List of Known Problems in Release, 49

■ List of Build and Supported Platforms for Release, 55

■ List of Dropped Platforms, 58

■ Important Notes, 59

■ Platform Specific Notes, 63

■ Security, 66

Page 4: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix
Page 5: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

MSC.Nastran for Windows Release Guide

The release of MSC.Marc 2001 family of products broadly encompasses the following objectives:

• Major new enhancements in several areas in both solver and GUI capabilities

• Substantial improvements in quality – several defects in the previous versions have been fixed

• Notable increase in robustness of analysis

• Notable solver speed improvements

MSC.Marc 2001 and MSC. Marc Mentat 2001 Release Notes

■ List of the New Functionalities

■ Description of the New Functionalities

■ References to Examples of the New Functionalities

■ List of Defects Fixed in Release

■ List of Known Problems in Release

■ List of Build and Supported Platforms for Release

■ List of Dropped Platforms

■ Important Notes

■ Platform Specific Notes

■ Security

Page 6: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of the New FunctionalitiesMSC.Marc 2001

2

I. List of the New Functionalities

There are significant new enhancements in various key technology areas besides improvements in existing functionality in the MSC.Marc 2001 family of products. The extent of improvements is fairly substantial and spans a broad range of industries. A list of new features for both the solver and graphical user interface is given below. Details can be found in the next section for the enhancements and modifications in both the MSC.Marc and MSC.Marc Mentat 2001 versions.

MSC.Marc 2001

1. Analysis Speed and Memory Improvements

2. AXITO3D: Data Transfer from Axisymmetric to 3-D Analysis

3. Contact Enhancements

4. Cyclic Symmetry

5. Improvements in Element Technology

6. Gasket Material and Pre-Tension Bolts

7. Mesh Adaptivity

8. Miscellaneous Enhancements

9. Parallel Enhancements

10. Postprocessing Enhancements

11. Robustness of Automatic Load Stepping Schemes

MSC.Marc Mentat 2001

12. Mentat Menu Enhancements

13. Mentat Preprocessing Enhancements

14. Mentat Postprocessing Enhancements

Page 7: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

3Description of the New FunctionalitiesAnalysis Speed and Memory Improvements

II. Description of the New Functionalities

1. Analysis Speed and Memory Improvements

Several improvements have been made to improve the speed of the analysis for both linear as well as nonlinear problems. The most notable ones are:

A. Contact Analysis

Improvements in contact analysis have been obtained by: (1) Improved bounding box algorithm, (2) memory reduction and (3) automatic determination of the number of subdivision for NURBS surfaces. Please refer to Contact Enhancements: B. Memory Reduction and C. Automatic determination of the number of subdivisions for NURBS surfaces for details.

The speed and memory improvements based upon relative performance of the same problem in the 2000 and 2001 versions of Marc are shown in Tables 1 through 3.

Table 1 Job Statistics for Case 1 Rigid Contact

Version Memory [Mw]CPU Times

[sec]

2000 14.6 3145

2001 2.13 1778

Ratio 6.85 1.77

Table 2 Job Statistics for Case 2 Deformable Contact

Version Memory [Mw]CPU Times

[sec]

2000 56.2 4232

2001 57.0 2678

Ratio 0.99 1.58

Table 3 Job Statistics for Solver Improvements

Version Memory [Mw]CPU Times

[sec]

2000 107.86 1024.26

2001 71.3 629.06

Ratio 1.51 1.62

Page 8: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesAnalysis Speed and Memory Improvements

4

B. New Multifrontal Sparse Solver

The 2001 release contains a new sparse direct solver based on a multi-frontal scheme. The solver is tuned for optimal performance on Sun/SunOS, SGI/IRIX, IBM/AIX, Compaq OSF, HP/HP-UX, Linux, and on Intel/NT machines.

For single-processor execution, the solver is available for the following types of matrices:

(1) Symmetrical and nonsymmetrical real matrices. An out-of-core capability is available for both the symmetrical as well as for the nonsymmetrical case.

(2) Symmetrical and nonsymmetrical complex matrices. An out-of-core capability is available for both the symmetrical as well as for the nonsymmetrical case.

For parallel processing, the solver can be used with symmetrical real matrices including out-of-core.

In- and out-of-core execution are controlled primarily by the amount of memory available on the machine to which the job is submitted. It also can be controlled directly by the user by explicitly setting parameters as outlined below. Sufficient disk space and a minimum amount of memory must be available if the solver goes out-of-core.

The amount of memory used by the solver can be controlled by setting operating system limits for individual memory usage by a user, in the tools/include file the MAXSIZE option, and through the input data file the OOC option, the SOLVER option, and/or the CONTROL option. Specifically, the solver automatically goes out-of-core if:

(1) A memory limit set by the operating system is exceeded.(2) The total amount of memory required by the model, including the matrix

solution aspect, exceeds the value of MAXSIZE in the tools/include file. MAXSIZE is specified in millions of 4-Byte words on all systems except on some CRAY platforms.

(3) The OOC parameter in the input data file can be used to force the out-of-core solution. This option will make the solver to go out-of-core using the minimum possible amount of memory required by the solver, regardless of which other options are specified.

(4) The solver memory limit under the SOLVER option is reached. This limit, which applies only to the matrix solution aspect of the job, is specified in MBytes.

Since the solver needs a minimum amount of memory to run out-of-core, the job will terminate if this is not available. Memory requirements, both minimum as well total amounts, are printed to the output file associated with the job.

Page 9: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

5Description of the New FunctionalitiesAnalysis Speed and Memory Improvements

The solver is available for eigenvalue extraction of symmetrical real matrices by using the Lanczos procedure, and of symmetrical as well as nonsymmetrical real matrices by using the inverse iteration method.

Finally, the 2001 release, as before, automatically determines the type of matrix such as real or complex, or symmetrical or nonsymmetrical.

Figure 1: Solver Submenu

Page 10: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesAXITO3D: Data Transfer from Axisymmetric to 3-D Analysis

6

2. AXITO3D: Data Transfer from Axisymmetric to 3-D Analysis

This feature involves axisymmetric model generation with results transfer for fully three-dimensional analysis. In many cases, the component has an initially axisymmetric geometry and is initially axisymmetrically loaded, and hence is truly axisymmetric. The second stage of the problem can involve asymmetric loading and hence be fully three-dimensional (Figure 2). Large savings in computational cost can be expected. This feature can be used with lower- and higher-order displacement and Herrmann elements in static, dynamic, and heat transfer analysis. This feature can be used with both rubber elasticity and metal plasticity.

Figure 2: Data Transfer from Axisymmetric to 3-D Analysis

The feature AXITO3D has been further improved for ease-of-use and has expanded functionality in the MSC.Marc2001 release. The enhancements contain non-equispaced mesh expansion and data transfer from axisymmetric to 3-D case, data transfer for rebar elements, as well as simplification of model preparation for 3-D jobs with MSC.Marc Mentat. In Marc 2001, the loads and boundary conditions can be expanded from the originally defined axisymmetric model file to generate the 3-D model (exception being when the axisymmetric model involves remeshing). The state variables (displacements, temperatures, etc.) and stresses/strains etc. are read from the post file.

Step 1: Axisymmetric

Step 2: Model Expansion to 3-D

Step 3: 3-D Analysis with Contact

Analysis

Page 11: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

7Description of the New FunctionalitiesAXITO3D: Data Transfer from Axisymmetric to 3-D Analysis

Figure 3: Axisymmetric to 3D Menus

Refer to MSC.Marc Volume C: Program Input for details on which elements may be used for AXITO3D analysis.

Expand Menu Axisymmetric Model To 3D Expand

Page 12: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesContact Enhancements

8

3. Contact Enhancements

A. Improvements in Iterative Penetration Checking Procedure

The automatic penetration checking procedure is available by selecting PER ITERATION in Mentat menu (Figure 4) or by setting the 7th field of the second line of CONTACT option to 3 in the input file. It is automatically activated if the adaptive loading procedure is selected. It currently is not available for dynamics and the arc length control procedure (AUTO INCREMENT). If the automatic penetration checking procedure is selected for these two options, a different procedure will be used instead, as described in MSC.Marc Volume A: Theory and User Information.

When using this procedure, it is important to ensure that the maximum allowable number of iterations to complete an increment is set to a sufficiently large value.

Figure 4: Iterative Penetration Checking Menu

B. Memory Reduction

This has mainly been obtained by:

(1) Dynamic memory allocation per contact body. In previous MSC.Marc versions, the amount of memory needed per contact body was the same for all bodies and thus dictated by the largest contact body. This implies that adding one small contact body could result in the allocation of a significant amount of memory. In the current version, the amount of memory needed for a contact

Page 13: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

9Description of the New FunctionalitiesContact Enhancements

body depends on the size of the body itself and not on the size of the other bodies. As a result, adding e.g. a simple symmetry plane needs only a limited amount of additional memory.

(2) For deformable contact problems, which are solved using multipoint constraints, only nodes in contact cause memory allocation for those multipoint constraints. This dynamic memory allocation is in contrast with the static allocation in previous versions, which normally over-estimated the amount of memory needed for this purpose.

C. Automatic determination of the number of subdivisions for NURBS surfaces

In previous MSC.Marc versions, the number of subdivisions for analytical rigid bodies was fixed, and especially for complex NURBS surfaces the number of subdivisions written by Mentat could be very high. A high number of subdivisions not only influences the amount of memory needed, but also decreases the speed of the contact analysis due to costly searching operations. In the current version, the optimal number of subdivisions is determined automatically based on a target angle between the NURBS segments.

D. Nonsymmetric CONTACT TABLE

The CONTACT TABLE option has been modified to accommodate nonsymmetric behavior (Figure 5). This significantly improves the contact behavior in a number of scenarios.

Within MSC.Marc, the general procedure for contact detection depends on the numbering of the contact bodies: starting with the first deformable body and ending with the last. Especially when there are many contact bodies present, this dependency on the body numbering could make it a complicated task to come up with the optimal body numbering (normally the numbering resulting in a maximum number of multipoint constraints due to contact). In the current version, the CONTACT TABLE option has been extended to make this easier. Now one can indicate that contact detection should, e.g., be done from deformable body 4 with respect to deformable body 2, where in previous MSC.Marc versions always detection from body 2 with respect to body 4 was done first. The rule that, in general, it is better that a body with a dense element mesh should touch a body with a coarse element mesh has also been automated: using a CONTACT TABLE, the order in which contact will be searched for can be a function of the element edge length at the boundaries of the contact bodies.

Page 14: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesContact Enhancements

10

Figure 5: Contact Table Menus

E. Stress-free Initial Contact

Upon initial contact (increment 0), coordinates of nodes in contact can be adapted, such that they cause stress-free initial contact. This might be important if, due to inaccuracies during mesh generation, there is a small gap/overlap between the node and the contacted element edge/face. If such a gap would be removed by displacement changes, undesired stresses might be introduced. This option is also activated using CONTACT TABLE shown in Figure 5.

F. Delayed Slide Off

By default, at sharp corners, a node will slide off a contacted segment as soon as it passes the corner by a distance greater than the contact error tolerance. For certain applications, extending this tangential tolerance might be advantageous, and this capability is also available now via a CONTACT TABLE as shown in Figure 5.

G. Improved Bounding Box Algorithm

The contact search part of the contact algorithm has been enhanced to make more use of bounding boxes. This has lead to an increased speed of all contact analysis, in particular for large three-dimensional problems.

Page 15: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

11Description of the New FunctionalitiesContact Enhancements

H. Enhancements in Glue Contact

The Contact Glue option now truly glues the nodes by default. Previously, you would have to specify a high separation force in addition to flagging glued contact in the contact table. In order to obtain the case of no tangential sliding but allowed separation (infinite friction), two possibilities exist:

(1) invoke standard separation behavior via the CONTACT TABLE (10th entry of third data block), so that a node separates if the tensile contact force exceeds the maximum residual force component;

(2) specify a small enough separation force, either via the CONTACT option or the CONTACT TABLE option.

Page 16: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesCyclic Symmetry

12

4. Cyclic Symmetry

A special set of tying constraints for continuum elements can be automatically generated by the Marc program to effectively analyze structures with a geometry and a loading varying periodically about a symmetry axis. Figure 6 shows an example where in Figure 6(a), the complete structure is given and in Figures 6(b) and (c), a sector to be modeled by taking advantage of the cyclic symmetry of the structure which give results equivalent to the full model. This feature can result in substantial savings of computer time.

Figure 6: Stress Contours for Friction Clutch Models

(a) Full Model

(b) Model 1:Quarter Model

(c) Model 2:Quarter Model

Page 17: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

13Description of the New FunctionalitiesCyclic Symmetry

In Marc, the input for the CYCLIC SYMMETRY option consists of the direction vector of the symmetry axis, a point on the symmetry axis and the sector angle . The following items should be noted:

1. The meshes do not need to line up on both sides of a sector (for example, see Figure 7).

Figure 7: Finite Element Mesh for Cyclic Symmetric Structure with Different Mesh Densities on the Sector Sides

2. Any shape of the sector sides is allowed, provided that rotating the sector times about the symmetry axis over the sector angle will result in the complete model.

3. The CYCLIC SYMMETRY option can be combined with the CONTACT option.

4. The CYCLIC SYMMETRY option can be combined with global remeshing.

5. In a coupled thermo-mechanical analysis, the temperature is forced to be cyclic symmetric. A nodal point on the symmetry axis is automatically constrained in the plane perpendicular to the symmetry axis.

6. A nodal point on the symmetry axis is automatically constrained in the plane perpendicular to the symmetry axis.

7. The possible rigid body motion about the symmetry axis can be automatically suppressed.

8. Cyclic Symmetry is:

a. valid only for the continuum elements. However, the presence of beams and shells is allowed, but there is no connection of shells to shells, so the shell part can, for example, be a turbine blade and the volume part can be a turbine rotor. The blade is connected to the rotor and if there are 20 blades, 1/20 of the rotor is modeled and one complete blade.

b. valid for all analyses involving contact.

c. valid for nonlinear static analysis including remeshing as well as coupled analysis.

d. invalid for pure heat transfer.

α

360 α⁄α

Page 18: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesCyclic Symmetry

14

e. valid also for: eigenvalue analysis such as buckling or modal analysis; harmonic analysis; and transient dynamic analysis. However, there are restrictions in the case of modal analysis which are described in more detail in the section on Cyclic Symmetry in Chapter 9 of Volume A.

Page 19: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

15Description of the New FunctionalitiesImprovements in Element Technology

5. Improvements in Element Technology

A. Low-order Triangular and Tetrahedral Elements for Incompressible Materials

Description

Low-order triangular and tetrahedral elements have been developed (elements 155, 156, and 157), which can be used for incompressible as well as nearly incompressible materials, e.g. elastomers (Figure 8) and metal plasticity. The motivation was to derive the benefits of the triangular and tetrahedral meshers.

In the current release, the degrees-of-freedom of the center node have been condensed out at the element level before the assembly of the global matrix. This can reduce the cost of computing considerably for large scale problems using these elements.

Besides the computational speed, these elements have the ability to output results at the centroid, which results in a considerably smaller post file, without losing too much significant information.

Figure 8: New Rubber Elements and Material Models

Although these elements accommodate both compressible as well as incompressible deformation, due to higher order of numerical integration and more degrees-of-freedom per node, they are still computationally more expensive than their linear displacement counterparts and should generally be used for analysis with incompressible materials.

Page 20: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesImprovements in Element Technology

16

B. Composite Heat Transfer Shell Elements

The temperature profile in thickness direction of heat transfer shell elements can now be linear or quadratic per layer, where in previous MSC.Marc versions this could only be linear or quadratic through the whole thickness. This implies that now complicated temperature distributions in thickness direction can be described accurately, which might be important for composite shell structures.

C. Rebar Element Enhancement

The enhancement allows the use of rebar elements with both total and updated Lagrangian formulations and with the enhanced AXITO3D feature. The input deck changes allow much more general definition of rebar properties through input files. Pre- and postprocessing of the elements are also improved, since rebar layers can be visualized and global layer identifiers can be specified.

Figure 9: Rebar Element Menu

Page 21: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

17Description of the New FunctionalitiesGasket Material and Pre-Tension Bolts

6. Gasket Material and Pre-Tension Bolts

Engine gaskets are used to seal metal parts of the engine to e.g. prevent steam or gas from escaping. They are complex (often multi-layer) components, usually rather thin and typically made of several different materials of varying thickness. The gaskets are carefully designed to have a specific behavior in the thickness direction. This is to ensure that the joints remain sealed when the metal parts are loaded by thermal or mechanical loads.

The new GASKET material model addresses various problems by allowing gaskets to be modeled with only one element through the thickness. The experimentally or analytically determined complex pressure-closure relationship in that direction is used directly as input for the material model.

The new CROSS-SECTION option provides an efficient and easy to use way to simulate the fastening of the bolts. It allows an arbitrary number of cross-sections to be defined in the model. Such a cross-section consists of a list of nodes, a list of elements, a normal vector, and a control node. The elements in the cross-section can be shortened by a certain amount by applying a fixed displacement boundary condition to the control node of the cross-section. Alternatively, the cross-section can be loaded with a certain force by applying a point load to the control node.

Figure 10: Finite Element Mesh of the Cylinder Head Joint

Page 22: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMesh Adaptivity

18

7. Mesh Adaptivity

A. Global Remeshing:

Several improvements and enhancements have been made in remeshing controls in automated global remeshing and rezoning over the previous version.

I. Curvature Criterion Control in Remeshing

For the Advancing Front and Delaunay meshers, the 2-D remeshing can now be based on the curvature of the boundary and thin region of the deforming body. This makes remeshing more adaptive to the changing geometry during the deformation.

II. Element Number Control in Remeshing

2-D remeshing can now be controlled by the number of elements required instead of the target element size. The number of elements can further be controlled by percentage change limit. This will make sure that the new mesh is not too fine or too coarse.

III. Penetration Control in Remeshing

The 2001 release also allows users to specify the penetration limit to check if remeshing is required. The default of using the contact tolerance is still valid.

IV. Element Edge Length Control in Remeshing

A user subroutine (usizeoutl.f) is provided for users to specify different edge lengths along the boundary. This gives users more control over the element size on the boundary. The reference to contact bodies or certain nodal positions are provided in the routine. This capability is only available for the Advancing Front and Delaunay meshers.

Figure 11: Quad Global Remeshing Menus

Advancing Front Overlay

Page 23: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

19Description of the New FunctionalitiesMesh Adaptivity

V. Error Trapping

In the analysis with remeshing, the (externally applied) boundary conditions and loads are allowed only on the bodies that are not being remeshed. For bodies involving remeshing, the boundary conditions and loads can be applied only via the contact bodies, otherwise the analysis will stop with Marc Exit 81.

B. Local Adaptivity:

An additional criterion based on temperature gradient has been introduced where an element is subdivided if the gradient in the element is greater than a given fraction of the maximum gradient in the solution. This is the recommended method for heat transfer.

Page 24: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMiscellaneous Enhancements

20

8. Miscellaneous Enhancements

A. Springs

In this version of MSC.Marc, a general spring has been added. In the previous MSC.Marc versions, the definition of a spring required not only the node(s) between which the spring is active, but also the degree(s)-of-freedom. For the new general spring, the stiffness is applied in the direction determined by the current position of the beginning and end node of the spring.

B. Substructures

A user subroutine USSUBS has been added to easily import substructures from other programs, like MSC.Nastran. The data which can be imported includes the loading, the stiffness matrix and the mass matrix.

C. CHANGE STATE Option

The CHANGE STATE option for specifying state variables has been enhanced for fixed stepping procedures like AUTO LOAD, DYNAMIC CHANGE. The state variable values can now be specified for each and every increment through the entered values, user-routine NEWSV, or the thermal post-file options. It should also be noted that the incremental change in the state variables is now reset to 0 before each increment. This means that if the state variable is not specified for an increment, the value from the previous increment is maintained.

D. POST Option

For post codes 411, 421, 431, and 441, global quantities for shell elements are reported for as many layers as requested and using the same layer numbering system as regular shell quantities. Layer 1 is the top surface, layer 2 is the next surface, etc. This convention is followed from Marc 2000 onwards.

E. Magnetostatics

The 3-D magnetostatic formulation has been improved. For this vector potential method, an important aspect is the way in which the divergence of the magnetic potential is enforced. The penalty factor used for this purpose is now be user-defined, while a new default value has been chosen, which leads to accurate results for various test problems. Also the treatment of nonlinear material behavior has been modified, so that a faster convergence will be obtained.

Page 25: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

21Description of the New FunctionalitiesParallel Enhancements

9. Parallel Enhancements

In a network parallel run, the input files are now automatically transferred to the remote hosts if necessary and the post files are transferred back after the run.

Figure 12: Network Settings Menu

Page 26: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesPostprocessing Enhancements

22

10. Postprocessing Enhancements

A. Energy Output and Energy Balance

This is available in the output as well as the post file. The types of calculated energies are:• Total strain energy• Total elastic strain energy• Total plastic strain energy• Total creep strain energy• Thermal energy (for heat transfer analysis or coupled mechanical analysis only)• Total work by all external forces

within which various contributions are also calculated as:– total work by contact forces– total work by applied forces– total work by friction forces

• Total kinetic energy• Total energy dissipated by dampers• Total energy contributed by springs• Total energy contributed by foundations

The calculated energies are available in the output as well as the post file. If needed, the energy calculations and output can be bypassed by using:

(i) parameter POST, ,N (where N>0) in the input fileor

(ii) Mentat command *job_option post_energy off.

Figure 13: The Dynamic Analysis of a Block Sliding over a Surface with Friction

Page 27: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

23Description of the New FunctionalitiesPostprocessing Enhancements

Figure 14: The Energy changes during the Sliding Process

Total original and current volumes and the total mass are also available in the output and post file.

Note that in this version, the thermal energy is not calculated for initial temperatures, whereas the kinetic energy is calculated for initial velocities.

Page 28: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesRobustness of Automatic Load Stepping Schemes

24

11. Robustness of Automatic Load Stepping Schemes

A. Automatic Time Step Cut-back

The feature to automatically cut back the time step was added in the 2000 release for AUTO LOAD and AUTO INCREMENT. However, it required use of the RESTART LAST option for data backup through the file-based I/O. The feature is now available in the AUTO STEP procedure (Figure 15) also and the backup of the data necessary to restore from the end of the previous increment is done in memory. For very large jobs, instead of using memory, the data (including that needed for data backup for the cut-back feature) can be stored on a file by using the ELSTO option. The solver can be forced to go out-of-core using the OOC parameter.

Figure 15: Robustness of Automatic Load Stepping Schemes

Any automatic load incrementation method is currently limited to input histories that only have linear variations in load or displacement since all of the automatic load incrementation methods only require the total load or displacement at the end of the loadcase. For example, one may not use a rigid body with a linearly changing velocity, since the resulting displacement of the rigid body would give parabolically changing displacements. In this case one would need to use a constant velocity for the automatic load incrementation methods to work properly.

For any automatic load incrementation, care must be taken to approriately define the loading history in each loadcase. The load case should be defined between appropriate break points in the load history curve. For example, in Figure 16, correct results would be obtained upon defining three distinct loadcases between times , , and during the model preparation. However, if only one loadcase is defined for the entire load history between , the the total applied load for the loadcase is zero.

0 t1– t1 t2– t2 t3–

0 t3–

Page 29: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

25Description of the New FunctionalitiesRobustness of Automatic Load Stepping Schemes

Figure 16: Defining Loadcases for Automatic Load Incrementation

B. Enhanced AUTO STEP (multi-criteria)

The AUTO STEP procedure has been greatly enhanced in a number of areas. It now fully supports mechanical, thermal, and thermo-mechanically coupled analysis. The procedure supports the above mentioned automatic time step cut-back. In addition to the existing user defined criteria for controlling the load step, there is the option of having the load step controlled by the number of recycles needed to obtain convergence. This option is now the default method for the AUTO STEP procedure and it allows many analyses to be run without having to change the settings for the load stepping method. AUTO STEP (multi-criteria) is now the method of choice for most types of analysis, except when the arc-length method (available through the AUTO

INCREMENT option) is more appropriate, for example, post buckling calculations.

P (

Load

)

P2

P1

t1 t2 t3

t (Time)

P (

Load

)

P2

P1

t3

t (Time)0 0

a. Three Defined Loadcases b. One Defined Loadcase

Page 30: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesRobustness of Automatic Load Stepping Schemes

26

The post file can be written with output frequency dependent on time in addition to the increments.

C. Convergence Automation

This feature addresses the problem where convergence in the solution could not be obtained due to very small reaction forces or displacements. This happens, for instance, in a contact problem where two bodies are moved into contact, but in the first few increments they may not touch so the reaction forces are almost zero. Another example is free thermal expansion. The convergence automation feature detects this case by evaluating the normalized strain energy and checking if it is very small. Other situations where convergence problems can occur is in springback calculations where the displacement increments are very small and in constrained thermal expansion where the displacements are nearly zero. In such cases, the convergence automation feature detects the small displacement increments and temporarily switches to residual force based convergence checking or vice-versa. The feature can be turned on and off with the AUTO SWITCH button in the menu shown in Figure 17 below.

Figure 17: Convergence Automation

Page 31: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

27Description of the New FunctionalitiesRobustness of Automatic Load Stepping Schemes

D. Analysis Progress Reporting

Marc 2001 has added a new file to record the progress of a calculation, which is named as jobname.sts. It is possible to view this file in Mentat through the STATUS FILE button as shown in Figure 18.

Figure 18: Run Job Menu and New Status File Button

Page 32: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMentat Menu Enhancements

28

12. Mentat Menu Enhancements

1. The TOOLS menu can now be accessed through both the RESULTS and the RESULTS→MORE menu.

2. The RESULTS→SCALAR PLOT menu section has been redesigned.

3. The button CHANGE TITLE under RESULTS has been moved to RESULTS→TOOLS.

4. JOBS→(...)→ANALYSIS OPTIONS: The label ELASTICITY PROCEDURE has been renamed to RUBBER ELASTICITY PROCEDURE.

Figure 19: Redesigned ANALYSIS OPTIONS Menu

5. The JOBS→RUN menu has been updated to support the use of a DCOM server (for Windows NT only).

6. The JOBS→RUN menu now displays more job progress reporting. The number of iterations, number of separations, number of cutbacks and number of remeshes are displayed.

7. JOBS→(ANALYSIS CLASS)→JOB PARAMETERS: The BANDWIDTH OPTIMIZATION button has been moved to the SOLVER menu. It is only active for the DIRECT PROFILE and MULTIFRONTAL SPARSE solver types.

8. MESH GENERATION→EXPAND: Two new buttons, AXISYMMETRIC MODEL TO 3D and NON-EQUISPACED, have been added to support axisymmetric modeling.

9. MATERIAL PROPERTIES→NON-MECHANICAL (MATERIAL TYPES)→FLUID: The buttons for options supporting BINGHAM, CARREAU, and GENERALIZED POWER LAW are only displayed when these models are selected.

Page 33: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

29Description of the New FunctionalitiesMentat Menu Enhancements

10. MATERIAL PROPERTIES→(LAYERED MATERIALS): The DEFINE buttons are only active when the current material is COMPOSITE, REBAR, or GASKET.

11. MATERIAL PROPERTIES: The ORIENTATION button has been relocated adjacent to the ID MATERIALS button.

12. CONTACT→CONTACT TABLES→PROPERTIES: This menu is now a floating menu that can be repositioned. The PARAMETERS section is now located in the new floating menu that is activated when one of the buttons from the contact table matrix is selected. These buttons must also be used to change the body pair when the CONTACT TABLE ENTRY PROPERTIES menu is already popped up. Note that setting the contact type to NO CONTACT, TOUCHING or GLUE must now be done in this same menu.

13. The appearance of the roller button has been changed. The roller button provides a choice of one from a list that is cycled through as you click on the button. A yellow triangle pointing down now appears on the left side of the button.

14. Separate lists have been created in the JOB RESULTS menu to allow easy verification of which element and nodal results quantities have been selected in the current job.

15. The number of interdomain nodes for a given decomposition of the finite element mesh is now displayed in the JOBS→DOMAIN DECOMPOSITION menu. This number is directly related to the amount of interdomain communication required during a DDM job.

16. The menu section for SHELL EXPAND has been moved to a new submenu MESH GENERATION→EXPAND→SHELL/LINE ELEMENTS.

17. Subsets of the GLOBAL REMESHING CRITERIA and GLOBAL REMESHING PARAMETERS have been moved to ADVANCED submenus.

18. The CONSTANT DILATATION, ASSUMED STRAIN, and UPDATED LAGRANGE PROCEDURE buttons in JOBS→(...)→ANALYSIS OPTIONS have been moved to a new ADVANCED submenu.

19. In JOBS→(...)→CONTACT CONTROL, the FRICTION menu section and the INITIAL CONTACT button have been retained whereas all other menu items have been moved to a new ADVANCED CONTACT CONTROL submenu.

20. The INCREMENT SPLITTING menu section has been renamed to PENETRATION CHECK. The ALLOWED, ITERATIVE, and SUPPRESSED buttons have been renamed to END OF INCREMENT, PER ITERATION, and OFF, respectively.

21. The menu section POSITION in CONTACT BODIES→RIGID→POSITION CONTROL has been renamed to POSITION (CENTER OF ROTATION).

Page 34: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMentat Menu Enhancements

30

22. For boundary and initial conditions types with only one degree-of-freedom (for example, STATE VARIABLE); buttons are only active if the ON button is "on". Note that for these types the ON button must be on regardless of the method (ENTERED VALUES, USERSUB, or POST FILE).

23. The PARAMETERS and ALIASES menus are now standalone.

24. Text items are being used on a much wider scale now. Most of the text items are editable, but some are readonly.Readonly text items:A readonly text item has the same colors as a display item. It can be easily distinguished from a normal display item because it lights up when the cursor is positioned over the text item. Unlike the display item, the readonly text item allows scrolling the text. If the cursor is positioned over the readable text item, the following key actions are recognized:

• Arrow Left moves the displayed text section one character to the left

• Arrow Right moves the displayed text section one character to the right

• Arrow Up moves the displayed text section one character to the left

• Arrow Down moves the displayed text section one character to the right

• Control + Arrow Left moves the displayed text section to the begin

• Control + Arrow Rightmoves the displayed text section to the end

• Page Up moves the displayed text section five characters to the left

• Page Down moves the displayed text section five characters to the right

• Home moves the displayed text section to the beginning

• End moves the displayed text section to the end

• Control + A moves the displayed text section to the beginning

• Control + E moves the displayed text section to the end

Editable text items:An editable text item can now be distinguished more easily from a normal display item because it has a darker body color and its text color is yellow instead of white. The editable text item allows scrolling and editing of the text. As a first step, the user must activate the editable text item by clicking the left mouse button

Page 35: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

31Description of the New FunctionalitiesMentat Menu Enhancements

while the cursor is positioned over the text item. As a result, the text color changes to magenta. The following mouse and key actions are then recognized:

• Mouse Left repositions the cursor

• Arrow Left moves the cursor one character to the left

• Arrow Right moves the cursor one character to the right

• Arrow Up moves the displayed text section one character to the left

• Arrow Down moves the displayed text section one character to the right

• Control + Arrow Left moves the cursor to the first character

• Control + Arrow Rightmoves the cursor to the last character

• Page Up moves the displayed text section five characters to the left

• Page Down moves the displayed text section five characters to the right

• Home moves the cursor to the beginning

• End moves the cursor to the end

• Control + A moves the cursor to the beginning

• Control + E moves the cursor to the end

• Control + H deletes the character to the left of the cursor

• Control + K deletes all characters to the right of the cursor

• Control + U deletes all characters

• Control + W deletes all characters to the left of the cursor

• Insert toggles between Overwrite and Insert mode

• Delete deletes the character under the cursor (Overwrite) or to the right of the cursor (Insert)

• Enter executes the command using the current text

• Printable Character inserts a character to the left the cursor (Insert) or replaces the character under the cursor (Overwrite) Changes to the text become permanent only if the Enter key is used.

Page 36: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMentat Menu Enhancements

32

25. The post file name in the RESULTS menu is now an editable text item. The text may be edited; when the Enter key is hit, a post file with that name is opened. This also provides an easy way to reopen the current post file: click the text item and hit the Enter key.

26. The ELASTIC ANALYSIS roller button has been replaced by a LINEAR ELASTIC ANALYSIS toggle button combined with a STORAGE roller button.

Page 37: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

33Description of the New FunctionalitiesMentat Preprocessing Enhancements

13. Mentat Preprocessing Enhancements

1. When a job CHECK is performed or a Marc input file is written, the program now checks if the geometric property types used are compatible with the element types. If not, an error message is issued.

2. More checks are now done when a job CHECK is performed, a Marc input file is written, or a job is submitted. The total number of warnings and errors are reported. If the SUBMIT command has been used and errors are detected during the automatic job checking, the job will not be submitted.

3. The user may now re-define the name of all nodal and element results quantities in the JOB→...→RESULTS menu. For each job, the modified names are stored in the model, whether the quantity has been selected or not. For selected quantities, the modified names are written to the Marc input file. As a result, they are also available on the post file. The most common use is to modify the names of the user defined element and nodal quantities such that they are more meaningful. Modifying the names of the standard element and nodal quantities may be especially useful for users who prefer to use a different language. The editing of the quantity names has been made simple through the use of text items.

4. A special expand operation has been added that allows expanding elements by rotating in a non-equispaced manner. In the new EXPAND→NON-EQUISPACED submenu, the user can define up to 25 groups. For each group, an angle and a number of repetitions can be defined.

5. Two buttons have been added in JOB→(...)→JOB RESULTS→OUTPUT FILE to toggle the writing of the CONNECTIVITY and the COORDINATES to the output file.

6. The buttons to set the PLASTICITY PROCEDURE to SMALL STRAIN-RADIAL R (*job_option plasticity:s_strn_rr) and LARGE STRAIN-RADIAL R-ADDITV D (*job_option plasticity:l_strn_rr_add) have been taken out.The other three buttons SMALL STRAIN-MEAN NRM, LARGE STRAIN-MEAN NRM-ADDITV D and LARGE STRAIN-RADIAL R-MULTIP D have been renamed to SMALL STRAIN, LARGE STRAIN ADDITIVE, and LARGE STRAIN MULTIPLICATIVE, respectively.When an older model file is imported, SMALL STRAIN-RADIAL R will be treated as SMALL STRAIN, and LARGE STRAIN-RADIAL R-ADDITV D will be treated as LARGE STRAIN ADDITIVE.

7. The loadcase option CONVERGE to select the CRITERIA in the CONVERGENCE TESTING popup menu has been split up into three options: converge, converge_moment, and converge_rotat.The latter two (INCLUDE MOMENTS and INCLUDE ROTATIONS) toggle the testing on moments and rotations respectively. As a consequence, in older procedure files

*loadcase_option converge:force_only

has to be replaced by*loadcase_option converge:residuals

Page 38: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMentat Preprocessing Enhancements

34

*loadcase_option converge_moment:off

and*loadcase_option converge:disp_only

has to be replaced by*loadcase_option converge:displacements

*loadcase_option converge_rotat:off

Compatibility of older model files has been ensured.

8. The AUTOMATIC TIME STEP CUT BACK feature (*loadcase_option time_cut), to be used in conjunction with loadcase stepping procedures FIXED, MULTI-CRITERIA, and ARC LENGTH, is now "on" by default. Older procedure files may have to be adapted.

9. The buttons INITIAL TIME STEP, MINIMUM TIME STEP, and MAXIMUM TIME STEP in the ADAPTIVE MULTI-CRITERIA LOAD STEPPING have been replaced by INITIAL FRACTION OF LOADCASE TIME, MINIMUM FRACTION OF LOADCASE TIME, and MAXIMUM FRACTION OF LOADCASE TIME, respectively. Compatibility of older model files has been ensured. Older procedure files using MULTI-CRITERIA stepping (*loadcase_option stepping:multicriteria) must be adapted.Instead of *loadcase_value inittime, use *loadcase_value initfraction, and divide the value by the TOTAL LOADCASE TIME (*loadcase_value time).Instead of *loadcase_value mintstep, use *loadcase_value minfraction, and divide the value by the TOTAL LOADCASE TIME (*loadcase_value time).Instead of *loadcase_value maxtime, use *loadcase_value maxfraction, and divide the value by the TOTAL LOADCASE TIME (*loadcase_value time).

10. The default #STEPS (*loadcase_value nsteps) as used in loadcases with FIXED stepping procedure, has been changed from 1 to 50. Older procedure files may have to be adapted.

11. For springs, the user may now choose from three types: FIXED DOF, TO GROUND, and TRUE DIRECTION. The button to toggle the SPRING TO GROUND functionality has been taken out. The same effect can now be achieved by setting the spring type to TO GROUND.Similar changes have been made to the N TO 1 SPRINGS/DASHPOTS and N TO N SPRINGS/DASHPOTS menus. Compatibility of older model files and procedure files has been ensured.

12. The FORMATTED/BINARY buttons have been taken out for boundary and initial conditions. This is now derived from the post file name.

13. The buttons supporting Marc’s AUTO TIME procedure - loadcase stepping procedure TIME (MECHANICAL) (*loadcase_option stepping:time_mech) - have been taken out, except for the LOADCASE→MECHANICAL→STATIC menu. If a user opens an older model file which uses this loadstepping scheme, the MULTI-CRITERIA scheme will now be highlighted.

Page 39: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

35Description of the New FunctionalitiesMentat Preprocessing Enhancements

At opening of such a model file, the following loadcase options and parameters are changed:The parameter minstep divided by the loadcase time is copied to the minfraction parameter. The maxinc parameter is copied to the maxnsteps parameter. The minimum of the maxfraction parameter and the inverse of the minfraction parameter is copied to the scale_step parameter. The desired option is switched on. Older procedure files which use this loadstepping scheme must be edited in a similar fashion.

14. If an element is expanded, the element type is now automatically set based on the type of the original element. This may influence older procedure files.

15. SUPERPLASTICITY CONTROL may now be used in conjunction with the MULTI-CRITERIA stepping procedure. The combination with the ARC LENGTH stepping procedure has now been disabled.

16. The time step size in a loadcase using the FIXED stepping procedure is now displayed.

17. The number of STATE VARIABLES in a job can now be set in JOBS→(...)→JOB PARAMETERS. This is useful when the user wants to have more state variables than what is automatically calculated.

18. In JOBS→(...)→JOB PARAMETERS - SOLVER, the NONSYMMETRIC MATRIX solver type has been removed and NONSYMMETRIC SOLUTION is now a separate job option. Compatibility of older model files has been assured. In older procedure files, the line *job_option solver:nonsym must be replaced by *job_option solver:dir_profile *job_option solver_nonsym:on.

19. In MESH GENERATION→ATTACH, the user can change the number of curve/surface DIVISIONS used for attaching nodes/elements to curves or surfaces.

20. The PARAMETERS menu offers two methods of defining or modifying parameters (*define vs. *eval_define). If the EVALUATION METHOD is DELAYED (the default), the parameter becomes an abbreviation for the expression that is assigned to it. If the EVALUATION METHOD is IMMEDIATE, the expression is evaluated first and its value is assigned to the parameter.The difference becomes apparent when the expression contains other parameters or calls to numerical functions that return information about the model. The value of a parameter defined using the delayed evaluation method is the value of the expression assigned to it at the time the parameter is being used. By contrast, the value of a parameter defined using the immediate evaluation method is the value of the expression at the time of the definition of the parameter.

21. If needed, the user may enter the command *job_option post_energy:off to let Marc bypass the computation of energies for the post file.

Page 40: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMentat Preprocessing Enhancements

36

22. A button called UNITS AND CONSTANTS has been added to the JOBS→(...)→ PARAMETERS menu allowing you to set the job option temperature_unit, which can be either kelvin, celsius, fahrenheit, or rankine. You can also set the universal gas constant and the Stefan-Boltzmann constant.The default temperature unit has been changed to celsius. This may influence older procedure files for radiation analysis.The existing buttons to set the temperature unit and the Stefan-Boltzmann constant have been removed from the RADIATION PARAMETERS menu. Related buttons for heat transfer truss geometric properties have been removed.

23. The drawing of orientations can now be controlled via the PLOT menu. Drawing of orientation can be switched on or off, drawing of orientation labels is supported and the red, green, and blue vectors that indicate the first, second, and third direction of the orientation can be switched on and off individually.

24. The button to set the DYNAMIC TRANSIENT OPERATOR to HOUBOLT (*job_option dynamic: houbolt) has been taken out. When an older model file is opened, HOUBOLT will be treated as SINGLE-STEP HOUBOLT. In addition, the buttons MODAL SUPERPOSITION, NEWMARK, and SINGLE-STEP HOUBOLT have been moved to the new IMPLICIT submenu, whereas the buttons CENTRAL DIFFERENCE and FAST CENTRAL DIFFERENCE have been moved to the new EXPLICIT submenu.

25. The default BUCKLE SOLUTION METHOD is now LANCZOS. Older procedure files may have to be adapted.

26. The REBAR MATERIAL PROPERTIES menu has been updated to support the new input options for rebar elements. Due to the increased number of input options, only the buttons for a single layer are displayed. The LAYER button allows switching between the various layers.Note that the THICKNESS DIRECTION for rebar elements is now entered in this menu. Previously, this was done in GEOMETRIC PROPERTIES. The menus for REBAR geometric property types have therefore been removed. The THICKNESS of plane strain and 3-D membrane rebar elements must now be entered in the PLANE STRAIN and MEMBRANE geometric property type menus.When an older model is opened, the old thickness direction geometric property data is not automatically transfered to the new thickness direction material property data. The rebar geometric property types are changed to the equivalent non-rebar types. For convenience, a string "_f45", "_f31", "_f02", "_e02" or"_e31" is appended to the name of those geometric properties to indicate the old thickness direction (FACE 4-5, FACE 3-1, FACE 0-2, EDGE 0-2 or EDGE 3-1, respectively).

27. New functionality has been added to enhance tha support of the Marc capability AXITO3D. A new menu MESH GENERATION→EXPAND→EXPAND AXISYMMETRIC MODEL has been created, and an option has been added in the INITIAL CONDITIONS→MECHANICAL→AXISYMMETRIC TO 3D menu. See also the special section on AXITO3D in this chapter.

Page 41: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

37Description of the New FunctionalitiesMentat Preprocessing Enhancements

28. The default for GLUE contact is now to suppress separation. A new toggle SEPARATION ALLOWED has been added to the CONTACT TABLE ENTRY PROPERTIES menu to allow glued contact bodies to separate. Old model files still behave as before. Old procedure files may have to be adapted.

Page 42: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Description of the New FunctionalitiesMentat Postprocessing Enhancements

38

14. Mentat Postprocessing Enhancements

1. For a scalar plot using NUMERICS, the user can now choose between various formats for the display of the numeric values. This can be done in RESULTS→ SCALAR PLOT SETTINGS→NUMERICS.Possible formats are AUTOMATIC, EXPONENTIAL, FLOATING, and INTEGER. For the exponential and floating format, the PRECISION may also be changed (default: 3). The default format is AUTOMATIC, which is the format used by previous Mentat versions.

2. For a scalar plot using NUMERICS, numeric values are now drawn only at nodes which have a nodal value within the RANGE specified in the RESULTS→SCALAR PLOT SETTINGS→RANGE menu section.If the range is set to MANUAL, this feature can be used to produce cleaner plots.

3. For a scalar plot using NUMERICS, the LEGEND only shows the minimum and the maximum of the range.

4. The user can choose between various formats for the display of the values in the LEGEND. This can be done in the new LEGEND submenu, which can be accessed through RESULTS→SCALAR PLOT SETTINGS, RESULTS→VECTOR PLOT SETTINGS, RESULTS→TENSOR PLOT SETTINGS, and RESULTS→BEAM DIAGRAM SETTINGS.Possible formats are AUTOMATIC, EXPONENTIAL, FLOATING, and INTEGER. For the exponential and floating format, the PRECISION may also be changed (default: 3). The default format is AUTOMATIC, which is the format used by previous Mentat versions. Note that the button to toggle the display of the legend has been moved to the new LEGEND submenu.

5. The size of the color boxes in the LEGEND in case the number of LEVELS is smaller than 10 is now the same as when the number of LEVELS equals 10.

6. Two new commands have been added to allow more flexible access of post file increments.

PREV (*post_prev): reads the previous increment.LAST (*post_skip_to_last): reads the last increment.

7. When the post file is closed, the program now automatically switches to displaying the model.

8. Tools have been added to the RESULTS/TOOLS menu to select nodes or elements based on the values of the scalar quantity that is being postprocessed. The nodes and elements were the scalar quantity assumes its minimum or maximum or in which the scalar quantity assumes values in a given range can be selected. The tools will select only nodes or elements that are visible and are that being post-processed. Selection is always based on the values of the quantity at the nodes and takes the active extrapolation scheme into account.

Page 43: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

39Description of the New FunctionalitiesMentat Postprocessing Enhancements

Five new numerical functions have been added that are especially useful in procedure files during postprocessing:

As with the selection tools, only the values of the scalar quantity at the nodes are considered by these functions.

9. The toggle button LABEL CONTOURS has been added to the RESULTS→SCALAR PLOT SETTINGS menu. This toggle controls the labeling of CONTOUR LINES plots.

scalar_pos(x,y,z) Returns the value of the scalar quantity that is being postprocessed at (x,y,z), if that position is located somewhere in the finite element mesh or 0 if the position is outside the finite element mesh. The value is obtained by interpolating in the closest element.

scalar_min_node()scalar_max_node()

Returns the first node in which the scalar quantity assumes its minimum or maximum.

scalar_min_element()scalar_max_element()

Returns the first element in which the scalar quantity assumes its minimum or maximum.

Page 44: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

References to Examples of the New FunctionalitiesMentat Postprocessing Enhancements

40

III. References to Examples of the New Functionalities

1. Analysis Speed and Memory Improvements• Nearly all examples with contact• Nearly all examples using the new multifrontal sparse (Solver,8)• New Features Guide: Chapter 1

2. AXITO3D: Data Transfer from Axisymmetric to 3-D Analysis

Volume E: e8x61a, e8x61b, e8x67a, e8x67bNew Features Guide: Chapter 6 examples on standard mechanical, rebars, and remeshing/rezoning

3. Contact Enhancements

Volume E: e8x65, e8x67b, e8x68New Features Guide: Chapter 9

4. Cyclic Symmetry

Volume E: e8x69New Features Guide: Chapter 3 examples on torsion of a bar, friction clutch analysis as standard mechanical as well as coupled

5. Element Technology

Volume E: e7x20e, e7x29e, e7x33

6. Gaskets and Pre-Tension in Bolts

Volume E: e2x79, e3x39New Features Guide: Chapter 2

7. Mesh Adaptivity

Volume E: e8x59d, e8x59e, e8x64New Features Guide: Chapter 8 examples on remeshing with rubber as well as rubber and metal

8. Parallel Enhancements

New Features Guide: Chapter 5 examples to demonstrate file copy feature

9. Postprocessing Enhancements

Volume E: e3x32a, e5x7, e6x22, e8x13, e8x55, e8x66New Features Guide: Chapter 7

10. Robustness of Automatic Load Stepping Schemes

Volume E: e8x65, e8x67bNew Features Guide: Chapters 4 and 7

Page 45: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

41List of Defects Fixed in ReleaseMSC.Marc 2001

IV. List of Defects Fixed in Release

MSC.Marc 2001

Adaptive Mesh Refinement:

Contact:

Coupled Analysis:

1 Manual remeshing has been fixed to give correct results for tetrahedral elements.

2 CONTACT CHANGE, GEOMETRY CHANGE, and ISOTROPIC CHANGE options have been fixed to give correct results in rezoning.

3 The use of distortion criterion has been fixed for automated remeshing with multiple bodies.

4 Adaptive meshing has been fixed to give correct results for tetrahedral elements.

5 DEACTIVATE option has been fixed to give correct results with adaptive meshing.

6 The convergence testing on displacements in the step after remeshing in the automated remeshing and rezoning has been fixed.

7 Shell elements now give correct results in coupled analysis when adaptivity is used.

8 wkslp.f and crplaw.f are now correctly called for analyses with global remeshing.

1 A node with a fixed displacement coming into contact with a flexible patch from which the patch normal is not exactly perpendicular to the fixed displacement could get some small displacement in the direction of the fixed displacement. This defect has been fixed.

2 In the usage of motion.f and defining velocities of the die as a function of time (cptim), the potential problems with the APPROACH option have been fixed.

3 Error in analysis with two load controlled bodies and one velocity controlled body has been fixed.

4 Use of ADAPT GLOBAL now gives correct results with contact in coupled analysis.

5 Iterative penetration checking procedure has been fixed with position controlled bodies.

6 Error for a node with applied displacements and simultaneously in contact with two NURBS has been fixed.

7 Gradual release has been fixed to give correct results.

1 Coupled analysis procedure for anisotropic materials has been fixed.

2 Coupled analysis with UPDATE and TRANSFORMATION options has been fixed.

Page 46: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Defects Fixed in ReleaseMSC.Marc 2001

42

Design Sensitivity and Optimization:

Dynamics:

Element Formulation:

Fluid Analysis:

Fracture Mechanics:

Heat Transfer and Thermal Stress:

1 Element number printout in design sensitivity analysis has been fixed. Analysis was correct though.

1 Dynamic,5 (Fast Central Difference Operator) has been fixed to give correct results in the first increment also in the case of applied loads without follower force.

2 Lanczos and Power sweep now give identical results during buckle increments.

3 Harmonic analysis now gives correct results with elastic foundation.

4 Interfaces to user subroutine usprng.f has been fixed to give correct results in harmonic analysis.

5 Modal superposition with elements 52 and 98 has been fixed.

1 Element type 52 (elastic beam) has been fixed to give correct results with PROCESSOR and POINT LOAD options.

2 Element type 19 (generalized plane strain) has been fixed to give correct results in a finite strain analysis.

1 Fluid Solid analysis has been fixed to give correct results for heat transfer elements defined on last line of connectivity block.

2 film.f is correctly called for fluid-thermal-solid simulation.

3 Fluid Solid analysis has been fixed to allow the use of assumed strain for the solid part of the model.

1 Shift direction calculation for collapsed brick elements in 3-D analysis with J-Integrals has been fixed.

1 Thermal radiation with reflection for fahrenheit has been fixed.

2 RADITION option has been stabilized (for cases where part of the model is connected to the outside world via radiation and not structured elements, films, and boundary conditions.

Page 47: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

43List of Defects Fixed in ReleaseMSC.Marc 2001

Loading and Boundary Conditions:

Material Models:

Memory and I/O Related:

Miscellaneous:

Parallel Processing:

1 Nodal coordinates with CYLINDRICAL option are correctly transformed.

2 INITIAL ACCELERATION option has been fixed to work correctly for AXITO3D analysis.

3 SERVO LINK option has been fixed to read maximum number of retained nodes correctly.

1 The resulting creep tensor has been fixed to be defined correctly when ORIENTATION option is used.

2 Plastic strain energy is now being calculated correctly for steady state, Eulerian R-P Flow.

1 The NEW option has been fixed to be read in the model definition section.

1 User subroutine upstno.f modified to correctly extract nodal data.

2 The .t01 is no longer erroneously deleted at the end of the run.

3 The utility routine elmvar.f has been modified to correctly pass back beam forces and moments.

4 Nodes of the springs are no longer being swapped in the usprng.f user subroutine.

1 Parallel version has been fixed to correctly support for t19 file to input a post file in case of change state (e.g. Thermal-Stress analysis).

2 Parallel analysis is fixed to give correct results with a combination of AUTO THERM and CHANGE STATE.

3 Creep analysis now gives correct results in analysis on multiple processors.

4 AUTO CREEP option has bee fixed to give correct results with use of nonconsecutive element numbers.

Page 48: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Defects Fixed in ReleaseMSC.Marc 2001

44

Preprocessing, Postprocessing, and Output:

Restart:

Solver and Analysis Procedure:

Also, several changes have been made to documentation and data files in the demo directory.

1 Discontinuous post file on restart has been fixed for adaptive meshing.

2 User subroutine elmvar.f has been fixed for post code 269.

3 Post file has been fixed to contain correct results in magnetostatic analysis.

4 Output has been fixed to contain correct values for the maximum and average relative sliding velocity.

5 Output for strain energy has been fixed for APPROACH option.

6 Correct messages are issued in case of residual convergence criterion usage where loads are applied only to free node.

7 Analysis with usage of flow lines option without global remeshing exits correctly with input error message.

8 Strain energy is correctly output for rubber models in total Lagrangian analysis.

9 The beam moments for element type 5 have been made consistent with other beam elements.

1 The restart capability has been fixed when upper bound on the number of elements on the ADAPTIVE option is much larger than the actual number of elements used.

1 AUTO STEP procedure has been fixed for cases with coupled analysis.

2 Case of multiple AUTO STEP options has been fixed.

3 AXITO3D feature fixed to correctly account for point and distributed loads in increment 0.

4 Transient heat transfer has been fixed for powder materials.

5 Solver, 6 has been fixed for use with RESTART and ADAPTIVE MESHING on SGI.

6 For analysis using the in-core, direct profile solver, an automatic switch is made to the out-of-core direct profile solver if the integer value, during the determination of the storage requirements, exceeds the number 2**31.

7 Eigenvalue analysis with greater than 160 Lanczos vectors using HP hardware sparse solver has been fixed.

Page 49: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

45List of Defects Fixed in ReleaseMSC.Marc Mentat 2001

a

s

.

MSC.Marc Mentat 2001

Preprocessing:

1 Mentat will now correctly evaluate an Ogden curve fit with small volumetric strains and a large bulk modules. Previously a “stair-step” would appear in the curve.

2 The CHECK ZERO VOLUME option now properly identifies zero volume elements.

3 Mentat will now properly display the ORIENTATION TYPE for 3D ANISO.

4 It is now possible to assign a table of type TEMPERATURE to the INITIAL YIELD STRESS when USER SUB WKSLP has been selected.

5 When a node is deleted in a sweep operation, its crack tip node data is now transferred to the node that is replacing it.

6 When an element is deleted in a sweep operation, its orientation data is now transferred to the element that is replacing it.

7 When a node (element, point, curve, surface), that is part of a set, is deleted insweep operation, the program now functions properly. Previously, the program might crash if the node (element, point, curve, surface) that was replacing it wanot part of the same set.

8 After editing a line element (*edit_element), the program automatically redraws in all cases.

9 A link is automatically redrawn when the position of one of its nodes is changed

10 The material type of nonmechanical materials is now shown correctly in menuswhere materials are selected (e.g. MATERIAL PROPERTIES – EDIT).

11 The length of the table selection lists is now correct in cases when only tables of the specified type or of type none are shown.

12 In table selection lists for parameters that have multiple tables, tables of type none are not shown.

13 The light on the INITIAL LOADS button now functions correctly. Previously, it would not burn if initial conditions were selected and all of them deleted from the model subsequently, which is incorrect if boundary conditions have been selected for the job.

14 The current job (loadcase, boundary condition, table, etc.) is now restored after closing a post file or using the UNDO command. This may influence older procedure files which use these two commands (*post_close, *undo).

15 The buttons to set element type 15 and 16 have been taken out as these types are not completely supported by Mentat (special coordinates).

16 Curve fitting now allows fitting of data for continuous and discontinous rubber damage models.

Page 50: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Defects Fixed in ReleaseMSC.Marc Mentat 2001

46

Postprocessing

Marc Input File Writer

1 The Post Monitor command can now be interrupted by pressing the Enter key.

2 The Post Monitor command now properly handles remeshed geometry.

3 The display of Links and Rigid Dies are now properly updated when using the Post Monitor command.

4 Particle Tracking is now properly handled when a discontinuous post file is used.

5 The SIZE value listed in the SCAN menu now properly accounts for all domains. It previously only reported the value for the first domain.

6 Scale factors for the XY Plotter will be correctly displayed for values in the range of 0 to 0.5.

7 The computation of the value of the phase angle from complex harmonic results is correct on all platforms (HP and Solaris were incorrect before).

8 After history_collect, the program does not automatically switch to displaying the model.

9 The deformed configuration of springs is automatically updated when going to another increment.

10 The CONTOUR plotting on 8-noded element faces is correct in cases of a nonlinear gradient over the element face.

11 The automatic calculation of the RANGE for 8-noded element faces is correct.

12 User-defined nodal vectors can be postprocessed when the maximum number of degrees-of-freedom per node is 1.

13 The axis scale factor in tables, history plots etc. is displayed correctly. For a factor of 100000, it uses x1e5. Previously, x10e5 was used.

1 If a model contains an initial condition of type displacement, a correct Marc input file will be produced if a nonzero value has been specified for an inactive degree-of-freedom (the ON button is off.) The same fix applies for initial condition types velocity, stress, temperature, and joul_temperature.

2 Mentat will write a correct Marc input file if a model contains fluxes, films, or charges on the bottom face of shell elements.

3 If a model contains multiple point loads for a dynamic harmonic loadcase, Mentat will write a correct Marc input file.

4 Mentat will write a correct Marc input file if a model contains a velocity or position-controlled rigid contact body that has no entries (curves, surfaces).

5 If a model contains a VOLUME CURRENT boundary condition, Mentat will write a correct Marc input file.

Page 51: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

47List of Defects Fixed in ReleaseMSC.Marc Mentat 2001

Marc Input File Reader

I-DEAS Reader

6 If a DDM model contains a loadcase using the MULTI-CRITERIA stepping procedure, and a node or element set has been selected for the criterion, a correct Marc input file is produced. Before, problems would occur if the set did not have any entries in one of the domains.

7 A correct input file is produced for models with nonuniform fluxes/films on the first edge of triangular heat transfer elements (type 37 and 38).

8 A correct input file is produced if for an isotropic material rigid-plastic plasticity has been selected and subsequently removed,

9 A correct input file is produced for all available models of FLUID material properties. Previously, only the default (Newtonian) model was handled correctly.

10 An error message is produced if a float value is encountered that cannot be written in exponential format; for example, when it exceeds the maximum allowed float value. Previously, the program would crash.

11 When a node is attached to the end point of a curve, it is taken into account when a boundary condition has been placed on that curve. This is consistent with the plotter.

12 Elements of type 14 are read.

1 Marc reader has been fixed to correctly read in the control node when reading an input in Mentat.

2 The import marc command properly handles distributed loads for shell elements when the element numbering is not consecutive.

3 The requested layers for element results quantities are read from a Marc input file.

4 The data for GLOBAL REMESHING CRITERIA is transferred (in case the ADAPT GLOBAL option appears before END OPTION in the Marc input file).

5 The connectivity of 3-noded line elements is transferred correctly.

6 Elements of type 14 are read.

1 The Ideas translator will import materials for data set 773 and point load data for set 782 properly.

2 Permanent groups appearing as data set 2432 or 2435 are processed.

Page 52: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Defects Fixed in ReleaseMSC.Marc Mentat 2001

48

Nastran Reader

Patran Reader

Import/Export General

1 The RBE2 elements in a Nastran bulk data file are properly converted to tying type 80.

2 The Nastran translator properly uses transforms CORD1R and CORD2R.

3 Correct coordinates are generated for nodes (entry GRID, field CP) for which the displacements are defined in a spherical coordinate system (entries CORD1S and CORD2S).

4 Correct transformations are generated for nodes (entry GRID, field CD) for which the displacements are defined in a spherical coordinate system (entries CORD1S and CORD2S).

5 Generated transformations have names.

1 Importing a Patran neutral file is working in those cases where the Patran model contains element classes which are not supported by Mentat (for example, Hex9) and the node numbering is nonconsecutive.

1 The limitation for a 72 character path/filename has been removed.

Page 53: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

49List of Known Problems in ReleaseMSC.Marc 2001

V. List of Known Problems in Release

MSC.Marc 2001

1. Analysis may prematurely become unstable with Newmark-Beta implicit dynamics algorithm in an analysis involving contact where a few or several nodes separate from the contact surface within a span of few increments. In such cases, the vibrations propagate to generate spurious energy.Workaround: Use the new Single Step Houbolt dynamic operator instead.

2. Shell thickness is incorrectly reduced by thermal expansion upon use of LARGE DISP, UPDATE, FINITE parameters due to use of incompressibility condition.

3. Potential core dump on selecting post codes that are not appropriate for analysis type, for example, requesting creep strains when creep is not involved in an analysis.

4. In a coupled analysis, during the heat transfer pass the temperature of the tied node is set equal to the temperature of the first retained node, except for:

a. user-defined tyings, which go through user subroutine uforms;

b. tying types 31, 32, 33, and 34, which are treated correctly;

c. tying types 85, 86, and 87, which are special temperature tyings;

d. tying types 23 and 25, which are ignored.

5. If a read or write problem (disk full, for instance) occurs during a parallel analysis, some processes might not stop and the job will hang indefinitely. If the job is started from the command line and running on the foreground, it can be stopped by entering Ctrl-C. If the job is started from Mentat, the processes need to be identified and stopped. If no user subroutine is used, the name of the executable program is marc (UNIX) or marc.exe (NT). If a user subroutine plotv.f is used, the name of the executable is plotv.marc (UNIX) or plotv.exe (NT).

6. If a material database file is used in a parallel network run with local directories, it must be copied into the local directories of the remote machines before the job is started.

7. Solver 8 sometimes terminates abnormally when a pivot tolerance is specified under the SOLVER or CONTROL option.

8. When solver 8 goes out-of-core, it sometimes will print an amount of disk space required which is not large enough.

9. The parallel version on NT sometimes will terminate abnormally with a message stating that memory allocation failed. In this case, the value of SHAREMEM in the tools\include.bat should be increased to a value large than 20,000,000.

Page 54: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Known Problems in ReleaseMSC.Marc 2001

50

10. Marc does not increase the available memory at the time an out-of-core solution has been decided upon. Thus, job will fail if memory needed at this stage is more than that requested initially, although it may be less than what could be supplied for an in-core solution. In this case, the problem can be resolved by increasing the amount of memory requested to a number greater than indicated as needed for the out-of-core solution.

Page 55: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

51List of Known Problems in ReleaseMSC.Marc Mentat 2001

MSC.Marc Mentat 2001

1. Static Standalone Menus

The command line option -df STATIC_STANDALONE no longer works when the menus are read from a binary menu file. Instead the above option should be used when compiling the menus (mentat -df STATIC_STANDALONE -compile menus/main.msb), or the binary menu file should be deleted and the option used as normal.

2. Radiation View Factors

The Marc reader does not support radiation view factors.

3. Marc import does not support element types 4, 8, 13, 15, 16, 17, and 24

Element types 4, 8, 13, 15, 16, 17, and 24 are not supported by the Marc reader (IMPORT MARC).

4. Running Marc Job in Different Directory

A Marc job can only be started in the working directory. If a Mentat model file is opened in another directory, you must first do a SET DIRECTORY to that directory if you want the job to run there. A Marc job is always run in the working directory. See Item 5 under VIII. Important Notes in the Release Notes.

5. Drawing of symbols on Digital Unix very slow

The drawing of symbols (nodes, points, etc.) in the OpenGL version of Mentat on Compaq/Digital Unix is very slow. This is due to a problem in the glBitmap implementation. This problem is seen when a model is first drawn with nodes or points turned on.

6. Marc import and export does not support edge foundation on 3-D beam elements

For 3-D beam elements, the edge foundation option (BOUNDARY CONDITIONS – MECHANICAL – EDGE FOUNDATION) is not supported by the Marc reader (READ MARC) or Marc writer (WRITE MARC).

7. Converting quad surface to solid face not supported

Converting a quad surface to a solid face is not supported.

8. Recover option always requests both modal stresses and reactions

When doing an eigenvalue extraction, Mentat always generates the RECOVER option to request both modal stresses and reactions. This can lead to slow eigenvalue analysis if these items are not needed. To disable this, specify a 0 in the 3rd field (columns 11-15) of the second data block of the RECOVER option if only the eigenvectors are required.

9. Contact Status may show non-integer values in Local Adaptivity analysis

When postprocessing the scalar Contact Status in a Local Adaptivity analysis, some nodes may appear in red (a value of .5) when they should have an integer value. The value of 0, so the nodes with a value of 0.5 are not in contact

Page 56: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Known Problems in ReleaseMSC.Marc Mentat 2001

52

10. 3-D Beam Results Layer Selection not written to dat file

When results are requested for ALL or OUTER & MIDPLANE layers of 3-D beam elements (under JOB RESULTS), this information is not written to the .dat file. Only layer 1 is written to the .dat file post section.

11. Thickness not written to dat file for Bearing Analysis

When a Bearing analysis is run, the thickness option and the loadcase options for stiffns components and thickns change are not written to the .dat file.

12. Global Remeshing and Local Adaptivity

Mentat does not give an error message if GLOBAL REMESHING and LOCAL ADAPTIVITY are used at the same time.

13. Scaling a Solid Cylinder fails on HPUX

The MOVE – SOLIDS command will not scale a solid cylinder on HP-UX 10.20. This is due to a problem in the ACIS library that Mentat uses for solid modeling.

14. Patran Reader does not support thickness of shells

The Patran reader will not properly read the thickness of shells.

15. Converting Solid Faces to Surfaces

Running the SOLID FACES TO SURFACES command under the SOLIDS menu will fail if there are any inside out faces. If the command fails, the solid should first be checked with CHECK ENTITIES before running this command. Run the CHECK ENTITIES command, and if any error is found, do not run the SOLID FACES TO SURFACES command.

16. Converting a Solid Cylinder to Faces

When a solid cylinder is converted to a surface using the SOLID FACES TO SURFACES command and then converted to elements using the SURFACES TO ELEMENTS command, the resulting elements will overlap at the surface boundary.

17. Python feature availability

The external modules py_mentat and py_post are not available for IBM AIX, Solaris 2.5, and HP platforms with the PA 1.1 architecture.

18. Using Font 9x15 on HP-UX

To use the 9x15 font on HP-UX 10.20, you must run the following command prior to running Mentat:

xset -fp /usr/lib/x11/fonts/iso_8859.15/75dpi

Page 57: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

53List of Known Problems in ReleaseMSC.Marc Mentat 2001

19. Mentat OpenGL version on IBM

The OpenGL version of Mentat may not operate properly on some IMB platforms. The runtime libraries patch 4.3.3.25 is required.:

20. Linux Platforms

The Solids version of Mentat is not suppported on the Linux platforms for this release. MesaGL v3.4 or higher is required to run the OpenGL version on Linux.

21. Remeshing

If a job requires remeshing, a SCAN (post_scan) will not update the increment list properly while the job is running. This is also true for PATH PLOT and HISTORY PLOT. A workaround for this problem is to select the LAST increment button, and then proceed with SCAN, PATH PLOT, or HISTORY PLOT.

22. Particle Tracking while a job is running

Particle Tracking will not be updated properly when doing a SCAN, NEXT, or LAST while a job is running. It will be correctly displayed when the job has completed.

23. Job Check Error Messages

Upon writing a Marc input file, checking a job or submitting a job, Mentat fails to give an error message if one of the situations listed below occurs in the model for loadcases using an adaptive stepping procedure. In such cases, the user must either select fixed stepping, or cut up the loadcase in smaller parts such that the situation does not occur.

(i) A boundary condition that is written to the Marc input file in an incremental fashion, which was active previous to this loadcase and inactive in this loadcase, has a degree-of-freedom with a nonzero magnitude at the start of the loadcase

(ii) A boundary condition that is written to the Marc input file in an incremental fashion, which is active in the loadcase, has a degree-of-freedom with a magnitude that is varying nonlinearly over the loadcase time period.

(iii) A boundary condition that is written to the Marc input file in an total fashion, which is active in the loadcase, has a degree-of-freedom with a magnitude that is not constant over the loadcase time period.

(iv) The position of a position-controlled rigid body is changing during the loadcase time period.

(v) The velocity of a velocity-controlled rigid body is changing during the loadcase time period.

(vi) The length of an actuator truss element is changing during the loadcase time period.

Page 58: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Known Problems in ReleaseMSC.Marc Mentat 2001

54

Boundary condition types that are written to the Marc input file in an incremental fashion are:

fixed_displacement, point_load, edge_load, face_load, global_load, gravity_load, centrifugal_load, fixed_pressure, point_source,edge_source, face_source, volume_source, fluid_point_load,fluid_edge_load, fluid_face_load, fluid_global_load,fluid_gravity_load, fluid_centrifugal_load

Note that for centrifugal loads the square of the angular velocity in radians/time is used as magnitude.All other boundary condition types that are written to the MARC input file in a total fashion.

Page 59: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

55List of Build and Supported Platforms for ReleaseMSC.Marc 2001

VI. List of Build and Supported Platforms for Release

MSC.Marc 2001

Note: For most platforms, the default MPI setting for this release uses MPICH, with the option of switching to hardware specific MPI when so desired.

Vendor OS HardwareFORTRAN

VersionParallelEnabled

DefaultMPI

AlsoWorks On

Compaq (DEC) OSF1 4.0d Alpha f77 5.1 yes MPICH 1 TRU64

CRAY UNICOS 10.0.0.8UNICOS 10.0.0.8

J90C90

CF90 3.0.2CF90 3.0.2

yesyes

CRAY MPICRAY MPI

YMP, SVIT90

HP HPUX 10.20HPUX 10.20HPUX 11.0

(32 bit)HPUX 11.0

(64 bit)

PA1.1PA2.0PA2.0

PA 2.0

f77B10.20.09f77B10.20.09f90 2.4

f90 2.4

noyesyes

yes

MPICH 1

MPICH 1

HP MPI01.06

IBM AIX 4.3.1AIX 4.3.3

RS/6000RS/6000 SP

XLF 5.1XLF 5.1

yesyes

MPICH IBM POE

PPE 3.1

AIX 4.3.2–4.3.3

Intel NT 4.0 sp3 Intel Pentium Digital Fortran 6.0a2 yes PaTENT Windows 2000

Linux3 Linux 2.2.12 Intel Pentium pgf77 3.1-3 yes MPICH Linux 2.2.13 or later

SGI IRIX 6.2IRIX 6.2

mips4 64 bit mips3 32 bit

f77 7.2.1f77 7.2.1

yesyes

MPICH 1

MPICH 1IRIX 6.4, 6.5IRIX 6.3, 6.5

Sun Solaris 2.5 Ultra2 f77 4.2 yes MPICH 1 Solaris 2.6, 2.7, and 2.8

1 Hardware MPI version also available (via maintain in /tools directory).2 Can be used with Digital Fortran 6.5.3 The Solids version of Mentat is not supported on the Linux platform.

Page 60: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Build and Supported Platforms for ReleaseMSC.Marc Mentat 2001

56

MSC.Marc Mentat 2001

The following platforms and operating systems are supported by Mentat 2001.

Vendor OS Hardware Also Works On OpenGL1

Compaq (DEC) OSF1 4.0D Alpha TRU64 y

HP HPUX 10.20.0HPUX 10.20.0

PA1.1PA 2.0

HPUX 11.0HPUX 11.0

yy

IBM AIX 4.3.1 RS/6000 AIX 4.3.2–4.3.3 y

SGI IRIX 6.2 mips3 IRIX 6.3–6.5 (32 bit and 64 bit)

y

Sun Solaris 2.5Solaris 2.6

Ultra Solaris 2.7–2.8 y

Intel NT 4.0 sp4 Intel Pentium Windows 2000 y

Linux 2 Linux 2.2.12 Intel Pentium Linux 2.2.13 or later y

1 See OpenGL Compatibility table below.2 The Solids version of Mentat is not supported on the Linux platform.

Page 61: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

57List of Build and Supported Platforms for ReleaseMSC.Marc Mentat 2001

OpenGL Compatibility

When running over a network the following combinations of client machine (where Mentat is running) and graphical server (where the user is viewing the program) have been found to work properly using OpenGL:

Client

Server

Compaq HP8 IBM SGI7 SUN6 NT2, 10 Linux

Compaq (DEC) y1 n y n y y n

HP y y y y9 n y y

IBM y y y y y y n

SGI n y y y y y n

SUN y y y n y3 y n

NT n n n n n y n

Linux5 y y y n4 y y y1 Double buffering not available.2 Requires additional software (see http://www.hummingbird.com or other vendor of X server

software).3 Single (direct) buffering may not work on some Solaris 2.6 machines.4 X version doesn’t work either.5 Requires MesaGL v3.4 or higher.6 Running “what /usr/openwin/lib/libGL.so” should return a date of 10/27/99 or later.7 On SGI Onyx with Reality Graphics, see the MSC.Marc 2000 and MSC.Marc Mentat 2000

Installation Instructions for UNIX Systems Appendix B for information on installing a special version of Mentat.

8 You must install the “OpenGLRuntime B.10.20.08 HP-UX OpenGL Run Time Environment” (OpenGL 1.1 Revision 1.15).

9 Some buffering problems may occur when changing workspaces.10 The following OpenGL graphics cards have been found not to work:

Compaq PowerStorm 300 and 4D10T

STB Velocity 4400

Intense 3D Pro 3410

Page 62: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

List of Dropped PlatformsMSC.Marc Mentat 2001

58

VII. List of Dropped Platforms

The following platforms have been dropped as of this release:

• Sun Supersparc

• HP SPP-UX

• Compaq NT Alpha

• Intel Digital Fortran 5.0

In future, users are recommended to upgrade the compilers to FORTRAN-90 on high-end machines to have compatibility with the built version using FORTRAN-90.

The following platforms will be dropped as of the next release:

• Sun - Solaris 2.5 (minimum supported will be Solaris 2.6)

• IBM - AIX 4.3.1 (minimum supported will be 4.3.3)

• HP - UX 11.0 (32-bit)

Page 63: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

59Important NotesMSC.Marc 2001

VIII. Important Notes

MSC.Marc 2001

1. Use of the radial return plasticity formulation through PLASTICITY,2 and PLASTICITY,4 parameters is no longer supported.

2. There have been significant changes in the MSC.Marc 2000 (and subsequent versions) regarding memory management. All jobs without user subroutines or jobs with user subroutines but not accessing the Marc code internals should run fine. However, data files using old user subroutines (i.e. before this release) that access Marc internals would need changes in addressing in the vars (...) or ints (...) of the element variables if the data contains multiple dissimilar element types. Dissimilar element types are elements which have non-identical number of generalized stresses, number of layers, or number of integration points. Examples are combinations of: element 7 and 75, element 7 and 117, element 75 and 139, element 10 and 116, etc. Typical quantities requiring addressing changes are element variables which are stored at integration points or layers. Examples are stresses, strains, energies, etc.The addressing changes in the old user subroutines are not needed for:

a. analysis with only one element type

b. non-element variables (e.g. nodal quantities like displacements, reaction forces, etc. or global quantities)

This issue can easily be bypassed with use of elmvar.f subroutine (please consult MSC.Marc Volume D: User Subroutines and Special Routines) where variables in Marc database can be accessed (regardless of whether the variable to be accessed has been used in the POST option or not).

3. Displacements are not automatically written in the custom post file unless explicitly chosen. Besides the chosen quantities, if the deformation also needs to be visualized then the displacements also need to be chosen as nodal quantities.

4. For all implicit analysis with contact, the new dynamic operator (Single Step Houbolt activated by DYNAMIC,6 parameter) is recommended.

5. The startup script for Marc (run_marc or run_marc.bat) runs the job in the directory where the command is issued, even if a path to the input file is provided.Example:

run_marc -j ../otherdir/job

The job runs in the current directory. All results files are created in the current directory. No files are created in ../otherdir; only the input file is read from there.

Page 64: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Important NotesMSC.Marc 2001

60

This has an important implication for Mentat. You have to use SET DIRECTORY to move to the directory where the job is to be run. It is not possible to open a Mentat model file in another directory and start a Marc job without setting the current directory in Mentat to that directory.Filename extensions are now allowed in the command line options.Example:

run_marc -j job.dat -u usersub.f

A new option: -dir directory allows a different working directory to be specified. All created files, scratch files, and results files except the log file and status file are created in the directory specified with this option. This option is not supported through Mentat.

6. In parallel contact jobs, all nodes must be numbered sequentially.

7. When running any of the examples in the MSC.Marc New Features Guide or MSC.Marc Introductory Course, it is best to copy all the files (.proc, .mfd, .mud, .t16, .t19, etc.) in the example directory to the current, local directory. This is especially required for the examples where the procedure file uses the previously generated results file or model file to demonstrate the example.

8. Hardware Vendor Provided SolverThe hardware vendor provided solvers (solver 6) are available for parallel matrix solution. Exception: HP-UX 10.20. In a parallel run using Domain Decomposition, this is utilized automatically. This feature can also be used in a serial run in which case only the matrix solution will be performed in parallel. There are two ways to activate this feature:(1) Using the command line option -nthreads.

Example:run_marc -v no -j test -nthreads 4

will run the job test.dat using four processors for the matrix solution. This is not available from within Mentat.

(2) Using the environmental variable MARC_NUMBER_OF_THREADS. This variable is set to the number of processors to be used. Note that it needs to be defined in the same window as the one in which the job is started. If the job is started from within Mentat, the variable needs to be set before Mentat is started. If this variable is set and the -nthreads option is used, the value given by -nthreads will be used.

9. The parallel version of Marc is delivered with MPICH (public domain MPI) for most UNIX platforms. This version can be used for both single multiprocessor machines as well as for separate machines connected over a network. When running a job over the network a so-called host file should be used, see Installation and User Notes for Network version. Note: The host file should not be used in a run on a single multiprocessor machine.

Page 65: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

61Important NotesMSC.Marc 2001

On most of the platforms using MPICH, it is possible to switch to hardware vendor MPI (a Fortran compiler is required for doing the switch). Only analyses on single multiprocessor machines are supported in the case of versions using hardware vendor provided MPI. An exception to this is the 64-bit HP version which fully supports the network parallel analysis with HP-MPI.

10. Installation related:

i. If you get an error message of f77 not found or f90 not found when running a job with a user subroutine and you know there is a FORTRAN compiler on the machine, its path needs to be provided. A typical example would be the Sun platform where the f77 compiler may live in the /opt/SUNWspro/bin directory. This path must be added if you get the f77 error message.

ii. On a rare occasion, a job can fail to run on certain platforms with a message; for example, on DEC machines libUfor.so not found or on SUN machines libsunmath.so.1 not found. These files with extensions of .so are shared objects and the error message suggests that either the run time libraries are missing from the system or installed in a nonstandard place. This problem can be fixed with one of the following procedures:

a. Try relinking the version first by executing the make_marc script in the marc2001/tools directory and run the job with and without user subroutines.

b. If the problem persists, check if the .so file exists in the marc2001/lib/lib_shared directory. If it does exist, uncomment the following two lines in the run_marc script under marc2001/tools directory:

LD_LIBRARY_PATH = $DIR/../lib/lib_shared:$LD_LIBRARY_PATH

export LD_LIBRARY_PATH

If the first line already exists and points to some other directory, replace it with the new line. Run the job with and without user subroutines once again.

c. If the .so files do not exist in the marc2001/lib/lib_shared directory or if the lib_shared directory does not exist, contact your system administrator to off load the necessary run time libraries from the system CD.

11. When using the -host command line option to run a Marc job, the output will automatically be written to the directories specified in the hostfile. For instance, when running a 4 domain Marc job as follows:

run_marc -jid jobid -host hostfile -nprocd 4

the output will be written for each domain to the directories as specified in the hostfile. By default, Mentat always will write the hostfile to contain the directory specifications.

Page 66: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Important NotesMSC.Marc 2001

62

However, the following exception applies to the default described above. On Unix systems using the IBM cluster product POE or the Sun cluster product HPC, the -host command line option should never be used. Instead, the -dir command line option can be used to customize the location of the output. The user notes can be consulted for further information on how to use the -dir option.

Page 67: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

63Platform Specific NotesMSC.Marc 2001

IX. Platform Specific Notes

1. SGI Machines:

(1) When running the parallel version with (with hardware vendor provided MPI) the Arrays 3.2 version, the job may not run if the marc installation or run directory path name is very long. Normally, path names up to 256 characters are allowed in Marc, but there is a problem with the Arrays 3.2 version.Remedy: install patch 3532 from SGI or upgrade to Arrays 3.3 or later

(2) The current version of Marc requires that the blas library is installed for user subroutines to work. This library is normally installed together with the compiler, but on some versions of IRIX they did not get installed automatically. This is the case for IRIX 6.5.2, 6.5.3, and 6.5.4. For these versions, the fortran compiler runtime libraries in

ftn_eoe.sw and ftn_eoe.sw64 need to be installed.

2. HP Machines:

(1) The HP-UX 10.20 executables have been built for both PA-RISC 1.1 and PA-RISC 2.0 architecture. The architecture can be checked by running a command on the executable in the marc2001/bin directory as:

file marc. Please note that the executable will give a message of incompatibility with hardware if the PA-RISC 2.0 executable is used on a PA-RISC 1.1 architecture. The reverse, however, (i.e. PA-RISC 1.1 on PA-RISC 2.0), will work but at a slower speed. The platform can be identified with the use of the command:

/usr/bin/getconf SC_CPU_VERSION. If it returns a number greater than or equal to 532, it is a PA_RISC 2.0 system.

(2) On HP-UX 10.20, PHSS_17872 and PHSS_17225 (or newer) patches are needed by Mentat.

(3) To use the 9x15 font on HP-UX 10.20, you must run the following command prior to running Mentat:

xset -fp /usr/lib/x11/fonts/iso_8859.15/75dpi

Page 68: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

Platform Specific NotesMSC.Marc 2001

64

3. IBM-SP Machines:

MP_EUIDEVICE=css0This specifies that the tasks will use the High Performance Switch for communication.Note: A group of workstations connected by an ethernet network would use:

MP_EUIDEVICE=en?where:

? specifies the network device adapter [ 0, 1, 2, ..., n ]MP_EUILIB=ip

This specifies that the task will use "ip" protocol when sending messages to each other. Not the best performance, but always gets through the switch.

MP_EUILIB=usThis gives the best performance over the switch, but causes delays in starting jobs on older versions of PSSP.Note: A group of workstations communicating over a network would have to specify "ip" since "us" is only available for communication over the switch.

#MP_RESD=yesNo longer used for job scheduling with LoadLeveler. Required for older version of PSSP which uses the Partition Manger to schedule jobs.

MP_RMPOOL=1This specifies a "Pool" of nodes that LoadLeveler will use for scheduling the tasks if the file host.list does not exist in the directory where the job starts.

MP_HOSTFILE="NULL"This specifies the file that contains the list of nodes to schedule the tasks on will have the default name "host.list" if it exist.

#MP_HOSTFILE=$DIR/tools/host.listAllows the user to specify any file name and its location, instead of host.list in the directory where the job starts.

MP_INFOLEVEL=0Specifies the amount of information that LoadLeveler/POE gives the user about his job. The zero specifies "none" and the user would not know what happened if his job failed. Use a value of 2 (default).

4. IBM Machines:

The OpenGL version of Mentat may not operate properly on some IBM platforms. The runtime libraries patch 4.3.3.25 is required.

Page 69: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

65Platform Specific NotesMSC.Marc 2001

5. CRAY Machines:

(1) Due to a linker defect in the OS for the CRAY J-90 version, there may be a failure in running a job with a user subroutine. In such cases, the following command must be issued:

setenv TARGET cray-jse

(2) MSC.Marc licensing for CRAY machines requires the use of remote license server from other UNIX platforms.

(3) There is a problem related to sed in some CRAY machines which prevents the installation script to function properly. Specifically, the u option under the main menu, which is used to update the directory path of Marc installation, in case of directory changes or accessing from other machine via mounting. In such a case, manual editing of the run_marc script is necessary in order to update the path.

(4) The post file support on CRAY is as follows:

(i) Only post revision 9 or later is supported.

(ii) Only IEEE 32 post file reading and writing is supported.

(iii) Hypermesh, SDRC, and Unigraphics files are not supported.

(iv) The following new options are supported: TRACK, FLOW LINES, and AXITO3D.

(v) Continuous post file writing during a restarted analysis is supported.

(vi) The following initial options are supported: INITIAL STATE, CHANGE STATE, INITIAL PLASTIC STRAIN, INITIAL DISP, INITIAL VEL, INITIAL TEMP, POINT TEMP, INITIAL PORE PRESSURE, CHANGE PORE PRESSURE, and PRE STATE.

Page 70: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

SecurityMSC.Marc 2001

66

X. Security

The security layout for Marc and Mentat 2001 has been changed to align with other MSC products. Prior versions of Marc and Mentat used a directory named security to store the license file (license.dat), the license manager (lmgrd.marc) and the vendor daemon (MSC). The 2001 release stores the license manager (lmgrd) and the vendor daemon in a directory named flexlm for Windows NT, and for UNIX platforms it is flexlm/<platform>, where <platform> is aix, alpha (Tru64), irix, linux, solaris, or sun. The default location for the license file is flexlm/licenses.

The Marc and Mentat 2001 release uses new security libraries. Any Marc or Mentat 2000 version license will not work with the 2001 version. You must obtain a new license to be able to run the 2001 release.

To continue running your pre-2001 versions of Marc and Mentat with the new licenses, you must update the FLEXDIR variable in the marc2000/tools/run_marc (include.bat for Windows NT) and mentat2000/bin/mentat scripts to point to the new license directory flexlm/licenses. In addition, the script commands that automatically start the license manager on UNIX need to be changed as follows:

if [ -f $FLEXDIR/../<platform>/rc.lmgrd ] ; then. $FLEXDIR/../<platform>/rc.lmgrdfi

LAPI security has been implemented in the products. The capabilities that require a license are given below with feature names as required in the license file.

i. MARC one token required to run one single processor job or one instance of a multiple processor (parallel) job.

ii. MARCN one token required per processor in a parallel run (for example, a four processor job requires one MARC token and four MARCN tokens).

iii. Forge-M2D one token required for each run requiring automatic 2-D remeshing feature in MSC.Marc.

iv. MENTAT one token required for each instance of Mentat.

v. HEXMESH one token required for each instance of Hexahedral mesher.

vi. ACIS one token required for each instance of ACIS when working (import/export) with ACIS based models.

vii. ITI-IGES one token required for each instance of IGES file translator when working (import/export) with PDELIB based models.

viii. ITI-VDAFS one token required for each instance of VDAFS file translator when working (import/export) with PDELIB based models.

Page 71: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

67SecurityMSC.Marc 2001

ix. ITI-AUTOCAD one token required for each instance of DXF file translator when working (import/export) with PDELIB based models.

x. V_CMOLD one token required for each instance of CMOLD when working (import/export) with CMOLD based models.

The following types of licenses are available with the products:

i. Nodelocked, countedii. Nodelocked, uncounted

iii. Floating (concurrent)iv. Campusv. Demo

Please refer to the installation guide for more information on security or contact your local MSC representative.

Page 72: MSC.Marc 2001 and MSC.Marc Mentat 2001 · MSC.Marc 2001 and MSC.Marc Mentat 2001 Version 2001 Release Notes. ... HP/HP-UX, Linux, and on Intel ... including the matrix

SecurityMSC.Marc 2001

68


Recommended