Reports

The Manikin Reports in the PPR tree.

The selections for the window are:

• Reporting Capabilities - Updating
• Update's the Report
• Viewing a Report
• Defining Input Parameters for Reports
• Deactivate (deactivates the report)

Using the Adds a description to a manikin object, descriptions can also be created for the vision, the anthropometry, or the posture of the manikin command. Select the appropriate node in the specification tree (Manikin, Anthropometry, Vision, or Body) and the corresponding description appears in the text field.

This explains some of the choices for the dialog box

Note: The Output File field contains a default path, pointing to the temporary directory (CATTemp), but you can change the output file of the report by clicking the File... button. This field also contains a history of the last few report files used (hence the combo). If the output file name's extension is .htm or .html, then the report written to this file is in html format, Otherwise, the report is written in text format. This default path can be changed in the Tools > Options > Human Builder > General tab. Each report object must be associated to a specific log file; however, it is permitted to assign two or several different report objects to the same log file.

Any combination of analyses can be activated, and each report object must point to a valid output file. A specific analysis in the above list is selectable for activation only if the proper product license check succeeds for this analysis. For instance, the Push/Pull and RULA analyses is selectable only if the Human Activity Analysis product is installed.

This explains some of the concepts for exporting a .txt file.

Each line of this log file is the output of a specific analysis. The output itself is divided into several fields, separated by tab (ASCII character 9) characters. For all analyses, the third field always identifies the type of analysis. The first field displays the date and time at which the analysis took place. It is therefore possible to easily filter out all analyses except the ones that were made at a specific date. The second field displays a unique identifier constructed from the current date and time. This field can be used for example to reconcile several analyses that produced their outputs in several different files. By looking at this field, you can easily know whether or not two specific analyses were carried out upon the same select Update (the date and time also provide this information, of course).

The fourth field contains the type of the data output by the analysis. For example, in the case of a RULA analysis, this field says Global Score, whereas for a position constraint, it says Distance (mm).

The fifth field of a text log file is the most important one: it contains the numerical value of the analysis output. All analyses writes a numeric value in this field, or the phrase N/A meaning Not Applicable. The unit of that value depends on the type of analysis and the type of output. For instance, for a position constraint, the value represents the distance between the end effector and the target (after update), in millimeters, whereas for a carry analysis, it represents the maximum acceptable weight in Newtons.

In some analysis outputs, the sixth field contains more details about the value given in the fifth field. For other analyses, the sixth field remains empty. Finally, the seventh field displays the name of the manikin on which the analysis is performed. The eight field gives additional information if available (such as the constraint identification) and the ninth field contains the name of the report.

See Exporting Different Formats from a Report File

This describes the concepts for Defining Input Parameters. for Reports.

The Define Input Parameters dialog contains all the explicit parameters for each analysis, organized in dialog's tab pages. This enables you to specify the parameters values for that report. Any parameter value specified replaces the default parameter value in the analysis dialog. This dialog has one important particularity: it is not modal. The reason behind this choice is that for the update in simulation frame, you need to be able to select activities to get their beginning and end time. The downside of this choice is that some values are updated if they change: the default values (Default: default value) and the Automatic values (for RULA). Implicit parameters doesn't appear in the dialog since they do not inherently belong to the report. In that way, they do not need to be saved with the reports since they are saved with the manikin.

On opening of the Define Input Parameters dialog box, and when the current report selection changes, the display of the dialog and its sensitivity changes accordingly to a few simple rules:

• On opening: if an analysis is found in (at least) one selected report, its corresponding tab or frame is created.
• On selection of the All Reports, every tab and frame is fully activated (like a single report that was the union of each report).
• On selection of a single report: every analysis not present in the report has its tab disabled. If the last selected tab is still enabled, this tab is selected. If not, the first enabled tab is selected. If no tabs are enabled (which can be the case with reports that contain only biomechanics analyses, for example), the first tab is selected and the controls is disabled. For the load frame, if the current report contains analysis that doesn't need a load (only RULA and biomechanics analyses need), the frame is disabled. In case of a report that has a RULA analysis and no biomechanics analysis, only the Total magnitude spinner and the Get Load values is enabled (since in the RULA analysis only the total magnitude is used).
• If the current workbench is Human Task Definition, the frame Update during simulation is opened in this mode, but hidden.

The Dialog box: