Ltd Software Suite Version 15 · 2018. 5. 15. · 2.4 REPORTER 45 2.5 Shell 48. 3 Enhancements 50....

Ltd Software SuiteVersion 15Update and Release Notes

SHELL

Oasys Ltd LS-DYNA Environment Software Release Notes Version 15.0

Ove Arup and Partners Limited | Final | May 2018

Contents Page

1 Introduction 1 1.1 Compatibility with LS-DYNA releases 1 1.2 Hardware platforms supported 1 1.3 Graphics hardware supported 1 1.4 FLEXlm Licensing 2 1.5 Extra history variables data 2

2 Bugs Fixed 3 2.1 PRIMER 3 2.2 D3PLOT 30 2.3 T/HIS 40 2.4 REPORTER 45 2.5 Shell 48

3 Enhancements 50 3.1 PRIMER 50 3.2 D3PLOT 62 3.3 T/HIS 69 3.4 REPORTER 71 3.5 Shell 73



Page 1

1 Introduction The Oasys Ltd LS-DYNA Environment 15.0 suite, dated May 2018 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 14.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 15.0 release has been used and tested with LS-DYNA version R10.0, and supports all the keywords in volumes I, II and III of the R10.0 User’s Manual dated October 2017.

LS-DYNA R9.0 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 15.0 is available on the following platforms:

Windows Windows 7 Windows 10

64 bit

Linux RedHat Enterprise 6.x, RedHat Enterprise 7.x SUSE Enterprise 12.0

64 bit

For simplicity of support and maintenance only the RedHat Enterprise 6.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 on Linux platforms only, since these are used by a small minority of clients who display over a network of mixed machine types. However this X driver is not maintained or updated and will give poor performance, so it should only be used as a last resort. There are much better “thin wire” graphics solutions available today, and Oasys Ltd can give advice about these on request.



Page 2

1.4 FLEXlm Licensing The version 15.0 software has been compiled using version 11.14.1 of FLEXlm.

The version 15.0 software requires a new license file and will not run with existing version 14.1 or earlier licenses.

The version 15.0 license file and license daemons are backwards compatible with both the 14.x and 13.x software releases. This means that any existing 14.x and 13.x software will continue to work with new license files and servers.

We recommend that you update all of your Oasys Ltd LS-DYNA environment license servers with the files shipped with the version 15.0 software.

1.5 Extra history variables data D3PLOT 15.0 includes a new material properties component that marries history variables with appropriate data component names for different elements. Some of this information has been sourced from the following site: https://www.dynasupport.com/howtos/material/history-variables.

1.6 Important T/HIS JavaScript Update JavaScript written for T/HIS 14.0 and 14.1 which use data components will not run in version 15.0.

JavaScript written for T/HIS 14.x which use variables that have the same name as a data component (e.g. ‘X’) will run in T/HIS 14.x, but almost certainly gave the wrong answer. In version 15.0 the variable will have the correct value, so give the right answer.

This is because in T/HIS 14.x the data component constants were global constants. They could over-write other variables used in the script. In T/HIS 15.0, data components are accessed by a Component class.

To correct your scripts which use data components make the following change to functions QueryDataPresent() and GetDataFlagged():

Version 14.x: m.QueryDataPresent(DX, Entity.NODE); curve_array = m.GetDataFlagged(f, DX);

Version 15.0: m.QueryDataPresent(Component.DX, Entity.NODE); curve_array = m.GetDataFlagged(f, Component.DX);

https://www.dynasupport.com/howtos/material/history-variableshttps://www.dynasupport.com/howtos/material/history-variables



Page 3

2 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.

2.1 PRIMER

2.1.1 Bugs Fixed in 15.0

Airbag • Case 33474 The sketch function for *AIRBAG_SHELL_REFERENCE_GEOMETRY has been re-written to be faster.

Airbag folding • Case 34669 Cancel did not work in the local coordinate system panel. Now fixed.

Auto create • Case 35804 Wrong MAT type was assigned to the Shell type seat belt elements which are fixed now.

Belts • Case 34792 A model with *BELT cards caused PRIMER to hang during keyword input. This turned out to be due to a hand-edited set of *BELT cards from model ‘A’ being grafted into model ‘B’ that might have had similar geometry but used wildly different labels. As a result, the belt fitter got caught in a very long loop over a huge label range and hung the machine. The bug which caused the hang has been fixed and the model now reads in with errors, although the error message that is reported does not really describe the problem, it does give an indication of the underlying cause. • Case 35115 When re-meshing an existing seatbelt definition an error could occur in the following situation: - Original belt had retractor or slipring at a point. - User edited the definition to remove the slipring or retractor. - After 'fit' and 'mesh' cycle the retractor or slipring would re-appear. This was caused by a wrong test in the logic which 'crawls along' the belt looking for the best match for nodes, retractors and sliprings. It was looking for the latter two when it should not. This has been fixed.



Page 4

Checking • Case 33699 Shells of formulation 29 may have zero area. For these the spurious error message about negative area has been removed. • Case 34833 PRIMER can write out element quality metrics to a summary file. In previous versions, the columns for skew and warpage were interchanged. Additionally, 0 values were unconditionally being written out for the Jacobian. These have been fixed. • Case 34953 When PRIMER writes in pre-971 format it has to convert *SET_XXX_ADD to a 'simple' *SET_XXX card since _ADD is not supported. Earlier versions of PRIMER made this conversion successfully, but when *SET_XXX_ADD_ADVANCED and some other more complex *SET types appeared internal changes broke this conversion process, and an attempt at output would probably crash. This has been fixed. *SET_XXX_ADD is now decomposed into the underlying definitions in a plain *SET_XXX card. *SET_XXX_ADD_ADVANCED cannot be converted, and the original (wrong) logic which attempted this is replaced by a warning that the set is being omitted. • Case 35043 Error messages for fields containing DEFINE_FUNCTION have been corrected. • Case 35312 Check for overlapping contacts did not work if an exempted part set was used. Now fixed. • Case 35499 The Autofix to remove duplicate database history beams could cause a SIGSEV when the edit panel was subsequently activated. Now fixed. • Case 37355 When running a model check with a part with SHELL elements but not a SHELL section, Primer crashed. This happened when the section is of type TSHELL for example. Now the crash has been fixed, and there appears a message about inconsistent element type between elements and the section of the part.

Clipboard • Case 37221 Clipboard sub-model may contain *ELEMENT_MASS_PART_SET. The mass value (added or target) on the original card is now factored down by the ratio of sum of relevant sub-model part areas (or volumes) to those of the original model. Without this change, the sub-model will be assigned too much NSM (unless it contains all the parts of the *ELEMENT_MASS_PART_SET)



Page 5

Comments • Case 34512 PRIMER did not store embedded comments for *INCLUDE and *INCLUDE_TRANSFORM correctly. This is now fixed.

Composites • Case 33252 When the user deletes layups from the composites panel, it used to only delete PRIMER's internal *COMPOSITE_LAYUP card. This deletion has now become recursive. This means that the user can select to delete the plys, shells, shell sets or nodes of the elements which belong to this layup as well. Please note that deletion of the ply will only delete PRIMER's internal *COMPOSITE_PLY card. It will not delete the corresponding data on the actual *ELEMENT_SHELL card. • Case 33969 The composite data which is not safe to be edited from the shell panels has now been greyed out. This operation is not safe because the user could change ply data which is common across the ply and thus changing them on an individual element could cause subsequent problems. The user has an option to override these settings by clicking on the 'EDIT' button on these panels. • Case 34314 After using composites ‘Automake’, if the user tried to set the angles of the ply from the ply panel and update the layup, PRIMER used to remove some of the previous composite data from the shells. This has now been fixed. • Case 34325 After using composites ‘Automake’, the model which was generated was found to be inconsistent after a read/write operation in PRIMER. This has now been fixed. • Case 34432 When removing shells from a ply, the corresponding data from the ELEMENT_SHELL_COMPOSITE(LONG) layer was not being removed. This has now been fixed. • Case 34808 Previously, when trying to edit plys and layups which contained part-composites (probably generated by Composite Automake) using the ply and layup panels, PRIMER used to generate ELEMENT_SHELL_COMPOSITE cards on these shells. This lead to a case where a shell belonged to both an ELEMENT_SHELL_COMPOSITE card and a PART_COMPOSITE card which is an error. This has now been fixed by preventing the user from updating plys and layups which contain PART_COMPOSITE cards.

Connections • Case 33242 When Primer makes bolts it creates parts at highest+1. If one is reading an xml connection file and finds a layer part reference which conflicts with the label of a bolt part, the latter is now renumbered. This will avoid problems when one tries to delete bolts where the part is referenced by a connection layer.



Page 6

• Case 34319 Autoscale now works as expected if the only entities shown are DEFINE_HEX_SPOTWELD_ASSEMBLY. • Case 34706 Sometimes bolt connections would fail to realize when the xml file was read during model build. This happened when no length info was supplied in the xml. A default length setting is now applied. • Case 34771 A new option has been added when creating patch adhesive. This allows source tria elements to create cohesive 6 nodes elements (n1, n2, n3, n3, n4, n5, n6, n6) instead of standard 6 noded pentas (n1, n2, n3, n4, n5, n5, n6, n6). • Case 34939 When replacing a part with MIG welds with some attached to the nodes of the part and some projected onto the part, the latter were not being re-projected to the new surface. Now fixed. • Case 35093 Connection contact creation has been corrected so as not to include the nodes of weld elements that are meshed in (HAZ welds). If necessary, contact is set up using *SET_NODE_GENERAL with DNODE. • Case 35255 When creating spot-welds with heat affected zones the undo last feature did not work correctly. It has now been fixed. • Case 35696 Users have reported that single point bolts sometimes make correctly but when the model is written/read or copied the bolt cylinder shows a slight misalignment which can result in BADGEOM error status as an NRB node is unexpectedly outside the volume. To avoid the loss of axis (as calculated on creation) this is now encoded using the otherwise unused coordinates for P2 and will now be 'remembered' across write/read/copy operations. • Case 35875 When created between misaligned holes, an NRB bolt which uses 'user diameter' setting could sometimes give the BADGEOM error as an edge node lying outside the fixed radius of the bolt got included in the NRB. In other modes the radius is always expanded to include edge nodes. Now fixed. • Case 35921 When holes are misaligned, using the centres for 2-point bolt was giving a bolt which was not normal to the panels. Primer now adjusts the 2nd point (as it did before for pick on shell). • Case 36451 Part replace now supports replacement of parts with HAZ welds. This process should maintain nodal connectivity and node/shell set membership.



Page 7

• Case 36512 When using HAZ spotwelds with the orient to free edge option on PRIMER was giving small variations in spotweld orientation when comparing the difference between remaking via a part replace or remaking via the connections table. This has been corrected. • Case 36647 When a modular bolt clamps two plates of different thicknesses using the fit=1 option, the algorithm to calculate the shrink could result in very small elements. This has been improved.

Constraints • Case 34735 *BOUNDARY_PRESCRIBED_MOTION and *BOUNDARY_SPC both have an optional _ID suffix which permits an explicit label and title to be defined. The label is not referenced elsewhere in the input deck and the LS-DYNA user manual explicitly states that it does not have to be unique. However, PRIMER's internal logic will not permit distinct definitions (as opposed to 'clones' of the same definition) to share the same label, so it treated multiple occurrences of the same label for these cards as an error while LS-DYNA would read the file quite happily. To solve this problem PRIMER now treats duplicate labels as a warning, and changes them to unique values. This change is permanent, meaning that if the deck is written out it will have changed with respect to the original, which breaks the rule that 'PRIMER should not alter decks'. However, it is difficult to see what else to do in this situation, and since these labels have no intrinsic meaning or purpose it can do no harm. • Case 35421 The popup on the field RPS on *CONSTRAINED_JOINT was not working. This has now been fixed. • Case 36175 Clean-up unused on *CONSTRAINED_LINEAR could result in SIGSEV. Now fixed.

Contacts • Case 33976 Dragging nodes in the contact fixer was sometimes slow to respond. In particular, this happened when the contact involved parts going around the whole model volume, but modifications were local to just a few nodes. The speed has now been improved. • Case 35415 *CONTACT_SURFACE_TO_SURFACE_INTERFERENCE has been corrected to use same contact penetration calculation as *CONTACT_SURFACE_TO_SURFACE. • Case 36244 PRIMER will now allow the _OFFSET options for the *CONTACT_TIED_SHELL_EDGE_TO_SOLID contact type.



Page 8

Contour • Case 35412 Primer contours resolved element formulation if ESORT is set on *CONTROL_SHELL or *CONTROL_SOLID. This was not implemented correctly and in some cases the over-ride formulation was being plotted when it should (it only applies for degenerate formulations). Now fixed. Also there is new contour option under Elem Props 'form (native)' which ignores ESORT. • Case 36439 Changed warning for 'Added Mass' Failed criteria reference value appropriately. It now warns the user to set the appropriate 'Added mass' reference limit value.

Control • Case 34699 CONTROL_FORMING_ONESTEP now writes a blank line instead of FLATNAME when OPTION = 7 (or -7) as per the keyword manual.

Deleting • Case 34875 Deleting or doing undo of creation for *PART_MOVE did not un-apply the transformation. Now fixed. • Case 34919 When PART(s) are deleted from the MODEL, the references in DEFORMABLE_TO_RIGID cards are now cleaned up properly. • Case 35085 When SET_PARTs are deleted from the MODEL, the DEF_TO_RIGID_AUTO cards referring to these SET_PARTs were also getting deleted. Now only the rows in those DEF_TO_RIGID_AUTO referring to those SET_PARTs will be removed from the keyword. • Case 36365 Deleting a *MAT_ADD_EROSION card with recursive deletion would not delete the LCSDG table and associated curves. Now fixed. • Case 36693 In rare case PRIMER could crash when deleting models containing assigned mass. This has now been resolved.

Dummies • Case 35446 The error 'connectivity check shows nodes in multiple assemblies' was appearing incorrectly for dummies where the nodes are actually constrained to the correct assembly by *CONSTRAINED_EXTRA_NODE. This no longer provokes an error message.



Page 9

Edit • Case 33305 Macro creating an open ended *CONTROL keyword fails intermittently when editing any of the keyword fields like PART, CURVE etc. Fixed the issue by adding a macro tag to such open ended keyword panels. • Case 34253 CONTACT_AUTO_MOVE now has an edit panel. • Case 34344 Normal/Align dock panel flickered while selecting elements. The panel buttons were getting mapped and un-mapped unnecessarily while element selection. Now mapping the buttons only when required. • Case 34591 Some editing operations in PRIMER work on the 'live' database definition rather than a scratch copy; examples are all keyword editors, and also the top level *PARAMETER editing panel. This is done because trying to track and update changes from a scratch copy would be impossibly complex in these situations, and in practice the way these panels work is: - Make a backup of the original definition. - Update the current database definition with the modified values. This leaves a 'pending edit' in force. Then 'update' will make these changes permanent, propagating changes through the model, and 'abort' or 'reset' will undo them, restoring values form the backup. However, a problem arises when a model is written out to file when this 'pending edit' situation is in force, since if left uncorrected it would be possible for the output written to file to contain the pending edits which might subsequently be undone. This may also lead to inconsistent values being written since the effects of these pending changes has not been propagated correctly through the database. Therefore, a pre-output check for any of these editing panels with pending edits has been added. This warns the user, explains the problem and offers to shut down these panels, losing the pending edits. A similar check has been added prior to Model Copy, and Model Merge. A separate but related problem was that using the 'Tidy all' button to get rid of all editing panels would also not necessarily undo all these 'pending edits', despite giving the appearance of having done so. This has now been fixed. Note that 'single item' editing panels, the typical 'create' and 'modify' cases, do not suffer from this problem since they always work on a scratch copy. It is only keyword editors and the top level editing panel which suffer from this problem. • Case 34832 Parameter handling in Open ended keyword like *DEFINE_SPH_TO_SPH_COUPLING was missing in open lists. Fixed this.



Page 10

• Case 35016 There were instances where the user could make the keyword *DEFINE_SPOTWELD_FAILURE_ADD card to refer to itself which is a bug. This has now been fixed by explicitly disallowing the users from doing so. Also when the _ADD card referred to a latent card, this card was lost during a model copy operation. This is also fixed. • Case 35111 The PIDREF popup for *PART_STACKED_ELEMENTS did not work. This has been corrected. • Case 35121 Some strange characters appeared on the material database import panel, in the text box next to 'Database:'. This has now been fixed. • Case 35325 Primer was issuing a false warning about PSETID being empty (in *DATABASE_BINARY_D3PART) when it was not. This has now been fixed. • Case 35657 Corrected the parameter definition handling in the editor for keyword *ALE_STRUCTURED_MESH_CONTROL_POINTS. • Case 35659 The *AIRBAG_REFERENCE_GEOMETRY editor would 'lose' any parameters used to define reference nodal coordinates in the editing panel, and could also lose existing parameterised coordinates of all nodes if any such node was edited in this panel. This has been fixed: parameters used to define coordinates are now preserved during passage through the editor. • Case 35660 The *CONTACT_COUPLING editor panel would 'lose' parameters associated with open-ended lines of coupling set data due to an internal error, now fixed. • Case 35661 Corrected transfer of parameters for input line of *INITIAL_HYDROSTATIC_ALE. • Case 35662 Fixed parameter input for entry line of *INITIAL_AIRBAG_PARTICLE_POSITION. • Case 35663 Parameters are now transferred correctly when inserting or moving rows in DEFINE_TRANSFORMATION. • Case 35665 In DEFINE_SPH_DE_COUPLING edit panel, parameter entries were lost after adding the open-ended rows. Now fixed. • Case 35667 Parameter handling in the *DEFINE_SPOTWELD_FAILURE editor has been corrected.



Page 11

• Case 36309 Parameter handling in the *CONTROL_CHECK editor has been corrected. • Case 36311 Parameters are now transferred correctly from the create row in the CONTROL_FORMING_AUTOPOSITION_PARAMETER edit panel. • Case 36312 Parameters are now transferred correctly from the create row in the CONTROL_FORMING_OUTPUT edit panel. • Case 36313 Parameters are now transferred correctly from the create row in the CONTROL_FORMING_PARAMETER_READ edit panel. • Case 36316 Parameters were not working for *CONTROL_IMPLICIT_MODAL_DYNAMIC_DAMPING with SPECIFC or FREQUENCY_RANGE option. This affected both reading/copying/writing a model and the edit panel and has now been fixed. • Case 36317 Parameters were replaced by their values for *CONTROL_MPP_DECOMP_BAGREF. This affected both reading models and the processing on the edit panel. Now fixed. • Case 36318 Fixed parameters on entry row on edit panel for *CONTROL_MPP_DECOMPOSITION_PARTSET_DISTRIBUTE. • Case 36319 Fix for parameters lost on entry row on edit panels for open-ended keyword CONTROL_MPP_DECOMPOSITION_ARRANGE_PARTS • Case 36320 Fix for parameters lost on entry row on edit panels for open-ended keyword CONTROL_REQUIRE_REVISION. • Case 36321 Some parameters were lost on *DATABASE_TRACER_GENERATE edit panel. This has now been fixed. • Case 36322 Some parameters were lost on *INTERFACE_DE_BOND edit panel. This has now been fixed. • Case 36323 Some parameters were lost on *SENSOR_SWITCH_SHELL_TO_VENT edit panel. This has now been fixed. • Case 36366 Parameters are now stored correctly in open ended panels when they have more than one row.



Page 12

Element quality • Case 34851 Even if the Added mass failure settings are OFF, the 'worst' Added mass values should always be outputted into the Model Summary file. Similarly, minimum value of Timestep should always be outputted in Model summary.

Elements • Case 34397 Added a new logic to manage case with CST = 2.0 in *SECTION_BEAM and ICST = 9.0 in *INTEGRATION_BEAM keywords for *ELEMENT_BEAM_ELBOW beam type.

Explode • Case 35410 Primer's exploded view function could previously throw an error (in rare circumstances) if an attempt to explode empty parts were then followed by a deletion and a second explode attempt. This has now been fixed.

Geometry • Case 33981 If PRIMER read an IGES file and could not tessellate all of the surfaces correctly it would give lots of error messages that could be repeated during some operations. This could slow down some tools (for example adhesive creation). Now the error messages are not repeated. • Case 34527 IGES curves list is not visible when user tries to create nodes along geometry curves the second time in the same session.

Graphics • Case 35038 When CN (Centre Node) mode was used to lock the centre node about which the view rotates a clipping error could occur. This would manifest itself in the follow sequence: - Select CN - Pan most of the model off the screen (shift + middle mouse) - Increase the scale a little (shift + right mouse) - Pan the model back onto the screen (shift + middle mouse again) This could result in parts which had been moved off the screen during the first pan operation not being redrawn when they moved back onto the screen after the second pan operation. The cause was that the 'coarse clipping' which determines whether or not to draw a part was not considering changes when in CN mode. Now fixed. • Case 35084 PRIMER could sometimes 'lose shading' of parts when a certain sequence of dynamic viewing operations was performed. An explicit redraw in some other viewing mode, followed by a shaded mode plot, would restore shaded graphics.



Page 13

Due to an internal error in wireframe (control key + mouse) dynamic viewing which would sometimes leave an internal setting stuck in wireframe mode. Now fixed. • Case 36345 *CONSTRAINED_INTERPOLATE cards referencing independent node sets were not drawn correctly in PRIMER. This has been corrected. • Case 36666 The Left CRTL Key + Left Mouse Button rotate of a Model in Cut Section mode, switched the model to the Wireframe mode, even after releasing the CTRL key. Fixed this. • Case 37215 When part of a model is off the screen due to zooming in, then it is moved back onto the screen using [control key] wireframe mode dynamic viewing, the newly visible components may get 'stuck' in wireframe display mode even when the control key is released. Graphics driver error, now fixed.

Help • Case 33968 Help box was not getting activated for Normals/Align panel for Shells/Solids/T-Shells. Fixed this.

Include • Case 33464 PRIMER was writing out the comments from the include file into master file after copying the model. It has been fixed now. • Case 34802 A recent (R9) innovation in LS-DYNA input syntax is that the suffices '+' for large format and '-' for small format can be appended to an *INCLUDE keyword, meaning that the following include file(s) are implicitly this format. PRIMER did not support this, but this has now been corrected in V15. Note that if the file itself contains a *KEYWORD card with an explicit 'long=xxx' definition this will supersede any suffix on the parent *INCLUDE card. • Case 35017 The _AUTO_OFFSET offset on a *INCLUDE card allows the node and element labels in the include file to overlap with existing ones in the model, and these are then offset as required by LS-DYNA to avoid label clashes. PRIMER was getting this logic wrong in some circumstances, resulting in latent nodes not being offset or - worse - ending up with negative labels, and in some cases a crash during keyword input. This was due to a misunderstanding of how this sub keyword was supposed to work and has now been fixed.



Page 14

Javascript API • Case 34807 Corrected the JS-script manual comment for Sketch Java script function for *BOUNDARY_SPC cards: If option is set to true (or omitted) the plot will be redrawn each time. If sketching a large number of items, efficiency will be gained by setting the argument to false for all but the last item sketched. The final call will redraw. • Case 34888 JS API File.IsWritable() did not work when testing to see if a filename could be used to create a new file or if a filename was a directory. Now fixed. • Case 34949 PRIMER could crash if the Model.ImportInclude() function tried to import a file that contained a *INCLUDE_TRANSFORM. This has been fixed in v15. • Case 35046 If a second JavaScript was started when one was already running, then terminating the second JavaScript would also close the first script. This has been fixed. • Case 35209 If a material that could have an optional card was read from a keyword file and it did not have the card it was not possible to set a property on the optional card with JavaScript. A new AddOptionalCards() method has been added which now makes this possible. • Case 36305 The ‘numtypes’ property for the Xrefs class would occasionally give the wrong value if items had been deleted from the model. Now fixed. • Case 36413 Setting a property on a WidgetItem not attached to a Widget would cause PRIMER to crash. Now fixed. • Case 36416 The getter for the colour property did not work correctly. Now fixed. Additionally several new Colour constants have been added and a new ExtractColour() method added to keyword classes. • Case 36426 'Beam on Elem. edges' Tool: Shortcut keys were not working to 'Reverse Blanking' etc. while Selection or Picking of entities was being done. Fixed this. • Case 36504 If AddFlagged() was used on a 'parent' collect set then PRIMER would add incorrect 'child' collect sets instead of the flagged items. The AddFlagged method will now throw an exception if used for a 'parent' collect set.



Page 15

• Case 36721 Using a widget timer could stop the buttons in the window top left [-] pop-up panel from working. Now fixed.

Keyword • Case 33858 Fields DC and VC did not have unit conversion in *DEFINE_FRICTION. Now these conversions are consistent with the corresponding fields in the contact cards. • Case 34309 IGAP can now be > 2 on the *CONTACT card. IGNORE can now be -1, -2, -3 or -4 if the _MORTAR option is on. • Case 34329 PRIMER now supports the large format option on *INITIAL_STRAIN_SHELL. Also, when the _SET option is used, DYNA ignores NPLANE and NTHICK and always expects data for two integration points. Previously Primer expected NPLANE*NTHICK integration point cards, but now it is consistent with DYNA expecting two such cards. • Case 34510 Some of the cards and fields for *ICFD_CONTROL_TURBULENCE were being written for the wrong LS-DYNA version. These have now been fixed. • Case 34647 In *PART_MOVE keyword editor, it was not possible to type out of range value and when reading a model with IFSET field being out of range, it was changed to 0 or 1 automatically. It has been fixed now, now out of range value can be added/read. • Case 34948 *CONTROL_FORMING_OUTPUT which has a single card is implemented as open ended and during key out all the keywords are written under single keyword header. When the model is read back in PRIMER it reads it as a single keyword and shows difference with original model during model modified. This is fixed now. Now keyword header is written for all the *CONTROL_FORMING_OUTPUT keywords. • Case 35128 The fields FT and FC on MAT_280 were interchanged. This has been fixed. • Case 35129 MAT_280 was being filtered out on the modify panel when the entity type was a shell. This has now been fixed. • Case 35231 Key out for *INITIAL_STRESS_SOLID key words with Thermal History variables was done incorrectly. Fixed this. • Case 35269 PRIMER used to allow users to select the SEATBELT option in ETYPE when editing *SENSOR_DEFINE_ELEMENT_SET, this is no longer allowed.



Page 16

• Case 35890 *INTEGRATION_SHELL can be applied to thick shells. The code for mass calculation and timestep calculation has been updated to include this usage.

Keyword editor • Case 34172 When using the keyword editor to edit multiple rows in a single operation (highlight multiple rows, change a field on one row, see the change propagate to all highlighted rows) data field referring to Loadcurves that were defined by a parameter might fail to propagate that parameter to all highlighted rows, instead using the underlying parameter value. Editing a single row would work correctly. PRIMER was missing special logic needed to process Load-curve labels when defined by parameters. Now fixed. • Case 34673 When using the *ELEMENT_SOLID keyword editor to create new elements the right click popup to 'create' nodes for nodes 5 to 8 would appear to work when used on the new element entry line, but when 'creating' the node nothing would appear in the element's topology list. This was caused by some special internal logic that has to deal with degenerate elements in which not all the nodes in the topology list are defined, and it was 'losing' nodes in some creation contexts. Now fixed.

Loading • Case 36463 Fix in load summary calculator when using local coordinate systems.

Macro • Case 34526 It is now possible for a macro to run a JavaScript that uses macros. • Case 35336 If a UTF-8 encoded macro contained Japanese filenames they would be corrupted when the macro was replayed. Now fixed. • Case 35878 Macros now work with the FREQUENCY_DOMAIN_MODE create panel and more than one line of data can now be added using the FREQUENCY_DOMAIN_MODE panel.

Mass • Case 36624 The check function for assign mass could report failure to meet target mass value when inspection of assign mass edit panel would suggest otherwise. This has been traced to different treatment of mass on nodes which are shared by multiple deformable parts. The check function has been corrected to follow the same methodology as assign mass.



Page 17

• Case 37220 Selection by entity for 'mass property' calculation can give unexpected results when the selection includes part of a connection (adhesive or spotweld lines) or some of the elements that are used in a *ELEMENT_MASS_PART definition. The calculation has been corrected to only count the correct portion of the mass in these cases.

Materials • Case 33759 When trying to edit any MAT_WINFRITH_REINFORCEMENT cards, the PRIMER label used to get incremented by 1. This has now been corrected. • Case 34732 Cards 5 and 6 were being mapped for MAT_59 when no option was set. This has now been corrected. • Case 34891 When a material card is written in a version not supporting a non-zero field, Primer warns the user about the omission. This message did not appear correctly when the omitted field was zero, but defined by a parameter. This has now been fixed. • Case 34895 For some materials with variable number of rows optional cards sometimes disappeared from the edit panel after a text edit. This has now been fixed. • Case 35211 Added optional _TITLE options for *MAT_ADD_COHESIVE, *MAT_ADD_THERMAL_EXPANSION, *MAT_NONLOCAL. • Case 35409 The variables HIS1, HIS2 and HIS3 on *MAT_ADD_GENERALIZED_DAMAGE were being processed as floats but in reality they were integers when positive and load curves when negative. This has now been fixed. • Case 36383 Keyword *MAT_CHRONOLOGICAL_VISCOELASTIC has up to 12 optional cards from LSR7.1 onwards, but PRIMER was still supporting only up to 6 optional cards. Fixed this.

Measure • Case 34656 Measure part to part can be very slow if large areas of the parts are in close proximity. In this case the new contour part to part algorithm is far more efficient. The code has been modified to run contouring in hidden mode to find the closest points in these circumstances. For a model consisting of bonnet inner and outer this has reduced the time taken from 20s to 0.2s. • Case 34869 When zero distance is input to node to node measure, the undo function incurred NaN (divide by zero) arithmetic error. Now fixed.



Page 18

Mechanism • Case 34787 When the following are all true: A mechanism contains one or more active mechanism contacts, and One or more nodes in a mechanism assembly is being sketched, and The mechanism assembly is dragged with the mouse. Then there is potential for the sketched nodal coordinates to be corrupted. This is because coordinates are backup up in an array normally used for plotting, and the act of sketching a node during the drag process can overwrite this backup which then leads to corruption of the 'true' nodal coordinate. Fixed by suppressing sketching for the duration of the mechanism drag process. • Case 35480 When modifying an assembly, connection, point, child or stretch from a mechanism edit panel, but aborting the Modify session on the parent mechanism panel, the changes were lost without warning. Now Primer warns with a message.

Menus • Case 34469 The colours of the buttons on the adhesive path panel did not match the standard PRIMER colours. This has been corrected. • Case 35226 PRIMER un-maps some of the Mesh Tool menu buttons if the related script is not found. Most of the other script tools buttons are always mapped whether the script is found or not. The behaviour of all script tools buttons has been made consistent i.e. to always map those buttons. PRIMER will throw warnings if the script is not found for any of the tools. Also Hover text for such buttons will warn the user. • Case 35238 In certain cases, the check boxes in the model build template panel used to get unmapped when refreshing this panel, this has now been fixed.

Merge • Case 32633 Parameter definitions with clashing names in Model -> Merge were sometimes lost without warning. This has now been fixed. There are also more refined options now about how to deal with these clashes. • Case 34216 When the parameter radio button or the Merge_COLLECT checkbox is changed in the Model->Merge panel, some of the merge panel properties reset to default (like Master Model is reset back to Model 1). Fixed this. • Case 34246 When there were two models opened in PRIMER, one with includes and the other without. When the user tried to merge these models and click on the select button, then if the user



Page 19

changed the master model to the model without the includes, the include object menu was still mapped. If the user then clicked on this panel, PRIMER would crash. This has now been fixed. • Case 34251 When deleting include files from a model, the labels are not sequential. When merging another model into this with a specified destination include, there were error messages and sometimes crashes. This has now been fixed.

Mesh • Case 30912 Re-meshing an area of shells some of which have inconsistent normals now works. • Case 31242 PRIMER Mesh tool can now remove more irregular hole types. • Case 33767 Added a 'Preview Mesh' button for Ruled Mesh panel to preview the to be created ruled mesh before actual creation of mesh with 'Apply' button. • Case 34391 Default element size in Mesh Tools panels should reflect the value given for preference 'mesh_element_size'. • Case 34589 Meshing holes with large curvature now works more reliably. • Case 34708 Elements generated though Mesh Tools are not visible, if that element visibility is Turned OFF in Entities Panel. Mesh tools functions will now turn ON the Visibility of those newly created Elements, and update the graphics. • Case 34959 Attempting to remove holes where associated shells are connected to more than 1 other shell not all of which are flagged for re-meshing is now trapped instead of creating an incorrect mesh. • Case 35042 If the nodes selected for extrusion to shells was done in non-consecutive order of node labels, the shells were not created in correct order. Fixed this. • Case 35440 PRIMER could crash when removing a hole in a mesh in very rare circumstances. The method for removing a hole has now been changed to prevent this. • Case 35497 Shells could be missed when meshing a hole of complex shape. This has been fixed.



Page 20

Model modified • Case 27372 Model modified could report spurious differences in models with SET_COLLECT because these use internally generated labels. This has been fixed. • Case 33827 The comparison of titles in model modified can now be controlled by a radio button on the front end. Comparison may be unconditional (as before), conditional on both titles existing or may be skipped altogether. • Case 34803 When comparing unlabelled items where some match across models and some do not, the order of said items could get changed due to manipulation of the internal label. Whilst this should not affect results, it is annoying to users who want to check their files with xdiff. The internal label is no longer changed, so order should now be preserved. • Case 34809 On keyin NRBs with clashing labels are relabelled. Model modified failed to report these or 'red-light' the includes in which they are found. Now fixed. • Case 34999 Model modified could get confused when handling SET_COLLECT. For example, a change of order of the includes could cause a spurious warning of contents change. The logic has been made more robust.

Nastran • Case 36576 When writing Nastran files with include files, PRIMER could generate duplicate labels in the entities being created due to the conversion from DYNA->NASTRAN. This has been corrected.

Node • Case 34736 The List button on docked panels for some keywords, for example NODE, only listed the number of items selected. This has now been changed to explicitly list the labels of all selected items.

Orient • Case 35047 When in the orient panel, if the user dismissed the orient tab while working on the interpolate function, some buttons were not being mapped properly when reopening the orient tab. This has now been fixed.

Output • Case 34931 If an include or master file contains *PART_MODES this might not be written out unless the file also contains some other *PART_XXX keywords. Caused by an internal error, now fixed.



Page 21

Parameter • Case 33773 When a model with several *PARAMETER_LOCAL cards with the same name in different include files was written with the Merge -> Master option, they were written to the same file and caused name clashes. Now Primer changes the names by appending _L1, _L2 etc. to avoid these clashes. There is now a message saying this when writing the model. • Case 34131 When writing a model with *PARAMETER_LOCAL in a DYNA version not supporting the _LOCAL suffix (older than 971R5), Primer attempted to rename the parameters to avoid name clashes when they are not written as local. There were several problems with that: The names are made unique by appending 1, 2, 3 etc. to the parameter names, but previously Primer appended 1 several times, so the names were not unique. Expression parameters referencing a local parameter which is renamed have now got their expression strings updated with the new name as well. Previously this was not the case and caused evaluation errors in the expressions after renaming. The names remained changed in the Primer session after the model had been written. Now the names and expressions are only changed in the files written out, but after that they are the same as before in the active Primer session, so it is possible to write the unmodified model in a newer version. When parameters are renamed for the file written, then they are written without _LOCAL suffix now. • Case 34145 When several _MUTABLE parameters were on the popup at a text box and the name was already typed in full length, all but the first one were greyed out. Now it is possible to select any of the mutable parameters. • Case 34362 When renaming a parameter used in an expression, the expression sometimes appeared in red indicating syntax errors even if the action to update the expression strings was selected. This has now been fixed. • Case 34416 Parameters can seem to get 'lost' in the following situation: + An item in model A is fully defined and refers to a parameter that is also fully defined. + The user decides to create a new item of this type in model B, and does so via 'copy existing' of the item in model A. + This copies the item, including the reference to the parameter, and makes a latent definition of this parameter in model B. So far, so normal, however when a parameter is copied between models in this situation PRIMER actually has enough information to 'populate' the attributes of the latent parameter in model B, and it has to do this otherwise there would be a mismatch between the (known) value of the parameterised data field in model A and the (unknown unless we populate the parameter)



Page 22

value of that data field in model B. So the parameter in model B occupies a slightly unusual position inside PRIMER which is not quite 'installed', but not quite 'latent' either since its actual attributes are known. This in turn means that the value in that parameterised data field is known inside PRIMER, but is lost when the model is written out since the relevant *PARAMETER card is not written. To get round the parameters in this situation are now given the following special treatment: - When copied to a new model as part of a 'referenced during copy of something else' operation they will remain latent (as before) so long as the item which refers to them is a scratch definition inside an editing panel. - However if that definition is saved to make it permanent, i.e. it becomes 'installed', then any parameters it refers to are also made 'installed' so that they do not get lost when the model is written out. This means that parameters referred to in this way are treated automatically as 'referenced items' and are copied along with their referrer, which is not normal practice inside PRIMER and makes them a special case. However, this seems to be the best solution to the problem and is probably what most users will expect to happen. • Case 35106 Primer incorrectly reordered parameters during model build. This happened when a parameter was referenced in a different include file as it was defined. When there are parameter expressions, this could leave syntax errors in the model because the parameters referenced in an expression sometimes appeared after the expression itself in the model. Now the parameters appear in the same order in the model as they are defined in the input files. • Case 35108 Parameters were lost on *DATABASE_HISTORY cards in several contexts: When writing a model, only the first item on the list appeared with a parameter, whereas parameters were replaced with values for the other items on the list. When adding parameter references on the *DATABASE_HISTORY edit panel, updating the definition from the panel in fact created the *DATABASE_HISTORY card without parameters. These two problems have now been fixed. • Case 35113 Character parameters were handled inconsistently in the title field for *DATABASE_HISTORY_XXXX_ID. On the first card under the keyword header a string &title was stored as the literal string &title rather than a parameter reference. This can cause problems when the parameter is renamed or deleted, but otherwise is no problem when writing the model to run it in LS-DYNA. From the second card onwards character parameters were replaced by their values, so if the title was defined as &title in a keyword file and the value of that character parameter was 'My title', then the string 'My title' would have appeared directly as the title in Primer. In version 15 Primer now handles parameters in the title field on any row in the same way as it did for the first row, i.e. it stores the string &title verbatim without recognising that it is a parameter. Strictly speaking this is not correct, but it appears in the file as if it was a parameter when writing the model. Also, LS-DYNA seems to allow character parameters in the middle of the string like 'My



Page 23

database title &title', which Primer does not support, but keeping the string verbatim without recognising the parameter means that LS-DYNA will treat &title as parameter in this example as long as the parameter &title is not renamed or deleted in Primer. • Case 35431 Parameter values with leading zeroes can cause problems in LS-DYNA. Sometimes they can be misunderstood as octal values or they can cause errors in LS-DYNA. There have already been warnings in Primer for the case that octal values mismatch the decimal values, but now these errors generally appear in the model check if it is run immediately after reading the model. When writing a model, all numbers are written without leading zeroes because Primer only stores them as numbers rather than strings. For parameter expressions containing numbers with leading zeroes there are errors in the model check. They are not corrected automatically because they are likely caused by typing errors. • Case 35433 Leading spaces in parameter expression strings can sometimes cause errors in LS-DYNA. Normally the first 10 characters for a parameter expression are reserved for the type (I or R) and the name, and the expression starts from character 11. When from the 11th character onwards there are leading spaces, this sometimes but not always causes problems. When reading a model in Primer, there is now the option to automatically remove the leading spaces. • Case 35705 When using parameters on the part table for *PART_COMPOSITE in the section ELFORM, GAUGE and/or NIP columns, PRIMER crashed. For ELFORM parameters are now correctly processed and displayed. For GAUGE and NIP they are rejected in the same way as ordinary numerical values because these fields cannot be edited on the part table. • Case 35851 Some parameters were being lost on the part card when the _COMPOSITE option was turned on. The affected fields were ELFORM, SHRF, NLOC, MAREA, HGID, ADOPT, TSHEL also the fields on the _CONTACT options were also losing parameters. This has now been fixed. • Case 36447 There were problems with parameters on the edit panel for *DATABASE_HISTORY. The old edit panel has been replaced with a keyword editor, which extends the existing one for *DATABASE_HISTORY_NODE_LOCAL.

Part table • Case 33887 Choosing latent IDs for *MAT or *SECTION from the part table would previously create new *MAT or *SECTION cards with attributes copied over from the old ones. This behaviour has been changed to make things consistent with other functions in Primer. Latent *MAT or *SECTION cards are now produced in these cases. • Case 35109 PRIMER crashes on launch of a Model PART Table, if value of oa_pref setting 'part_table_columns' is ill-conditioned. Fixed this.



Page 24

Part replace • Case 35581 Part replace has been fixed to handle remake of HAZ weld connections when these attach to a part being replaced. The weld is undone before the replace process, then redone afterward. As currently programmed, the process could re-mesh panels which are not the ones being replaced. A future upgrade under consideration is to limit the re-mesh to the replaced parts. • Case 35846 Part replace was losing NCPU information due to an error in model copy function. Now fixed.

Part tree • Case 37192 White space is no longer drawn between tree and PART or PART TREE ASSEMBLY keywords in part tree contents mode.

Pedestrian • Case 35277 The pedestrian markup protocols state that the front of the vehicle the outer surface should be approximated with tape so that the markup lines don't fall into the gaps around the grill area. Previous versions of the script did not do this and you could end up with WAD lines that jumped around. The latest version now does this and the WAD lines are much smoother as a result.

Penetrations • Case 33236 When contact thickness is defined by factors TH_SF on *CONTROL_CONTACT, SFT on *CONTACT, SSF on *PART_CONTACT the algorithm that thins contact on small shells should not be ignored. This was done correctly for cases of defined thickness (TH, SST, OPTT) but incorrectly being applied for the factor cases. Now fixed. • Case 33923 When beam entity switch is set to off, these will no longer plot in contact contour plot. Previously the user had to explicitly blank all beams to suppress their plot.

Preferences • Case 34954 The oasys*manual_dir preference to set the directory where the manuals are located was being ignored by PRIMER. It is now read.

Program crash • Case 35418 PRIMER would crash on startup on a RHEL 6 or 7 machine if patch CVE-2016-0718 was installed on the machine. Now fixed.



Page 25

Properties • Case 34603 When saved property files were written from PRIMER or D3PLOT, then reread into either code, they worked correctly when the model onto which the properties are applied was identical to the model used when writing the file, but could lead to a 'Swiss cheese' problem if the model differed a bit, specifically if parts contained different elements. 'Swiss cheese' refers to the effect of leaving holes in the model when unexpected elements are blanked, although it was equally likely that elements that should have been blanked might not be. This was partly because the file was run length encoded, which meant that a [start…end] range of items was written on a single line if all items in the source range were the same. So if a part was entirely blanked then there would typically be a line giving the [start...end] labels in that part, which could cause problems if elements in that range in the target model were in fact in a different part. The other half of the reason was that both PART and part-based element properties were output, and the order in which they were processed was not strictly defined. Moreover, this led to unnecessary redundant output if all elements in a part had the same properties, and could lead to the first problem described above. To fix this the following changes have been made: (1) Part-based element properties are only written out for elements with properties different to those in their parent part. This often means that lines of element data can be omitted, making the files smaller and more efficient. It also greatly reduces the chances of the 'wrong' elements being included in a [start ... end] element range when the target model is significantly different. (2) PART and element lines can still be written in any order (to preserve backwards-compatibility) but when a file is read the order of operations is: Firstly process any PART lines and propagate their properties to their underlying elements. Then process any explicit element lines, which may have the effect of superseding the ex-PART properties. This gives a more consistent and predictable result, and by eliminating redundant blocks of run length-encoded element properties should - hopefully - reduce the 'Swiss cheese' effect when properties from model A are applied to different model B.

Read • Case 35251 PRIMER will now detect character labels in SET_GENERATE and warn the user about model errors. • Case 36717 PRIMER was not storing the correct label when reading *ELEMENT_BEAM_PULLEY cards. This has been corrected.



Page 26

Renumber • Case 34960 PRIMER could fail to renumber entities using the renumber tool after using certain functionality. This has been corrected. • Case 36714 The condense materials function was found to cause SIGSEV on a model with rigid materials. This arose from a failure to allocate enough memory when comparing character string field ALIAS. Now fixed.

Rigidify • Case 37354 Rigidify was failing to delete *CONSTRAINED_NODAL_RIGID_BODIES which use non-conventional set definitions (SET_ADD, SET_GENERAL, etc.). This has been fixed.

Scripting • Case 34199 Modified the way I was generating impactor while running the script. Earlier, I was subtracting shell thickness of 2mm from offset distance which was written out in log file. Now, creating impactor in such a way that outer surface dimensions’ match with the specification given in regulation (FMVSS-226). • Case 34200 Moved the text printed at points in x and z direction show that it remains visible from side view. • Case 34206 If no target point is located, script will not show visualisation panel, it will remain in model inputs panel. • Case 34823 In ejection mitigation script, depenetration is not required for model build if user has selected either 'Target point + offset' or 'Target Y-coord'. Depenetration related buttons on model build panel are now disabled, if user has selected either one of the option. • Case 35097 Script cross_section_curve.js was not working with multiple models, this has now been corrected. • Case 35469 SBA script was not generating good quality seat belts. Some new options have been added to improve seat belt fitting.

Sections • Case 34913 In *SECTION_SHELL_XFEM edit panel, XFEM card was losing data after enabling the beta angle card. This was due to incorrect addition to beta angle stack. It is fixed now.



Page 27

• Case 34916 In *SECTION_SHELL_XFEM edit panel with ICOMP = 1, NIP=8, there was a gap between beta angle and XFEM cards on edit panel. XFEM card was not repositioned correctly. It is fixed now. • Case 35461 When using 2d seatbelt elements it is important that the numbering of elements and nodes across the belt is topologically consistent, and PRIMER checks for this in various contexts, including the EDGSET definition on the *SECTION_SHELL card. Due to poor logic this check would sometimes give a false error for a set that was in fact correct, particularly if the ordering of elements in the set was not in lowest to highest label order. This check has been recoded to be independent of label order, and should no longer suffer from this problem.

Segments • Case 35850 The coat tool in segment mode has been modified so creation of a segment set is handled in same way as creation of a part for coating shells. This mean that the users can add segments for multiple faces to the same segment set in a sequence of operations.

Selection • Case 33007 The nodes or shells having edges that are shared by three or more shells create problems in determining proper Path-Area Object menu selections. The behaviour is streamlined to allow user have better selection process. • Case 34943 Trying to pick DATABASE_CROSS_SECTIONS in the graphics window did not always select the one that was closest to the mouse cursor. This has now been fixed and the 'predictive pick' sketch of which DATABASE_CROSS_SECTION will be selected has also been improved. A small box is now drawn around the point on the section to be selected to indicate why it was selected. • Case 35258 When using the 'Free edge' or 'Hole' object menu picking methods the selection worked correctly but the relevant rows in the menu of items were not highlighted to show what was picked. This meant that a subsequent click on a menu row might actually invert its selection status, i.e. 'unpicking' it, by accident. Now fixed.

Sensor • Case 36031 The sequence 'Keyword edit *SENSOR_SWITCH', and from within that keyword editor panel 'Edit *SENSOR_ID' caused a crash if the parent _SWITCH definition was modified in any way and the keyword editor was saved and updated while the child _ID editing panel was still open. This was caused by out-of-sequence updates inside PRIMER that arose when both parent and child editing panels were keyword editors, now fixed.



Page 28

Sets • Case 33442 PRIMER did not support using a negative label in *SET_PART_ADD to define a range. It now does.

Sketch • Case 35190 Sketch called sequentially off multiple edit panels could get confused about where to apply cross-hairs and CN for rotation. Now the first done edit sketch 'owns' the cross-hair. Subsequent sketches will just sketch until first done sketch is killed by explicit redraw.

Timestep • Case 33469 Corrected timestep calculation for elform 2,13 beams with IRR=0. These use IRR = ISS + ITT in the calculation. • Case 35889 Primer's calculation of timestep for thick shells (both isotropic and composite) has always been wrong. Now fixed.

Transform • Case 36354 Potential crash in DEFINE_TRANSFORMATION edit panel using POS6N with latent nodes resolved.

Undo • Case 34417 The general UNDO button would not 'undo' creation of multiple nodes in one click through the node creation panel (for example the create multiple along one-line method). This has been corrected. • Case 35374 PRIMER could crash when carrying out an UNDO operation after a whole model renumbering operation. This has been corrected. • Case 35447 Graphics bar UNDO button remains activated even if the PRIMER operation is not successful. Fixed this.

User interface • Case 35331 The cursors for Sketch, Find, Transparency and Set current layer were not being displayed properly over a white background. This has now been fixed.



Page 29

Views • Case 34454 When a modal window is used in PRIMER dynamic viewing is still possible. However, zooming using the mouse wheel did not work. Now fixed.

Volume 3 • Case 30818 ICFD_DATABASE_POINTOUT was missing from green keyword buttons. It is added now. • Case 36489 Program no longer crashes when volume III control cards are edited from a tree view.

Write • Case 33559 The default preference setting for HM comment writing is now AUTO which means HM comments will be written if any were found when the model was read. If the preference is set to OFF the comments will not be written. • Case 34911 Field headers for NPROC and FRSTP where not set for CONTROL_MPP_DECOMPOSITION_ARRANGE_PARTS. This has now been fixed. • Case 35586 When checking a model with *ELEMENT_BEAM cards with unspecified PID, PRIMER crashed. This has now been fixed. • Case 37409 EM_DATABASE_FIELDLINE keywords that do not contain optional cards are now correctly written out and read in.

X-sections • Case 36448 *DATABASE_CROSS_SECTION with RADIUS > 0 did not resolve correctly if ZCT > ZCH due to an error in the logic. Now fixed.

Xref • Case 33826 Cleanup unused has been corrected to remove *CONSTRAINED_INTERPOLATION where independent nodes have no external usage (no Xrefs to items of other type). • Case 35464 Load-curves referenced in *DEFINE_CURVE_FUNCTION string by LCnnn are now given a cross-reference. This means they will be supported for label change and “protected” from deletion e.g. by cleanup.



Page 30

2.2 D3PLOT


Adaptivity • Case 35428 D3PLOT could crash if an adaptive model was read in and the number of nodes didn't change over an adaptive re-mesh. If the number of nodes either increased or decreased then D3PLOT was OK. This has now been fixed.

Annotation • Case 37241 If the numerical format for the 2D graticule option was set to 0 decimal places then the numbers displayed on the screen had a trailing “.” so '100.' was displayed not '100'. This has been fixed.

Blanking • Case 36748 If multiple models were loaded into different windows in D3PLOT then the blanking status of models could get lost if some of the models were closed. If for example four models were loaded (one per window) into windows W1, W2, W3 and W4 and there was some blanking in model 4 (W4) the blanking status would be lost if any of the models in W1, W2 or W3 were closed. This has been fixed. • Case 34861 Using Quick Pick to blank by INCLUDE could blank the wrong items after starting the D3PLOT>T/HIS link. This has been fixed. • Case 34839 If a user carried out the following sequence of actions: 1. Select the blanking menu 2. Blank by parts 3. Select visible 4. Select parts using the blank circle 5. Reverse blanking using 'R' shortcut with blank menu still active then after the reverse blanking operation D3PLOT would appear to hang (it doesn't actually hang it just becomes very slow). A workaround was to close the Blanking menu before reversing the blanking using the 'R' shortcut. This problem has been fixed.



Page 31

Cut section • Case 36724 If items were excluded from a cut section then those items could not be picked using the new style object menus used in the Blank menu. Blanking using Quick Pick or the old-style menus did work correctly. This has been fixed. • Case 33990 For a cut-section defined with three nodes, the coordinates were recomputed every time the cut-section panel was opened. The coordinates are now only recomputed when the nodes are changed.

Data components • Case 37078 GetData generated an error message for SPC_F and SPC_M. This has been fixed and GetData now extracts the data for these components. • Case 36225 When reading results from double precision LS-DYNA that have been written in double precision (64 bit) format, D3PLOT normally converts results to single precision (32 bit) format during the read process, and then treats all data as single precision. In most cases this loss of precision is negligible. However, this can be significant if the size of the nodal coordinates is large in comparison to the size of displacements, since the displacements can be lost on subtraction of two large coordinates. In order to avoid loss of small displacements, comparisons of coordinates between reference states and between models have been changed to take place at 64-bit precision if the original files are in this format. Data components other than nodal coordinates are not affected, and are still stored and processed at 32-bit precision, so the memory usage and speed of the code is not significantly affected.

Deform • Case 36765 D3PLOT would crash if the undeformed geometry was drawn with free edges and the reference state was turned on and applied to the undeformed geometry. This has been fixed.

Envelope • Case 34403 If a model was in multiple windows which were displaying envelope data then any redraw event in a window (dynamic viewing, etc) would cause D3PLOT to re-scan and rebuild the envelope plot data. A work around was to open the same model multiple times instead of opening multiple windows that all reference the same instance of a model. This problem has been fixed.



Page 32

Explode • Case 36704 In Explode -> Automatic there are options From Origin, From Node, From Part. Previously if From Node or From Part was selected the button highlighting was not changed until a node (or part respectively) was successfully picked. This was disconcerting. The selected option is now highlighted before the picking.

General • Case 37321 Previously if D3PLOT was run with the options -d=tty and -exit it would not always exit. Now it does. • Case 35706 If a model was read into D3PLOT with an old (version 11) ZTF file containing spotweld information, the size of the spotweld spheres was calculated incorrectly, as the beam section information needed to calculate it wasn't present in a V11 ZTF file. This has been fixed.

Graphics • Case 36422 If multiple models were loaded into one window, the following set of actions could result in colour changes being applied to the wrong model. • Open model 1 (M1) • Open model 2 (M2) in the same window • Display only M1 (using arrow key) • Use Quick Pick to drag out an area round M1 with the right mouse button and then change

the colour of everything • Display only M2 (using arrow key) • Use Quick Pick to drag out an area round M2 with the right mouse button and then change

the colour of everything to a different colour • Swap back to M1 and the colour has also changed so that it's the same as M2 This has been fixed in V15. • Case 35856 D3PLOT would often crash if the draw update option in the States menu was changed to 'None'. This menu has three options. 'Release' (the default) means that when the slider is dragged the image is only redrawn once when the slider is released. 'Drag' means that when the slider is dragged through multiple states the image gets redrawn for each state. 'None' means that the image doesn't update until the user presses one of the HI, SH, CT buttons. In version 15 the 'None' option has been removed. When it was originally added systems were a



Page 33

lot slower and images could take a long time to redraw so it was useful but these days it's not needed.

Groups • Case 36631 Fixed an issue where D3PLOT was attempting to delete a Model's group file twice causing the program to crash on some Windows systems.

Image • Case 36746 On Windows, if the popup menu attached to the [-] button in the top left of a graphics window was used to save the contents of a graphics window to a bitmap, then the image would just contain an empty (black) graphics area. If the option to copy the image to the Windows clipboard was used then that would correctly capture the contents of the graphics window. This has been fixed.

JavaScript API • Case 37107 Fixed a memory issue when trying to access child models for the GetNumberOf() and GetWindowModels() JavaScript functions. • Case 37106 Fixed Pick() to work correctly with type codes MODEL and WINDOW. • Case 34906 Updated IsBlanked() so if the PART is empty this returns JS_FALSE.

Labels • Case 37247 If user defined names were defined for nodes (Utilities->Entity Names) then the ON/OFF switch in the menu didn't work for turning on and off the display of the names. The display of the node names could be on/off via the entity menu. This has been fixed. • Case 35330 If the option to label all attached nodes was used and the last node (highest ID) was attached to an element, then the label wasn't displayed for that element. This has been fixed. • Case 34946 In previous versions, vector plots could display 0 values for dynamic labels. This has now been fixed.



Page 34

Local axes • Case 35118 Beam local axes were not correctly displayed for beams with offsets and third nodes below the offset beam axis in analyses with NREFUP = 1. This has been corrected for analyses without dynamic relaxation. For analyses with dynamic relaxation and the above characteristics beam local axes may not be displayed correctly.

Measure • Case 36707 If measurements were being displayed in wireframe mode and perspective viewing was then turned on in the window the measurement line and end points disappeared. This has been fixed. • Case 36574 Previously, error messages arose if windows or models containing measurements were closed. The measurements are now being properly deleted and the error does not occur. • Case 36573 Previously, if measures were drawn with 'hidden line mode', extraneous labels and lines might appear on the plot. This has now been cleaned up. • Case 34976 If a window contained multiple models and a measurement was setup and then exported to the XY-DATA menu to produce an XY plot of distance versus time then D3PLOT would crash. A workaround for this was to animate the window containing the models once through all the states before setting up the measurement. This has been fixed. • Case 34777 Shortcut key 'M' now resumes measure from quick pick without the user having to press 'resume measure' button.

Menus • Case 37166 Previously in an object menu for 'Entity' if you opted to 'Key in' and entered a numeric value but with no letter prefix to identify the type of entity D3Plot would crash. Now it displays a warning message 'No Type Prefix' and does not crash. • Case 35429 If two models were open in separate windows and the display toolbar and options were used to display filenames rather than model titles, then when you merged all the models to W1 the display setting was not remembered for all models. This has been fixed.



Page 35

Metal forming • Case 37189 If a FLD or strain path plot was generated and the maximum x-axis value was less than 0 then the vertical axis was correctly drawn on the right of the plot but there wasn't enough space for the axis values to be displayed. This has been fixed. • Case 37018 For a model with multiple families the shell selection in the FLD plot window now persists when the state is changed to a state in a different family. The FLD plot now updates automatically when the state is changed.

Nastran • Case 34996 Reading in a NASTRAN OP2 results file from a model that contained a PLSOLID card would crash D3PLOT. This was because PLSOLID was not supported by D3PLOT. Support has now been added and the model can be read in.

Output • Case 37104 Keyword data output from D3PLOT now includes *END at the end of the file.

Properties • Case 37084 Before, if there were two models open and a properties file was written, it could refer to entity labels in the wrong model, or even cause D3PLOT to crash. This has been fixed. • Case 34602 When saved property files were written from PRIMER or D3PLOT, then reread into either code, they worked correctly when the model onto which the properties are applied was identical to the model used when writing the file, but if the model differed a bit, specifically if parts contained different elements, then the model could be left with unexpected holes where unexpected elements were blanked. This has been changed to give a more consistent and predictable result, which should reduce the production of undesired holes when properties from model A are applied to a different model B. • Case 30815 Default name for properties file for output files using the LSTC naming convention (d3plot, d3plot001, etc) is now oa_d3plot_xxx.prp to allow users to use rm d3* without removing the properties file. D3PLOT will still automatically recognise old properties files named d3plot_xxx.prp.

PTF compress • Case 36762 D3PLOT could crash when generating a cut-down (compressed) PTF file if during the process the main window was resized or if another window was moved in front of D3PLOT. This has been fixed.



Page 36

• Case 33148 Previously when the ptf compress part selection was read back in it did not reliably select all the parts, this has been fixed.

Quick pick • Case 37244 If the Quick Pick Entity type was changed to 'Spotweld Parts' then the Entity Type button didn't change to show 'Parts (sweld)' it remained as it was. This has been fixed.

Read • Case 36673 If the analysis title defined using *TITLE was longer than 40 characters, D3PLOT and T/HIS would only display the first 40 characters. In the PTF file format there is only space in the control block for the first 40 characters of the analysis title to be stored (in a single precision file). In recent versions of the PTF file an additional data block containing the first 72 characters of the title has been added and D3PLOT and T/HIS now read this additional block if present and use it. • Case 35132 D3PLOT would fail to read a set of contact force files if NFAIL was set to 1 on *DATABASE_EXTENT_INTFOR, as this option added additional data to the file to indicate which contact segments had failed and D3PLOT didn't recognise this additional data. This has been fixed. • Case 34675 [File] Scan states picked up new output states in an existing file family, but did not detect new file families if a model used adaptive remeshing. This is now fixed. Scan will look for and open new file families (d3plotaa, d3plotab, etc) if they exist.

Settings file • Case 34964 The state time is written to the settings file with 4 d.p.. Previously after reading a settings file the state number was determined by rounding up the specified time; now it finds the nearest state to the specified time. • Case 33278 Exploded part settings are now stored in property states within D3PLOT, are written out to the properties file, and can be reloaded from properties files.

Sketch • Case 35089 When items were sketched using one of the new object menus, then, unlike PRIMER, the items remained sketched in D3PLOT when the user generated a new plot using one of the plotting mode buttons (SI, LI, CT, etc) or a shortcut key.



Page 37

D3PLOT has been modified so that the behaviour is now similar to PRIMER, in that the sketched items are now cleared if the user updates the plot (dynamic viewing doesn't clear the sketched items).

Streamlines • Case 37239 Streamline max/min values not updated when a streamline group was turned off in a window (using the 'Shown in:' popup). This has been corrected. • Case 36984 Previously streamlines were only drawn on models that were visible in the graphics window. However, if the view changed and a model became visible, the streamlines would not be drawn on it. Users had to click 'Refresh’ to get these to draw. Now these are drawn automatically.

T/HIS link • Case 37230 If when running the D3PLOT > T/HIS link multiple graphs were setup and then one of them was deleted and recreated the graph could end up completely blank and some of the colours in one of the D3PLOT windows could be overwritten by the colours that T/HIS uses for its curves. This has been fixed. • Case 36965 D3PLOT could crash if, when using the D3PLOT > T/HIS link, the locate option in a T/HIS graph was used to locate a spotweld element in D3PLOT. This has been fixed. • Case 35539 D3PLOT could crash if the D3PLOT > T/HIS link was used and the option to pick items visually that you wanted to read results for into T/HIS was used. The crash would only occur if multiple models were loaded into both D3PLOT and T/HIS and if the option to display 'Common ID's' was set in the T/HIS entity menu. This has been fixed. • Case 34577 If, when running a D3PLOT > T/HIS linked session, the user pressed the arrow keys to change the D3PLOT state, then nothing happened if the mouse was in a T/HIS window. Similarly if a shortcut key that was assigned in D3PLOT was pressed while in a T/HIS window and the shortcut didn't do anything in T/HIS then shortcut key didn't do anything. From version 15 onwards, any shortcut keys (including arrow keys) that are pressed in a T/HIS window but do not do anything in T/HIS are now passed back to D3PLOT and processed as though they were pressed in a D3PLOT window. • Case 33824 When running the D3PLOT>T/HIS link, the tools area in D3PLOT didn't resize correctly if the user selected the option to compress the tools menu and to display it as a popup box. This problem was caused by the D3PLOT and T/HIS tools menus being independent of each other and one being compressed while the other was expanded.



Page 38

Version 15 has been modified so that, when previously it was possible to collapse/expand the D3PLOT tools independently of the T/HIS ones, they are now linked together so that if the user collapses one set of tools the other set are also collapsed. The logic behind this change is that if the user needs to collapse the tools to get more vertical space in one set of menus, then they probably want the same in the other set of menus. To make it easier to access the T/HIS tools when displaying the D3PLOT menus (and vice versa), the collapsed T/HIS toolbar popup is now available via the T/HIS button at the top of the D3PLOT menus. This means that if you are working in the D3PLOT menus and then want to quickly do something in a T/HIS menu, you can now simply right click on the T/HIS button at the top of the D3PLOT menu and select the T/HIS menu you want. Previously you would have to click on the T/HIS button to map the T/HIS set of menus and then click on the T/HIS menu you wanted.

User interface • Case 36530 D3PLOT could crash if you tried to debug a JavaScript in JaDe at the same time as running a script. This is now fixed.

User defined • Case 37028 In v14 if a user component was defined with the same name in the .ucf and .ubd files only the component in the .ucf file would be read. Since the .ubd file is model specific, the behaviour has been changed so that D3PLOT will read the component from the .ubd file. A message is displayed to inform the user which component has been used.

Utilities • Case 37232

Previously D3PLOT would allow PR plot of ENG_MAJOR_STRAIN or ENG_MINOR_STRAIN for cutdown results files that contained these components but did not contain the strain tensor, which is required to calculate the arrow direction. The results were displayed as 0.0 for all elements. These results are now shown as NC (not computed).

Views • Case 36658 If two models were read into the same window and then a pre-saved view was applied to that window, the two models were drawn correctly on the screen using the new view but screen picking items using Quick Pick didn't work correctly for the second model. As soon as any dynamic viewing took place in the window screen picking then worked correctly. This has been fixed.



Page 39

Volume clip • Case 37008 D3PLOT could crash if a model contained *DATABASE_CROSS_SECTION definitions that D3PLOT had read via the ZTF file and the cross sections were visible when a volume clipping definition was setup. This has been fixed.

Write • Case 37144 Previously in the write menu, the 'Format' popup to select the output filetype was available when the user selected 'output to screen', rather than when they selected 'output to file'. This has been corrected. • Case 35413 D3PLOT would crash if the command line was used to generate Envelope data using the WRITE menu. If, for example, the following was typed into the dialogue window, then D3PLOT would crash /WRITE ENVELOPE COMPONENT MAX_VALUE ENVELOPE STATES ALL NODE AV DX This has been fixed. • Case 35341 Fixed bug that meant GROUPS and INCLUDES buttons were not working in the WRITE Scan Menu.

XY plot • Case 37151 Previously in XY plot if only some states were selected then data points were plotted for states in the order they were selected, rather than being time ordered. They are now plotted in time ascending order.



Page 40

2.3 T/HIS


Curve menu • Case 36508 Users were unable to move a curve if there was only one curve active on the curve manager. This has been fixed. • Case 35184 If there were more than 1000 curves in T/HIS and the options to display a range of curves that have ID's > 1000 in the curve manager were used, the curve manager wasn't resetting to show the valid range of curves if a 'condense' operation removed all the curves in the range you were viewing. For example, if you had 1010 curves and were displaying curves 1001 - 2000 in the curve manager and you then deleted curves 1 to 1005 and condensed the curves that were left the highest curve you would have left would be number 5. The curve table would still, however, be showing the range 1001 - 2000. This has been fixed.

Curves • Case 37260 If the COR2 function was selected using the 'TOP BAR->Functions-> Automotive->COR2' button then the COR1 function was applied to the input curves instead of the COR2 function. If the COR2 function was selected via the Automotive Menu then it was OK. This has been fixed.

Datum • Case 36505 Fixed an issue whereby datum lines were not being correctly written to a FAST-TCF file when no model data had been read into T/HIS. • Case 36253 Fixed a bug whereby datum lines were not being handled correctly when logarithmic axes were active.

Dialogue command • Case 35854 If the dialogue command /WRITE CSV was used to output a CSV file with a '/' as the first character in the fi

Ltd Software Suite Version 15 · 2018. 5. 15. · 2.4 REPORTER 45 2.5 Shell 48. 3 Enhancements 50....

Documents

Transcript of Ltd Software Suite Version 15 · 2018. 5. 15. · 2.4 REPORTER 45 2.5 Shell 48. 3 Enhancements 50....