Ltd Software Suite Version 13 Update and Release Notes

SHELL

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Contents Page

1

2

Introduction

1

1.1 1.2 1.3 1.4

1 1 1 2

Bugs Fixed 2.1 2.2 2.3 2.4 2.5

3

Compatibility with LS-DYNA releases Hardware platforms supported Graphics hardware supported FLEXlm Licensing

PRIMER D3PLOT T/HIS REPORTER Shell

3 3 38 52 55 58

Enhancements

59

3.1 3.2 3.3 3.4 3.5

59 75 81 84 85

PRIMER D3PLOT T/HIS REPORTER Shell

Ove Arup and Partners Limited | Draft 1 | March 2016

Oasys Ltd LS-DYNA Environment Software

1

Release Notes Version 13.0

Introduction

The Oasys Ltd LS-DYNA Environment 13.0 suite, dated March 2016 is a full release which supersedes all previous releases. This document lists the enhancements that have been made during development, and the bugs that have been fixed (since 12.1). Each “case id” referred to in these lists is unique and should be cited if more information or clarification are required.

1.1

Compatibility with LS-DYNA releases

The 13.0 release has been used and tested with LS-DYNA version R7.1, and supports all the keywords in volumes I, II and III of the R7.1 User’s Manual dated May 2014 LS-DYNA R7.1 is now the default keyword output format from PRIMER. (However output may be generated for later releases of LS-DYNA.)

1.2

Hardware platforms supported

The complete Oasys Ltd LS-DYNA Environment 13.0 is available on the following platforms: Windows

Linux

Vista, Windows 7, Windows 8/8.1, Windows 10

32 bit

Vista 64, Windows 7 64bit, Windows 8/8.1 64bit, Windows 10 64 bit

32 and 64 bit

Redhat Enterprise 4.x Redhat Enterprise 5.x Redhat Enterprise 6.x SUSE Enterprise 11.0

32 and 64 bit

For simplicity of support and maintenance only the RedHat Enterprise 5.x build has been released on the website as this has been found to run on most machines. If you require a different Linux build, please contact us.

1.3

Graphics hardware supported

The default graphics protocol used on all platforms in the table above is OpenGL, which gives good quality 3D performance on a wide range of hardware. “Legacy” X-Windows (2D only) graphics drivers remain in PRIMER and D3PLOT on Linux platforms since these are used by a small minority of clients who display over a network of mixed machine types.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 1

Oasys Ltd LS-DYNA Environment Software

1.4

Release Notes Version 13.0

FLEXlm Licensing

The version 13.0 software has been compiled using version 11.11.0 of FLEXlm (the same as the version 11.0 and 11.1 releases) The version 11.0 licence file and licence daemons are backwards compatible with both the 10.x and 9.x software releases. This means that any existing 10.x and 9.x software will continue to work with the new licence files and servers. Note: 1) On Windows the version of “lmgrd.exe” that is installed with the version 13 software been changed to 11.11.1. Version 11.11.1 is supported on Windows Server 2012 while the 11.11.0 release shipped with the version 11 software isn’t. 2) We recommend that you update all of your Oasys Ltd LS-DYNA environment license servers with the files shipped with the version 13.0 software.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 2

Oasys Ltd LS-DYNA Environment Software

2

Release Notes Version 13.0

Bugs Fixed

The enhancements and bug-fixes for each program have been broken down into a series of topics. Within each topic enhancements and bug-fixes are listed by case ID (most recent first).

2.1

PRIMER

2.1.1

Bugs Fixed in 13.0

Airbag 

Case 28184

Fixed updating of NID in AIRBAG_REFERENCE_GEOMETRY edit panel. 

Case 28175

There was a potential crash when using the *AIRBAG_SHELL_REFERENCE_GEOMETRY panel with any 'PID' field set to zero. This has been corrected.

Ale or Euler 

Case 26503

Fixed crashes of MSTYP in ALE_COUPLING_NODAL_CONSTRAINT and ALE_COUPLING_NODAL_PENALTY.

Assembly 

Case 30007

Sketching part tree assembly which is its own child crashed. Now fixed. 

Case 29238

Quick pick of part tree assemblies now takes into account all geometry entity types rather than just parts.

Attached 

Case 30251

Using 'Find attached' in a model containing 3d elements could result in internal faces of those elements becoming visible when they should not be. This would only be apparent if the parts in question were made transparent, since then their internal faces would be visible. This was in fact caused by the tied contact checker, called by find attached to track across tied contacts, which used the internal face calculation to work out which elements of a partially unblanked part were visible. This should have backed up the 'true' internal face status, recalculated it temporarily according to different criteria, then restored it, but this was not always happening. Now fixed: the backup is restored correctly. 

Case 28321

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 3

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

With find attached, the 'recursive' options did not take into account the rigid part 'whole' or 'single element' setting - it always used 'whole part'. This has been corrected.

Belts 

Case 29387

When creating a new seatbelt using the belt fitter label clashes between newly created belt nodes and elements and existing nodes and elements in the model could occur in the following situation: - Belt is created in an explicit include file, by setting this as the current layer for creation and - That include file has specific label ranges defined for nodes and elements and - those ranges do not leave a single contiguous label 'gap' that is long enough to hold the newly created nodes and/or elements. That is the stipulated label range is already full, or nearly full, of the relevant types. The belt fitter did check for available label space prior to generating the new belt mesh, but it did not consider this particular situation. This has been fixed by making the 'check for space before meshing' logic more general, which means that it now detects this situation. The user is presented with various choices which will get round the problem automatically, or they can reset the start labels for the affected element / node types manually to something that gives sufficient label space. 

Case 29323

The seatbelt fitter crashed during the belt meshing stage if all of the following were true: - The belt was meshed with 2d seatbelt shell elements. - The section shell card was already defined - This section shell card had an existing EDGSET definition - That set definition was latent (i.e. referenced but not defined) The crash occurred when trying to insert nodes into the set when that set was not correctly initialised. This has been fixed: attempting to insert data into a latent set will now work, and because that set now has content it will be converted from 'Latent' to 'Installed'. 

Case 29158

The belt fitter in PRIMER used the wrong elements when auto-refitting an existing belt mesh. In this instance the problem was caused by an unusual choice of original mesh, and this confused the existing logic which 'crawls up' the mesh to determine how it is organised. This logic has been improved so that it will handle a much wider range of possible belt mesh layouts, including the new possibilities added in PRIMER V13.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 4

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

In addition from V13 onwards PRIMER now writes extra information to the *BELT_MESH cards which states explicitly how the belt was meshed. When the model is reread for remeshing this information is used to determine the meshing of the new belt. This information is valid for an auto-refit, or for a manual refit where the belt topology is not changed; however when processing an older deck written before V13, or a belt in which the path has been edited, the older (improved) logic is still used. 

Case 28874

Various problems with seatbelt fitting: (1) Changing a belt from old-style (1d belt elements + shells) to (2d belt elements) caused problems. The belt fitter in V13 has improved its diagnosis of how an existing belt is organised, and for future belts it now writes this information explicitly in the *BELT cards after *END. This should improve the accuracy of (re)fit of existing belts, and also the conversion between meshing styles. (2) Remeshing a belt with multiple sections of 2d belt elements interspersed with shells could leave 'orphan' *SECTION_SHELL cards behind that were not used by any elements. This in itself is not an error, however these still contained their old EDGSET definitions, used to work out the topology of 2d belts, and these now contained no nodes which resulted in an error during initialisation in LS-DYNA. This has been fixed. Belt paths with multiple stretches of 2d belt elements have to create separate *PART and *SECTION cards for these, but these are re-used during refit, or if they are not reused then they are deleted if no longer required which solves the 'empty EDGSET' problem. A related problem of 'orphan' empty node sets used for extra nodes on rigid parts following a belt refit has also been fixed. (3) Both 1d and 2d belt elements need to have an initial length that is at least 1.6x the LMIN minimum length on the *MAT_SEATBELT card, otherwise initialisation will fail in LS-DYNA. The belt fitter now checks for this during the meshing phase, and in addition the standard check function for this material type will now detect and warn if any such elements are found. (Strictly this LS-DYNA criterion only applies to belt elements attached to a slipring, but in practice adjacent elements can feed through, so PRIMER tests all belt elements.) 

Case 28323

When a seatbelt fitting path is modified using the JavaScript Belt method to add a node, the coordinate of that node is not copied into the appropriate storage in the seatbelt structure. This doesn't matter during interactive usage, because opening the belt fitter panel will perform that copy anyway, but if a belt is edited using JavaScript in pure batch mode (i.e. read model, edit belt, write out again) this problem could occur. Now fixed: using the JavaScript API to edit or add a belt path point specified by a node now also copies that node's coordinates into the appropriate storage. 

Case 27873

When seatbelt path twist is being controlled (the belt path editor is in 'control twist' mode) it is now easier to see what is happening:

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 5

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

(1) The twist handles used to drag the belt twist are now drawn in a way that ignores hidden surface removal, making them easier to see and in particular meaning that they don't get 'lost' inside adjacent structure. (2) Moving the mouse near to a twist handle will now highlight it in red, making it easier to see which path point will be selected by a mouse click. (3) Where path twist is defined by nodes these are now highlighted and labelled (again ignoring hidden surface removal) making it much easier to visualise them.

Capture 

Case 28027

When capturing an image from PRIMER for REPORTER it may have been possible to get predictive picking on the image. This has been fixed.

Checking 

Case 30134

In models with large numbers of complex set definitions, autofixes could run very slowly because of repeated (unnecessary) recalculations of set contents. Now fixed. 

Case 30019

Sketch of large number of items on check tree could be very slow. Now fixed. 

Case 30018

If IPBACK flag is set, constrained contacts may be used to tie rigid bodies. In this case error messages about the contact should not be issued. 

Case 29995

When preference option 'automatically_create_connections_from_welds' is set to off, the option to check contacts for constraint clash was incorrectly switched off. Now fixed. 

Case 29880

The test for type 2 quad shells with opposed free edges has been improved to test for attachment to elements of other types as well as constraints. Additionally, the verbatim test for element formulation on the section card has been replaced with a more robust lookup function. 

Case 29608

Stress strain curves for MAT24 (and similar) may start at values of X less than zero. Also the yield stress should be calculated from the interpolated y value at x = 0, not simply taken as the first point of the curve. These have been corrected. 

Case 29205

The logic that matches the error tags in the error control file to those on the error messages could result in unwanted behaviour. A shorter tag such as CTRL_20 was being incorrectly applied to messages CTRL_200, CTRL_201, etc. Now fixed. 

Case 28837

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 6

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

A new check (and autofix) has been added that reports an error if a SET_SEGMENT is referenced by a CESE card but the SOLVER field is not CESE. 

Case 28813

Added missing categories to model check panels. 

Case 28213

When using DAMPING_PART_MASS on part set, Primer applied to the part which has the same ID user typed in rather than the part set. Now fixed. 

Case 28781

The text file written by model check function used a format of width 10 for the label listing. This meant that long labels got concatenated with consequent confusion. The format has been amended so that a space is inserted between labels when required. 

Case 28708

Models with local prescribed motion on rigid parts and local constraints on the material card could give spurious messages about constraint conflict. The check has been corrected to consider only the cases where global motion is defined. 

Case 28592

Duplicate error tags have been relabelled to ensure they are unique to avert potential problems with user defined error configuration files. 

Case 28340

Enabled editing of 'Added Mass' parameters in Check Options Settings Dialog even if those parameters are not used for Model Checking. 

Case 27922

A Seatbelt Retractor can have 'unborn' elements inside it waiting to be pulled out, and the PRIMER editing panel allows you to define how many such elements exist. PRIMER also allows you to add or remove elements from this unborn list, and there was an error in determining the free end of 1d belt elements used this way if the free end of the element's topology pointed 'away from' the retractor mouth node. In other words if the retractor mouth node was NA, and the seatbelt elements inside the retractor were organised so that node #1 was NA and node #2 was further inside it would fail to find the free end, i.e. the last inside element. The effect would be to refuse to add or remove unborn seatbelt elements from the retractor, leaving the list 'as is'. Now fixed by considering the case of unborn elements facing in either direction. 

Case 27902

When the slave side of tied contact is defined by parts, LS-Dyna does not tie the internal nodes of solids. This was only detected if the solid was a Primer connection (weld or adhesive). The test has been generalised and the contact check option 'slave nodes on solid face must tie' may be used to detect untied nodes for any contact. 

Case 27646

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 7

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

A look up type function for STRUCT_NODE was missing in *DEFINE_DEATH_TIMES, now fixed it.

Comments 

Case 29414

Now storing rest of line after *COMMENT. 

Case 26113

The default for writing HM comments is false (or set by preference). Previously it got set to true when HM comments were encountered on model read which could be confusing and potentially caused generation of HM comments in models which had none. Now the action is stored on a per model basis and the global default will not change unless the user changes it.

Compare 

Case 28330

Connection compare was comparing fields which are not applicable for certain types of connections.

Composites 

Case 29344

Updated thicknesses on the composite ply edit panel are now synced with the layup edit panel. 

Case 29103

Fixed crash in SHELL_COMPOSITE edit panel when turning on _LONG. 

Case 28877

Added warnings about composite plies used in several layups at the same time. 

Case 28552

Fixed button errors in composite ply edit panel. 

Case 28544

Fixed blanking for Composite Layups. 

Case 28311

When ELEMENT_TSHELL_COMPOSITE(_LONG) was keyed out in an unsupported version the option was incorrectly removed from the keyword. Now fixed.

Connections 

Case 30025

Fixed reading VIP connection files with more than 150 characters on a line. 

Case 29861

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 8

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Primer would sometimes fail to read a VIP connection file if the parts referenced to join together were specified as CAD/part names in the VIP file. This has been corrected. 

Case 29417

When creating beam spotweld with a latent section definition, Primer will create ELEMENT_BEAM_PID on assumption that user will make valid beam section (elform=9) later. If the section is defined and it is not elform=9 _PID will not be applied. 

Case 29111

The connection bolt maker sometimes made an ill-conditioned DEFINE_COORDINATE_SYSTEM when creating a discrete bolt. Now fixed. 

Case 28700

When checking a model where all connections were defined with layers referencing parts which do not exist, the check process exited with messages about internal error in the spot-welder. In this case where connections cannot be processed, no attempt is now made to setup the spotwelder and the process is ended gracefully without disruption to model check. 

Case 28281

When MIG connections are automatically made from existing MAT100 beams, Primer does not always get the order of nodes correct. The free node that requires contact should always be N2. If order is wrong this will result in a failure of the connection contact fixer to work. Now fixed. 

Case 27202

Connection compare logic was corrupting *SET_NODE data - Now fixed. 

Case 26714

Angle tolerance for bolt connections defaults to (e.g.) 30 degrees is now written as 30.0 (rather than 0.0) to the post end data. If an old format keyword was read and the connection table invoked, model modified reported differences. The problem has been fixed by converting the value from 0.0 to the default on read of the connection.

Constraints 

Case 29986

When creating *CONSTRAINED_NODAL_RIGID_BODY entities in manual (i.e. non-auto) mode the optional suffix (_SPC etc.) would get reset each time to 'not defined', whereas in automatic creation mode this suffix would be remembered. This was annoying since, on the whole, when you create a sequence of items the chances are that they will all share the same options and keyword suffices. Therefore the panel now remembers rather than resets the suffix, regardless of the current creation mode. 

Case 28728

The dependant node on CONSTRAINED_INTERPOLATION is now structural. 

Case 25590

In CONSTRAINED_GENERALISED_WELD panel, if we are using creation methods like pick nodes or pick nodes with tolerance, we first create a new node set from the list of nodes and then

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 9

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

we create the weld. If weld length is longer than maximum allowed length then weld is not created but newly created node set remains in model. Now set will be made after length test.

Contacts 

Case 30285

The determination of the segment to which a node is tied by a tied contact could give the wrong answer in some cases where there are multiple candidate segments. 

Case 30224

Keyin of label on object menu to select a contact for penetration checking got stuck in a loop setting up the panel. Now fixed. 

Case 29227

On *CONTACT card FS = 2 FD = table of data, is now handled for all contacts listed in the manual. 

Case 28549

For INITITER Field in CONTACT_MPP, a blank field is not the same as zero, it means default value of 2. So we trap a blank string and replace it with default=2, the same way it is done for CONTACT_MPP Modify Dialog. Else if, INITITER is given some valid integer value (including 0 or 2), we show that value in the text box. 

Case 28516

In the CONTACT editing panel the 'Copy existing' button only allowed you to copy data from a contact in the current model, as opposed to from any model. This has been fixed. (The same error existing in the CONTACT_2D editing panel as well, also fixed) 

Case 26543

The duplicate shell treatment option did not work for tied contacts where the nodal thickness was derived from the average thicknesses of the shells that attached. This has been modified to use the thinnest or thickest as per the option. The default of 'automatic' will mean use the thinnest in this context, which is safest as LS-Dyna's choice is unpredictable. 

Case 26539

Determination of slave node contact thickness will only include the effect the thickness of attached shells if at least one of these is in the contact. Thus a contact where the slave side is defined as beam parts will not be influenced by shells that mesh onto the beam nodes. 

Case 26532

Fixed crash in field OFFSET of *CONTACT_DRAWBEAD_COUPLING

Contour 

Case 29427

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 10

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Refinement of the mass scaling contour, either by clicking on contour bands or by setting values in the settings panel, would sometimes incorrectly omit relevant elements. This has now been fixed. 

Case 29353

PRIMER could crash when plotting yield stress of composite parts. This has been corrected. 

Case 25900

Restricting what is shown in a contour (data) plot by clicking on a contour band worked correctly in the sense that you then only saw items of that band, but it failed to update PRIMER's understanding of what was visible. This meant that screen-picking would often select the wrong item, typically a part not currently visible, and moreover this could make it impossible to screenpick what you *could* actually see on the screen. This has now been fixed. Restricting by contour band now updates PRIMER's internal visibility tables correctly, meaning that it now 'knows' what you can see and will not attempt to screenpick something that is not drawn. NOTE: restriction of what is visible to items in a given contour band is not the same as blanking, and does not affect the blanking status of the elements and nodes being shown. In particular it is *not* the same as an 'only' (in the sense of blanking) operation. To perform an 'only' operation on what is visible it will be necessary to select it, by area or explicitly, and then to choose 'Only' as the operation to be performed on this selection. 

Case 18842

Time step calculation for 4/10-noded solid tetrahedral elements has been corrected.

Control 

Case 28344

For keyword CONTROL_CPM, Zero values for NCPMOUT and SFFDC are allowed, Primer only checks range for Non-Zero Values in such cases. 

Case 27246

FLATNAME on CONTROL_FORMING_ONESTEP edit panel was not mapped properly, now fixed. 

Case 27240

SMIN on CONTROL_ADAPTIVE_CURVE is float type and integer type was used to update text field, now fixed.

Curves 

Case 29785

Load curve units were sometimes wrong when curves are referenced multiple times. Now fixed.

Cut section 

Case 28584

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 11

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

When a cut-section is drawn through segments, typically when the visibility of *SET_SEGMENT is turned on in the Entity panel while cut sections are active, they are drawn by default with a 'capping' polygon of fixed thickness. This is to give the cut a finite graphical appearance, similar to that used when shells are cut. Unfortunately this capping polygon thickness was hard-wired with a value of 10.0, which was fine for a model in mm units, but gave disastrous graphics when the model was in metre units! This fixed capping polygon size is now model-dependent, and will be 10.0 (as before) if the diagonal across the bounding box that encloses the model is > 100.0 units, presuming mm units. However if the diagonal is less than that then metre units are assumed and it is set to 10.0e-3 

Case 28482

When shell elements have their neutral axis offset from the nodal plane by using the _OFFSET suffix, or setting NLOC on the part or section card, they should be drawn offset from the nodal plane. In normal PRIMER graphics shells are drawn as infinitely thin plates on the plane defined by their nodes, regardless of any offset, and this is an acceptable compromise which gives fast rendering. If 'true' shell thickness display is turned on (in Display Options) then shells are drawn showing their actual thickness, and any offset from the nodal plane is also included so that the shape and position of the element is correct. However when cut-sections are turned on in normal graphics mode shell elements are given a 'capping polygon' of the section thickness, and this was also drawn centred on the plane of the nodes even if the element had an offset, giving the misleading impression that the element was not offset. This has now been corrected: when cut sections are turned on the capping polygon drawn for a shell will now take into account any offset of the element neutral axis, even in 'normal' graphics mode.

Damping 

Case 24849

Modified *DAMPING_MASS_PART edit panel, so that multiple definitions with _SET option can also be created.

Database 

Case 30122

In *DATABASE_BINARY_D3PLOT, _FILTER will be appended to header if TYPE is nonzero. 

Case 28653

The template panel when fully expanded was incorrectly remapping itself when any button click occurred in grey space of the panel. This lost the slider position. This has been fixed so the panel only remaps when the number of rows or columns has changed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 12

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Deleting 

Case 29878

Forcible deletion from include tree with option DELETE_1 now offers question to completely remove file. 

Case 29854

Removing an include file sometimes deleted its contents only. Now fixed. 

Case 29277

In cleanup unused if the option to treat Lumped Mass as non-structural was turned off PRIMER would still include the node on the lumped mass in the total number of items to clean up. This has been fixed. 

Case 29223

Some damping cards with empty sets were not removed in cleanup. Now fixed. 

Case 28473

The [Remove] Cleanup Unused function has been extended to include the following: - Groups which are empty (unless explicitly locked against deletion by the user). - DATABASE_CROSS_SECTION cards which don't do anything. For the _PLANE variant this means not cutting any elements, and for the _SET variant it means if all sets are empty. - CONSTRAINED_INTERPOLATION cards which don't do anything, i.e. when all independent nodes are only in this constrained card and have no other structural attachment. 

Case 28341

In a model with many parts (e.g. >10,000) in which one or more sets contain most or all of these parts the 'Calculate cleanup' operation could become very slow. This was because it was looping over the set contents for each part, giving a #parts squared loop. This was unnecessary and has been recoded to loop over only once, which gives a much faster response.

Dummies 

Case 30220

When using 'Dyna dummy positioning', you can specify to rigidify assemblies. If you specify to turn off the rigidification of an assembly, the 3 nodes automatically chosen may be different to the original ones chosen before you specify to rigidify. This has been corrected. 

Case 29163

For Dyna Dummy positioning you could end up with a *DEFINE_CONSTRUCTION_STAGES card with a label greater than 999 (this card is used to create a dynain file). Labels this high are invalid in versions of LS-DYNA previous to R7. A check has been added for the output version to ensure if running in older versions of LS-DYNA the label is valid. 

Case 28312

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 13

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

When editing a Dummy definition it is confusing that the point generated automatically at the dummy H-Point position can be edited, but that these edits are 'lost' when the dummy is updated and that point is re-created at the 'True' H-Point definition. So a warning has been added to the Dummy Point editor if an attempt is made to edit this point, and the editing panel is set to read-only mode. This warning also explains how to change the dummy H-Point position via 'Position, Set H-Point'. 

Case 27494

Some dummies define their PRIMER tree file in such a way that the pelvis, torso and head assemblies report angles that are 'relative to root' rather than 'relative to parent'. This can be more intuitive since, for these dummy components, angles relative to some absolute system are easier to measure and record. This is done by defining a top level assembly that is the dummy's global coordinate system, and then specifying *DEFINE_COORDINATE cards on the *CONSTRAINED_JOINT_STIFFNESS cards for these assemblies such that the nodes on the 'parent' side of the joint stiffness are actually on this global assembly, rather than on the assembly that is the immediate parent. PRIMER's checking logic detected this and reported this as an error (demoted to a warning in 12.1) because the nodes on the parent coordinate system were not on the parent assembly. From release 13.0 onwards this way of modelling is now considered, and no warning will be reported for any joint stiffness if the nodes on the parent side coordinate system are on this parent assembly or any of its ancestors in the dummy tree hierarchy.

Edit 

Case 29953

Pressing the 'P' parameter button when editing MAT_ADD_EROSION remapped the material panel in the normal material mode. Now fixed. 

Case 29539

Writing a model in select file mode with check file write active, followed by edit checking with a subset of includes being checked could result in SIGSEV failure. This has been fixed. 

Case 29531

Corrected button text for RT2 on ELEMENT_BEAM edit panel. 

Case 29429

Added new buttons like Xrefs, Copy Existing...to *ICFD_PART edit panel. 

Case 29167

Set type field on DATABASE_FSI create panel now works correctly. 

Case 29060

PRIMER could crash when picking nodes to add to a node set if there were multiple set editing windows open. Now fixed. 

Case 29011

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 14

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

These keywords can now be edited in Primer: *MESH_BL_SYM, *MESH_EMBEDSHELL, *MESH_SIZE, *MESH_INTF, *MESH_VOLUME 

Case 28568

Rotate orient converts DEFINE_BOX definitions to _LOCAL. Subsequent edit of the box would not allow the option to be switched off. Now fixed. 

Case 28527

PRIMER could crash when creating entities in the BOUNDARY_PRESCRIBED_FINAL_GEOMETRY edit panel. This has been corrected.

Elements 

Case 28546

Problem with screen pick of overlapping elements. Now Fixed. 

Case 28409

In the SECTION Dialog for Tshell, IRID field now accepts 'User Defined' INTEGRATION_SHELL values. 

Case 28317

PRIMER could write *ELEMENT_SHELL_NURBS_PATCH cards incorrectly, corrupting the data. Additionally editing the element could cause PRIMER to crash. Both these problems have now been fixed. 

Case 28205

Fixed crash in the 3 node option on shell edit panel. 

Case 28176

The object menu is now not seen in Element->TSHELL and Element->Solid Align panel when it is not required. 

Case 28118

Some Primer crashes has been resolved for Solid->Align and Shell->Align.

Error Trapping 

Case 29355

Error message corrected for zero length discrete beams with SCOOR = 3.

FMH 

Case 30205

If you cycle through various help (?) buttons on the final pane in the FMH script menu without dismissing the help menu each time, you could end up with an older help image. This has been fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 15

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 28091

For the FMH manual setup panel, it was not obvious that you have to click 'Done' at the top of the panel to apply the velocity to the model. A new popup message has been added to tell the user if this is the case.

Frequency 

Case 28278

Tabbing out of the SSTYPE box in the Create/Modify panel for FREQUENCY_DOMAIN_ACOUSTIC_BEM no longer causes the SSID field to be reset to zero (if SSTYPE hasn't changed).

Graphics 

Case 30370

Predictive picking did not work for latent parts. Now fixed. 

Case 30289

When a database contained two or more models, and something (e.g. ORIENT) was used to move parts in a lower-numbered model to a location that was not currently visible, then using dynamic rotation or panning to move those parts back into view could result in their failing to be drawn. They are shown correctly if the scale is changed, for example by autoscale or by dynamic zoom, or if the display mode is changed. The problem was that the coarse 'clipping' used to remove complete parts from the graphics pipeline was getting confused in this situation, effectively resetting itself to 'nothing is clipped' each time a model was drawn. So moving a lower numbered model resulted in PRIMER 'forgetting' that something in it had been clipped, and thus failing to draw it when it moved back into view. Scale and viewing mode changes reset the clipping test, and provide an easy solution to the problem. Fixed by making sure that the clipping status does not get reset between models. 

Case 30129

Degenerate 6-noded cohesive solid elements, which have a 'pentahedral' topology that is different to the normal 6-noded 'wedge' shape in LS-DYNA, were not being drawn correctly. In addition some spurious error messages about their topology were generated during Model Check if they used hexahedral ELFORM 19 or 20, but the ESORT flag on *CONTROL_SOLID, which automatically sorts these into pentahedrons, was not set. Both problems now fixed. 

Case 30103

In rare situations the use of 'mesh split' for solids in a model in which some other solids were blanked could result in exposed internal solid element faces not being drawn. This was due to internal confusion about the visibility of internal faces following the change to the mesh topology, and has now been fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 16

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 30029

Fixed crash in display of material axes for part without section. 

Case 29787

When beam 'true section' display mode was used for a model that contained many beams that had their properties defined by explicit Area, Ixx and Iyy on the *SECTION_BEAM card PRIMER could be slow to perform dynamic zoom (shift + right mouse). This was because of unnecessary repetition of the calculation of an equivalent section shape of these beams. These repetitions have been eliminated resulting in much faster graphical response. 

Case 29527

True beam sections sometimes caused HANG. Now fixed. 

Case 28644

BOUNDARY_PRESCRIBED_MOTION labels are no longer drawn in yellow but in a colour that is easy to see depending on the current background colour. 

Case 28623

Primer's local angles display function was incorrectly ignoring beta from *MAT for aopt (also from *MAT) values other 3 for simple (non-composite) shell definitions. This has now been fixed. 

Case 28357

Corrected toggling logic on entities panel. 

Case 28121

Sketch arrows for LOAD SHELL pointing towards the median point of the shell in direction of normal to shell. On activating DRAW for LOAD_SHELL, these arrows will be displayed for all shells. 

Case 27963

PRIMER has the ability to draw thin shell elements using their 'true' thickness (see Display Options, Shells thin/thick), but historically this has only 'capped' the free edge faces of shells. This treatment is correct if no shells in a part are blanked, because the free edges will also be the free faces, but if a shell *is* blanked this can expose an 'internal' face on the adjacent shell, and this newly visible face was not being drawn leading to what looked like visual holes in the image. This has now been corrected: when in shell true thickness display mode the necessary calculations to find exposed internal faces are now performed, and the image is updated to show these faces. 

Case 27945

On Windows platforms from Vista onwards the Aero desktop logic introduced by Microsoft could result in rather ugly black areas being left behind when sub-windows were dragged. The logic used to perform this dragging has been modified to get rid of this problem. 

Case 27587

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 17

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

When performing a contact plot with the option set to draw the rest of the model normally, a dynamic zoom appeared to lose the drawing of the rest of the model and revert to a plain contact plot. This has been fixed by removing the stack redraw in this case.

Groups 

Case 27041

When a model containing Database_Extent_SSSTAT is read, Primer automatically creates groups of parts for each set. These are now named SSSTAT_part_set_n, where 'n' is the index 1, 2,.. rather than the label of the part set. This makes the process independent of model renumbering.

Help 

Case 28697

Added missing help text for composite layups and plies.

IPP 

Case 30369

Added manual page link and help button to IPP panel.

Include 

Case 29101

PRIMER could crash when writing a model containing *INCLUDE_TRANSFORMs if an include file was deleted from the model. Now fixed. 

Case 28550

Object menu key-in of include file IDs now works correctly, including the use of wild cards.

Include transform 

Case 29978

PRIMER no longer offsets any volume III keywords in *INCLUDE_TRANSFORM (as LSDYNA not does) 

Case 28351

Fixed a crash when *INCLUDE_TRANSFORM + ORIENT (on INCLUDES) + LARGE LABELS combination operation was done. 

Case 26981

If *INCLUDE_TRANSFORM files were defined with labels for items less than the offset then PRIMER could write a different incorrect positive label instead of the 'correct' negative label. PRIMER would not be able to read *INCLUDE_TRANSFORM files that contained negative labels, even if the label would be positive after offsetting the label. Both these issues have now been fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 18

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Initial 

Case 28563

PRIMER incorrectly rejected a part defined by a character label on a *INITIAL card, claiming that it had an illegal negative value. This was because PRIMER assigns negative internal ids to items that use character labels, and this test was wrongly detecting this as an error.

Installation 

Case 28999

Windows executable files now have fully populated 'resources'. This means that their names on icons, revision numbers and other information are all properly defined as expected by Windows (previously some of these data fields were missing or generic). In particular it means that the proper version information will appear on the 'open with' panel, making it possible to distinguish between multiple executable versions.

JavaScript API 

Case 30083

On Linux Window.GetFilename() could not be used to give a new filename. This can now be done by using an optional 'save' argument. 

Case 29969

The JavaScript API function Xrefs.GetType crashed when there were no cross references. Now it reports an exception. 

Case 29864

Parameters diam2, length2, angtol, angtol2, shape, shape2 which are used for bolt creation have been added to the JavaScript API. 

Case 29322

File.Copy() threw an exception if it failed. File.Delete() returned false if it failed so the API was inconsistent. File.Copy() has been changed so it just returns false if it fails to make the API consistent. Additionally the user does not have to rely on try/catch to prevent the script from terminating on error. 

Case 29255

IMSCL on *CONTROL_TIMESTEP could not be set to a negative value from JavaScript. Now fixed 

Case 29151

If material curves were updated in JavaScript the curve cross references could contain extra incorrect references. Now fixed. 

Case 29112

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 19

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

If Model.Write was used to write a model and it contained labels higher than the label limit for 'normal' keyword format PRIMER would truncate the labels. PRIMER will not automatically switch to use 'long' format. 

Case 29067

Cross references of type 'CONNECTION' did not work in the Xrefs class. This has been fixed. 

Case 28809

Model.ImportInclude would not read *PARAMETER_LOCAL cards if a parameter with the same name already existed in the model. This has been fixed. 

Case 28788

Fixed return value for ExtraNodes.Create and RigidBodies.Create in JavaScript API. 

Case 28677

The JavaScript function which reports whether a part is rigid or not was found to sometimes give the wrong answer. The determination of whether a part is rigid is both intensively required and sufficiently complex so that the status is stored internally on the part structure and only recalculated if required. This requirement is determined by the 'data changed flag' which is updated internally in Primer whenever a data changing operation (creating, editing, deleting, etc.) is invoked. JavaScript data modification has been fixed to work in the same way. 

Case 28616

The model centre of gravity could be incorrectly calculated if nodal coordinates were changed. Now fixed. 

Case 28540

Shells with 6 nodes can now be correctly created in JavaScript API constructor. 

Case 28490

Corrected renumbering logic in JavaScript API constructors of optionally labelled items. 

Case 28191

The object returned from Curve.Create() was corrupt. Now fixed. 

Case 28180

On Windows using System() when reading a file flushed the file you are reading so further reads did not work. This has now been fixed. 

Case 27760

Added support for _COMPOSITE_LONG in the Part and Shell classes. 

Case 26980

When changing the label of an item in JavaScript there was no check to make sure the new label was not an existing label. A check has now been added. 

Case 26525

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 20

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

The limit of 20 lines for Window.Information(), Window.Message() etc. has been removed. The maximum number of lines is now controlled by Options.max_window_lines. 

Case 21633

When running a script in the debugger and line numbers reported when compiling a script with 'strict mode' were incorrect by a line. Now fixed.

Keyword 

Case 29972

Card 2 on *MAT_ADD_FATIGUE not culling when writing in R8 - Now Fixed 

Case 29862

The presence of *CONTACT_RIGID_SURFACE card could previously lead to the removal of unused nodes that contain no direct cross-references. This could result in data for latent nodes being remove from *AIRBAG_REFERENCE_GEOMETRY cards. This has now been fixed. 

Case 29630

Corrections to LOAD_THERMAL_VARIABLE keyword write out for older versions. Also LCIDR is no longer a compulsory field. 

Case 29610

VID on SENSOR_DEFINE_NODE can now be X, Y or Z. 

Case 29411

Added option FATIGUE on FREQ_DOMAIN_RANDOM_VIBRATION keyword editor panel. 

Case 28879

Added drawing function for LOAD_SEGM_CONTACT_MASK 

Case 28811

CHEMISTRY_MODEL missing from the green keyword buttons -> Now Fixed. 

Case 28586

Errors related to update and edit of *CESE_BOUNDARY_PRESCRIBED_SET card have been fixed. 

Case 28534

Previously, Primer was writing out multiple ICFD_BOUNDARY_XXX cards under one header and it was causing problem in DYNA. Now, Primer will write out one header per keyword. 

Case 28499

Decks containing the *ALE_AMBIENT_HYDROSTATIC keyword with more than one card 2 can now be processed. 

Case 28280

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 21

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Primer could previously omit some intermediate rows in ICFD_MAT if only zero values were encountered while still writing some subsequent rows. This would have had the effect of incorrectly shuffling some rows up. This has now been fixed. 

Case 28045

Greyed out sketch button for *CESE_BOUNDARY 

Case 26704

Replaced buggy keyword editor with edit panel for BOUNDARY_MCOL. 

Case 26605

In *INITIAL_HYDROSTATIC_ALE, wrong entity type was used to allocate and return memory. It is fixed now. 

Case 26591

The format for the keyword INCLUDE_STAMPED_PART/SET_MATRIX(_INVERSE) has been modified to match the latest manual. The keyword editor has also been corrected. 

Case 26573

INTERFACE_SSI_AUX card did not handle title option correctly. 

Case 26571

Primer did not read INTERFACE_BLANKSIZE_INITIAL_TRIM. Now fixed. 

Case 26542

Fixed errors reading *DEFINE_FILTER 

Case 26332

The FREQUENCY_DOMAIN_ACOUSTIC_BEM panel had incorrectly programmed options. Now fixed.

Kwd editor 

Case 29629

Keyword editors did not always warn about pending changes on entry row. Now fixed. 

Case 29276

The *CONTACT keyword editor did not take into account contact types when determining if FD was a float, *DEFINE_TABLE or *DEFINE_FRICTION value. This has been corrected. 

Case 29108

Latent MAT and EQOS volume III keywords now appear in the keyword editor 

Case 29030

Some of the *INITIAL keyword editor panels, for example _SHELL_STRESS, have to deal with the problem of displaying different formats depending on the number of integration points on plan and through the thickness, and sometimes other permutations as well. In order to avoid

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 22

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

showing large numbers of unused data fields the user is required to select which permutation of these is to be shown, and display is limited to just those data fields. PRIMER attempts to start the editor with a sensible display by examining all the potential candidate cards and extracting the most likely permutation. This worked correctly when all such cards in the model were being displayed, but when the user selected a subset (for example by screen-picking) it failed to examine only that subset, with the result that if the selected items did not match the 'whole model' scan nothing would be shown. This has been corrected: when a subset of the available cards is selected only these are scanned to determine the correct settings for launching the panel. 

Case 28591

SST and MST fields of *CONTACT_TIED_ Keyword can now be given negative values in keyword editor.

Labels 

Case 30034

Null beams from contact penetration check could be created with corrupted labels. Now fixed. 

Case 28539

Large labels will now be outputted properly for *EMAG_MAT. 

Case 28375

When creating entities using the 'highest plus 1' labelling method, you may receive unexpected results for constrained nodal rigid bodies or parts. This has been improved. 

Case 28359

An input deck using character labels failed to handle these correctly due to an internal error in parsing them. The problem can be solved by reading the model twice (deleting the first instance). 

Case 26828

Models with optionally labelled types (e.g. contact) which have been read as long labels would write out in large format (long=y) when they should not because the label option has been switched off. The test for long labels has been corrected to ignore cases where the option is off.

Loadcurves 

Case 29542

Corrected units for loadcurves on CONSTRAINED_SOIL_PILE

Local axes 

Case 27665

Primer's local direction display function now takes cognizance of MACF (axes swapping) specifications in *MAT cards

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 23

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Macro 

Case 29271

If a relative pathname was given for a macro to record by typing the (relative) filename into the textbox and the file selector button was then pressed the selector could sometimes not open in the correct directory. Now fixed. The filename is now automatically converted to the absolute filename 

Case 29022

Macros involving editing text in slider area of INITIAL_HYDROSTATIC_ALE Create/Modify panel now work correctly. 

Case 28028

Few buttons on *AIRBAG_SHELL_REF_GEOM edit panel did not have macro tag, now fixed it.

Mass 

Case 30127

Model checking for ASSIGN_MASS was missing. Now added. 

Case 28350

The totals reported in the summary file for include file part masses have been corrected so that lumped mass on deformable parts is not included in the part mass. 

Case 27477

The function 'Mass of Visible Elements' (Mass Property Tool) incorrectly included mass of any attached Nodal_Rigid_Body_Inertia irrespective of whether or not it was visible. Now fixed. 

Case 27071

When reading very old (pre version 8.2) assign mass definitions into PRIMER the centre of gravity could be lost. Now fixed.

Materials 

Case 30322

The Suffices button on edit panel for MAT_181 was incorrectly greyed out. Now fixed. 

Case 30287

Fixed a crash in material keyword editor when MAT_ADD_XXX cards were present without main material card. 

Case 29619

Updated the MAT_221 fields' description. 

Case 28703

For the Young's modulus in MAT_255 there was no cross reference put on a negative curve id. Now fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 24

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 28643

For MAT187 EPFAIL is now supported as failure strain (positive) or failure strain curve (negative) 

Case 26727

Fixed: MAT_075 appears twice in the material type menu. 

Case 26406

When editing the field ISLC for material 248 the panel scrolled back to the top. This has now been fixed. 

Case 26230

Checks on complex materials (such as MAT224) that use piecewise linear stress-strain curves could give incorrect error messages about SIGY or curves crossing below failure strain. These have been fixed. 

Case 25570

If a title was given on a *MAT_EROSION card it overwrote the title for the 'normal' material with the same ID instead of storing the title on the *MAT_ADD_EROSION card. This has now been fixed.

Mechanism 

Case 30243

A crash occurred when a mechanism was created automatically, and then positioned enough times to require joints which had moved apart to be auto-fixed to coincident. This was due to an internal error and is now fixed. 

Case 29565

Previously it has been hard to visualise the contents of dummy and mechanism assemblies because there is no easy way to visualise them in isolation. The 'only' option on the options popup in selection menus did not work for these types. That popup menu has now been fixed, and in addition the standard 'Only' (and 'find' etc.) button has been added to the editing panels for assemblies, 'stretches' and child mechanisms. 

Case 28463

When a mechanism or dummy positioning operation is performed, and then the result is 'rejected' the operation is reversed so that the model is restored to its original state. However this involves inverse transformations which introduce some small rounding errors, meaning that the nodal coordinates can change slightly - typically in their 7th significant figure. In itself this does not have any real engineering significance, but it does mean that if a 'Model modified?' operation is performed subsequently then these many small differences can mask any 'real' differences that might arise for other reasons. Therefore the nodal coordinates prior to positioning are now backed up and if the positioning operation is rejected the original coordinates are restored precisely from this backup. 

Case 28115

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 25

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Mechanism 'auto-make' can potentially be used to create a mechanism out of a complete model, and for a large model this can result in assemblies containing well over 100,000 node sets and parts if the model has been built in a way that contains many small weld parts. This is not a problem in itself, but when it comes to save the mechanism in the database it can overflow the internal buffers used to read and transfer data. The problem has been solved by changing the way automatically created mechanisms are stored in assemblies. Instead of a list of parts these are now all stored in a single part set. Likewise instead of a list of node sets all the nodes in these sets are stored in a single large node set. This makes no difference to how mechanism assemblies work, since they are effectively rigid components defined by elements and nodes, however it greatly simplifies their definition and storage which solves this buffer overflow problem.

Menus 

Case 28543

Added missing include selection buttons on edit panel for COMPOSITE_LAYUP.

Merge 

Case 29270

Volume 3 control cards got lost on model merge. Now fixed. 

Case 28997

Model merge could fail if one of the models was oriented immediately prior to the merge. This has been fixed. 

Case 28023

It is no longer permitted to merge the same model number. Previous attempting this action caused a crash. 

Case 27846

Node merge will no longer consider 3rd nodes on beams as long as those nodes are nonstructural otherwise. This is only applicable to the 'more cautious' mode. 

Case 27666

PRIMER would not merge nodes that were used with *LOAD_NODE_SET. This can now be done in the 'less cautious' merge mode

Mesh 

Case 29395

PRIMER could have extra unused mesh 'surface parts' after creating an *ICFD_PART definition with the keyword editor. This has been fixed. 

Case 29038

PRIMER could crash when creating a cobweb mesh if the radius and the element size for the first cylinder were the same. Now fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 26

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Model build 

Case 26129

Temporary sets created during IHI style model build using the auto-vertical option are not purged at the end of the process. This has now been fixed.

Model modified 

Case 29596

In Model modified tree viewer, keyword editor was available even if selected CESE_BNDY keywords are of different sub-types. Now keyword editor will be available only if selected CESE keywords belong to same subtype, else it will be greyed out. 

Case 28173

Primer could output 'Invalid Load Path Label' error messages when using Model Modified on a model containing Load Paths. It could also relabel load paths in the original model.

Nastran 

Case 28533

Fixed bug in convert MIG welds to RBE3 option - Nastran output.

Nodal rigid bodies 

Case 29985

When creating nodal rigid bodies using the automatic 'nearest n nodes to pick point' method the process would sometimes fail after the view had been changed. Small changes of view would not normally cause this problem but large changes, especially when zoomed tightly in to a small area of mesh, could provoke it. This was due to an internal error in the update of the projected screen space coordinates of nodes, which are used in this context, and has been fixed.

Node transform 

Case 28352

Unit conversion was not being done correctly on an *INCLUDE_TRANSFORM definition containing a *NODE_TRANSFORM card. Now fixed.

Orient 

Case 30061

The default text displayed in entity (input) textboxes in the Orient panel would previously show 'm?[n/p/s]?' even when only one model were active. The 'm?' part is now suppressed if only one model is active. 

Case 29567

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 27

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

If orient was used to orient several include files using 'consider transforms' and the include files were transforms that referred to the same *DEFINE_TRANSFORM then the transformation was added to the *DEFINE_TRANSFORM card multiple times. This has now been fixed. 

Case 29410

Opening the Orient tab without any model in memory and then reading one caused errors. Now fixed. 

Case 29165

When orienting with the include transform method, Primer was refusing to proceed if *NODE_TRANSFORM was in use. If the transform is contained in the include file, it is now used to adjust the nodal coordinates and the same check is applied as before. If it is not the user will receive a warning message but will not be blocked from proceeding. 

Case 28339

When reflecting shell elements in a model the topology was reflected. However the topology of any corresponding *AIRBAG_SHELL_REFERENCE_GEOMETRY card was not reflected which meant they did not match and LS-DYNA would not run. The topology on the *AIRBAG_SHELL_REFERENCE_GEOMETRY card is now reflected to match. 

Case 28325

When orient copy with make new part and same include options (the latter is implicit in Primer12) was applied to a selection of elements, the copied elements were correctly put in the same include as the originals but the part ended up in the master file. This has been fixed so the part will be in the same include as the elements.

Parameter 

Case 30128

Using *PARAMETER_MUTABLE caused problems when the mutable parameter was used in the label field of items. Something might get created with the first definition of the parameter, and in a few cases would not have its label updated subsequently to the revised parameter definition. Further problems could occur if, in the meantime, a latent definition of the same label was created. Now all fixed. 

Case 29058

Prior to V13, PRIMER has not read 'implicit' parameter expressions in data fields, which are actual expressions in on comma-separated input lines which behave like *PARAMETER_EXPRESSION without having an explicit *PARAMETER definition. V13 now processes these as follows: - These are read and turned into 'implicit' parameter expressions in PRIMER. - Implicit parameters are the same as ordinary ones in PRIMER in most ways, except that they are not normally shown in the top level parameter panel. - Editing panels show the implicit expression in rather than a parameter reference, and the user can add, modify or delete such expressions at will.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 28

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

- During keyword output a line containing implicit parameters has the relevant expression written out in , and that line is converted to comma-separated format. 

Case 28523

If a parameter was used in the ESORT field on *CONTROL_SHELL, Primer would always write the parameter value rather than the parameter reference. This has been corrected. 

Case 28047

Two problems have been identified with *PARAMETER definitions when units are changed in a model. (1) If a model uses a simple parameter in some context that requires a factor following a units change, and that parameter is also used in a parameter expression, problems can arise if the units conflict. This is best explained by example. There are two parameters: TIME_1 simple parameter with the value 1 TIME_2 expression parameter with the value 'TIME_1 + 1' = 2 Now consider what happens if the time units of the model are changed from seconds to milliseconds. TIME_1 changes from 1 to 1000 TIME_2 changes from 2 to 2000 However the expression 'TIME_1 + 1' used for parameter TIME_2 evaluates to 1001 which conflicts with the expected and wanted value. Previously PRIMER would fail to convert parameter TIME_2, and while any location in which it was used would correctly receive the value 2000, this would 'break' the association with the parameter, and each such data field would become a plain number. So the model would still be correct in the numerical sense, but the parameterisation would be lost. This has been fixed so that in the example above the parameter TIME_2 would be changed from 'TIME_1 + 1' (wrongly gives 1001) to '1000 * ((TIME_1 / 1000) + 1)' (correctly gives 2000) Since the evaluation is now correct the use of parameter TIME_2 in data fields that refer to it will not be broken. (2) The use of parameters on MAT, TMAT, EQN_OF_STATE and AIRBAG cards could get 'Broken' following a units change. Inside PRIMER the data fields on these cards are stored in a special way, and this meant that the association between the parameter and the data field referring to it could be lost following a units change operation that changed the numerical value. As above the value in the data field would be correct, however even if the parameter also evaluated to the correct result when scaled the connection between data field and parameter could get broken due to an internal error.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 29

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

This has now been fixed. 

Case 26892

Fixed a crash with parameters in *BOUNDARY_MCOL.

Part table 

Case 28655

The part table has been fixed to allow input of negative values for section element formulation. These are also supported for BOM input.

Part replace 

Case 29448

Part replace was blocked if the target model contained only elements and nodes (latent parts). This restriction has been removed. 

Case 29443

The merge tolerance value applied during part replace is always initially zero, meaning that all nodes will be re-attached if possible. The user sets the value to exclude nodes. Sometimes the text box retained the last used value, this has been corrected. 

Case 29351

Part assembly replace now allows replacement when parts of different element types with matching part ids are encountered. This will now work if the import section option is active. 

Case 26855

Part replace via the dialogue box did not allow long labels for the part ID's specified. This has been corrected.

Part tree 

Case 28581

A 'cloned' definition of a duplicate *CONTROL card caused a crash when an attempt was made to investigate it in the part tree. This was due to an internal error and has been fixed. Various other problems relating to the handling of clones of 'once off' (static) items such as control cards have also been fixed.

Pedestrian 

Case 30363

After quitting the pedestrian markup script, pressing [x] to dismiss Primer did not give the option to EXIT, KEEP_CP or CANCEL, it just closed straight away. This would happen if the upper leg impactor was used and the automatic calculation of the angle and mass was selected. This has been fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 30

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 29906

The algorithm for calculating the Bonnet Rear Reference offset line has been improved. 

Case 29261

The bumper zone can be extended to the outer limits of the bumper beam/cross beam structures, but the button to select these structures was inactive for the EuroNCAP v5.3.1 protocol. It has now been made active. Also, the impact point on the extreme end of the bumper zone would sometimes be given a blank label. 

Case 29229

The pedestrian markup script could calculate the head impact zones incorrectly for the EuroNCAP v5.3.1 protocol if the WAD1000 line was forward of the BLE line. This has been corrected. 

Case 29122

The pedestrian markup script did not always create enough upper leg impact points when they were on the bumper. This has been fixed. 

Case 28981

The pedestrian markup script could create lines in a 'figure of eight' which had no adverse effect on the position of impact points, but looked odd. This has been fixed. 

Case 28810

The default height above the ground for lower leg impacts was set to 25mm for all protocols. This was correct for v5 and v6 of the EuroNCAP protocol, but since v7 the height is now 75mm. The default is now set to 75mm for the EuroNCAP v7 onwards and the GTR protocol. 

Case 28802

In rare cases the pedestrian markup script could create a point for the WAD line at y=0 that was outside the edge of a selected outer surface part. It should only have gone up to the edge. 

Case 28771

The pedestrian markup script would sometimes create a duplicate adult head impact point when using the GTR protocol. Also, it sometimes did not create the child head impact point at C,0,0. These have both been fixed. 

Case 28749

When building upper leg impact models from the pedestrian markup script it used the PEDLEG_UPPER model build option. With this option you only have to specify the X and Y coordinate and then PRIMER calculates the Z coordinate by projecting vertically to the vehicle surface. This worked well if the points are on the bonnet which is near-horizontal, but not so well if the points were on a near-vertical surface, e.g. the grille. The markup script has been changed so it now uses the PEDLEG_UPPER_2 option instead which allows the Z coordinate to be explicitly specified.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 31

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 28514

The pedestrian markup script creates some temporary nodes in the vehicle model when it does the markup which should get deleted when the script is finished, but some weren't deleted. They are now. 

Case 28486

The pedestrian markup script could be slow calculating the bonnet rear reference line if the beam element length was set to a small value (~5mm). The calculation is now ~50x faster. 

Case 28369

In models where the WAD 1000 line was on a near-vertical surface, i.e. the front of the vehicle rather than on a near-horizontal surface, i.e. the bonnet, the calculated head impact points would sometimes not line up with the WAD lines. This has been fixed. 

Case 28358

The bonnet rear reference offset line calculated by the pedestrian markup script would sometimes not be offset far enough. 

Case 28223

The pedestrian markup script did not always calculate the WAD lines correctly if they were on the front grille of the vehicle rather than on the bonnet. It has been improved to give a better performance.

Penetrations 

Case 29388

For *CONTACT_FORMING the master side thickness is now treated as zero. 

Case 29268

The part pen check function has been corrected so that penetrations from self-contact are ignored in this context. 

Case 29114

'Quit' on the contact penetration summarise all panel was not closing the listing correctly. Now fixed.

Program crash 

Case 30031

PRIMER could crash if the shift + arrow key shortcut was used to unblank a model and there were empty models in the list. Now fixed. 

Case 29589

Fixed crash on popup for MMGPREF on CONTROL_ALE edit panel.

Quick pick 

Case 29155

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 32

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Added macro tag for Key in on quick pick 

Case 29087

ELEMENT_DISCRETE_SPHERE AND ELEMENT_MASS_PART can now be picked. 

Case 28356

Quick picking of joints by screen drag can trigger a crash in rare cases. This has now been fixed

Read 

Case 29960

Fixed error when reading INTERFACE_COMPONENT_NODE_TITLE. 

Case 29380

PRIMER (and LS-DYNA) sometimes fails to process an *INCLUDE_PATH statement correctly when the pathname that follows ends with Kanji characters. The was due to an error in interpreting the encoding used to represent Kanji when cleaning up unwanted trailing white space characters from the end of the string, and is now fixed. 

Case 29061

Primer now correctly finds the *INCLUDE_STAMPED include files when opening a model after another model containing include files had been opened in the same session. This works for both regular file open commands and the drag and drop method. 

Case 28957

PRIMER failed to spot that a random set of characters in the SIGY field of MAT100 were illegal, instead treating them silently as zero. That is an example of a data field which means one sort of loadcurve when positive, and a different loadcurve when negative, so processing of the field during input has to consider possible negative labels. This got confused with the internal logic within PRIMER that treats character labels as (large) negative values, resulting in the data field being assigned to a spurious character label. Now fixed: loadcurve, table and other special data fields that can have different meanings depending on their sign now detect when a spurious character string has been inserted, and treat this as an input error. 

Case 28113

When PRIMER encounters legitimate duplicate definitions in multiple include files it creates 'clone' definitions so that these are not lost. The sorting function for these used the wrong logic, meaning that if the number of clones read lay exactly on certain internal list size boundaries there could be memory corruption. These boundaries would be 4, 10, 25, 50, 100, 250, 500, and so on. Other numbers would be OK. The workaround would be to change the number of duplicate definitions by one, thus avoiding the critical list boundary numbers. 

Case 26706

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 33

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

The keyword reader in PRIMER used a method of detecting grammatical and formatting errors that was adequate in the days of LS940, but which was not really up to the task of checking more modern input decks with their more varied keywords in a rigorous fashion. It was caught between the rock of detecting too many errors, and the hard place of misinterpreting some data fields. Error trapping, and parsing of numbers for correct syntax, has now been revised to be both more rigorous and also more robust. It is possible that input decks which previously were read without warnings, despite containing errors, may now fail to read in. This is intended, since more rigorous checking of input will detect more errors. 

Case 26396

When LS-DYNA reads an input deck containing multiple (explicitly labelled) definitions of the same *CONTACT it permits all such definitions to remain in the model. Prior to R7 the multiple contacts kept the same labels, making post-processing confusing; from R7 onwards new labels are assigned to the duplicates. Historically PRIMER has treated duplicate labelled contact definitions as an error, and has rejected them. In order to make its behaviour more LSDYNA-like it now processes them as follows: It reads duplicate contact definitions unconditionally during keyword input, and gives the surplus ones temporary labels. When keyin is complete it scans these definitions looking to see if they are the same or different, and also whether or not they are referenced by anything else. Then it lists all duplicates, giving label, include file of residency, whether different or not and how many references. The user is invited to choose one of three options for dealing with them: Relabel: i.e. what Dyna does, although possibly not with the same labels; Clone: Turn duplicate definitions into PRIMER clones of the first found; Merge: Merge all into the first found, deleting the remainder. So behaviour is not totally LSDYNA-like in that the user gets an explicit warning and is forced to choose what to do, but this is considered to be the best compromise between providing error checking and imitating LSDYNA behaviour.

Renumber 

Case 30227

When using 'renumber selection' PRIMER could occasionally end up with duplicate labels if the target label range contained existing items. Now fixed. 

Case 29178

When using 'renumber selected' you could get unexpected results due to PRIMER avoiding labels used by entities which will actually be renumbered. This has been corrected. 

Case 28347

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 34

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

For CONSTRAINED_NODAL_RIGID_BODY entity labels which clash with PART entity labels after renumbering, the post-renumbering function which fixes the label clash could lead to unexpected labels. This has been corrected. 

Case 28217

Edit panel updates in Primer could previously result in spurious warnings about out-of-range labels for unlabelled types if the internal labels of those items were out of user-defined numbering ranges. This has been rectified and said warnings are no longer thrown. 

Case 27988

The visualise labels panel would not automatically refresh after using 'renumber to here' to renumber entities within the panel. This has been corrected. 

Case 27073

Conx->ID field was not being renumbered accordingly. Now fixed.

Rigidify 

Case 28562

The interface file created during rigidify was not populated correctly, which could lead to errors in 'simplify and delete'. This has been corrected.

Scripting 

Case 30199

Window border and global triad could, under rare circumstances, appear in non-standard line style (dotted) or width (thick line) when running FMH script. This has been fixed 

Case 27808

Ejection mitigation script was giving wrong results if selected part do not have thickness. Now script will throw a warning message which explains what is required, if user has selected part with no thickness. Added a few extra checks to make sure window door frame parts are properly selected. 

Case 27992

The JavaScript debugger could crash if a script was being run outside the debugger and the Interrupt button was pressed. Now fixed.

Sections 

Case 28283

Field at card 2, column 4 (for elem types 2, 12, and 13) had wrong name. Now fixed it.

Selection 

Case 29354

In contact penetration fixer, in manual mode, the selection of nodes to fix using the feature line option off the object menu did not work. This has been fixed for 'all nodes' mode.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 35

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 29118

Fixed problem in feature line picking of nodes when display of internal faces is turned on. 

Case 26693

Fixed some problems with the handling of Discrete Element Sphere (DES) types: (1) In object menus they could not be filtered by PART, nor by anything on the part card. (Nor could SPH elements.) (2) The updating of the visibility of DES elements was not working correctly, meaning that the code would probably think they were not 'visible', despite having been drawn, and therefore would not permit them to be screen-picked.

Sensor 

Case 30364

Fixed check for SENSOR_DEFINE_FUNCTION such that 0 sensors are permitted at end of card 1. 

Case 28784

Sensor define function edit panel was not working properly - Now fixed.

Sets 

Case 28605

Problem with removing segments from set - Now fixed.

Sketch 

Case 30006

Sketching latent beams after include replace crashed. Now fixed. 

Case 29890

Sketch function for *CONSTRAINED_INTERPOLATION could crash when drawing items at the edge of the screen. Now fixed. 

Case 28791

Fixed crash in sketch function for BOUNDARY_PRESCRIBED_FINAL_GEOMETRY with NID set to 0.

Spotwelding 

Case 30279

Added a check to see if the model exists while reading in spotwelds from files.

Undo 

Case 28360

Undoing deletion of *SET_SEGMENT cards did not work correctly. Now fixed. Ove Arup and Partners Limited | Draft 1 | March 2016

Page 36

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Units 

Case 28614

Corrected the units for *CESE_EQOS fields. 

Case 28582

Corrected the units for *CESE_BOUNDARY_PRESCRIBED fields. 

Case 28343

Force units are applied for F0 field for MAT 71. 

Case 28322

The internal 'plumbing' to Orient and apply units changes to *FREQUENCY cards was missing, meaning that these would not be processed correctly by these two operations. In the case of Orient this almost certainly wouldn't matter, since orienting the model as a whole would update items affected by these definitions anyway, but the units change would not work even if the whole model was selected. Now fixed.

User interface 

Case 28342

Added hover text for entity names on deletion and model check panels.

Xref 

Case 30395

PRIMER could crash when resizing the cross reference viewer after deleting an item in the viewer caused the tab to be removed. Now fixed. 

Case 29455

The cross references viewer could get corrupted if an item in the tree was edited and updated and the viewer had more than one tab open. This has now been fixed. A workaround was to press the tab again.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 37

Oasys Ltd LS-DYNA Environment Software

2.2

D3PLOT

2.2.1

Bugs Fixed in 13.0

Release Notes Version 13.0

Animation 

Case 29357

If the option was set to only animate a subset of states or interpolate states by time (Animate>Set states), the keyboard arrow keys would still step backwards/forwards one state at a time rather than going to the next one as defined by the selected option. This has been corrected.

Blanking 

Case 28765

When screen picking groups from the blank menu the ambiguous selection menu could get shown, listing duplicate groups. This should not have happened. 

Case 28684

For blanking menu with an ambiguous screen pick: when the user hovered over an item in the ambiguous pick list, what was sketched did not correspond to the item. This is now fixed. 

Case 28682

In V12 when selecting items in in the blank menu using either the 'pick' or 'area' options the deselection using the right mouse button was not working.

Component 

Case 30265

The PEMAG component was not being calculated correctly as the function assumed the strains were in Voigt notation, however this is not the case. It has been corrected, however a preference d3plot*pemag_calculation_v12 can be set to TRUE to revert to the old method if required. 

Case 30269

Internal energy density for solids was wrongly computed as 0.5*(SxxExx + SyyEyy + SzzEzz + SxyExy + SyzEyz + SxzExz) where it should have been 0.5*(SxxExx + SyyEyy + SzzEzz + 2*SxyExy + 2*SyzEyz + 2*SxzExz).

Connections 

Case 17883

In previous versions of D3PLOT the display of solid and beam spotwelds via the Entity panel was controlled by the underlying solid and beam elements. In version 13 this has been changed so that the display via the Entity panel is now independent. As solid and beam spotwelds can display both spotweld data components and normal structural components (stress, strain etc) new options have been added which control how these elements are drawn and contoured.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 38

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

By default these entities are now drawn and contoured as though they are spotwelds so they are automatically excluded from normal data components unless the display of spotwelds had been turned off. If the display of spotwelds is turned off then the solids and beams will be included for normal data components. Other options allow for these entities to always be treated as spotwelds or as normal elements regardless of the display status.

Contour 

Case 29171

If a velocity plot was generated for a model which had airbag particles the values displayed in the contour bar included velocities on airbag particles but the min/max values displayed on the plot only included nodes. In version 13 the min/max values consider both nodal values and airbag particles. 

Case 28471

A contour plot would not update if the contour levels were manually set and a ref node was selected.

Cut section 

Case 29190

In V12.1 D3PLOT added a contribution from the local Mxy twisting moment in shells to the overall calculation of bending moment in cut section. Unfortunately this was applied wrongly, resulting in the local moments in cut shells being wrong, see case 27133. (Force calculations were unaffected). This has been corrected and twisting (warping) moments due to variations of local XY shear stress through shell thickness are now computed correctly. 

Case 29115

If the current plotting mode's frame of reference had been changed from the default global to a local system, then cut section forces calculated by cutting through solid and thick shell elements would be wrong. This was because the cut section calculation presumed that it was working on a stress tensor in the global system, whereas in this situation the tensor it received had been rotated to a local system, leading the stresses being transformed wrongly. Now fixed by ensuring that the stress tensor used to calculate cut sections through solids and thick shells is always in the global system. 

Case 28179

Cut section forces through beams were wrongly always returning zero force. This was caused by an internal check for a zero length cut, which is geometrically correct for a beam, being treated as an error. Now fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 39

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Data access 

Case 29848

When extracting data from a frequency domain model with phase angles, the XY data menu would not always return the correct results. Similarly the JavaScript GetData() function could return incorrect values if the 'dda' argument was set to ON. Both these problems have been fixed.

Data components 

Case 30432

Removed invalid option to plot scalar strain components: SMAX_SHEAR_STRAIN, PEMAG_PLAST_STRN_MAG, E2D_PRINC_STRAIN_RATIO, and SAV_AVERAGE_STRAIN as principle (PR) plots. Previously could be clicked and generated repeated error messages. 

Case 30244

The PEMAG component could be calculated incorrectly if MAXINT was different to the number of integration points in a part. This has been fixed. 

Case 29330

In previous versions of D3PLOT the data component 'Resultant Moment' that could be plotted on LoadPath segments was calculated incorrectly using the torsional moment and one of the bending moments instead of the 2 bending moments. This has been fixed in version 13. 

Case 29334

In version 13 the options to display the 'Max All', 'Min All' and 'Mag All' values which look through all the integration points now work when doing principle stress plots. Previously in other versions of D3PLOT if you tried to use these options D3PLOT would reset the selected surface to 'Middle' and would display a message in the dialogue box. As well as being supported in principal stress plots the 'Max All', 'Min All' and 'Mag All' options are now supported when displaying a principal stress summary in the WRITE menu. 

Case 29320

In version 12 the data component 'Formability' which could be plotted via the 'Metal Forming' option in the utilities menu didn't set the contour colours correctly. In version 13 'Formability' has been moved into a new 'Metal Forming' data component category that can be accessed via the normal data component menu. If 'Formability' is selected a special set of contour level buttons is displayed which allows the input parameters needed to calculate the formability values to be defined. As 'Formability' has is own special contour bar then selecting it as a data component will automatically turn off any other data component selected for that window. 

Case 28670

If a model contained coincident contact surfaces where more than one contact segment had the same topology then some of the nodal based contact data components were not plotted correctly

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 40

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

as the values from each coincident segment were summed together at each node. These components included the local and global forces and the contact gap. 

Case 28625

If the user setup a user defined coordinate system to display results the data values displayed were not updated unless either 1) The data component was changed 2) After setting up the axis the user switched to either Global, Local or Cylindrical and then back to User Defined.

Deform 

Case 29375

If the ref node option was on and a component was contoured, the max min values were calculated correctly. If the ref node settings were then changed, i.e. different nodes selected or output in a different system, the max min values did not get updated. 

Case 29280

If M1 had 10 states and M2 had 20 states and you tried to set the reference state in M1 to be M2 state 20, D3PLOT would refuse to set it, clamping it to the last state number in M1 (i.e. 10). This is correct if the reference model is 'Current Model', but when the user has explicitly selected a reference model it should have been clamping it to the last state in the reference model. 

Case 29182

D3PLOT was using the wrong node when calculating relative values for Velocity and Acceleration plots (selected in Deform->Ref Node). Relative displacements were being calculated correctly. 

Case 28476

In the shift deformed menu it is possible to restrict the picking of nodes to a certain model. This did not always work and D3PLOT could refuse to select a node.

Deleting 

Case 28642

If more than one window was used to display a model, and the current states in each window were different, the element deletion status could go wrong. What in effect was happening was that the elements deleted in the most recently manipulated window could 'leak' their deletion status to the same model but different state in the other window. Now fixed.

Envelope 

Case 29269

If the state selector for envelope plots was displayed and then all of the model selection tabs at the top of the 'Data Component' were turned off then the state selector would correctly update to show no states but ERROR messages were also generated in the window D3PLOT was started in.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 41

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 26982

In version 12 and earlier it was not possible to do an Envelope plot of a X-section or Loadpath data component.

Graphics 

Case 29416

We have observed problems with shaded images on laptops running Intel HD integrated graphics cards as follows: - Only occurs in lit (shaded) plots when 'hardware shaders' are active. - Only occurs on HD 5xxx series cards, or HD 4xxx series updated to drivers of approximately mid 2015 vintage or later. The workaround for pre-V13 software was to turn off hardware shaders, but this was a poor fix on machines that had both Intel HD and also high performance NVidia Quadro or AMD FirePro cards installed, since they worked correctly and hardware shaders give a significant performance gain. Therefore V13 software now detects when Intel HD 5xxx graphics is being used and automatically suppresses hardware shaders, effectively automating the workaround. This behaviour can be modified via a preference to re-enable hardware shaders if in the future Intel fix their drivers, and in addition we will attempt to find a proper fix to the problem. 

Case 29360

If a window contains multiple models and the display of nodes is turned on then the nodes in the 2nd model could be drawn using the current background colour instead of the current 'text' colour while the nodes in the 1st model were always drawn using the 'text' colour. In version 13 the nodes for all models in a windows are drawn using the 'text' colour. 

Case 29359

If a window contains multiple models then sometimes the colour used to sketch items when using predictive picking is set to the background colour instead of the current 'Text' colour. This can make it difficult to see the item that is being sketched. In version 13 this has been corrected so the current 'Text' colour is always used. 

Case 29073

LS-DYNA can move the position of the 3rd node on a beam so that the local axes line up with the principal axes and D3PLOT did not take this into account when drawing the true beam sections. This could result in it getting drawn in a different orientation to the one defined by the user. D3PLOT now works out the angle of rotation applied by LS-DYNA about the X-axis by comparing the undeformed state (which has the 3rd node in the position defined by the user) with the first state (which may have the 3rd node in a different position). This rotation offset is then applied to the beam when it is drawn so it is in the correct orientation. 

Case 28187

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 42

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

If a model was initialised with a dynamic relaxation and NREFUP was used to get LS-DYNA to update beam third nodes, drawing true beam sections could show spurious rotations. This is because D3PLOT copies the position of the third node from the first state to the undeformed geometry (state 0) so that the correct orientation is calculated. However, for this case this should not have been done because the first state is not the initial state. If a 'd3drlf' or '.rlf' file exist in the same directory as the model the position of the third node is no longer copied to the undeformed geometry. A new preference d3plot*correct_beam_3rd_node has also been added to turn off the copying. It is on by default. 

Case 28040

In LS-DYNA its is possible to create a *DATABASE_CROSS_SECTION definition that doesn't actually cut through any elements. D3PLOT 12 was including the centroid of these 'empty' cross sections when auto scaling (AC) the plot. In version 13 any 'empty' cross section definitions are ignored when performing an autoscale. 

Case 27844

In version 12 of D3PLOT if a CT or SI plot was done of the individual X,Y or Z velocity components the data component actually plotted was the velocity magnitude. This has been fixed in V13. 

Case 27254

If the option to display beams using the true section properties is used D3PLOT can not calculate a size for discrete beams from the data available so discrete beams are drawn as either a single sphere for zero length beams or as pair of spheres connected by a line. In version 13 a new option has been added to the 'Beam Symbols' menu that can be used to control the size of the spheres.

Groups 

Case 12853

In the blank menu groups could be selected in menu list, but picking them in the graphics window did not work. It now does.

Image 

Case 30342

When a non-standard line thickness (more than one pixel thick) is set under 'Tune' this should be the standard width for all lines in all plots. However if 'Measure' was used anything which redraws the plot, such as rotation or image capture, would revert line thicknesses back to one pixel. This was because Measure uses thicker lines to show the current measurement, and after this it was resetting the thickness explicitly to one pixel rather than the current default. Fixed by ensuring that line thickness reverts to the current default.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 43

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 28657

BMP images written from D3PLOT would fail to read in some image viewing packages. This has been fixed. 

Case 28505

Previously if user made a .jpg (or other static image) with 2x (or 4x) screen resolution and a white background, the graphics window changed to a white background, until a cursor was moved over it. Now the user does not see the graphics window having a white background. 

Case 28491

If the file selected to write an image to already exists the user is given the option for a new file or to overwrite. Previously the change file format button remained active, now it is greyed out until the user chooses a new file or to overwrite. 

Case 28485

If the file selected to write an image to already exists the user is given the option for a new file or to overwrite. Previously the plot button remained active, now it is greyed out until the user chooses a new file or to overwrite. 

Case 28484

Previously the Postscript/PDF menu could have title, figure and margin button stuck on inactive after the user had plotted multiple figures. These now to return to being active.

Javascript api 

Case 30137

The JavaScript Pick() function should have written a message to the JavaScript menu to let the user know what they should be picking, but it wasn't being displayed. Now fixed. 

Case 28595

The JavaScript function IsDeleted() should check to see if an element is deleted in the current state, as set by SetCurrentState(). This was not the case and it was actually checking if the element was deleted in the state currently displayed in D3PLOT. The IsDeleted() function now checks if an element is deleted in the state set by SetCurrentState(). 

Case 28500

Using try/catch did not work properly with the D3PLOT JS API. It now does. 

Case 27220

The JavaScript function GetTopology() returns an object with information about an element, but if the element ID didn't exist the whole script would error out. It now returns a null object so the user can trap the error and carry on running the script. Similar changes have been made in the following functions, although they return JS_FALSE rather than a null object on error: GetSegmsInSurface()

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 44

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

GetCutCoords() GetElemsAtNode() GetElemsInPart() GetLabel() GetPid() GetMid()

Memory 

Case 29160

If a model contained MIG lines defined in PRIMER then D3PLOT could crash when exiting if the model had been read in and a ZTF file containing MIG line information had also been read into D3PLOT. 

Case 28124

In D3PLOT 'Memory' button shows both physical memory (RAM) usage by this application on its top line, and overall virtual memory consumption on the machine as a whole (bottom line). On Linux platforms only the virtual memory line was being calculated wrongly, in effect measuring just swap space usage from (swap used / total swap). While this was not an unreasonable way of measuring load on the system it tended to give an unreasonably pessimistic result for machines that had less swap space than RAM. Therefore this calculation has been revised to calculate (ram used + swap used) / (total ram + total swap), which is much closer to the way this figure is calculated on Windows systems, and gives a better measure of how close the machine is to running out of resources.

Menus 

Case 30420

The Averaging popup menu did not update correctly if there were multiple windows open and they had different settings. Now fixed. 

Case 29140

In version 13 the 'Window' tabs which are displayed at the top of the 'Data Component' and 'View' menus when multiple windows are being used are linked so that selecting a tab in one menu also selects the same tab in the other menu. This is a change of behaviour since V12. 

Case 28762

D3PLOT could crash if you hovered over a joint in an object menu, e.g. in the blank menu and predictive picking was on. 

Case 27766

In version 12 it was not obvious to the user that if they had multiple windows open and changed the contour bar limits from 'Automatic' to 'Max & Min' the values displayed in the text boxes

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 45

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

were only those that were being applied to the 1st active window and that other windows would have their own Max and Min values. In version 13 the text boxes that display the Max and Min values are now drawn with a washed out background colour if the same Max and Min values are not being applied to all the active windows. The same logic has also been applied to the text box that displays the number of contour levels and the min and max values displayed under the 'Limiting Values' tab. 

Case 27755

If the colour palette was used to select the 'fill' colour used for VECTOR plots via the 'Data Menu' (Data=>(under Contour Options)=>Vec Plots tab) then it would sometimes be displayed filling the whole screen and other times it wouldn't appear at all.

Movies 

Case 29033

When recording MPEG movie if a window resize was required, on occasion D3Plot would resize the wrong window. Now it resizes the correct window. 

Case 28622

Previously writing movies (on Windows) would not capture the entire image - it would be zoomed in - if the static image resolution was not screen resolution. This is now fixed. 

Case 28517

Previously writing movies (on Windows) would not capture the entire image - it would be zoomed in, if the static image resolution was not screen resolution. This is now fixed.

Multiple windows 

Case 29892

If you went through the following sequence: Start D3PLOT Open model in W1 Close W1, but choose to 'leave' the model in the database Open a new model in W1 Then things got very confused, with a second window being opened and almost certainly a crash. This was because it was getting confused about having no windows, but an existing model. Now fixed.

Nastran 

Case 29973

If a Nastran input file had 'PARAM,OGEOM,NO' set then D3PLOT would issue the error message 'failed to allocate space for nip data in d3_read_op2_properties' when trying to read the resulting OP2 file and could then crash. Ove Arup and Partners Limited | Draft 1 | March 2016

Page 46

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Having 'PARAM,OGEOM,NO' set means the model geometry (nodes, elements, parts) is not output to the OP2 file, but D3PLOT requires that it is. D3PLOT now checks that it has read the model geometry and abandons trying to read the model if not, issuing a more useful error message to let the user know why. 

Case 29069

A Nastran OP2 file was crashing because of an internal error when reading RBE2 elements. 

Case 28688

Nastran OP2 results files that had an initial static subcase followed by a different analysis type subcase, e.g. modal analysis, would get displayed incorrectly as a static analysis. This meant that only the phase angle was written at the bottom of the graphics window, but not the frequency. It now writes both.

Quick pick 

Case 28798

Previously if Quick Pick - Locate in Part Tree was used for Entities there was an error message. Now it locates the relevant shell/beam/etc in the Part Tree.

Read 

Case 29876

D3PLOT could fail to read all the 'states' in a D3EIGV file as it was assumed that the states would be written to the file in order of increasing eigenfrequency. It turns out that the modes are written out in order of increasing eigenfrequency magnitude. 

Case 29817

If a full deck restart was carried out in LS-DYNA and the PTF files were given the name 'd3plotaa' then D3PLOT would think that these files were part of a model containing adaptivity if the original 'd3plot' were also in the same directory. This is because the default naming convention used by LS-DYNA when a model with adaptivity generates multiple set of results is d3plot, d3plotaa, d3plotab ... If the number or parts had been changed as part of the full deck restart this would cause problems as D3PLOT assumes that the number of parts is constant during an adaptivity run and it's just the number of nodes and elements that change. In version 13 the number of parts is now checked and if they are different the 'd3plotaa' series of files are ignored and an message is displayed in the dialogue window telling the user to move the 'd3plotaa' files to a new directory and to read then in as a separate model. 

Case 29624

If a transform was applied to a model and the model was then re-read the transform would be lost and would have to be re-applied. In version 13 the transform is automatically re-applied after the model has been reread. 

Case 29142

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 47

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

D3PLOT 12 could crash if a model containing airbag particles was read in and the model was animated to show something like 'Leakage' before the user has stepped through the states. The problem was caused by multiple threads and would not show up with all models and systems as the crash would depend on how the multiple threads interacted. A work around in V12/12.2 is to set the ENVIRONMENT variable 'D3PLOT_NO_READ_AHEAD'. 

Case 28320

D3PLOT could crash when reading in a model which contained parts which had been defined using character part labels. the crash would occur in 2 situations. 1) All of the parts used character part labels. 2) Any parts that did not have character part labels were numbered sequentially from 1. 

Case 29528

If a file was dropped onto the main D3PLOT window (using drag and drop) when D3PLOT 1st started and the 'Open Model File' window was displayed then D3PLOT would read in the model and then crash. This has been fixed in V13. 

Case 29126

D3PLOT 13 now supports the D3EIGV eigenvalue solution files named 'd3eigv1', 'd3eigv2'... which can be generated by a transient frequency domain analysis. 

Case 29125

D3PLOT 13 supports the new D3EIGV_AC file format that is generated by the *FREQUENCY_DOMAIN_ACOUSTIC_FEM_EIGENVALUE keyword. 

Case 29075

Version 12 of D3PLOT would crash if a model containing *STOCHASTIC_SPRAY_PARTICLES or *STOCHASTIC_TBX_PARTICLES was read in. Version 13 does not currently support the output generated by these cards. If a model containing a Stochastic Particle Domain is read in D3PLOT now generates a message warning the user that the domain type isn't supported but continues to read the rest of the data in the model. 

Case 27172

When a volume 3 analysis (ie CESE, ICFD, etc) was running and the 'Rescan states' option in D3PLOT was used to look for further states that might have been written it would look in the wrong disk address and thus pull out numbers which it 'thought' were times, but in fact were some sort of data. This would give both the wrong time and also tend to report time reversals and other errors; furthermore if this corrupt data was used then it could lead to a crash. A 'Reread' of the model from scratch worked fine. Now fixed: it now looks at the correct disk address, picking up new data correctly. 

Case 26695

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 48

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

D3PLOT has historically been limited to 2 GWords (8 GBytes single precision, 16 GBytes double) when reading individual files in a results dataset, although there is no practical limit to the overall size of the dataset. This limit is now removed, and individual files may now be of any size (up to a theoretical limit of 9 Exawords, ie 3.6e19 bytes in single precision).

Scripting 

Case 29283

WebGL files created from D3PLOT always used the undeformed state instead of the current state. Now fixed.

Selection 

Case 28678

In V12 when selecting items in the blank menu using either the 'pick' or 'area' options the deselection using the right mouse button was not working.

Shortcut 

Case 28654

If the option was set to only animate a subset of states or interpolate states by time (Animate>Set states), the keyboard arrow keys would still step backwards/forwards one state at a time rather than going to the next one as defined by the selected option. This has been corrected.

User defined 

Case 29080

D3PLOT saves user-defined binary data in .ubd files, and the names it generates for these have many leading zeros. For example my_job_0000000001.ubd. A problem has been reported, but cannot be reproduced, that the 10th such data component file fails to read back in as written, but that deleting some of the unnecessary leading zeros causes it to be read. However the internal logic that generates all these leading zeros is unnecessary and has been removed, so in the future files will only have a single one, for example my_job_01.ubd.

Utilities 

Case 30277

Compressing a model that contained rigid shell compression (DCOMP=2 on the *DATABASE_EXTENT_BINARY card) using the Utilities->PTF compress function could result in a corrupt output file. This has been corrected. 

Case 29964

The Utilities->PTF Compress function did not allow you to deselect the stress tensor and plastic strain components for solid elements. This restriction has been removed. 

Case 28624

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 49

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

When writing a reordered database (Utilities->Compress) extra, random data could be written to the file if all of the available LSDA components were not selected. This would result in a file that either could not be read into D3PLOT, or the coordinates of nodes would be wrong. 

Case 28615

D3PLOT would crash when writing a reordered database (from the Utilities->Compress menu) from a model containing DATABASE_CROSS_SECTIONs read from the ZTF file, but with no LSDA (binout) file. This has been fixed. 

Case 28382

In the PTF compress menu for selecting states, if there were multiple models in a window D3PLOT could crash or select random states. This has been fixed. 

Case 28282

Using Utilities -> Compress with multiple models now correctly allows user to change between models when selecting states and parts.

Views 

Case 29352

If multiple models were loaded into a single window and a previously saved view was restored using the 'View manager' window the view was not applied correctly to all of the models. This would cause problem when the view was later updated by rotating/zooming.

Write 

Case 30270

If a model contained beams which were oriented using an orientation vector rather than a third node and the WRITE->KEYWORD function was used, D3PLOT could crash. This has been fixed. 

Case 28305

If the WRITE menu was used to display the list of nodes for a Joint then the wrong node numbers were displayed as they were all shifted right by one position if for example you had 2 joints defined as follows Node 1

Node 2

Joint 1

17

18

Joint 2

20

21

Node 3

Node 4

22

23

Node 3

Node 4

Then these would have been displayed as

Joint 1

Node 1

Node 2

1

17

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 50

Oasys Ltd LS-DYNA Environment Software

Joint 2

1

Release Notes Version 13.0

20

21

22

XY plot 

Case 29331

For models with phase angle data, the XY Data menu would plot either Magnitude or Magnitude * cos(phase+phi) depending on what was selected from the popup menu in the main data menu, which was confusing. A popup has been added to the XY Data menu so it can be controlled independently of the main data menu. 

Case 29035

The labels did not match the curves in a .cur or .csv file written from the XY Data function if the curves were sorted by anything but the default order (e.g. by Y-mag).

ZTF file 

Case 29856

If a D3PART file (created using *DATABASE_BINARY_D3PLOT) was read into D3PLOT along with a ZTF file D3PLOT could crash. The problem was the ZTF file contain lots of information for things that don't exist in a D3PART file as this is just a subset of the original model. For version 13 an additional test has been added and if the file is a D3PART file the ZTF file is ignored and a message is written to the dialogue box.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 51

Oasys Ltd LS-DYNA Environment Software

2.3

T/HIS

2.3.1

Bugs Fixed in 13.0

Release Notes Version 13.0

Component 

Case 30457

The PEMAG component was not being calculated correctly as the function assumed the strains were in Voigt notation, however this is not the case. It has been corrected, however a preference this*pemag_calculation_v12 can be set to TRUE to revert to the old method if required.

Curves 

Case 28360 The symbol frequency on graphs now updates immediately when the frequency is changes in the Display menu.

FAST-TCF 

Case 29400 The command to extract airbag part data, e.g. ab_part 1 1:100 maf tag part##maf tagged all the curves with part1maf, i.e. it substituted the ## with the airbag ID. In this case it should substitute it with the part IDs, i.e. part1maf, part2maf, part3maf, etc... 

Case 29282 If the FAST-TCF command to create part groups (gdef ) was too long (over 1000 characters), T/HIS could crash. The command is now truncated along with an error message. 

Case 28633 If a FAST-TCF script read data from a source other than a model, a CSV file for example, and it read a datum definition the script would not run.

Graphs 

Case 28160 If a curve was plotted on the Y2 axis, the Y2=Y=0 switch was turned on and then the graph was auto scaled, the curve could get wrongly plotted if the minimum value on the Y1 axis was zero. 

Case 28157 If a curve was plotted against the 2nd Y-axis and then 2nd Y-axis was turned off, auto scaling the graph did not work. 

Case 28186

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 52

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

If the model prefix option was used and set to 'directory' for a model which only contained the old ASCII LS-DYNA output files then the directory would not be displayed, instead the model number would still be shown.

Javascript API 

Case 30032 The Operate.Zero(), .ZeroX() and .ZeroY() methods all generated an error if only one argument was passed to them. This was incorrect and has been fixed. 

Case 29601 If a JavaScript was run that used the DialogueInput function to set the integration point used to read beam data then following the command T/HIS could get stuck in a loop displaying the following message. %%%ERROR%%% Invalid command /_J_DIALOGUE_END 

Case 28531 The Curve.First() function should have returned NULL if there were no curves loaded in T/HIS, but the script exited with an error instead. It now returns NULL. 

Case 28501 Using try/catch did not work properly with the T/HIS JS API. It now does.

Menus 

Case 29303 In T/HIS there are a number of places where curves can be deleted, blanked or have their properties like colour/line width modified. If the Curve Table or Curve Manager were being displayed while these changes were made then the contents of the Curve Table or Curve Manager didn't always update immediately.

Operations 

Case 30030 The Operate->R-AVE function was incorrect if the first point was not at X=0.

Quick Pick 

Case 27952 If a lot of curves were selected using Quick Pick and deleted T/HIS could appear to hang. The problem was caused by T/HIS updating the contents of the curve manager window once for each curve as it was deleted. T/HIS now updates the curve manager once after the last selected curve has been deleted.

Read 

Case 29962

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 53

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

If a channel in a DIADEM file did not have any data then T/HIS would crash. This has been fixed. 

Case 29149 T/HIS could crash when trying to read in a CSV file with only one column of data. It now issues an error message to let the user know that they need to change the file format to X,Y,Y,Y and turn on the option to generate X values. 

Case 28577 In some situations T/HIS would think that a model contained shells with multiple in-plane integration points when in fact it didn't. 

Case 28558 T/HIS could crash when reading data from the PLLYOUT ASCII file. 

Case 28224 T/HIS could crash when reading acceleration magnitude data from the binout file, from a model using *FREQUENCY_DOMAIN_RANDOM_VIBRATION. 

Case 28158 T/HIS would fail to read the names of items correctly from the LSDA (binout) file from files created by recent versions of LS-DYNA. This problem was caused by a change in the format used to store the name information within the LSDA file. 

Case 27049 CSV files written from the D3PLOT menu can now be read into T/HIS. The Write->Entity and Write->Scan formats are both supported.

T/HIS Link 

Case 29250 When using the D3PLOT->T/HIS link if T/HIS opened a model containing a corrupt THF file then an error message would be correctly displayed but after displaying the message D3PLOT would fail to correctly position all of the T/HIS windows and menus. 

Case 29248 After doing a model rescan in the D3PLOT side of the D3PLOT->T/HIS link the option to 'overwrite existing curves' in T/HIS was left turned on as T/HIS has silently enabled this option so it can update the curves of the model being rescanned. In version 13 the status of the 'overwrite existing curves' option is restored to it's original value after all the models have be rescanned and curves rebuilt.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 54

Oasys Ltd LS-DYNA Environment Software

2.4

REPORTER

2.4.1

Bugs Fixed in 13.0

Release Notes Version 13.0

Capture 

Case 27581

Old style command file lines (the lines have numbers after column 81) could not be added to a D3PLOT object after a capture. This is now fixed. 

Case 28211

Generating a D3PLOT object that read Nastran results from an OP2 file caused D3PLOT to hang.

General 

Case 28814

For pelvis force reported for WorldSID based tests (side pole and MDB), the curve was multiplied by -1 when it was not required. This has been corrected. 

Case 28630

In various standard templates, the neck exceedence was not calculated correctly. This has been fixed. 

Case 28611

The bending moment in standard templates was not calculated correctly. This has been corrected.

Generate 

Case 27384

The numbering of 'generated' items on a page missed out tables. Tables have been added as they can contain scripts that need to be generated.

Javascript API 

Case 28332

If the name argument in the Item constructor was given it was ignored. This is now correctly used. 

Case 22881

The Variable class now has properties for the variable precision and format.

Powerpoint 

Case 29325

The page background colour was not being used when writing PowerPoint.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 55

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Additionally the page background colour can now be inherited from the page master.

Standard templates 

Case 29959

The EuroNCAP FFB standard templates only checked the positive values of neck shear. It now looks at both the positive and negative values and reports the one with the highest magnitude. 

Case 29958

The neck compression values reported in the IIHS ODB and SOB standard templates were incorrect. They were actually showing the tension values. 

Case 29402

The EuroNCAP head impact templates did not work with models run using the *CASE keyword. This has been fixed. 

Case 28770

The EuroNCAP and GTR head impact templates were crashing if the .lst files contained points that had been manually created in the pedestrian markup script. The templates expect the filenames of each impact point to be in the format A__.key, but for manually created points they are A_.key, which caused the template to crash. For the EuroNCAP templates these points are now ignored. For the GTR template they are processed as a valid points. 

Case 28628

In the standard templates, for assessments that had variable limits, e.g. neck shear exceedence, the calculation could be wrong if the model time unit wasn't milliseconds, as this is what the time axis of the limits was using. This has been corrected so it now converts the time axis to the model units. This affected the following templates: CNCAP_Front_ODB_Impact_2012 EuroNCAP_Front_ODB_Impact_2014 EuroNCAP_Front_ODB_Impact_2015 IIHS_Front_ODB_Impact_XIV IIHS_Front_SOB_Impact_II 

Case 28627

In the standard templates, the calculation that converts the chest rotation to compression could sometimes get the sign the wrong way round. This affected the following templates: CNCAP_Front_ODB_Impact_2012 EuroNCAP_Front_ODB_Impact_2014 EuroNCAP_Front_ODB_Impact_2015 IIHS_Front_ODB_Impact_XIV IIHS_Front_SOB_Impact_II

Text 

Case 29173

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 56

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Text in textboxes had different line spacing when writing a PowerPoint file. Additionally text size, spacing and wrapping is now much more consitent between REPORTER, Acrobat and PowerPoint files

User interface 

Case 29326

On windows the dots per inch for the monitor was not determined correctly if you were not running at the recommended monitor resolution. This has been fixed.

Variables 

Case 29141

REPORTER could crash if you edited an argument for a Library program, right clicked and used 'Insert variable' or 'Modify variable'. This is now fixed.

Write 

Case 28661

Cropped images were not written to PowerPoint correctly. This has been fixed.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 57

Oasys Ltd LS-DYNA Environment Software

2.5

Shell

2.5.1

Bugs fixed in 13.0

Release Notes Version 13.0

Menus 

Case 30286

If you pressed the Quit button in the Kill Options menu it would stay pressed even if you selected another option.

Multiple jobs 

Case 30299

If a *.lst list file was selected before changing the file format to List then the shell would issue a warning when submitting the job saying it was unable to create a .bat file. If the file format was changed to List before selecting the *.lst file, the job submission was OK. It now does not matter which order this is done in.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 58

Oasys Ltd LS-DYNA Environment Software

3

Release Notes Version 13.0

Enhancements

The enhancements and bug-fixes for each program have been broken down into a series of topics. Within each topic enhancements and bug-fixes are listed by case ID (most recent first).

3.1

PRIMER

3.1.1

Enhancements in Version 13.0

Airbag 

Case 20588

Made DATABASE_CPM_SENSOR a drawable entity.

Bom 

Case 27793

Added an option to select parts on BOM write panel. This option is available for both EXCEL and CSV file format. 

Case 24802

In 'BOM Write panel', added ability to export PART images to excel sheet.

Belts 

Case 27872

When (re)fitting a seatbelt where database cross-sections are generated it can be hard to work out which cross-section has been created where. It is now possible to control the cross-section start labels in both manual and auto-refit meshing modes, and in addition the feedback given when a belt is meshed now states explicitly the label and position of each cross-section that has been created. 

Case 27871

In PRIMER V12 the ability was added to define a parameter during seatbelt fitting whose value is updated to be the overall belt length. This feature has been extended so that if the relevant option is chosen a further parameter is created for each segment of the belt that contains the length of its segment. Rather than define a succession of individual names the parameters use the overall belt length parameter name with _s1, _s2, etc. added for segment 1, 2, etc. 

Case 26595

There have been several requests for the seatbelt fitter to provide an alternative to *ELEMENT_SEATBELT_SLIPRING in the form of explicitly meshed elements wrapping round a tight radius.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 59

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

This has been added as part of the seatbelt improvements in V13: sliprings can now be 'meshed' around a user-defined radius. This requires shorter elements, and the size of these together with their extent in the straight belt mesh either side of the slipring can also be controlled. 

Case 30464

A new Fitting Options panel has been added to the belt fitter that is an interface to the following new features and enhancements: The shape of the belt path interpolated from the basic path points can now be a cubic spline as before, or linear, or the average of these. Belt path visualisation has been improved: the default is now a fully shaded and lit path that is drawn using the true belt thickness. Wireframe display, the previous method, is still available. It is now possible to restrict display of the belt path to only a single segment, as well as the default of all segments. The belt fitter now automatically switches the display of shells in the dummy and vehicle 'structure' to be 'True thickness'. This not only draws shells in their true thickness but also includes any offsets from the nodal plane. This makes fitting of the belt in tight goemetries easier since the actual clearances can be visualised. Belt-to-belt self contact during fitting can now be turned on or off, with the option of using a greater thickness initially that ramps down to the actual thickness over a defined number of iterations. Initial depenetration of the belt from the 'structure', and also where regions of belt path selfpenetrate, is now available as an option. It is intended to sort out minor errors in the initial path definition which previously might have caused the belt to get stuck on the 'wrong' side of the structure. The belt-on-belt depenetration can also resolve which segment of belt should be 'in front' where two segments overlap and penetrate one another. Various other existing settings which were previously hard to access during belt path creation have also been duplicated on this fitting options panel, making them quicker and easier to use.

Checking 

Case 29024

Detailed listings for errors and warnings can now be accessed by a dropdown on the category branch of the check tree. 

Case 28479

Primer Check function will now output warning in following cases if *NODE is in an INCLUDE_TRANSFORM has a negative 'SCALE' value in its DEFINE_TRANSFORM: 1. If any *AIRBAG_REFERENCE_GEOMETRY keyword references the Node. 2. If any *AIRBAG_SHELL_REFERENCE_GEOMETRY references the Shells that in turn reference the Node. 3. If any *AIRBAG keyword references parts/part sets that in turn reference the Node through any of parts' elements. 

Case 28048

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 60

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Primer now reports an error if an empty Part/Segment SET is referenced in *AIRBAG. 

Case 27859

Following info will be listed in error file generated by the primer batch check: 1. Which master file has been checked; 2. Which oa_pref files have been used; 3. Which error config file has been used; 4. Summary of total number of Errors and Warnings; 5. All include files. 

Case 27838

A command line argument -ignore_user_pref has been added which means oa_pref file in user's home area and any such file in the current working directory will be ignored. The system oa_pref file will be read and any file specified by the -pref option on the command line. 

Case 26798

Updated the part crack check implementation. Updated the part crack warning message to: 'Acute free edge angle in part mesh – may suggest cracks' 

Case 26476

Added preference zero_volume_warning to control warnings about elements of zero volume. 

Case 26329

Model checking in V13 is significantly faster than in V12. Particular effort has gone into reducing the time taken to check larger models, where the 'n squared' effects of some loops can dominate the time taken. For a typical 5m element model V13 performs the standard checks in about 65% of the time of V12; for a 20m element model it takes about 55% of the time. (Model size alone is not a reliable indicator of the time taken, since the details of model contents will influence the time taken, but these figures are indicative of the improvement in speed.) 

Case 25864

Primer now warns if MAT24 or MAT251 table curves end in negative slope 

Case 24870

New options have been added to refine the model check performed to identify free-ended beam and discrete elements. Users can now optionally choose to report errors for rigid elements and also to report errors only when both nodes are free.

Coating 

Case 27869

Implemented Coat Thick Shells faces with Shells and Segments.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 61

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 23343

A new JavaScript (beams_on_element_edges) has been added to Primer that automatically creates beams along edges of selected shells and solids.

Compare 

Case 26677

Primer's 'Compare' tool and the Part Compare functions now both include options to highlight holes (gaps) in entities that are being compared. The two sets of entities are highlighted using different line colours and styles.

Composites 

Case 28530

Populate Ply IDs in composite shells after keyin automatically. 

Case 24599

A check has been added to ensure that composite plies do not have mesh discontinuities.

Connections 

Case 26854

Added ability to read 'master connection file' from command line interface. 

Case 26100

Added the ability to filter connections by the XML filename they were read from. 

Case 25048

Added ability to compare connections a) Across models. b) Model vs Connection file. 

Case 20668

Primer connection method now supports library connector which allows user to import their own FE model as a bolt type connection.

Constraints 

Case 28674

In Constrained Nodal Rigid Body (NRB) panel, made some changes to 'edge of hole' method to allow picking of multiple holes to NRB node set.

Contour 

Case 30003

Contour limits, as specified by clicking on contour bands, will now be reset if CT, SI or Node plot buttons are clicked or if the corresponding shortcut keys are pressed. Ove Arup and Partners Limited | Draft 1 | March 2016

Page 62

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 27865

Added a new menu in 'Contour Level & Value Format settings' dialog to control display text of values of contour bars.

Crash test setup 

Case 25060

New Frontal Oblique Overlap crash test added to crash test setup JavaScript.

Database 

Case 27009

In DATABASE_CROSS_SECTION edit panel, added an option to auto-create/append the title of database Xsecs showing the coordinate of the plane. By default, it is turned off. Added a preference 'add_database_xsec_location_to_title' for this in case user want to turn it on all the time.

Deleting 

Case 26255

An 'Xrefs' option has been added to quick pick to open the cross references panel. 

Case 15300

Deletion has been added to the right click popup on the part tree when in 'contents' mode. 

Case 14633

A deletion option has been added to the right-click popup on the cross references panels. 

Case 12542

'Remove' has been added to the right click popup in the part edit panel contents list.

Dummies 

Case 27548

Added an option 'Consider encrypted materials' on dummies positioning panel. If the 'Consider encrypted materials' option is ON, and a part material type is not specified or it is encrypted, the following extra rules are used to determine material types of parts, and hence if a node on a part is rigid or not: 1) If a part has a title containing 'rigid' (upper or lower case), the material is assumed to be *MAT_RIGID; 2) If a part has a title containing 'null' (upper or lower case), the material is assumed to be *MAT_NULL; 3) If a part is referenced by a *CONSTRAINED_RIGID_BODY/EXTRA_NODE card it is assumed to be *MAT_RIGID;

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 63

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

4) If a part references a section card of type BEAM with an elform of 6 it is assumed to be *MAT_LINEAR_ELASTIC_DISCRETE_BEAM; 5) If a part references a section card of type DISCRETE it is assumed to be *MAT_SPRING_ELASTIC.

Edit 

Case 28329

Added two separate buttons for 'Add' and 'Remove' Nodes for *CONSTRAINED_INTERPOLATION. 

Case 25446

Added a generic Find/Only button to most edit panels.

Element quality 

Case 21362

'TimeStep' and 'Added Mass' are two new criteria added to calculate Quality Imperfection Contours. Also added these fields for Failed Criteria. Also added the weight factor preferences for these two into Preferences dialog. Also these two criteria will be added into Utilities>Summary output.

Elements 

Case 29012

Add a new 'Convert' button to MESH_SURFACE_ELEMENT dock window. This button converts SHELL Element to MESH_SURFACE_ELEMENT. 

Case 27870

Align Operation is now supported for Thick Shells. A Check button 'Swap to side faces' is introduced in the dialog UI to provide user an option if the align operation should allow thick shell top and bottom faces to swap to side faces. 

Case 27834

Added normals align and reverse normals functions for thick shells. Implementation is analogous to that done for same function of Shells. Added an extra check button to allow user to choose whether to swap to side faces of thick shells while aligning of normals or directions. This button gives user an option to choose whether to swap to side faces of thick shells while aligning of normals or directions is done. With this button “OFF”, the Normals/Align behaviour is same as that of Shells. The “Reverse normals” or “Make Consistent” operations would just swap TOP and BOTTOM faces of Thick shells. With this button “ON”, the Normals/Align behaviour is same as that of Solids (except for 6 node thick shells, where swapping to side face is NOT allowed.)

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 64

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Explode 

Case 29254

A selected include and its connections to other includes in the model can now be viewed in Primer. Relevant includes are also automatically exploded away from others and unconnected includes hidden from view. Connections, in this context, include elements, constrained types and tied contacts. Users may choose to consider either all includes for connection or a subset of those. Users may also choose to display (or hide) connection labels.

Geometry 

Case 25434

JT files can now be read from PRIMER. Only the tessellation is read from the files 

Case 21618

Added menu Mesh->Surf to create geometry from mesh.

Graphics 

Case 28169

PRIMER handles duplicate definitions by creating internal 'clones' of the true original in other include files, but these are a bit hidden away and have not previously been something that can be drawn, edited or inspected at all. There is now a 'Clones' option under the 'Other' tools menu button which allows them to be created, edited, deleted, sketched and generally processed just like any other keyword. In addition the treatment of duplicate nodes is a special case in LS-DYNA, with multiply defined coincident nodes in different include files being a legitimate way of stitching models together. PRIMER handles this using clones as well, but hitherto it has not been possible to inspect these nodes visually. There is now a special 'Clones' button in the NODE panel which allows duplicate nodes to be sketched and labelled on the plot. 

Case 25436

Primer now includes an 'Exploded view' function that allows users to push selected parts, part sets, includes, or part tree assemblies away from other items of the chosen type to obtain the desired view. Users may choose to stretch parts that are meshed together to obtain a more organic view or opt to ignore shared nodes entirely when shifting parts away from one another. Various options for controlling explosion centre, direction and spacing are included. 

Case 24832

Added ability to only/sketch *DEFINE_FRICTION rows.

Image 

Case 24480

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 65

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Improvements to 3D PDF writer including: - Portrait/Landscape (default) and paper size options are now available; - Defaulted to open in fit to page mode so that scrolling not necessary; - Include files show up in 3D PDF Model Tree;

Include 

Case 27813

Use of INCLUDE_PATH with a relative filename is now reported as an error and Primer offers autofix by converting the invalid definitions to INCLUDE_PATH_RELATIVE. 

Case 24821

Made Primer able to read ANSA include ranges.

Include transform 

Case 27906

Added an option to see original coordinates if the *DEFINE_BOX is present in *INCLUDE_TRANSFORM. 

Case 27518

Added an option 'Re-Order' on include tree right-click menu panel. It will allow users to reorder include files in alphabetical order or numerical order.

Initial 

Case 28053

Added new button “Multiple” in stacked menu to create Multiple INITIAL_FOAM_REFERENCE_GEOMETRY (I_FRGM) cards from current nodal coordinates.

JavaScript API 

Case 29398

Added an option to write the include file into the same directory. 

Case 29397

Widget images can now be scaled to fill the widget. Additionally a transparent colour can be defined for the image. 

Case 29028

The title of an hourglass card can now be set in the Hourglass class. 

Case 29001

Created JavaScript global class functions 'SetPreferenceValue' and 'GetPreferenceValue'. 

Case 28483

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 66

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Model.Check can now write the file as JSON. This makes it easier for a script to parse the errors. 

Case 28162

The XML parser can now parse UTF-8 encoded XML files 

Case 27975

Added new JavaScript API class for *DEFINE_CONSTRUCTION_STAGES 

Case 27974

Added new JavaScript API class (Boundary) PrescribedOrientationRigid 

Case 27962

Added function Set.Empty to JavaScript API. 

Case 27961

Added new argument force to JavaScript member function Model.DeleteInclude 

Case 27960

Files can now be written using UTF-8 encoding for text 

Case 27959

Added new class (Boundary) PrescribedAccelerometerRigid for JavaScript API. 

Case 27956

Added new class (Define) ElementDeath to JavaScript API. 

Case 26820

The new line can now be omitted when using Message(). 

Case 26640

Added a JavaScript API which returns true if a Part is cut by a Cross Section. 

Case 26308

Added ability to set/unset model tabs active option. 

Case 26306

A new Widget.ClearSelection() method has been added to be able to clear any selected WidgetItems. The selected property for a WidgetItem is now writable. These 2 changes allow widgetitems to be set/cleared programmatically. 

Case 26304

Added Browse function for JavaScript keyword classes. 

Case 26303

Added new sketching options in JavaScript API for SPC.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 67

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 26301

The method Window.MiddleBorder() has been added to return the position of the border between the tools/keyword window and the docked window. 

Case 26300

Added JavaScript API to reverse/make consistent shell normals. 

Case 26294

Added JavaScript API classes (Airbag) ReferenceGeometry and ShellReferenceGeometry. 

Case 26267

GetFlagged() method added to the Primer JavaScript API. This function returns an array of flagged objects of a particular class - and, additionally, of a given type in the case of the Set class - for a specific model. 

Case 25808

Added new JavaScript API class (Element) MassPart. 

Case 25797

Added new JavaScript API class (Initial) StressSection. 

Case 23703

Added an extra argument 'option' in SET constructor JavaScript API to create set _ADD, _INTERSECT, _GENERATE and _GENERAL. 'add', 'intersect', and 'generate' properties are writable now. These properties will be applied if the set is empty. 

Case 22943

Added new JavaScript API class (Element) DiscreteSphere 

Case 22776

A new model property has been added to classes so the model an object is in can be found 

Case 19841

Added Airbag class to JavaScript API. 

Case 19162

Added Timestep functions to JavaScript API classes Beam, Discrete, Seatbelt1D, Solid and Tshell.

Keyword 

Case 27845

NSOLVR value 12 in Control_IMPLICIT_SOLUTION is added.

Kwd editor 

Case 28572

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 68

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Added ability to export data from keyword editors as keyword or CSV file. 

Case 26143

Some *INITIAL cards, notably *INITIAL_STRESS or STRAIN, have the potential to have many rows of data. For example *INITIAL_STRESS_SHELL may have one or four integration points on plan, and open-ended number of integration points through the thickness, and also an open-ended number of 'extra' variables at each integration point. This means that the keyword editor for these cards may have to show a very large number of data fields, and in a model with different values for these parameters many data fields may be present on one element but not on another. In order to manage this in a sensible way these keyword editor panels have user-defined settings which allows the user to limit display to a given number of integration points, extra variables, etc., etc. However this also means that in a model with mixed attributes a keyword editor panel may not be showing all possible cards of the given type. For example in a model with initial stresses defined for fully-integrated shells the quadrilateral elements will have four integration points on plan, but the triangular ones will only have one. Therefore the editor will show 'all quads' or 'all trias' but not both at the same time, and this is not obvious to the user. To try to prevent confusion these keyword editor panels now scan the model before displaying themselves, looking for instances of different values of these user-defined parameters. If any such cases are found a warning message is given that lists the range of values and explains what is happening, so that the user will no longer be taken by surprise. 

Case 24834

For *DEFINE_FRICTION card- sort option based on friction parameters has been added to edit panel 

Case 20667

Added formula input to edit panels, keyword editors and other menus.

Measure 

Case 27866

Added one more measure option 'Node Curve Length'. Selecting the button will bring up two options i.e. 'Multi Node Curve' and 'Free Edge Node Curve'. Selecting 'Multi Node Curve' will allow picking nodes and getting the distance of this created path. The distance would be cumulative based on all nodes picked and 'Free Edge Node Curve' option will allow picking two nodes on the free edge and distance of the created path along free edge will be represented.

Mechanism 

Case 28335

It is now possible to colour parts in the model according to the Mechanism or Dummy assembly to which they belong. (This has been the default during mechanism positioning, but the capability has now become global.)

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 69

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Under Display, Colour, Colour all by ... there is now an 'Assembly' option which will list all mechanisms and dummies in all models. Choosing one of these will result in its parts being coloured by assembly id, and all other parts being white. 

Case 24858

Added ability for Primer to read ANSA mechanism information.

Menus 

Case 28496

Added 'Align', 'Create' and 'Modify' popups for Thick Shells in Mesh tools menu. 

Case 28361

A new filtering option for GROUPs has been added to object menus. 'Group Contents' lists all underlying types (e.g. PART) referenced by groups, and selecting a particular type will limit what is shown in the menu to only groups which reference that type. There is also an option to show empty groups.

Mesh 

Case 27758

Added new option to choose local axes for splitting hexagonal solids. 

Case 26315

The remesh area tool has been completely rewritten for version 13. 

Case 21964

PRIMER can now remove multiple holes in a mesh in one operation. 

Case 18897

Primer's 'Remove hole' function now provides an option to create an unattached node at the centre of the erstwhile hole.

Model build 

Case 28988

Primer's build-from-csv function includes the new type GENERAL_TRANSLATE_PARAMETER that is applicable if the impactor is to be translated and rotated about global Y or Z and, optionally, furnished a parameter value and corresponding parameter name. Interactive editing of this type is currently not available 

Case 28465

The pedestrian markup script needs to pass along some generic information such as impactor model name, orient definition, and depenetration information to the model build (from csv) function. This was previously done either by selecting a template file or by hand-editing the output csv file prior to 'build'. This process has been improved as follows. A template may automatically be chosen via Primer preferences. Alternatively, an interactive menu may be fired

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 70

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

that facilitates the creation of a template and the updating of said preference. The final fall-back option of hand-editing the output file is still available 

Case 28201

Z may now optionally be specified for PEDHEAD and PEDHEAD_ANGLE style model build from csv operations. If a value is specified, the coordinates (X, Y, Z) are taken as such as the initial target point. If Z is omitted, Primer computes the initial point by the usual projection method

Nastran 

Case 28058

When a model contains duplicated tied contacts (one constrained, one penalty, with matching master and slave sides) on keyout of a Nastran model with the option to convert tied contact to RBE3, only the penalty contact will be processed. The user no longer needs to remember to predelete the constrained contact.

Nodal rigid bodies 

Case 6833

There are now new options for controlling the action of the middle and right mouse buttons during picking. One new option, 'Apply selection' allows the user to quickly create many entities using the mouse during picking, without having to return the cursor to a creation panel to click on 'Create'. Also, the return/enter key can also be used to 'Apply selection'.

Orient 

Case 24665

Added option to Orient copy to use a new part but same section/material.

Output 

Case 28198

The specified LS-DYNA output version is now written as a comment at the top of output decks.

Parameter 

Case 27849

The top level parameters menu now has a 'Find...' button to make it easier to find a parameter for editing in a model with many parameters. Using this will map a menu of all candidate parameters, and the standard filtering options (and in particular by text string) can be used to narrow down the list to the wanted parameters only. 

Case 27231

*PARAMETER definitions can now be added to the *ENCRYPTED block following *END (along with loadcurves and materials). This block exists so that decks which contain opaque PGP encrypted data that include *MAT, *DEFINE_CURVE or (now) *PARAMETER definitions can supply a 'simplistic' definition for

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 71

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

use during pre-processing, satisfying the requirement that he cards must exist without revealing details of the true data they contain. Because these cards appear after *END they are only 'seen' during pre-processing, and they can contain very simplified values. During the actual analysis LS-DYNA will ignore these and use the actual values from the decrypted PGP data block.

Part table 

Case 26446

In PART TABLE->Write, added an option to export part images to excel file.

Part replace 

Case 28564

An 'unattached items to clipboard' button has been added to the part replace merge panel.

Pedestrian 

Case 29438

Command line options have been added to the pedestrian markup script to write out the markup lines to file. 

Case 29408

The 'Draw process on screen' option did not show the tape used to create the WAD lines. It now does. 

Case 28164

The EuroNCAP v8.2 protocol has been added to the pedestrian markup script. 

Case 28163

An option has been added to the pedestrian markup script to write out the lines and/or test fields as keyword or IGES files. 

Case 26346

The parts selected in the pedestrian markup script can now be Sketched or Only'd to view what has been selected.

Penetrations 

Case 28020

The penetration checker for sliding contacts now has functions 'show pen elements' and 'show x'd elements'. These will blank the currently displayed elements so the only the penetrating/crossed ones are shown.

Preferences 

Case 27075

Added 'Save settings to oa_pref file' button to Pre-output check.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 72

Oasys Ltd LS-DYNA Environment Software



Release Notes Version 13.0

Case 18212

Added 'Save display settings' button to Display options panel. 

Case 15301

Added 'Save Orient settings' button to Orient options.

Quick pick 

Case 24108

Added 'Set current layer' to the quick pick options.

Renumber 

Case 27864

Added a button 'VISUALISE DECLASH' on Renumber->Declash All panel. Clicking on the button will bring up a pop-up panel with sketch/only button on it. Sketch/only button can be used to visualise entities which will be renumbered due to clash. 

Case 24822

More control over the label ranges for specific entity types is available.

Scripting 

Case 27820

If input logging is turned on (see case 27818, the -rlog_dir command-line argument, etc.) then nodes which are defined in multiple files but have been merged because they are coincident are reported to the primer.readlog.txt file. 

Case 27819

If logging of read messages to the dialogue box is enabled (see case 27818, the -rlog_dir command-line argument etc.) then details of all duplicate parameters are added to this listing file. Parameters may be multiply defined if: - They use the _LOCAL suffix, which means that they only apply within the scope of this file. - They use the _MUTABLE suffix which, in effect, allows all but the last definition of the parameter to be ignored. - There is a *PARAMETER_DUPLICATION card which defines how multiply defined parameters will be handled. - The user has made a good old-fashioned error! PRIMER will list all such duplicate definitions, and will state whether they are valid, and if so why, or whether they are in error. 

Case 27818

During keyword input messages written to the dialogue box are saved, and can be viewed via the Read Log button on the model read panel. However these data are overwritten when a new

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 73

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

model is read, and are also lost once the PRIMER session is closed unless the user saves them manually from an editor. It is now possible to turn on logging of these messages so that they are copied to a permanent file 'primer_readlog.txt'. This is done by any of the following methods: (1) Preference primer*save_read_log_dir: directory (2) Command-line argument -rlog_dir=directory (3) Turning read logging on interactively in the Model Read, Options panel. In all cases directory is the pathname of the directory in which file primer_readlog.txt will be saved, and this may also be defined as JOBDIR which means the directory of the master keyword file. If this file already exists then its name will be augmented to primer_readlog_n.txt where 'n' is the smallest integer that will make the name unique. In addition to the normal input logging this file will also contain details of any duplicate nodes that were merged, and also any duplicate parameter names, in both cases explaining how they were processed and whether or not they were legal. (See cases 27819 and 27820.)

Selection 

Case 25307

In solid/shell create panel, added an option 'Auto' on right click menu of noded element creation method. If 'Auto' is selected, 'Create' button will be enabled automatically after user has selected appropriate number of nodes (for shell 3/4/6/8 and solid 4/6/8).

Sets 

Case 29439

Child sets of a SET_xxx_COLLECT can now be edited from the panel of the parent.

Sketch 

Case 27965

Sketch arrows for LOAD SHELL pointing towards the median point of the shell in direction of normal to shell. On activating DRAW for LOAD_SHELL, these arrows will be displayed for all shells.

Undo 

Case 26600

A general undo button has been added for undoing simile entity creation/modification.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 74

Oasys Ltd LS-DYNA Environment Software

3.2

D3PLOT

3.2.1

Enhancements in 13.0

Release Notes Version 13.0

Airbag 

Case 26149

Done via data mapping. See case 27811.

Composites 

Case 29605

If a model has adaptive remeshing users are warned that ply data is unavailable and is blocked. This is because it would not be clear what shells were in what plys after an adaptive remesh. 

Case 29338

The dialogue commands /STRESS_CONTROL PLY_SELECT and /STRESS_CONTROL PLY_LOCAL can be used to set the composite plys to plot data on and set the frame of reference to ply local. 

Case 29308

If a surface/int point based data component is plotted and the user has selected composite plys instead of a surface to plot the data on then the component is now only contoured on shells and all other element types are drawn in grey. 

Case 29295

If the user chooses multiple plys or multiple models the selected plys are displayed in the bottom left of the graphics window. 

Case 29241

For shell data you can select a surface which corresponds to a ply to write out data. 

Case 29093

For a model with composite plys, for relevant data components and selected plys, users can plot data with respect to the 'Ply Local' axis, which is given by the fibre angle in the ZTF file written from PRIMER. 

Case 29092

The surface to plot data on can be selected by composite plys. Multiple plys can be selected. Where a shell element is in two selected plys, the ply with the lowest ID is used. Data is prevented from being averaged across different plys. 

Case 29091

On the data menu users can now choose surface as 'selected plys'. This gives a menu of available plys in models in different windows. Users can filter the list of plys to make it more managable. Users can select a list of plys, these are used as the data surface. 

Case 28012

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 75

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

Composite layups (where available) and composite plys are available in the part tree; quick pick menu; and blank menu. They can be blanked, unblanked, and only shown.

Cut section 

Case 26999

In the Cut Section menu under the Exclude tab a new option has been added to select parts to exclude from the cut section. Airbags can also be selected to exclude airbag particles.

Data components 

Case 29394

'Triaxiality' (-1 * pressure/von mises stress) has been added as a new data component in version 13. This new component is available via the 'Stress' data component category. 

Case 28991

D3PLOT 13 now supports results for beam elements in the D3FTG file that recent versions of LS-DYNA generate. 

Case 28664

D3PLOT V13 supports the new data components that are written to the D3ACS file by LSDYNA R8.0 and later. 

Case 28663

Version 13 of D3PLOT supports the new version of the D3FTG file format (*FREQUENCY_DOMAIN_RANDOM_VIBRATION_FATIGUE) that is generated by LSDYNA R8.0 and later. 

Case 28610

D3PLOT 13 now support the 'Wear Sliding Distance' data component written to the CTF (interface force) files. 

Case 27551

If the data component 'Contact Gap' was plotted then some elements reported values of 999.0 This is actually a special value which actually means that the interfaces are not in discernible contact but just processed and plotted this value as though the gap was 999.0. In version 13 D3PLOT detects this special value and ignores it when calculating the contour bar range and plots the segment in grey (uncontoured). 

Case 27550

D3PLOT 13 now support the Wear Depth data component written to the CTF (interface force) files which is defined on the *DATABASE_EXTENT_INTFOR card. 

Case 26131

D3PLOT 12 would fail to read in models containing DES elements that were run in recent version of LS-980 due to a change in the PTF file format. D3PLOT 13 now supports this new format ad it also supports the new DES data components introduced in LS-980. 

Case 26070

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 76

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

D3PLOT 13 now support the Wear Depth data component written to the CTF (interface force) files which is defined on the *DATABASE_EXTENT_INTFOR card.

Deform 

Case 29166

The CURRENT COORDINATE components can now be selected in a contour plot (previously they were limited to the WRITE and XY_DATA menus). This makes is possible to plot the relative distance from a node (when used in conjunction with Ref Node), for example a node on the seat of a car to view the 'survival space'.

Dialogue command 

Case 29819

A dialogue command has been added to translate a model in the graphics window in screen space (X, Y), e.g. /TR 0.1 0.2 

Case 29633

For models with composite shells, dialogue commands have been added to the WRITE and XY DATA commands to select surfaces by PLY and set the reference frame to PLY LOCAL.

Graphics 

Case 29514

A preference has been added to set the discrete beam default radius, d3plot*discrete_beam_radius. 

Case 29275

In some situations the sketching of items when using predictive picking in D3PLOT was difficult to see. To make things easier in version 13 the default line width used to sketch items has been increased from 1 to 2 pixels. A new option has also been added to the 'Utilities->Graphics' menu that can be used to change this. 

Case 28669

Occasionally D3PLOT can get stuck displaying data that is out of date. This shouldn't happen as D3PLOT should know when it needs to update the graphics, but when it did happen there wasn't a way to manually force a refresh. There is now a button next to 'AC' in the Viewing panel to do this. 

Case 27811

Data mapping has been implemented for 'single point' element data, that is Airbag particles, SPH elements and Discrete Element Sphere (DES) elements. This makes it possible to generate ISO surface contours of results in the volume of space they occupy, and the same logic can also be used to contour cut-section planes through this volume.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 77

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

It works by placing a bounding box around the relevant element type and creating a notional cellular mesh ('sugar cubes') into which the discrete element values are mapped. Each cell can then have an aggregate value calculated by a variety of means, and the resulting mesh can be ISO contoured. When cut-sections are active it is also possible to evaluate contours on the plane through this mesh, permitting contour bands to be drawn. Special 'mapped' data components have been added for airbag particles in which this process is used to derive pressure and averaged velocity of the gas in the airbag volume. 

Case 27805

The options to control the appearance of spotwelds have been reduced so that in V13 there is now 1) Draw as Structural Elements 2) Draw as Spheres. If option (1) is selected the solid, beam and cluster spotwelds are drawn using the geometry of the underlying solid and beam elements. The 'entity' panel options for spotwelds have also been changed so that it is now possible to turn on and off the drawing of solid, beam and cluster spotwelds separately from the underlying element types. Multiple data components can be plotted at the same time in V13 and spotweld solids and beams are a problem as it is possible for the user to select a data component that applies to solids and a component that applies to spotwelds and in this case it is only possible to show one of the 2 data components on each element. To solve this a new option has been added into V13 which has 3 settings for spotweld beams and solids. 1) Never draw spotwelds as structural elements 2) Only draw as structural if spotwelds are turned off 3) Always draw spotwelds as structural elements 1) With this option elements that are spotweld beams and solids are always treated as though they are spotwelds and are ignored for things like contouring and min-max values of any non spotweld data component. If for example you do a SI plot of Von-Mises stress then any spotweld solids will be drawn as uncontoured. 2) With this setting spotweld beams and solids are treated as spotwelds and are ignored for things like contouring and min-max values if the entity switch for spotwelds is turned on. If for example you do a SI plot of Von-Mises stress and the entity switch for spotweld solids is on then any spotweld solids will be drawn as uncontoured. If the switch is turned off then the spotwelds solids will be treated as normal elements and contoured. 3) This is the opposite of (1). With this option the spotwled beams and solids are always treated as though they are normal structural elements and will be included in data plots for structural data components. If a spotweld data component is plotted then the spotweld beams and solids will be uncontoured but any generalised or constrained welds will still be contoured as normal. The default option has been set as (2) because if users have gone to the effort of creating spotweld solids and beams then they are likely to want to see the spotweld data components by default. 

Case 27383

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 78

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

In Primer, if a beam section is defined with A, Iss, Itt explicitly and true sections are on, it either gets drawn as a rectangular or I-section, whichever is more appropriate. D3Plot only ever drew these beams as rectangular sections, but it is now the same as Primer and will draw them as I-sections if more appropriate. 

Case 27162

If the option to display beams using the true section properties is used D3PLOT can not calculate a size for discrete beams from the data available so discrete beams are drawn as either a single sphere for zero length beams or as pair of spheres connected by a line. In version 13 a new option has been added to the 'Beam Symbols' menu that can be used to control the size of the spheres.

Javascript api 

Case 29600

GetElemsInPly(), GetPlysInLayup and GetPlyIntPoint() have been added to the JavaScript API to help work with models with composite shells. Case 29547 A new optional argument has been added to the GetData() function to specify whether to return the Magnitude or Current Value [Magnitude * cos(Phase + Phi)] for phase angle results, e.g. a = GetData(DZ, NODE, 1, 0, 0, 0, 0, OFF, OFF, MAGNITUDE); or a = GetData(DZ, NODE, 1, 0, 0, 0, 0, OFF, OFF, CURRENT_VAL); 

Case 28597

An optional state_id argument has been added to the JavaScript function IsDeleted() to specify the state to check if an element is deleted. This can be used as an alternative to calling SetCurrentState() before IsDeleted(). 

Case 28520

A -js command line argument has been added to D3PLOT to specify a JavaScript to run. A -js_arg command line argument has also been added to enable arguments to be passed to the JavaScript.

Measure 

Case 26158

The measure menu in D3PLOT can now find the shortest distance from a node to a part and from a part to a part. 

Case 22034

The Nodes or Parts used in a measurement can now be re-picked by right-clicking on the Node or Part label textbox and selecting 'Pick'.

Menus 

Case 25647

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 79

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

The write images menu can now be undocked.

Read 

Case 28328

D3PLOT 13 supports the new D3ATV and D3EIGV_A file generated by the *FREQUENCY_DOMAIN_ACOUSTIC_BEM_ATV and *FREQUENCY_DOMAIN_ACOUSTIC_FEM_EIGENVALUE keywords.

Scripting 

Case 27748

A new function GetMultipleData() has been added to the Javascript API. This works in exactly the same way as the existing GetData() function, but instead of only getting results for one item at a time it extracts results for a user-defined range of items in a single call.

Volume clip 

Case 28120

The Volume Clipping 'Screen Space' option has been removed as it is obsolete.

Write 

Case 28440

The Write table can write data directly to an Excel XLSX file. 

Case 27083

An option has been added to the Write menu to output data in CSV format. The old text file format is still available and is the default. 

Case 26840

In version 13 the WRITE menus has been redesigned to allow multiple data components to be selected and displayed in one go. The data is now displayed in a table that can be scrolled and the values being displayed can be sorted by any of the columns.

XY plot 

Case 27004

In version 13 the XY-Data menu has been updated to use the same popup menus for selecting data components as the new data component menu that was added in version 12.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 80

Oasys Ltd LS-DYNA Environment Software

3.3

T/HIS

3.3.1

Enhancements in 13.0

Release Notes Version 13.0

Data Components 

Case 28983

T/HIS can now read in the following multiphysics ASCII results files: CESE_ELOUT (*CESE_DATABASE_ELOUT) CESE_POINTOUT (*CESE_DATABASE_POINTOUT) ICFD_NODOUT (*ICFD_DATABASE_NODOUT) ICFD_POINTOUT (*ICFD_DATABASE_POINTOUT) EM_ELOUT (*EM_DATABASE_ELOUT) EM_NODOUT (*EM_DATABASE_NODOUT) EM_POINTOUT (*EM_DATABASE_POINTOUT) 

Case 28056

Version 13 of T/HIS supports the 'Nparticles' data component from the ASCII cpm_sensor file. 

Case 28055

Version 13 of T/HIS supports the following new data components from the ABSTAT part of the LSDA (binout) file Airbag - Translational Kinetic Energy Airbag - Inflator Energy Airbag Parts - Heat Convection Energy 

Case 19532

'Triaxiality' (-1 * pressure/von mises stress) has been added as a new data component in version 13. This new component is available via the 'Stress' data component category.

Datum 

Case 26271

Datum definitions written to a .dtm file could not be used by a FAST-TCF script as the 'START DATUM' and 'END DATUM' lines that enclose the definition contain a space. The FAST-TCF script requires '_'s instead ('START_DATUM' and 'END_DATUM'). T/HIS has been updated so it can now accept either. To read in a .dtm file use the 'inc' keyword, e.g. inc C:\my_datum_file.dtm.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 81

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

FAST-TCF 

Case 29393

A new FAST-TCF command has been added to add parts to a group (gadd). This can be used if the command to create a part group (gdef) becomes too long. 

Case 26222

A new FAST-TCF command has been added to set the user defined model prefix: prefix model 'num / all' 'prefix' 

Cases 25010 & 22243

In version 13 the processing of FAST-TCF scripts has been modified to speed things up when the same data component is read for multiple items. Previously the data was read for each item separately, in version 13 a stack of read operations is now created and processed so that multiple items are processes together. 

Case 18050

$ftcf_startin_dir has been added as a FAST-TCF built in variable to store the directory that T/HIS was started in.

Javascript API 

Case 28519

A -js_arg command line argument has been added to T/HIS to enable arguments to be passed to a JavaScript.

Operations 

Case 27379

An ATAN2 function has been added in the Maths menu. It can also be used in a JavaScript using Operate.Atan2().

Read 

Case 27750

T/HIS was limited to reading 10,000 data variables per element from a THF file. It can now read as many data variables as have been written to the THF file. 

Case 26686

Curves written to the CURVOUT ASCII file can now be read into T/HIS. These are curves defined using *DEFINE_CURVE_FUNCTION and output using *DATABASE_ASCII_CURVOUT.

T/HIS link 

Case 17952

In a D3PLOT-T/HIS linked session the Timeline option can be used to draw a vertical line in the T/HIS graph to show the current time in D3PLOT.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 82

Oasys Ltd LS-DYNA Environment Software

Release Notes Version 13.0

For curves created using the COM operation, e.g. Force-Displacement of a spring, the X-axis will no longer be time and drawing a vertical line makes no sense. For curves that have been created this way, a point is now drawn on the curve instead. If the Timeline option is on to show the current time in D3PLOT, it makes no sense to do this by drawing a vertical line.

Units 

Case 29243

Additional units have been added to deal with results from Multi-physics ASCII files (CESE, ICFD and EM).

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 83

Oasys Ltd LS-DYNA Environment Software

3.4

REPORTER

3.4.1

Enhancements in 13.0

Release Notes Version 13.0

Generate 

Case 29004

It is now possible to control the size and aspect ratio of images produced in PRIMER, D3PLOT and T/HIS 

Case 28875

Images for Image file, PRIMER, D3PLOT and T/HIS objects can now be justified. 

Case 24911

Files or directories can now be dragged into a template to update DEFAULT_DIR and DEFAULT_JOB and generate the report.

Javascript API 

Case 28334

The Page.Duplicate() method can now have an optional index argument which is where the duplicate page should be inserted into the template. 

Case 28221

An ImportItem method has been added to the Page class.

Variables 

Case 28459

Variables can now be marked as temporary variables. Temporary variables can be removed from a template with a new 'Delete temporary variables' command in the Variables menu.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 84

Oasys Ltd LS-DYNA Environment Software

3.5

Shell

3.5.1

Enhancements in 13.0

Release Notes Version 13.0

General 

Case 26272

On Windows, pressing the Status button in the Shell would issues an error message if C:\TEMP or C:\TMP did not exist, as it needed to write a batch script to one of these directories. It now searches for more potential directories to write the script, so should now be less likely to issue this warning. 

Case 24110

The map='filename' and map1='filename' command line arguments can now be specified from the Optional Files menu. These are used with *INITIAL_ALE_MAPPING and *BOUNDARY_ALE_MAPPING.

Ove Arup and Partners Limited | Draft 1 | March 2016

Page 85