PRIMER 15 - Oasys€¦ · • Open specific pages in the LS-DYNA keyword PDF manual. It can be...
Transcript of PRIMER 15 - Oasys€¦ · • Open specific pages in the LS-DYNA keyword PDF manual. It can be...
Back to Contents Slide 1
PRIMER 15.0
Slide 2Back to Contents
PRIMER 15.0 - Contents
• Quick Find
• Tutorials
• Mesh Morphing
• Save Window Position
• Mechanisms
• Swages Mesh
• Composites
• Pedestrian Markup
• Decomposition
• Occupants
• Dyna Dummy Positioning
• *DATABASE_HISTORY
• Connections
• Parameters
• Node
• Meshing
• Beams on Nodes
• Preview Ruled Mesh
• Align Solids
• Contact Friction
• Orient
• Measure
• Mass Contour
• Checking Improvements
• Improved Model Read and Write
• Integration with Post-Processing
• Scripting
• Save Settings to Preference File
• Miscellaneous
Slide 3Back to Contents
Keyword Support
R10 Vol I Keywords
R10 Vol II Materials
R10 Vol III New solvers
✓
✓
✓
• PRIMER v15:
– Keywords: LS-DYNA up to R10 fully supported.
– Volumes I, II and III of the Keyword Manual.
– Some development “R11” new keywords/fields
also included.
Back to Contents Slide 4
Quick Find
Slide 5Back to Contents
Quick Find
A ‘Quick Find’ feature has been added to allow users to search for and then quickly:
• Go to menus / functionality in PRIMER.
• Open model entity edit panels.
• Blank / Unblank / Only Include files.
• Open tutorials.
• Open specific pages in the LS-DYNA keyword PDF manual.
It can be accessed by clicking on the magnifying glass above the model functions menu or by pressing
the ‘#’ key.
Typing in the textbox brings up a list of found items that match the entered text. Items in the list can be
selected by clicking on them or by using the up and down arrow keys and pressing enter. The selected
item will then perform the task, e.g. open a menu.
or
Slide 6Back to Contents
Quick Find
A ‘fuzzy’ matching method is used to match the entered text with the searchable items. It judges that
something has matched when the characters of the entered text appear in the same order as the item that
can be searched for.
For example if you type ‘mptp’ then ‘Tools->Measure->Part To Part’ would be a match, but ‘Tools-
>Measure->Point Angle’ wouldn’t because the final ‘p’ doesn’t match. (Note that the search is case
insensitive).
Additionally, if the entered search pattern contains spaces and the characters do not all match in the same
order then PRIMER will look to see if the words can be swapped to find a match.
For example ‘create node’ would find ‘Tools->NODE->Create’ even though the words do not appear in that
order.
This hopefully makes it easier to find items as you do not need to know the precise search term.
The found items are listed in order of how closely they match the entered text so items that more closely
match appear nearer the top of the list. It determines this by assigning a score to each match, with higher
scores given to items that contain consecutively matched characters and if the characters appear at the
start of words.
Slide 7Back to Contents
Quick Find
The default search term associated with a menu item is the trail of menus/buttons you would need to
manually open/press, e.g. to get to measure part to part you would need to go to Tools, then Measure
then Part to Part, hence the search term ‘Tools->Measure->Part to Part’.
In addition, some menus have alternative search terms associated with them. For example Measure Part
to Part can also be found from the alternative text ‘Distance Between Parts’:
This can be useful for cases where you don’t know or can’t remember under which menu some
functionality lives.
Note that the alternative text appears in brackets under the default search term so you can see how you
would get to the menu manually.
If you can’t find menus that you know exist in PRIMER it is likely that you are using different terminology to
what we expect. If so, please contact Oasys Ltd and we can add alternative text based on what you are
entering as your search text.
Slide 8Back to Contents
Quick Find
Alternative text associated with a menu may also describe some of the features on a menu. For example
the overlay colour of elements is set in the Display Options menus, but if you didn’t know this it would be
hard to find.
In this case the alternative text ‘Set Overlay Colour’ is associated with this menu:
As you can see the alternative text ‘Beam True Sections’ is also associated with this menu as the switch
to select this option is also on the Display Options menu.
Slide 9Back to Contents
Quick Find – Keyword menus
As well as Tools / Mesh Tools menus, menus that live under Keywords can also be searched for. For
example if you want to open the *ELEMENT_SHELL keyword panel you could type ‘eshk’:
Note that certain menus may not be searchable depending on the contents of any models loaded in
PRIMER. For example, if a model doesn’t contain any SPH elements you would not be able to search for
‘Keywords->ELEMENT_SPH->Modify’.
Keyword menus are coloured green in the list to help differentiate them from Tools / Mesh Tools menus
which are coloured blue.
Slide 10Back to Contents
Quick Find – Tutorials
If the installation of the Oasys Ltd software has the $OA_INSTALL/manuals/tutorials/primer directory it is
also possible to search for tutorials on certain topics. This should be the case in a full installation.
For example, to open the tutorial for checking a model:
Slide 11Back to Contents
Quick Find – LS-DYNA keyword manual
If the installation of the Oasys software has the $OA_INSTALL/manuals/lsdyna/keywords.txt file it is also
possible to search for a keyword and open the LS-DYNA PDF manual at the appropriate page. This
should be the case in a full installation.
For example, to open the manual at the *BOUNDARY_PRESCRIBED_MOTION page you could type
‘bprmman’:
Slide 12Back to Contents
Quick Find – Edit menus
If a model is loaded in PRIMER it is also possible to search for entities and open their edit panels, for
example if you wanted to edit a part with the title ‘Loadcell’ you could search for ‘editload’:
Note that this is limited to entities that can have titles, i.e. *NODEs, *ELEMENT_xxxx entities are not
searchable. This is so that the list of searchable items is kept to a manageable size.
Slide 13Back to Contents
Quick Find – Include files
If a model has include files they can be searched for and ‘Blanked’, ‘Unblanked’ or ‘Only’d:
For example to ‘Only’ the
hvac_03.key include file.
Slide 14Back to Contents
Quick Find - Preferences
In addition to the main Quick Find button in PRIMER the Preferences Editor now also contains a search
facility to help find preferences.
This works using the same ‘fuzzy’ matching method as the main Quick Find menu. The search terms
contain the name of the program, the name of the nodes on the tree, the preference name and the
description of it.
Slide 15Back to Contents
Quick Find
There are a few options that can be set to alter how Quick Find works. These can be accessed by
pressing the ‘Options >>’ button:
Save the settings to the oa_pref file.
Set which items are searchable.
Set the text colours.
Recently selected items are saved by PRIMER and
appear higher in the list of available options. By default
the last ten selected items are saved, but this can be
changed here. To turn it off set it to zero.
The number of found items displayed in the list can be
changed here.
Back to Contents Slide 16
Tutorials
Slide 17Back to Contents
If the installation of the Oasys Ltd software has the
$OA_INSTALL/manuals/tutorials/primer directory it
is possible to access tutorials on certain topics.
This should be the case in a full installation.
These tutorials can be found in ‘Help -> Tutorials’:
Tutorials
Back to Contents Slide 18
Mesh Morphing
Slide 19Back to Contents
Mesh Morphing
• In previous releases of PRIMER, you could use orient + interpolate to
“morph” mesh.
• In v15 a new interactive morph tool has been introduced.
• The morph tool allows you to create bounding boxes around mesh. You
can then interactively change the size and shape of the box which in turn
changes the size and shape of the mesh.
Slide 20Back to Contents
Mesh Morphing: Create tab
Mesh morphing can be accessed using Mesh Tools->Morph.
The mesh morphing tool consists of three tabs:
• Create tab: this tab includes options for creating a bounding
box surrounding mesh which the user wants to apply mesh
morphing on.
It is possible to create a bounding box in both GLOBAL and
LOCAL coordinate system. Using the latter option, it is
possible to identify a local coordinate system selecting 3
nodes in the model or directly selecting a
*DEFINE_COORDINATE_SYSTEM.
To select nodes to insert in bounding box, it is possible to
select node by PART, SHELL or directly by NODE.
Slide 21Back to Contents
Mesh Morphing: Morph tab
• Morph tab: this tab includes the interactive tools to modify
the shape of the bounding box and hence morph the mesh.
The mesh morphing algorithm acts on the mesh by moving a
HANDLE. A HANDLE is corner, edge midpoint or face
midpoint of a morph box.
It is possible to move a handle in any direction, both
individually using X, Y and Z options and all together using
FREE option. The MOUSE option gives the possibility to
move a handle in any direction using left (X), middle (Y) and
right (Z) mouse button.
There are two ways of interactively selecting handles:
• INTERACTIVE: using mouse pointer, the user can
modify one handle position at a time.
• SELECTION: using mouse pointer, the user can select
several handles first and then modify handles position.
Slide 22Back to Contents
Mesh Morphing: Morph tab (contd.)
A handle can be dragged in both GLOBAL and LOCAL
coordinate systems (CSYS). To identify a local coordinate
system it is possible to select 3 nodes in the model or
directly selecting a *DEFINE_COORDINATE_SYSTEM.
Finally, it is possible to undo the latest drag operation by
using the UNDO button.
Furthermore, it is possible to apply a specific displacement
value to a handle by using OFFSET option.
Slide 23Back to Contents
Mesh Morphing: Reset tab
It is possible to return at the initial configuration of a specific
morph box by using the RESET button.
Note morph bounding boxes are saved after *END when
PRIMER writes a model. This means they will be available when
reading the model into a later PRIMER session.
Back to Contents Slide 24
Save Window Position
Slide 25Back to Contents
Save window position
In PRIMER v15 if you reposition your menus, next time you open PRIMER they
will appear in this position.
Slide 26Back to Contents
Save window position
The save window position feature
applies to the following menus:
• Part TreeThe positions are saved in
.primer_menus_15 in your home area.
Delete this file if you do not want the saved
positions.
Set the preference save_window_positions to FALSE if you do not want the
window positions to be saved at the end of each session.
Back to Contents Slide 27
Mechanisms
Slide 28Back to Contents
The Coupler Connection
There is a new mechanism connection type COUPLER, which imposes a linear equation:
c1*(r1 or d1) + c2*(r2 or d2) = 0 or
c1*(r1 or d1) + c2*(r2 or d2) + c3*(r3 or d3) = 0,
Where:
c1, c2, c3 are user-defined coefficients and r1, r2, r3, d1, d2, d3 are rotation angles and translation distances of hinge or line connections specified on the coupler definition.
Most commonly only two connections are coupled. There are the following cases:
• Rotation against rotation.
• Rotation against translation.
• Translation against translation.
Slide 29Back to Contents
Coupler Between Rotation and Rotation
Assume we have got a mechanism with the following connections:
• Hinge 1 between green gear and red base with axis orthogonal to the parts.
• Hinge 2 between blue gear and red base with axis orthogonal to the parts.
As the radius of the blue gear is three times the radius of the green gear, the rotation r1 of the green gear is three times the rotation r2 of the blue gear, but in reverse direction, so:
3.0 * r1 + 1.0 * r2 = 0.
This can be defined as a coupler with coefficients c1 = 3.0 and c2 = 1.0.
r1 r2
Slide 30Back to Contents
Coupler Between Rotation and Translation
Here we assume a mechanism with the following connections:
• Hinge 1 between green gear and red base with axis orthogonal to the parts.
• Line 2 between blue rack and red base with horizontal axis.
If R is the radius of the green gear and the gear rotates by the angle r1 in radians, then the sliding distance d2 of the rack against the base is d2 = R*r1. This can be written as:
R*r1 – 1.0*d2 = 0,
so a coupler can be defined with coefficients c1 = R (in model length units) and c2 = -1.0.
r1
d2
R
Back to Contents Slide 31
Swages/Bead Creating
Slide 32Back to Contents
Mesh Tools -> Swages
• A new tool has been added to easily create swages/beads in shell
meshes.
Slide 33Back to Contents
Mesh Tools -> Swages (cont.)
• The tool takes inputs for swage mesh width (TOP/ BASE), swage
height and element sizes and remesh parameters values.
• The swages mesh is created along the NORMAL direction of the
shell element on which the first Swage path point was selected.
This direction can be reversed with the Reverse button.
• The SIDE ends of the swages mesh can take three different
types of shapes: CHAMFERED, SLANTED, VERTICAL.
• Also the SIDE surfaces for the swages mesh can be created with
these two methods: FREE, STRUCTURED.
• Original shell mesh is remeshed up to the distance from the
swages mesh defined by Remesh Distance and Break Angle.
• Add Remesh and Remove Remesh can be used to alter the
selection of shells to be re-meshed on the original shell mesh.
• Auto PID automatically uses the same PART ID from the shell
element on which the first swage path point was selected at.
• Swage mesh parameters can be saved as PRIMER preferences
with “Save Settings” button.
Back to Contents Slide 34
Composites
Slide 35Back to Contents
Manual Editing
PRIMER now automatically greys ply specific fields if it determines that the edit panel in question
belongs to PRIMER's internal ply/layup cards. The user can choose to override this functionality
by clicking on the "EDIT" tab.
Users can also edit multiple ply at the same time by using the "ctrl" and "shift" buttons and clicking on the
layer buttons. Now any value set on any of the selected plys is automatically copied over to all selected
layers.
This functionality is available on the PART, (T)SHELL and COMPOSITE_LAYUP panels.
Slide 36Back to Contents
Graphics Options
It is now possible to select and edit composite plys and layups using the quick pick menu . The
current options available for both plys and layups are:
• Blank.
• Unblank.
• Only.
• Information.
• Delete.
• Edit.
• Sketch.
• Find.
• Xrefs.
• Set current layer.
Please note that deleting plys and layups only deletes PRIMER's internal *COMPOSITE_LAYUP and
*COMPOSITE_PLY cards does not remove the corresponding data on the part/shell. This has to be done
from their corresponding edit/keyword panels
Slide 37Back to Contents
Orient
• The Tools->Composite->Orient panel offers several
techniques with which users can set Beta angles on
composite elements/parts.
• All operations in this tab apply to a selection of plys in a
layup.
• The user is first presented with an object menu from which
to select any layup in the model.
• This then opens up another object menu with all the plys in
the selected layup.
• The user can then select the required plys and the apply
any of the orient operations to these selected plys.
• There are four options which the user can use to set
composite angles, these are:
a) Rotate Fibres.
b) Set using Vectors.
c) Map Fibres.
d) Set Beta.
Slide 38Back to Contents
Orient: Rotate Fibres
• This option allows users to rotate the angles in the ply by the specified amount.
• The user has to enter the desired angle increment in degrees in the text box and use the + or - buttons to
rotate the fibres.
Slide 39Back to Contents
Orient: Set using Vectors
• This option basically consists of options which are present in the ply panel, but from here, they can be
applied to a selection of plys rather than just one.
• For more details on these options, please refer to the documentation on the ply panel.
Slide 40Back to Contents
Orient: Map Fibres
• This function can be used to interpolate fibres along map lines which can be specified by the user.
• The user has a choice of selecting free edges or map lines.
• The interpolation takes place based on the inverse (distace)^(2 x mapping parameter).
• The value of the mapping parameter is set to 1.5 by default but this can be changed by the user in
Options -> Program Options -> Composites -> Mapping Parameter.
Slide 41Back to Contents
Orient: Map Fibres(contd.)
Slide 42Back to Contents
Orient: Map Fibres(contd.)
• Free edges can be selected or rejected using the
mouse buttons.
• Map lines are lines along the surface of the ply and can
also be selected using the mouse.
• After the user is satisfied by the selection of free edges
and map lines, hitting “Apply” will start the interpolation
process and set the beta angles accordingly.
• This function can also be accessed from the _options
tab on ELEMENT->SHELL.
• The option is called “Map Beta” on this panel and it
functions similar to the corresponding option on the
composites panel.
Slide 43Back to Contents
Orient: Set Beta
• This option can be used to directly set the value of beta angles on the entire ply.
Back to Contents Slide 44
Pedestrian Markup
Slide 45Back to Contents
Pedestrian Markup
The CNCAP 2018 protocol can now be used to
mark vehicles:
This uses the plate method to find the corner
bumper.
The GTR protocol now uses this method too.
Slide 46Back to Contents
Pedestrian Markup
The outer surface around the front of the vehicle is now approximated using tape to span any gaps, for
example in the grill area.
This is used in the WAD line calculations to stop points on the line falling into gaps.
Slide 47Back to Contents
Pedestrian Markup
The sticks and tape used to markup the vehicle are now output to a separate model. They can then be
used as references for making design changes.
Slide 48Back to Contents
HIC Area Tool – Added in V14
• New interactive tool for calculating and interpreting
pedestrian head impact HIC area.
Slide 49Back to Contents
HIC Area Tool – V15 Enhancements
• New features and calculation methods added to HIC Area Tool:
Now possible to assign
and show a point name
as an alternative to a
value.
New tool to highlight which
points are close to changing
banding, based on an input
HIC delta value.
Yellow close to turning orange.
Green close to turning yellow.Option to edit an individual point by clicking it
on screen and typing a new HIC value.
New EuroNCAP v8 grid
method score calculation.
Back to Contents
Decomposition
Slide 51Back to Contents
Model Decomposition
• New utility script (available in Tools->script) allows you to easily see how a model has
been split across multiple CPUs for LS-DYNA analyses.
• Reads a *decomp_parts.ses file and changes the colours of the shells, solids and
beams in a model according to the decomposition.
Model courtesy of the NHTSA website: https://www.nhtsa.gov/
Back to Contents Slide 52
Occupants
Slide 53Back to Contents
New options for Dyna dummy positioning
New option to NOT attach cables to assemblies. This can be useful if the dummy is
over constrained when cables are attached to all the assemblies.
Cables
attached to all
assemblies
(default).
Press the ‘I’
toggle button
to ignore an
assembly so
cables are not
attached.
Back to Contents Slide 54
Combined Dyna Dummy Positioning
and Seatsquash
Slide 55Back to Contents
Combined LS-DYNA Dummy Positioning and Seatsquash
For a while PRIMER has had two separate tools to create LS-DYNA models for
positioning dummies and for performing a seatsquash analysis.
In v15 a new tool has been added that can create a single model to perform both
the dummy positioning and seatsquash in one analysis. It does this by creating
cables to pull the dummy into position and means that interactions between the
various parts are taken into account.
Slide 56Back to Contents
Combined LS-DYNA Dummy Positioning and Seatsquash
A floating window guides you through the process of creating the model.
The first stage is to select what type of analysis you want to setup. The options are:
• Dummy > Seat: Combined
dummy positioning and
seatsquash analysis
• Dummy: Dummy positioning
only
• One Stage: Position the dummy
and squash it into the seat in
one stage
• Two Stage: Position the dummy
in one stage and then squash it
into the seat in a second stage
• Displacement: Displacement
based cables
• Force: Force based cables
Slide 57Back to Contents
Combined LS-DYNA Dummy Positioning and Seatsquash
If a combined dummy positioning and seatsquash analysis type was selected, the next stage
will ask for information required for the seatsquash analysis (part IDs, dummy to seat contact
ID, etc.):
This data is entered in the menu in the bottom right
hand corner of PRIMER.
Slide 58Back to Contents
Combined LS-DYNA Dummy Positioning and Seatsquash
The next stage will ask for data required for the dummy positioning. This includes things like
which nodes the cables should be attached to, the analysis time, the stiffness for the cables,
etc.
This data is entered in the menu in the bottom right
hand corner of PRIMER.
Slide 59Back to Contents
Combined LS-DYNA Dummy Positioning and Seatsquash
To set up the analysis you need to define a starting position for the dummy, an intermediate
position (if the two stage analysis option was selected) and a final position.
There are two methods for defining these
positions:
• End Position – You define the final position
and PRIMER will calculate the starting and
intermediate positions. This is the quickest
way to define the positions.
• Sequential – You define the start,
intermediate and final positions. This takes
more time to setup, but gives you more
control over the positions.
You can define multiple end positions. PRIMER will create a model for each one.
Slide 60Back to Contents
Combined LS-DYNA Dummy Positioning and Seatsquash
Finally, if you selected a combined dummy positioning and seat squash analysis with the ‘end
position’ method you will need to define a vector to depenetrate the dummy out of the seat so
that PRIMER can calculate the start and intermediate dummy positions:
You can then create the model(s) to run in LS-DYNA. This will output a dynain file containing
the final coordinates which can be imported back into the original model.
Slide 61Back to Contents
Dummy Finger Positioning
• A new script is also included to easily create finger assemblies in a dummy model.
• This allows you to position fingers within PRIMER – which can feed into simulation
based positioning.
After: Dummies fingers can now be manipulated around a steering wheel.
Back to Contents Slide 62
*DATABASE_HISTORY
Slide 63Back to Contents
Editing *DATABASE_HISTORY
The edit panel for *DATABASE_HISTORY in PRIMER 14 has been
replaced with a generic keyword editor in PRIMER 15:
PRIMER 14
PRIMER 15
Slide 64Back to Contents
Include files for *DATABASE_HISTORY
PRIMER 14: Only one file selector
for all *DATABASE_HISTORY
definitions. If they are in different
include files, opening and closing
the panel may spuriously move
them to a different include.
PRIMER 15: The include file selector
can be opened individually for each
*DATABASE_HISTORY entry. It is
also possible to select multiple rows
and move the entries to a new
include simultaneously.
Slide 65Back to Contents
*DATABASE_HISTORY_NODE(_LOCAL)
PRIMER 15:
On the keyword editor the _SET, _LOCAL and
_ID suffices can now be selected all on the
same editor.
PRIMER 14:
There were two separate buttons
HISTORY_NODE and
HISTORY_NODE_LOCAL on the green
DATABASE popup. The former opened the old
edit panel and the latter a keyword editor, but it
was not easy to turn on or off the _LOCAL suffix
from either of these two panels.
Slide 66Back to Contents
Other advantages of the keyword editor
The keyword editor has also got other advantages:
• More robust handling of *PARAMETER references
• Ability to move *DATABASE_HISTORY definitions
into a *CASE
• Exit check messages when updating the cards
• More consistency with panels for other keywords
But: If you have got macros recorded in the panel in PRIMER 14 or older versions, you will need
to replace the lines on the old *DATABASE_HISTORY edit panel with something equivalent for
the new keyword editor to get them playing back in PRIMER 15.
The next few slides show how equivalent operations can be performed on the keyword editor.
Slide 67Back to Contents
Adding single new entries
In PRIMER 14 new entries were
made in the ID text boxes. There were
two different parts of the panel for
entries without and with _SET option.
In PRIMER 15 the ID needs to be filled in to the
entry box and then added by clicking Create. The
_SET option can be turned on and off at the
Suffices popup.
Slide 68Back to Contents
The _ID option
In PRIMER 14 the
*DATABASE_HISTORY
entries with _ID option
can be made visible by
toggling the _ID button.
In PRIMER 15 _ID option can be selected by
right-clicking in the Suffices column and then
turning on the suffix. All existing definitions with
and without _ID appear simultaneously on the
keyword editor unless they are filtered.
Slide 69Back to Contents
Removing entries
In PRIMER 14 on the
*DATABASE_HISTORY
edit panel entries can be
deleted by deleting the
text box entry or by
right-clicking the text
box and hitting
REMOVE.
In PRIMER 15 an entry can be removed by right-clicking on the
row and clicking Delete. The deletion should be confirmed by
clicking Delete Items -> Delete sel -> Continue.
Slide 70Back to Contents
Adding multiple entries
In PRIMER 14 multiple entries can be
added using the Add… buttons.
In PRIMER 15 the
MULTIPLE.. option at
the ID popup on the
entry row should be
used to open a similar
selection menu.
Slide 71Back to Contents
Removing multiple entries
In PRIMER 14 multiple entries can
be removed using the Remove…
buttons.
In PRIMER 15 multiple
entries can be removed by
clicking Options… ->
Select…, making a
selection from the object
menu, right-clicking on any
of the highlighted row
buttons and then clicking
Delete in the same way as
in the single remove case.
Back to Contents Slide 72
Connections
Slide 73Back to Contents
New Options for Spotweld Alignment
• New options have been added for the orientation and alignment of
spotwelds created in PRIMER:
Align solid with free edge – Align spotweld axis with closest free
edge.
Consider feature lines for alignment – Consider local feature lines
as well as free edges when aligning spotweld – a break angle can
also be modified to specify the feature line.
Always align flat edge – always align a flat edge of a solid
spotweld with the closest free edge/feature line.
Ignore inner layers for alignment – only consider the outer layers
of parts being joined together for alignment – i.e. ignore free
edges/feature lines on the inner layers.
Alignment search distance – Search distance for finding free
edges/feature lines near the spotweld.
Slide 74Back to Contents
Adhesive Patch – Cohesive Elements
• When creation adhesive patches, it is now possible to specify that any pentahedrons created follow the
cohesive node topology order (n1,n2,n3,n3,n4,n5,n6,n6) rather than the normal order
(n1,n2,n3,n4,n5,n5.n6.n6)
1
2
3
4
5
6
Back to Contents Slide 75
Parameters
Slide 76Back to Contents
Parameters in Model -> Merge
• There are now new options to control
the behaviour of parameters with
clashing names when merging
models. In PRIMER 14 some of these
definitions were lost without warning.
Slide 77Back to Contents
Renaming Parameters
• When changing the name of a
parameter on the edit panel and there
are several (probably _LOCAL or
_MUTABLE) parameters with the
same name in the model, PRIMER
now asks whether all of them should
be renamed at the same time.
Back to Contents Slide 78
Node
Slide 79Back to Contents
Node Drag
• Now in node->drag panel using N1-
>N2 mode, it is possible to select the
first node on the target model and the
second node on any models.
• Also in the node->drag panel, it is
now possible to drag nodes in the
screen XYZ direction.
Back to Contents Slide 80
Meshing
Slide 81Back to Contents
Improved Meshing
• General meshing quality improvements:
Slide 82Back to Contents
Improved Meshing
• Removing holes with a large curvature is more reliable:
Slide 83Back to Contents
Improved Meshing
• Adding ‘caps’ using planar surface option is more reliable:
Slide 84Back to Contents
Improved Meshing
• Removing highly irregular holes is more reliable:
Slide 85Back to Contents
Creating Holes
• When creating holes, the user can now set the washer layers to a specific
part ID.
Slide 86Back to Contents
Mesh Splitting
• Some modifications have been made for the
case of spitting triangular meshes into two.
• Now splitting occurs along the longest edge
and if there is a possibility of nodal merging,
then that option is preferred.
• This should reduce some of the mesh
transition issues that used to occur with this
type of mesh splitting.
Back to Contents Slide 87
Beams on Nodes
Slide 88Back to Contents
Mesh Tools -> Beams -> On Nodes
• Added a new tool in Mesh Tools-> Beams-> On Nodes.
• The tools lets user to pick any number of nodes and
create beams joining those nodes in the pick order.
• All beams will have same part (PID) and orientation node
(N3) defined in the panel. N3 is kept optional for creation
of beams.
• The beams will be created connecting nodes in the exact
order of selection by the user.
• An extra beam can also be created connecting the first
and the last nodes in the selection list. This is based on
the user selection in 'Create as' pop-up option.
• Also, added a new UNDO type and its preference for this
purpose: "undo_beam_on_nodes".
Back to Contents Slide 89
Preview Ruled Mesh
Slide 90Back to Contents
Mesh Tools -> Mesh -> Ruled Mesh
• Added a new ‘Preview Mesh’ button for RULED Mesh
panel.
Back to Contents Slide 91
Align Solids
Slide 92Back to Contents
Align Solids
• Added menus into “Solid Align” panel to allow the user to
align the solid elements along at least one and at most two
element axes.
• Seed align should be used if you wish to align elements to
the vector directions defined by nodes of another
element. Vector align should be used if you wish to align
elements with a specified vector, either defined by an input
box or by selecting 2 nodes.
• "First Align" is the first axes to be aligned and "Second
Align" is to align the second axes after alignment of the
first axes. Second axis alignment is optional.
• When the second align option is ON, the "Vector Align" is
not possible.
• To align the second axes, the first axes alignment may
have to be changed. For this purpose, the "Angle
Tolerance" value can be modified. This value is the
maximum angle allowed between the final first axes and
the first axes direction achieved.
• Also added a new preference "align_solid_axes_tol_angle"
for Angle tolerance. Default value 15.0. Limits (0.0 - 90.0).
Back to Contents Slide 93
Contact Friction
Slide 94Back to Contents
Investigating Friction
• Contact friction coefficient values are important in any LS-DYNA model.
• There are now a variety of ways of setting friction coefficient values used
in contacts:
• The *CONTACT card itself.
• The *CONTROL_CONTACT card.
• *PART_CONTACT cards.
• *DEFINE_FRICTION cards.
• If you have a combination of the above methods, it can be difficult to
understand which friction coefficient values are used in your model.
• New tools in PRIMER allow you to investigate these values.
Slide 95Back to Contents
Contact Friction Write
• Select the contacts
• Select output file
formal Excel or Csv.
• Enter the destination
file
• Provide image
dimensions and
background details
• Hit ‘Apply’ to write
Slide 96Back to Contents
Contact Friction Plotting
• Select a part. After part selection a list of all
contacts which refer to the selected part will
be shown.
• Select a contact from the list followed by
‘Apply’.
• All the parts in the selected contact will be
shown in the exploded view.
Back to Contents Slide 97
Orient
Slide 98Back to Contents
Orient
• In the node drag panel using N1->N2
mode, it is now possible to select the
first node on the target model and the
second node on any other model.
• In the project panel, when projecting
using the arbitrary plane, it is possible to
select an additional optional node which
can be used to offset the selected
projection plane to that nodal location.
This optional node can be selected
using the "Pick O Nd" button.
• It is now possible to select *SHELLS
and *SET_SHELL as the contact target
in orient using contact.
Back to Contents Slide 99
Measure
Slide 100Back to Contents
Measure – Node to Node
• In the Node to Node panel, it is now possible to
edit the vector box and set N2 based on the input
vector direction and/or magnitude.
Slide 101Back to Contents
Measure – Part to Part
• Part to part measure now supports contour plot
• Multiple parts on each side can be included
• Measure updates as parts added/removed
Slide 102Back to Contents
Mesh Volume Analysis Tool
This is a tool for analysing the volume of
closed meshes.
Key features include:
• Advanced visualisation such as liquid
line visualisation.
• Choosing tilt angles or Local
Coordinate Systems.
• Calculations on fuel tank:
• Full tank volume.
• Step-by-step volume calculation.
• Wetted surface.
• Writing these results to Excel.
Slide 103Back to Contents
Step-by-step volume calculation:
• Input volume - output height
• Input height - output volume
Mesh Volume Analysis Tool
GUI panel.
Wet surface area up to the line.
Relative
height
Liquid
volume
Wet
surface
20 4171 1254
18 4049 1154
16 3727 1015
14 3259 884
12 2689 760
10 2073 633
8 1456 490
6 886 358
4 424 238
2 113 91
Relative
heightLiquid
volumeWet
surface
17.6 4000 1123
15.0 3500 958
13.1 3000 822
11.4 2500 720
9.8 2000 610
8.2 1500 501
6.4 1000 391
4.4 500 254
Excel results.
Excel results.
GUI panel.
Back to Contents Slide 104
Mass Contour
Slide 105Back to Contents
NS MASS CONTOUR: Part plot vs Nodal plot
• Contour Plot > Part Mass (NS added mass) gives
aggregate value for added mass on part (or part set).
• For details of local mass distribution use Node Plot > Node
Mass with ELEMENT_MASS_PART selected under
settings.
Back to Contents Slide 106
Checking Improvements
Slide 107Back to Contents
Model Check
• Model checking continues to be an integral part of PRIMER.
• ~500 new checks added into v15 compared to v14.
• Now ~7200 individual checks in PRIMER.
Slide 108Back to Contents
Model Check reports omitted keyout items
When keyword output targets a version of LS-DYNA that pre-dates new keywords, or new data fields on
existing keywords, PRIMER has historically reported this only during keyout itself, for example:
This was annoying because you only discovered unsupported keywords when you came to write the model
out to disk.
This information is now captured during Model Check and is reported along with “ordinary” errors/warnings.
For example here is the Model Check error tree output from the Model above:
Slide 109Back to Contents
Model Check reports omitted keyout items
This is configurable in the Model Check, Options panel
under category “Other”:
• The LS-DYNA output version can be set here (this is
the same as the setting in the Model Write panel).
• Omitted keywords can be reported as warnings
(default) or as errors, or the check can be suppressed.
This status can be stored as a preference.
Limitation:
This information is only available in the context of Model Check, it will not appear in “local” checking
functions, for example from an editing panel.
This is because it requires a “pseudo-keyout” pass through the model to collect and store errors, which is
information that can become out of date very quickly as the model is edited, so it cannot be stored and re-
used.
Slide 110Back to Contents
“Check” generally shows more details
PRIMER’s “check” functions have always summarised data briefly, for example:
ERROR: JNTC_13 JOINT_xxx: Node 1 is not on a rigid body
ERROR: JNTC_29: Nodal pair (1,2) not coincident. Fails LS-DYNA test
They also have the ability to give more detailed information about the error, for example:
(Nodal separation = 1.3e-2, exceeds 1.0e-3 LS-DYNA test)
(Node list is: 11369 22414)
(No rigid part/set for node 1)
However this “detailed” information was not reported in all contexts, meaning that it was sometimes
necessary to resort to a different checking context, or maybe to edit the item, to find out more information
about the problem.
“Detailed” checks are now the default in most contexts, in particular under the [Keyword] Check
summaries.
Slide 111Back to Contents
Dashboard Improvements
• Can now compute model health using the results of all other dashboards.
• This should be done in the script named “model_health.config.js” which should be placed
along with the other user defined dashboard scripts.
• Results from all other dashboards can also be accessed from this script.
• A new tile called “Keyword Cull Check” has been added to the dashboard which lists all the
keywords/fields which will be culled by writing out the model in the current LS-DYNA output
version.
• The dashboard can now be run in batch mode using the syntax:
• DASHBOARD MODEL <n> DASHFILE <filename> APPLY
Slide 112Back to Contents
LS-DYNA Output File Reader – V14
Slide 113Back to Contents
LS-DYNA Output File Reader – V15
• In addition to errors and warnings, PRIMER can now read “termination”
style messages:
Slide 114Back to Contents
LS-DYNA Output File Reader – V15
• The dyna output reader can now be run in batch mode using the syntax:
• DYNA_OUTPUT MODEL <n> DYN_OUT_FILE <filename> APPLY
Back to Contents Slide 115
Improved Model Read and Write
Slide 116Back to Contents
Improved Model Read and Write
Model read and write speeded up.
• Parallelisation and efficiency improvements mean that V15 reads a typical model in about 60% of
the time of V14.
• Model write is also faster taking about 70% of the time, but if a model has many include files then
the speed up will be greater.
• Input and output to a slow network disk are also improved due to better buffering and
parallelisation.
New optional Binary keyword output format added
• Files start off in ASCII, so the tops of file (e.g. comments) remain readable.
• After (new) *START_BINARY keyword they swap to binary.
• Binary file size is typically 30% of original ASCII keyword file and writes to disk in about 25% of the
time of the equivalent ASCII file. File read is also faster than ASCII as no conversion is needed.
• Binary format preserves original formatting, and can be turned back into a normal ASCII formatted
keyword file using a standalone programme as well as PRIMER.
• Binary format is used for “Undo”, speeding up the disk i/o of this substantially.
Slide 117Back to Contents
Improved Model Read and Write (ctd)
Optional data compression has been added.
• Files can be compressed to gzip (.gz) format typically found on *nix systems. So “name.key”
becomes “name.key.gz”.
• Files can also be compressed to Winzip (.zip) format typically found on Windows systems. So
“name.key” becomes “name.zip”. Models with multiple include files can be compressed into a
single .zip archive containing master file and all includes in an embedded INCL directory.
• The degree of compression is user-configurable, the default level giving file sizes about 25% of the
original ASCII files. This default is the lowest level of compression since this fastest, higher levels
can be used to give smaller files, but at the expense of longer keyword output times.
• Binary format can also be compressed, typically resulting in files that are < 20% of the size of the
original ASCII files.
The following table shows file sizes and timings for reading and writing a typical 5m element
automotive model using the various format and compression options.
Vers-
ion
Original ASCII file
(592MB)
Binary file
(201MB)
Compressed ASCII
(159MB)
Compressed
binary (98MB)
V14 Read 25s Write 45s n/a n/a n/a
V15 Read 17s Write 33s Read 10s Write 9s Read 16s Write 30s Read 11s Write 10s
Slide 118Back to Contents
Improved Model Read and Write (ctd)
The Model Write panel has been reconfigured to use “tabs”, making it clearer and easier to use
on a shallow display (e.g. wide screen laptop).
The new “Compress” tab (on the right above) gives access to the new compression and binary
output options.
(Input of binary and compressed files is automatic: the file type is deduced from its extension, and
sections of binary encoding from the *START_BINARY keyword in the file itself.)
Back to Contents Slide 119
Integration with Post-Processing
Slide 120Back to Contents
Integration
• With the Oasys Ltd. products you would traditionally look at LS-DYNA
input files and output files separately.
• It is often desirable to access both sets of information at the same time,
for example:
• With output results, wanting to look at material properties for a part that has
failed.
• In the input model, wanting to look at spotweld failure of a current analysis
when deciding how to change your spotweld configuration.
• The ZTF file (written by PRIMER) allows some model information to be
transferred to D3PLOT to aid this.
• In V15 there is also an ability to open one piece of software from another
with the contents linked to allow easy access to both sets of information.
Slide 121Back to Contents
Integration
Shared memory
Can exchange:
- Viewing attributes
- Cut sections
- Model data
Shared memory
Can exchange:
- Curve information
- Edit entities
Socket link
Can exchange:
- Timeline etc.
Slide 122Back to Contents
Integration
A new capability to link PRIMER and the post-
processing tools (D3PLOT and T/HIS) has been
added in version 15
This option is activated by clicking on the POST
button at the top of the PRIMER Tools Menu.
This option opens a shared memory connection
between PRIMER and D3PLOT/T/HIS that allows
commands and data to be exchanged between the
two codes.
The POST button launches the “Post” status panel
shown here, from which linkage is managed.
Slide 123Back to Contents
Integration
Add to D3PLOT
Find Results
Disconnect
PRIMER has found the results
automatically.
PRIMER cannot find the results,
browse for it manually to add this
model to the D3PLOT or T/HIS
session.
Model is currently linked with
D3PLOT or T/HIS. Disconnect the
link. Both programmes are left open
but they are no longer synchronized
Add to T/HIS
Slide 124Back to Contents
Integration: PRIMER <-> D3PLOT
It is possible to synchronise the following attributes across the D3PLOT link:
Viewing: The current view (orientation, scale, position) including dynamic viewing.
Visibility: The current blanking and entity visibility status.
Attributes: The colour, transparency and plotting mode.
Xsec: Cut-section attributes, including dragging.
Slide 125Back to Contents
Integration: PRIMER <-> D3PLOT
D3PLOT PRIMER
Plotting modes,
blanking, zoom levels,
cut sections are all
synced
Slide 126Back to Contents
Integration: PRIMER <-> T/HIS
Load curves can be sent from PRIMER to a linked T/HIS session. T/HIS can then
perform various operation on these curves and the updated curves can be sent
back to PRIMER.
Back to Contents Slide 127
Scripting
Slide 128Back to Contents
JavaScript API – New Features
• Now it is possible to read a JT format file by using Model.Read("/data/test/file.jt", Model.JT, 10).
• It is now possible to launch a contact pen check edit panel by using Contact.PenCheckEdit().
• The WidgetItem class now supports the monospace property.
• The Shell class now has an Area() method to calculate the area of the shell.
• The Solid class now has an Volume() method to calculate the volume of the solid.
• Shell.MakeNormalConsistentFlagged() now returns an array containing the shells that have had
normal reversed.
• The Model class now has a CopyFlagged() method to copy flagged items to another model.
• The Window background property can now be used with the output from Colour.RGB().
• The Material class now has a optionalCards property to query and an AddOptionalCards() method to
add any optional extra cards for the material.
• CrossSection.Properties() now includes center of gravity in the global coordinate system.
Slide 129Back to Contents
JavaScript API – Visual Studio Intellisense
Writing JavaScripts can be time consuming when trying to remember which
functions are available in which classes and the number and order of arguments
in the functions. To find out, you would normally have to go searching for it in the
manual and doing this over and over again is frustrating and time consuming.
One way to speed up writing scripts is to use software that provides information as
you write your script. One such program is Visual Studio (produced by Microsoft)
which uses something called ‘Intellisense’ to list objects, functions and parameters
as you type, e.g.
List of
functions/properties Select the function Press the ‘Tab’
key to select
Slide 130Back to Contents
JavaScript API – Visual Studio Intellisense
In v14 a primer.intellisense.js file located in the ‘Oasys 14/Intellisense’ directory could be
used to provide Intellisense for the PRIMER JS API, e.g.
The latest version of Visual Studio can no longer use this file; it now uses a Typescript
declaration file (*.d.ts) instead. In v15 this is provided as well as the old file, so either
version of Visual Studio can be used.
Note that Visual Studio downloads are large (a few GBytes) and an alternative is to use
Visual Studio Code. This is a lightweight code editor with excellent support for JavaScript
editing. We would recommend using this instead of Visual Studio. A word document in the
Oasys 15/Intellisense directory gives instructions on how to download it and set things up
to use the Intellisense file.
Show static functionsShow a description of the function
and parameters, list the parameters and show the return type
Slide 131Back to Contents
JavaScript API – Widget Image Colours
In v14 PRIMER only supported a limited number of colours for widget images.
In v15 PRIMER now uses full 24 bit colour for images.
Slide 132Back to Contents
JavaScript API – Font Sizes
• Font sizes of
Widget.LABEL and
Widget.BUTTON can now
be controlled though the
Javascript API.
• Both LATIN1 and UTF-8
encoded fonts are
supported on Windows but
Linux only supports
LATIN1.
• Currently only the following
point sizes are supported:
8, 10, 12, 14, 18, 24.
Slide 133Back to Contents
JavaScript API – Keyout Hook
• PRIMER now supports the running of a JavaScript “hook” just before writing out a keyword
deck.
• This can be used by customers to enforce company specific best practice rules/guidelines
when writing out a model.
• This script can then be used to either proceed with or abort the keyout process.
• The script should be located in primer_library/scripts/hooks/ and should be named
“keyout_hook.js”.
• This hook is currently active from the regular model write tab, the dialogue box and the
include tree.
Slide 134Back to Contents
JavaScript API – File.ReadCSV()
• Now it is possible to read a CSV file through Javascript API ReadCSV()
in File Class.
• The API reads the input CSV file and returns an array of string arrays.
• If the CSV file has legitimate records the function returns an Array object
containing sub-arrays of strings otherwise the function returns NULL.
• The lengths of all the sub-arrays are the same and equal to maximum
number of fields in any of the records. For records in a CSV file having
fewer fields, the respective sub-arrays are padded with NULL elements
to the maximum array length
Back to Contents Slide 135
Save Settings to Preference File
Slide 136Back to Contents
Save Settings to Preference File
• Settings for Seatsquash Squash, Import and Export options can now be
saved directly to the oa_pref file using new buttons.
Back to Contents Slide 137
Miscellaneous
Slide 138Back to Contents
Renumber Rigid Patches
• It is now possible to renumber small
rigid patches. A small rigid patch is
defined as a rigid part with is smaller
than a specified reference length.
• The reference length (w.r.t. part
diagonal) can be set in the Options-
>Program options->Renumber panel.
• While working on RIGID_PATCHES,
the parts which are classified as rigid
patches are excluded from the PART
tab in the same panel.
Slide 139Back to Contents
Seatbelts Panel
• It is now possible to launch the
seatbelts fitting options panel from the
main fitting panel as well.
• This panel is also launched when
initially entering the “2. Fit->” panel
and from ‘Define path->Tools…”
Slide 140Back to Contents
*INCLUDE_STAMPED_PARTS
• It is now possible to read all the
*INCLUDE_STAMPED_PART
definitions in the entire model by right
clicking on the model icon and clicking
on the 'Read all S.P." button.
• This read function automatically
merges any nodes which may be
present and a summary of the labels
decashed/merged is presented to the
user.
• It is also possible to read in stamped
parts from the quick pick menu for
*PART.
Slide 141Back to Contents
Model ->Write – do not write xref comments
• By default PRIMER will write cross reference information as comments for load curves and sets. This
can increase file size significantly on certain models that use a significant number of load curves or
sets. A new model write option has been added to allow the user to turn off the writing of these
comments.
With this option OFF,
these comments will
not be written (default
is ON
Slide 142Back to Contents
Cut Section Properties
• The cross section panel now
includes center of gravity in the
global coordinate system.
Slide 143Back to Contents
Part Tree
• The part tree now has an option
which can be used to create
items.
Slide 144Back to Contents
PRIMER’s local element axes function now includes support for thick shells
*MAT aopt specifications, *PART_COMPOSITE, _BETA, _COMPOSITE (on *ELEMENT_TSHELL) are all
supported
Thick Shell Local Element Axes
Slide 145Back to Contents
Save and restore ‘Part tree’ window position and size
• When PRIMER is closed and re-opened, the position and size of the ‘Part tree’
window is restored.
• In PRIMER 14 this window was always docked when PRIMER was re-opened.
Slide 146Back to Contents
Contact Information
For more information please contact the following:
www.arup.com/dyna
or contact your local Oasys Ltd distributor
UK:
The Arup Campus
Blythe Valley Park
Solihull
B90 8AE
United Kingdom
T +44 121 213 3399
China:
Arup
39F/41F
Huaihai Plaza
1045 Huaihai Road (M)
Xuhui District
Shanghai 200031
China
T +86 21 3118 8875
India:
Arup
Ananth Info Park
HiTec City
Madhapur Phase-II
Hyderabad 500081, Telangana
India
T +91 40 44369797 / 98