Manual Airbus Custom Tools: (Model/Result Comparison Tools and Reporting)

Manual
Airbus Custom Tools

(Model/Result Comparison Tools and Reporting)
03. December 2019

Version 2.00
Altair Engineering
Calwer Straße 7
Pavan Pendyala
71034 Böblingen
Contents
1. Introduction .............................................................................................. 4
2. Installation by adding a menu button ........................................................ 4
3. Functionality of Tools ................................................................................ 5
3.1 Compare Internal Results ........................................................................................ 5
3.1.1 Description: ...................................................................................................... 5
3.1.2 User Inputs....................................................................................................... 5
3.1.3 Functionality ..................................................................................................... 6
3.2 Compare Results Between Different Models ........................................................... 8
3.2.1 Description: ...................................................................................................... 8
3.2.2 User Inputs....................................................................................................... 8
3.2.3 Functionality ....................................................................................................10
3.3 Compare Models ....................................................................................................11
3.3.1 Description: .....................................................................................................11
3.3.2 User Inputs......................................................................................................12
3.3.3 Functionality ....................................................................................................12
3.4 Compare Extracted Data ........................................................................................14
3.4.1 Description: .....................................................................................................14
3.4.2 User Inputs......................................................................................................14
3.4.3 Functionality ....................................................................................................14
3.5 Comparison by Location .........................................................................................14
3.6 Synchronize Sets from HM to HV ...........................................................................17
3.6.1 Description ......................................................................................................17
3.6.2 User Inputs......................................................................................................17
3.6.3 Functionality ....................................................................................................17
3.7 Core Reporting .......................................................................................................17
3.8 M2036 Forms .........................................................................................................18
3.8.1 Description: .....................................................................................................18
3.8.2 User Inputs......................................................................................................18
3.8.3 Functionality ....................................................................................................22
3.8.4 Outputs ...........................................................................................................37
3.8.5 Configuration ...................................................................................................37
3.9 Compare Modes for Scaling Checks ......................................................................38
3.9.1 Description ......................................................................................................38
3.9.2 Pre-requisites ..................................................................................................38
3.9.3 User Inputs......................................................................................................38
Altair Engineering GmbH 1

3.9.4 Functionality ....................................................................................................38
3.9.5 Outputs ...........................................................................................................39
3.9.6 Configuration ...................................................................................................39
3.10 Interfaces Identification ..........................................................................................39
3.10.1 Description ......................................................................................................39
3.10.2 Pre-requisites ..................................................................................................39
3.10.3 User Inputs......................................................................................................40
3.10.4 Functionality ....................................................................................................40
3.10.5 Outputs ...........................................................................................................40
4. General Requirements .............................................................................41
4.1 Operation System ..................................................................................................41
4.2 HyperWorks Version ..............................................................................................41
4.3 Additional Software and Versions ...........................................................................41
4.4 Batch Mode execution ............................................................................................41
4.5 Delivery of custom code .........................................................................................41
4.6 Excel as Interface for Tables ..................................................................................41
4.7 Reporting Format ...................................................................................................41
5. Tutorial ....................................................................................................41
5.1 Comparison Based on IDs- Altair Model .................................................................41
5.1.1 Compare Internal Results ................................................................................41
5.1.2 Compare Models .............................................................................................42
5.1.3 Compare Results Between Different Models ...................................................43
5.1.4 Compare Extracted Data .................................................................................44
5.2 Comparison Based on IDs- Airbus Model ...............................................................44
5.2.1 Compare Internal Results ................................................................................44
5.2.2 Compare Models .............................................................................................46
5.2.3 Compare Extracted Data .................................................................................47
5.3 Comparison Based on Location- Airbus Model .......................................................48
5.3.1 Compare Models .............................................................................................48
5.4 Base Reporting Solution (WORD Reporting)- Create Word report right from scratch
using Company Word Master document ...........................................................................51
5.5 Base Reporting Solution (WORD Reporting) - How to insert Cross References or
Table of References in Word Reports ...............................................................................62
5.6 Base Reporting solution (WORD Reporting)- Create Standardized Report from a pre-
defined Report Template (Interactive Mode) .....................................................................65
5.7 Base Reporting Solution (PPT)- Create MS office PPT report right from scratch using
the Company PPT Master document ................................................................................67

5.8 Base Reporting Solution (PPT)- Create Standardized Report from a pre-defined
Report Template (Interactive Mode)..................................................................................78
5.9 Airbus Custom Word Reporting Modules - M2036 Forms .......................................80
5.10 Airbus Custom Word Reporting Modules - Compare Modes for Scaling Checks ....82
5.11 Airbus Custom Word Reporting Modules - Interfaces Identification ........................82
6. TroubleShooting .......................................................................................83
6.1 Model/Result Comparison Tools ............................................................................83
6.1.1 Character Limitation for File Paths in Windows ...............................................83
6.1.2 Ulimit value setting in Linux .............................................................................83
6.1.3 Rods as Beams in HyperView .........................................................................84
6.2 Automated Reporting .............................................................................................84
6.2.1 Character Limitation for File Paths in Windows ...............................................84
6.2.2 Pending Action in MS Office Before Export .....................................................84
6.2.3 Changes to Report Level.................................................................................85
6.2.4 Word Report Creation Failed ...........................................................................85
6.2.5 M2036 Forms ..................................................................................................87
6.2.6 Core Reporting, Airbus Custom Reporting and Automated Reporting Director 87
6.2.7 Do not open output files while the module’s execution is running or while the
report is being created ...................................................................................................87
7. Project Stakeholders ................................................................................87

1. Introduction
The main goal of the project is to facilitate the users to:
• Compare model attributes such as PSHELL Thickness, Elemental Area etc. between two models
• Compare Internal Results such as vonMises Stresses, Displacements etc. between two different sub
cases of the same model
• Compare Results such as vonMises Stresses, Displacements etc. between two different sub cases of
different models
• Create (Semi) Automatic Reports for M2036 Forms, Interfaces Identification, Compare Modes for
Scaling Checks etc.
2. Installation by adding a menu button

Before you proceed with the installation of this custom tool, make sure that you have HW 2019.1.1 installed on
your machine.
Copy the Airbus-CustomTools solution provided to any directory on the local drive. Please make sure that there
are no spaces in the directory path. Please follow the steps described below:
• Open HyperMesh Desktop (with hyperworks_hmdesktop on Linux) and click on File->Run->Tcl/Tk Script
and select the ‘install.tcl’ file from <Airbus-CustomTools Installation directory> as shown in the picture
below
• After this preparation a new menu entry will be added in HyperMesh Desktop:
Figure: Installing the tool

Note: If the menu entry doesn’t appear on relaunching HyperMesh Desktop as shown above, please
launch the GUI of the tools manually by clicking on File->Run->Tcl/Tk Script.
Tool Script to Load
Compare Internal Results <Tool-Installation-Directory>/src_ModelResultComparison/

Main_CompareInternalResults_GUI.tcl
Compare Results Between <Tool-Installation-Directory>/src_ModelResultComparison

Different Models /Main_CompareResultsFromDifferentModels_GUI.tcl
Compare Models <Tool-Installation-Directory>/src_ModelResultComparison

/Main_CompareModels_GUI.tcl

User Documentation and <Tool-Installation-Directory>/src_ModelResultComparison
Tutorials /Main_Documentation.tcl
Synchronize Sets from HM <Tool-Installation-Directory>/src_ModelResultComparison

to HV /Main_SyncSets_HM_HV.tcl
Automated Reporting <Tool-Installation-Directory>/src_Reporting_Core/

Main_Launch_HW_CustomReporting.tcl
3. Functionality of Tools
As a part of this project, the following eight custom tools are developed for Airbus.
3.1 Compare Internal Results
3.1.1 Description:
This tool allows the user to compare the internal results between two different sub cases of the same model.
A possibility to create derived load cases through linear super position of the base load cases is also provided.
Various real-life comparison use case scenarios such as the following are also considered while designing the tool
• One Load Case against another Load Case
• Envelope (Min/Max) of a set of Load Cases against one Load Case
• Envelope (Min/Max) of a set of Load Cases against Envelope (Min/Max) of another set of Load Cases
3.1.2 User Inputs

User inputs for this tool are described below:
a. Reference Model- User selects the Reference FE model. Allowed file types for FE model are all OptiStruct File
formats and all Nastran File Formats. User may load a .xdb, .h3d or a .op2 file also as reference model.
However, the user has to make sure that the model data is present in this result file. For ‘Comparison by
Location’, only the OptiStruct and Nastran File Formats are allowed and result files are not allowed.
b. Result Files- User selects the result files. Allowed file types for result files are .xdb, .h3d, .op2. Depending on
the extension of file selected, the reader type is automatically detected.
User has to make sure that no two selected result files contain the same sub case ID.
c. Load Combination Files- User selects one or more CSV files or .SDB files that contains the load combinations
to be used to create the derived load cases automatically. The CSV file has to follow a particular format and
an example of this CSV file can be seen in <Custom Tool Installation directory>/src_ModelResultComparison
/4_testdata/Inputs_CompareInternalResults/AltairModel/Model 1-LSP 1.csv. Similarly, the format of the .SDB
file is fixed and an example of this CSV file can be seen in <Airbus Model Result Comparison
Tools>/4_testdata/Inputs_CompareInternalResults/AltairModel/Model 1-LSP 1_WF.SDB.
User has to make sure that the base sub case ids shown in the CSV file or the .SDB file are present in one of
the result files selected above.
User has to make sure that only a double number (such as 1, 4, 6 , 6.7, 7.5 etc.) is specified as scale factor for
all the derived load cases.
User has to make sure that no two derived load case names mentioned in the CSV or SDB files have the same
name.
d. SET 1 Load Cases: User selects the sub cases that would be used to create an envelope for SET 1. Make
sure that the sub case names don’t contain special characters such as {, }, !, §, %, $, / etc.
User has to make sure that at least one load case is selected here.
Note: Even if exactly one load case is selected, the maximum and minimum envelope for SET 1 is created.
e. SET 2 Load Cases: User selects the sub cases that would be used to create an envelope for SET 2. Make
sure that the sub case names don’t contain special characters such as {, }, !, §, %, $, / etc.
f. Result Type- User selects the result types to be compared.

a. Add Row- Using this, the user can add a new result parameter row in the table and select the result type,
component, layer etc. from the drop down lists available
b. Duplicate- Using this, the user can duplicate the selected row in the table and create a new result parameter
to be compared by quickly changing one or more of the result parameters
c. Remove- Using this, the user can delete a result parameter row from the table
d. Save/Load Config- The user may optionally save the result parameter settings as a configuration file so
that it could be reloaded at a later point in time using the Load Config button.
g. Use Elements: User selects if only selected entities are to be considered for comparison (Default is All).
h. Global Scale Factor (SET 1): User specifies the global scale factor that is to be applied to each sub case (both
base and derived) in SET 1
i. Global Scale Factor (SET 2): User specifies the global scale factor that is to be applied to each sub case case
(both base and derived) in SET 2
3.1.3 Functionality
On click of “Get Loads” button, the following actions are performed:
a. Inputs provided are validated.

b. The selected model and result files are loaded on to the current page and window
c. Any load case combination .SDB file would be converted in to the .CSV format. The .csv file is
saved in the output directory. If the load case name contains ‘/’, then it is replaced with ‘_’
d. The derived load case names (LSPs) and the associated scale factors would be read from these
.CSV files
On click of “Extract” button, the following actions are performed:
a. A log file is written in the output directory showing the progress of the tool
b. For each result type selected,
o For each base sub case selected in SET 1 and SET 2, the contour is plot and a H3D file is
exported in the output directory. The global scale factor specified is also applied here.
o For each derived load case selected in SET 1 and SET 2, the derived load case is created
with that name and the contour is plot. A H3D file is also exported to the output directory. The
global scale factor specified is also applied here.
o For all the base and derived sub cases selected in SET 1, a Maximum and Minimum envelope
is created and the H3D files are exported to the output directory.
o For all the base and derived sub cases selected in SET 2, a Maximum and Minimum envelope
is created and the H3D files are exported to the output directory
In the ‘Comparison View’ browser that opens up, User can compare the results. The various
inputs/functionality in the comparison browser are explained below.

Basic Settings:
a. Result Type: Select the desired result type to be compared
b. SET 1 Sub Case: Select the desired sub case from set 1. Available options are Max Envelope of Set1, Min Envelope of
Set1, selected base sub cases from Set1 and selected derived sub cases from Set 1
c. SET 2 Sub Case: Select the desired sub case from set 2. Available options are Max Envelope of Set 2, Min Envelope of
Set 2, selected base sub cases from Set 2 and selected derived sub cases from Set 2
d. Comparison Formula: Select the desired comparison formula to be used. Along with the company standard formulae,
the user defined formulae are read from the configuration file defined in <Airbus Custom Tools Installation
Directory/src_ModelResultComparison/1_config/config.tcl>
Advanced Settings:
a. Show Comparison Results with N/A: Specify if the entities with comparison value as ‘N/A’ are also to be written to the
CSV comparison file or not.
b. Show Reference and Variant Entities: Specify if the contour is to be displayed for all the entities in Reference and
Variant model or only for those entities with results above/below a threshold value
c. Threshold: Specify the threshold value to be considered for showing the reference and variant entities. This option is
active only if the ‘Show Reference and Variant Entities’ is set to ‘Above Threshold’ or ‘Below Threshold’
d. Show Results in TableView: Specify if the CSV created for each comparison is to be loaded in TableView or not.
e. Create Notes at Top ‘N’ Contour Values: Specify the number of automatic notes to be created for the top N contour
values
f. Create Notes at Bottom ‘N’ Contour Values: Specify the number of automatic notes to be created for the bottom N
contour values
g. Legend Settings: Specify the legend settings file to be used for sorting the contour on all the 3 windows of comparison.
By default, the legend used is <Airbus Custom Tools Installation
Directory/src_ModelResultComparison/1_config/legend.tcl>
h. Create Additional Sets: Specify how many additional sets are to be created and specify also the min/max range for
each additional set. By default, up to 6 additional sets are allowed. But this can be easily changed in <Airbus Custom
Tools Installation Directory/src_ModelResultComparison/1_config/config.tcl> by editing the variable as shown below

i. Compare Data: Shows the comparison results by loading the selected SET1 sub case, selected SET2 subcase and
comparison as per the formula chosen. Also, a CSV summary file is created in the output directory. If the contour is
nodal binding (Ex. Displacement results), then the summary Is created for nodes. Otherwise for elements. In addition,
the results are loaded on to a new page in Table View client if the ‘Show Results in TableView’ is set to ‘Yes’
j. Help: Launches the user manual and tutorial of the solution
Related tutorials are Altair Model and Airbus Model

3.2 Compare Results Between Different Models
3.2.1 Description:
This tool allows the user to compare the results between subases originating from different models and result files.
A possibility to create derived load cases through linear super position of the base load cases is also provided.
Various real life use case comparison scenarios such as the following are also considered while designing the tool
• One Load Case against another Load Case
• Envelope (Min/Max) of a set of Load Cases against one Load Case
• Envelope (Min/Max) of a set of Load Cases against Envelope (Min/Max) of another set of Load Cases
3.2.2 User Inputs

a. Reference Model- User selects the Reference FE model. Allowed file types for FE model are all OptiStruct File
formats and all Nastran File Formats. User may load a .xdb, .h3d or a .op2 file also as reference model.
However, the user has to make sure that the model data is present in this result file. For ‘Comparison by
Location’, only the OptiStruct and Nastran File Formats are allowed. Result files are not allowed.
Reference Result Files- User selects the result files for Reference Model. Allowed file types for result files are
.xdb, .h3d, .op2. Depending on the extension of file selected, the reader type is automatically detected.
User has to make sure that no two selected result files contain the same sub case name.
b. Load Combination Files- User selects one or more CSV files or .SDB files that contains the load combinations
to be used to create the derived load cases automatically. The CSV file has to follow a particular format and
an example of this CSV file can be seen in <Custom Tool Installation directory>/src_ModelResultComparison
/4_testdata/Inputs_CompareInternalResults/AltairModel/Model 1-LSP 1.csv. Similarly, the format of the .SDB
file is fixed and an example of this CSV file can be seen in <Airbus Model Result Comparison
Tools>/4_testdata/Inputs_CompareInternalResults/AltairModel/Model 1-LSP 1_WF.SDB.

name.
c. Variant Model- User selects the Variant FE model. Allowed file types for FE model are all OptiStruct File formats
and all Nastran File Formats.
d. Variant Result Files- User selects the result files for Variant Model. Allowed file types for result files are .xdb,
.h3d, .op2. Depending on the extension of file selected, the reader type is automatically detected.
User has to make sure that no two selected result files contain the same sub case name.
e. Variant Load Combination Files- User selects one or more CSV files or .SDB files that contains the load
combinations to be used to create the derived load cases automatically for the Variant Model. The CSV file has
to follow a particular format and an example of this CSV file can be seen in <Custom Tool Installation
directory>/src_ModelResultComparison /4_testdata/Inputs_CompareInternalResults/AltairModel/Model 1-LSP
1.csv. Similarly, the format of the .SDB file is fixed and an example of this CSV file can be seen in <Airbus
Model Result Comparison Tools>/4_testdata/Inputs_CompareInternalResults/AltairModel/Model 1-LSP
1_WF.SDB.
name.
f. SET 1 Load Cases: User selects the sub cases that would be used to create an envelope for SET 1. Make
sure that the sub case names don’t contain special characters such as “{”, “}” etc.
g. SET 2 Load Cases: User selects the sub cases that would be used to create an envelope for SET 2. Make
sure that the sub case names don’t contain special characters such as “{”, “}” etc.
h. Result Type- User selects the result types to be compared.
a. Add Row- Using this, the user can add a new result parameter row in the table and select the result type,
component, layer etc. from the drop down list available
b. Duplicate- Using this, the user can duplicate the selected row in the table and create a new result
parameter to be compared by quickly changing one or more of the result parameters
c. Remove- Using this, the user can delete a result parameter row from the table
d. Save/Load Config- The user may optionally save the result parameter settings as a configuration file so
that it could be reloaded at a later point in time using the Load Config button.
i. Comparison By: User selects whether the comparison is to be done by ‘ID’ or ‘Location- Element Dimension
Only‘ or ‘Location- Element Dimension and Configuration’. More information on how this algorithm works is
explained here
j. Proximity Search Radius: User specifies here the factor with which the Average element size in variant model
needs to be multiplied with to achieve the Proximity Search Radius. This is shown only when ‘Comparison By’
is set to ‘Location- Element Dimension Only‘ or ‘Element Dimension or Configuration’. More information on how
this algorithm works is explained here
k. Use Elements: User selects if only selected entities are to be considered for comparison (Default is All). This
is active only if the ‘Comparison by’ is set to ‘ID’
l. Global Scale Factor (SET 1 LCs): User specifies the global scale factor to be used for each of the selected sub
cases in SET 1
m. Global Scale Factor (SET 2 LCs): User specifies the global scale factor to be used for each of the selected sub
cases in SET 2

3.2.3 Functionality
On click of “Compare” button, the following actions are performed:
a. The Source/Reference model and Variant/Target model are loaded in HyperMesh batchmode to find the
element mapping based on location. More information on how this algorithm works is explained here
On click of “Get Loads” button, the following actions are performed:
a. Inputs provided are validated for correctness

b. The selected reference model and result files are loaded on to the current page and window
c. Any load case combination .SDB file would be converted in to the .CSV format. The .csv file is saved in the
output directory. If the load case name contains ‘/’, then it is replaced with ‘_’
d. The derived load cases (LSPs) and the associated scale factors would be read from these .CSV files
On click of “Extract” button,
The following actions are performed for Reference model and then same actions are performed for the
Variant model:
b. For each result type selected,
I. For each base sub case selected in SET 1 and SET 2, the contour is plot and a H3D file is
exported in the output directory. The global scale factor specified is also applied here.
II. For each derived load case selected in SET 1 and SET 2, the derived load case is created with
that name and the contour is plot. A H3D file is also exported to the output directory. The global
scale factor specified is also applied here.
III. For all the base and derived sub cases selected in SET 1, a Maximum and Minimum envelope is
created and the H3D files are exported to the output directory.
IV. For all the base and derived sub cases selected in SET 2, a Maximum and Minimum envelope is
created and the H3D files are exported to the output directory
Basic Settings:
b. SET 1 Sub Case: Select the desired sub case from set 1. Available options are Max Envelope of Set1, Min Envelope of
Set1, selected base sub cases from Set1 and selected derived sub cases from Set 1
c. SET 2 Sub Case: Select the desired sub case from set 2. Available options are Max Envelope of Set 2, Min Envelope of
Set 2, selected base sub cases from Set 2 and selected derived sub cases from Set 2

d. Comparison Formula: Select the desired comparison formula to be used. Along with the company standard formulae,
Advanced Settings:
a. Show Comparison Results with N/A: Specify if the entities with comparison value as ‘N/A’ are also to be written to the
b. Show Reference and Variant Entities: Specify if the contour is to be displayed for all the entities in Reference and
c. Threshold: Specify the threshold value to be considered for showing the reference and variant entities. This option is
values
contour values
i. Compare Data: Shows the comparison results by loading the selected SET1 sub case, selected SET2 subcase and
nodal binding (Ex. Displacement results), then the summary Is created for nodes. Otherwise for elements. In addition,
the results are loaded on to a new page in Table View client if the ‘Show Results in TableView’ is set to ‘Yes’
Related tutorials are Altair Model

3.3 Compare Models
3.3.1 Description:
This tool allows the user to compare the desired attributes such as Property thickness, material’s Youngs Modulus,
elemental area etc. for two different models.

3.3.2 User Inputs
a. User selects the Reference and Variant model. Allowed file types are all OptiStruct File formats and all Nastran
File Formats. Depending on the extension of file selected, the user profile is automatically detected and set in
HM session.
b. User selects the Output Directory where all the HWASCII files are to be saved.
c. User selects one or more desired attributes for the entity types Elements, Nodes, Properties, Materials and
EngineeringData. Only these five types are supported. The solution shows all the HM supported data
names/attributes for each entity type.
d. Comparison By: User selects whether the comparison is to be done by ‘ID’ or ‘Location- Element Dimension
Only‘ or ‘Location- Element Dimension and Configuration’. More information on how this algorithm works is
explained here
e. Proximity Search Radius: User specifies here the factor with which the Average element size in variant model
needs to be multiplied with to achieve the Proximity Search Radius. This is shown only when ‘Comparison By’
is set to ‘Location- Element Dimension Only‘ or ‘Element Dimension or Configuration’. More information on how
this algorithm works is explained here
f. Use Elements: User selects if only selected entities are to be considered for comparison (Default is All). This
is active only if the ‘Comparison by’ is set to ‘ID’
3.3.3 Functionality
On click of “Get Data” button, the following actions are performed:
a. The reference model selected is loaded on to the current page/window.
On click of “Compare” button, the following actions are performed:
a. The Source/Reference model and Variant/Target model are loaded in HyperMesh batchmode to find the
element mapping based on location. More information on how this algorithm works is explained here
On click of “Extract” button, the following actions are performed for each attribute selected,
b. For each element, in Reference model, the value of the attribute is queried and the data is written to
a HWASCII file in the output directory.
c. For each element, in Variant model, the value of the attribute is queried and the data is written to a
HWASCII file in the output directory.

Basic Settings:
b. Comparison Formula: Select the desired comparison formula to be used. Along with the company standard formulae,
Advanced Settings:
a. Show Reference and Variant Entities: Specify if the contour is to be displayed for all the entities in Reference and
b. Threshold: Specify the threshold value to be considered for showing the reference and variant entities. This option is
c. Show Comparison Results with N/A: Specify if the entities with comparison value as ‘N/A’ are also to be written to the
values
contour values

i. Compare Data: Shows the comparison results by loading the Reference and Variant models and calculates the
nodal binding (Ex. Nodes-Global X), then the summary Is created for nodes. Otherwise for elements. In addition, the
results are loaded on to a new page in Table View client if the ‘Show Results in TableView’ is set to ‘Yes’
Related tutorials are Altair Model and Airbus Model
3.4 Compare Extracted Data
3.4.1 Description:
This tool allows the user to compare the results extracted at any point later once the result files (H3D in case of
Compare Results tool and HWASCIIs in case of Compare Models tool) are created.
3.4.2 User Inputs

a. Results Directory: The directory where the extracted result files are present. It is mandatory to have one of the
three TCL Files (CompareInternalResults.tcl or CompareModels.tcl or CompareDifferentResults.tcl) in this
directory.
3.4.3 Functionality
On click of “Compare Data” button, the following actions are performed:
a. The comparison browser opens up facilitating the user to perform comparisons for the results.
b. The functionality of the comparison browser is explained already in the above 3 tools.
3.5 Comparison by Location

In this section, the algorithm used behind ‘Comparison by Location’ feature in ‘Compare Models’ and ‘Compare
Results between Different Models’ tools is described. The Core HyperMesh entity “Fields” is used to find the
element mapping between Reference and Variant models. The steps followed are:
a. Reference Model is loaded in HyperMesh
b. If the ‘Comparison by Location’ is set to ‘Location-Dimension Only’, then for all the 1D elements, the Centre of Gravity
is extracted and a CSV file is created as shown below. This step is repeated for 2D and 3D elements also.

c. If the ‘Comparison by Location’ is set to ‘Location-Dimension and Configuration’, then for each configuration in the 1D
elements (such as BAR, ROD, BEAMS etc.), the Centre of Gravity is extracted and a CSV file is created as shown above.
This step is repeated for all the configurations in 2D (tria3, quad4 etc.) and 3D elements (tetra, penta etc.) also.
Note: If a particular element dimension or configuration is not available in the Reference model, then it is skipped.
d. Now, the variant model is loaded by deleting the Reference model and the average element size for shell elements is
found as per the formula below:
• quad elements: average size of one element = sqrt(1/2 * (longest diagonal) * (sum of the parallel altitudes))
• tria elements: average size of one element = sqrt(area)
• The total average size is then calculated by summing each average size and dividing by the number of elements
considered.
e. At each of the Centre of Gravity locations shown above, a virtual node is created in the variant model and a circle is
then drawn with the Radius = Proximity Search Radius Factor (Specified in the GUI) X Average Element Size from
Variant model. The variant element that falls within this radius is taken as the “Mapping” variant element for the given
reference element. There could be a single element or multiple elements that falls within this radius.
Note: The default Proximity Search Radius Factor specified in the GUI (0.5) is usually good/precise enough to find
the mapping elements from the variant model.
f. Following sets are created to enable the user review the mapping found by the solution:
• A set 'No_MappingFound_elements' is created comprising of those elements from the reference model to which
a mapping element from the variant model is not found.
• A set 'MappingFound_elements' is created comprising of those elements from the reference model to which a
mapping element from the variant model is found.
• A set 'Single_MappingFound_elements' is created comprising of those elements from the reference model to
which a UNIQUE or SINGLE element from the variant model is found.
• A set 'Multiple_MappingFound_elements' is created comprising of those elements from the reference model to
which more than one mapping element from the variant model is found.
g. Similarly, for nodes also, these four sets are created.

h. Along with the sets, CSV files are also created showing the single and multiple mapping elements. And similarly, single
and multiple mapping nodes. If there are no multiple mapping nodes/elements, then the corresponding CSVs are not
created.

i. In case multiple mapping elements or multiple mapping nodes are found, the user is expected to review the CSV files
and make sure that there is one to one mapping between Reference and Variant models by deleting the unwanted
elements/nodes as shown below.
j. If the user doesn’t do this task, then for each reference element (which has multiple mapping), the corresponding last
variant element is taken for mapping. For example, in above image, 86001 variant element would be taken as mapping
for the first reference element (16900000)
k. Refer to the video <Airbus- Custom Tools Install Directory>/1_CompareTools- Comparison By Location- BackEnd
Workflow using Fields.mp4 for the complete ‘Mapping’ workflow.
Limitation:
a. If there are coincident elements (Elements having the same centroid location) of same configuration in both Reference
and Variant models, then only one of such reference elements (typically with lower element id) is considered for
mapping. For example, in the reference model “<Airbus Custom Tools Installation
directory>\src_ModelResultComparison\4_testdata\Inputs_CompareModels_Location\AirbusModel\s19_XLR_inclxbdf
incl_REFERENCE.dat”, the element ids 16005729 and 16005663 are both of CQUAD4 configuration and they are exactly

at the same location. In this case, only element id 16005663 is selected for mapping with variant elements. The
element id 16005729 is ignored.
b. So, in such cases, it is advised to use “Comparison By ID”
c. In the next work package, there is a plan to support “Comparison by ID + Location” which will find mapping based on
location and then refine the search so that identical element ids are picked automatically.
Related tutorials are Airbus Model
3.6 Synchronize Sets from HM to HV
3.6.1 Description
This tool runs in HyperMesh and allows the user to select some sets present in HM session.
The tool then automatically creates these sets in HyperView also. This tool is just a short cut
to ‘Sync Sets HM to HV’ in Aerospace Tool bar.
3.6.2 User Inputs

Following are the user inputs of this module:
• Sets- Desired sets from HM page
• HV Pages/Windows- Pages/Windows (With active HV client) where these sets need to be
created.
3.6.3 Functionality
The user selected sets in HM page are created in HV pages/windows selected also with the
same name of sets.
3.7 Core Reporting

Since HW 2019.1.1, Automated Reporting Director (ARD) which was formerly a PSO is
integrated into core HyperWorks.
More information about this tool can be found in the online HW help.

It is highly recommended to watch the demo video of the tool which can be found here:
<Custom-Tools-Installation
Directory>/2_Report_DemoVideo_Aerospace_Word_29092019.mp4
The Airbus custom modules such as M2036 Forms, Interfaces Identification, Compare Modes
for Scaling Checks are developed based on this framework.
Related Tutorials are Word- New Report, Word- Standardized Report, PPT- New Report , PPT-
Standardized Report, Word- Cross References
3.8 M2036 Forms

Note this module appears and runs only in HW 2019.1.1 and above
3.8.1 Description:
This module creates (semi) automatically M2036 forms. The base template
(configuration) of these forms can be found in <Tool Installation
Directory>/src_Reporting_Core/airbus/config/M2036-Forms.xlsx folder.
3.8.2 User Inputs

User inputs for this module are categorized into 7 sections:
• General
• Files Record
• Model Check List
• Analysis Check List – Static Analyses
• Elasto Thermic Analysis
• Normal Modes and Ground Check Analysis
• FEM Identity Card
3.8.2.1 General
This category contains some generic inputs from the user which are used in multiple forms. The property editor
area for the References category is as shown below. Note that the special characters such as ‘ä’, ‘ü’, ‘ö’ etc. are
not supported in the General section. Having such characters lead to erroneous/undesired characters in the final
report.
3.8.2.2 Files Record

This category contains the information about files used to create the report. The property editor area for the Files
Record category is as shown below

a. Folder with Files: User selects a folder containing the files to be documented.
3.8.2.3 Model Check List

This category contains the model information extracted from the.f06 file The property editor area for this category
is as shown below
a. Output (F06 File): User selects the .f06 file to be used to extract the model information.
b. Nastran Deck: User selects the Nastran input deck on which all the model checks are to be performed
c. Thresholds for various checks: User specifies the threshold limit for various checks such as Element
Warping, Aspect Ratio etc.
d. Perform 1D Offsets Check: User specifies here if an image showing the 1D elemental offsets need to be
captured as well. This is usually the most time taking check. It is advisable to deselect this check when more
than 200,000 elements are present in the model.
3.8.2.4 Analysis Check List

This category contains the analysis information extracted from the f06 file. The property editor area for this category
is as shown below
a. Number of F06s: User can select the desired number of F06s to be used. (Depending on if all the required
analyses are present in the same run/f06 or multiple runs/f06 files). For each f06, user has to provide the
following inputs:
1. F06 File – User selects the f06 file path
2. Sub-cases: User selects the subcases for which the information is to be extracted. On selection of
the f06 file path above, the solution reads the different subcases present in the file and shows
them here in the drop down. The order of the key words searched in the f06 file to find subcases
information is “SUBCASE=”, “LABEL =”, “SUBTITLE=” and “SUBTITLE = ”. For instance, if the key
word “SUBCASE=” is not found in the f06 file, then the key word “LABEL =” is searched. If this key
word is found, then the rest of the key word search is aborted, and the sub cases information is
extracted.

3. Result File: User selects the result file (op2, h3d or xdb) corresponding to the f06 file selected
above.
b. Legend File (Optional): User selects the legend TCL file to be used to update the contour settings. The
decimal precision of contour values, number formatting, position of the legend etc. can all be defined in the
legend TCL file. Follow the tutorial shown below to set up your customized legend
a. Show Deformed Shape: User specifies if the deformed shape is to be shown in the images or not. If this
option is activated, then the following settings are also applied in the Deformed panel before capturing
images.
3.8.2.5 Analysis Check List- Elasto Thermic Analysis

This category contains the analysis information extracted from the f06 file corresponding to Elasto-
Thermic Analysis. The property editor area for this category is as shown below
a. F06 File – User selects the f06 file path corresponding to the Elasto-Thermic Analysis

b. Elasto Thermic Subcase (F06 File): User selects the subcase corresponding to the elasto thermic analysis. On
selection of the f06 file path above, the solution reads the different subcases present in the file and shows
them here in the drop down. The order of the key words searched in the f06 file to find subcases information
is “SUBCASE=”, “LABEL =”, “SUBTITLE=” and “SUBTITLE =”. For instance, if the key word “SUBCASE=” is not
found in the f06 file, then the key word “LABEL =” is searched. If this key word is found, then the rest of the key
word search is aborted, and the sub cases information is extracted.
c. Result File: User selects the result file (op2, h3d or xdb) corresponding to the f06 file selected above.
d. Legend File: User selects the legend TCL file to be used to update the contour settings. The decimal precision
of contour values, number formatting, position of the legend etc. can all be defined in the legend TCL file.
Follow the tutorial shown below to set up your customized legend
e. Threshold: User specifies the vonMises stress threshold value for the elasto thermic subcase
3.8.2.6 Analysis Check List- Normal Modes

This category contains the analysis information extracted from the f06 file. The property editor area for
this category is as shown below
b. F06 File: User selects the .f06 file to be used to extract the Normal Modes information.
c. Normal Mode Subcase (F06 File): User selects the subcase corresponding to the Normal Modes. On selection
of the f06 file path above, the solution reads the different subcases present in the file and shows them here
in the drop down. The order of the key words searched in the f06 file to find subcases information is
“SUBCASE=”, “LABEL =”, “SUBTITLE=” and “SUBTITLE= ”. For instance, if the key word “SUBCASE=” is not
found in the f06 file, then the key word “LABEL =” is searched. If this key word is found, then the rest of the
key word search is aborted, and the sub cases information is extracted.
d. Result File: User selects the result file (op2, h3d or xdb) corresponding to the f06 file selected above.

e. Legend File: User selects the legend TCL file to be used to update the contour settings. The decimal precision
of contour values, number formatting, position of the legend etc. can all be defined in the legend TCL file.
Follow the tutorial shown below to set up your customized legend
f. Show Deformed Shape: User specifies if the deformed shape is to be shown in the images or not. If this
option is activated, then the following settings are also applied in the Deformed panel before capturing
images.
g. Capture Each Mode View in a Separate Image: User specifies if a separate image is to be captured for each
mode view. If this option is activated, then each mode view is shown in a separate image. If this option is not
activated, then all the 4 views (Left, Front, Top and ISO) of each mode are captured in one image.
3.8.3 Functionality
After providing the desired inputs and on click of “Execute”,
a. A copy of the “M2036 Excel Configuration” file (This is present in <Airbus Custom Tools Installation
Directory>/src_Reporting_Core/airbus/config) is made to the output directory with the name M2036-
Forms_CurrentDate_CurrentTime. This is done to prevent overwriting of the output M2036 files everytime.
The output excel file is opened in the background and the information extracted from the various user
inputs is written to the output excel file.
b. General – The inputs provided by the user such as Project, Part Component, compiled by etc. is inserted to
the corresponding cells in all the relevant sheets in the output excel file.

c. Files Record – The information about each file present in this folder (including sub folders) such as date of
creation etc. is read and added to the output excel file as shown below.
d. Model Check List: Sample f06 file used for testing and development is present in <Tool Install
Directory>/src_Reporting_Core/airbus/4_testdata/M2036_Forms/M,A_2-S15 SOL101 D20191025 UOR.f06
• The key word ‘M O D E L S U M M A R Y’ is searched in the selected f06 file and based on the element
mapping shown below, the number of Grids, 1Ds, 2Ds etc. are identified.
Info to be Key Words constituting Info in .f06

presented (Model summary section)
GRIDS GRID
1D CBAR, CBEAM, CROD, CFAST

2D CTRIA3, CTRIA6, CQUAD4,
CQUAD8
3D CTETRA4, CTETRA10
Springs CBUSH
Rigid Bodys RBE2, RBE3
Note: This element mapping can be easily updated in in the <Airbus Custom Tools Installation
Directory>/src_Reporting_Core/airbus/config/config.tcl as shown below.
• Various model checks such as Coincident Nodes, Coincident Elements, Free Edges, Element Warping
etc. are performed and more explanation behind each check can be found here: <HyperWorks
Installation Directory>/help/engsol/topics/pre_processing/aerospace/global_model_validation_r.htm

• This tool simply uses the Global Model Validation tool in Aerospace profile in the background for
performing all these checks.
• Two checks (Interior Angle TRIA and Interior Angle QUAD) are not a part of the Global Model Validation
tool. For these two checks, the standard “Element Checks” panel from HyperMesh is used by setting
the Calculation method to Patran as shown below.
• For all the model checks, images are also captured and stored in a folder called ‘ModelCheckImages’ in
the ARD output directory selected by the user as shown below.

• The NASTRAN Version (key word used is “Version”) and Operating System (The next line after the line
where the keyword MODEL is found) is read from the f06 file as shown below.
• The maximum diagonal factor is read from the f06 file (MAXIMUM MATRIX-TO-FACTOR-DIAGONAL
RATIO) as shown below. As there could be more than one set of these values, the first set is just taken
here.

• The key word ‘G R I D P O I N T S I N G U L A R I T Y T A B L E’ is searched in the f06 file and if it is
present, then Grid Point Singularity table empty value is set to No, otherwise Yes.
e. Static Analysis Check List: Sample f06 file used for testing and development is present in <Tool Install
Directory>/src_Reporting_Core/airbus/4_testdata/M2036_Forms/M,A_2-S15 SOL101 D20191025 UOR.f06
For each f06 file selected and for each sub case selected in the f06 file, the following is done:
• An excel sheet ‘Analysis_Check_List_Subcase ID’ is created in the output excel file.
• The load case information present in the f06 file is extracted from the f06 file and added to Load Case
Description section as shown below.
• The applied and reaction forces are read for the sub case. Key word used is ‘E Q U I L I B R I U M C H E C
K’ as shown below
• The GRID & VALUE of max/min summary of displacements is extracted for the subcase from the f06 file
(Key word used is ‘M A X / M I N S U M M A R Y ( DISPLACEMENTS )’) as shown below.

For the solution to extract the GRID & VALUE of max/min summary of displacements,
the following request must be present in the Nastran input deck.
• The Epsilon and External Work for each sub case is read from the f06 file (using the key word:
MAXIMUM MATRIX-TO-FACTOR-DIAGONAL RATIO) as shown below.

• After extraction of this information from f06, a new page is added in HyperView and the selected result
file is loaded into the new page. Contour is plotted using the default settings provided in <Airbus
Custom Tools Installation Directory>/src_Reporting_Core/airbus/config/config.tcl. If you want to plot
some other result type instead of displacements, then simply update the config.tcl section shown
below (Save the config.tcl after updation). If the legend file is provided, then the contour settings are
updated with respect to the legend file. If the “Show Deformed Shape” is activated, then the Deformed
shape is also shown with the settings shown in the User Inputs section of this module. Static min/max is
activated, and an image is captured for each selected sub case. The default image format is JPEG and
the width and height of the image used is 1240 and 974 respectively. This can be changed as shown
below in the config.tcl. The image format, height and width settings shown here apply to all the images
created by the custom M2036 Forms module.
Note: After updating the config.tcl, remember to relaunch HyperWorks and then launch Automated
Reporting tool for the changes to be made effective.
If the result type, component etc. specified by the user is not present in the result file, then the first
result type in the result file would be considered automatically.

Note: All the images corresponding to this section are placed in <ARD Working Directory Shown
Below>/StaticAnalysis folder
Note: To sum up, if 6 f06 files are selected and in each f06 file, if there are 100 sub cases, but the user
selects only 12 sub cases in each f06 file, then in total 72 (6*12) excel sheets are created in the output
excel file.

f. Elasto Thermic Analysis: Sample f06 file used for testing and development is present in <Tool Install
Directory>/src_Reporting_Core/airbus/4_testdata/M2036_Forms/ E-S15_TEMP_D20190520PRINT.f06
For the sub case selected in the f06 file, the following is done:
• An excel sheet ‘Elasto_Thermic_Analysis’ is created in the output excel file.
• The load case information present in the f06 file is extracted from the f06 file and added to Load Case
Description section as shown below.
• The applied and reaction forces are read for the sub case. Key word used is ‘E Q U I L I B R I U M C H E C
K’ as shown below
• The keywords “M A X / M I N S U M M A R Y (QUAD4)” and “M A X / M I N S U M M A R Y (TRIA3)” are

searched and the keywords corresponding to the selected subcase are found. As shown in the image
below, the element and stress value corresponding to the max stress are found. Max stress is found by
taking the max value out of 1,2,3,4 red marked circles below.

Note: For the solution to extract the maximum stresses, the following request must be
present in the Nastran input deck.
• The Epsilon and External Work for each sub case is read from the f06 file (using the key word:
MAXIMUM MATRIX-TO-FACTOR-DIAGONAL RATIO) as shown below.

For the solution to extract the GRID & VALUE of max/min summary of displacements,
the following request must be present in the Nastran input deck.
file is loaded into the new page. Contour is plotted using the default settings provided in <Airbus
below (Save the config.tcl after updation) If the legend file is provided, then the contour settings are
updated with respect to the legend file. Static min/max is activated, and an image is captured for each
selected sub case. The default image format is JPEG and the width and height of the image used is 1240
and 974 respectively. This can be changed as shown below in the config.tcl. The image format, height
and width settings shown here apply to all the images created by the custom M2036 Forms module.
If the result type, component etc. specified by the user is not present in the result file, then the first
result type in the result file would be considered automatically.

Below>/ElastoThermic folder
g. Normal Modes Analysis Checklist:
Sample f06 file used for testing and development is present in <Tool Install
Directory>/src_Reporting_Core/airbus/4_testdata/M2036_Forms/ NG-S15_SOL103_D20190520.f06
If the sub case is not present in the f06 file, then the first sub case present in the result file would be taken
as the Normal modes sub case.
• The mass information is extracted from the f06 file (Key word is “MASS AXIS SYSTEM”). X axis of Mass
is taken for the check 1 and check 3 in the forms.

• The Cycles information is extracted for each mode from the f06 file (Key word is “R E A L E I G E N V A L
U E S”. The first section of modes (1-6) are for check1 and second section of modes (7-15) are for
check3. Check2 is left blank
file is loaded into the new page. If the sub case information is not present in the f06 file, then the first
sub case in the result file selected is taken as the Normal Modes sub case. For each mode present in
the sub case, a new page is added with 4 windows and the view of model is set to Left, Front, Top and
Isometric views in these windows. Contour is plotted using the default settings provided in <Airbus
below (Save the config.tcl after updation). If the legend file is provided, then the contour settings are
updated with respect to the legend file. Static min/max is not activated by default, and an image is
captured.
• If the “Show Deformed Shape” is activated, then the settings shown below are configured in the
Deformed panel.

• If the “Capture Each Mode View in Separate Image” is activated, then for each view in the mode, a
separate image is captured. If the “Capture Each Mode View in Separate Image” is not activated, then
for each mode, an image is captured showing all the 4 views in that image. The default image format is
JPEG and the width and height of the image used is 1240 and 974 respectively. This can be changed as
shown below in the config.tcl. The image format, height and width settings shown here apply to all the
images created by the custom M2036 Forms module.
Below>/NormalModes folder

h. Ground Check Analysis Checklist:
Sample f06 file used for testing and development is present in <Tool Install
Directory>/src_Reporting_Core/airbus/4_testdata/M2036_Forms/ NG-S15_SOL103_D20190520.f06
• The ground check analysis information is extracted from the f06 file (using the keyword “RIGID BODY
CHECKS OF MATRIX” - multiple searches are performed to identify all the sets such as G-SET, N-SET, F-
SET, A-SET etc.). All the information shown for this key word block is extracted and added to the
Ground Check Analysis form.
3.8.4 Outputs
One excel file with multiple sheets containing the information extracted as shown above and
corresponding images.
3.8.5 Configuration
The configuration excel file for this module is in <Custom Tools Install
Directory>/src_Reporting_Core/airbus/config/M2036-Forms.xlsx.
Any changes made to this configuration excel file would be reflected in the final output table of
the module also.
You can change any of the below parameters in this configuration excel file:
a. Background color of the table
b. Title of the table
c. Numeric formatting within the table

d. Font Size of the contents of table
The sheet names should not be changed. Any rows or columns from any of the sheets should
not be removed. Once the desired changes are done, save this configuration file and re-launch
‘Automated Reporting’ for these changes to be made effective.
Related Tutorials are M2036 Forms
3.9 Compare Modes for Scaling Checks

3.9.1 Description
This module compares the cycles information for each mode between two different f06 files –
Reference and Variant f06.
3.9.2 Pre-requisites
Modes and cycles information should be present in the f06 files
3.9.3 User Inputs
User inputs for this module are below:
• Reference F06 File
• Variant F06 File
3.9.4 Functionality
• A check is done to make sure that the valid Reference and Variant f06 file paths are
given
• For each mode in both the f06 files, The Cycles information is extracted for each mode
from the f06 file (Key word used is “R E A L E I G E N V A L U E S”).
• For each mode, the formula used for cycle comparison is
Comparison = (Cycle Value from Reference Model - Cycle Value from Variant Model) /
(Cycle Value from Reference Model)

This comparison value obtained is then multiplied with 100 to get the percentage cycle
comparison value.
• The last two validation columns are intentionally left blank so that the user can fill the
information manually later.
3.9.5 Outputs
One excel file with one sheet containing the information extracted as shown above.
3.9.6 Configuration
The configuration excel file for this module is in <Custom Tools Install
Directory>/src_Reporting_Core/airbus/config/CompareModesForScalingChecks.xlsx.
Any changes made to this configuration excel file would be reflected in the final output table of
the module also.
You can change any of the below parameters in this configuration excel file:
a. Background color of the table
b. Title of the table
c. Numeric formatting within the table
d. Font Size of the contents of table
The sheet names should not be changed. Any rows or columns from any of the sheets should
not be removed. Once the desired changes are done, save this configuration file and re-launch
‘Automated Reporting’ for these changes to be made effective.
Related Tutorials are Compare Modes
3.10 Interfaces Identification

3.10.1 Description
This module finds the common nodes between various includes in the model
3.10.2 Pre-requisites
Include structure should be maintained in the FEM model selected. The include names should
contain the keyword specified by the user in the user interface of the module.

3.10.3 User Inputs
User inputs for this module are below:
• FEM Deck – Main deck that contains all the include structure
• Consider only Includes with Keyword – The keyword to be looked up in the include file names
• Image Caption – Desired caption of the image.
3.10.4 Functionality
• If a HyperMesh page already exists, then the page/window where HM client is present
would be identified and it is made the active page/window. If a model already exists in
the HyperMesh client, the user would be informed of this and is provided an option to
continue with erasing the existing model and loading the new model.
• If a HyperMesh page/window doesn’t exist, then the current page/window would be

changed to HyperMesh client.
• The FEM deck would be loaded in HyperMesh client
• All the includes that contain the keyword specified would be identified and the
components present inside these includes would be taken into consideration for
detecting the common nodes between these components. If the keyword is not
specified by the user, then all the includes in the model would be considered.
• The nodes that are shared by more than one component are identified using the Tools >
Find > Between option as shown below. A temporary node is created at all such
interface nodes
• The model is set to Isometric View and fit to screen and an image is captured with the
name specified by the user.
• The user is provided an option then to review the interface nodes found and edit
(add/delete) the interface nodes and capture one more image which would replace the
initially captured image.
3.10.5 Outputs
One image with the caption specified by the user.

Related Tutorials are Interfaces Identification
4. General Requirements
4.1 Operation System
The Model/Result Comparison tools is developed and tested on both Windows and Linux
platforms. Windows 10 and Linux CentOS 6.7 is used for testing from Altair side.
The Automated Reporting tool is developed and tested on Windows only. Windows 10 is used
for testing from Altair side.
4.2 HyperWorks Version
The Model/Result Comparison tools is developed and certified for HW 2017.2.4 and HW
2019.1.1. (Comparison by Location works only on HW 2019.1.1) and The Automated
Reporting tool is developed and certified for HW 2019.1.
4.3 Additional Software and Versions
For the Automated Reporting tool, Eventual MS Office Word Report would be created. MS
Office 2010 or above is needed.
4.4 Batch Mode execution
Batch mode functionality is not supported for both “Model/Result Comparison Tools” and
“Automated Reporting”. Only interactive mode.
4.5 Delivery of custom code
The solution would be delivered in TCL format as requested specifically by some Airbus users
4.6 Excel as Interface for Tables
Whenever a table will be created in Word, this table shall be first created within Excel.
The Excel file will be saved. After that this Excel table gets imported into Word. This
enables the user to modify the table within excel (in content and formatting) before it is
printed into the final document. The modifications of the format etc. in excel shall be
done by the end user only.
4.7 Reporting Format
All the custom modules are developed only for Word format and not for PPT. However,
user may use base modules in PPT mode.
5. Tutorial
Please follow the steps below to get ‘Hands-On’ on the software. Please complete the
Altair Model tutorials first before proceeding on to the Airbus model ones.
5.1 Comparison Based on IDs- Altair Model
5.1.1 Compare Internal Results

All the files required for this tutorial are present in <Airbus-CustomTools Installation
directory>/src_ModelResultComparison/4_testdata/Inputs_CompareInternalResults/AltairModel/. This would be
hereafter referred to as ‘Tutorial Files’
1. Open HyperView 2019.1.1
2. Launch the tool “Compare Internal Results” from the Airbus custom menu item.
3. Provide the following as inputs:
a. Reference Model- Select ‘Model 1.fem’ from the ‘Tutorial Files’

b. Result Files- Select ‘Model 1-Result 1.h3d’ and ‘Model 1-Result 2.h3d’ from the ‘Tutorial Files’
c. Load Combination Files- Select ‘Model 1-LSP 1.csv’, ‘Model 1-LSP 2.csv’, ‘Model 1-LSP 1_WF.SDB’ and ‘Model 1-
LSP 2_WF.SDB’ from the ‘Tutorial Files’
d. Output Directory- Any desired directory on local drive.
4. Click on “Get Loads” button in the GUI
5. Select the following load cases:
a. SET 1- DLC15, DLC010, DLC17, DLC02, Subcase 1 (GRAVITY)
b. SET 2- DLC12, DLC05, DLC11, Subcase 2 (FORCES)
6. For the “Use Elements” parameter, switch to “Selected” and using the “SELECT” button next to this parameter, select
the elements belonging to the set “Ply 1” as shown below
7. Click “Extract”
8. In the “Comparison View” browser that opens up,
a. Select Result Type as “Element_Stresses_(2D&3D)….”
b. Select Set 1 Subcase as “Max Envelope” and Set 2 Subcase as “Max Envelope” and click on “Compare Data”
c. Notice that a comparison is done and a CSV file, showing summary of comparison results is written to the output
directory and the CSV file is also loaded into TableView client on a new page (If show results in Table View is set
to Yes)
5.1.2 Compare Models

All the files required for this tutorial are present in <Airbus-CustomTools Installation directory>/
src_ModelResultComparison /4_testdata/Inputs_CompareModels/AltairModel/. This would be hereafter referred to
as ‘Tutorial Files’
1. Open HyperView 2019.1.1 and change the client to HyperMesh
2. Launch the tool “Compare Models” from the Airbus custom menu item.
b. Variant Model- Select ‘Model 2.fem’ from the ‘Tutorial Files’
c. Output Directory- Any desired directory on local drive.
4. Click on “Get Data” button in the GUI
5. In the “Selection” table that shows up,
a. In the Entity column, Select Elements;
b. In the Data Names column, Select Area and Aspect
c. Click on ‘Select’ button below. Notice that the selected data names show up in the section below. Refer to the
image below.

d. Similarly, In the Entity header, Select Nodes;
e. In the Data Names header, Select ‘globalx’, ‘globaly’ and ‘globalz’
f. Click on ‘Select’ button below. Notice that the selected data names show up in the section below
g. Similarly, In the Entity header, Select Properties;
h. In the Data Names header, Select ‘PSHELL_T‘
i. Click on ‘Select’ button below. Notice that the selected data names show up in the section below
j. Similarly, In the Entity header, Select Materials;
k. In the Data Names header, Select ‘E’
l. Click on ‘Select’ button below. Notice that the selected data names show up in the section below
m. Similarly, In the Entity header, Select EngineeringData;
n. In the Data Names header, Select ‘EA’
o. Click on ‘Select’ button below. Notice that the selected data names show up in the section below
a. Select Result type as “elements-area” and click on the “Compare Data” button
b. Notice that a comparison is done and a CSV file, showing summary of comparison results is written to the output
to Yes)
5.1.3 Compare Results Between Different Models

All the files required for this tutorial are present in <Airbus-CustomTools Installation
directory>/src_ModelResultComparison/4_testdata/Inputs_CompareDifferentResults/AltairModel/. This would be
2. Launch the tool “Compare Results Between Different Models” from the Airbus custom menu item.
b. Reference Result Files- Select ‘Model 1-Result 1.h3d’ and ‘Model 1-Result 2.h3d’ from the ‘Tutorial Files’
c. Reference Load Combination Files- Select ‘Model 1-LSP 1.csv’, ‘Model 1-LSP 2.csv’ from the ‘Tutorial Files’
d. Variant Model- Select ‘Model 2.fem’ from the ‘Tutorial Files’
e. Variant Result Files- Select ‘Model 2-Result 1.h3d’ and ‘Model 2-Result 2.h3d’ from the ‘Tutorial Files’
f. Variant Load Combination Files- Select ‘Model 2-LSP 1.csv’, ‘Model 2-LSP 2.csv’ from the ‘Tutorial Files’
g. Output Directory- Any desired directory on local drive.
a. SET 1- DLC02, Subcase 1 (GRAVITY)
b. SET 2- DLC04, Subcase 2 (Bending)

6. Open the “CommonElements_InBothModels.txt” in ‘Tutorial Files’ and copy the contents.
7. For the “Use Elements” parameter, switch to “Selected” and paste the element selection as shown below.
to Yes)
5.1.4 Compare Extracted Data

2. Launch the tool “Compare Extracted Data” from the Airbus custom menu item.
a. Results Directory – Any directory where the results are extracted for comparisons. For example, you can select
the output directory which you specified for the “Compare Internal Results” tool in the first tutorial
4. Click on “Compare Data” button in the GUI
to Yes)
5.2 Comparison Based on IDs- Airbus Model
5.2.1 Compare Internal Results

src_ModelResultComparison /4_testdata/Inputs_CompareInternalResults/AirbusModel/. This would be hereafter
referred to as ‘Tutorial Files’
2. Launch the tool “Compare Internal Results” from the Airbus custom menu item.
a. Reference Model- Select ‘A350_SMM13_i1b_d20180129.dat’ from the ‘Tutorial Files’
Note: Switch the file type as shown below for the Nastran File formats.
b. Result Files- Select ‘NAST13.OP2’ from the ‘Tutorial Files’

c. Load Combination Files- Select ‘LCDEF_edit.csv’, ‘LCDEFCRA_edit.csv’ from the ‘Tutorial Files’
d. Output Directory- Any desired directory on local drive.
a. SET 1- All LSP load cases that belong to the source ‘LCDEF_edit.csv’.
Tip: An easy way to do this is by moving the scroll bar to extreme right as shown below and then clicking on the
source header (This sorts the contents). Scroll down to the first row with source LCDEF and select that row. Press
the Shift button on keyboard and select the last row with source LCDEF.
b. SET 2- All LSP load cases that belong to the source ‘LCDEFCRA_edit.csv’.
6. For the “Use Elements” parameter,
a. Switch to “Selected” and using the “SELECT” button next to this parameter, select the element with ID 61108003
(This is an element on the left wing) and select ‘Proceed’ as shown in the image below.
b. Extend the elements selection by Face as shown below

to Yes)

src_ModelResultComparison /4_testdata/Inputs_CompareModels/AirbusModel/. This would be hereafter referred
to as ‘Tutorial Files’
a. Reference Model- Select ‘Model 1.dat’ from the ‘Tutorial Files’
b. Variant Model- Select ‘Model 2.dat’ from the ‘Tutorial Files’

d. In the Entity column, Select Elements;
e. In the Data Names header, Select Area and Aspect
f. Click on ‘Select’ button below. Notice that the selected data names show up in the section below. Refer to the
image below.

g. Similarly, In the Entity header, Select Nodes;
h. In the Data Names header, Select ‘globalx’, ‘globaly’ and ‘globalz’
j. Similarly, In the Entity header, Select Properties;
k. In the Data Names header, Select ‘PSHELL_T‘
m. Similarly, In the Entity header, Select Materials;
n. In the Data Names header, Select ‘E’
p. Similarly, In the Entity header, Select EngineeringData;
q. In the Data Names header, Select ‘EA’
r. Click on ‘Select’ button below. Notice that the selected data names show up in the section below
a. Select Result type as “elements-area” and click on the “Compare Data” button
b. Notice that a comparison is done and a CSV file, showing summary of comparison results is written to the output
to Yes)
5.2.3 Compare Extracted Data

2. Launch the tool “Compare Extracted Data” from the Airbus custom menu item.
a. Results Directory – Any directory where the results are extracted for comparisons. For example, you can select
the output directory which you specified for the “Compare Internal Results” tool in the first tutorial
4. Click on “Compare Data” button in the GUI
to Yes)

5.3 Comparison Based on Location- Airbus Model

src_ModelResultComparison /4_testdata/ Inputs_CompareModels_Location/AirbusModels. This would be
a. Reference Model- Select ‘s19_XLR_inclxbdfincl_REFERENCE.dat’ from the ‘Tutorial Files’
b. Variant Model- Select ‘S19_D150415_shifted_VARIANT.dat’ from the ‘Tutorial Files’

a. In the Entity column, Select Elements;
b. In the Data Names header, Select Area and Aspect
c. Click on ‘Select’ button below. Notice that the selected data names show up in the section below. Refer to the
image below.
d. Similarly, In the Entity header, Select Nodes;

e. In the Data Names header, Select ‘globalx’, ‘globaly’ and ‘globalz’
f. Click on ‘Select’ button below. Notice that the selected data names show up in the section below
g. Similarly, In the Entity header, Select Properties;

h. In the Data Names header, Select ‘PSHELL_T‘
j. Similarly, In the Entity header, Select Materials;
k. In the Data Names header, Select ‘E’
m. Similarly, In the Entity header, Select EngineeringData;
n. In the Data Names header, Select ‘EA’
6. Select ‘Comparison By’ as ‘Location- Element Dimension and Configuration’.
7. Click on “COMPARE” button that is present right next to the ‘Comparison By’ field.
8. Once the comparison is done, Open the MultipleMappingNodes.csv generated in the output directory and make sure
to review the mapping between Reference and Variant nodes here.
10. In the “Comparison View” browser that opens up, Select Result type as “elements-area” and click on the “Compare
Data” button (Keeping other parameters unchanged)
11. Notice that a comparison is done and a CSV file, showing summary of comparison results is written to the output
directory
12. Now, Select Result type as “property-PSHELL_Thickness” and click on the “Compare Data” button (Keeping other
parameters unchanged)
directory

14. Now, Select Result type as “properties-property.PSHELL_T” and specify the other parameters as shown in the image
below
directory.
16. Click on the window 3 in the new comparison page and switch to the Results browser and notice that two additional
sets as requested are created.
17. (Optional) To bring the sets created in the first page in HyperMesh to all the other pages/windows with HyperView
client, Click on “Synchronize Sets from HM to HV” tool in the “Airbus-Custom Tools” menu item
18. (Optional) Select all the sets in the HyperMesh page as shown below and click on OK

19. (Optional) Now, select the pages/windows where these sets need to be copied
20. (Optional) Notice that the sets are copied to the selected Pages and Windows (With HyperView client).
5.4 Base Reporting Solution (WORD Reporting)- Create Word report right from
scratch using Company Word Master document
The objective of this tutorial is to create a Model Overview report in Word format for an
Aerospace Wing Frame model using the Altair Word Master document. All the files required
for this tutorial are present in <Airbus Custom Tools Install
Directory>/src_Reporting_Core/ReportingTutorialFiles.
1. Open HyperView 2019.1.1.

2. From the HW menu bar, select File > Open > Session.
3. Select the ‘WingFrame_Variant1.mvw’ from the ‘Tutorial Files’ folder.
4. Select the user profile as ‘OptiStruct’.
5. From the HW menu bar, select File > Publish > Report to launch the ‘Report’ browser as
shown below. Alternately, it can also be launched from the drop down at the PPT Export
icon.

6. From the Report menu bar, select New > Word option.
7. Select the ‘wordMaster.docx’ shown in the ‘File Select’ window that shows up and click
on ‘Open’. This is the default Altair Word master document.
8. Select the Report level (Model Overview Report) and in the property editor area below,
specify the ‘Name’ as ‘Model Overview Report’ and click Enter
Introduction
9. Right click at the ‘Report’ level and select Add > Items > Chapter and In the property
editor area that shows up, enter the ‘Name’ of the chapter as ‘Introduction’.

10. Right click on the chapter ‘Introduction’ in the Report tree and select Add > Items > Text
and In the property editor area, click on the field against ‘Text’ and in the window that
shows up, specify the text as “This is a Model Overview Report” as shown below.
11. Right click on the chapter Introduction in the REPORT tree and select Add > Items >
Image and In the property editor area that shows up, Enter the ‘Name’ and ‘Caption’
as Model Overview.
Note: The string entered for field ‘Name’ shows up in the Report browser and the string
entered for field ‘Caption’ shows up as the caption of the image when the report is
exported.

12. Right click on the Image (Model Overview) in the browser and select Execute. Now, click
on the Preview/Eye icon to preview the image created.
13. In case, the ‘Model Info’ on HyperMesh page is not desired in the image, Switch to the
‘Model’ browser and hide the ‘Model Info’ as shown below.
14. Switch back now to the ‘Report’ browser and Right click on the Image (Model Overview)
again in the browser and select Execute. Now, click on the Preview/Eye icon to preview
the image created. Notice that the ‘Model Info’ is removed now from the captured image.
Similarly, the ‘Display Scale’ may also be removed in case it is not desired in the image.

Abbreviations:
15. Right click on the chapter ‘Introduction’ in the REPORT tree and select Add > Items >
Chapter and in the property editor area, enter the ‘Name’ of chapter as ‘Abbreviations’.
16. Right click on the chapter ‘Abbreviations’ in the REPORT tree and select Add > Items >
Word Document. In the property editor area, Select the ‘File Path’ as
‘Abbrevations.docx’ from the ‘Tutorial Files’ folder.
Software Used for Analysis
17. Right click on the chapter ‘Introduction’ in the REPORT tree and select Add > Items >
Chapter and in the property editor area, enter the ‘Name’ of chapter as ‘Software Used for
Analysis’.
18. Right click on the chapter ‘Software Used for Analysis’ in the REPORT tree and
select Add > Items > Excel Document. In the property editor area, Select the ‘File Path’ as
‘Software Used.xlsx’ from the ‘Tutorial Files’ folder. Select the ‘Sheet’ as ‘Sheet1’ and
specify the ‘Caption’ as ‘Software Used for Analysis’.
19. Right click at the Report level (Model Overview Report) and select Add > Items > Break.
In the property editor area, select the Orientation as ‘Page Break’.

Model Overview
20. Right click at the Report level (Model Overview Report) and select Add > Items >
Chapter. In the property editor area, Specify ‘Name’ of the chapter as ‘Model Overview’.
21. Right click the chapter ‘Model Overview’ in the REPORT tree and select Add > Items >
Text File. In the property editor area, Select the ‘File Path’ as ‘Model
Description.txt’ from the ‘Tutorial Files’ folder.
22. Right click the chapter ‘Model Overview’ in the REPORT tree and select Add > Modules
> Entity Overview. In the property editor area, Select the Model as Page 2/Window 1 and
Select Entity Type as ‘Components’.
23. Right click the module ‘Entity Overview’ in the REPORT tree and select Execute. Click
on the ‘Capture Image’ button in the stand-alone tool bar to capture the current window
and click on ‘X’ close button on the stand alone tool bar to close this additional GUI.
> Entity Overview. In the property editor area, Select the Model as Page 2/Window 1 and
Select Entity Type as ‘Properties’.
and click on ‘X’ close button on the stand-alone tool bar to close this additional GUI.
> Model Statistics. In the property editor area, Select the Model as Page 2/Window 1
27. Right click the module ‘Model Statistics’ in the REPORT tree and select Execute.
28. Switch to the Page 3 in HyperView manually
29. Right click at the Report level (Model Overview Report) in the REPORT tree and
select Add > Items > Chapter. In the property editor area, Specify ‘Name’ of the chapter
as ‘Results Overview’
Results Overview- Displacements Overview
30. Right click on the chapter ‘Results Overview’ and select Add > Items > Chapter. In the
property editor area, Specify ‘Name’ of the chapter as ‘Displacements Overview’
31. Right click the chapter ‘Displacements Overview’ in the REPORT tree and select Add >
Modules > Loop Results. In the property editor area,
a. Enter the ‘Name’ of the loop as ‘Displacements’
b. Select the ‘Model’ as ‘Page 3/Window 1’
c. Select the ‘Load Cases’ as ‘Subcase 1 (GRAVITY), Subcase 2
(FORCES) and Subcase 3 (PRESSURE)’ as shown below

32. Now, right click on the ‘Displacements (Loop Results)’ module and select Add > Items >
Image.
33. In the property editor area for image:
a. Select the ‘Note Display Options’ (from Notes section) as ‘master’.

b. Select the ‘Legend File’ (from HyperView section) as ‘Legend File.tcl’ from ‘Tutorial
Files’ folder.
c. Click on the widget against the field ‘Threshold’ (from Advanced section) and simply
click on the ‘OK’ button in the ‘Define Threshold’ window that pops up. This means that
the default fail and warn limits are accepted.

34. Select the module ‘Displacements (Loop Results)’ in the REPORT tree and right click and
select Execute.
35. Expand the Outputs section and click on the Preview/Eye icon for ‘Displacement (Mag)’
as shown below. Navigate through the various combination of ‘Components and Load
Cases’ by clicking on the various cells in the table. You may also update the image/view
for each combination of component and load case in case the view provided by the
solution is not satisfactory. Note that in case the view is changed and ‘Save Image’ button
is clicked, then the corresponding image for that combination is also automatically
updated in the ‘REPORT’ tree. Click ‘Cancel’ on the ‘Displacement (Mag)’ table
Note: Steps from 36-47 are optional and may be skipped. These optional steps explain
the various ways of setting up ‘Loop Results’ module.
Results Overview- Stress Overview

property editor area, Specify ‘Name’ of the chapter as ‘Stress Overview’
38. Right click the chapter ‘Stress Overview’ in the ‘REPORT’ tree and select Add >
a. Enter the ‘Name’ of the loop as ‘Stress
c. De-Select the already selected ‘All’ components and Select only components with IDs
105791, 105797, 105843 as shown below and click on ‘Proceed’ button
d. Select the ‘Load Cases’ as ‘Subcase 1 (GRAVITY), Subcase 2

39. Now, right click on the ‘Stress (Loop Results)’ module and select Add > Items > Image.
In the property editor area for image:
a. Select the ‘Model’ as ‘Page 4/Window 1’

b. (This step is optional and may be skipped, thereby retaining the default note text as it
is) Edit the ‘Note Text’ as shown below.
c. Select the ‘Note Display Options’ (from Notes section) as ‘master’.
d. Specify the ‘Zoom Factor’ (from Notes section) as 3
e. De-select the check button for ‘Hide Local System’ (from HyperView section)
40. Select the module ‘Stress (Loop Results)’ in the REPORT tree and right click and
select Execute.
41. Expand the Outputs section and click on the Preview/Eye icon for ‘Stress (vonMises)’ to
navigate through the various combination of ‘Components and Load Cases’.

42. Right click in the ‘Empty’ area in the ‘REPORT’ browser and select ‘Collapse All’ as
shown below
Results Overview- Forces Overview

property editor area, Specify ‘Name’ of the chapter as ‘Forces Overview’
45. Right click the chapter ‘Forces Overview’ in the ‘REPORT’ tree and select Add >
a. Enter the ‘Name’ of the loop as ‘Forces’
c. De-Select the already selected ‘All’ components and click on ‘Proceed’ button
d. Select the ‘Load Cases’ as ‘Subcase 1 (GRAVITY), Subcase 2
e. Select the check button for ‘Loop Over Hotspots’
46. Now, right click on the ‘Forces (Loop Results)’ module and select Add > Items > Image.
In the property editor area for image:

b. Specify the ‘Note Location’ as ‘HotSpots of Contour’
c. De-select the “Best View” option
d. Specify ‘Find Hotspots’ as ‘Above Threshold’
e. Specify the ‘Threshold’ value as 325
f. Specify the ‘Note Display Options’ as ‘master’

47. Select the module ‘Forces (Loop Results)’ in the REPORT tree and right click and
select Execute.
48. Click the ‘Export’ button on ‘Report’ menu bar to export the report to the desired
directory and notice that along with the word document, a Report Template (.tpl) file is
automatically created.

5.5 Base Reporting Solution (WORD Reporting) - How to insert Cross
References or Table of References in Word Reports
All the files required for this tutorial are present in <Airbus Custom Tools Install
1. Open HyperView 2019
2. Using File > Open > Session, launch the ‘WingFrame_Variant1.mvw’ from ‘Tutorial Files’
directory
3. From the HW menu bar, select File > Publish > Report to launch the ‘Report’ browser as
icon.
4. From the Report menu bar, select New > Word option.
5. Select the ‘wordMaster.docx’ shown in the ‘File Select’ window that shows up and click
on ‘Open’. This is the default Altair Word master document.
6. Select the Report level (Model Overview Report) and in the property editor area below,
specify the ‘Name’ as “How to Add Cross References” and Specify the Working Directory
as desired.
7. Right click at the Report level and add item “Table of Reference”.
a. Select the table showing Table of Reference in the Report tree and In the property
editor area below,
b. Click on Data and import the CSV “TableOfReferences.csv” from Tutorial Files
folder and Click on OK after the table is imported.

Table of Reference and Cross Reference
8. Right click at the Report level and add item ‘Image’. In the property editor area below,
specify the caption as “Model Overview”. Now, right click on the image and select
‘Execute’. The image on Page 1/Window 1 is now captured.
9. Right click at the Report level and add item ‘Text’
a. Specify text as “Please refer to” and right click then in the text widget and select
‘Insert Table of Reference’ and select the cell with title “DFEM Validation
CheckList2”.
b. Click Enter to go to the next line. Specify text as “Please refer to” and right click
then in the text widget and select ‘Add Cross Reference’ and select the image in the
tree in the GUI that shows up

c. Click OK finally on the text widget.
10. On successful assignment of cross references and table of references, the text window
should be as shown below.
11. Right click at the Report level and add item ‘Text’
a. Specify text as “Please refer to ModelOverview”. Now select the portion of text
‘ModelOverview’ and right click on the selected text and select ‘Add Cross
Reference’ and select the image in the tree in the GUI that shows up
b. Specify text as “Please refer to checklist”. Now select the portion of text ‘checklist’
and right click on the selected text and select ‘Insert Table of Reference’ and select
the image in the tree in the GUI that shows up.

c. On successful assignment of cross references and table of references, the text
window should be as shown below.
d. Click OK finally on the text widget. See the images below that explain the steps.
12. Now Export the word document finally.
5.6 Base Reporting solution (WORD Reporting)- Create Standardized Report

from a pre-defined Report Template (Interactive Mode)
The objective of this tutorial is to create a standardized Model Overview report in Word
format for an Aerospace Wing Frame model (Variant 1) using a pre-defined report template.
All the files required for this tutorial are present in <Airbus Custom Tools Install

2. Select the user profile as OptiStruct.
3. From the HW menu bar, select File > Publish > Report to launch the Report browser as
icon.

4. From the Report menu bar, select Load > Load Report Template option and select the
report template which is produced as an output of the previous tutorial.
5. In the stand-alone GUI that shows up,
a. Specify the ‘HM_MODEL_1’ as ‘WingFrame_Variant2.hm’
b. Specify the ‘GRAPHIC_FILE_1’ as ‘WingFrame_Variant2.fem’
c. Specify the ‘RESULT_FILE_1’ as ‘WingFrame_Variant2.h3d’
d. Specify the ‘Reporting Directory’ as desired or simply hit on the ‘Default’ button to
get a default reporting directory
e. For the ‘Word/PPT Master Document’, Click on the ‘Default’ button to use the
Default Altair Word Master document
f. Click on the ‘Load’ button. This loads the Report Parameters (Models/Results etc.)
and the Report Structure from the Report Template (TPL)
6. Once the report template that is produced as an output of the previous tutorial is loaded:
a. Right click at the Report level (Model Overview Report) and select Delete >
Outputs to delete the outputs of all the modules currently stored in the template.
7. Click on the Execute button from the REPORT menu bar.

8. Capture the required images for Components Overview and Property Overview. You can
re-position or update the notes as required.
9. Click on the Export button from the REPORT menu bar to export the report to desired
location.
5.7 Base Reporting Solution (PPT)- Create MS office PPT report right from
scratch using the Company PPT Master document
The objective of this tutorial is to create a Model Overview report in PPT format for an
Automotive Sub Frame model using the Altair PPT Master document. All the files required
for this tutorial are present in <Airbus Custom Tools Install

2. From the HW menu bar, select File > Open > Session.
3. Select the ‘SubFrame_Variant1.mvw’ from the ‘Tutorial Files’ folder.
icon.

6. From the Report menu bar, select New > PPT option.
7. Select the ‘pptMaster.pptx’ shown in the ‘File Select’ window that shows up and click on
‘Open’. (This is the default Altair PPT master document.)
8. Select the Report level and in the property editor area below, specify the ‘Name’ as
‘Model Overview Report’ and click Enter
Introduction

9. Right click at the Report level and select Add > Slide Layout > ‘One Image with Caption’
and
10. Note: These slide layouts are read from the PPT master file selected.
11. In the property editor area that shows up, enter the ‘Name’ as ‘Introduction’. This is
basically the title of the slide.
12. Switch to the ‘Text’ object in the first slide and specify the text as ‘Model Overview’ as
shown below.
13. Switch to the ‘Image’ object in the first slide and specify the ‘Name’ as ‘Model
Overview’ as shown below.

Note: The string entered for field ‘Name’ shows up in the Report browser only and is not
reflected anywhere in the exported PPT report.
14. Right click on the Image (Model Overview) in the browser and select Execute. Now, click
on the Preview/Eye icon to preview the image created.
15. In case, the ‘Model Info’ on HyperMesh page is not desired in the image, Switch to the
‘Model’ browser and hide the ‘Model Info’ as shown below.
16. Switch back now to the ‘Report’ browser and Right click on the Image (Model Overview)
again in the browser and select Execute. Now, click on the Preview/Eye icon to preview
the image created. Notice that the ‘Model Info’ is removed now from the captured image.
Similarly, the ‘Display Scale’ may also be removed in case it is not desired in the image.
Entity Overview
17. Right click at the Report level (Model Overview Report) and select Add > Modules >
Entity Overview. In the property editor area, Select the Model as ‘Page 2/Window 1’ and
Select Entity Type as ‘Components’.

and click on ‘X’ close button on the stand-alone tool bar to close this additional GUI.
Entity Overview. In the property editor area, Select the Model as Page 2/Window 1 and
Select Entity Type as ‘Properties’.
Model Statistics
Model Statistics. In the property editor area, Select the Model as Page 2/Window 1
21. Right click the module ‘Model Statistics’ in the REPORT tree and select Execute.
Displacements Overview
select Add > Modules > Loop Results. In the property editor area,
a. Enter the ‘Name’ of the loop as ‘Displacements’
c. Select the ‘Load Cases’ as ‘Subcase 2 (Bending) and Subcase 3 (Torsion)’ as shown
below

24. Now, right click on the ‘Displacements (Loop Results)’ module and select Add > Slide
Layout > One Image with Caption.
25. Switch to the Image object in the slide
26. In the property editor area for image:
a. Select the ‘Note Display Options’ (from Notes section) as ‘master’.

b. Select the ‘Legend File’ (from HyperView section) as ‘Legend File.tcl’ from ‘Tutorial
Files’ folder.
c. Click on the widget against the field ‘Threshold’ (from Advanced section) and simply
click on the ‘OK’ button in the ‘Define Threshold’ window that pops up. This means
that the default fail and warn limits are accepted.

27. Select the module ‘Displacements (Loop Results)’ in the REPORT tree and right click and
select Execute.
28. Expand the Outputs section and click on the Preview/Eye icon for ‘Displacement (Mag)’
as shown below. Navigate through the various combination of ‘Components and Load
Cases’ by clicking on the various cells in the table. You may also update the image/view
for each combination of component and load case in case the view provided by the
solution is not satisfactory. Note that in case the view is changed and ‘Save Image’ button
is clicked, then the corresponding image for that combination is also automatically
updated in the ‘REPORT’ tree. Click ‘Cancel’ on the ‘Displacement (Mag)’ table
Note: Steps from 28-43 are optional and may be skipped. These optional steps explain
the various ways of setting up ‘Loop Results’ module.
Stress Overview

select Add > Modules > Loop Results. In the property editor area,
a. Enter the ‘Name’ of the loop as ‘Stress’
c. De-Select the already selected ‘All’ components and Select only components with IDs
7,8 as shown below and click on ‘Proceed’ button
d. Select the ‘Load Cases’ as ‘Subcase 2 (Bending) and Subcase 3 (Torsion)’ as shown
below
31. Now, right click on the ‘Stress (Loop Results)’ module and select Add > Slide Layout >
Two Images with Captions. In the property editor area for image:
32. Switch to the first ‘Text’ object inside the slide and insert the word ‘Global’ in the text as
shown below.
33. Now, Switch to the second ‘Text’ object inside the slide and similarly insert the word
‘Local’ in the text.

34. Switch to the first ‘Image’ object in the slide,
b. De-select the “Best View” option
35. Switch to the second ‘Image’ object in the slide,

b. De-select the “Best View” option
d. Select ‘Zoom Factor’ as 3

36. Select the module ‘Stress (Loop Results)’ in the REPORT tree and right click and
select Execute.
37. Expand the Outputs section and click on the Preview/Eye icon for ‘Stress (vonMises)’ to
navigate through the various combination of ‘Components and Load Cases’.
38. Right click in the ‘Empty’ area in the ‘REPORT’ browser and select ‘Collapse All’ as
shown below

40. Right click at the Report level (‘Model Overview Report’) and select Add > Modules >
Loop Results. In the property editor area,
a. Enter the ‘Name’ of the loop as ‘Stress (HotSpots)’
c. De-Select the already selected ‘All’ components and click on ‘Proceed’ button
d. Select the ‘Load Cases’ as ‘Subcase 2 (Bending), Subcase 3 (Torsion)’ as shown
below
e. Select the check button for ‘Loop Over Hotspots’

41. Now, right click on the ‘Stress (HotSpots) (Loop Results)’ module and select Add > Slide
Layout > One Image with Caption. In the property editor area for image:
42. Switch to the ‘Image’ object inside the slide and

b. Specify the ‘Note Location’ as ‘HotSpots of Contour’
c. De-select the best view option
d. Specify ‘Find Hotspots’ as ‘Above Threshold’
e. Specify the ‘Threshold’ value as 2250
f. Specify the ‘Note Display Options’ as ‘master’

43. Select the module ‘Stress (HotSpots) (Loop Results)’ in the REPORT tree and right click
and select Execute.
44. Click the ‘Export’ button on ‘Report’ menu bar to export the report to the desired
directory and notice that along with the PPT document, a Report Template (.tpl) file is
automatically created.
5.8 Base Reporting Solution (PPT)- Create Standardized Report from a pre-
defined Report Template (Interactive Mode)
The objective of this tutorial is to create a standardized Model Overview report in PPT format
for an Automotive Sub Frame model (Variant 1) using a pre-defined report template. All the
files required for this tutorial are present in <Airbus Custom Tools Install

icon.

4. From the Report menu bar, select Load > Load Report Template option and select the
report template which is produced as an output of the previous tutorial.
5. In the stand-alone GUI that shows up,
a. Specify the ‘HM_MODEL_1’ as ‘SubFrame_Variant2.hm’
b. Specify the ‘GRAPHIC_FILE_1’ as ‘SubFrame_Variant2.fem’
c. Specify the ‘RESULT_FILE_1’ as ‘SubFrame_Variant2.h3d’
d. Specify the ‘PLOT_FILE_1’ as ‘SubFrame_Variant2.pch’
e. Specify the ‘Reporting Directory’ as desired or simply hit on the ‘Default’ button to
get a default reporting directory
f. For the ‘PPT/PPT Master Document’, Click on the ‘Default’ button to use the Default
Altair PPT Master document
g. Click on the ‘Load’ button. This loads the Report Parameters (Models/Results etc.)
and the Report Structure from the Report Template (TPL)
6. Right click at the Report level and select Delete > Outputs to delete the outputs of all the
modules currently stored in the template.
7. Click on the Execute button from the REPORT menu bar.
8. Capture the required images for Components Overview and Property Overview. You can
re-position or update the notes as required.
9. Click on the Export button from the REPORT menu bar to export the report to desired
location.

5.9 Airbus Custom Word Reporting Modules - M2036 Forms
All the files required for this tutorial are present in <Custom Tool Installation
directory>/src_Reporting_Core/airbus/Testdata/’. This would be hereafter referred to as ‘Tutorial Files’
1. Open HyperMesh Desktop 2019. Remember Not HyperMesh StandAlone or Not HyperView.
2. Launch the tool “Automated Reporting (ARD)” from the AIRBUS custom menu item and click OK on the user message
that shows up.
3. Click on the first button in the menu bar of the ARD browser (Tooltip of the button is ‘Create New Word Report’) and
Select the Airbus-wordMaster.docx from <Airbus Custom Tools Installation
Directory>/src_Reporting_Core/airbus/config> folder.
4. Select the Report level and in the property editor area

a. Specify the title as “Model Validation Report”
b. Specify the Working Directory as desired. Make sure that there are no spaces in this directory.
M2036
5. Make sure you specify the desired working directory in step 4 as all the outputs of the module (Excel file, log file,
images etc.) would be created inside this working directory.
6. Right click at the Report level and add modules “M2036 Form”
7. In the ‘General’ section enter the details as shown below.

8. In the ‘Files Record’ section select the folder ‘<Tutorial Files>/M2036Forms.
9. In the ‘Model Check list’ section
a. Select Output (F06 File) as ‘<Tutorial Files>/M2036Forms/M,A_1-S15 SOL101 D20191025 UOR.f06’
b. Select Nastran Deck as ‘<Tutorial Files>/M2036Forms/M-S15 SOL101 D20190520.dat’
c. Keep the default values for the other parameters in this section.
10. In the ‘Analysis Checklist – Static Analyses’ section
a. ‘Specify number of F06s’ as 2 from the drop down
b. Select F06 File-1 as ‘<Tutorial Files>/M2036Forms/ M,A_1-S15 SOL101 D20191025 UOR.f06’
c. Select the Subcases-1 as ‘GRAVITY_-1GX’ as shown below. Remember to click the OK button after selecting the
sub case.
d. Select the Result File -1 as ‘<Tutorial Files>/M2036Forms/A-1-S15 SOL101 D20190520.op2’

e. Select F06 File-2 as ‘<Tutorial Files>/M2036Forms/ M,A_2-S15 SOL101 D20191025 UOR.f06’
f. Select the Subcases-2 as ‘GRAVITY_-1GY’ and ‘GRAVITY_-1GZ’ as shown below. Remember to click the OK button
after selecting the sub case.
g. Select the Result File -2 as ‘<Tutorial Files>/M2036Forms/A-2-S15 SOL101 D20190520.op2’

11. In the ‘Analysis Check List – Elasto Thermic Analysis’ section
a. Select F06 file as ‘<Tutorial Files>/M2036Forms/ E-S15_TEMP_D20190520PRINT.f06’
b. Select Elasto Thermic Sub case as ‘THERMO-ELASTIC CHECK (1)’
c. Select Result File as ‘<Tutorial Files>/M2036Forms/E-S15_TEMP_D20190520.op2’
12. In the ‘Analysis Check List – Normal Modes and Ground Check Analysis’ section
a. Select F06 file as ‘<Tutorial Files>/M2036Forms/NG-S15_SOL103_D20190520.f06’
b. Select Result File as ‘<Tutorial Files>/M2036Forms/NG-S15 SOL103_D20190520.op2’
13. Right click the module “M2036 Form” and click “Execute”.
14. Now Export the word document finally as shown below to the desired directory

5.10 Airbus Custom Word Reporting Modules - Compare Modes for Scaling Checks
1. Open HyperView 2019
that shows up.

b. Specify the Working Directory as desired.
Compare Modes for Scaling Checks
6. Right click at the Report level and add modules “Compare Modes for Scaling Checks”
7. Select the Reference file as <Tutorial Files>/CompareModes/AC_SOL103_mm_Ref.f06
8. Select the Variant file as <Tutorial Files>/CompareModes/AC_SOL103_mm_Scaled.f06
9. Right click the module “Compare Modes for Scaling Checks” and click “Execute”.
5.11 Airbus Custom Word Reporting Modules - Interfaces Identification

1. Open HyperMesh Desktop 2019
that shows up.


b. Specify the Working Directory as desired.
Interfaces Identification
6. Right click at the Report level and add modules “Interfaces Identification”
7. Select the FEM Deck as <Tutorial Files>/Interfaces Identification - Complete Aircraft/GRAV_Output-1000.dat
8. Keep the default values for the other parameters in this section.
9. Right click the module “Interfaces Identification” and click “Execute”
10. (Optional) Click the Shoft + F2 button on keyboard and update the interface nodes and click on the “Capture Images”
button as shown below.
6. TroubleShooting
6.1 Model/Result Comparison Tools
6.1.1 Character Limitation for File Paths in Windows

As the maximum characters in the file path can not exceed 260 characters in windows, it is
advised to have a short path for the Output Directory in the three compare tools. All files
created would be saved in this working directory defined. It is advised not to select a output
directory that contains more than 160 characters keeping in mind that the new files created by
the solution would also have some characters length. Please refer to
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file for more details.
6.1.2 Ulimit value setting in Linux

In ‘Compare Internal Results’ and ‘Compare Different Results’ tools, In the main Graphical
User Interface, If the user selects more than 500 load cases in either SET1 or SET2 on
LINUX OS, Then sometimes due to a local setting called ulimit, all the 500 load cases may

not be enveloped. Ulimit decides how many files can be loaded simultaneously. Setting this
value to a higher number or unlimited will resolve this issue. Please refer to
https://www.ibm.com/support/knowledgecenter/en/SS8NLW_10.0.0/com.ibm.discovery.es.in.
doc/iiysiulimits.htm) for more details.
6.1.3 Rods as Beams in HyperView

HyperView tends to show the rods, bars etc. as beams. So, the custom tool which is dependent
on HyperView also shows the rods, bars as beams. This would be enhanced as a part of the
next phase of the project.
6.2 Automated Reporting
6.2.1 Character Limitation for File Paths in Windows

As the maximum characters in the file path can not exceed 260 characters in windows, it is
advised to have a short path for the Working Directory in the Reporting solution. All files created
would be saved in this working directory defined. It is advised not to select a working directory
that contains more than 160 characters keeping in mind that the new files created by the
solution would also have some characters length. Please refer to
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file for more details.
6.2.2 Pending Action in MS Office Before Export

Before exporting Word or PPT reports, any pending actions in the already opened MS Office
applications (This includes PowerPoint, Excel, Word, Outlook etc.) must be completed first.
For instance, image shown below with Save or Don’t Save dialog is a pending action and this
needs to be addressed first before exporting a new report through ARD.

6.2.3 Changes to Report Level
User should define report level settings only once and that too right after starting ARD. Any
changes done to the report level (Ex. Changing work directory, Save PDF, Capture HW
resolution etc.) after adding/executing/exporting a few modules may lead to errors/undesired
behavior. Imagine, a user trying to change the working directory just before exporting the
report, In this case, all the created images/excel files etc. are stored in the previous work
directory and this leads to errors.
6.2.4 Word Report Creation Failed

In case, the user message “Word report creation failed. Please try again” appears, this can be
due to a variety of reasons such as User Right Access issues, MS Office Issues/Updates,
Windows Issues/Updates etc.

To cleanup, please do the following things in the same sequence:
a. Close all the currently opened MS Office applications (This includes Word, Excel, PowerPoint etc.)
b. Close all the currently opened HyperWorks applications
c. Delete all the contents of temp directory. (The temp folder should be empty). Temp directory can
be found by typing “%temp%” and click Enter in the Windows Explorer as shown below. Note
that your Matrix Browser Macros may also get deleted if they are stored in the temp directory,
So, you might move the macros before deleting the temp directory.
d. Restart Computer
e. Note that the entire report structure need not be created again in ARD, Simply Launch HW and
launch ARD tool and click on “Load Template” use case and select the last generated tpl file.
f. If this error still shows up, please contact Broemmer, Gerd [email protected] or
Rudorff, Sven-Thomas [email protected]

6.2.5 M2036 Forms
For the M2036 forms module to extract the ‘right’ information from the f06 files, the following
output requests must be requested in the Nastran input deck and then the relevant information
is extracted from the f06 file.
6.2.6 Core Reporting, Airbus Custom Reporting and Automated Reporting Director
From HW 2019.1.1, Automated Reporting Director (ARD) (which is formerly a Packaged
Solution Offering PSO) is integrated in core HyperWorks. The integrated solution is called
“Core Reporting”.
Launching ARD and Core Reporting solution in the same session would lead to conflict
between both the tools and produces TCL errors. It is therefore advised to launch the two
tools in separate HW sessions if required.
Core Reporting Solution can be launched in HW 2019.1.1 by FILE > PUBLISH > REPORT. In
the Core Reporting solution, Airbus custom modules (M2036 Forms, Interfaces Identification
and Compare Modes for Scaling Checks) would not be shown.
The Custom Reporting solution (Which is Core Reporting + Airbus Custom modules mentioned
above) can only be launched from the “Airbus-Custom Tools” menu item only.
6.2.7 Do not open output files while the module’s execution is running or while the
report is being created
It is highly recommended not to open any of the output files such as the M2036 excel file or
images during the module’s execution. However, once the module’s execution is complete,
these output files can be opened and reviewed or updated.
Similarly, during Export of the Report also, it is recommended not to open any of the output
files such as the M2036 excel file or images.
7. Project Stakeholders
The main technical lead for this project is KARL BRÖKER ([email protected]) from
Airbus Operations, Hamburg.
If you notice any bugs while using the solution or if you have any new enhancement requests,
Kindly get in touch with this technical lead first before you get in touch with Altair directly as
the technical lead might have known about the limitation in the solution or probably got the
solution developed only for specific needs. This technical lead is also responsible for collecting

all such bugs/enhancements requests within Airbus and prioritizing the implementation of
these requests.

Manual Airbus Custom Tools: (Model/Result Comparison Tools and Reporting)

Uploaded by

Copyright:

Available Formats

Manual Airbus Custom Tools: (Model/Result Comparison Tools and Reporting)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Airbus Custom Tools: (Model/Result Comparison Tools and Reporting)

Uploaded by

Copyright:

Available Formats

What are the main tools described in the document?

What are the main tools described in the document?

What are the user inputs required for the 'Compare Models' tool?

What are the user inputs required for the 'Compare Models' tool?

Manual

Airbus Custom Tools

03. December 2019

Altair Engineering GmbH 1

Altair Engineering GmbH 2

Altair Engineering GmbH 3

2. Installation by adding a menu button

Figure: Installing the tool

Tool Script to Load

Compare Internal Results <Tool-Installation-Directory>/src_ModelResultComparison/

Compare Results Between <Tool-Installation-Directory>/src_ModelResultComparison

Compare Models <Tool-Installation-Directory>/src_ModelResultComparison

Altair Engineering GmbH 4

Synchronize Sets from HM <Tool-Installation-Directory>/src_ModelResultComparison

Automated Reporting <Tool-Installation-Directory>/src_Reporting_Core/

3.1 Compare Internal Results

3.1.2 User Inputs

Altair Engineering GmbH 5

a. Inputs provided are validated.

Altair Engineering GmbH 6

Altair Engineering GmbH 7

Related tutorials are Altair Model and Airbus Model

3.2.2 User Inputs

Altair Engineering GmbH 8

Altair Engineering GmbH 9

a. Inputs provided are validated for correctness

Altair Engineering GmbH 10

Related tutorials are Altair Model

Altair Engineering GmbH 11

a. The reference model selected is loaded on to the current page/window.

On click of “Compare” button, the following actions are performed:

Altair Engineering GmbH 12

Altair Engineering GmbH 13

Related tutorials are Altair Model and Airbus Model

3.4 Compare Extracted Data

3.4.2 User Inputs

3.5 Comparison by Location

Altair Engineering GmbH 14

g. Similarly, for nodes also, these four sets are created.

Altair Engineering GmbH 15

Altair Engineering GmbH 16

Related tutorials are Airbus Model

3.6 Synchronize Sets from HM to HV

3.6.2 User Inputs

3.7 Core Reporting

Altair Engineering GmbH 17

3.8 M2036 Forms

3.8.2 User Inputs

• Model Check List

• Analysis Check List – Static Analyses

• Elasto Thermic Analysis

• Normal Modes and Ground Check Analysis

• FEM Identity Card

3.8.2.2 Files Record