REPORTER 22.1

Multiple Analysis Templates

Multiple analysis templates

For the pedestrian impact protocols multiple analyses are run with impacts on different parts of the vehicle. The scores for each impact are combined to calculate an overall score for the test.

There are two multiple analysis type templates:

Pedestrian headform impacts
Pedestrian legform impacts

Generally they follow the same process, but they are different enough that we'll go through an example of how to use them both.

The section will describe how to run them interactively using the menus in REPORTER, but it is also possible to run them in batch mode.

Pedestrian headform

Select the template

Use the File Open Library Template menu and select a template from the Automotive tab (see Reading an existing template or report for more details).

Generate the template

After selecting the template REPORTER should prompt you to select the .lst file for the adult head impacts.

The .lst file is a simple text file that lists the file locations of each model keyword file. If you use PRIMERs model build process to create the models it is created automatically. If not, you can create it manually or as part of your own process for building the models. The names of the models are important as they tell the template the location/zone of the impactor. If you have used the pedestrian markup script in PRIMER, they will be named correctly.

After pressing 'OK' a file selector is mapped for you to select the .lst file. If you do not want to process the adult head impacts or you don't have a .lst file, press cancel in the file selector.

In order to correctly extract the results needed for the protocol the template needs model information such as Node IDs and the unit system etc. This needs to be supplied to the template from comments written in the .lst file and the template will help you to create this information.

The template will scan the .lst file to see if it contains the required information. If it does you will be asked if you want to use it:

If you press 'No' or the .lst file does not contain the required informtion REPORTER will inform you that it will start PRIMER so you can select the required information interactively:

After pressing 'OK' PRIMER will start, the first model in the .lst file will be read in and a window will be open for you to interactively select the required information. Select the information in the same way as described in the single analysis template section.

On returning to REPORTER you should be prompted to select the .lst file for the child head impacts. This follows the same process as for the adult .lst file. If you do not want to process the child head impacts or you don't have a .lst file, press cancel in the file selector. So long as you have selected at least one .lst file, the template should generate.

Finally you will be asked for a directory where REPORTER should write any images.

Press OK and select the directory.

REPORTER should now have all the information it needs. T/HIS will load and carry out the post-processingg according to the selected protocol, generating the required graphs. Once this is finished, REPORTER will ask a final question asking you how/if you want to save the report:

If you don't want to save the report, just press 'Cancel'. If you do, select the format(s) you want to save it in, press 'OK' and select where you want to save it in the file selector that will pop up.

The final report should look something like this, with a front summary page showing the protocol scores in tables and as an image; a pages to set default scores; a page to set test point and blue zone scores; and pages of head acceleration graphs for each impact point:

Set default scores

Some points do not need to be tested and can be defaulted either to Green (max score) or Red (min score).

You can manually set default scores on the second page by pressing the 'Set Defaults' button.

This will bring up a window where you can set the default values either to GREEN, RED or leave blank.

Once you have set the values and pressed 'OK' the scores will update automatically.

Alternatively, you can get the template to automatically default points to GREEN when the LST file is read in. This requires a special comment ' $DG: ' before each file location. e.g.

$DG:C:\Model\A_1_1\a_1_1.key
C:\Model\A_1_2\a_1_2.key
$DG:C:\Model\A_1_3\a_1_3.key

will default the score for the 1st and 3rd model to GREEN and will not attempt to read any results for them.

This can be done automatically if you use the pedestrian markup script in PRIMER. You can select an area where you want the points to default to green and PRIMER will add the 'DG:' comments to the correct lines in the LST file.

Test points

The results from the analyses are scaled using a correction factor, which is calculated based on results from a number of real world verification tests. The correction factor is calculated by dividing the actual tested total score of the verification points by the predicted total points of these verification points.

The correction factor is then applied to all points execept for defaulted and blue points .

To specify the test points press the 'Set Test Points' button on the third page:

This will bring up a window where you can enter the test point row, column and value (HIC) for up to 20 test points:

Once you have set the values and pressed 'OK' the scores will update automatically.

If no test points are specified a correction factor of 1.0 is used.

Blue zones

Some impact point locations may give unpredictable results when analysed and in these cases test data can be used instead. These are specified as blue points, either singly or grouped together in adjacent pairs to form a blue zone. Up to 8 blue zones can be specified. The test results of the blue points are applied to each point in the zone.

To specify blue points press the 'Set Blue Zone' button on the third page:

This will bring up a window where you can enter the test point row, column and value (HIC) for up to 8 blue zones:

Once you have set the values and pressed 'OK' the scores will update automatically.

Pedestrian legform

Select the template

Use the File Open Library Template menu and select a template from the Automotive tab (see Reading an existing template or report for more details).

Generate the template

After selecting the template REPORTER should prompt you to select the .lst file for the lower leg impacts.

The .lst file is a simple text file that lists the file locations of each model keyword file.If you use PRIMERs model build process to create the models it is created automatically. If not, you can create it manually or as part of your own process for building the models. The names of the models are important as they tell the template the location/zone of the impactor. If you have used the pedestrian markup script in PRIMER, they will be named correctly.

After pressing 'OK' a file selector is mapped for you to select the .lst file. If you do not want to process the lower leg impacts or you don't have a .lst file, press cancel in the file selector.

The template will scan the .lst file to see if it contains the required information. If it does you will be asked if you want to use it:

If you press 'No' or the .lst file does not contain the required informtion REPORTER will inform you that it will start PRIMER so you can select the required information interactively:

On returning to REPORTER you should be prompted to select the LST file for the upper leg impacts. This follows the same process as for the lower .lst file. If you do not want to process the upper leg impacts or you don't have a .lst file, press cancel in the file selector. So long as you have selected at least one .lst file, the template should generate.

Finally you will be asked for a directory where REPORTER should write any images.

Press OK and select the directory.

The final report should look something like this, with a front summary page showing the protocol scores in tables and as an image and pages of tabulated results and graphs for each impact point:

Previous | Next