GT-POST User's Manual GT-SUITE

(1)

GT-SUITE

GT-POST User's Manual

VERSION 7.4

by

Gamma Technologies

All information contained in this manual is confidential and cannot be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without

the express written permission of Gamma Technologies, Inc.

(2)

GTI SUPPORT

• TELEPHONE: (630) 325-5848

• FAX: (630) 325-5849

• E-MAIL: support@gtisoft.com

• Web Address: www.gtisoft.com

• Address: 601 Oakmont Lane, Suite 220 Westmont, IL 60559

USA

Telephone Support Hours

8:00 A.M. to 5:30 P.M. Central Time Monday - Friday

(3)

CHAPTER 1: Introduction to GT-POST

1.1 What is GT-POST

GT-POST is a powerful data analysis tool used to plot, view, and manipulate data generated either by a GT-SUITE simulation or by an external source. It offers a more efficient data analysis solution than standard spreadsheet software. By employing data pointers, the results viewed in GT-POST are updated automatically and immediately when a model is changed and a simulation is rerun. Also, GT-POST lends itself nicely to the development of portable, user-defined templates that control how results are presented.

This manual describes the features of GT-POST. It is assumed that the user is already familiar with GT- ISE, the GT-SUITE Graphical User Interface (GUI), and the process of building models in GT-SUITE.

1.2 Consider Learning GT-POST by tutorial or training class

This manual documents the features of GT-POST and can be a useful reference, but most users of GT- SUITE have found that the easiest way to learn GT-POST is by working through a tutorial or taking a training class. The GT-POST tutorial can be found at

$GTIHOME\vX.X.X\tutorials\Graphical_Applications\GTpost\gtpost-tutorials.pdf. A training class is also strongly recommended for users of GT-SUITE. The training includes instruction on using the GT- ISE interface, proper modeling techniques, different modeling options, as well as interpreting results using GT-POST. This approach is the fastest, most effective, and most enjoyable way to learn about GT- SUITE. Please see http://www.gtisoft.com/training/training.php for information on training in the United States and Europe and http://www.gtisoft.com/contacts.html for contact information for our representatives in Japan, Korea, China, India, and Brazil.

1.3 Starting GT-POST

GT-POST can be launched from within GT-ISE either by clicking the "Open GT-POST" toolbar button, or by selecting the "Open GT-POST" option under the Run menu. When GT-POST is opened from within GT-ISE, a dialog box will prompt the user to select a .gdx file. The default .gdx file (which automatically appears in the "File name" field) corresponds to the currently active GT-ISE model.

GT-POST can also be opened independently of GT-ISE, by running the GT-POST executable from the command prompt in Windows or UNIX, or from Explorer in Windows.

1.4 GT-POST Files

The following are files relevant to GT-POST:

• The .gdx file is a read-only file that can be opened in GT-POST to view all results requested from the simulation. This file is created by GT-SUITE at the end of each simulation and contains all requested plots and tables, a copy of the project map, and all animation and order data. Because the .gdx file is read-only, plots, tables, and data can be viewed but not modified (because any changes made to this file by the user would be overwritten if the simulation was re-run). Also, new plots, tables, and data cannot be added without explicitly requesting additional plots from within GT-ISE and then rerunning the simulation.

• The .gu file is a user plot file that can be created by the user for the purpose of manipulating plots, tables, or data sets. This user has "write" access to this file, because it is not directly associated with

(5)

any particular simulation (so the file cannot be overwritten when a simulation is re-run). Plots, tables, and implicit data can be copied directly from a .gdx or .gp file into the .gu file. In addition, plots or tables created using the numerous macros available in GT-POST will be placed in a .gu file. Also, .gu files may contain explicit data (i.e. data entered directly by the user) or implicit data with links to Ascii or Excel files.

• The .snap file is a method of storing a plot or set of plots for future viewing within GT-POST. A .snap file is only created by request of a user of GT-POST (right click on plot tab, Save As > Snap File) and is a convenient way to share a specific set of plots with another GT-SUITE user without requiring all of the associated .gdx files to be sent. A .snap file will open in POST and the plot(s) will be automatically viewed. However, there is no tree on the left, and all data is explicit. In this way the file is standalone, and simply by opening the file, the desired plots are displayed.

• The .gp file is an intermediate file which contains pointers to the data in the .gdx file for the plots specifically requested by the user (prior to the start of the simulation). This file also contains the data and plot-formatting instructions that are internally hardwired for each GT-SUITE application. At the end of a simulation, all of the information in the .gp file is assimilated into the .gdx file. To create this file, go to the Tools menu within GT-ISE, select Options…, choose the Run tab, and check the item Create .gp/.alt/.olt files. Plots resulting from simulations run in older versions than 6.0 of GT- SUITE will be stored in .gp files. GT-POST can open .gp files directly.

• The .gpd file is effectively a "style" template that determines the default properties and presentation of plots and data. All .gdx files generated from GT-SUITE simulations point to an application- specific .gpd file (e.g. $GTIHOME\vX.X.X\resrc\gtpower.gpd). Users are able to edit the default .gpd files or create their own .gpd files in GT-POST.

• The .plt file is a binary-format plot file generated by an older version of GT-POST. These .plt files may be opened directly via the File menu and viewed in GT-POST.

• .gx/.gdt are database files which stored simulation data for GT-SUITE applications in V7.3 and older.

Starting in V7.4, these two files were replaced with the single .gdx file.

1.5 GT-POST Views

GT-POST provides simulation post-processing functionality through the *.gdx file via 4 different operating views. The user can easily toggle between these four views using the buttons in the upper left hand corner of the *.gdx file window:

• Arrange Windows for Plotting View automatically controls window sizes and positions for convenience when working primarily with plot trees and the plot window. All *.gdx and *.gu files will be tiled to the left (and may be minimized or maximized), while the Plot Window is fixed to the right. This view closely duplicates GT-POST behavior from previous versions and can be accessed through the "Tile for Plotting" button.

• GT-ise Style Map View closely resembles the project map in GT-ise. Both instantaneous plots and RLT data (an RLT variable is any simulation result which is calculated by GT-SUITE once per cycle) may be accessed through this view by single-clicking or right-clicking on the appropriate part in the map. The map display properties may be temporarily changed by right-clicking on the map;

these settings may also be changed globally in the Tools Options… menu.

• RLT Contour Map View allows the user to view a particular RLT variable result for all parts simultaneously in a graphical representation of the model. It is also possible to view all RLT variables for a specific part or group of similar parts. In addition, the user can view an animation plot

(6)

for each part which shows how the given RLT variable changes for each sub-volume within the part.

Both instantaneous plots and RLT data may be accessed through this view by right-clicking on the appropriate part in the map. The map display properties may be temporarily changed by right- clicking on the map; these settings may also be changed globally in the Tools Options… menu.

• Animated Contour Map View allows the user to watch an animated graphical representation of how a given result variable changes with time in every sub-volume in the model. The user can also generate an animation file (.avi or .mov) which can be viewed with video player software. Animation view also provides the capability to create spatial animation plots, which gives the user a clear view of wave dynamics in pipes and flowsplits and displays standing wave mode shapes.

1.6 GT-POST Tiling Modes

In addition to the 4 View options described above, GT-POST Files (i.e. *.gdx and *.gu files) may be automatically tiled using the three options described below, which can be found on the main tool bar:

• Arrange Windows for Plotting is described above in GT-POST Views.

• Arrange Windows Freely allows all GT-POST windows to behave as standard windows.

They may be maximized, minimized, or resized however the user desires. In this mode, *.gdx file and *.gu files are treated the same.

• Arrange Windows to work with maps is a specific tiling option that will tile *.gu files to the left (assuming a standard width) with the remainder of the space on the right allocated for

*.gdx files. These *.gdx files can be maximized, minimized, etc. within their designated space, but will never cover up a *.gu file. However, if no *.gu files are open, the entire workspace will be allocated for the *.gdx file(s). If a *.gu file is opened (or created from scratch), space on the left will automatically be allocated, and the *.gdx file(s) will resize accordingly.

1.7 GT-POST Tools Menu

There are a number of useful items located in the Tools menu of GT-POST:

Open Output Files:

This option enables the user to directly open solver text output files associated with the active *.gdx file from within GT-POST. This option can be accessed from the Tools menu or from the "Open solver text output files" button on the toolbar. When this option is selected, a dialog will open that allows the user to select any solver output file (*.out, *.msg, etc.). The selected file will open in the third party text editor defined within Tools/Options.

Import Excel/Ascii:

This feature will allow GT-POST to import multiple Excel or Ascii datasets into the plot or table tree of a GU file. The ability to import Excel or Ascii data is also available from a toolbar button and from the

"add data" right-click option in plots and tables, and is covered in detail in the Plots/Tables Chapter.

Export Data …:

This feature enables the export of plot or RLT data to an Ascii text file (including .csv format). A wizard will allow selection of multiple result variables to include in the export and offers flexibility in the

(7)

grouping and formatting of the data. The ability to export data is available only when a *.gdx file is active and can also be accessed via the "Export data to text files" button on the toolbar.

Configure Default RLT Units …:

This option opens a wizard that allows the user to select the global default units of any Instantaneous Plot or RLT variable that will be used in the plots or viewed in the RLT Viewer Mode. Note that the units that are displayed in GT-POST can also be changed by the user locally for that specific instance. This option is useful if a user will always want a particular Plot or RLT variable to be displayed in a non-default unit.

In the first screen of the wizard, a unit category is selected and then the specific units to replace are defined. The second screen then shows a tree containing all RLT variables arranged by template that are currently assigned the unit to replace. The checkboxes can be used to select a subset of the tree for replacement. In the example shown below, the default unit of the "Initial Heat Transfer Area" RLT of the 'Burner' template is changed from m^2 to mm^2.

(8)

1.8 Tools Options…

1.8.1 General Warn Before Closing Application

If this is checked, a warning message will come up every time GT-POST is closed. It will ask the user if they really want to close GT-POST.

Save relative path to data files

If this option is checked, then all .gdx file references in a .gu file are written with relative paths rather than absolute paths. This option is useful if the user often moves .gu and the associated .gdx files.

Show Evolution Message at File Open for Report Tables

If this option is checked, GT-POST will display a message when any file is evolved from an old version of GT-POST that contains tables using an old format. These tables cannot be viewed and will not be evolved. The simulation will need to be rerun with the new version in order to regenerate these tables.

Autosave Every __

Minutes

This allows the user to specify the time in minutes between each autosave event. If this option is not selected, GT-POST will not create any autosave files (not recommended).

Query Results/De-select Variables With No Data in RLT Trees

If this option is selected, GT-POST will query the result database (.gdx) to determine which RLT variables exist. Any RLT that is not found in the result data will be unchecked in the CaseRLT and TimeRLT trees.

The database queries are done by template as the RLT trees are expanded and can take several seconds, especially for templates with large numbers of RLT's (i.e. EngCylinder). This delay can be avoided by de-selecting this option. In this case, all RLT variables will be checked in the tree whether or not they have data.

(9)

RLT tree level to expand on open

This sets the desired level of the RLT tree to initially expand to upon entering the CaseRLT or TimeRLT folders within Plots/Tables mode.

Number of Significant Figures Displayed:

This controls the number of significant figures of the data displayed on the map in the RLT Viewer Mode.

Clear recent file list This option will remove all files from the recent file list under the File menu.

1.8.2 Plot/Table Viewing

Plot Initial Zoom Factor: This sets the initial optical zoom level for viewing plots (to avoid constantly zooming plots in or out depending on screen size and resolution). Note the "Auto" option, which will automatically adjust the zoom as the plot window size is adjusted so that the entire plot is visible.

Plot Color Scheme: Defines the color scheme used for all plots, either black or white background.

Location of new tree items:

This option determines whether new plot or table tree elements (groups/plots/tables/datasets) will be added to the beginning or the end of the parent tree element.

Maximum number of tabs in view:

This attribute determines the maximum number of view tabs that may exist in the Plot / Table view pane. Once this maximum is reached, each subsequent view operation that generates a tab will cause the oldest unpinned tab to disappear.

Prompt Before Assigning Y2 Axis

When this option is selected, the warning message that normally pops up when a dataset of some unit is dragged and dropped into a plot which already has a Y dataset of a different unit, will not be displayed. The warning message tells the user that a data set with a different unit is using the Y axis and asks if the user wants to assign the new data set to the Y2 axis.

Ask confirmation when closing any tab

Defines whether a dialog will open asking for confirmation each time a plot view tab is closed.

Automatically view highlighted tree item

Turns on automatic viewing mode such that a new plot view is automatically generated whenever the highlighted tree item changes (no view command required). This means that any left click in the plot/table tree will generate a new view. Note that this option can also be toggled on or off using a toolbar button.

Automatically create snapshot for recent view

Turns on an option to automatically take a snapshot of the previous Live View with each new view command. This replicates classic GT-POST behavior from V6.2 and earlier where a separate tab was generated with each successive view command. Note that this option will slow down plotting performance by requiring a snapshot for every view command.

1.8.3 Map Options Default Map Background Color:

This sets the background color of any *.gdx file opened in GT-POST.

This option could be used to distinguish the GT-POST map from the GT-

(10)

ISE map, or could simply be used to "customize" the look and feel of GT-POST to the user's liking.

Fade Parts without Plots: Enabling this option will fade all of the parts on the map which do not have instantaneous plots turned on. This is useful if one wishes to view part plots from the map using the right-click option. This fading option is also available via the toolbar button.

Display Background Grid:

This option is used to determine how the map background grid will be displayed upon opening a *.gdx file in GT-POST. If "Load from GTM"

is chosen, the state of the grid (On or Off) will be determined by the grid settings of the *.gtm model file defined in GT-ISE.

Display Link ID Numbers:

This option is used to determine how the Link ID Numbers will be displayed upon opening a *.gdx file in GT-POST. If "Load from GTM"

is chosen, then the display settings will be determined by the settings of the *.gtm model file defined in GT-ISE.

Display Component Names:

This option is used to determine how the Component Part Names will be displayed upon opening a *.gdx file in GT-POST. If "Load from GTM"

Display Connection Names:

This option is used to determine how the Connection Part Names will be displayed upon opening a *.gdx file in GT-POST. If "Load from GTM"

Default setting in gdx file for 'Draw Numbers on Map':

This option is used to determine how the "Draw Numbers on Map"

option of the "RLT Contour Map" view will be set upon opening a *.gdx file in GT-POST.

1.8.4 Plot Auto Increment Settings

This folder allows the user to globally configure the appearance of the plots. By using the “Automatic”

Increment by dropdown, any plots whose display properties are set to “automatic” will inherit the properties in this folder. In this way, users can easily differentiate between plots based upon file, case, part, and a number of other criteria. Additionally, these properties can be overridden in the individual plots by using the Children Properties->Data feature.

1.8.5 Table Format

This folder allows the user to configure the appearance of the tables that can be viewed in the Plots/Tables Mode. The font, text alignment, colors, and column widths can all be changed independently for row and column headers and for even and odd datasets.

1.8.6 Paths

Alternate Unit Lookup File

This option defines a file to be used to assign units during the importing of Excel or Ascii data. When data is imported from an external file, a unit row may optionally be specified. In this case, GT-POST will read the text strings in the cells of this row in an attempt to correctly define the unit for that column of data. There is a default string that will be

(11)

interpreted correctly for each unit, but any alternative text strings need to be defined in an alternate unit lookup file. A new unit lookup file can be created by selecting "New". This will bring up the window shown below, where the default string for each unit is shown in the first column.

The remaining columns can be used to enter alternate text strings that should also be interpreted as the same unit. In the example below, either the default "m^2" or the alternate "m2" will be interpreted as AREA in meters squared. Once a file is saved, it can be modified later using the

"Modify" option.

PDF Reader This determines the path of the PDF Reader used to open tables exported to PDF file.

Default Editor This determines the path of the text editor used to open solver text output files, and includes an option to set program arguments.

1.9 Allocating More Memory to GT-POST or Opening Large Files

In certain cases, GT-POST may run out of memory when post processing many files simultaneously or when a single file is very large. "Huge Mode" is a configuration of GT-ISE and GT-POST that allocates more memory to these applications. There are default amounts of initial and maximum memory that are allocated to GT-ISE and GT-POST when the applications are started. A typical model will not need more memory than the default maximum, however in certain situations, such as opening the results file of a large DOE, Huge Mode will be needed. GT-ISE and GT-POST will notify the user with a warning message if the applications do not have enough available memory to proceed. Some examples of error messages are "Java Heap Space Error" or "Out of Memory".

To use the Huge Mode, there are two options. The first option is to temporarily run in Huge Mode. This is the recommended option, because when GT-ISE/GT-POST is closed, the allocated memory will reset to the default settings. However, if very large models or results files will be handled frequently, then the second option is to permanently run in Huge Mode. The second option is not recommended unless the workstation has a higher than average amount of RAM (2 GB or more).

(12)

Option 1 - Temporarily using Huge Mode:

The first option is to start GT-ISE/GT-POST from a command line and append "-huge" after the executable filename. To do this in Windows, create a command line by going to Start -> Run -> type

"cmd" and press the enter key, and then type "gtise -huge" and press the enter key. Please note that there is a single space between "gtise" and "-huge". Likewise for GT-POST the command is "gtpost -huge".

Depending on how your software is installed, you may need to change the directory to

$GTIHOME\vX.X.X\GTsuite\bin\win32 for gtise or gtpost to be recognized ($GTIHOME is usually C:\GTI).

Option 2 - Permanently using Huge Mode (program links and shortcuts):

The second option is to change the shortcuts to GT-ISE and GT-POST so they will always start in Huge Mode. The shortcut can be either a shortcut icon on the desktop or the shortcut link in the programs list.

To change the shortcut link in Windows go to Start -> Programs -> GTI Applications Group -> move the mouse pointer over GTise or GTpost to highlight -> right-click with the mouse -> select Properties -> in the Target box append " -huge" after gtise.exe or gtpost.exe. Then press the OK button and start the program. Again please note that there is a single space between gtise.exe and -huge.

Increasing the Huge Mode Memory Allocation:

If the Huge Mode setting is not large enough, the value for the maximum memory allocation can be increased in the file called product.cfg. Note that depending on your system configuration, you may need administrator rights to modify the product.cfg file. Also note that the product.cfg file is overwritten when a Build update is installed. To change the maximum memory allocation value:

• Browse to $GTIHOME\vX.X.X\GTsuite\bin

• Make a backup copy of the file called product.cfg and save with a different name

• Open product.cfg with a text editor

• Search for "[GUI-all huge]". On the following line is a variable *VM_OPTIONS for controlling the huge mode memory allocation. Change the number following Xmx in the VM_OPTIONS string in order to change the maximum memory allocation.

• The default is 1024 MB. A general recommendation is to increase in increments of 32 MB until GT-ISE/GT-POST is able to function correctly. Larger increments, for example 128 MB, may be used if the workstation has a higher than average amount of RAM (2 GB or more). Be cautious when increasing the value. If it is set near or above the total RAM of the computer, you may not be able to run other programs and/or the OS may freeze/crash when trying to run GT-ISE or GT- POST.

If the Huge Model Does Not Work for a Single Set of Results

If the huge mode does not allow results from a single model to be opened, this typically means that excessive amounts of data were requested by the user. This typically happens if plots and/or tables are requested for large DOE runs (1000's of cases). In this situation, try using the "File > Open (Skip Plots/Tables…) feature in GT-POST as a last resort to access the data. A detailed description of that feature will be displayed in a message window just before the file is opened.

(13)

CHAPTER 2: Viewing and Editing Plots in GT-POST

2.1 Basic Tree Operations

The various plot and table folders of each .gdx or .gu file contain a hierarchical tree, organized into four levels. The highest level of this tree is referred to as the case level. For a multi-case simulation, the .gdx pane will display only one case at a time. The user can switch between cases using the case selection field located at the top of the .gdx pane. Within each case, there will be one or more group levels. In a .gdx file this level will correspond to the parts or objects in the model for which plots have been requested. Within each group, there are one or more plots or tables containing one or more datasets.

The following figure shows a typical .gdx plot tree on the left and a table tree on the right demonstrating all of the levels of the tree. The plus (+) or minus (-) symbols next to each item allow the user to expand or contract each level.

The different folders of a .gdx or .gu file are used to organize specific types of plot or table output. These types are described below:

Plots In a .gdx file, this folder contains all of the "instantaneous" plots requested in the various parts or objects of the .gtm. Each plot in the tree is available for each case from the simulation (the case can be changed using the case selection field at the top of the .gdx file). In a .gu file, this folder contains any plots copied to (or created in) the .gu file by the user.

End of Run Plots This folder exists only in .gdx files and only when there are specific output plots requested by the user that require data from multiple cases.

The most common examples are acoustic result plots and turbocharger result plots that involve plotting data from all cases. The behavior of this folder is identical to the regular plots folder, except that the case selection field is not available.

CaseRLT This folder exists only in .gdx files and contains a tree of all assemblies, templates, and parts in the model. Each part contains one or more sub- folders that organize the RLT (result) variables for that part. Each RLT variable appears as a single plot in the tree with an associated dataset, and may be viewed or copied like regular plots. A "Case RLT" is the value of the specific RLT for the last cycle of each case, so each dataset will include one value per case for all of the cases in the run. The selected RLT variable will be plotted on the Y axis. The X-axis will be either the case number or a different RLT variable that represents the different cases.

(14)

TimeRLT This folder exists only in .gdx files and is visually identical to the CaseRLT folder, but each RLT variable in the tree represents the time dependent values of the RLT variable for the case shown in the selection field at the top of the .gdx file. The X-axis for each plot is either time or cycle number. This folder will be empty if Time RLT output has not been requested in the model.

Tables In a .gdx file, this folder contains all of the tables generated by the automatically by the simulation. Each table in the tree is available for each case from the simulation (the case can be changed using the case selection field at the top of the .gdx file). In a .gu file, this folder contains any tables copied to (or created in) the .gu file by the user.

The only folders that do not use the four-level tree described above are the CaseRLT and TimeRLT folders of a .gdx file. These folders use a similar structure but it has more levels to account for Assemblies, templates, parts, and RLT folders. These special folders are described in a separate section below.

2.1.1 Viewing Plots or Tables

There are two different modes of viewing plots, depending on whether the Automatically View Highlighted Tree Item ON/OFF button in the toolbar is turned on or off (This setting can also be set in Tools > Options > Plot/Table Viewing).

If Automatically View Highlighted Tree Item ON/OFF is "off", plots or tables must be requested with a view command. To generate plots or tables from the .gdx/.gu pane, right-click on the desired item in the tree and select View (alternatively, the user may highlight the relevant tree item and then press the

<F4> key).

If Automatically View Highlighted Tree Item ON/OFF is "on", plots or tables may be viewed by simply highlighting the relevant item in the tree. The resulting view will be automatically displayed in the live view tab.

Regardless of the Automatically View Highlighted Tree Item ON/OFF setting, any level of the tree may be selected, from a single dataset within a plot or table up to the whole tree. When a case or group level is selected, all of the selected children elements will be generated. Any level of the tree may be selected or deselected for viewing by clicking the checkbox to the left of the item. Only items that are selected will be generated for viewing. This is useful when, for example, the user wishes to plot three out of the five plot level items within a particular group.

2.1.2 Viewing Data

Raw data can be viewed by right-clicking on the desired data level item and selecting View Data (alternatively, the user may highlight the relevant data level item and then press the <F7> key). In addition, the view data dialog can be launched by right clicking on the parent plot in the view pane and selecting View Data >. A dialog box displays the data in array format as shown below. This data can be copied and pasted into another application. If the data is explicit (contained directly in the .gu file), the data can also be edited in this dialog box. The Export, View Even X-Increment Data, and Data Statistics options in the dialogue box are addressed in later sections.

(15)

2.1.3 CaseRLT and TimeRLT Folders in .gdx file

The CaseRLT and TimeRLT folders of the .gdx file use a slightly different tree structure than the other plot folders. The plot and data levels of the tree are similar, but instead of a single group level, there are multiple levels that represent the various assemblies, templates, and parts in the model. In addition, there are sub-folders within each part used to organize the RLT variables for that part. The trees for the CaseRLT and TimeRLT tree are visually identical. Only the content of the plots and datasets is different.

An RLT (result) variable is by definition any quantity that is calculated once per simulation cycle (i.e.

average pressure in a pipe). A "Case" RLT is the value of the specific RLT variable for the last cycle of the case (one value per case). "Time" RLT's are the time dependent values of the specific RLT variable within a single case.

The CaseRLT folder allows the user to view plots of any RLT variable versus another RLT representing the case. The RLT on the X-axis may literally be the case number, or can be any other RLT (ideally one that changes from case to case). This RLT may be selected in OutputSetup of the .gtm before running the model. If no RLT is selected, the X-axis will default to case number. To change the selected X-axis RLT in GT-POST, right-click anywhere in the tree and select Change X-Axis RLT variable. This will open the Plot File Properties dialog where the X Case RLT may be changed.

The TimeRLT folder allows the user to view any RLT variable versus time or period (cycle number) for a specific case (selected with the case selection field at the top of the .gdx file). The X-axis of the TimeRLT plots can be changed between "time" and "period" by selecting Change X-Axis RLT variable from the right click menu. This will open the Plot File Properties dialog where the X Time RLT may

(16)

be changed. Changes to the X-axis variable affect all plots in the tree, regardless of whether they have had specific properties changed locally (shown in green).

To use either of these folders, expand the tree until the desired RLT variable is found. By default, GT- POST is configured so that any RLT variable listed in the tree that does not contain data in the simulation results will be unchecked (this can be turned off in Tools / Options if desired). In general, the behavior in these trees is similar to the standard plot trees. Viewing plots or data are accomplished via the view or view data options. In the RLT trees, view data is also made available at the plot level because each plot can by definition contain only one dataset. Any portion of the RLT tree may be copied to a .gu file if desired.

In addition to the view and change x-axis variable options, the following right-click options are also available:

Change default unit Opens a dialog that allows user to change the default unit for the selected RLT variable. This will change the default display unit for that RLT so that any future view commands involving that RLT will be displayed using the specified unit.

Reset to Global Properties

This option will only be available for any tree element that has properties currently set that are different from the currently defined global properties (indicated by green text in the tree). If selected, this option resets all properties of element to the global properties.

Global Properties Opens a properties dialog that affects all plots or datasets in the tree that have not had a specific property change saved. This could be used to change the X-axis range for all plots in the tree, for example. Changes to global properties will not affect specific plots that have had property changes saved locally (indicated by green text in the tree).

Properties Opens the properties dialog for the selected plot or dataset. Any change made to properties is saved in memory for the GT-POST session, but will be lost when the .gdx file is closed. To permanently save plots with property changes, the plot should be copied to a user file (.gu). Any tree element that has properties set differently than the global properties will be indicated in the tree by green text.

2.2 Plot and Table Tabs (Live View vs. Snapshots)

When a new set of plots or tables is requested, they will be generated in the live view tab, which is always the tab furthest to the left. This tab is referred to as the "live view" tab because the plots shown in this tab are directly linked to the *.gdx or *.gu document. This means that any change to the selection state of children elements in the tree (checkboxes on or off) or any change to properties will be immediately visible in the live view plots, without required a new view command. The only time it should be necessary to request a new view (using F4 or right click > view) is when it is desirable to plot a different level of the tree.

Interactive features within GT-POST also allow certain properties to be changed directly in the live view tab (i.e. zooming in to a smaller X and Y range). These changes will be reflected in the *.gdx or *.gu tree. In other words, an interactive properties change in the live view tab and a "traditional" properties change made by editing the properties dialog in the tree are identical.

(17)

A snapshot tab is a copy of the live view tab at some instant in time. Snapshots are useful mainly to keep previous plot views for reference later in a GT-POST session without requiring another plot view command. A snapshot may be generated using the toolbar button, or by right clicking on the live view tab and selecting Make Snapshot. This action makes a copy of the tree that was originally viewed within temporary memory in GT-POST. Any implicit data (referring to .gdx, Ascii, or Excel files) will be converted to explicit data. This means that there is no link between the snapshot and the original *.gdx or

*.gu documents.

The same interactive features exist for snapshot tabs that exist for the live view tab, however the user should be aware that property modifications made using the interactive features are only affecting the tree in temporary memory and are not impacting any *.gdx or *.gu tree.

Each consecutive snapshot request generates a new snapshot tab in the view pane until the allowed maximum number of tabs is reached (set in Tools > Options). Once the maximum number is reached, the oldest unpinned snapshot tab will be removed with each subsequent view operation. Note that there is an option within Tools > Options to automatically generate a snapshot with each successive view command (replicates behavior of GT-POST v6.2 and earlier).

2.3 Interacting with Plots (Plot Window and Plot Control Toolbar)

When a new set of plots or tables is requested, the plot window will appear (if it is not already open) and the plots will be generated in the live view tab. After generating a plot tab, a toolbar exists above the plot view area that enables navigation between pages and some features that all interaction with the plots.

Each button in the toolbar is detailed below:

Undo/Redo Properties Change

These buttons allow for any properties modification to be reversed or re- applied. When a plot view is initially generated, these buttons will be disabled. Once a property modification has been made (i.e. zooming into a plot), the Undo button will become active. Pressing the Undo button will reverse the previous property change and enable the Redo button (which allows the change to be re-applied). Multiple properties modifications are stored so that Undo/Redo may be pressed multiple times consecutively.

Zoom In/Out (Range Zoom)

These buttons will zoom into or out of the active plot by adjusting the X and Y axis minimum and maximum values. Each zoom action changes the total range by roughly 25%. Note that this action forces the X and Y axis range properties to be set to "User" values.

Zoom to fit Data

This button sets X and Y axis minimum and maximum values to "auto", which effectively zooms the plot range to fit the data (and tries to find

"nice" numbers for the axis).

Select Mode

This button switches to Select Mode (from Zoom/Pan mode described below). In select mode, various elements of the plot may be selected directly via right click to make properties modifications (i.e. axis settings). The coordinate display feature described below also works only in select mode.

(18)

Zoom/Pan Mode

This button switches to Zoom/Pan Mode (from Select mode described above). In Zoom/Pan mode, the mouse may be used to zoom into a specific area of a plot by dragging a box around the exact area to be viewed. While dragging, tooltips will display the axis min and max values.

When the mouse cursor is near the edges of the plot, the cursor will change to a large yellow arrow indicating that pan operation is possible.

If the left mouse button is clicked when the cursor is showing the yellow arrow, the axis ranges will be adjusted to move the plot in the direction indicated by the arrow.

This mode may also be activated by holding down the <CTRL> key.

Coordinate Display Settings

This pull-down allows the user to select the desired options for the coordinate display feature (available only in Select Mode). The coordinate display feature shows the X and Y values for points in the plot close to the mouse cursor. The algorithm to determine the closest point considers X data first, and then among the closest X points considers Y values.

• All - The coordinate values will be displayed for the point closest to the mouse cursor from each curve (one coordinate pair per data set).

• Single - The coordinate values will be displayed only for the single point closest to the mouse cursor (one data set).

• Off - No coordinate values will be displayed.

Optical Zoom Options

These buttons control the relative size of the plot image. The Auto Fit zoom button is particularly useful for optimizing the size of the plot image with respect to the size of the Plot Window.

Snapshot

This button is active only for the Live View tab, and will generate a new tab that is a copy (snapshot) or the original live view tab. The new tab will be fully interactive just like the live view, but the snapshot tab is not tied in any way to the *.gdx or *.gu document. The data displayed and all plot and data properties are stored explicitly in temporary memory.

Pin (or Unpin) Tab

This button is only active for a snapshot tab, and allows the tab to be pinned or unpinned. Pinning a tab will keep the snapshot from being replaced if the maximum number of snapshot tabs has been reached and more snapshots are generated (common if the automatic snapshot option is turned ON). If a snapshot tab is not pinned, it will eventually be replaced by a future snapshot as more snapshots are generated.

Add Note to Plot

This button is only active when a single 2D plot has been selected, and allows a text note to be added to the plot. The text is added as a CXY data set, with C representing the display text and (X,Y) is the location of the text on the plot. The data set properties control the appearance of the text (rotation angle, font, coordinate system). This functionality may also be accessed via right click menu at plot level from the tree.

(19)

Page Navigation Buttons

Each tab may consist of multiple pages with one or more plots on each page. The page navigation buttons provided allow the user to move between these pages. The pulldown allows a direct change to a specific page number, while the buttons allow for first, previous, next, and last page. The <Page Up> and <Page Down> keys also function for previous and next page navigation.

Plot Window Mode Button

This button controls the "mode" of the Plot Window. By default, the plot window will be Internal. This implies that it will be treated as any other file window in GT-POST (i.e. just like *.gdx and *.gu files) in terms of tiling, minimizing/maximizing, etc. The Plot Window may optionally be switched to External/Always-On-Top mode. This treats the Plot Window as a separate window from GT-POST, and forces it to be always-on-top.

In this mode, the Plot Window may be dragged outside of the bounds of GT-POST. This is especially useful for users with multiple monitors, as they can have GT-POST open in one monitor with their *.gdx file maximized (in RLT Contour View, for instance), and the Plot Window open in the second monitor. Enabling this External/Always-On-Top mode also allows the AutoPlot feature (see section 2.10 below) to be enabled, allowing the user to quickly and easily generate plots from the plot tree without the Plot Window being hidden underneath the maximized *.gdx file.

2.3.1 Interacting with 3-Dimensional Plots

Three-Dimensional plots (3D Contour and 3D Spatial plots) will have additional interactive controls that are not available within 2D plots when a single 3D plot is the only plot on the active page (page layouts with multiple plots per page will result in "static" 3d plots). The 3D plot can be rotated, zoomed in or out, or panned via the mouse. To use these interactive features, the user must click and hold the appropriate mouse button while in the plot window and then drag the mouse.

Spin: left mouse button

Spin on axis: <CTRL> + left mouse button Zoom: middle mouse button/wheel

Pan: <Shift> + left mouse button

The above actions may also be performed using a graphical controller that will appear in the upper right corner of the plot when the mouse cursor is moved near the corner (shown below).

(20)

In addition, various standard orientations may be selected by right clicking anywhere on the plot. The resulting menu options are shown below:

The final option in the above menu allows for 3D plots to be sectioned. Selecting this option brings up sectioning controls that allow a sectioning plane to be selected and dynamically moved on the plot.

(21)

2.3.2 Animated Plots

Any plot containing multiple data sets may be viewed as an animation rather than as a static plot. A plot may be specified as an animation plot using the Animation checkbox within the plot properties. In a plot animation, each frame is viewed one at a time at a specific frequency such that an animation is created.

Each frame of the animation may be made up of one or more datasets within the plot. Each dataset is assigned to a specific frame number of the animation using the Animation Frame Number property.

When an animated plot is viewed, some additional interactive controls will be available in the plot toolbar for controlling the animation (shown in the red box below). These include the options to Loop the animation, Stop, Play/Pause, change the Speed that the animation is viewed, and to Create a Video which will save the animated plot as a video/movie in .mov format. Note that the speed slider controls the frames per second (fps) of the saved animation movie file.

(22)

2.4 Viewing Part Output Plots and RLTs from the Map

Both instantaneous and Case/Time RLT plots may be accessed directly from the map simply by selecting a desired part, which will open a dialog showing all plots and RLTs related to the part. This dialog can either be docked to the map (docked on bottom as shown below) or can be viewed as a floating dialog.

The toggle to change between docked and floating modes is in the upper right-hand corner of the dialog.

Right-clicking on a part will open a menu allowing the selection of all available Plots. There is an option in Tools -> Options… -> Map Options which allows the user to fade the parts on the map which do not have instantaneous plot available. This option is also available from the toolbar by clicking the button.

2.5 Tile for Plotting View

Tile for Plotting View automatically controls window sizes and positions for convenience when working primarily with plot trees and the plot window. This view closely duplicates GT-POST behavior from previous versions. After opening a .gdx or .gu file in GT-POST, this view can be entered by selecting the

(23)

"Tile for Plotting" button in the upper left portion of the open .gdx file or by selecting the identical button in the GT-POST toolbar.

Tile for Plotting View provides the capability to view plots and tables and to create and modify user plot files. The user-interface for Tile for Plotting is shown below. Each open .gdx or .gu file is shown in a pane along the left side of the window. These files are organized into different folders (Plots, Tables, etc.). The pane of the currently selected file is highlighted. Plots or tables that are viewed are shown in the Live View Tab. The plots or tables in the Live View tab may be saved to a Snapshot tab so that they may be referenced later without requiring another view command. This may be useful to compare plots (flipping back and forth between tabs). Both the live view and snapshot tabs have interactive features (zooming, etc.). The main difference is that the live view is directly linked to the *.gdx or *.gu file. A snapshot has no link to any *.gdx or *.gu (it is explicit data in short term memory). This means that if a simulation is re-run and results change, a previously taken snapshot will still reflect the old results. An option exists in Tools > Options that allows for an automatic snapshot to be taken with each successive view command. This option emulates GT-POST behavior from versions 6.2 and earlier.

2.6 User Plot and Table files (GU files)

User plot files (.gu files) must be used anytime the user wishes to edit and save any plot or table found in a .gdx file, or whenever the user wishes to create any new plots or tables (e.g. using plot creation macros).

It is also used to compare data from different simulations or to compare simulation data to experimental

(24)

data. It also allows the user to create a "template" for viewing the simulation results that are most important. The behavior of a .gu file is nearly identical to that of a .gdx file, except that there are additional options available for creating or manipulating plots and tables that are not available for .gdx files. A .gu file can be created by selecting the Create New GU File button on the toolbar or by selecting New GU under the File menu. A .gu file can also be created using any of the Plot or Table Creation Macros.

The .gu pane is very similar to the .gdx pane with one exception. The case level is assigned the name

"New Case" by default and there is no case selection field. This is because a user plot file does not inherently have multiple cases (the plots and underlying data sets within a .gu file may be derived from multiple cases and/or multiple simulations).

2.6.1 Drag and Drop between GT-POST trees

One method of adding items to a user file is using mouse "drag and drop" operations. This can be used to transfer data, plots, groups and cases from .gdx trees to .gu trees, from one .gu tree to another, or between different locations in a single .gu tree. The drag and drop operation is executed by selecting an entity (data set, plot, etc.) and dragging it to the desired location in the .gu tree.

When dragging and dropping a plot data set from a .gdx file to a .gu file or between plots within a .gu file, the units of the data being dragged must match the units of either the Y1 or Y2 axis of the plot where it is to be dropped. If the units do not match the Y1 axis, and there is not yet a Y2 axis defined for the plot, the user will be given the option of assigning the dataset unit to the Y2 axis. If desired, GT-POST can be configured (using Tools / Options) to automatically assign the Y2 axis in this situation without prompting the user. If the dataset being dragged into a plot is assigned "No Unit", then the option is provided to convert the dataset units to Y1/Y2 axis units.

2.6.2 Adding New Data

Often, it is desirable to add external data (not generated by GT-SUITE) to existing plots in a .gu file. For instance, experimental measurements are often compared with simulation results to validate a model.

Data can be added to a single plot or table using the Add Data selection from the right-click menu. The dialog for adding data to an XY scatter plot is shown below (the dialog will present different options depending on the plot or table type). The data type must be selected from a list of the allowable data types for that plot or table type (in this example, only XY data is allowed so only one selection is shown).

The second option to select is the source of the data. The data may be typed or pasted in (Explicit) or may be imported from Excel or Ascii.

(25)

The Excel or Ascii options may be used to import data directly from Excel spreadsheet or Ascii text file.

The imported data may be either explicit (contained in .gu file) or implicit (points to data in the external file). If either of these options is selected, the remaining dialog screens are identical to the tool used to import multiple Excel or Ascii data sets (covered in a later section). If the Explicit option is chosen, the remaining two screens shown below are used to define a dataset name and units and to enter (or paste in) the data. After the data has been entered and the OK button selected, the data will be added as a new dataset within the original plot. The new data set will be "explicit", meaning that it is not tied to any GT- SUITE simulation results or to any external file.

2.6.3 Right-Click Menu Options

Most of the options available in the right click menu within the GT-POST tree are discussed in detail elsewhere in this manual. This section covers only those items that are not covered elsewhere.

Add ... Adds a new group, plot, table, or data set to the .gu file. Each item that may be added at a specific level will have its own menu item. For

(26)

example, at the Group level in a plot tree, it is possible to Add Group or Add Plot.

Expand All ... Available only at Case levels to expand all children groups and at the group level to expand all children plots/tables. For example, selecting this option at the group level will expand all children plots under that group so that all datasets are visible.

Collapse All ... Available only at Case levels to collapse all children groups and at the group level to collapse all children plots/tables. For example, selecting this option at the group level will collapse all children plots under that group so that no datasets are visible.

Switch Y1 / Y2 Axis Available at the plot level, switches the axis labels, settings, and units from Y1 to Y2 and vice versa. Also moves all datasets previously assigned to Y1 axis to the Y2 axis, and moves all datasets previously assigned to Y2 axis to the Y1 axis.

Move Y1 / Y2 Available at the dataset level, switches the selected dataset between the Y1-axis and the Y2-axis, assuming this operation is allowed. A dataset may only be moved to a different axis if the unit category of the dataset and the destination axis match. If the Y2 axis has not yet been defined (no datasets assigned to Y2), selecting this option will define the Y2 axis with the units of the selected dataset.

Assign Units Opens a dialog that allows user to assign a unit to a plot and all children datasets of that plot. This option is only available if the original plot and all children datasets are assigned "no unit". This is useful for plots that come from controls components where the unit of the control signal is not generally known (and is therefore assigned "no unit").

2.7 Plot Creation Macros

A typical .gdx file contains many plots that are created by the solver, either automatically or at the user's request. These plots may be copied to a user .gu file and customized, however often it is necessary to create customized plots to combine different datasets. Several plot creation macros are available in the GT-POST toolbar to accomplish this task. The following plot macros are available from the toolbar (or from the Macros menu) when a .gdx file is active. The plots that result from these macros are normally saved in user .gu files using the Document Name and User Group pull down menus at the bottom of each window, but can optionally be displayed without creating any .gu tree entries by setting the Document name to "None".

2.7.1 Plot Case Combine/Repeat

For any subset of the plot tree in the .gdx file, the data for an arbitrary selection of cases may be combined into one set of plots or repeated for each selected case. In the macro dialog, the window on the left is used to select the subset of the plot tree, and the window on the right is used to select the affected cases. Below the right window there are radio buttons to select whether multiple cases are combined or repeated. If the cases will be combined, a checkbox is available that allows a 3-D waterfall (carpet) plot

(27)

to be created with case number as the additional Z-axis. In the example below, the Temperature plot within the Cylinder-01 group will be combined for the four selected cases (6000, 5000, 4000, 3000 rpm).

The resulting plot is shown below.

(28)

2.7.2 Plot Data Combine

This macro allows any datasets that share a common unit category to be combined into a single plot. In the macro dialog, the left window is used to select the "source dataset". This is used to filter all of the datasets in the tree so that only those datasets with a matching unit are shown in the center window. This filtered list can be further filtered by selecting either "variable" or "template" from the pull-down above the center window. These options will only show datasets with the same unit AND the same variable (i.e.

pressure) or the same template (i.e. Pipe), respectively. The desired datasets for the plot are selected in the center window and the affected cases are selected in the right window. Below the right window there are radio buttons to select whether multiple cases are combined into one plot or repeated in multiple plots.

In addition, there is a field where the new plot name may be set if desired. In the example below, the Pressure plot from the four EngCylinder parts are combined to show the cylinder-to-cylinder variation in pressure at 6000rpm.

(29)

2.7.3 RLT Plots

This macro can be used to create several different types of plots involving RLT variables. Plots can be created from both Case RLTs and Time RLTs. For Case RLTs, four plot types are allowed including XY Scatter, 2D Contour, 3D Contour, and Bar. For Time RLTs, only XY Scatter is allowed.

(30)

For Case RLT plots:

The XY Scatter Plot is used to create XY plots of "case" RLT values (values of RLT variables from the final cycle or RLT interval of each case). An RLT variable is specified for the X-axis and the Y1 axis for each plot. If the same X-axis variable is used for each plot, it may be entered only once in the "Plot1"

row or the table. Additional Y variables may be defined in columns Y2+ as long as there is a maximum of two different unit categories used (for Y1 and Y2 axis in the resulting plot). In the example below, several EngineCrankTrain RLT's are plotted vs. engine speed.

Parameters defined in Case Setup are also stored as RLT variables and are available for Case RLT plots.

Parameters may be requested in any letter-case (case-insensitive), but a "+" must be appended to the end of the name. For example, the parameter "[RPM]" may be requested by "RPM+" or "rpm+".

(31)

The Bar Graph is very similar to the XY Scatter plot however the difference is that the data is in bar form instead of line form. Please note there can only be one Y axis (one unit category) for bar graphs. An example plot is shown below where the average wall temperature of four exhaust runners is plotted vs.

engine speed.

The 2D Contour Plot is used to create a 2D contour by defining an RLT variable for the X, Y, and Z axes. The data is triangulated onto a surface and plotted with the Z coordinate color contoured.

Additionally, it is possible to plot contour lines, in either color representing the contours, or as numbered lines. An example of brake power vs. torque and engine speed is plotted below.

The 3D Contour Plot is very similar to the 2D contour plot, except that the plot is constructed in 3D space instead of 2D. The data is triangulated onto a surface and plotted with the Z coordinate color contoured. An example is plotted below with the same data set as in the above 2D contour plot.

(32)

For Time RLT plots:

Time RLTs can be plotted as an XY Scatter plot of "time" RLT values (values of RLT variables stored at a user defined interval for a given case). One or multiple cases of Time RLTs can be plotted together with the RLT variable for the X-axis and RLT variable(s) for the Y-axis. This option will only be active if time RLT's have been saved for the simulation. An example Time RLT plot is shown below where the wall temperature of the exhaust runner #1 is plotted vs. time for multiple cases in the same plot.

(33)

Useful Features for All RLT Macro plots:

Restore Button: For all plots, there is a Restore button at the top right of the window, which can be used to recall the values that were entered the last time the RLT Plots macro was used (within the same GT- POST session). An example of using the Restore button is displayed below.

Before hitting the Restore button After hitting the Restore button

Cursor Direction: For all plots, there is a Cursor Direction dropdown at the top right of the window, which can be used to set the direction for the next cell. The default option is set to "DOWN", meaning the next cell will be down from the previously entered cell. This option is handy when the user is creating many different plots. By setting the option to "RIGHT", the pointer will move to the cell to the right of the previously entered cell. This option is handy when the user wants to define many Y datasets within a given plot.

(34)

Constraints: For all plots, the user may choose to "filter" the dataset and report values which meet a certain criteria. In order to create a constraint, the user must select an RLT. Each plot is only allowed one constraint RLT, but multiple bands of the RLT can be used. As an example, suppose the user has data over an engine speed range from 500-6000rpm, but only the 2000-3000rpm and 5000-6000rpm bands are of interest. In this case, the user could create a constraint on the engine speed parameter, and set the min.

and max. constraint values as shown in the figure below. This effectively filters the data in the plot to be within the range of the constraint. A unique dataset is created for each constraint min/max and each Y dataset. So if there were 3 Y datasets in a plot and two constraints, there would be a total of 6 datasets in the plot.

Dataset Labeling: For all plots, the user can name each dataset through the Output Options dialog shown below.

(35)

Case RLT Output Options Time RLT Output Options

By default, the Case RLT plot displays the dataset as: Part Name : Y RLT Name : Constraint RLT, Min/Max (if constraint exists). The user can create a unique label for each dataset by selecting the appropriate label option or appending a user defined label. An example is shown below where the Brake Torque and Brake Power RLT of the "Engine" part are plotted in the same plot.

For Time RLTs, the "Use Short Case Legend" option is on by default, as well as the constraint RLT, min/max.

(36)

2.7.4 Create Contours of Instantaneous Data

This macro allows the user to display a contour plot combining multiple cases of any instantaneous plot data from the "Plots" tree. Optionally, the contour can display the results of an FFT (Fast Fourier Transform) of each dataset. If the "Perform FFT" checkbox is turned on, the resulting plot will consist of frequency or order on the X-axis, any RLT on the Y-axis, and the contours of the FFT results of a single dataset displayed in the plot. Without the FFT, the plot will consist of time or angle on the X-axis, any RLT on the Y-axis, and the selected instantaneous plot variable plotted in contours.

In the macro dialog, the user can select one "instantaneous" dataset from the left window, multiple cases in the center window, and one RLT for the Y-axis in the right window. The Perform FFT checkbox is below the left window. If this is selected, the X axis type and maximum X axis range must also be specified. In the example below, the pressure in EngCylinder part "cyl1" will be plotted vs. crank angle and Engine speed.

2.7.5 Histogram Creation Wizard

This macro allows the user to create a histogram dataset for one or multiple cases. Three types of histograms currently exist:

1. 1D Discrete Histogram - this option can be used for creating a 1-dimensional histogram of discrete variables or when the user wants to display the data in discrete "bins" in bar graph form.

(37)

2. 1D Continuous Histogram - this option can be used for creating a 1-dimensional histogram of continuous variables

4

3. 2D Contour Histogram - this option can be used for creating a 2-dimensional histogram of continuous variables

(38)

The steps to create a histogram are as shown below. The wizard guides the user through the steps of building the appropriate histogram. The first step is to select the histogram type from the three options discussed above.

Within each type of histograms, there are four residency type options. This allows the user to track history as a function of time, percentage of time, a user-defined variable (eg. consumed fuel), and percentage of the user-defined variable.

When "Time" or "Time Fraction" are chosen as the residency option, 1 dataset (X-variable) must be specified for the 1D Histogram types, and 2 datasets (X-variable and Y-variable) must be chosen for the 2D Contour Histogram type.

(39)

When "User-Defined Variable" or "User-Defined Variable Fraction" are chosen as the residency option, 2 datasets (X-variable and User variable) must be specified for the 1D Histogram Type, and 3 datasets (X- variable, Y-variable, and the User variable) must be chosen for the 2D Histogram type.

Histograms can be created either from .gdx or .gu files and can be from either Time RLTs or Instantaneous Plots.

In the Source Data pane, the user can select (and drag and drop) into the Math Dataset tree.

(40)

In this dialog, the user would specify the number of bins, or alternatively the bin width and the range over which to create the histogram.

For the User-defined variable dataset, the user has the option to assign a unit and integrate it before it gets added to the histogram. This would be useful if the user-defined dataset has a rate unit, such as fuel consumption rate.

2.8 Table Creation Macros

Two table creation macros are also available in the GT-POST toolbar when a .gdx file is active.

The plots that result from these macros are normally placed in user .gu files using the Document

Name and User Group pull down menus at the bottom of each window, but can optionally be

displayed without creating any .gu tree entries by setting the Document name to "None".

2.8.1 Table Case Combine/Repeat

For any subset of the table tree in the .gdx file, the data for an arbitrary selection of cases may be combined into one set of tables or repeated for each selected case. In the macro dialog, the window on the left is used to select the subset of the table tree, and the window on the right is used to select the affected cases. Below the right window there are radio buttons to select whether multiple cases are combined or repeated. In the example below, the Engine Performance Predictions for the three selected cases (6000, 5000, and 4000 rpm) are combined into one table.

2.8.2 RLT Tables

(41)

The RLT Tables macro can be used to create two different types of tables involving RLT variables. In the upper left corner of the macro dialog, the user must specify the type of RLT table to be created using the Table Type pull-down menu. The different table types are defined as follows:

Case Sweep is used to create tables of "case" RLT values (values of RLT variables from the final cycle of each case). Each dataset in the table will consist of a single selected RLT variable, and the results of all cases from the simulation will be displayed. In the example below, a table is created included several RLT variables from the 'EngineCrankTrain'.

The table resulting from the above dialog is shown below.

GT-POST User's Manual GT-SUITE

GT-SUITE