PRIMER 9.2

1. PRIMER 9.2

2. Contents • Keyword support • *DATABASE_CROSS_SECTION • *INTEGRATION • Other new keyword support • INCLUDE file + path > 80 characters • Preferences • Comments in INCLUDE files • Miscellaneous • Options on writing keyword file • INCLUDE file numbering ranges • Unique curve/Table ID for Mat 24 • Command-line commands • RADIOSS Block format translator • Model building and positioning • Automatic assembly of multiple models using a positioning file. • Positioning with the database & template system • New Template editing panel • Automatic free-motion headform (FMH) positioning • Error checking • Separate warnings & errors in the errors panel • The error tree • Error summary file • User-defined error checks • Active Model LS-DYNA is a registered trademark of Livermore Software Technology Corporation

3. MAIN MODEL IMPACTOR MODEL BUILD FILE OUTPUT AUTOMATIC SUBMISSION POSITIONING FILE Keyword file containing e.g. vehicle model Keyword file containing e.g. barrier View & build models automatically in Primer Output of analysis-ready models from Primer Creation of *.lst file for automatic submission and monitoring. CSV file containing positioning data Automatic assembly using a positioning file General positioning GENERAL_TR_ROT $ model, /directory/file.key impactor, barrier.key $ orient, nodes, base node, x node, y node rootname, odb depenetrate, partset, 3, XZ$ RUN1, 101.3, 899.9, 1393.1 RUN2, 225.1, 841.0, 1276.2

4. Automatic assembly using a positioning file • There are also two special cases for automatic assembly: • Pedestrian head impact • These are explained in the following slides. • Interior head impact

5. POSITIONING FILE MAIN MODEL IMPACTOR MODEL BUILD FILE OUTPUT AUTOMATIC SUBMISSION CSV file containing positioning data Keyword file containing e.g. vehicle model Keyword file containing e.g. headform model View & build models automatically in Primer Output of analysis-ready models from Primer Creation of *.lst file for automatic submission and monitoring. Automatic assembly using a positioning file Pedestrian head impact

6. POSITIONING FILE MAIN MODEL IMPACTOR MODEL BUILD FILE OUTPUT AUTOMATIC SUBMISSION CSV file containing positioning data Keyword file containing e.g. vehicle model Keyword file containing e.g. headform model View & build models automatically in Primer Output of analysis-ready models from Primer Creation of *.lst file for automatic submission and monitoring. Automatic assembly using a positioning file Interior head impact

7. Automatic free-motion headform (FMH) positioning • The Primer FMH tool now has the ability to automatically position the interior head impact free motion headform (FMH).

8. Automatic free-motion headform (FMH) positioning • In FMH select EDIT under CURRENT HEAD POSITION. • Automatic positioning is available for: • Vertical angle • XYZ position

9. Automatic free-motion headform (FMH) positioning • FMH auto-position example – initial position INITIAL POSITION SHOWING TARGET POINT INITIAL PENETRATIONS

10. FINAL POSITION AUTO POSITION FUNCTION USED Headform position adjusted for minimum penetration. Positioning may take place in the x direction, the xz plane or freely (xyz). Automatic free-motion headform (FMH) positioning • FMH auto-position • XYZ STARTING POSITION

11. Automatic Model Assembly Primer can assemble models from a Database of INCLUDE files. For each loadcase or model configuration, a template defines which INCLUDE files are selected. New Template Panel

12. loadcases Template Panel The Template Panel is new in Version 9.2. All templates can be viewed and edited together. components Add new tpl Copy existing template Add a new (blank) template Create a new template by copying an existing one – right-click on template name New Template Panel

13. Build Models Build multiple models by selecting from the list of templates. Primer writes the master keyword files and a keylist file (list of models). All the models may be submitted to the queuing system in one operation using the keylist file. New Template Panel components

14. Error checking • Separate errors and warnings in the error panel. • Carrying out an error check will now display the error tree as well as the error panel. • Many new error checks have been added in Version 9.2. THE ERROR TREE

15. ERROR INFO GENERAL ERRORS WARNINGS Accessed by right-clicking on the entity type General options Error specific options Warning specific options. Error checking Separate warnings and errors in the error panel.

16. Error checking – the error tree • Right-click on errors/warnings to edit, view, blank/unblank, delete or sketch the offending entity

17. Error checking – the error tree • For a more detailed study of the offending entity, use ONLY…

18. Error checking – the error tree • … and then ATTACHED to find connected entities

19. The error summary can also be written when writing out the keyword file Writing an error summary file

20. User-defined checking options • Set error checking options from inside Primer… Element quality Spotweld quality Rigid constraint size INCL file self-contained

21. User-defined checking options • Set error checking options from inside Primer… Timestep and added mass Joint stiffness Mat24 TH Output

22. User-defined checking options • … Or in Preferences (these become effective next time you start Primer) • Red=system-wide preferences • Green=user-specific preferences

23. Active Models • In Version 9.1, the Model List controlled only the visibility of models. • In Version 9.2 the Model List also determines which models are Active. • If only one model is Active, new entities will automatically be created in that model (in Version 9.1, Primer asked which model should be used). For operations on a model (e.g. Check), the active model will automatically be selected.

24. Active Models • Object menus now have tabs to separate the contents of the different models. • By default, entities from only the active model(s) will be displayed. • The tabs can be clicked to determine which models are listed. • If more than one tab is green, the entities in those models are listed sequentially (M1 then M2 then M3…) as in Primer version 9.1.

25. *DATABASE_CROSS_SECTION • New menu to Create and Edit DATABASE, CROSS_SECTION.

26. ‘Traditional’ method New, automatic method PSID manually defined here PSID defined by visible parts or those cut by plane. *DATABASE_CROSS_SECTION • A part set for the section may be defined manually, or using AUTO CREATE PSID, which can create part sets from either all visible parts or those cut by the defined plane.

27. *DATABASE_CROSS_SECTION • The cross-section orientation may be defined as: • Origin + vectors • Three nodes bust be picked, 1→2 defining local ‘z’ & 1→3 defining local ‘x’. • 3 nodes • Three nodes must be picked that lie in the plane (the first is the origin point). • Constant X/Y/Z • On node must be defined as the origin / centre (see next slide).

28. Centre of plane Origin of plane Picked note is at the geometric centre. Picked note is at the plane origin. *DATABASE_CROSS_SECTION • This node can either be at the centre of the plane, or the origin (for constant X/Y/Z planes only).

29. *DATABASE_CROSS_SECTION • Once the plane is defined, the finite cross-section may be dynamically altered using DRAG TRANSLATE …

30. About x About y About z *DATABASE_CROSS_SECTION • …or DRAG ROTATE.

31. *DATABASE_CROSS_SECTION • With AUTOCREATE, a new *DATABASE_CROSS_SECTION is created each time you click.

32. *INTEGRATION_SHELL • Recommended method to create a new integration rule for shells: Auto generate n layers

33. *INTEGRATION_SHELL • The coordinate and weighting factors can be viewed/adjusted as per the LS-DYNA input data • … or switch to “Simple Mode”…

34. *INTEGRATION_SHELL • Now the thickness of each layer can be changed, or new layers can be inserted. • The LS-DYNA input data (coordinate and weighting factor) are automatically calculated. • Each layer may use material data from a different Part ID (but all parts must use the same material type). This option is used for composites. • In LS-DYNA 971, *PART_COMPOSITE allows simpler definition of composite layers. This feature is supported in Primer 9.2.

35. INCLUDE file path options Space then + at end of line => continue on next line • LS-DYNA 970 6763 supports INCLUDE files with path names up to 240 characters. These are written to the keyword file thus: • Another new option in LS970 6763 is *INCLUDE_PATH. This keyword has a list of directories in which LS-DYNA will search for INCLUDE files. For example: • Primer 9.2 supports both these formats. *INCLUDE H:\DATA\TEMP\long_directory_name_1\long_directory_name_2\long_directory_name3_ + \long_directory_name_4_sub_version_35_different_materials\ver_verbose1\INCL\co + ntrol_standard2.key *INCLUDE_PATH /data/work/PROGRAM_A/BUILD_LEVEL_6 /data/work/PROGRAM_A/EXTRA *INCLUDE ENGINES/engine_v6.key SUSPENSION/susp_ver23.key e.g. LS-DYNA would find /data/work/PROGRAM_A/BUILD_LEVEL_6/ENGINES/engine_v6.key

36. Other new keyword support • Other LS970 keywords that can now be created and edited in Primer 9.2: • *AIRBAG_INTERACTION • *CONTACT_ENTITY • *CONTACT_INTERIOR • *CONTACT_GUIDED_CABLE • *DEFORMABLE_TO_RIGID • All new control parameters and *MAT types in 970 6763 • Primer 9.2 can read/write the majority of new LS-DYNA 971 keywords (and modifications to existing keywords). Known exceptions include *CASE and *EF. Many of these are also editable in Primer 9.2, such as *PETURBATION and *NODE_TRANSFORM. • The LS971 manual is due to be issued by LSTC in the summer of 2006. Around that time we will release an update to Primer to maintain full compatibility.

37. Edit Preferences • Users can change their preferences (customisable settings) from within PRIMER. • The new preferences take effect next time you start PRIMER. • Remember to Save Preferences before dismissing the menu.

38. Comments in INCLUDE files • Primer 9.2 preserves comments at the top of INCLUDE files • Comments can be edited from within Primer - access from Part Tree or from the Include menu

39. Comments in INCLUDE files • An existing text editor is invoked automatically by Primer – see later slide on selecting an editor. • Edit the text, then save and exit.

40. Comments in INCLUDE files • Comments are then written to top of INCLUDE file: • See also separate notes on automatically-generated comments: INCLUDE file mass, master model error check report. $> Include file H:\DATA\TEMP\suspension2.key $> (Used by master file H:\DATA\TEMP\test3.key) $> $> Created on Mon Nov 07 13:04:06 2005 $> $This INCLUDE file contains suspension components $Created by A. N. Engineer on 25th March 2005 $ $Change history: $ - Bush rates changed to Level 3 - Bart Simpson, 18th May 2005 $ - Added initial rotation of wheels - Maggie Simpson, 25th May 2005 $ $> end_saved_comments

41. Comments in INCLUDE files • Choice of text editor can be governed by preference text_editor • Set this to the full path of the editor program (this works only if the editor automatically fires up its own window – see next slide for how to deal with other editors). • Alternatively, set environment variable EDITOR to the full path of the editor program. Again, for this to work, the editor must fire up its own window automatically. On some unix systems, EDITOR may be set already.

42. Comments in INCLUDE files • To set a preference on unix for an editor such as vi that does not automatically fire up a window, create a 2-line script as shown below, and set the preference text_editor to the path to that script. #!/bin/csh -f xterm -title "Primer editing panel" -e vi $1

43. New options: Write • Error Summary can be created and written as a separate file, or at the top of the master keyword file as comments • Model mass, and/or the mass of each include file, can be calculated and written as comments

44. New options: Write $ ============= ERRORS =========== $ $ CONSTRAINED ERROR $ Separation of rigid bodies exceeds user defined tolerance (3) $ 11 12 34 $ $ NODAL_RIGID_BODY ERROR $ NODAL_RIGID_BODY_SPC: Dimensions of nodal rigid body exceed user defined maximum (6) $ 1001388 1001389 1001396 1001397 1001424 1001425 $ $ MATERIAL ERROR $ <LCSS> curves starts at Y <= 0.0 (4) $ 59 60 61 62 $ PIECEWISE_LINEAR_PLASTICITY: <LCSS> curve does not begin at X = 0.0 (6) $ 138 139 140 141 142 143 $ PIECEWISE_LINEAR_PLASTICITY: table curves cross at eps.lt.eppf (1) $ 226 • Example of error summary written to keyword file: • Example of model mass written to keyword file: $ $ Model mass is: 7.093e-001 $ Model C of G is: 2.965e+003 1.963e+001 6.139e+002

45. Numbering with INCLUDE files • Numbering ranges can now be defined for INCLUDE files $> $> end_saved_comments $ $PR_MIN_LABEL: 2000000 $PR_MAX_LABEL: 2500000 $ $PR_N_EL_MIN_LABEL: 2000000 $PR_N_EL_MAX_LABEL: 2500000 • These are written to the keyword file for re-use next time that INCLUDE file is read in.

46. Numbering with INCLUDE files • When new entities are created in a layer (INCLUDE file) that has ranges defined, the options for new labels now include “first free in layer” and “highest free in layer” • Primer 9.2 has an error check to detect any entities not obeying the given numbering ranges.

47. Unique curves for Mat 24 • New option to ensure each part has unique copies of stress-strain curves and tables for Mat type 24 • Complements MID=>PID and SID=>PID options that ensure unique material and section cards • Used in optimisation studies to allow separate control for each part

48. RADIOSS – BLOCK format input • A new input translator is available for RADIOSS Block format. • Details are given in the Primer user manual.

49. New command-line options • Model check summary file: • /CHECK MODEL n APPLY • /CHECK MODEL n CHECKFILE filename APPLY • Apply all available autofixes: • /AUTOFIX MODEL n APPLY • Model build from database/template: • /BUILD DATABASE database.dba TEMPLATE front.tpl SIMPLE • Model build from positioning file (e.g. multiple analyses for pedestrian, interior head impact, etc) • /BUILD READ example.csv

50. PRIMER 9.2