Pedestrian Head Impact
Pedestrian Head Impact
$
$tag to activate de-penetration
$ method = contact, contact name/id, dof <x, xz or xyz>
$ method = partset, partset name/id, dof
$
$tag for projection method used to obtain target point
$ method = 0 (default): project along global Z
$ method = 1: project back along line of flight
$
$optional offset for deployable bonnet, applied along line of flight
$ tag for root directory for output
$ tag for root name for output files
$
$
$tag for master model style
$ style = 0 (default): Standard
$ style = 1: GM style - All *DEFINE_TRANSFORMATION definitions are written to a common user-defined file. Each *DEFINE_TRANSFORMATION definition is given a unique label which is equivalent to the directory name if valid. Each master model then refers to the appropriate *DEFINE_TRANSFORMATION by its label.
$ style = 2: CASE style - A single master model is written. Each *DEFINE_TRANSFORMATION and the corresponding *INCLUDE_TRANSFORM definition is specified using a *CASE definition
$
$tag for file to which all transforms will be written to (master_style 1 and 2)
$
$tag for define transform title (master_style 1)
$
$tag for building only the first loadcase
$ value = 0 (default): all loadcases built
$ value = 1: build all loadcases but write only the first master model; a common file will hold *DEFINE_TRANSFORMATION definitions for all loadcases
$
$ Create a *BOUNDARY_SPC definition using the specified node set
$
$ loadcase lines consist of
$ directory name, zone name(as dir if blank), X coord, Y coord, (optional Z
coord)
Etc.
The pedestrian head model, unlike the free motion headform, does not carry a specified base coordinate system. Thus the "orient" line is necessary to define
- the base coordinate (at the centre of the head)
- the X coordinate (to give the line of flight pointing in the correct direction)
- the Y coordinate (which defines the normal to the XZ plane for the impactor).
The three points may be defined by the name or id of a DEFINE_COORDINATE_SYSTEM or by defining three nodes.
If these are DATABASE_HISTORY_NODE_ID, they may be defined by name as alternative to label, which has the advantage that they will not be affected by renumbering.
Depenetration is activated either by referencing a surface-surface contact between the head skin and the bonnet or a single part set comprising both. In the latter case, PRIMER will generate a contact between impactor and target parts.
Finally, the loadcase lines consist of a unique directory name for output key file, the zone name (which if blank, will default to same as directory name), and an X coordinate and Y coordinate. If the Z coordinate is not defined, as is usually the case, it will be calculated by projection determining the target geometry from the depenetrate information. For this reason, if depenetrate is not active, the Z coordinate must be defined explicitly.
In the root directory a submission file (.lst) will be written which may be used by the submission shell.
By default reporter variables ZONE, XCOORD, YCOORD and ZCOORD are passed into the file. These may be accessed by the individual reporter templates.
Note : Optional fields such as zone name may be specified by including a space between commas (,<space>,). Omitting the space might result in erroneous processing.
Master model options : Three options are available for the generation of master models:
- By default (or if is set to 0), PRIMER will generate a master keyword file in each output directory, which will reference the main model with *INCLUDE and the impactor with *INCLUDE_TRANSFORM.
- If is set to 1, all *DEFINE_TRANSFORMATION definitions are written to a common user-defined file ( ), each definition carrying a unique label equivalent to the directory name, and a title composed of a loadcase name, a user-defined string ( ) and depenetration information. This mode will also add a pair of cancelling transforms to each loadcase that correspond to negative and positive aim point coordinates.
- If is set to 2, all output is written to a single user-define master model (transform_file). The main model and the impactor are both referenced once using *INCLUDE and *INCLUDE_TRANSFORM respectively. Data pertaining to individual loadcases is written using *CASE specifiers, each carrying a unique label/id.