PRIMER 22.1

The Dialogue Command Structure

The command structure forms a hierarchical "tree", with the top-level PRIMER_MANAGER at its "root".

The following rules apply:

Command words may be abbreviated to any degree so long as:
- they are unique in the context of their current menu
- they must have at least their first two characters given
For example READ DK_DYNA_KEYWORD may be abbreviated to RE DK .
Navigation up and down menu levels is performed as follows:
- <command> takes you to that command's (sub-)menu level
- Forward slash "/" takes you back to the top PRIMER_MANAGER level before executing the following command(s)
For example READ above takes you down into the READ_MODEL sub-menu
The command /WRITE DK would work at the READ_MODEL prompt because it would return to the top level before parsing the WRITE command
There is also a "global menu" of commands which is available at any (sub-)menu prompt.
- These are primarily graphics commands that do not require a context.
- The commands can be listed with the GM (for Global Menu) command
Any command can be aborted by typing Q (uit). This will return control to the next highest command prompt in the "tree".

At any prompt you can type H (elp) to receive advice about what to do next.

Commands that perform model-based operations:

READ

Reads in models in the following range of formats:

DK_LSDYNA_KEYWORD		Reads Ansys LS-DYNA keyword input decks
BDF_NASTRAN_BULK_DATA	TRANS	Nastran "Bulk data" (.bdf) file
UNV_UNIVERSAL_FILE	TRANS	Ideas/Master Series "universal" (.unv) files
RADF_RADIOSS_FIXED_FORMAT	TRANS	Radioss fixed format "starter" (00) files
RADB_RADIOSS_BLOCK_FORMAT	TRANS	Radioss block format "starter" (00) files
PNF_PATRAN_NEUTRAL_FILE	TRANS	Patran 2.5 "neutral" (.ntl) file
SAP_2000	TRANS	SAP 2000 input (.s2k) files
ABAQUS	TRANS	Abaqus keyword input decks

In all cases the syntax is READ <format> <filename> <target model id>
for example: READ DK test.key 2

All the "non- LS-DYNA " options imply a degree of translation, click on the TRANS buttons in the table above to view the relevant sections in Appendix F which describe translation during input.

WRITE

Writes out models in the following range of formats:

DK_LSDYNA_KEYWORD DB_LSDYNA_KEYWORD DM_DYNA_MERGE_INCLUDES DO_DYNA_OMIT_INCLUDES		All four options write out Ansys LS-DYNA keyword files: DK writes separate include files DB writes out the master file only DM merges include data into a single master file DO omits data in include file
BDF_NASTRAN_BULK_DATA	TRANS	Writes out the model in Nastran Bulk Data File (BDF) format.
I5_IDEAS_LEVEL_5 I6_IDEAS_LEVEL_6 MS_IDEAS_MASTER_SERIES	TRANS	All three options write Ideas or Master Series universal files, but the modules used reflect the version chosen.
P25_PATRAN_2.5_NEUTRAL P3_PATRAN_3_NEUTRAL	TRANS	Some of the <config> arguments change between Patran levels 2.5 and 3 neutral files.
ZTF_FILE		Writes the <name>.ztf file for post-processing in D3PLOT
GROUP_FILE		Writes <namennn>.bin file(s) to make *GROUP data available for post-processing in D3PLOT
PARTS_GROUP		Expanded ascii parts group file
SF_SUMMARY_FILE		Writes a summary file giving the main parameters of the model

In all cases the syntax is WRITE<format> <filename> <target model id>
for example: WRITE DK test.key 2

The Ideas/Master Series, Patran and Nastran output formats require some translation, and sometimes some adjustments to element labels. Click on the TRANS buttons in the table above to view the relevant sections in Appendix G which describe translation during output.

COPY

The syntax is EXECUTE <list> <target>

This copies the model(s) in <list> into the <target> model, which must not already exist.

DELETE

The syntax is EXECUTE <list>

This deletes the model(s) in <list> .

ORIENT

Applies orientation to models, or subsets of them.

The syntax is:

<orientation parameters>

Where:

Is one of TRANSLATE, ROTATE, REFLECT, SCALE, CONTACT, AXIS_ROTATE, TRIADTOTRIAD

Is one of:

MODEL
PART
<element type> (e.g. SOLID, SHELL,...)
NODE

model number

Is the model id

Is a valid <list> of the relevant object type

Depend on the <orientation type>:

TRANSLATE	[dX, dY, dZ] translation distances
ROTATE	[rX, rY, rZ] rotation angles in degrees [cX, cY, cZ] centre of rotation
REFLECT	X or Y or Z reflection axis <Distance along axis>
SCALE	[sX, sY, sZ] scales in each of X,Y,Z [cx, cY, cZ] centre of scaling
CONTACT	[cX, cY, cZ] centre of rotation <N> number of iterations
AXIS_ROTATE	[nX, nY, nZ] direction of translation [rX, rY, rZ] vector defining axis of rotation <Angle> rotation angle in degree
TRIADTOTRIAD	No parameters for this option.

Options for orient are given in the tabel below. These are typed in before <orientation type>

USE_INC_TRANS	For Include transform	Use include transform where possible
DONT_USE_INC_TRANS	For Include transform	Do not use include transform (def)
MOVE_EXNO	For controlling selection	Move extra nodes when rigid part oriented (def)
NOMOVE_EXNO	For controlling selection	Do not move extra nodes
MOVE_BM3	For controlling selection	Move n3 when beam oriented (def)
NOMOVE_BM3	For controlling selection	Do not move n3
MOVE_SLAVE	For controlling selection	Move slave when rigid master part oriented
NOMOVE_SLAVE	For controlling selection	Do not move slave (def)
PROPAGATE	For controlling selection	Propagate orient of parts and nodes (see below)
NOPROPAGATE	For controlling selection	Do not propagate (def)
ADD_GAP <distance>	For CONTACT operation	Distance shifted from the point of contact)

These commands should not all be given on one line! Give each section separately to avoid confusion, for example:

PRIMER_MANAGER >>> ORIENT TRANSLATE
ORIENT WHAT? MODEL
Give MODEL <list>: 1 2 3
Give X,Y,Z translations: 1.0 2.0 0.0

DT_DATA_TRANSFER

Transfers selected data from a "source" model to a "target" one, according to a range of parameters.

The syntax is:

SOURCE <model id>	Required. Defines the source model <model id> from which data are extracted.
TARGET <model id>	Required. Defines the target model <model_id> into which data will be transferred.

DATA_TYPE <type(s)>

Required, no default.

Defines the type(s) of data which will be transferred. Valid <type>s are:

MAT	Structural materials
EOS	Equations of state
SECTION	Element section data
HOURGLASS	Hourglass definitions
TMAT	Thermal materials

Selections are additive. Thus you could give the commands:

DATA_TYPE MAT SECTION TMAT

To transfer those three types of data.

You may also give the commands:

NOT <type>	(e.g. NOT EOS ) to remove a selection from the current list
CLEAR	to clear the current selection
STATUS	to show what is currently selected.
DONE	to return to DT_DATA_TRANSFER prompt.

MATCH_BY <method>

Optional, defaults to "match by NAME ".

Defines how objects in the source file are matched for data transfer. Valid <methods> are:

ID	If labels match
NAME	If <source> name (i.e. _TITLE ) is equal to or a subset of <target> name.
BOTH	First by ID , then by NAME .
ALL	All the data in the <source> is transferred to the <target>
STATUS	to show what is currently selected.
DONE	to return to DT_DATA_TRANSFER prompt.

ACTION <action>

Optional, defaults to action CS_COPY_TO_SEPARATE .

Defines how data transferred from source to target models is stored in the target model. Valid actions are:

CS_COPY_TO_SEPARATE	This causes transferred data to be stored in a separate include file in the target model. This include file will be given the name "dt_transfer_from_< target >.key" This is the default behaviour, and is recommended since it will make it easy to identify data that has been transferred.
CO_COPY_TO_ORIGINAL	The include file of the destination in the target model is unchanged by the transfer operation. For example if a material in include aaa.key is overwritten it remains in that file.
CM_COPY_TO_MASTER	Any data transferred into the target file is made to exist in the master file.
RO_READ_ONLY	This is rather different to the options above: It is assumed that the <source> file will be included verbatim via an INCLUDE keyword at run-time; It is also assumed that the contents of this file will not be changed. Therefore the following actions are taken: Any data transferred into the <target> file is placed in a special "Include" file which is marked "read only". When the <target> model is finally written out this file is not included, rather the original <source> file is referred to via an INCLUDE statement, using its full original pathname.
STATUS	Shows the current status of ACTION .
DONE	Returns to DT_DATA_TRANSFER prompt.

NAME_MATCH <method>

Optional, defaults to EITHER .

Defines how names in source and target models are matched when the MATCH_BY method is NAME .

T_IN_S	T arget I n S ource. A match is made if the target's title string is equal to or a subset of (<=) the source title.
S_IN_T	S ource I n T arget. A match is made if the source's title string is equal to or a subset of (<=) the target title.
EITHER	A match is made if either S_IN_T or T_IN_S is true.
EXACT	A match is made only if the target and source titles are identical.
STATUS	Shows the current status of NAME_MATCH
DONE	Returns to DT_DATA_TRANSFER prompt.

Note that name matching is also subject to the following rules:

Matching is case IN sensitive. So ABC = abc = ABC = ABC

Leading and trailing spaces are ignored. (But intermediate spaces between words are significant, thus

" ABCDEF " matches " ABCDEF "
" ABC DEF " does not match " ABCDEF "

SUPERSEDED

Optional: defaults to SAVE .

This controls how objects that are overwritten ("superseded") in the target model are handled.

SAVE	Relabels the "old" objects and transfers them to include file "dt_renumbered.key". They will not be referenced by anything and can be deleted by a CLEANUP_UNUSED operation.
DELETE	The incoming definition supersedes the object in the target model, and the original definition is lost.
STATUS	Shows the current status of SUPERSEDED
DONE	Returns to DT_DATA_TRANSFER prompt.

FEEDBACK

Optional: defaults to PART_STATUS in non-graphical mode.

"Feedback" controls how much information about what happened during a data transfer operation is given to the user. Any permutation of the options below can be selected.

SKETCH	Sketches all updated objects on the current plot. In non-graphical mode this option is ignored.
PART_STATUS	Creates two tables: the first lists all parts that were affected by this data transfer operation, the second lists those that were not.
NOT <option>	Unsets <option>. For example NOT SKETCH means that sketching will not take place.
CLEAR	Clears all options leaving none selected.
STATUS	Shows the current status of FEEDBACK
DONE	Returns to DT_DATA_TRANSFER prompt.

STATUS

Lists the status of all subcommands and settings in the DT_DATA_TRANSFER menu.

APPLY

Checks the input parameters, and carries out the actual transfer operation.

Several of these settings can also be preset in the "oa_pref" file. See the data transfer section .

BOM (Bill of Materials)

Allows reading or writing of a Bill of Materials file. There are 5 options available:

READ_BOM	Read a bill of materials file. The columns in the file will be auto-detected from the headers and the file read.
NODE/MA/EL	Node/Mass/element renumbering activated
CREATE	Create mode activated
DEFAULT	Default (no create) mode without renumbering
WRITE_BOM	Write a bill of materials file

For all options the syntax is <filename> <model id>. Where:

<filename>	Is the filename of the Bill of materials to read/write
<model id>	Is the number of the model to read the BOM into/write the BOM from.

PART_INFO

Allows writing of a part information .csv file for all parts in a model. There are 2 options available:

WRITE	Write information in full with mass properties
NOMASS_PROPS	Write information excluding mass properties

For all options the syntax is <filename> <model id>. Where:

<filename>	Is the filename of the part information file to write
<model id>	Is the number of the model to write the part information file from.

ASSIGN_MASS

The syntax is APPLY_ALL <model id>

This applies all the assign mass definitions in model number <model id> .

MD_MATERIAL_
DATABASE

Performs a material database "import" operation.

The syntax is <model id> <database id>. Where:

<model id>	Is the number of the model in which material properties will be updated.
<database id>	Is the <i_th> *MATL database in the predefined database file.

Once these two parameters have been defined a "MATCH_ALL" operation is carried out.

SPOTWELD

Performs spotweld functions. A number of options are available for this menu.

READ

Read spotweld menu options, four file types are supported:

SPOTWELD	Read PRIMER spotweld file
CATIA	Read Catia spotweld file
UG	Read a UG weld file
CONNECTION	Read PRIMER XML connection file

The following syntax is <filename> <model number> <part for welds> . Where:

FILENAME	Connection file name
MODEL NUMBER	Model number to read connections into
PART FOR WELDS	Part for the spotweld beams/solids to go into. This must be a valid spotweld part: SECTION_BEAM with ELFORM=9 (for beams) and material type MAT_SPOTWELD

After the spotweld file is read, PRIMER tries to make the connections. Any bad welds are reported to the screen and written to a PRIMER spotweld file called <inout weld file name>_bad .
For example: 5 bad welds from example.weld would be written to the file example.weld_bad .

An example input line is: /SPOTWELD READ CATIA example.weld 1 40000
This would read the Catia spotweld file example.weld into model 1, part 40000.

WRITE

Write spotweld menu options, four file types are supported:

SPOTWELD	Write PRIMER spotweld file
UG	Write a UG weld file
CONNECTION	Write PRIMER XML connection file
USER	Write a user defined connection file

The following syntax is <filename> <model number> . Where:

FILENAME	Connection file name
MODEL NUMBER	Model number to write connections out of

TYPE

Here you can set the type of spotweld that will be created when reading in a connections file. Note this does not affect the connections read in from a PRIMER XML connections file, as this will contain the spotweld type already. Available types are:

BEAM	Create spotweld beams
HEXA	Create a single spotweld solid
4_HEXA	Create a solid spotweld nugget with 4 solids
8_HEXA	Create a solid spotweld nugget with 8 solids
12_HEXA	Create a solid spotweld nugget with 12 solids
16_HEXA	Create a solid spotweld nugget with 16 solids

DIAMETER

Here you can set the diameter of the spotweld that will be created when reading in a connections file. Note this does not affect the connections read in from a PRIMER XML connections file, as this will contain the spotweld diameter already.

DUMMY and
MECHANISM

ASSEMBLY

Select an assembly by name or number, then perform one of the following operations upon it:

FIX dof code	Restrain the assembly in degrees of freedom dof code
TRANSLATE dx, dy, dz	Translate assembly by amount dx,dy,dz
RX or RY or RZ theta	Rotate assembly to angle theta degrees about x/y/z
RESET	Undo all dummy transformations and return to initial state
DONE	Finish with assembly and return to DUMMY > prompt

POINT

Select a point by name or number, then perform one of the following operations upon it:

(Note: moving the point implicitly moves its "owner" assembly.)

FIX dof code	Restrain the point in degrees of freedom dof code
TRANSLATE dx, dy, dz	Translate point assembly by amount dx,dy,dz
POSITION x, y, z	Translate point assembly to coord x, y, z
RESET	Undo all dummy transformations and return to initial state
DONE	Finish with point and return to DUMMY > prompt

CONNECTION

Select a connection by name or number

SLIDE distance	Applies to LINE connections only, and will slide the joint by distance down its AB axis.
ANGLE theta	Applies to LINE and HINGE connections only, and rotations the assemblies to achieve angle theta (in degrees) about the AB axis.

POSITION

Specify a position name or id

Retrieves and applies the stored position name or id

SAVE

Specify a position id and (optional) name

Saves the current configuration as a saved position id, with optional name .

H_POINT

Specify coordinate x, y, z

Will move the Dummy H-Point to coord x, y, z

READ_CONFIG

Specify a filename

Retrieves a free-standing dummy configuration file (the keywords and data between *DUMMY_START and *DUMMY_END ). Filename will usually have the extension .dcf

READ_DUMMY_
ANGLE

Specify a filename

Retrieves and applies the overall orientation, H-Point and joint angles stored in a Dummy Angles File (usually extension .daf).

WRITE_DUMMY_ANGLE

Specify a filename

Writes out the Dummy Angles File, for the selected Dummy, with the specified filename.

ACCURACY

Specify a value

Global factor on the accuracy of the mechanism positioning process. Value must lie in the range 0.1 to 100.0

ACCEPT	Accept the current dummy position, save its updated geometry and return to the main [PRIMER >] prompt.
RESET	Undo all transformations and restore the initial geometry of the dummy, remaining at this prompt level.
QUIT	Undo all transformations and restore the initial geometry of the dummy, then return to the main [PRIMER >] prompt.

Meanings of terms in the table above
dof code	Is a numeric Degree of Freedom code made up of any permutation of 123456, where 1 = Tx, 2 = Ty, 3 = Tz, 4 = Rx, 5 = Ry, 6 = Rz For example code 136 means restraint in Tx, Tz, Rz Code 0 may also be used, meaning "free all restraints"
dx, dy, dz	Is a translation vector, ie a relative movement from the current position, made up of three numbers. For example 10.0 20.0 30.0 means translate 10.0 in X, 20.0 in Y, 30.0 in Z. "Wildcard" syntax is permitted: any number entered as an asterisk (""), and omitted trailing digits, are treated as "free" values. For example: 10.0 means translate 10.0 in X, but permit Y and Z to adopt any value. * 20.0 means translate 20.0 in Z, but permit X and Y to adopt any value
x, y, z	Is an absolute coordinate. For example 10.0 20.0 30.0 means coordinate X=10, Y=20, Z=30. Wildcards as for translations above are permitted
theta	Is an angle in degrees for the given degree of freedom. In a dummy model angles are absolute values expressed in the coordinate system of the connection between this assembly and its parent. In most cases this will mean the system implied by the local axes of the joint stiffness definition at the joint.

BUILD

Allows the user to access PRIMER's model build functionality. Available options are:

DATABASE

To select a database file for build use:

The following syntax is DATABASE <filename.dba>

TEMPLATE

To select a template file for build use:

The syntax is TEMPLATE <filename.tpl>

SIMPLE
RIGOROUS
MASTER

You apply the build process by selecting the build mode:

SIMPLE will build without checks or renumbering
RIGOROUS will build with checks and renumbering
MASTER <a.key> will just write out a masterfile to a.key (no orient)

An example of the syntax is:

BU DATAB all_models.dba TEMPL odb_40.tpl SIMP

Alternatively you can set up multiple models using a build file:

READ	To set up multiple models using a build file: The syntax is READ <build.csv>

Before READ you may set the following:

KEEP	Keep each PRIMER model after keyout
DEL	Delete PRIMER model after keyout (default)
ECHO	Echo each line from input file
NOECHO	Do not echo (default)

To sketch target points either before or after building:

SKETCH

Sketch target points in file

The syntax is SKETCH <build.csv>

An example of the syntax is:

BU KEEP RE headpos.csv

The build mode is SIMPLE in this case

PREFERENCE

Read the preference file. Available options are the location of the preference file:

SYSTEM	look for the preference file in the $OASYS directory
HOME	look for the preference file in the home directory
PATH	use file path as supplied

After the option is chosen, you are prompted for the filename. An example of the syntax is:

HOME oa_pref

CHECK

This function will check the model specified. Syntax is:

MODEL n CHECKFILE filename APPLY

The name of an output file is specified with the CHECKFILE option. For example, to run an error check on model 2:

MODEL 2
CHECKFILE nyname.txt
APPLY

Omitting the checkfile option will give the default filename derived from the root of the dyna key file - <file>.check:

MODEL 2 APPLY

The MODEL option may be omitted if only one model in memory.

Before applying you may set the format option to FULL_LIST or SHORT_LIST (default). Just type FULL_LIST or SHORT_LIST to activate the option.

FULL_LIST will ensure that label lists are written for all item types. By default these are not written for the potentially highly populous types (NODES, ELEMENTS etc.).

AUTOFIX

This function will auto fix all errors/warning in the model. Syntax is:

MODEL n APPLY

The MODEL option may be omitted if only one model in memory.

CONNECTION

The option allows the user to remake connection in the model. Available options are:

ALL_WELDS	remake all welds
ALL_GLUE	remake all adhesive
ALL_BOLTS	remake all rigid bolts
UNMADE_WELDS	remake unmade welds
UNMADE_GLUE	remake unmade adhesive
UNMADE_BOLTS	remake unmade rigid bolts

You can also modifiy the pitch of spotwelds by selecting the following option:

MODIFY_PITCH

Change the pitch of spotwelds.

Required inputs for this operation are:

SELECT_SPOTWELDS	Select the spotwelds you wish to modify
NEW_PITCH	The new pitch value you wish to apply

After choosing SELECT_SPOTWELDS above, the user is prompted to select the type of entity through one of a number of different methods:

ALL	Select all spotwelds in the model
BY_LAYER_PART	Select the parts that have a layer that contains the selected parts
ATTACHED_TO_PANEL	Select spotwelds that are attached to the selected parts
BY_SINGLE_SEAM	Select spotwelds that are attached to ALL the selected parts
BY_MULTIPLE_SEAM	Select spotwelds that are attached to ANY combination of the selected parts
QUIT	Quit the selection process

When selecting parts for some of the above, you first define the type then the labels of items of the type. For example, to select a part range type PART 10 to 19 or to select a part set type PART_SET 5 .

Optional things to modify are:

BREAK_ANGLE	Used to determine how the lines of spotwelds are split (default 45.0 degrees)
MAX_PITCH	Maximum distance allowed between two spotwelds so that they can be considered on the same line (default 80.0mm)
SIMILAR_PITCH_ON	Group connections by similar pitch
SIMILAR_PITCH_OFF	Do not group connections by similar pitch (default)

See Modifying Spotwelds and Adhesives through Lines for more information on these inputs.

Finally:

APPLY	Apply the new pitch to the selected spotwelds.
DONE	Quit without applying the new pitch

RENUMBER

Allows you to renumber entities within the model. Available options are

MODEL	Select the model you want to operate on, for example MODEL 2
SELECT/DESELECT	Select or deselect items to renumber. After choosing select or deselect, you then must select the type of entity, and finally the labels of the items you wish to renumber. The type is one of: MODEL PART <element type> (eg SOLID, SHELL,...) NODE etc.
APPLY	Choose a start point and apply the renumbering

Syntax is MODEL n SELECT type , followed by APPLY.

For example:

model 2
sel part
10 to 19
apply

MODEL option may be omitted if only one model in memory.

SCRIPT

Reads a PRIMER JavaScript. Syntax is READ <filename> .

BELT

Refit an existing seatbelt to a dummy. PRIMER will select a seatbelt definition in the model automatically. Available options are:

SELECT	Select a different belt definition for refitting
REFIT	Refits the current belt definition to its dummy
PR_BASIC	Retrieve and update basic belt dimensions and form-finding parameters
PR_REFIT	Retrieve and update belt refit parameters
DONE	To return to the main menu prompt

SEATSQUASH

Impliment auto seatsquash function on a model. Available options are:

PRIMER

The simple PRIMER method of seatsquash .

Required inputs for this method are:

SEAT_FOAM	Select the seat foam
SEAT_TOP	Select the top of the seat
SEAT_BOTTOM	Select the bottom of the seat
DUMMY	Select the dummy
CONTACT	Select the contact between the dummy and the seat
X	X displacement per iteration
Y	Y displacement per iteration
Z	Z displacement per iteration

After choosing SEAT_FOAM , SEAT_TOP , SEAT_BOTTOM or DUMMY above, the user is prompted to select the type of entity, then the labels of items of the type. For example, to select a part range type PART 10 to 19 , o select a part set type PART_SET 5 or to select a dummy type DUMMY 17 .

Optional inputs for this method are:

MAX_ITER	Maximum number of iterations (default 100)
SOLID_REL	Stop if the solid element relative volume reaches this value (default 0.2)

Finally:

STATUS	Report what still has to be defined
APPLY	Initiate the seatsquash

DYNA

The Dyna method of seatsquash. Sets up an Ansys LS-DYNA analysis that carries out the seatsquash operation.

Required inputs for this method are:

SEAT_ALL	Select the seat parts
SEAT_DEFORM	Select the seat parts to remain deformable
DUMMY	Select the dummy
CONTACT	Select the contact between the dummy and the seat
X	X displacement per iteration
Y	Y displacement per iteration
Z	Z displacement per iteration

After choosing SEAT_ALL , SEAT_DEFORM or DUMMY above, the user is prompted to select the type of entity, then the labels of items of the type. For example, to select a part range type PART 10 to 19 , o select a part set type PART_SET 5 or to select a dummy type DUMMY 17 .

Optional inputs for this method are:

MAX_ITER	Maximum number of iterations (default 100)
DUMMY_POS_TIME	Time to position the dummy (default 0.075)
ANALYSIS_TIME	The termination time of the created analysis (default 0.1)
DAMPING	Global damping (default 50.0)
CONT_KEEP	Select contacts to keep in the analysis (by default all apart from the one selected above will be deleted)

Finally:

STATUS	Report what still has to be defined
APPLY	Initiate the seatsquash

IMPORT

Import a Dynain file

EXPORT

Export a Dynain file

DYNA_DUMMY

Impliment Dyna dummy positioning method. Available options are:

POSITION

Sets up a dyna analysis to position a dummy. When entering the POSITION setcion you will be asked if you wish to automatically determine assembly nodes. This is recommended if you have not already set these nodes up within PRIMER and saved the information to the dummy tree keywords in the keyword file associated with the dummy. See Dummy Positioning Using Ansys LS-DYNA for more information of how to do this.

Required inputs for this method are:

NECK_NODE	Node at the base of the neck (this may be set and saved to the keyword file pria to command line positioning)
HIP_NODE	Node on the left or right hip (this may be set and saved to the keyword file pria to command line positioning)
POSITION	Choose the desired position. This should be setup pria to command line positioning. See Further Positioning Commands for information on saving positions.

Optional inputs/things to modify for this method are:

RIGID_ON	Select assemblies to rigidify
RIGID_OFF	Select assemblies to turn off rigidification
DEFORM_PARTS	Select parts to remain deformable in rigidified assemblies
ANALYSIS_TIME	The end time of the analysis (default 250.0)
DAMPING	Global damping (default 50.0)
DAMPING_OFF	Turn global damping off
CABLE_DAMPING	In-line damping applied to cables (default 0.5)
FORCE_RAMP	Force ramp up time in cable (default 10.0)
CABLE_FORCE	Force in cables (default 1.0)

Finally:

APPLY

Initiate setup

IMPORT

This imports a dynain file produced in an Ansys LS-DYNA dummy positioning analysis.

Required inputs for this method are:

FILENAME	Select the dynain file to import
POSITION	Choose the desired position. This should be setup pria to command line positioning. See section 6.12.2 for information on saving positions.

Optional inputs for this method are:

COORDINATES	Import the deformed coordinates
SOLID_INIT	Import *INITIAL_STRESS_SOLID
SHELL_INIT	Import *INITIAL_STRESS_SHELL
BEAM_INIT	Import *INITIAL_STRESS_BEAM
DELETE_INIT	Delete existing *INITIAL_STRESS cards
ALL_OFF	Turn all options off

Finally:

APPLY

Import the data

DS_DYNA_DUMMY_AND_SEAT

Set up an analysis to position a dummy and squash it into a seat. Available options are:

SETUP	Specify the type of analysis
SEAT	Specify input for seat squash
DUMMY	Specify input for dummy positioning
FINISH	Specify any other input and create models

Dialogue commands that control viewing - the "Global Menu"

The following commands can be used to control graphics and viewing. When running in "text-only" mode they are ignored and will have no effect.

Drawing commands: LINE HIDDEN_LINE SHADED	These commands generate plots of the following types: Line gives a wireframe plot (no hidden surface removal) Hidden-line shows element edges, but with hidden surfaces removed Shaded produces a shaded and lit plot, implicitly with hidden surfaces removed.
Commands which control the current view: SXY, SYZ, SZX ISOMETRIC RS <x y z> RM <x y z> ZM CENTRE MG <scale> AU_AUTOSCALE AC_AUTOSCALE_CURRENT ZERO_VIEW	These commands control how the image appears on the screen. SXY is a view on the XY plane, down Z; SYZ on YZ down X; SZX on ZX down Y Isometric is a view down the vector X=Y=Z (at 45 deg to each axis) RS <x y z> rotates the image by <x> degrees about screen X, <y> about Y etc RM <x y z> rotates the image by <x> degrees about model X, etc ZM "zooms" in to the rectangle dragged out by the cursor CENTRE centres the image at the cursor location MG <scale> magnifies the image by <scale>. Values less than 1.0 reduce its size. AU autoscales on the complete model, ignoring the effects of blanking etc (ie as if all unblanked) AC autoscales on what is currently visible, taking into account blanking etc ZERO_VIEW resets the viewing routines to their default state: Autoscaled view on SXY.
Other commands: GM_GLOBAL_MENU GH_GLOBAL_HELP	Commands to do with the global menu GM lists the commands above, with a brief description GH gives more general help on the "global" menu.

Previous | Next