HyperWorks Release Notes€¦ · HyperWorks Desktop 2017.2.2 hotfix contains enhancements and bug...

HyperWorks Desktop 2017.2.2 Release Notes 1

Proprietary Information of Altair Engineering

HyperWorks Desktop

2017.2.2 Release Notes

Introduction

HyperWorks Desktop 2017.2.2 hotfix contains enhancements and bug fixes for HyperMesh, HyperView, HyperCrash, HyperForm, MotionView, Motion Auto, HyperStudy, NVH Director and

HyperWorks Verification and Validation Harness (HVVH). The details are documented below.

Note: HyperWorks Desktop2017.2.2_hotfix is a cumulative release. It should be installed on top of HyperWorks 2017.2 release.

HyperMesh

New Features and Enhancements

Engineering Solutions: Aerospace Profile

• Create and Review Zero Length Elements

This tool creates zero length elements (CELAS*, CGAP, CMASS* and CBUSH) between

disconnected nodes within a given tolerance or between selected congruent nodes by

detaching them.

With this tool, you can:

• Identify coincident nodes

• Create 0D elements between disconnected nodes within tolerance

• Create 0D elements between connected nodes by detaching the nodes

picked

• Import, Export of Data using the Entity Editor

This function can import, append or export CSV files from EE table data for the

following cards – PCOMP, PCOMPG, TABLEM/S/D



This helps you update table entries in EE without manual typing.

• Ability to Transform Systems using the Transformation Tool

The Transformation tool can be used to transform system in few different ways.

• When components/ elements are transformed, systems are also transformed if the

system was created using nodes (origin node, x direction node, y direction node)

from those elements/components.

If some of the anchor nodes are not associated with any of the transformed

element, the association is broken and a new system is created while transforming

using axis definition instead of node definitions.



• If the system is not associated with elemental nodes which are being transformed,

then you can only select “system” and it will transform as an axis system.

• Creating Linear Gap Elements Automatically

This tool can be accessed via Aerospace > Connections > Linear Gaps.

This will create old Nastran linear gaps that contains MPC, SPC, SPOINTS and

SUPPORT and allow the user to set up the corrispondant parameters (CDITER, CDCPH and CDPRT) to control this type of analysis.

Example: The following cards will be created.

• SPOINT 55 155 ( two spoints 55, 155)

• SUPORT 55 0 ( support at one spoint)

• SPC 101106 155 0 .05 ( spc at the other spoint with initial gap of 0.05, with

DOF=0)



• $ SID G1 C1 A1 G2 C2 A2 ( MPC for linear gap. In DOF =2. for

Nastarn)

MPC 101106 3 2 1.0 2 2 -1.0

$ G3 C3 A3 G4 C4 A4

55 0 1.0 155 0 -1.0

This tool can also convert other types of 1D connector elements (CGAP, CBUSH,

CELAS) to linear gap (MPC /SUPORT, SPC, SPOINT).

• Visualize CBAR Beams on the Centroid instead of the Shear Center Even for

Non-bi Symmetric Sections

In previous releases, HyperMesh exposed a global option called “1D at Centroid”

(available in the Options panel; keyboard shortcut “o”). This option drives the display

of beam section 3D representation either at its Centroid (“on”) or its Shear Center

(“off”).

In the image below, you can see 3 straight lines meshed with 4 CBAR and 4 CBEAM

each. A T2, L, and Hat section was assigned, respectively. “1D at Centroid” is “on” so

each GRID matches with a section’s Centroid.



If “1D at Centroid” is switched “off”, HyperMesh represent the 3D detailed view with

GRID at section’s shear center.

However, when using a CBAR element, its elastic axis, gravity axis, and shear center

all coincide for the solver. In the example, sections for which shear center is offset

from centroid were used.

In order to reflect what the solver actually considers, HyperMesh now displays the

section based on element formulation (always at centroid for CBAR)

• Import and Check Ground Check Forces

This tool, available in Nastran profile only, can be accessed via Aerospace > Results >

GroundCheck Forces



Select an f06 file where the GroundCheck forces have been asked as well as output

(e.g. GROUNDCHECK(SET=(G,N), DATAREC=YES)=YES)

Once the file has been selected, the tool parses it and recognizes for which set the output has been required. You can select these sets and the relevant results will be available in the “Select Result Cases” box.

You can select one of the results and then one result type to contour (a vector

visualization is as well available for both translational and rotational DOFs).

In the example below, Mode G-Set, direction 6 – Translation Magnitude has been

selected. Matrix Browser technology is used in the background to apply the contour.

You can create a HWASCII file and use it in a HyperView session.



In this case each set will be treated as load Case, direction as simulation (mode) and

results nested in the vector root.

The checkbox “Use Failed nodes only” implies if results will be created for failed nodes

only or for all database nodes in the database.

• Fringe Post-processing Using Different Volume Averaging Methods

This tool can be accessed via Aerospace > Results > Averaged Post Processing;

The tool enables you to evaluate, for the selected elements, the averaged value of the

selected result type (component, layer and system). Three different options are

available:

• None: no ponderation value will be used

• Volume: the exact volume of the element will be taken as ponderation value

• Area: the pondered value will be the length for 1D elements, the area for 2D

elements and the volume for 3D elements

You can select more than one subcase.



Two options are available for the contour selection:

• Set Up on Active Window: Add, Remove or Duplicate Rows in the available UI. By

Adding a row you can set up the whole configuration of Data Type, Component, etc.

In addition to the pondering value, you can set up a min/max filtered value which

will tell the tool the range of result values that will be extracted.

This result configuration can be saved (and afterwards loaded) via CSV file data

format exchange using Save and Load Config. buttons respectively.



• Select from Session: You can select the available contoured results from the

HyperView client in the session (Type/Component/Layer/System entries are

therefore frozen). Set up the pondering option and as well the min/max value as

contour filter.

As outcome, a new UI is displayed where all selected combinations can be

accessed.

Results can be saved in a dedicated folder. In addition, use the option “use Matrix

Browser” to generate a table for each combination which can be processed using

the Matrix Tool.



• Enabling Ability to Control Nodal Coordinate Precision (rounding off)

This tool can be accessed via Aerospace > Nodes > Precision Control.

This tool will round off the node coordinates (multiple nodes) to the desired precision

and update the HM data base.

Before update

After update

• CBUSH Node to Node Connector in Aerospace Fastener Tool

This tool will create Node to Node CBUSH elements at the connector locations provided

either point/node or line locations. It is mandatory that users to make sure the nodes

are opposite each other when two plates are connected (congruent meshes). If the

meshes are not congruent, it is advisable to use RBE3-CBUSH-RBE3 or CFAST

connector type from the same dialog.

Note: It is required to provide Rivet diameter manually for this tool to work, or have

axillary lines to represent the diameter.

• Manually Synchronizing System between HyperMesh and HyperView

This tool can be accessed via Aerospace > Systems > Sync HM-HV;

This enables you to have the same system defined in both HyperMesh and HyperView clients. If a system is defined in HyperView session not present in HyperMesh, the missing system will be created in the session.

This tool currently supports Rectangular and Cylindrical systems but not Spherical ones.

• Aircraft Transformation Tool

This tool can be accessed via Aerospace > Assembly > Aircraft Transformation Tool.



This tool allows to apply a full transformation (translation+rotation) to the following

entities:

• Elements

• Nodes

• Components

• Systems

Four different methods are available to input the transformation matrix:

• By Config File: in this case a CSV structured needs to be imported, as in the

example below

Once the file has been loaded, you can set up Reference and Destination point.



• By Direct Input: Directly input the transformation matrix in the given fields

• By System: Select reference and destination system from those available in the HM

database. The found transformation matrix will be stored as CSV file.

• By three nodes: This function re-applies the Position tool where three nodes as

reference and three nodes as destination are used for the transformation

• Also in this case, you can save the transformation matrix as a CSV file.

In addition, when the Component is selected, the tool allows you to transform the

found associated systems.

• Conversion of Elemental Pressure to Nodal forces on the Same Model

This tool converts pressure load to be applied on shell elements to equivalent forces on

the corner nodes of the selected shell elements. TRIA3 and QUAD4 elements are

supported. This tool is available for Nastran and OptiStruct solver profiles. Select the

shell elements of first order elements from “entities” in the Pressure To Force dialogue

available at Aerospace Loads/BCs Pressure To Forces.



Input the uniform “pressure” that needs be distributed as equivalent forces at the

corner nodes of the selected elements. Pick the Load collector in which the forces are

to be stored. Enter a new name for load collector or pick one of the existing load

collectors or current load collector.

• Improvement in Set Browser for Importing Patran Session Files

HyperMesh Set Browser capability of importing Patran Session (*.ses) file has been

improved as follow:

• Groups with RBEs listed as MPC entry in Patran used to generate an error during

import which has been resolved.

• The original Patran group (containing eventually both elements and nodes) is now

created and includes both nodal and elemental sets.

• Adding a Function to Export Sets in a Custom File Format

This tool can be accessed via Aerospace > Sets > Export in Custom Format.

Currently two types of export methods are available:

• PSN8 (Legacy Airbus)



• PSN29 (Legacy Airbus)

• Finding and Displaying Sets Containing Nodes/Elements

This tool can be accessed via Aerospace > Sets > Set Review

It enables you to select either elements or nodes from the model and find in which sets these are already collected.

Once the sets are found, their names are displayed in the UI and can be selected and the entities belonging to the selection will be isolated (shown) in the HyperMesh graphic area.

• RBE2 Filter

This tool can be accessed via Aerospace > Loads/BCs > RBE2 Filter.

It enables you to implement a special RBE2 connection with assigned DOFs.

After selecting two nodes, Node 1 (A) and node 2 (B), the tool will:

• Generate two nodes, C and D in between node A and node B (node C and D will

have the same coordinates);

• Create RBE2 connecting node C as Master and Node A, B and D as slave with DOF

123;

• Create RBE2 connection node D as Master and node A and B as slave with DOF 456;

• Create SPC with clamped DOF456 at node C;



In addition to this:

• If Multiple nodes selection option is checked you pick more than one node (e.g. in

Node 1 selection panel), the tool will generate a RBE2 connecting the selected

nodes to a master node. The position of the master node will be automatically

calculated by HyperMesh as the COG of the selection and this node will be taken as

Node A for the further connection (same approach for Node 2 selection);

• You can choose the numbering scheme for nodes and RBE2s which will be created;

• You can choose the name of components and load collector where the newly

created RBE2 and SPC will be landing respectively. If this option is not used, the

tool will create these entities in the current collectors.

This tool is available for Nastran and OptiStruct solver profiles.

• Result Explorer : Ability to Store all the Results in a Single File

In the previous release of HW results explorer exports the default load case output to

separate individual files for each load case. New option is now added to export all the load case into a single csv file or text file using the save-all option button.



Using Save All option a single file is created for all the load cases selected.

• Enhancement to Create Material System for Solid Elements (HEXA and PENTA) with Elemental Angle Theta (like CQUAD shell elements)

There are two ways now in HW to assign material system orientation for solid elements for OS solver.

• Material system can be assigned to PCOMPLS property and with C8 option ON and

INT8 option set to ASTN. All elements using that property will use this system for

their material orientation. The software will project the material system so that Z

axis coincides with the elemental Z axis (face 1 to face 6 for Hex elements

–stacking direction) and material x axis is projected on the local xy plane of the



elemental system. Please also make sure element CORDM card also points to

user defined MCID.

• The new element angle option for Hexa solid (Theta) is very useful if the material

system is changing from element to element. The material system x axis will be rotated about local elemental Z axis (stacking direction face 1 to face 6) by the

angle Theta in the xy plane. Material z axis is same as the elemental Z axis.

Red is the material X axis, Yellow is the elemental x axis. Blue – Z axis same for

elemental and material system.

• Field Mapping Support for 2nd Order Elements

Field mapping for second order elements is now available. The shape function of first

order elements will be used for these elements to map the values from the source.

• Field Mapping Function for HTC (thermal analysis)

The Field entity is enhanced to map the Heat transfer coefficients and bulk

temperature from CFD analysis or from a CSV file to structural mesh. As of now this mapping option is available for OptiStruct profile. You can use either

CSV file or Result log file from AccuSolve as source. Expected CSV file format:



If source is result log file from AccuSolve then you need to create a field with source

option: “results”.

During field realization, for elements, “convection” as “Field type” is introduced.

Choose appropriate Interpolation method, normal distance and Tolerance and then pick the Sub case and simulation from which the Heat transfer coefficients and Bulk temperature to be mapped. Select the Surface Film Coefficient from data type to map

both Heat transfer coefficient and bulk temperature (no need to pick Temperature). “Apply” will map the data to the structural mesh selected.

This mapping creates following solver entities for OS profile:

PCONV: Heat Transfer coefficient calculated during mapping process will be stored in this card- attribute:H1.

CHBDYE: Surface elements over target or base elements. CONV: Refers PCONV ID and arbitrary Node number (TA1) created for bulk

temperature SPC: An arbitrary node is created and SPC without any DOF is attached to this node.



This is to store bulk temperature calculated during mapping process.

• Dissimilar Shell Mesh Sewing Tool Using Special RBE3 (stuck node)

Stuck node RBE3 connection are created between discontinuous meshes. A new option has been added to the existing sewing tool for creating stuck node connection

(double RBE3) to connect master nodes and slave nodes of two disconnected components. First select the master nodes (from a coarse mesh) and then select

slave nodes from (fine mesh) to sew. Element to element sewing option is still retained as in the previous releases.

General

• Invoke Time Crash

We have added a setup related to HyperMesh crashes during invoke.

• The subsequent invoke after the crash will automatically bundle setting files like

hmmenu.set, hmsettings.tcl and command.tcl file in a zip file and also automatically set an environment variable ("HM_DONOT_READ_SETTING_FILES")

to avoid reading them during the subsequent invoke. User can also set this environment variable manually even if they don’t run in to invoke crash knowing that it will skip reading the setting files during invoke.

• The subsequent launch after the invoke crash will notify user about the crash via

pop up message with additional details.

NOTE: Once the environment variable is set, user must know that they will lose the

information that otherwise will be stored in the settings files. Information like the

user interface layout (tab locations, command window, panel location, toolbars,

etc.), keyboard preferences, import/export settings, recent files, and other various

settings will not be preserved. User can always go back and remove the

environment variable.



CAD

• Add support for CATIA V5-6R2017 (R27)

• SolidWorks 2017 on Linux

Resolved Issues

• Changing center of rotation (ctrl+left mouse button) was mistakenly picking entities in the graphics area. This issue was only observed on Linux platforms.

• In a case of insufficient write access in user start-up directory, second and subsequent HyperWorks session was not able to come up.

• Export of CQUAD elements with STL export.

• Some isolated crashes associated with HyperMesh models with superelements. • Random errors while expanding browser and while exiting HyperMesh.

• Component with numerical strings as name showing wrong property reference. • Reorder of assemblies move all components to root assembly level. • ID Manager failed to release ID associated with an entity even when the entity is deleted.

• Crash related to Autopitch creation in large models. • There are some instances reported where HyperMesh models have failed to open with

“Connectors entity was improperly created” message. • Resolved issue related to stiffness mapping in Aerospace Fastener Tool w.r.t. to stiffness

mapping for Huth formulation when multiple layers connected.

HyperView


Aerospace Tools from Aerospace User Profile

• Fringe Post-processing using Different Volume Averaging Methods

This tool can be accessed via Aerospace > Report > Averaged Post Processing;

Please, refer to the description given in the HyperMesh relevant session.

• Manually Synchronizing System between HyperView and HyperMesh

This tool can be accessed via Aerospace > Systems > Sync HyperView-HyperMesh;

HyperView use case:

• A session with a model in HM and same model with results in one or more HV

window

• In one HV client, you create one or more systems

• You launch the tool and select which system(s) will be created in the HM client

This tool currently supports Rectangular and Cylindrical systems but not Spherical ones.

Resolved Issues

• Issue reading d3eigv files created by LS-DYNA MPP job. • Application stops working when attempting to copy a non-active window in the Session

Browser.

• Curves from Build Plots panel are not plotted in specified window.



OptiStruct Interface


• CONTPRM, NONTIED, NO to Generation of non-tied.fem file for grids outside of search

distance. • You can provide positive values in B1 and B2 field in Type SN of MATFAT card to allow

direct input of the slops of SN curves.

• New response type GPSTRESS in DRESP1 card. • New response ATTB to support CORNER stress/strain in DRESP1 card.

• Maximum Bead width control for topography optimization. • New option NPRT to activate repeat laminate in PCOMP, PCOMPG and STACK. • Self-contact, in CONTACT card MSID can be left as blank or same ID of SSID can be

referred. • Damage evaluation and output based on the user defined table data through new table

card TABLEMD. • New option TSTIME to indicate Total/Subcase time switch in TLOAD1/2 card • ALLSET option in ACMODL to control the coupling grids in SSET and FSET

• New PARAM option GLOBEXPT. • New option NOTIED in CONTPRM card to generate ascii file for nodes not detected in Tied

contact. • New PARAM option DDMNGRPS to combine LDM and DDM run. • New option AUTO in RIGID I/O card.

• ESE I/O card enhanced to output Max plastic strain energy output. • DSIZE card enhanced to support PMDIS field to support Discrete design variables

• New option RESVEC6 in SYSSETTING card for six additional global RESVECs for Superelement generation with Component Mode Synthesis.

• New cards FATMCRV and TABLEXN has been added. • Support of sine sweep fatigue analysis. • DOPTPRM, APPROX option is added with HIGH, MEDIUM, LOW.

• New PARAM option AMSE4EFM,NO/YES. • USEMAT option in GE field to Calculate GE for PCOMP based on material GE.

• Option to switch SN curve based on amplitude/range (A/R) in MATFAT card.

Resolved Issue

• Damage models in RDMGMDL continuation line in FATPARM card is resolved to allow 4 fields.

• Some of the Includes are skipped while reading .fem file in LINUX platform. • CORD2R details are modified on I/O, provided solver option in export browser as follows

“Export CORD2R in long format”. • HyperBeam sections are not created on import with FE overwrite option. • Warning related to generic beam section comments not recognized during import.

Nastran Interface

Resolved Issues

• CORD2R details are modified on I/O, provided solver option in export browser as follows “Export CORD2R in long format”.



• HyperBeam sections are not created on import with FE overwrite option. • Incorrect attribute mapping for control card LINE.

• Warning related to generic beam section comments not recognized during import.

Abaqus Interface

Resolved Issues

• Error while exporting model using “Export Entities with Quotes”option.

Ls-Dyna Interface

Resolved Issues

• Improvements to support *ELEMENT_SHELL_COMPOSITE_LONG,

*ELEMENT_SHELL_BETA_COMPOSITE_LONG and *ELEMENT_SHELL_MCID_COMPOSITE_LONG

• Improvements in group entity IDs offset management influenced by the parameter

IDROFF in *INCLUDE_TRANSFORM. • Creation logic of Plot entity is improved especially for models having include files, where

in some cases, undefined curves were created. • Issue fixed when importing a model having

*BOUNDARY_PRESCRIBED_MOTION_(OPTION) with scale factor SF not defined or blank.

RADIOSS Interface

Resolved Issues

• Issue fixed in handling of porous surfaces in /MONVOL/FVMBAG1. • Support of engine card /DT/FVMBAG/1 is corrected. • New attribute Idege added in /INTER/TYPE19 as per RADIOSS 2017.2.2 release.

• Issue fixed for penetration check of /INTER/TYPE7 when Iremgap=2. • Added Ishell=24 into /PROP/TYPE16 as per RADIOSS version 2017.2.3.

• Added new parameter PSH and P0 in /MAT/LAW5 as per RADIOSS version 2017.2.3. • Added fct_ID31 and H=4;5 in /PROP/SPR_PUL as per RADIOSS version 2017.2.3. • Added new parameters Tswitch and kmesh as per RADIOSS version 2017.2.3.

PamCrash Interface

Resolved Issues

• Improvements in handling Hcont and ITPRT of contacts (CNTAC) with appropriate

messages as per solver versions.

• Export issue fixed when GES data has mixed range and list under GROUP keyword.

• MASS keyword is now listed in solver browser when applied through node GES.

• FE-Overwrite issues resolved with GES data across keywords (example: BAGIN & PREFA).



HyperCrash- LS-Dyna Interface

Resolved Issues

• Improvement of mass calculation accuracy for LS-Dyna profile R7.0.

• Improvements in contact treatment after replace by pairing operation. • Fix issue when moving *PART_INERTIA – coordinates of NODEID are now updated.

• Allow to select moving box into Move panel. • Fixed an issue to retrieve global parameter in the model when defined in an include.

HyperCrash- RADIOSS Interface

Resolved Issues

• Deleting parts of a dummy will now not delete the whole dummy tree. A variable in the

preferences is set-up to control this behavior and retrieve the previous one • Dummy pre-simulation with puppet method – issue fix for exporting pre-simulation deck

in case multiple dummies are in the model • Dummy pre-simulation with puppet method – new method implemented to ensure the

export of the dummy in the correct starting position.

• Issue fix by importing connections from csv file • Issue fix when importing material from database – now attached failure or thermal cards

are imported as well • Issue fix in ModelChecker when /PROP/TSHELL is used in the model • Support of engine card /DT/FVMBAG/1 is corrected

• Parameter FPenmax in /INTER/TYPE7 is now exposed without condition on Igap value • Issue fixed for penetration check of /INTER/TYPE7 when Iremgap=2

Keywords Updates

• Add Ishell=24 into /PROP/TYPE16 as per RADIOSS version 2017.2.3 • Add new parameter PSH and P0 in /MAT/LAW5 as per RADIOSS version 2017.2.3

• Add fct_ID31 and H=4;5 in /PROP/SPR_PUL as per RADIOSS version 2017.2.3 • Add new parameters Tswitch and kmesh as per RADIOSS version 2017.2.3

• New parameter Idege added in /INTER/TYPE19 as per RADIOSS version 2017.2.2 • Add new paramerer Icap=2 in /MAT/LAW24 as per RADIOSS version 2017.2.2 • Add new material /MAT/LAW93 as per RADIOSS version 2017.2.2

• Add new material /MAT/LAW94 as per RADIOSS version 2017.2.2 • Add new keyword /PERTURB/FAIL/BIQUAD as per RADIOSS version 2017.2.2

• Updates in /FAIL/BIQUAD as per RADIOSS version 2017.2.2 • Add /SENSOR/WORK as per RADIOSS version 2017.2

HyperForm – Incremental RADIOSS

New Enhancements

• Support for modeling of Hot Metal Gas forming process

• Tube bending model setup updated for fast run time

• Die compensation macro updated to work with models in the session

• Forming Limit Curve is now supported as constraints in optimization problem setup



Resolved Issues

• Supported multiple component selection for distance calculation between parts.

HyperForm – One Step RADIOSS

New Enhancements

• Results Initializer allows to attach results as Include files.

Resolved Issues

• Batch Results Initializer to work with files in folder that has names with special character

“~”

MotionView


• It is now possible to select or deactivate entities along with their dependents through the

Project Browser. Activating entities along with the entities that they refer to is also available.

• Copy functionality is now available in the Browser context menu. • MotionView now imports GRAPHICS statement of type EXTERNAL in the Adams ADM as

graphic entity of type CADGraphic

• With a model built using the Full Vehicle with Advanced Driver, Task Wizard would now bring up the Events dialog.

• It is now possible to control the mesh coarseness on individual graphic entity for contact simulations. A slider bar is now available in the Properties tab of the CADGraphic.

• The Display Fidelity slider bar in the Visualization tab is no longer available.

Resolved Issues

• An issue with Cut and Paste of Auto-Entities is now resolved. Earlier, the auto entity

definition would be lost during the paste operation • MotionView would fail to pick to a collector with “Allow CAD feature recognition” as ON on

certain occasions. This issue has been fixed.

• CAD Import using HyperMesh failed to launch HyperMesh in the interactive mode when certain options were changed. This issue has been resolved.

• An issue with increased time for importing Analyses as more analyses are imported has been fixed.

• An issue with importing a CADGraphic which contains backslash in the component name

has been fixed. • A misleading error message regarding Invalid argument name while saving model with

contacts that involves body pair has been fixed.



Motion Auto


• Leaf Spring Builder: Canvas Adds View Controls

You can now pan, zoom, and fit the view of the leaf shapes on the canvas in the Leaf

Spring Builder. In addition, you can save hard copies of the leaf shapes to a variety of

graphic file formats including Joint Photographic Experts Group (.jpeg), portable network

graphics (.png), and portable document format (.pdf). The new view controls are shown

in the figure below.

• Leaf Spring Builder: F1 Launches Help Pages

Now when you click F1 with the Leaf Spring Builder displayed, the Leaf Spring Builder

home page is displayed in your browser.

Resolved Issues

• Leaf Spring Builder: Entering Y bolt hole location on master leaf creates an

ill-formed spring.

Previously when you entered a Y location for the master leaf bolt hole the spring eyes and

shackle were offset from master leaf in the Y direction giving an ill-formed spring model.



While the field for the Y-location is still present in the UI, entering a Y location has no

effect: the Leaf Spring Builder creates the spring in the X-Z plane.

• Leaf Spring Builder: Clip Details are not displayed after opening a leaf property

file.

Previously if you selected clip details from the list of leaf spring components in the builder,

then opened a leaf spring property file the clip data was not displayed in the user

interface. However, if you selected any other leaf spring component then reselected the

clip details the clip data was properly displayed. Now, the Leaf Spring Builder properly

updates the clip details when you open a leaf spring property file.

• Leaf Spring Builder: Outputs poorly formed *.mdl file.

Previously when you built a leaf spring, the Leaf Spring Builder output wrote the model

definition file (.mdl) with graphic system definitions improperly nested within the leaf

spring system definition. Most users were unaffected because the nesting does not

prevent importing the leaf spring system into a model. However, the nesting does prevent

use of the leaf spring system as a wizard selection for users creating their own library and

assembly wizard. The Leaf Spring Builder now writes the graphics system definitions in

separate blocks from the leaf spring system definition hence resolving the issue.

• Leaf Spring Builder: Loading example leaf spring property files gives an error.

When you opened an example leaf spring property file the Leaf Spring Builder reported

that the build directory was incorrect as shown below. The error occurred because the

build directory was set to the directory containing the leaf property file and that directory

was not writable because it was within the HyperWorks installation directory. To resolve



the issue the builder now sets the build directory by default to the user’s desktop folder on

Windows and user’s home directory on Linux.

• Leaf Spring Builder: Springs with two slipper ends fail in force-deflection test.

When you built a leaf spring with two slipper ends and tested the spring to generate a

force-deflection curve the test failed because the spring’s longitudinal motion was not

constrained by the slipper end or the test rig. Now when testing a leaf spring with two

slipper ends, the leaf spring builder constrains the longitudinal motion of the spring at the

test rig with a spherical revolute joint between test rig jack and the spring seat.

• Leaf Spring Builder: Slipper end side contacts act on incorrect leaf body.

When you built a leaf spring with slipper ends with side contacts to control lateral

movement of the leaf spring relative to the slipper, the side contacts sometimes act on

the wrong leaf body. The problem occurs when the junction between two bodies in a leaf

is close to the line passing through the slipper pad and pin centers (see the figure below).

The logic selecting the leaf bodies for side contact is updated to resolve the issue.

However, should you encounter a similar issue, you can increase or decrease the number

of beams to shift the junction away from the line.



• Leaf Spring Builder: Rear spring eye inner radius not used

Previously if you built a spring using a bushing for the rear spring eye, then the front

spring eye inner radius was used to size the rear eye graphic or if there was no front

spring eye (e.g. the front used a slipper end) then the .mdl file generated had errors as

found by a check model as shown below. Now the rear eye inner radius sizes the rear

bushing graphics

• Leaf Spring Builder: C-Clip and Pin-Clip diagrams are incorrect.

Previously the diagrams in the leaf spring builder for C-Clips and Pin-Clips incorrectly

showed outside dimensions for height and width. The diagrams are updated to correctly

show that the height and width are inside dimensions as shown below.

• Leaf Spring Builder: Renaming a contact gives an application error.

In previous releases in the Leaf Spring Builder if you selected a contact and tried to

rename it an application error occurred. The issue is resolved.



• Leaf Spring Builder: Log file messages improved.

The messages output by the Leaf Spring Builder to the log file are improved: spelling and

grammar errors were corrected.

• Leaf Spring Builder: Slippers ends incorrect contact properties.

In some cases springs employing one or more slipper ends were built with incorrect

contact properties. As a consequence preload and/or force-deflection analyses of the

spring would fail in MotionSolve because of zero exponent in a set of contact properties

with this error:

ERROR Force_Contact/306001 exponent shall not be smaller or equal 0.

ERROR: Error encountered in model data!

ERROR: Error encountered in model preprocessing!

The contact properties are now output correctly.

• Leaf Spring Builder: Slipper ends contacts not written to .mdl file.

In some cases for springs with slipper ends the contact forces were not saved to the .mdl

file by the Leaf Spring Builder. Hence the spring would not transmit load to the chassis

and analyses using the spring would fail. The issue is corrected.

• Leaf Spring Builder: Renaming slipper end contacts causes errors

Previously if you built a spring with one or more slipper ends and renamed contact

properties referenced by one or more slipper ends, then saving the leaf spring property

file failed with errors. The failure no longer occurs.

• Leaf Spring Builder: Shackle bushing option not saved

Previously if you checked the box to use a bushing to attach the shackle to the vehicle

frame and saved the leaf spring property file, then when you reopened the file in the Leaf

Spring Builder and selected the shackle, the box to use a bushing was unchecked. The

problem is corrected.

• Leaf Spring Builder: Test Directory default path does not exist

Previously the Leaf Spring Builder set the test directory to the user’s desktop directory by

default. However, when a user’s account did not have a desktop directory an error to

occur. Now if a user’s account does not have a desktop directory, the Leaf Spring Builder

leaves the test directory blank.

• Leaf Spring Builder: Example leaf springs should build without errors

Previously some of the example leaf spring models accessed via the “Examples” menu

in the Leaf Spring Builder failed to build. Typically, the failure occurred when applying

preload to the spring. The models are updated to eliminate the failures.



• Leaf Spring Builder: Some points created at wrong locations in MDL

For leaf spring with slipper ends after applying preload the spring system .mdl file was

output with the side contact points for the slipper ends at the incorrect locations. The side

contact points are now output at the correct locations.

• Leaf Spring Builder: Rebound leafs cause failures

Springs employing two or more rebound leafs (leafs located above the master leaf) failed

to build giving errors as in the Leaf Spring Builder log file as shown below. The errors are

corrected.

leafTypes:reboundLeaf:createMDLMotion :: Error found , Terminating Process

leafTypes:reboundLeaf:createMDLJoint :: Error found , Terminating Process leafManager:leafManager:writeLeafMdl:writeLeafSystems :: Error Found Terminating

process

• Using a flexible chassis body for full vehicle models with Advanced Driver gives

errors

Previously when you built a full vehicle model using the assembly wizard, the chassis or

body (sys_body.body) was passed to the Altair Driver system as an attachment. Altair

Driver referenced the center of mass (cm) marker of sys_body.body to measure the

position, velocity and acceleration of the vehicle. However, if you changed the

sys_body.body from rigid to flexible then when simulating in MotionSolve gave an error

because the cm marker did not exist. Now Altair Driver attaches to a body in the

instrumentation system (sys_instrumentation) so when the chassis or body is flexible no

error occurs.

• autoTIre: Selecting a tire property file gives an error about the road property

file

Previously when you selected a tire property file an error was output indicating the road

property file was incompatible, even when the road property file was compatible with the

tire property file. The error output is shown below. Now when you pick a tire property file

if the road file is compatible no error is generated. Further, the file selector for road

property files is enhanced to filter road property files by extension that are compatible

with the selected tire property file.



• Check model gives errors for full vehicle models with an IC Engine Friction

Clutch

When you assembled a full vehicle model using the advanced driver and an IC Engine

Friction Clutch powertrain executing a check model gave errors about the engine speed

and gear ratio curve as shown in the figure below. The powertrain and driver systems are

updated to eliminate these errors.

• Truck Library: Child systems do not use parent system attachments

Dampers, bump stops and other systems that typically attach to the chassis or truck

frame and are children of the suspension systems, previously attached directly to the

chassis instead of to the chassis attachment in their parent suspension systems. For

models using one rigid body to represent the chassis, there is no issue. However, when

multiple rigid bodies are used to represent the chassis problems arise because changing

the body the parent suspension system attaches to does not change child system’s

attachments. The truck library is updated so that the children systems use the chassis

attachment of their parent system.

• Full vehicle events fails to execute from MotionView "Run" panel

When a full vehicle model was assembled using the advanced driver and an

“AltairDriveFile” event was added, hitting the “Run” button from the run panel, would

cause MotionSolve to report a missing file error. The issue is corrected.

NVH Director


FRF to CDS

• Enhancement to support creation of CDS from transfer functions in PUNCH file format.

• Provision to review and skip the channels used for CDS creation.

NOTE: Use the solver hotfix in 2017.2.3 to create CDS.

Resolved Issues

• Job Manager – Issues of automatic closing of job manager on creating new jobs. • Transfer Path Analysis – Issue in plotting structural responses in different direction

components for One Step TPA results.



HyperWorks Verification and Validation Harness (HVVH)


HVVH is a new framework developed for Verification, Validation of HyperWorks products. This will help end users to quickly evaluate the software quality, performance, reliability, scalability, robustness and gain more confidence in HyperWorks products. This also helps them to migrate

to newer HW versions faster. Some new features are added in the current version along with

resolution of reported issues.

Note: Additional help related to user and reference guides along with demos and tutorials

updates is available at the following location:

https://connect.altair.com/CP/downloads.html

New workflow verification and validation

• Auto compare

New feature that will capture many work flow and help in quickly identifying the issues with the model is added. This will help engineers to capture many processes and verify

the same as they migrate from version to different version or readiness of model for solver run or compare quality metrics. Supported for all FE model readers in HyperMesh.

• Compare model data- user defined –

• Summary of model (mass, inertia etc.,)

• Quality metrics

• Statistical details

• Material, property, special properties, composite data

• Model setup - setup material, properties, loading boundary conditions etc.,

• Verification and validation comparing

• Signature(reference)

• HM exported solver and reference files from scripts

• LEGACY SCRIPTS – For Customers/OEMs’ these are crucial as they want to see consistent results with custom scripts that they have

• Different options are allowed to compare reference summary files written out by scripts, exported files etc.,

• Direct generation of reference files and comparison across HM versions

• Simple New Auto Compare header name space is supported.

• CAD Import HM Versions comparison

• For all CAD files supported in HM imported CAD data across HyperMesh versions are verified based on Geometric entities.

• Any loss of geometric data is identified.

https://connect.altair.com/CP/downloads.html



• Comparison of Points, Lines, Surface, Solids, Assemblies, Components, Surface area comparison, Surface Metadata, Edge / Line Length comparison.

• FE Model- model setup – comparison across HyperMesh versions

• Users can now verify interactive HyperMesh sessions. Model setup across different

HyperMesh versions

• This will help them to check consistency of workflow as they switch to different

HyperMesh versions.

• HyperMesh batch mode or Interactive HM sessions with multiple scripts

• Import model, cmf/script file containing:

• Model changes on the fly

• Modify (add or remove or extend entities in groups, sets etc.,)

• Change the mesh and modify/ re-mesh

• Include transform, work on modification to include files

• Many more modeling activities that occur on a day to day basis

• Different levels of verification and validation - Functionality, feature, API verification

and validation

• Process Manager template in workflow

• Different workflows are captured by users in various Process Manager workflows. Consistency of these workflow with HW products can be verified with new Process

Manager support in FE Model- Model Setup.

• Users can use simple tcl file (sample in demo/tutorials) from which they can run any PM template and check for any problem in the HM, work flow or across

different HM versions.

• FE Model- Model setup has new HyperMesh user profile so that any scripts, cmf files can be run along with the hm files.

• Composite information for CAD IO and CAD-CAD comparison from the CATIA files can now be verified.

• Users can verify for CAD-IO and CAD-CAD comparison composite data for CATIA models with laminate and ply details.

• With details of Composite data new hyperlink is given to the main HTML report.

• List out missing surface/solids/assembly etc., in addition to the table which has number of solids/surfaces/assembly etc.

• Verification based on Modal Assurance Criterion (MAC) for OS solver (NVH)

• Along with OS solver results comparison the MAC data is key for identifying any problems in the model for NVH analysis

• Information on Modal Assurance Criterion (MAC) measuring the correlation between

two vibration shapes are extracted across two results. • Complete details of the Model correlation with MAC numbers and correlation plot are

published.



Resolved Issues

• In absence of model information in the result file it is extracted correctly from model

reader for HV version template-session comparison. • Solver version result comparison with Solver Run ON as the results are created from the

model additional check to verify model reader is removed and now results are loaded

properly for verification.

• Bug in the html report generated as NA when the actual results are available and are now correctly written as Pass for HV result comparison HV versions.

• While comparing OUT files in Solver Check run and Run spaces are neglected to generate correct report.

• Across different versions of the solver same solver file are to be used files at directories …\tutorials\hvvh\Solution\Radioss\Solver-versions-result-comparison are updated correctly

• FE model setup to accommodate write permission restrictions.

• With HV interactive option in Solution- Solver version comparison with RADIOSS solver it was showing NA after initially showing the values correctly in HV-graphics this is rectified.

HyperStudy


HyperStudy 2017.2.2 contains a combination of updates and new features that simplify both the setup and post-processing of design exploration projects. The new FAST Fit algorithm

eliminates the need for the user to make decisions on the best Fit algorithm for their data set. An improved SimLab model connection and the new lookup table model type reduce the steps

required to create new studies. For post-processing, the introduction of bubble plots to the scatter plots provides better insight to data visualization in multiple dimensions.

• Automatic Selection of Best Fit Method

The Fit approach has been redesigned to introduce a new method, Fit Automatically Selected by Training (FAST). This technology matches each unique response with its

highest quality predictive model. This setting will eliminate the time intensive steps of manually comparing Fit results, and will instead return the highest quality results without

overfitting.

The introduction of FAST means that each response within a Fit approach can have unique settings. FAST provides generalizability to new data by optimizing the settings for each response to maximize cross-validation diagnostics.



• Visualize Scatter Data in 4 Dimensions

Conventional scatter plots are limited to show data values plotted along 2 coordinate

axes. Scatter plots have been enhanced to incorporate bubble plots, which can be usedto show two additional data values via the size and color of the marker. This multi-dimensional visualization can be highly useful in many situations, and particularly

useful when reviewing the trade-offs from a multi-objective optimization.

The bubble plots option has been added to all 2d scatter plots in HyperStudy, including the Optima tab during Optimization post-processing.

• Connect to Tabular Data

Many real-world applications contain data stored in plain text tabular data, for example

the ubiquitous “csv” format. The new lookup table model quickly and efficiently connects HyperStudy to the tabular data.

This new model type automatically imports the variables and responses from a tabular file. During evaluation the model returns output responses that match the given inputs, or

it will fail if there are no valid matches. This model can be used to streamline studies that use pre-existing data, or can be used as conditional logic in multi-model studies.

• Mode Tracking using Modal Assurance Criteria (MAC)

Many design exploration problems include output responses based on an underlying eigenvalue problem, for example the natural frequencies of structural vibrations. The

modes in these problems require specialized tracking techniques as they mutually switch their order throughout the study. The new easy to use Modal Assurance Criteria (MAC)



data source in HyperStudy allows the user to ensure that their target mode is properly tracked.

Modes are tracked by finding the best match between the mode shapes in the target result file and a reference file. The mode may have been the first mode in the reference

file, but in the target it may have shifted into the third position. Information about the tracked mode can be used to either enforce a constraint condition on the mode’s value, or to force a shape match by maximizing the MAC.

• Improved Control and Efficiency During Approach Evaluation

During the Evaluation step, HyperStudy manages all of the tasks required to conduct the

approach. New features have been added to give the user greater control over the evaluation process in order to make it run more efficiently and provide more detailed information.

Multi-execute mode is always active, but can be set to 1 to enforce sequential analyses. The new horizontal evaluation option enables results to be extracted immediately after the execution. The timing of individual tasks are shown in the bubble help.



• Improved SimLab Model with Support for Output Responses

HyperStudy’s SimLab connection now supports SimLabv2017.2.1.

In addition to automatically detecting input variables, HyperStudy will now automatically detect and import any output responses defined inside SimLab. This enhancement enables users to define their study parameters within SimLab and seamlessly migrate

them into HyperStudy to conduct the design exploration.

• Query Data in Parallel Coordinate Plots

Parallel coordinate plots are aneffective way to visualize data trends in multiple dimensions. The new Query Data table lists detailed information about the filtered

evaluations, including matched highlighting between the table and the plot. This feature greatly expands the efficiency of data mining with parallel coordinate plots.

• Plot Data while Optimization Approach is running

In many cases, it is important to monitor the progress of an optimization while it is

running. Two Scatter tabs, an Evaluation tab, and an Iteration tab have been added to the optimization approach’s Evaluate step. The plots used in these tabs provide greater insight in the running process, notably when visualizing the non-dominated front of a

multi-objective optimization.



• Linking Models Into a Flow

Model resources define the file dependencies of a model connection. The new folder

resource enables users to assign all the contents of a directory as resources, and the new output model resource is introduced to be used as the target of a linked input resource. These changes to the Model Resources dialog make setup and review more intuitive,

including a visual link between output and link resource.

• Other Enhancements

• The HyperStudy Fit approach report (*. pyfit) can be imported as a model type into a

new study. This portable file can be used by groups to collaborate on system engineering projects by sharing the essence of their collected knowledge without

exposing details. • If selections with the file assistant lead to an unsupported 3-dimensional readsim data

source, the file assistant guides the user to split the selection into a set of

two-dimensional data sources. • The Evaluation step of a Fit can take advantage of multi-execution by supporting the

simultaneous calculation of multiple responses in parallel. • ASCII extract data sources support negative offsets to enable the selection of data

before a keyword. The data now equally supports both “4 apples” and “apples: 4”



• The matrix of data in a Fit previously known as a Validation matrix has been renamed as Testing to better align with generally accepted terminology.

• The ARSM optimizer now includes a “restart ARSM” option for inclusion. This option should only be used if the included data is from a previously run ARSM optimization

otherwise the included data can negatively affect the convergence.

Resolved Issues

• Fixed a problem where data source extraction failed when all responses from a model

connection were inactive.

• Added a limit to the size of the data source preview to avoid an unresponsive UI.

• Filters on the parallel coordinate are improved to work more logically with “bad values”

• Fixed the display of box plots when the data contained some “no values”

• The t and p values for regression diagnostics are now correct for categorical variables.

• Fixed an issue related to excluding run data from post-processing after sorting columns.

• Image captures now show the current theme.

Announcements

• The DSS executable will be removed from the installation in version 2018

• Python 2.7 will be replaced with 3.4 in version 2018



HyperWorks Desktop

2017.2.1 Release Notes

Introduction

HyperWorks Desktop 2017.2.1 hotfix contains enhancements and bug fixes for HyperMesh, HyperView, HyperGraph, HyperCrash, MotionView, NVH Director and HyperWorks Verification

and Validation Harness (HVVH). The details are documented below.

Note: HyperWorks Desktop2017.2.1_hotfix needs be installed on top of HyperWorks 2017.2

release.

HyperMesh


Engineering Solutions: Aero Profile

• Stuck node connection

Stuck Node connection is a special RBE3 connection that can be created between a

floating node and shell elements.

• CFAST converter

CFAST Converter will allow user to convert an existing CFAST connection type to a

CBAR + RBE3 connection.

• Window pressure

This tool converts window pressure to equivalent nodal forces on an opening. A new

load case is created in a local system and the nodal forces are applied to the nodes that

are enclosing the opening.

• Quick set creation

Quick set creates set of selected elements and then mask them from the display. User

can also append elements to an existing set and can also create nodal set from

selected elements as an option.

• Split 1D elements with property updates

This tool allow user to split an existing BEAM/BAR/ROD element at a specified location

and update its property. New property will have the same ID as the new element. The

tool will also handle tapered elements with only two sections.



• Quick coordinate creation

This tool creates new system using two methods:

o BAR method: In this method, x-axis is along the start to end node of a BAR element while z-axis represents the system direction.

o 2D elements: In this method, user selects an origin and x direction node to determine the x-axis. Z-axis will be the element normal.

• Easy graphical review of RBE/MPC

This tool provides quick and easy graphical review of dependent and independent

nodes, degrees of freedom and weight at nodes of MPC or RBE elements.

• Replace orientation node by orientation vector for Beam elements

This tool replaces orientation method for selected beam elements. User can change the orientation definition defined by a node to a vector.

• List 1D element from orientation nodes (Aero tools/Check)

This tool lists all the 1D elements which use the selected nodes to define orientation.

• CFAST fastener creation from lines and points

Aerospace Fastener tool method have been extended to support CFAST, CBAR and

RBE3-CBUSH-RBE3 element types.

• Fastener setup from csv file definitions (location file)

Aerospace faster setup tool now can get the fastener location from CSV file in addition

to lines/points from CAD system. For fastener locations defined in a local co-ordinate

system, the CID (System ID) of the system can be entered as additional column along

with co-ordinate columns in the .csv file. The local co-ordinate system needs to be

specified in the model. If none is found, the global system is considered for location

co-ordinates.

• Set Boolean operation

This tool creates element or node set from two entity lists by performing boolean

operation.

• Solid element orientation review

Aerospace orientation review tool is now enhanced to support solid element’s material

orientation. The support is extended for standards solids, continuum solids and



Layered solids (solid composite). Only for continuum solids, system will be projected

to a plane. Rest of the solid types use the system as is without projections.

• Syncing capabilities of sets created in HyperMesh or HyperView

User can add sets to HyperView session from HyperMesh and vice versa on the fly.

• MCSID review for Nastran profile

In orientation review tool, users can now review and display system based on material Coordinate system ID (MCSID) in addition to elemental system.

• Updates in Field mapping using Force Balancing option

An option has been provided to create moment loads during force balancing. By

default, this option is inactive and hence moments will be not created.

This option is applicable for nodes belonging to shell elements only and will not work

for solid elements.

• New option to map Pressures to create equivalent force

In this release, “Pressureforce balancing” has been introduced as a new interpolation

option for mapping pressure loads to a surface.

This option is available for current model or result files as a source. The feature is

useful when user is mapping pressure loads or distributed load from a source surface

to a target surface with different in size and shape meshes. This option when in use,

creates an internal model of source elements and selected target nodes. An OptiStruct

run will solve the model and gets the balanced forces at target nodes.

• Non uniform pressure realization:

Pressure load can now be realized to non-uniform pressure. “Nodal pressure” has been

added as a new option in the field type selection. With this option, pressure load card

(PLOAD4) can get different pressure values at each corner node of an element. This is

available only for OptiStruct and NASTRAN Solver Interfaces.

Resolved Issues

• Issue related to import of HMASCII file in a session containing beam sections.

• Crash on exporting Nastran or OptiStruct deck when a generic beam section is associated with a standard beam property.

• Groups and related set definitions could get incorrect reference when you merge two

HyperMesh models in Abaqus profile.

• Issue with precision value which leads to mapping of incorrect magnitude of pressure

loads.



HyperView

Resolved Issue

• The support of publishing to Microsoft PowerPoint 64-bit has been added.

HyperGraph

Resolved Issue

• The support of publishing to Microsoft PowerPoint 64-bit has been added.

HyperCrash


• Improvements have been done in penetrations calculation for /INTER/TYPE7.

• Saving of monitored volume even if normal are not detected as correctly oriented.

Resolved Issues

• Issue fixed using option "unlock other include entities referencing" under "Lock" option of include file.

• In full-dummy pre-simulation process, master nodes of rigid bodies are now exported at their correct position in the pre-simulation model.

OptiStruct Interface


• DMIGMOD card is enhanced to include RELOC field.

Nastran Interface


• Auxiliary output points along bar element axis CBARAO added to CBAR Entry.

RADIOSS Interface


• Improvements have been done in penetrations calculation for /INTER/TYPE7.

• Support of latest RADIOSS dummy models having positioning nodes (N1, N2, N3) defined in the dummy assemblies.



Resolved Issues

• Correction of graphical display for spring TYPE13.

Ls-Dyna Interface

Resolved Issues

• Correction in import process for *BOUNDARY_SPC_SET_ID when multiple boundaries are defined in a single keyword.

• Correction in import process for *MAT_LAMINATED_GLASS_TITLE.

MotionView

Resolved Issues

• Export of an extra marker per Body (Inertia Props marker) to ADM/XML.

NVH Director


• CDTire Support

Integration of Fraunhofer functionalities to generate CDTire models. These CDTire models

can be added in the tire path points manager where a CDTire representation can be created, repositioned and assigned to tire modules.

• Multiple Sample Analysis

Enhancement related to performing DSA and MSA runs with user specified run matrix.

• Design Sensitivity Analysis

Enhancement in the DSA post processing utility to support contouring of DSA results.

HyperWorks Verification and Validation Harness (HVVH)


HVVH is a new framework developed for Verification, Validation of HyperWorks products.

This will help end users to quickly evaluate the software quality, performance, reliability,

scalability, robustness and gain more confidence in HyperWorks products. This also helps

them to migrate to newer HyperWorks versions faster. Some new features are added in the

current version along with resolution of reported issues.

• Composite information for CAD IO and CAD comparison from the CATIA- CAD files can

now be used for CAD-CAD comparison.



• Composite ply layup associated lines and other geometric details can be analyzed along with CAD data

• HyperWorks template and session files with multiple clients are supported for result comparison of HyperView and HyperGraph versions.

• This helps in quick solver results comparison of user defined results in the form of animation and plots.

• Result comparison HyperView versions: Both template and session files.

• HyperWorks template with combination of Animation/contour data only or with plot details can be read and processed.

• Animation results are processed for any solver results in different HyperView versions and compared.

• Diff contour and the diff curve are generated for quick visualization along with HTML/PPT reports.

• Result comparison HyperGraph versions: Both template and session files.

• HyperWorks template with combination of time history/Plots only or with contour/animation details can be read and processed.

• Time history/plots are processed for any solver results in different HyperGraph versions and compared.

• Difference curve with statistical reports are generated for quick visualization along with HTML/PPT reports.

• For PamCrash profile HyperMesh 14.0 and later PamCrash2G2015 is supported for HyperMesh version comparison.

• For LsDyna profile HyperMesh 14.0 and later export of keyword971_R8.0 is supported for

HyperMesh version comparison.

Resolved Issues

• HyperMesh comparison across versions will show correct failure and will not publish performance charts for failure.

• Edit-Config save option is moved up so that users can easily save the configuration

changes.

•

HyperWorks Release Notes€¦ · HyperWorks Desktop 2017.2.2 hotfix contains enhancements and bug...

Documents

Transcript of HyperWorks Release Notes€¦ · HyperWorks Desktop 2017.2.2 hotfix contains enhancements and bug...