0% found this document useful (0 votes)

2 views

3 Data Explorer

Uploaded by

Giovanni Andrade

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

2 views

3 Data Explorer

Uploaded by

Giovanni Andrade

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 178

October 2013

AT2651E, Rev. 07

User´s Guide

DATA EXPLORER
AVL CONCERTO™ 2014
v4.6
Copyright 2013 AVL List GmbH, Graz - Austria

The contents of this document may not be reproduced in any form or communicated to any third party without the
prior written consent of AVL. While every effort is made to ensure its correctness, AVL assumes no responsibility
neither for errors and omissions which may occur in this document nor for damage caused by them.
All mentioned trademarks or registered trademarks are owned by their respective owners.

All rights reserved.

Table of Contents 3

Table of Contents

1 Data Explorer .................................................................................................................... 7

1.1 Data Model ............................................................................................................................... 7
1.1.1 Data Source ........................................................................................................................ 7
1.1.2 Files and Tests.................................................................................................................... 7
1.1.3 Base Types ......................................................................................................................... 8
1.1.4 Data Keys ........................................................................................................................... 8
1.1.5 Measurements .................................................................................................................... 9
1.1.6 Channels and Datasets....................................................................................................... 9
1.1.7 Dataset Names ................................................................................................................. 10
1.1.8 Formula Channels............................................................................................................. 10

1.2 Data Explorer Window............................................................................................................ 11

1.2.1 My Computer / Network View ........................................................................................... 11
1.2.2 Data Source View ............................................................................................................. 12
1.2.3 Toolbar.............................................................................................................................. 14
1.2.3.1 Filtering, Properties and View Operations ........................................................ 14
1.2.3.2 File Operations ................................................................................................. 14
1.2.4 Address Bar ...................................................................................................................... 15
1.2.5 Path and Conditions ......................................................................................................... 15
1.2.6 Icons ................................................................................................................................. 15
1.2.7 Explorer Bar ...................................................................................................................... 16
1.2.8 Test List ............................................................................................................................ 17
1.2.9 Context Menus.................................................................................................................. 17
1.2.9.1 My Computer / Network View ........................................................................... 17
1.2.9.2 Data Source View ............................................................................................. 18
1.2.9.3 Data Environment ............................................................................................. 26
1.2.10 Data Preview..................................................................................................................... 26
1.2.10.1 Channel Properties .......................................................................................... 26
1.3 File Formats............................................................................................................................ 32
1.3.1 Supported Formats ........................................................................................................... 32
1.3.1.1 Generic ASCII File (auto-detect format) .......................................................... 35
1.3.1.2 Multi ASCII File Types ...................................................................................... 36
1.3.1.3 AVL IFile .......................................................................................................... 37
1.3.2 Generic ASCII and Binary Formats................................................................................... 40
1.3.3 Dictionaries ....................................................................................................................... 40
1.3.4 Customer-specific Formats ............................................................................................... 41
1.3.5 ZIP Format ........................................................................................................................ 41
1.3.6 Conversion Programs ....................................................................................................... 41
1.3.7 User-specific File Access.................................................................................................. 42

1.4 Working with Data Files/Tests ................................................................................................ 43

1.4.1 Open ................................................................................................................................. 43
1.4.2 File Alias ........................................................................................................................... 44
1.4.3 Handling Measurements and Series................................................................................. 45
1.4.3.1 Measurements .................................................................................................. 45
1.4.3.2 Submeasurements............................................................................................ 45
1.4.3.3 Test Series........................................................................................................ 46
1.4.3.4 Series of Measurements................................................................................... 46
1.4.3.5 Opening Tests Containing Several Measurements of the Same Type............. 47

Data Explorer — User’s Guide

4 Table of Contents

1.4.4 Further Actions ..................................................................................................................47

1.4.4.1 Close .................................................................................................................47
1.4.4.2 Replace .............................................................................................................47
1.4.4.3 Comparing Files ................................................................................................47
1.4.4.4 Load Data Dialog ..............................................................................................48
1.5 Filtering and Searching........................................................................................................... 48
1.5.1 Filter Conditions ...............................................................................................................48
1.5.1.1 Text Filters ........................................................................................................49
1.5.2 Test Attributes in File System Data Sources.....................................................................50
1.5.3 Filtering by Attribute ..........................................................................................................51
1.5.4 Finding Tests on an ASAM Host .......................................................................................52
1.5.5 Extended Queries ............................................................................................................56
1.5.5.1 Selecting Extended Queries in the User Interface ............................................56
1.5.5.2 Syntax for Extended Query in the Query File....................................................57
1.5.6 Searching by Data Contents .............................................................................................58
1.5.6.1 Advanced Filter Dialog ......................................................................................68
1.5.6.2 Creating a ComposerFile from the Results of a Search Query in Data Explorer
70
1.5.6.3 Context Menu (Search Results Window) ..........................................................71
1.5.7 User Variables in Filter Conditions ....................................................................................71

1.6 Adjusting the Data Environment ............................................................................................. 73

1.6.1 Data Environment File (DXV) ............................................................................................73
1.6.2 Temporary Data Source ....................................................................................................74
1.6.3 Creating new Data Sources ..............................................................................................74
1.6.4 Organizing Data Sources ..................................................................................................76
1.6.5 User Variables...................................................................................................................76
1.6.6 Path Definitions .................................................................................................................76
1.6.6.1 Using Path Wildcards........................................................................................76
1.6.6.2 Multiple Paths....................................................................................................78
1.6.6.3 Defining Company-wide Paths .........................................................................79
1.6.7 DXV File Settings .............................................................................................................79
1.6.7.1 Settings for All File Formats ..............................................................................80
1.6.7.2 ASAM ODS Data Base .....................................................................................83
1.6.7.3 ATF Data Source ..............................................................................................83
1.6.7.4 Horiba VETS Export File ...................................................................................84
1.6.7.5 DIGALOG Data File ..........................................................................................84
1.6.7.6 IFile ...................................................................................................................84
1.6.7.7 MATLAB MAT File ............................................................................................85
1.6.7.8 MDF File............................................................................................................85
1.6.7.9 Multi ASCII File Types.......................................................................................88
1.6.7.10 PUMA Recorder File .........................................................................................88
1.6.7.11 RedLine (ACAP/CAS) File ................................................................................88
1.6.7.12 Script-based Tests ............................................................................................89
1.6.7.13 VAX-based PUMA TRR File .............................................................................89
1.6.8 Date Displays ....................................................................................................................90
1.6.8.1 ASAM-AODS.....................................................................................................90
1.6.8.2 File System .......................................................................................................90
1.6.9 Data Source Templates ....................................................................................................91

1.7 Data Source Properties .......................................................................................................... 92

1.7.1 Data Source Properties - Format ......................................................................................92
1.7.2 Data Source Properties - Data Source..............................................................................94
1.7.2.1 Data Source Property Page for ASAM-ODS Servers .......................................96
1.7.3 Data Source Properties - Formulae ..................................................................................97

Data Explorer — User’s Guide

Table of Contents 5

1.7.4 Data Source Properties - Advanced ................................................................................. 98

1.7.5 Data Source Properties - Context ................................................................................... 100

1.8 Accessing ASAM-ODS Data ................................................................................................ 103

1.8.1 Creating an ASAM-ODS Data Source ............................................................................ 103
1.8.2 Advanced ASAM Properties ........................................................................................... 106
1.8.2.1 ASAM Properties - Server .............................................................................. 106
1.8.2.2 ASAM Properties - Tests ............................................................................... 107
1.8.2.3 ASAM Properties - Measurements ................................................................. 108
1.8.2.4 ASAM Properties - Channels.......................................................................... 110
1.8.2.5 ASAM Properties - Units................................................................................. 111
1.8.3 DXV File Settings............................................................................................................ 111
1.8.4 Reference Attributes ...................................................................................................... 114
1.8.4.1 Concatenating Multiple Resolved Attributes ................................................... 118
1.8.4.2 Reference Attributes with Filter Conditions..................................................... 119
1.8.5 Creating and Restructuring Tests ................................................................................... 120
1.8.6 Saving ASAM ODS Data ................................................................................................ 124
1.8.7 Copying Tests into an ASAM Database.......................................................................... 125
1.8.8 Storing to Santorin with Channel Name Translation ....................................................... 126

1.9 Special Features for Accessing Data ................................................................................... 129

1.9.1 Splitting Data into Artificial Measurements ..................................................................... 129
1.9.1.1 Measurement Splitting via Channel Browser.................................................. 130
1.9.1.2 Measurement Splitting via Data Explorer ....................................................... 132
1.9.2 Working with Long Recorder Data .................................................................................. 134
1.9.2.1 Data Management by Blockwise Loading....................................................... 134
1.9.2.2 Adaptive Loading ............................................................................................ 135
1.9.2.3 Loading Constant Segments .......................................................................... 138
1.9.3 Merging Measurement Types ......................................................................................... 139
1.9.4 Translating Channel Names and Converting Units ........................................................ 140
1.9.5 Temporary Channels ...................................................................................................... 143
1.9.6 Alias Channel Names ..................................................................................................... 144
1.9.7 Hiding Formulas that are Not to Be Calculated............................................................... 145
1.9.7.1 Formula Dependency File............................................................................... 145
1.9.8 Load Data Macros (Repeated Points Filter).................................................................... 146
1.9.9 Embedded Data .............................................................................................................. 147
1.9.9.1 ASAM-ODS Data External References (Attachments) ................................... 147
1.9.9.2 Embedding Data from Other Data Sources .................................................... 148
1.9.10 Reading ASCII and Binary Files with Descriptor (Syntax) .............................................. 151
1.9.10.1 Identities ......................................................................................................... 152
1.9.10.2 Descriptor File Structure ................................................................................. 152
1.9.10.3 Examples ........................................................................................................ 159
1.9.11 Scripting Data Source ..................................................................................................... 162
1.9.11.1 Defining a Scripting Data Source.................................................................... 162
1.9.11.2 General Structure of a Script .......................................................................... 162
1.9.11.3 Script for Test List........................................................................................... 163
1.9.11.4 Script for Test Attributes ................................................................................. 165
1.9.11.5 Script for Data Keys/Measurements ............................................................... 165
1.9.11.6 Script for Measurement Channels .................................................................. 168
1.9.11.7 Script for Measurement Data.......................................................................... 170
Index............................................................................................................................................................ 171

Data Explorer — User’s Guide

6 Table of Contents

Data Explorer — User’s Guide

Data Explorer 7

1 Data Explorer
Data Explorer enables you to access your result data. The entire CONCERTO
data environment is presented in a clear structure.

1.1 Data Model

1.1.1 Data Source

Data Explorer administrates various kinds of data sources. These may be folders
containing data files, or also data servers (typically ASAM-ODS Data Base).
Each data source may only contain files of one CONCERTO file format and
display the data of one or more folders/drives or of one data server (database). If
a data source also contains files with another format (PDF, JPG, etc.), these are
opened via the relevant application. Data sources are a kind of pointer and work
similarly to shortlinks created for network drives without the user having to know
the actual position of the data within the network.
The advantage for the user is that there is no longer any need to navigate
through complex folder trees to reach certain subfolders. Apart from that, it is no
longer relevant whether users know what data format they are dealing with.
Accordingly, navigating through the data is always handled very much the same
way, even if different data formats are involved.
You can set up as many data sources as you like and also label them as you
wish.
Data Explorer saves the information about all data sources needed for later
sessions in special files, so-called DXV Files (e.g. concerto.dxv, demodata.dxv,
etc.). A DXV file corresponds to a data environment and contains the settings for
all data sources available on one common pane of the Explorer bar.
CONCERTO enables you to have more than one data environment (DXV file)
open at the same time.
Basically, Data Explorer distinguishes between two categories of data sources:
Permanent data sources (which are loaded via DXV files)
Temporary data sources, which are created automatically when a file for
which no data source yet exists is opened straight via the My Computer /
Network view.

The temporary data source can be converted to a permanent data source

via its context menu by moving it to one of the existing data environments
(DXV files) (see Creating new Data Sources on page 74).

1.1.2 Files and Tests

A data source can provide access to physical data files and databases. The
objects that correspond to data files in a database are called Tests.
In Data Explorer, the files in a file system and the tests saved in an ASAM data-
base are handled in the same way. The terms 'file' and 'test' are therefore inter-
changeable.
In order to be able to work with the contents of files/tests, these have to be
opened (see Open on page 43).
Alias Names The data source defines a default alias name, which is used by Data Explorer to
generate a file alias whenever a file or test is loaded. This alias is a logical file
name or handle used to represent the test. Referencing this alias, rather than the
actual file it represents, enables you to keep all your layout definitions test-inde-
pendent.

Data Explorer — User’s Guide

8 Data Explorer

1.1.3 Base Types

Engine test data is created by a variety of measurement devices. One way to
categorize it is by using the Base Type.
Logpoint Data Data which is logged step by step in single measurements. A record is stored for
every logged point (i.e. one measurement point per channel). This is data
derived from steady-state measurements on an engine test bed. An indicating
system can produce logpoint data when significant result values from an indi-
cating measurement (such as IMEP) are logged to an ASCII file. In integrated
systems these result values tend to be transferred directly to the test bed
system, merged into the data pool and thus stored as logpoint data together with
the other test bed data.
Time Based Data Channels continuously sampled over a period of time (e.g. recorder data on tran-
sient test beds or post-mortem data).
Crank Angle Data Data sampled by an indicating system on the crank angle. Often multiple engine
cycles are acquired.
Cycle Based Data Results from crank angle based measurements. A set of results values is stored
for every engine cycle.
Static Data Information recorded once per test (e.g. engine parameters, operating condi-
tions, cell information etc.).

1.1.4 Data Keys

Typical data files/tests contain different types of data, either because of different
base types, or due to some other logical reason. Data Explorer presents chan-
nels of the same type under a common data key.
Every file type can contain different data keys. An AVL IFile, for instance, can
contain crank angle data, time-based data, RTP data, general parameters,
system information, etc.
A PUMA Open test usually consists of start dialog information, engine data,
measurement data and end dialog information. All these data types have
different data keys which correspond to the storage keys set in PUMA Open.
Data of the same base type can also be stored under different data keys if it
does not belong together. A PUMA Open test can, for example, contain an
engine map and a separate full-load curve. Both data keys include logpoint data
and can also contain the same channels. But because they were acquired inde-
pendently, they were stored under different storage keys and are therefore
displayed as different data keys.
In addition to the data keys actually available in the file there are also artificial
data keys which are created by Data Explorer itself to encapsulate formula chan-
nels.

Data Explorer — User’s Guide

Data Explorer 9

1.1.5 Measurements
The ASAM data model does not use data keys to categorize the data belonging
to a test. Instead, it is assumed that tests are composed of individual measure-
ments. By this, measurements like e.g. Recorder measurements on the test bed
are meant. In steady-state measurement procedures, however, the individual
measurement points (which are recorded in steady-state measurements on the
test bed) form curves and/or maps, the entirety of which represent an ASAM
measurement. The storage key used in the AVL PUMA Open system is stored
as an attribute of the ASAM measurement. CONCERTO uses this attribute as a
data key.
The measurements within a test are often of different type and therefore corre-
spond to different data keys. However, it might happen e.g. that the same
Recorder (same storage key) is started multiple times. In this case, several
ASAM measurements are saved under the same data key. In order to ensure a
consistent structure in such cases, Data Explorer, for ASAM tests, always
displays a measurement hierarchy under each data key in the navigator bar,
even if a key only includes one measurement.
PUMA also stores descriptive information (engine parameters, user comments)
under separate storage keys. This data also appears as measurements (pseudo
measurements) under the relevant data key in CONCERTO.
Comparison of the individual Recorder runs is of special interest for Recorders
that have been started multiple times. It is not only possible to open/load a given
test, but also a single measurement. A separate file alias is assigned to this
measurement which allows the normal file comparison feature to be used for
comparative representation. If a file is opened and a data key in it contains
several measurements, the measurement to be displayed can be selected
directly via the slide bar on the status bar.

1.1.6 Channels and Datasets

The actual data is available as channels under a data key.
Channels represent the lowest level of the data model. In Data Explorer they are
only shown in the list view pane. When you select a channel and open its Prop-
erties from the context menu, a dialog box is displayed with three pages
showing channel information as well as a graphical and numerical preview.
Channels are used in display elements. When a channel’s data is loaded into
memory for processing, it is then called a Dataset.
A dataset can be thought of as columns of data or a vector containing one or
more points. The values in a dataset may be numbers or text but cannot be
mixed within one dataset. A dataset also contains a base vector describing the
X-axis.
The dataset is a complete self-describing data object which is the basis for data
manipulation within the application. Since it is totally independent of the file or
test from which it was loaded, the application handles all data in the same way
irrespective of its source.
Remember that channels are displayed both in data keys and in all individual
measurements that may be located under them. For channels loaded straight
from the data key the current measurement to be displayed can be selected
dynamically using the scroll bars. That is not possible for channels from a
specific open measurement.

Data Explorer — User’s Guide

10 Data Explorer

1.1.7 Dataset Names

A dataset is identified by a unique name which consists of the following compo-
nents:
File alias (referring to the file/test the data is derived from)
Data Keys
Channel name and optionally a measurement number, if there is more than
one measurement
Syntax The syntax is:
ALIAS:DT’CHANNEL[meas]

Examples
IFILE1:CA’CYLPR1 is the cylinder pressure loaded from an AVL IFile. CA refers
to the data key (CA=Crank Angle, i.e. crank angle data).
PUMA1:D’SPEED stands for the SPEED dataset, loaded from the file with alias
PUMA1, data key D.
AVL3:!0’BE[2] comes from the second recorder measurement (data key !0). The
BE channel is the specific fuel consumption. Alias AVL3 is the alias name of the
open file. The number indicates that 3 of these files are already open.

In formulas the alias name and data key reference can also be omitted. Data
Explorer will use the current context to fill in the missing parts and find the
required channel.

1.1.8 Formula Channels

Formulas are ASCII files containing calculation rules and residing in predefined
folders. They are shown as virtual channels and can be used like normal chan-
nels. When used they are calculated automatically.
Formula channels may be shown under the same data keys as the measure-
ment channels or in separate data keys depending on the settings for the data
source.

Data Explorer — User’s Guide

Data Explorer 11

1.2 Data Explorer Window

The Data Explorer window consists of two main areas, the Explorer bar (naviga-
tion area) and the test list (flat list display). In the Explorer bar, two views are
available:
My Computer / Network View
Data Source View

1.2.1 My Computer / Network View

This view displays your drives and network folders like MS Windows Explorer.

4
5

1 .....Explorer Bar
2 .....Test List
3 .....Data Environments
4 .....Toolbar
5 .....Adress bar with drop-down list of last opened files
Fig. 1

Files are the lowest level in this view and are never shown in the Explorer bar,
but only in the test list.
The right-hand section, the test list, shows the contents of the item selected in
the Explorer bar.
After selecting a file, you can open it by double-click, via its context menu or via
the toolbar button Open. A data source is then created automatically in the
Temporary Data Sources data environment, if no such data source yet exists.
If the file format is unknown, the data source settings have to be specified. The
relevant Wizard opens for this purpose.
Data sources can also be created via the context menu (see Creating new Data

Data Explorer — User’s Guide

12 Data Explorer

Sources on page 74), which is helpful if you want to create a data source in an
existing data environment anyway.

1.2.2 Data Source View

5
6
7

2
3

1 .... Explorer Bar

2 .... Test List
3 .... Data Preview Window
4 .... Data Environments
5 .... Toolbar
6 .... Address Bar
7 .... Path and Filter Condition Bar
Fig. 2

Unlike with the My Computer / Network view, this view does not show the disk
drives as nodes in the Explorer bar, but so-called Data Sources (see Data
Source on page 7) as the topmost level. These data sources are in turn part of
data environments (see Data Environment File (DXV) on page 73) with My Data
Sources being the main data environment.
A data source contains files of the same format from a given folder or folder
structure. Subfolders (or, in the case of ASAM, structures such as e.g. a test
series), files (i.e. tests) as well as their content structures are displayed hierarchi-
cally in the Explorer bar and/or the test list.
Channels are the lowest level and are never shown in the Explorer bar, but only
in the test list. The contents of a channel can be displayed via its properties
dialog.

Data Explorer — User’s Guide

Data Explorer 13

For a better overview, data sources can be grouped in the Explorer bar by
inserting a separating line via the context menu:

Fig. 3

Fig. 4

The Data Source view can consist of several pages, if several data environments
are available. Accordingly, the enclosed Demo Data appears in a separate data
environment.
There is always a data environment for temporary data sources as created auto-
matically when files are opened directly in the My Computer / Network view. All
data environments, except the temporary data sources, are saved as separate
files (DXV files) for the next session.

Data Explorer — User’s Guide

14 Data Explorer

1.2.3 Toolbar

1.2.3.1 Filtering, Properties and View Operations

Back / Forwards
These buttons are used for navigation within the Explorer bar of already visited
levels.
Up
With this button you can go one level up.
Open
This button opens a file/test.
For more on this topic, see Open on page 43.
Query / Search
This button opens a search results window. The drop-down-list displays entries
if Extended Queries have been defined for the data source in the DXV file.
For more on this topic, see Searching by Data Contents on page 58.
New Data Source
Launches the Data Source Definition Wizard where you can define a new data
source.
Properties
Opens the properties dialog for the current selection.
Edit Filter (in Data Source view only)
This button opens the Filter Conditions dialog which allows you to modify all
filter conditions defined for the current data source (see Filtering and Searching
on page 48).
User Variables
This button opens the dialog for editing user (path) variables which allows you to
modify the values of a path variable that is used in the current data path defini-
tion of the data source or to change user variables that are used in filters of the
current data source.

1.2.3.2 File Operations

These operations are related to data environment management. Just as you
would open, edit and save documents in a word processing program, you can
open, edit and save a data environment.
Open Environment
(alternatively also via context menu option Open Environment in the test list)
This button allows you to perform the following actions:
Open
Opens an existing data environment (DXV file); already opened data envi-
ronments will remain open. When opening an environment, the normal
Open dialog for type DXV files is displayed.
Replace
(also via the data environment's context menu)
Closes all open files and replaces the current data environment with
another one.
Reload
(also via the data environment's context menu)
Closes all open files and reloads the current data environment.
Close
(also via the data environment's context menu)
Closes the current data environment.
Save all
Forces immediate saving of changes made to the data environments.

Data Explorer — User’s Guide

Data Explorer 15

1.2.4 Address Bar

The address bar in the My Computer / Network view, like Windows Explorer,
shows the physical data path. In the Data Source view it shows the logical path,
i.e. the data source name and the hierarchy levels underneath.
When selecting the My Computer / Network view, the Desktop is opened by
default. The 10 last used folders are quickly available via a drop-down list.
If the view Entire Network is not available in your Windows environment
(because the group policy has been changed), you can navigate to the required
server by entering the server name directly in the address bar. Only those
servers with at least one share are shown.

1.2.5 Path and Conditions

The blue bar below the address bar displays the following information:
Data Source View Physical data path in the case of file-based data sources, or ASAM path
(hierarchical level in the ASAM-ODS model) in the case of ASAM data
sources
Filter conditions (see Filtering and Searching on page 48)
My Computer / No information displayed.
Network View

Path variables and user variables in filters are marked as links. Simply click on a
variable, and an edit field will be displayed allowing you to edit its value.
If you want to change all user variables in use by the data source, then click the
User Variables button on the toolbar to open the dialog.
Double-click anywhere else in the blue filter condition line to open the Filter
Conditions dialog where the current conditions can be modified. This is the same
as clicking the Filter button on the toolbar.

1.2.6 Icons
Icons displayed for the entries in the left and right panes provide a visual aid to
identifying an item’s properties and state.
File system group
Normal file system group.
Data source with user-specific access
File system data source containing files that are accessed via the user-written
API (see User-specific File Access on page 42).
ASAM server data source

Sub-level folder
Sub-level folder, folder or ASAM structure containing further sub-levels or tests.
File
File or test.
Open File
Open file, test or measurement – the alias name is shown in the item's label.
Data key: crank-angle data
Data key containing crank angle data.
Data key: cycle-based data
Data key containing cycle-based data.
Data key: time-based data
Data key containing time-based data.
Data key: data/parameters or
Data key containing parameters or other static data.
Data key: logpoint data
Data key containing logpoint data.

Data Explorer — User’s Guide

16 Data Explorer

Data key: formulas

Data key consisting entirely of formulas.
Data key: UTC data
Data key containing UTC data.
measurement
Submeasurement
Submeasurement (see Splitting Data into Artificial Measurements on page 129
and Working with Long Recorder Data on page 134)
Numeric values
Channel containing numeric values.
Text values
Channel containing text values.
Formula
Formula channel.
Binary values
Channel containing binary values.
Related data file
Channel embedded from a related data file.
Frozen channel: numeric values
Frozen formula channel containing numeric values.
Frozen channel: text values
Frozen formula channel containing text values.

1.2.7 Explorer Bar

In the My Computer / Network view the Explorer bar is identical to the Windows
Explorer bar. In the Data Source view, which is dealt with in more detail further
below, this area shows the data sources of each data environment with their
hierarchical structure. The standard view, which includes the subfolders, can
also be changed to a flat structure (which does not show the subfolders). It is
also possible to hide empty folders (see Data Source Properties - Data Source
on page 94).
The top-level root items are the data sources, and the lowest level leaf nodes are
the data keys and measurements (if any exist). The Explorer bar never shows
the channels.
Instead of using the mouse you can also use the keyboard to navigate through
the Explorer bar:
Cursor up: one entry up
Cursor down: one entry down

When navigating quickly through the data sources/test series/data keys using
cursor up/down, the sub-levels are not displayed, which is more effective espe-
cially in the case of ASAM-ODS-based databases and data sources pointing to
network drives.
Cursor right: open sub-level
Cursor left: hide sub-level(s)
Backspace: go to next higher level
Screen up: first data source
Screen down: last data source
Shift key + cursor select area, e.g. several tests
up/down:

Data Explorer — User’s Guide

Data Explorer 17

1.2.8 Test List

The right-hand pane of the Data Explorer window typically lists the tests
contained in the folder selected in the Explorer bar. If that folder contains any
subfolders, they will be shown in the test list.
The main function of the test list is to show the files/tests. Additional attributes
are also displayed, depending on the format. Selected files can be opened via
the toolbar or the context menu.
In the data source view, the file list allows you to view the contents of a test as far
down as the channel level. This is helpful if you cannot identify a test by its name
or attributes and wish to view the contained data directly.
To select multiple items, you can use the Ctrl and Shift keys in combination with
the mouse or the arrow keys in the normal way. Only when channels are
displayed can you drag the cursor over a number of items to make a multiple
selection.
The sequence in which multiple files or measurements are selected determines
the order of components when building a series file.

1.2.9 Context Menus

1.2.9.1 My Computer / Network View

Open
See Open on page 43.
Make New Data Source In ...
– By selecting this option from a file's context menu you can create a
new data source for that file. The new data source's path points to the
higher level folder of the selected file. The data source's file format
matches the format of the selected file, which is identified automati-
cally.
– When you select this option from a folder's context menu, a new data
source will only be created if the folder contains at least one valid data
file.
Add path to
CONCERTO checks whether there are already data sources for the
selected file which match the file's format. If so, they are displayed in a
dialog for selection.
If there is a data source which fits with respect to format and path, it is dis-
played in the data source view.
Replace path in
CONCERTO checks whether there are already data sources for the
selected file which match the file's format. If so, the current path is replaced.

Data Explorer — User’s Guide

18 Data Explorer

1.2.9.2 Data Source View

Information

Apart from offering general-purpose functions, context menus also enable you to
restructure ASAM-ODS data. To use this feature, you must have a Santorin
server, a license to use the Composer option and be operating CONCERTO at
an adequate user level. This applies to all the menu items below that are marked
with {W}.
For more on this topic, see Creating and Restructuring Tests on page 120.

The context menu consists of a predefined and a variable section. The variable
section can be defined by the user via data source context scripts. When a data
source context script is defined, the name of the script will appear in the context
menu from which it can be executed (see description under Data Source Proper-
ties - Context on page 100).
Data Sources Refresh
Reread the folders and tests (files) within the selected data source(s).
Change Login
Log off and log in to a Santorin ASAM Server again.
Cut
Delete the selected data source(s) and copy their definitions to the clip-
board.
Copy
Copy the selected data source definition(s) to the clipboard.
Paste
Paste the data source definition(s) from the clipboard after the current
cursor position.
New Folder
Create a new test series in the current data source {W}.
Delete Data Source
Delete the selected data source(s).
Move Data Source To
Move a data source, e.g. a temporary data source, to another data environ-
ment (see also Data Source on page 7).
Properties
Open a data source's properties dialog.
Folders, Test Series Refresh
Reread the test list (file list).
Paste
Paste a test from the clipboard after the current cursor position {W}.
Edit Attributes
In this dialog you can edit the attributes of a test series (test series name,
etc.).
Entries highlighted in gray are system defaults and cannot be changed {W}.
New Test
Create a new empty test within the current test series {W}.

Data Explorer — User’s Guide

Data Explorer 19

Files (Tests) Open with New Alias

Open the test a further time with a new alias name (_x). This can be useful
if you want to load a file with a different data point filter setting (_x) (see the
documentation about the User Interface Functionalities, under Special
Functionalities).
Open
Open the selected test(s).
Create Series of Log Point Data
Create a series from the selected tests (for multiple selection hold down the
Strg key) and open them as a series. Original data and result are logpoint
data.
The order in which the tests were selected is taken into account.
If there are matching channel and formula names, the channel contents are
displayed. This is indicated by a transparent channel symbol. To give the
formulas priority over the channels (e.g. if you wish to correct saved data),
this behavior can be reversed via this menu option. In this case, the for-
mulas will be displayed, and not the channels.

Information

In order to store formula channels as normal channels in the database, you need
to "freeze" them (see further below).

Data Explorer — User’s Guide

20 Data Explorer

– Raw data from a split measurement

(see Measurement Splitting via Channel Browser on page 130)

Fig. 5

Edit Attributes
In this dialog you can edit the attributes of a test (name, description, start
time etc.). Entries highlighted in gray are system defaults and cannot be
changed {W}.

Information

Changes should only be made by trained personnel to avoid data loss.

New Measurement
Create a new empty measurement within the current test {W}.
Delete Test
Select the current test as logically deleted {W}.
Replace
Replace an open test (in the submenu) with the selected test(s).
External Editor
Open an external file editor (i.e. the IFED.EXE editor for IFiles); only avail-
able if there is a refence to it in the DXV file (see also Data Source Proper-
ties - Context on page 100).
Properties
Show the property page for the selected test.
This includes e.g. file type, name, database attributes, etc. You can select
this option once and view different tests without having to close the dialog.
For tests with file format ASAM-ODS Data Base, this dialog also displays
the logged-in user's access permissions for the test:
R (Read), U (Update), I (Insert), D (Delete), G (Grant)
Data Keys Copy to ComposerFile
Copy the data to a ComposerFile.
For more on this topic, see the documentation about the User Interface
Functionalities, under Editing Data.
Open
Open all measurements available under this data key as virtual files (only
for tests of ASAM ODS Data Base format).

Data Explorer — User’s Guide

Data Explorer 21

Open Using Key

For tests of the ASAM ODS Data Base format or ATF files, this option can
be used to open measurements available under a data key by using an
alternative data key name. This allows layouts, expecting a particular data
key, to be filled with data from a whole variety of measurements. For this,
identical channel names are required.
In the following example, measurement 1 (12) available under data key D1
(Fulload_2.ATF) is opened under the alternative data key D:

Fig. 6

Data Explorer — User’s Guide

22 Data Explorer

Fig. 7

Fig. 8

Data Explorer — User’s Guide

Data Explorer 23

Fig. 9

Close
Close all measurements opened as files under this data key (only for tests
of ASAM ODS Data Base format).
ATF Export
Is used to export an ATF file.
New Measurement
Create a new empty measurement within the current test. {W}
New Channel
Create a new empty channel in all measurements of the current data key.
{W}
For more on this topic, see Creating and Restructuring Tests on page 120.
Show Formulae
If there are matching channel and formula names, the channel contents are
displayed. This is indicated by a transparent channel symbol. To give the
formulas priority over the channels (e.g. if you wish to correct saved data),
this behavior can be reversed via this menu option. In this case, the for-
mulas will be displayed, and not the channels.
In order to store formula channels as normal channels in the database, you
need to "freeze" them (see further below).
New Formula
Open the Formula/Script Editor to create a new formula. For more on this
topic, see the documentation about the Formula/Script Editor.
New Calculator Formula
Launch the Calculator to create a new formula.
For more on this topic, see Calculations in the Exploration Guide.
Properties
Show the properties dialog for the selected data key.

Data Explorer — User’s Guide

24 Data Explorer

Measurements Open
Open the selected measurement(s) as virtual test(s).
Create Series of Log Point Data
Create a series from the selected measurements (for multiple selection hold
down the Strg key) and open them as a series. Original data and result are
logpoint data.
The order in which the tests were selected is taken into account.
If there are matching channel and formula names, the channel contents are
displayed. This is indicated by a transparent channel symbol. To give the
formulas priority over the channels (e.g. if you wish to correct saved data),
this behavior can be reversed via this menu option. In this case, the for-
mulas will be displayed, and not the channels.

Information

In order to store formula channels as normal channels in the database, you need
to "freeze" them (see further below).

Data Explorer — User’s Guide

Data Explorer 25

Delete Measurement
Delete the selected measurement, if the relevant attribute is selected in the
data source properties (seeASAM Properties - Measurements on page 108,
under Deleted Measurements use attribute). {W}
Restore Measurement
Restore a backup or original measurement (see ISO 9000 Compliance on
page 120). {W}
Freeze Measurement
Save the selected measurement, permanently storing the results of formula
channels in the database {W} (see Freeze Measurements on page 123).
Show Formulae
If there are matching channel and formula names, the channel contents are
displayed. This is indicated by a transparent channel symbol. To give the
formulas priority over the channels (e.g. if you wish to correct saved data),
this behavior can be reversed via this menu option. In this case, the for-
mulas will be displayed, and not the channels.
In order to store formula channels as normal channels in the database, you
need to "freeze" them (see further below).
New Formula
Open the Formula/Script Editor to create a new formula. For more on this
topic, see the documentation about the Formula/Script Editor.
New Calculator Formula
Launch the Calculator to create a new formula.
For more on this topic, see Calculations in the Exploration Guide.
Replace
Replace an open test (in the submenu) with the selected measurement(s).
Properties
Show the properties dialog for the selected measurement.
Channels Copy
Copy the name of the selected channel(s) to the clipboard.
New Channel
Insert a new channel into the current measurement {W}.
For more on this topic, see Creating and Restructuring Tests on page 120.
Delete Channel
Delete the selected channel(s) from the current measurement {W}.
Freeze Channel
Save the selected formula channels, permanently storing the results in the
database (see Freeze Channels on page 124). {W}
Show Formulae
If there are matching channel and formula names, the channel contents are
displayed. This is indicated by a transparent channel symbol. To give the
formulas priority over the channels (e.g. if you wish to correct saved data),
this behavior can be reversed via this menu option. In this case, the for-
mulas will be displayed, and not the channels.
In order to store formula channels as normal channels in the database, you
need to "freeze" them (see above).
Edit Formula
Edit the selected formula(s).
New Formula
Open the Formula/Script Editor to create a new formula. For more on this
topic, see the documentation about the Formula/Script Editor.
New Calculator Formula
Launch the Calculator to create a new formula.
For more on this topic, see Calculations in the Exploration Guide.
Delete Formula
Delete the selected formula(s).

Data Explorer — User’s Guide

26 Data Explorer

Properties
Show the properties dialog for the selected channel. It has tabs for Channel
Details, Graphic and Numeric Preview and Quick Edit.
If the selected channel is an element of a test with ASAM-ODS file format,
this dialog also displays the logged-in user's access permission level:
R (Read), U (Update), I (Insert), D (Delete), G (Grant)

1.2.9.3 Data Environment

A data environment's context menu offers the following options:
Replace (also via the toolbar)
Replaces the current data environment with another one.

Information

Please note that all opened tests are closed in the process.

Reload
(also via the toolbar)
Closes all open files and reloads the current data environment.
Close
(also via the toolbar)
Closes the current data environment.

1.2.10 Data Preview

By double-clicking a channel or selecting a channel and choosing Properties
from the context menu you open a dialog which displays the channel's properties
and data.

1.2.10.1 Channel Properties

The channel properties dialog consists of four property pages:
General, Graphic, Values/Edit and Attributes. While it is displayed, you can
navigate in the Data Explorer window and the dialog tries to update its contents
to reflect your selection.

Data Explorer — User’s Guide

Data Explorer 27

General This page contains some basic channel information. If the channel is a formula,
the formula definition is also displayed.

Fig. 10

Graphic This page shows the curve(s) of currently selected channel(s).

Fig. 11

Values/Edit This page shows the values of currently selected channels as an editable table.

Data Explorer — User’s Guide

28 Data Explorer

Fig. 12

Cell Operations Change value

1. To change a cell's value, select the relevant cell.
2. Enter a new value. The modified value will be displayed in bold text.

Alternatively: Change data values using a cursor

You can easily change measurement values via the context menu of a vertical
single or band cursor:
1. Set the cursor directly at the position of the value to be changed in the dia-
gram.
2. Select Edit Data on the context menu.
In the Values/Edit tab that is now displayed the line containing the value on
which the cursor is positioned is already preselected. Cursor movements
are accepted immediately and the relevant lines are selected.
3. Double-click the relevant cell to change the value.
Please note:
– Changes are only stored temporarily in the memory.
– It is not possible to change indicating data.
4. Select a cell (multiple selection possible).

Data Explorer — User’s Guide

Data Explorer 29

5. Right-click to open the context menu:

Fig. 13

Copy Value
This function copies a current cell's value onto the clipboard.
Paste Value
This function transfers a value from the clipboard into the selected cell.
Invalidate Value
It is possible to invalidate values. Since invalid values are not displayed in
diagrams and reports, this is a convenient function for hiding data points that you
do not need.
If a value is invalid, the cell is displayed in red.
Validate Value
If the selected cell already contains an invalid point, the context menu will show
the command Validate Value. You can use this menu option to revalidate a
value.
Since, if you write back an invalid value, it is only ever possible to write back the
value 1e10, you can only revalidate a point previously marked as invalid with its
original value if you do it before you start to write back.
Column Operations 1. Click a column name (i.e. name of dataset represented in the column) to
select the column. Multiple selection is possible.
2. Right-click to open the context menu:

Fig. 14

Data Explorer — User’s Guide

30 Data Explorer

Copy Channels
With this command you can copy channels onto the clipboard. Channel informa-
tion (such as channel name, unit and description) will also be copied.
Paste Channels
This command inserts channels from the clipboard in front of the selected
channel. In this case, existing channels will shift to the right; they will not be over-
written.
Invalidate Channels
If the selected column already contains valid points, this command can be used
to invalidate the entire channel.
Validate Channels
If the selected column already contains invalid points, this command can be
used to validate the entire channel.
Invert Selection
This command inverts column selection. Columns that were selected will be
deselected, and vice versa.
Number Format
With this command you can define the number of decimal places to be
displayed.
Record Operations 1. Select a row (multiple selection possible).
2. Right-click to open the context menu:

Fig. 15

Operations acting on the entire record will affect all datasets of the measure-
ment.
Invert Selection
This command inverts record selection. Records that were selected will be dese-
lected, and vice versa.
Invalidate Records
If this command is selected, the entire row will be invalidated and highlighted
red.
Validate Records
If the selected row already contains invalid points, this command can be used to
validate the entire row.

Measurement Point Context Script

If you define a measurement point context script, as described under Data
Source Properties - Context on page 100, the name of the defined script appears
in the context menu of a record from where it can also be executed.

Data Explorer — User’s Guide

Data Explorer 31

Attributes This page shows specific attributes of the selected channel typically set during
measurement parametrization. These attributes are a detailed description of the
channel properties and can also be read in formulas and scripts.

Fig. 16

Specific attributes for IFiles

The attributes are in English and abbreviated.

CalibrationFactor Conversion factors (from Volt into physical units)

CalibrationOffset ...
PinOffType Pin off type (for internal use only)
SignalType This dataset attribute supports all available signal
types.
StepFactor, Internal conversion factors (from ADC values into V)
StepOffset
TDCOffset TDC offset relative to the reference cylinder
TDCValue TDC value of the relevant channel
(TDC of reference cylinder + TDC offset)
Description Signal description from the signal properties dialog
AdditionalText Additional text for the signal from the signal properties
dialog

If a signal is connected via an amplifier, further channel attributes, such as e.g.

sensor type, serial number of sensor, sensitivity, amplifier range, etc., are stored
in the file.

AmplifierRange, Amplifier measurement range and unit

AmplifierRangeUnit
AmplifierType Amplifier type (e.g. piezo amplifier)
SensorSensitivity, Sensor sensitivity (e.g. 12.6 pC/bar)
SensorSensitivityUnit
SensorSerialNumber Serial number of the sensor used
OutputOffset Amplifier offset (0 V or -8 V)
filter Low-pass filter at the amplifier input
(e.g. 100 kHz)

Data Explorer — User’s Guide

32 Data Explorer

DriftCompensation Drift compensation (on/off)

AmplifierRackType Amplifier rack type, e.g. 4M1
AmplifierCalibrationDate Date of most recent amplifier calibration
AmplifierRackSerial- Serial number of amplifier rack
Number
AmplifierChannel Position of channel in rack
AmplifierGain Amplifier gain
AmplifierTemperature Amplifier temperature

1.3 File Formats

1.3.1 Supported Formats

ASAM ODS Data Base
Oracle test result database via AVL Santorin server according to ASAM 3 or
ASAM 5 standard (see also DXV File Settings on page 79).
AST Gid File
(Option L[g]), crank angle based results of a combustion analysis
AST Rep File
XML based AST Rep files
AST Simulation
Simulation results from the following AVL simulation products: BOOST,
BOOST RT, EXCITE, CRUISE (binary), all as of v2010.x, as well as FIRE
(residual values only, as of v2010.1)
ATF Data Source
ATF files are files in ASAM Transport Format. According to ATF specifica-
tion, it is possible to store one or more tests or test series from an AODS
database into an ATF or XML ATF file.
The filter is able to read both formats and shows the entire ASAM hierarchy
in an ATF file. It can be considered a separate ASAM Server.
However, since you will frequently be working with files which correspond to
exactly one test, you can use the DXV entry ATFSingleTestMode=1 to pre-
vent higher ASAM hierarchy levels from being displayed.

Information

This entry may only be used if the ATF file actually contains one test only.

As opposed to ASAM-ODS servers, the following restrictions apply to the

ATF Data Source:
No support of extended queries, Aods security, editing of attributes and data
saving.
The following DXV keywords are ignored for the ATF Data Source:
– QueryFiles
– QueryName
– CaseSensitive
– CaseSensitiveChannels
– EncryptPasswords
– EditTestAttributes

Data Explorer — User’s Guide

Data Explorer 33

– EditMeasAttributes
– Iso9000
– EnableAodsSecurity
– LoginCaseSensitivity
– EnableInstanceAttributes
– PmatThresholds
– MandatoryAttributes
– UniqueTestNames
– PhysicalDeleteMeas
– AVL InMotion File
File format of the AVL Hybrid Development Platform™, based on AVL
InMotion™
See also DXV File Settings on page 79.
ATIVISION MAT File
MATLAB files from ATI Vision exported from recorder files
AveragedIFiles
Displays AVL IFiles with averaged crank angle data.
For this purpose, the Data Explorer auto-conversion feature is used. When
opening an IFile from this data source, the IFAV.EXE converter program
(specified in the data source properties) is launched automatically and a
temporary file is created where all crank angle based data is averaged to
produce one resulting cycle. Data Explorer then accesses it.
AVL InMotion
(Option L[y]), AVL InMotion format, identical to the IPG Carmaker format
BOBCAT Data File
(Option L[B]), data format of AVL BobCat
Cameo Optimisation Results
(Option L[c]), AVL Cameo optimization data
DCM Data File
Usual data format for control device applications from Bosch/Etas
DIAdem DAT File
(Option L[n]), files in the DIAdem (DAT) format
DIAdem TDM/TDMS File
(Option L[o]), files in the NI DIAdem TDM and the NI DIAdem TDM
Streaming (TDMS) format
DIGALOG Data File
Files in the Digalog format (see also DXV File Settings on page 79)
FAMOS Data File
(Option L[f]), files in the Famos format
GCA Rep File
Single result values of a combustion analysis
Generic ASCII File (auto-detect format)
Data source for ASCII files with automatic format detection.
For more on this topic, see Generic ASCII File (auto-detect format) on
page 35.
Generic Binary File
GTPower
(Option L[G]), simulation results of the CAE tool GT-Power.

Data Explorer — User’s Guide

34 Data Explorer

Horiba VETS Export File

Binary Horiba output files (see also DXV File Settings on page 79)
IFiles
Data files from AVL indicating systems.
Data from the AVL Indiskop 647 can be converted to IFiles using the sepa-
rate IFCO file converter (see also AVL IFile on page 37).
INI File
Files in the standard ini format
Intermediate Recorder Results
(Option L[i]), PUMA Intermediate Recorder data
Magic Analysis Result File
Results from AVL Magic evaluations (classification, event search)
MATLAB MAT File
(Option L[m]), MultiMatrix MAT files from MATLAB (see also DXV File Set-
tings on page 79)
Only MAT files containing simple structures are supported. More complex
structures like multi-dimensional matrices are not supported.
MDF File
(Option L[v]), data of an INCA or VS100 system from Bosch / ETAS.
Versions MDF4 and older are supported (see also DXV File Settings on
page 79).
Multi ASCII File Types
Data source for ASCII files which are described via the separate ASCII File
Wizard (see also Multi ASCII File Types on page 36).
PAtools Erg (Kratzer Automation)
(Option L[k]), PAtools Erg format (Kratzer Automation)
PC Indiskop Work File (MTF)
Indicating data of the AVL 647 saved on a VAX computer
PC-based PUMA TRR File
PUMA results saved on a PC
PUMA Recorder File/MCF
(Option L[p]), PUMA recorder data in Multi Channel Format (see also under
DXV File Settings on page 79).
RedLine File (DSP)
Indicating data from MTS ACAP and CAS systems (see also DXV File Set-
tings on page 79)
Script-based Tests
Script-based data source.
For more on this topic, see Scripting Data Source on page 162 and DXV
File Settings on page 79.
Transport File
Tests can be inserted in this file data source any other data source using
Copy/Paste. A Transport File is then generated from this test.
Universal File Format (Type58)
Standard ASCII file format as used in acoustics
VAX Indiskop Work File
Indicating data from the AVL 647 saved on a VAX

Data Explorer — User’s Guide

Data Explorer 35

VAX-based PUMA TRR File

PUMA result file converted into a sequential file and saved on a VAX (see
also DXV File Settings on page 79)
Yokagawa WT1600/WT3000 Trace
(Option L[j]), file format of the Yokogawa measuring devices WT1600 and
WT3000
Yokagawa DL9000
(Option L[Y]), file format of the Yokogawa measurement device series
DL9000

1.3.1.1 Generic ASCII File (auto-detect format)

CONCERTO is capable of interpreting text files without needing a descriptor file
or a Multi ASCII description.
Whenever this kind of data source is created, it is not necessary to add a
descriptor file.
The text file is analyzed and, depending on which separators are used, split into
segments and channels.
Possible separators are:
space character
tab
;
,
:
=
This means that several different separators may be detected inside a single text
file. In the header information, for example, the data may be separated by ":",
whereas in the main part, the measurement channels may be separated by a
"tab".
CONCERTO checks whether there are any useful data and creates a data key
for each segment. Header information is displayed in the key INF, data in D and
time-based data in TM.
Based on the first 10 data points, either a numerical or an ASCII channel is
created.
The following applies:
Numerical values use "." or "," as a decimal separator.
Numbers in exponential notation are taken into account.
Strings in numerical channels, such as error messages, etc., are interpreted
as invalid value.
Horizontally aligned data are interpreted as header information with one
data point.
Data aligned vertically in columns are interpreted as follows:
– The first line is searched for channel names or their unit in square
brackets.
– The second line may contain the channel units, the third one, option-
ally, the channel descriptions.
If there are no names, units or descriptions, the channel names "Channel1",
"Channel2" to "ChannelN" are created for each column.
Time-based data must contain a numerical channel that has a name starting
with "time" or "zeit". This channel is used as a basis for all the other chan-
nels and is not displayed as an explicit channel.
It is possible to read data with differing resolutions.

Data Explorer — User’s Guide

36 Data Explorer

Data points that do not exist due to a coarser resolution are not read – this
results in channels with different lengths and different resolutions.
This feature that automatically detects the format of any file enables the interpre-
tation of differently formatted text files contained in a single data source. The
detection is fast and causes minimal time loss, even if large files are involved.

1.3.1.2 Multi ASCII File Types

This data source is created temporarily when opening an ASCII file via the entry
Data Access | Open File on the workflow bar, after defining a new format using
the ASCII File Wizard (see Exploration Guide, under Basics of Operation).
The ASCII File Wizard creates a separate ini-file in the %MyLibdir\desc and
%ConcertotmpDir\Layout\desc folders for each ASCII format.
The advantage of this is that you can transport the format definition together with
a layout.
The name of the ini-file is derived from "multiascii_" plus the format name
selected in the ASCII File Wizard.
The Multi ASCII File Types data source may also be created without using the
ASCII File Wizard. In this case it is necessary to indicate the path to the interpre-
tation file. The data source is consequently fixed to an ASCII format from an
interpretation file.
This enables you to define data sources which obtain their format definitions
from a central folder such as %StdLibDir\desc; it is also possible to transport the
format definition within a work environment.
The path to the interpretation file can be deleted afterwards.
If no path is specified, the Multi ASCII data source will use the ASCII formats
from ini-files in the following folders:
%ConcertotmpDir\Layout\desc
%MyLibDir\desc
%StdLibDir\desc
%CurrentWorkDir\desc
multiascii.ini (the multiascii.ini path is defined in the concerto.ini file or the
DXV file)
If several multiascii_*.ini files are found in these paths (or if there are several
formats in a single ini-file), the list of all available ASCII sub-formats is shown.

Data Explorer — User’s Guide

Data Explorer 37

Fig. 17

The data source can be fixed to one sub-format.

If Auto is selected, the system searches all sub-formats for the keyword that
matches the ASCII file. The first matching sub-format is used.

1.3.1.3 AVL IFile

An AVL IFile will show the following data sources in Data Explorer:
CA CA contains channels with crank angle based raw data and one or more cycles.
In addition, artificial channels (V, V_ABS) are created which represent the course
of cylinder volume over crank angle.
These channels are dependent on a piston pin offset (pin off), if defined, and
their orientation.
As different cylinders may have differing pin off values and orientations, the
number of volume channels created also differs:
Volume channels without pin off:
– V: Relative cylinder volume (current cylinder volume relative to VH =
bore x current piston travel)
– V_ABS: absolute cylinder volume
Volume channels with pin off:
– VOFFp, VOFFn: cylinder volume with positive or negative pin off
– VOFFp_ABS, VOFFn_ABS: absolute cylinder volume with positive or
negative pin off
– VOFF2p, VOFF2n: cylinder volume for second positive or negative pin
off value
– VOFF2p_ABS, VOFF2n_ABS: absolute cylinder volume for second
positive or negative pin off value

Data Explorer — User’s Guide

38 Data Explorer

CAO CAO shows the same data as CA but with the cycles appended to one another
(crank angle overlapping mode). The resultant crank angle base will therefore
usually start at -360 but end at a high positive number (n* 720).
Given that the number of cycles may be high, the dataset may be very long,
which would take a long time to display. As a result, only a predefined number of
twenty cycles is displayed. You can change this default value under Extras |
Pre-Sets | General \ IFileCAOCycles = xxx without restarting IndiCom. Any
Open IFiles, however, need to be reloaded.
If you set this value to 0, all cycles will be concatenated.
You may also enter a negative value, in which case cycles are appended to the
left of the given cycle.

Example
IFileCAOCycles=2 results in a dataset ranging from -360 to +1080. Defining -2,
on the other hand, would mean a range from -1080 to +360.

The entry IFileCAOCycles affects all CAO datasets – something that is not
always desirable. If you prefer to leave the above cycle concatenation settings
as they are, however you want to create a specific formula channel, where a
different number of cycles are concatenated, you can do so via a formula by
using the GetCAOCycles method from the Dataset class (see Formula/Script
Editor help).
The resultant dataset is also managed cyclically, i.e. a certain cycle can be set
with the slider. The predefined number of following cycles is appended to it.
If this number is not available (e.g. when approaching the last cycles), only the
remaining ones will be appended. This means that if you select the last cycle,
this will be the only cycle you will see. This reduction in the dataset length,
however, is not always desirable. Especially if you want to do calculations with
CAO data across cycles, this might prove annoying.
Under Extras | Pre-Sets | General \ CAOCycleCountConstant you are able to
change this behavior.
If you set the entry to "REDUCED", the number of cycles available for CAO
channels is limited in a way to always produce datasets of the same length.
If you originally had, for instance, 100 cycles and wanted to link them together in
pairs in order to achieve a continuous low-pressure portion, the setting above
would reduce the number of available CAO cycles to 99.
In the case of cyclical management of CAO data, the crank angle value 0 refers
to the TDC of the current cycle, just like with CA data. If you instead want to
always leave a reference to Cycle 1, you can provide for this under Extras |
Pre-Sets | General \ CAOAbscissaRelatedtoCycle1. Set the entry to "YES"
(Cycle1).

Information

Please note that only the first cycle of the set may undergo zero level correction
because it shows the relevant angle range. The following cycles are appended
without a jump from the previous one. Signal drift is therefore visible as a result.
Under Extras | Pre-Sets | General \ CAOIndividualZeroLevel you are able to
change this behavior. Setting this entry to "YES" means that every cycle will
undergo zero level correction.

If you do not want the CAO data to be managed cyclically, set CAOCycleCount-
Constant to REDUCED and enter a value for IFileCAOCycles which exceeds the
number of cycles available in the file. This links all cycles and no slider appears.

Data Explorer — User’s Guide

Data Explorer 39

TM TM contains time-based measurement channels.

IFiles can also contain time-based measurements. Normally, this data is
displayed in ms units. In longer measurements, however, it makes more sense to
use seconds as the unit. You can change this via the IFileTimeBase entry in the
concerto.ini file:
Possible settings:

ms ... permanently on ms
s ... permanently on s
Auto_0.1ms ... switch to sec from a base interval (finest measure-
ment resolution) of 0.1 ms upwards
Auto_1ms ... switch to sec from a base interval (finest measure-
ment resolution) of 1 ms upwards

CY CY contains result values like IMEP or PMAX over the cycle number.
PAR PAR contains the following parameters:
BORE
CDMRNGST (CDM range start)
COMMENT (user comment on saving)
CONROD (conrod length)
DATE (acquisition date and time as ASAM timestamp (yyyymmddhhmmss))
ENGINE (engine name)
EPSILON (compression ratio)
FILENAME (file name)
GEO - geometry - a combination of all the parameters mentioned above
GEOUNIT (0=mm, 1=inch)
ENG_TYPE (0=Diesel, 1=Gasoline, 2=GDI)
NRSTROKE (number of strokes)
P* (01-28 or 99 if additional operating parameters have been defined (up to
99 are possible))
PINOFF (piston pin offset/crank offset)
PINOFF2 (piston pin offset/crank offset 2, typical application on V-engines,
second bank)
POLY_COEFF (polytropic coefficient from the engine parameters)
TIMESTAMP (measurement start)
STROKE
P01 - P99: operating parameters – they are additionally shown under their
assigned name.
SYS After a measurement, SYS contains the following system variables:
firmware version
Acquisition unit (hardware used for the measurement)
Original file name (The data file's original name is saved in the IFile. This
allows indicating data to be re-allocated to the measurement when the file
name is changed, because data is allocated via the IFile name during oper-
ation with PUMA Open.
User license (software license holder)
software options
Serial number (of hardware)
software version

Data Explorer — User’s Guide

40 Data Explorer

If CalcGraf is installed, the following additional data keys are shown:

CAF CAF contains crank angle based formulas, e.g. heat release.
CYF CYF contains formulas with cycle base (e.g. a calculated IMEP curve).
TMF TMF contains formulas with time base (e.g. result of a subtraction of two
time-based measurement channels).
VAL VAL contains result values which can be either cyclic (i.e. change when the cycle
number changes) or non-cyclic (e.g. a result value determined from a
cycle-based curve).
STA STA contains statistic results. As the respective display elements, e.g. statistic
bars, normally calculate the statistic information themselves when using CYF
formulas, these are relevant to displays in standard tables or forms.
MSC MSC contains other formula channels like the result from an FFT analysis, etc.
Depending on the IFile data source setting, the CAF, TMF and CYF formulas
may also be shown under CA, TM and CY together with the real file data.

1.3.2 Generic ASCII and Binary Formats

Depending on the complexity of the provided ASCII file, you can interpret it in the
following ways:
Via the Generic ASCII File (auto-detect format), in the simplest of cases
(see Generic ASCII File (auto-detect format) on page 35).
Always try to read the ASCII file with this format first, as it needs no further
settings.
There are a large number of ASCII files which can already be read using
this format.
Via the ASCII File Wizard in the case of a more complex structure within an
ASCII file, if it cannot be interpreted via auto detect.
This Wizard can be used to describe the ASCII file structure. If such files
can be identified by a keyword, different ASCII files can be read via a data
source.
For more on this topic, see Exploration Guide, under Basics of Operation.
For more complex header structures and ASCII formats as well as for cus-
tomer-specific binary formats it is possible to create special Descriptor
Files.
For more on this topic, see Reading ASCII and Binary Files with Descriptor
(Syntax) on page 151.

1.3.3 Dictionaries
Very often a file does not contain all the information required to interpret the data
and its format correctly. PUMA TRR files, for example, require a normname
index to resolve the normcodes embedded in the file into proper channel names.
Data Explorer calls these additional files Dictionaries.
Dictionaries may be mandatory, like the descriptor files for Generic ASCII and
Binary formats, or optional, for example, to define a channel name translation.
Note that a single Dictionary file usually applies to all data files in a data source.
Dictionaries are specified on the Format page in the Data Source Properties
dialog.

Data Explorer — User’s Guide

Data Explorer 41

1.3.4 Customer-specific Formats

Due to the modular design of the software and the source-independent nature of
datasets, it is relatively easy to incorporate your own formats. Customer-specific
formats are incorporated in special DLLs so that each application is tailored
exactly to your needs. AVL will be pleased to advise you about the best option
for integration if you have a file format that cannot be read by any other means.

1.3.5 ZIP Format

CONCERTO detects and unpacks ZIP files automatically. (files need not have
the .zip extension). The files are extracted and saved in a temporary folder
(\Temp\Zip) which is automatically deleted after closing CONCERTO.
This mechanism also works with file formats composed of several files, as is the
case e.g. with DIAdem files.
In addition, this functionality supports data that is stored in ASAM-ODS as
External References (Attachments); see ASAM-ODS Data External References
(Attachments) on page 147.
It is also possible to open ZIP files directly via the My Computer / Network view.
Restrictions:
Converter: This mechanism does not work if a Converter is defined (see
Conversion Programs on page 41).
ATF files: This mechanism only works for zipped ATF files in single-file
mode, but not if these files are Attachments.

1.3.6 Conversion Programs

Complex file formats often have a conversion program which extracts data and
stores it in another format, usually column-based text files. Data Explorer can
use such a program to convert from a format that it cannot read into one that it
can. The conversion program runs automatically and the process is transparent
to the user.
Before you can use this feature, you have to define the call for the conversion
program in the Data Source Properties dialog (Format property page, see Data
Source Properties - Format on page 92). Use the converted file's format as the
data source format.
Assuming, for example, that your data file format is not one of Data Explorer's
internal, generic or customer-specific formats, a program called MyConv.exe will
read it and generate a text file containing the columns of data that could be read
as a normal ASCII file. Define a data source with Generic ASCII format and
specify MyConv.exe as the conversion program. Your data source properties
dialog should look something like this:

Data Explorer — User’s Guide

42 Data Explorer

Fig. 18

Note the format of the conversion program's command line. It is usually

“MyConv.exe %1 %2” because the program probably takes two arguments: the
input file name and the output file name. Data Explorer inserts suitable values for
these arguments before running the program.
The output file is placed in the temporary folder as defined in the concerto.ini file
entry "Temp=". It will be deleted when it is no longer required.

1.3.7 User-specific File Access

If your data file format is not one of Data Explorer's internal, generic or
customer-specific formats, nor do you have a conversion program which can
extract data to a supported file format, then there is one more option. Data
Explorer supports a simple API so that anyone with C or Basic programming
experience can write their own access functions.
The API is described in full in a separate document which is available from AVL
on request.

Data Explorer — User’s Guide

Data Explorer 43

1.4 Working with Data Files/Tests

1.4.1 Open
Before datasets can be manipulated in the application, the tests to which they
belong must be opened.
Tests can be opened via the following toolbar button, irrespective of the view
currently being used:

In addition, you can replace a file/test with another file/test via the Replace
context menu option.
Alternatively In one of the two views:
My Computer / • Double-click the file (test, layout, page template, etc.) or choose Open from
Network View the context menu:

Fig. 19

Wherever possible, the format of the file to be opened is identified automat-

ically (see also Basics of Operation in the Exploration Guide). After opening,
the test name is displayed in bold text and its symbol changes. A temporary
data source is created, if no data source has yet been defined for the test.
This view also allows you to open ASAM data directly:
1. For this purpose, navigate to a computer in the network running one or
more ASAM-ODS servers.
If the view Entire Network is not available in your Windows environment
(because the group policy has been changed), you can navigate to the
required server by entering the server name directly in the address bar.
Only those servers with at least one share are shown.
2. Select a server from the list of available servers (which also include San-
torin environments). After logging in, you can navigate as far down as the
test level. You can also open the test or create a new data source straight
via the context menu.

Data Explorer — User’s Guide

44 Data Explorer

Fig. 20

Data Source View

Fig. 21

After opening, the test name is displayed in bold text and its symbol changes. A
temporary data source is created, if no data source has yet been defined for the
test.

1.4.2 File Alias

When a test is opened in Data Explorer, it is assigned a short name which
uniquely identifies the file and, in most cases, also the file type in the layout. This
short name is referred to as File Alias.
For example, when IFiles are opened in Data Explorer, the file aliases IFILE1,
IFILE2, etc., are automatically assigned to them.
The file alias is part of the dataset name and used in display objects to reference
a certain channel. Thus, by using alias names the layout becomes independent
of the name of the currently open file, which can be replaced globally in Data
Explorer.
1. Open Data Explorer.
2. Right-click on the desired test that naturally has to have the same file type
and structure, and select Replace from the context menu.
For each data source, the user or the administrator can set the file alias. Per file
type within a given organization, however, you should always use the same alias
so that the layouts remain interchangeable between the different users.

Data Explorer — User’s Guide

Data Explorer 45

1.4.3 Handling Measurements and Series

1.4.3.1 Measurements
ASAM tests consist of measurements which are displayed under data keys in
Data Explorer. Not only a complete test, but also single measurements can be
opened. A measurement is displayed as an open, virtual file in Channel Browser
and also receives a file alias. This enables the full file comparison logic to
operate on this measurement, too.
When a single measurement is opened, the open file in the channel list only
shows the data key containing the measurement.
Although only a single measurement has been opened, there is often data else-
where in the test which will be needed for diagrams (e.g. engine data from data
key !E). It is then possible to define additional data keys which are to be made
available when opening a single measurement as a logical file (see also Data
Source Properties - Advanced on page 98).
Only measurements can be opened as virtual files, but not data keys. Since
measurements are only shown in the Explorer bar of Data Explorer, you have to
click the required measurement explicitly (because there might be more than
one measurement under a data key) and then open it by selecting Open on the
context menu or clicking the Open button on the toolbar.

1.4.3.2 Submeasurements
Submeasurements are artificial measurements that can occur when recorder
data is segmented (see Working with Long Recorder Data on page 134) and
when measurements are split (see Splitting Data into Artificial Measurements on
page 129).
If measurements are split into submeasurements, it is no longer possible to open
the test on the Test level.
The measurement subdivision first defined causes the split measurement to be
opened instead of the test. In a split measurement, the measurement scrollbar
refers to the submeasurements.

Data Explorer — User’s Guide

46 Data Explorer

1.4.3.3 Test Series

Data Explorer allows you to define a sequence of files which are to be concate-
nated into a series (see also Context Menus on page 17). As a result, a virtual
file is created which is only displayed in Channel Browser and which contains the
channels merged from each of its component files.

Fig. 22

A series might be constructed, for example, if each file contains a single curve of
an engine map (e.g. static speed with varying torque), in which case the resulting
datasets from the virtual series can be used to calculate isolines and surface
maps.
Data Explorer remembers the order in which the files are selected. They do not
therefore have to be consecutive files, nor do they have to be displayed in
sequence.
Alias names for series are always in the format SERIESn.
The files used in a series are displayed in italics. The icon remains the same as
for the open single file.
File series can only be opened in the data source view.

1.4.3.4 Series of Measurements

In Data Explorer, it is also possible to create a series of measurements (see also
Context Menus on page 17). In this case, a new virtual file is created in Channel
Browser.
In a PUMA Test, the curves of an engine map may be stored in individual
measurements. This feature allows you to merge the data from all measure-
ments. You can still select the component curves and calculate isolines or
surfaces from the resulting channels of the virtual series file displayed in
Channel Browser.
Data Explorer remembers the order in which the measurements are selected.
They do not therefore have to be consecutive measurements, nor do they have
to be displayed in sequence. Alias names for series are always in the format
SERIESn.

Data Explorer — User’s Guide

Data Explorer 47

1.4.3.5 Opening Tests Containing Several Measurements of the Same Type

If several measurements are available under a data key in a test (e.g. if the same
Recorder was launched several times), it is possible to interactively select a
measurement after selecting a dataset under this data key. If such a dataset is
represented in a diagram window, a slide bar appears in the status bar via which
the measurement to be displayed can be selected. The represented curves will
automatically adjust.
CONCERTO also enables you to merge measurements of the same type (see
Merging Measurement Types on page 139).

1.4.4 Further Actions

1.4.4.1 Close
The context menu for an open file contains a Close command. This is the only
way an open file can be closed. Opening a new data environment causes all
open files to be closed.

1.4.4.2 Replace
One open file can be replaced by another.

Fig. 23

1. Select the Replace context menu option for the new file to display a sub-
menu with the alias names of all open files.
2. Select the file to be replaced.

1.4.4.3 Comparing Files

CONCERTO provides you with a simple way of comparing several files with one
another. You can choose between interactive file comparison and automatic file
comparison. The interactive mode gives you complete flexibility and the power to
influence the comparison process and should therefore be given priority. Auto-
matic file comparison is fully automatic, yet it requires certain structures in the
displayed layout.
(See the documentation about the User Interface Functionalities, under Special
Functionalities).

Data Explorer — User’s Guide

48 Data Explorer

1.4.4.4 Load Data Dialog

When loading a layout, a separate file selection dialog box is displayed. It
already contains a test list made up of the tests which were open at the time the
layout was saved. The test list also includes the data source of the test. In this
way, data sources with the same name that are used in different data environ-
ments can be clearly identified.
You can simply accept the test list by clicking Load.

Fig. 24

If you want to make changes to the proposed test list, just drag files, measure-
ments or tests onto an entry in the list. You can make one-to-one replacements,
for example, by dragging a single file onto an entry in the dialog or many-to-one
replacements by dragging multiple tests onto a single entry. In the latter case,
the additional tests are shown with the alias. Alias names will only be allocated
when you click Load.
Tests can be removed from the list by selecting them and pressing the Delete
key (Del). All tests can be removed from the list in one go using the "Empty"
icon.
Click the Skip button to load the layout without data.

1.5 Filtering and Searching

CONCERTO enables filtering at the test level, as described in the following
sections, and also by data point (see the documentation about the User Interface
Functionalities, under Special Functionalities).

1.5.1 Filter Conditions

The number of tests in a data source may be very large. That applies in partic-
ular to ASAM databases. Data Explorer therefore allows you to define one or
more filter conditions to be applied to the test list, thereby reducing the number
of tests presented.
For an ASAM database, the test list contains columns for all defined test
attributes. The "logical" file name is usually made up of two attributes which are
defined in the Data Source Properties dialog.
In a file system data source, it is possible to define attribute columns in addition
to the file name, date, time and size provided by the operating system, by scan-
ning the files and extracting certain values (figures and texts) (see Test Attributes
in File System Data Sources on page 50).
The principle for setting Filter Conditions applies to both situations equally. The
only difference is that for an ASAM data source at least one filter condition has to
be defined.
Filter conditions are displayed in the path and filter condition bar and can also
contain user variables. The current value is then displayed in blue and after

Data Explorer — User’s Guide

Data Explorer 49

clicking it you can change it in the edit field that appears (see Path and Condi-
tions on page 15 and User Variables in Filter Conditions on page 71).
Conditions are saved as part of the data environment (DXV file). If the DXV file is
on a networked read-only drive, then changes cannot be saved. However, using
a user variable allows you to define a general-purpose condition in the DXV file
which can be tailored to individual user’s needs by setting different values.

Example
A condition might, for example, read:
TestId > 200

That is a fixed condition. To display other tests, the condition has to be changed.
Alternatively, you could define the condition as follows:
TestId > %testId

%testId is a "user variable".

Now each user can work with the same filter condition by setting %testId to their
own values that are stored in the local INI file.

Information

Please note that conditions linked to an ASAM data source have to reference
attributes of a test. It is not possible to filter levels above the test (e.g. test
series). On the other hand, Data Explorer also suppresses the test series that do
not contain any more tests as a result of the filter conditions.

Special user variables containing relative times are also available. These start
with a $ character.

1.5.1.1 Text Filters

If the quantity to be filtered is a text, the following applies:
An exact string comparison is made for =.
>,>=,<,<= are also possible and the comparison is made lexicographically
(i.e. character by character), in accordance with the order in the ASCII
code. Remember that lowercase letters come after the uppercase ones
(e.g. d is greater than Z).
An * can be added at the beginning or end of a text as a wildcard (e.g. *ABC
or ABC*). Multiple wildcards and characters or strings following the wildcard
are not permissible.

Data Explorer — User’s Guide

50 Data Explorer

1.5.2 Test Attributes in File System Data Sources

When engine test results are stored in files, it can be difficult to locate the
required test based on a file name.
ASAM solves this problem by presenting a number of attributes for each test
along with the test name or ID. Data Explorer can emulate this feature for file
system data sources by using a file scan method.
In a file system data source, the operating system supplies four attributes as
standard: filename, date, time and size. The scan technique is used to generate
additional attributes from actual values loaded from each test. Since this will
normally be a lengthy procedure, all values extracted are cached to a file. When
the data source is explored, only the files that are more recent than the corre-
sponding cache entry need to be actually read.
Automatic configuration
The context menu option Show as Test Attribute in the test list allows you to
define which values are to be extracted from the files:

Fig. 25

The additional attributes created via this context menu option are saved to the
FILESCAN.TXT file. You can open the filescan file with a text editor and, if
required, also configure it manually (see further below).
To remove a test attribute from the test list, choose the Remove Test Attribute
option from the test list’s context menu.

Fig. 26

Manual configuration (if required)

Your CONCERTO installation includes a filescan file (FILESCAN.TXT) by
default. This file resides in the \StdLib\Desc folder.
The file path is defined via the following entry in the concerto.ini file:
ScannerFile=C:\CONCERTO\StdLib\Desc\Filescan.txt

The filescan file might look something like this:

[IFILE]
PAR'COMMENT PAR'ENGINE
[PC_PUMA]
$B'ENGNUM $B'TST_STRT

Each section begins with a header in the form of “[alias]”, where alias is the data
source's default alias. Following the header are a number of channel names
separated by spaces and occupying one or more lines. A data source will only

Data Explorer — User’s Guide

Data Explorer 51

display an extended attribute list if it has been enabled. In the Data Source tab
of the Data Source Properties dialog, activate the Enable Extended List check
box (see Data Source Properties - Data Source on page 94).
The Cache to File field should contain the complete path to the file in which
attributes will be cached. The browse button helps you to select an existing file:

This may be the same file as specified in another data source but choosing a
cache file dedicated to the data source will produce the best results. To summa-
rize, the following three conditions should be met to use this feature:
Enable Extended List should be activated in the Data Source Properties
dialog.
The cache file path should be specified.
The file specified in the concerto.ini file by ScannerFile= should have a sec-
tion with the same default alias as the data source.

1.5.3 Filtering by Attribute

If these requirements are met, you can define further meaningful conditions in
the filter dialog to reduce the number of tests. For this purpose, proceed as
follows:
1. Click Filter on the toolbar:

Fig. 27

The dialog for defining standard filter conditions opens.

(The dialog is scalable and the column width individually adjustable.)
2. Set the filter condition as required by clicking into the lines (e.g. $FILE-
NAME = OP*):

Fig. 28

You can activate/deactivate individual filter conditions via the check box.

Data Explorer — User’s Guide

52 Data Explorer

In order to delete a filter condition, click on the grey area to the left of the
check box to select the line and then click the Delete button.
3. Click OK.

Information

For more information about how to use the Filter Conditions Editor, refer to the
documentation about the User Interface Functionalities, under Special Function-
alities.

Data Explorer now only shows the tests that match the defined filter conditions.
All activated filter conditions (only one in our example) are displayed in the path
and filter condition bar. If you want to edit them, simply click them:

Fig. 29

Fig. 30

1.5.4 Finding Tests on an ASAM Host

To identify tests, ASAM internally uses a number of attributes for each one of
them. These attributes are automatically assigned by the system, such as e.g.
logged-on user, project name, start time of test, etc.
The purpose of these attributes, among other things, is to describe properties of
a test that are as unique as possible. Filtering based on these properties in Data
Explorer makes it much easier to find older tests.
For an ASAM data source at least one filter condition must be defined.

Example
Attributes include e.g.:
Engine number, customer-specific, e.g. V8_40N3 (for V8, 4.0 liters displace-
ment, ECU Version 3)
Test run type, e.g. FL (full load), EM (engine map), ET (endurance test), ETC
(European Transient Cycle), etc.
Test run version number
ECU/EDC version number
etc.

The figure below shows an unfiltered list - all test series/tests are displayed.

Data Explorer — User’s Guide

Data Explorer 53

Fig. 31

Now we want to set a filter.

1. Click Filter on the toolbar:

Fig. 32

The dialog for defining standard filter conditions opens.

If you are working in an environment with several, centrally managed CON-
CERTO installations, the CONCERTO Administrator will probably prefer to
use user variables.
For more on this topic, see User Variables on page 76.
2. Set the filter conditions as shown below by clicking into the lines
(Test.iName = 3lE33*):

Fig. 33

Data Explorer — User’s Guide

54 Data Explorer

Information

For more information about how to use the Filter Conditions Editor, refer to the
documentation about the User Interface Functionalities, under Special Function-
alities.

3. Click OK.
The filter condition is displayed in the path and filter condition bar. If you
want to edit it, simply click it:

Fig. 34

Fig. 35

Filtered list:

Fig. 36

Data Explorer now only shows the tests that match the defined filter condi-
tions.

Data Explorer — User’s Guide

Data Explorer 55

4. Now we shall define a filter condition for a further attribute, e.g. start time of
test.

Fig. 37

Information

Make sure to input the date in the following format: YYYYMMDDHHMMSS

You can also use only part of the date as filter criterion, e.g. by only specifying
the year and month.
Finally, the number of tests displayed will have been reduced to a small number
of tests or the one test you wanted to find:

Fig. 38

Accordingly, filters are a powerful tool for organizing larger ASAM databases,
and are essential for handling large data amounts efficiently.
Using filter attributes requires a uniform procedure, especially where large,
centrally organized test bed environments are involved.
Such filter criteria are also provided for file-based file groups (e.g. IFiles or
ASCII), however to a limited extent. Since no customized settings are offered, it
is only possible to filter by the file attributes, file name, date, time and size.
For more on this topic, see Test Attributes in File System Data Sources on
page 50.

Data Explorer — User’s Guide

56 Data Explorer

1.5.5 Extended Queries

As described in section Test Attributes in File System Data Sources on page 50,
it is possible to define standard filter conditions.
There are, however, some restrictions to these standard filter conditions.
You can only use attributes from the test table.
The individual criteria are always linked with logical AND. It is not possible
to use OR.
The Extended Queries were therefore added from ASAM-ODS Version 3.2 on. In
Extended Queries you can now use attributes from different tables. In addition,
you can also link the individual conditions with OR.
The CONCERTO AODS client supports the Extended Queries. Please ensure
that the ASAM-ODS server used also supports the Extended Queries (e.g.
Santorin 3.33a Hotfix 2 or PUMA Open 1.2.1 Hotfix 1 or PUMA Open 1.3 Hotfix
1).
By default (for all data sources) Extended Queries are defined in a file
(_Default_.qry) that is located in the tmp folder in CONCERTO.
If you want to use special data source-specific queries, further query files (.qry)
may be created that have to be defined in the DXV file in the section of the
respective data source via the QueryFiles= entry. This entry has the effect that
only those search queries appear in the drop-down list of the Search button that
were defined for this data source (see also DXV File Settings on page 79).
You can open and compare as many search results windows of varying data
sources or extended queries as you like.
Search results windows are top-level windows and have their own buttons on the
Windows task bar. Each window has a unique name that derives from the data
source and the query name or, in the case of local data, from the data source
and any of its subfolders.
If no Extended Query is selected, then, after the call, the search window displays
the test list for the data source selected in Data Explorer by applying the defined
filter conditions.
The content of the query files must be created with the text editor. The syntax
required to do so is heavily modeled on SQL (see Syntax for Extended Query in
the Query File on page 57).

Information

Besides the Extended Queries, the data search definitions are also saved in .qry
files. Unlike with Extended Queries, there is also a powerful editor available for
creating extended data searches (see Searching by Data Contents on page 58).

1.5.5.1 Selecting Extended Queries in the User Interface

With regard to selecting Extended Queries, Data Explorer provides a drop-down
list that offers all extended queries available. Besides the Extended Queries, this
list also contains the search definitions.

Fig. 39

Data Explorer — User’s Guide

Data Explorer 57

1.5.5.2 Syntax for Extended Query in the Query File

Attributes that are used in query files have to be referenced with the table and
attribute names as follows:

Example
for PUMA data model:
Test.iName, Test.Id, Measurement.iVersion

As the extended filtering enables you to define exactly what attributes are to be
returned and in what order the results are to be sorted, the column order and
column width in the filtered list are not managed.
Multiple query files can be defined with paths separated by semicolons.
Query File The query file's format is based on the INI file's. A query corresponds to a group
Structure in this file that, like in the INI file, starts with the group title in square brackets,
e.g. [last week's tests].
The query itself is based on SQL syntax and consists of the following three
entries:
Select =
Defines the attributes that are to be returned by the query and displayed in
Data Explorer.
Where =
Defines the query condition (you have the option of using parameter
ROWNUM to define the limit of the met filter conditions to be returned).
For non-ASAM-ODS data sources, only the Where= entry takes effect.
Search criteria are stored under the Values= entry in the query file.
OrderBy =
Defines the sort order for the query results. This entry is optional. If you use
the sort order, you can set parameter DESC to return the results sorted in
descending order.

Example
[Last 5 tests entitled Te* from the 4th test series]
Select = Test.Id, TestSerie.iName, Test.iDescription, Test.rTestSerie
Where = Test.iName = Te* AND Test.rTestSerie = 4 AND ROWNUM <= 5
OrderBy = Test.Id DESC

[The tests entitled Te* or Co*]

Select = Test.*
Where = Test.iName = Te* OR Test.iName = Co*
OrderBy = Test.Id

In addition to standard and extended filter conditions (Extended Queries), it is

also possible to filter even more complexly, this time by data content.
For more on this topic, see Searching by Data Contents on page 58.
Rules and Restric- The ASAM-ODS Standard defines that, in an Extended Query, conditions may
tions only be applied to application elements which are used in the report. To put it
another way, if you want a condition on a Measurement attribute, then at least
one Measurement attribute must be selected with Select.
As a typical example, suppose you wish to find all tests containing a recorder
measurement. The definition given below does not comply with the standards
(and would cause an error in the server) because Measurement is used in the
condition, but not in the Select clause.
Select=Test.Id, Test.iName, Test.iDescription, Test.iVersion
Where=Measurement.iType = 1

You could add a Measurement attribute to the Select clause, but this would
result in a list of Measurements.

Data Explorer — User’s Guide

58 Data Explorer

Furthermore, the standards dictate that the order of items in the Select clause
should be in their ‘natural’ top-down order. For example, these two would
normally produce very different result sets:
Select=TestSerie.Name, Test.Name, Measurement.Name, MeasurementQuantity.Name
Select= MeasurementQuantity.Name, TestSerie.Name, Test.Name, Measurement.Name

Since the order of selection determines the order of columns displayed in the
search results window, this restriction is important to CONCERTO.
However, CONCERTO is able to overcome these restrictions by normalizing
queries, presenting them to the server in a way that the server will accept them,
and pre-processing the results returned by the server.
Neither are you restricted to conditions on the Measurement – conditions on
MeasurementQuantity are also possible.
You could therefore ask for Tests which
contain specific channels:
Select=Test.Id, Test.iName, Test.iDescription, Test.iVersion
Where=MeasurementQuantity.iName = ALPHA
contain floating-point data:
Select=Test.Id, Test.iName, Test.iDescription, Test.iVersion
Where=MeasurementQuantity.iDataType IN (3, 7)
contain KF in data key ALPHA:
Select=Test.Id, Test.iName, Test.iDescription, Test.iVersion
Where=Measurement.iName = KF AND MeasurementQuantity.iName = ALPHA AND
(Test.iName = Copy* OR Test.iName = Full*)

1.5.6 Searching by Data Contents

(Option N[D] required)
In addition to standard and extended filter conditions (Extended Queries) that
practically form a first filter level, it is also possible to start a search for tests
where also real data contents are accessed.
In the following example, a new search definition is defined which contains the
following filter conditions:
all tests starting with the name Fuel* from the test series with Id=853
only tests of engine type PE000001
second filter criterion: !E'E_ID=*001 or EngPar'E_ID=*001
only measured data from the D or ST data keys
load points with 2000<speed<2500 and 100<torque<120
Example data from an ASAM ODS database is used.

Data Explorer — User’s Guide

Data Explorer 59

First of all, when establishing a link to the ASAM ODS database, the first filter
condition was set to test attributes (for an ASAM data source there must be at
least one defined filter condition):
Test.iName = Fuel*
Test.rTestSerie = 853

Fig. 40

Information

For more information about how to use the Filter Conditions Editor, refer to the
documentation about the User Interface Functionalities, under Special Function-
alities.

Data Explorer — User’s Guide

60 Data Explorer

Data Explorer shows the pre-filtered list - only tests starting with the name
Fuel* from the test series with Id=853:

Fig. 41

NOTICE

The data source in which the search should take place must be selected.

Click Search to open the search results window where you can define further
filter conditions:

Fig. 42

After expanding the drop-down list by clicking the arrow symbol you can select a
previously created search definition (e.g. Test Name):

Fig. 43

Data Explorer — User’s Guide

Data Explorer 61

Information

Apart from search functions, predefined Extended Queries may also be selected
from this drop-down list (see Extended Queries on page 56).
You can open and compare as many search results windows of varying data
sources or extended queries as you like.
Search results windows are top-level windows and have their own buttons on the
Windows task bar. Each window has a unique name that derives from the data
source and the query name or, in the case of local data, from the data source
and any of its subfolders.

Fig. 44

Data Explorer — User’s Guide

62 Data Explorer

Defining the Search Name

In this edit field you can create a new search or select an existing search via the
drop-down list and modify it. The queries stored in a query file can be saved
again (via button Save Query), renamed or deleted (via button Delete).
With the Delete button the current query is removed from the query file perma-
nently. You are therefore asked to confirm the action before proceeding.
1 - Pre-filter for
Tests

Fig. 45

The purpose of this filter level is to reduce the list of tests for the subsequent,
more time-consuming data search steps to a minimum by applying the fast
attribute filter.
This filter level filters according to test attributes (e.g. test name, test run, etc.).
This step corresponds to the previously mentioned definition of at least one filter
condition when linking with an ASAM ODS database and/or the procedure
described under Finding Tests on an ASAM Host on page 52.
The (...) button takes you to the standard filter dialog where you can modify
and/or extend this pre-filter.
If the check box Link with Data Source is activated, the Pre-filter for Tests is
also set as a filter for the data source.
2 - Data Pre-Condi-
tions

Fig. 46

Data Explorer — User’s Guide

Data Explorer 63

Here the filter conditions are defined for static data keys. While this filter level
does access measured data, it only accesses individual static values. This
makes it much less time-consuming than the subsequent record-based data
search.

Information

In the case of datasets containing a number of records, always just the first value
will be checked.

In this step, the number of tests is effectively reduced for the subsequent
record-based data search.
The (...) button brings you back to the standard filter dialog where you can
extend the search by individual values from the channel data.

Information

The Advanced button takes you to a further dialog which allows you to define
more complex filter criteria with logical structures (see Advanced Filter Dialog on
page 68).

Here you can define several data keys from which the filter channel is loaded.
This allows you to filter test lists with various types of measurement:

Fig. 47

For each test, the filter channels are loaded.

Channels with individual values can be compared directly with a value (standard
filter dialog), from channels with multiple values individual values can be calcu-
lated for filtering.

Data Explorer — User’s Guide

64 Data Explorer

3 - Record-based
Data Conditions

Fig. 48

Similar to 2 - Data Pre-Conditions this filter level filters data.

Unlike static data filtering, this filter is record-based. This means that the check is
run on the conditions for all measured points of the selected measurements. This
has the advantage that where large measurements are concerned, only those
measured points are precisely filtered which match the defined condition and are
therefore of interest.
The (...) button brings you back to the standard filter dialog where you can further
deepen your search. Here the dialog list contains nothing more than the channel
names of a test.
The purpose of this further filter is the retrieval of defined load points or operating
modes. The filter procedure returns a list of tests that contain these matching
load points.

Data Explorer — User’s Guide

Data Explorer 65

Fig. 49

Here too, similar to the static data filter, you may also enter the data keys to be
searched for filter channels.
See below what defines from which test or tests (multiple selection possible) the
channels are displayed:
The first opened test.
If no test is opened: the test selected in the test list.
If no test is selected, the first test in the list is automatically drawn upon.

Information

Here too, the Advanced button takes you to a further dialog that allows the defi-
nition of more complex filter criteria with logical structures (see Advanced Filter
Dialog on page 68).

The check box Collect Results into new ComposerFile allows you to export
the results of the search query to a ComposerFile (see Creating a ComposerFile
from the Results of a Search Query in Data Explorer on page 70).

Information

Please consider that if the check box is activated, the search process may take
longer since the search is not over if the condition is met in one record. If the
check box is activated, all records of a test are searched.

Data Explorer — User’s Guide

66 Data Explorer

The Search Now button launches the search query. All tests that match the
search criteria will be listed:

Fig. 50

If the Show Condition Values check box is activated, additional columns are
shown containing the current values for the data channels used in the data filter
levels. This is very useful for creating the data search criteria.
In our example the second column shows the engine number from the channels
!E'E_ID or EngPar'E_ID.
The first index of the retrieved load points is shown in the third and the fourth
column.
Only tests with the engine number *001 and tests with records that match the
condition with 2000<speed<2500 and 100< torque<120 are given the filter result
True.

Data Explorer — User’s Guide

Data Explorer 67

Run Script Further processing of search results can be made in your own scripts. For
example, define the following in the DXV file for this data source:
SearchTestContextScripts=d:\concerto\scripts\Analyse Results.csf;
d:\concerto\scripts\Further Analysis.csf

Path Variables may be used in place of the full paths – e.g.:

Example
SearchTestContextScripts=%ScriptDir\Analyse Results.csf; %ScriptDir \Further
Analysis.csf

If the first-level query has returned a list of tests, then these scripts are available
in a drop-down menu from the Run Script button:

Each script takes a single argument – the matrix of results. You can access each
column of data using the GetCell script function on row 1 – for example:

Example
arg m
ds1 = m.GetCell (1, 1)
nResults = ds1.Count
ds2 = m.GetCell (1, 2)
etc.

The column header is given by the cell’s name:

Example
aHeader = ds1.Name

There are 5 types of result cells, identified by the column header:

The attributes returned by the first-level query - ds.Name is “Test.Id”,
“Test.iCustom1”, etc.
The search criteria columns (if a Search has already been performed) -
ds.Name is MAX(D'ALPHA) or AVG (SPEED), for example. The values in
this column are exactly what appears on the screen.
The True/False column (if a Search has already been performed) –
ds.Name is True/False. The values in this column are “true” (this test
passed the search criteria), or “false” (this test failed the search criteria).
An extra column showing which rows have been highlighted by the user –
ds.Name is $SELECTION$. The values in this column are 0 (not selected)
or >0 (the order in which the user highlighted the rows). An empty value
means that the corresponding test was not eligible for the search proce-
dure. This can only happen in file-based groups, if the test did not fulfil the
first-level filter conditions.
An extra column defining the path of the Test on each row – ds.Name is
$PATH$. With this information, you can determine to which series/project
the test belongs. For example, the path ds.y[n] can be used in the LoadFile
script function for further processing.
The $PATH$ column will not be present if the query was performed on a
file-based group. In this case, the query was anyway restricted to a single
folder.

Data Explorer — User’s Guide

68 Data Explorer

Display Options Here you can define how to display the filtered tests.
Show Original Attributes: Displays tests with the attributes that are
defined in the query file under the statement Select or, in the case of normal
filtering, the attributes of the database (with ASAM-ODS data).
Other data is displayed the same way as in Data Explorer.
Show Condition Values: Displays additionally the calculated values of the
channels as separate attribute columns of the tests.
Show All Tests: Lists all results of the first filter level and marks the tests in
a separate attribute column with either true or false according to the filter
conditions.
This setting provides you with an overview of all tests that fail to comply with
the filter conditions.

1.5.6.1 Advanced Filter Dialog

In the second and third filter level (3 - Record-based Data Conditions and 2 -
Data Pre-conditions Filter) you can additionally apply complex filter criteria with
logical operations to the filtered list.
If you click the Advanced button in the Pre-filter for Tests dialog or the
Record-based Data Conditions dialog, the following dialog opens:

Fig. 51

The channels or data keys to be filtered were transferred to the window.

You can now apply the following operations to these channels or data keys:
First delivers the first data point
Last delivers the last data point
Min calculates the minimum
Max calculates the maximum
Avg calculates the mean value
Count delivers the number of points

Data Explorer — User’s Guide

Data Explorer 69

The results from these operations can now be compared with a value or a
CONCERTO variable using the following operators:
= equal
<> unequal
> greater
< less
~ within a value +/-Value in %

Each line now returns true or false. These logic results can now be connected by
AND and OR.
The order of operators can be specified by using parentheses. In this respect,
you must make sure that the innermost parentheses are set first; only then are
you able to set the outside parentheses.
Individual lines or parenthetical expressions can be negated by a preceding
NOT.
Search criteria can be defined as specific to a channel/data key, or generally for
any channel/data key.
By using the following definition, for example, CONCERTO filters out the engine
numbers *001 or *002:

Fig. 52

Click OK to start the search and close the advanced filter dialog. The results
from this evaluation are displayed in the search results window.
Since the search may take some time in the case of a large number of tests, a
status bar informs on the search progress. Additionally, the number of tests
along with the number of matching tests are displayed.
If you repeat the extended query, click Search Now again to activate the search
criteria.

Data Explorer — User’s Guide

70 Data Explorer

1.5.6.2 Creating a ComposerFile from the Results of a Search Query in Data Explorer
If you activate the Collect Results into new ComposerFile check box, the
results of a search query are exported directly to a ComposerFile and displayed
in Channel Browser. A dialog opens where you define the properties of the
ComposerFile:

Fig. 53

ComposerFile name
Defines the name of the new ComposerFile.
ComposerFile alias
Like any other opened file, ComposerFiles are provided with an alias by which
they can be unambiguously addressed.
Defines the alias for the ComposerFile. The alias must be unique, otherwise you
are prompted to specify a new alias.
Key
Specifies the name of the new data key.
Description (optional)
Specifies the descriptive text for the new data key.
Automatically take over data key names from source data keys
If you deactivate this check box, you can enter a data key name and a data key
description.
For the ComposerFile, both definitions are taken from the source, by default.
Copy only records that match the filter criteria:
The data filter allows you to take over only those data from the source into the
ComposerFile whose data values match certain criteria (see also the documen-
tation about the User Interface Functionalities, under Special Functionalities -
Selective Data Transfer)
These criteria are defined in the form of data filter conditions. Data filter condi-
tions may either be entered or modified in the form of text as an expression in
the corresponding edit field or via the Filter Conditions Editor. The Filter Condi-
tions Editor can be called by using the Edit Condition button (see the documen-

Data Explorer — User’s Guide

Data Explorer 71

tation about the User Interface Functionalities, under Special Functionalities -

Filter Conditions Editor)
The data filter is applied to the source data and only those records are copied to
the ComposerFile that satisfy this filter condition.
Add channels "_SourcePath_" and "_SourceBaseValue_" for back refer-
ence to original data
In the "_SourcePath_" channel the path to the data key is entered from which the
corresponding record was transferred (source of the data).
In the channel "_SourceBaseValue_" the base value (x-value) of the corre-
sponding record is entered in the form it originally existed.
By combining these two values the record copied to its target location can be
traced back to its source.
ComposerFile data is embedded in Layout
This check box can be used to define whether the ComposerFile is to be auto-
matically saved in the layout. This is useful if you are using the ComposerFile to
create parameter data for calculations that is used in the layout. When the layout
is loaded, this parameter data is reloaded with the ComposerFile for further use.

1.5.6.3 Context Menu (Search Results Window)

Right-clicking a result in the search results window opens a context menu which
contains the following options:
Locate Test (only available if server supports extended queries)
Finds the corresponding test in Data Explorer, as long as the current line
represents some item belonging to a test (i.e. Test, Measurement or Mea-
surementQuantity).
If you try to locate a test which is not available in DataExplorer because it
does not match the current filter conditions, CONCERTO outputs a warning.
You can avoid getting this dialog by setting DialogOnNavigateFail=0 in con-
certo.ini. The message will still be displayed.
Open
Opens the test, unless it is already open.
Close
Closes the test, unless it has already been closed.
Copy to ComposerFile
Copy the data to a ComposerFile.
For more on this topic, see the documentation about the User Interface
Functionalities, under Editing Data.
Test Context Script
If you define a file context script, as described under Data Source Proper-
ties - Context on page 100, the name of the defined script appears in the
context menu from where it can also be executed.
Double-clicking a result opens the test in Data Explorer (like Locate Test).
If the DXV entry DeletedTestFlag is set as a test attribute, that test is not
returned by the extended query (see ASAM Properties - Tests on page 107).

1.5.7 User Variables in Filter Conditions

Standard filter conditions, extended queries and search criteria may apply user
variables instead of fixed values. The user variable value is displayed in blue in
the header of the search results window in the complete filter condition.
You can edit the value of the user variable by double-clicking it.

Data Explorer — User’s Guide

72 Data Explorer

Fig. 54

If the user variable is part of the standard filter or the extended query, the test list
of the first filter is recalculated.
If the user variable is part of the search criteria, no new search must be started.
The True/False attributes of the tests are automatically refreshed.

Data Explorer — User’s Guide

Data Explorer 73

1.6 Adjusting the Data Environment

1.6.1 Data Environment File (DXV)

Data Explorer saves the information about all data sources needed for later
sessions in special files, so-called DXV Files. These data environment files
contain all of the definitions that were set in the Properties of each data source
(e.g. file paths, folders and available formulas).
It is possible to load more than one data environment simultaneously. Each DXV
file currently loaded is displayed as a separate category in the Explorer bar.

Fig. 55

You can change the displayed name by entering a new name under Label in the
relevant DXV file. There are several options to do this:
Label = My Text
Shows "My Text" as a category in the Explorer bar.
Label = My Text (%s)
Shows "My Text" and, in parentheses, the name of the DXV file without
extension.
Label = My Text (%s)2
Shows "My Text" and, in parentheses, the path and name of the DXV file
with extension.
If no label is found in the DXV file, the category is assigned the name of the
DXV file itself.
All of the DXV files in use are referenced in the concerto.ini file under the entry
EnvironmentFile, which enables them to be automatically displayed as available
data environments at every session.
After initially installing the software, you will not only find the data environment
DemoData for the provided data examples (demodata.dxv file), but also your
personal data environment MyData from the concerto.dxv file in the subfolder
MyLib. If you have very large data volumes and would like to display the data in
various different data environments, you can generate another DXV file manually
and reference it in the concerto.ini file.
In large companies it might be useful if the administrator provided a certain stan-
dard data environment where e.g. the Santorin server or the standard file shares
with measured data could be located. Then the users would no longer need to
generate these data sources themselves. For this purpose, a special DXV file
has to be created and specified under the entry GlobalEnvironmentFile=*.DXV in
the concerto.ini file. This global data environment file is typically a read-only file
on a network drive, so no modifications made by users are written to the file.
Instead, a local copy is created each time the software is started and any
changes are made to the copy. At the beginning of each new session the deter-
mining settings (data format, path/server, etc.) are retrieved from the global data
environment file. Whereas any entries that are very user-specific (filtering condi-
tions or similar) are used from the local copy so that despite global data sources,
it is still possible for users to make certain adjustments. If these options are not

Data Explorer — User’s Guide

74 Data Explorer

sufficient, in other words, if users would like to make changes beyond these
possibilities, it is sufficient to shift the global data source into their own data envi-
ronment, where all changes are possible and remain in effect.

1.6.2 Temporary Data Source

Besides the data environments stored in the DXV files, there is also an auto-
matic, implicit data environment for temporary data sources. If a file is opened
via the My Computer / Network View or directly, via a file dialog, a temporary
data source with the matching format and the path leading to the file is generated
automatically. In this data source Data Explorer also marks this file as open.
Temporary data sources are not saved beyond a session. So if you want to make
such an automatically generated data source persistent for later use, you can
simply shift it into your personal data environment (MyDataSources) via the
context menu (by right-clicking the data source node).
There is another application in which temporary data sources are generated. If
you load a saved layout, a dialog appears that displays the files/tests used in the
layout at the time it was saved. If you just want to open it to continue your
previous session, Data Explorer tries to access the previously used data sources
too (the information is also stored in the layout).
If the data sources are no longer available, the system first checks whether they
might have been renamed since then. If this is not the case, corresponding
temporary data sources are created and used to open the files/tests, provided
they are still located on the same server or in the same folder.

1.6.3 Creating new Data Sources

The following actions will create a new data source:
Opening a file directly via Data Access | Open File on the workflow bar
(see also Exploration Guide, under Basics of Operation)
This method creates a temporary data source. In order to make it available
also in later sessions, select Move Data Source To from this data source's
context menu to add the data source to an already existing data environ-
ment.
My Computer / Calling up Make New Data Source In from a context menu in the My Com-
Network View puter / Network View

Data Source View Click the following toolbar button:

Alternatively Ins key

A new node is created and the Data Source Definition Wizard opens,
which guides you step by step through the process of defining a new data
source.

Data Explorer — User’s Guide

Data Explorer 75

Fig. 56

For ASAM data source, see Creating an ASAM-ODS Data Source on

page 103.
1. On the first page you are prompted to select which file format this data
source will read.
The list of available formats also includes formats from templates as speci-
fied in the data environment file (see Data Source Templates on page 91).
2. Click Next.
The second page defines the data location. If you selected a file-based data
format on the first page, a file/folder selection dialog will appear.

Fig. 57

With the filter type to All Files, you will see files and folders and can select
the data file you wish to read in this data source.
With the file type set to Folders Only, you can select a folder and click OK.
This enables you to select an empty folder.
The Wizard may terminate at this point if no more information is required.
However, some formats depend on auxiliary files (Dictionaries) to work cor-
rectly. If that is the case, you are prompted to define them on the final page.
3. Close the Wizard by clicking Finish.

Data Explorer — User’s Guide

76 Data Explorer

It is also possible to drag a data file from Windows Explorer to an empty spot
below Data Explorer's data source list.
In this case, the source path is already defined by the file which was dropped
and Data Explorer attempts to identify the correct file format based on its exten-
sion. You can influence the decision process by defining your own data source
templates as explained in Data Source Templates on page 91.

1.6.4 Organizing Data Sources

The Explorer bar can be used to organize data sources.
To delete a data source, select it and press the Del key or select Delete Data
Source from the context menu.
Data sources can be inserted into the same or another data environment via the
context menu or by using the standard Copy or Cut key combination.
Since all data source names within a data environment have to be unique, Data
Explorer gives a copy of a data source a temporary name (Copy 1 of xxxx).
Data source names can easily be changed in the Explorer bar, in the same way
as you would change a folder name in Windows Explorer. If you enter a new title
which is already in use by another data source, the changes are rejected and the
title remains unchanged.

1.6.5 User Variables

A data source can use User Variables to define paths and filter conditions more
dynamically. User variables are wildcards for strings which can be substituted
with actual values during run time. They should begin with %, which not only
indicates the start of the user variable but also means that they will be saved in
the uservariables.ini file ready for the next session. Following the initial "%", user
variables can contain any alphanumeric characters and underscore ("_").

Example
%engine
%project

User variables may be saved with a work environment or with a layout. As the
variables are additionally given the specific names %CWF_ (for work environ-
ment) or %CLY_ (for layout), the user variables are either saved with the current
work environment or the layout and are retrieved together with these whenever
they are reloaded.

1.6.6 Path Definitions

Data sources referencing physical files need a path definition specifying a folder
from where the files are to be read.

1.6.6.1 Using Path Wildcards

By default, the data sources are shown in a hierarchy with all the contained
subfolders. You can change this behavior by deactivating the check box
Recurse into sub-folders in the Data Source Properties dialog (see Data
Source Properties - Data Source on page 94).
It is, however, also possible to define specific data paths with wild-card levels,
which gives you more control but also entails certain limitations.
With the following path definition you will see two selection levels under the data
source before you are shown the list with files (*.*):

Example
N:\DATA\*\*\*.*

Data Explorer — User’s Guide

Data Explorer 77

When you expand a data source like this in the Data Explorer’s tree, you are
presented with all the folders under N:\DATA. Expand one of these folders and
you will see the folders it contains, and so on.
This strategy helps even to make complex structures clear without having to
create a separate data source for each folder.
One drawback of this mechanism is that, if any of the wildcard levels involves
many folders, it could take some time to collect the folder names (especially on a
network drive), and the tree will be filled with an unmanageable number of
entries.
For this reason, you can define a user variable as one of the path levels in place
of the wildcard. Suppose your data structure is, for example, organized under
N:\DATA\PROJ1 by engine number folders containing the data files:

N:\DATA
\PUMA
\ENG1234
\ENG1235
\ENG1236

etc.
Here you can define the data path as:
N:\DATA\PROJ1\%engine\*.*

Now Data Explorer will resolve the value of %engine at runtime. When first
created, it has no value and therefore resolves to “*”, giving a complete list of
engine folders. If you change the value to “ENG1235”, Data Explorer no longer
has to find all the engine folders and only this one will be entered in the tree.
Data Explorer shows the current path in the path line below the toolbar. When a
data path contains user variables, the current value is shown in blue and can
easily be changed by double-clicking it and editing in place. Alternatively you can
click the "%" button on the toolbar to launch a dialog for modifying the user vari-
ables.
Note that you can also use wildcards in setting the value of a user variable. For
example, you can set %engine to “ENG22*” which will return all engines begin-
ning with "ENG22".

Example
You may of course also use multiple user variables e.g.
N:\DATA\%project\%engine\*.*

The values of user variables are kept in the uservariables.ini file for the next
session.

Information

User variables used in the data path may not contain the following characters:
":", ";", ".", "\", "/", "(", ")", "%", "_"

Data Explorer — User’s Guide

78 Data Explorer

1.6.6.2 Multiple Paths

It is possible to specify several folder paths in a Data Explorer data source but
certain rules have to be obeyed.
The decisive factor is always the folder level from which the paths first start to
differ:

Examples
N:\aaa\projects\*\*\*..
N:\aaa\concepts\*\*\*..

In the example above, the paths start to differ at folder level 3 (N = Level 1,
aaa=Level 2).
This level can change, however, when a new path is added:
N:\aaa\projects\*\*\*..
N:\aaa\concepts\*\*\*..
N:\bbb\*\*\..

Now the paths differ from Level 2.

The following two rules apply to the folder level from which the paths start to
differ:
Rule 1: The folders at the level from which the paths first start to differ must have
different names!
That also applies when the paths start to differ at Level 1 (i.e. at the letter for the
drive). No two paths may then lead to the same drive.

Example
Not valid (because folder name aaa occurs twice):
N:\aaa\projects\*.dat
N:\aaa\concepts\*.dat
N:\bbb\*\*.dat

Correct:
N:\aaa\*\*.dat
N:\bbb\*.dat

Rule 2: No files may be located at the level from which the paths first start to differ!

Example
Not valid (because both folders and files are to be read from Level 3 – the first
level from which the paths start to differ):
C:\abc\spec\*.dat
C:\abc\*.dat

Correct:
C:\abc\spec\*.dat
C:\abc\std\*.dat

Structures of any depth and complexity are permissible in the individual paths
after the folder level from which the paths first start to differ.

Example
Valid path definition:
D:\Files\aaa\*\*\*\*\*.*
D:\Files\bbb\*\*\*.*

The reason for these apparently complex rules is that Data Explorer tries to
display only the actual variable part of the path. The constant first part (i.e. drive

Data Explorer — User’s Guide

Data Explorer 79

and same root folder) is suppressed. The same applies to the file references
stored in a layout, and in the event that you want to address a file directly in a
script. To do that the data source name is needed (with which Data Explorer
associates the initial part of the path that is the same for all paths) and the test
path which includes the remaining subfolders up to the actual file name.
If the complete data structure is moved to another server, or if a user has another
drive definition, it is sufficient to change it in the data environment file for the
respective data source. The navigation when opening a layout remains unaf-
fected as well as any scripts that access files.

1.6.6.3 Defining Company-wide Paths

It is often convenient to define a data environment which can be used by anyone
in the company. The global data environment mechanism supports this (see
Data Environment File (DXV) on page 73).
The environment then has to be defined so that the paths it contains are valid for
everyone irrespective of which shares are mapped to which drive letters. In addi-
tion, since formulas and dictionaries are typically stored globally, the strategy
should apply to all paths that can be found in the data environment.
The simplest solution is to use UNC (Uniform Naming Convention) designations
in your path definitions.

Examples
Suppose your data files are stored on computer Abacus and under the share
name TESTDATA. Rather than expect everyone to map drive N: to
\\Abacus\\TESTDATA, you can simply use the UNC path:
\\Abacus\TESTDATA\PUMA\*.DAT.

Another option is to use user variables at the start of paths. For example,
suppose you define a path as:
%Drive:\DATA\AVL\*.TRR

Then each user can have their own setting for %Drive (e.g. “N” or “C”), which will
be saved locally in their INI file.
Alternatively, you could use user variables to define complete source paths. For
example, suppose there are some globally defined steady-state formulas in the
read-only folder \\Abacus\formulae\steady\*.frm. Then you could set the user
variable %SteadyFrm to "\\Abacus\formulae\steady" and define the formula path
as %SteadyFrm\*.frm.

Sometimes it might be necessary to make changes to central formulas. Create a

copy of the formula paths on your local drive and set the user variable value
accordingly, e.g. %SteadyFrm to C:\FORMULAE\STEADY.

1.6.7 DXV File Settings

The following section describes the file format-specific functions that you do not
set in the data source properties in Data Explorer, but only become effective if
you add them or edit the data environment file (*.dxv). The DXV file is structured
like an INI file, with a separate section being available for each data source. The
data source name matches the section name.
This does not apply to the formats ATF, Horiba VETS Export File, MDF and
VAX-based PUMA TRR File, which allow you to set file format specific functions
both in the DXV file and, more conveniently, in the Data Source Properties dialog
(see Data Source Properties - Format on page 92).

Data Explorer — User’s Guide

80 Data Explorer

1.6.7.1 Settings for All File Formats

Entry: Ascii2Time=
Value: Datakey1’DatasetName1=FormatString1 [;
Datakey2’DatasetName2=FormatString2] .. [; DatakeyN’Dataset-
NameN=FormatStringN]
– DatakeyN
Defines the dataset's data key.
– ChannelNameN
Defines the dataset's name.
– FormatStringN
Defines the dataset's source format.
By setting the entry Ascii2Time= it becomes possible to display in
Microsoft time format datasets containing time-related information in
the form of a string, which is not, however, fully compliant with the sup-
ported time format.

Example
Ascii2Time=D‘Zeit=YYY-MM-DD-hh:mm:ss;D‘Time=YYYY/DD/MM hh:mm:ss

The channels D’Zeit and D’Time are displayed as time channels in the Microsoft
time format.

Entry: BitChannels=
Value: Datasets1|BitMask1=BitChannelName1
[, BitMask2=BitChannelName2] .. [, BitMaskN=BitChannelNameN] ..
[; Datasets2|BitMask1=BitChannelName1 [, BitMask2=BitChannelName2]
.. [, BitMaskN=BitChannelNameN] ]
– DatasetsN
Defines the source dataset's name. You may also specify dataset lists
separated by a comma. In addition, wildcards can be used.
– BitMaskN
Defines the bits to be evaluated.
– DatasetsN
Defines the component name of the evaluated bits.
Some measurement systems (e.g. INCA) are known to save several bit
channels in one common channel. For evaluation purposes it is therefore
necessary to extract these individual bit channels from the common channel
they were collectively saved to.
By setting the entry BitChannel= it has now become possible to access
these single bit channels individually. The width and position of such indi-
vidual bit channels may be defined by using a bit mask.
The individual bit channels are displayed as components in a dataset array.

Examples
BitChannels=State,BitChan*|00000001=Ignition

Regarding channel State and all channels that begin with BitChan, the first bit
(bit 0) is cut out and displayed under the respective datasets as component
#Ignition.
BitChnnels=State|00000110=EngineState

Regarding channel State, bit 1 and bit 2 are cut out and displayed as channel
State#EngineState.

Data Explorer — User’s Guide

Data Explorer 81

Entry: HideMeas=
Value: data key names
By setting the entry HideMeas= you can hide a test's data keys.
Multiple entries can be defined separated by semicolons.

Example
[Demo IFiles]
.
.
HideMeas=UTC;CAO

Hides data keys UTC and CAO in all the tests for data source Demo IFiles.

Entry: HideEmptyMeas=
Value: data key names [,1]
If you set the entry HideEmptyMeas=, the defined data keys will be hidden if
they have no formulas and data channels or only formula channels -
depending on the parameter set.
Multiple entries can be defined separated by semicolons. Alternatively, you
can also insert wildcards (*) to set multiple selections.
The table shows when a data key is displayed and when hidden:

No Channels Data Only Formulas Only Data and

Formulas
HideEmptyMeas=XX h s s s
HideEmptyMeas=XX,1 h s h s

Tab. 1

H = Data key is hidden

S = Data key is displayed

Example
[Demo IFiles]
.
.
HideEmptyMeas=UTC

Hides data key UTC for the tests in data source Demo IFiles if it does not
contain data or formula channels.
[Demo IFiles]
.
.
HideEmptyMeas=UTC,1

Hides data key UTC if it only contains formulas and no data channels.
[Demo IFiles]
.
.
HideEmptyMeas=UTC;RecResult*

Hides data key UTC in data source Demo IFiles and all the data keys starting
with RecResult, if it does not have any channels - data channels or formulas.

Entry: InvalidValue=
Value: measurement value
According to AVL convention, numeric values of 1e10 are interpreted as
invalid points for PUMA-based data models.

Data Explorer — User’s Guide

82 Data Explorer

For file formats such as e.g. ATF Data Source or Generic ASCII this does
not apply.
By setting the entry InvalidValue=1e10, however, measurement points of
this value are interpreted as invalid points.
Entry: QueryFiles=
Value: query file path
This entry defines the query file path. A query file contains extended filter
conditions that take effect if this entry is set.
Query files can be used for data stored in folders/drives and for ASAM-ODS
data.
Information on how to create a query file can be found under Extended
Queries on page 56.
Entry: QueryName=
Value: query file name
This entry defines the query file to be executed when the Query / Search
button (magnifying glass) on the toolbar is clicked.
Entry: Recursive=

Information

This setting is also available in the Data Source Properties dialog (see Data
Source Properties - Data Source on page 94).

Value: 0, 1 (default), 2
This entry defines the way the data sources are displayed in the Explorer
bar (data source view).
– Recursive=0
delivers a flat display of the data source, without subfolders. Files in
subfolders are not included.
– Recursive=1 (default)
delivers a structured data display that includes subfolders.
– Recursive=2
delivers a structured data display with subfolders, any empty folders
are hidden.
Entry: ShowChannelAttributes=
Value: Data Key, Attribute1, Attribute2, ...; [Data Key, Attribute1,...]
In the channel list Data Explorer only shows its unit and description in addi-
tion to the actual channel name by default.
By setting the entry ShowChannelAttributes= you can display other channel
attributes for defined data keys.
The attributes to be shown for a data key are defined separated by
commas. Multiple data key definitions (data keys can also be defined with
wildcards) are separated by semicolons.
The following attribute types can also be displayed in the channel list:
ASAM-ODS attributes that refer to the Measurement Quantity table, e.g.
units or quantity attribute.
If only one attribute is referenced, it is displayed from the Measurement
Quantity table.

Data Explorer — User’s Guide

Data Explorer 83

By defining Table.Element you can however also reference an attribute from

another table.

Examples
[Demo PUMA Recorder]
.
.
ShowChannelAttributes=TM*,Count,Resolution

In all the tests for data source Demo PUMA Recorder the additional attribute
Count (number of measurement points) is displayed for all the data keys.
[Demo PUMA Recorder]
.
.
ShowChannelAttributes=*,Count,Resolution,Name,iLocalName,Description,Datatype,
Quantity.Name,Quantity.Default_MQ_Name

In all the tests for data source Demo PUMA Recorder the additional attributes
Count (number of measurement points) and Resolution (only for time-based
data) are displayed for all the data keys. In addition, the attributes Name, iLocal-
Name, Description and Datatype are taken from the related AoMeasure-
mentQuantity elements, and Name and Default_MQ_Name from the related
AoQuantity element.

1.6.7.2 ASAM ODS Data Base

See DXV File Settings on page 111.

1.6.7.3 ATF Data Source

Information

This format-specific setting is also available in the Data Source Properties dialog
(see Data Source Properties - Format on page 92).

Entry: ATFSingleTestMode=
Value: 0 (default), 1
By setting the entry ATFSingleTestMode=1 the files are displayed in a flat
file structure. Wildcards in the data path and multiple data paths are sup-
ported only in this mode.

Data Explorer — User’s Guide

84 Data Explorer

1.6.7.4 Horiba VETS Export File

Information

This format-specific setting is also available in the Data Source Properties dialog
(see Data Source Properties - Format on page 92).

Entry: HoribaLineOriented=
Value: Pretest
If you set this entry, the contents of the channels ANSWER, PT_CODE and
QUESTION in the PRETEST section are displayed as separate channels.
Here the measurement points of channel PT_CODE are interpreted as the
name, the measurement points of channel ANSWER as the measured
value and the measurement points of channel QUESTION as the descrip-
tion of the channel created.

1.6.7.5 DIGALOG Data File

Entry: DigalogModel=
Value: 0 (default), 1, 2, 3
Given the various views in this file format, you can change the interpretation
(based on the REMARKS table in the Access database) and therefore also
data display by adding the following entries in the relevant section of the
data environment file:
– DigalogModel=0 (default)
Data with non-consecutive block numbers or with a previous change to
the base interval are displayed for a separate measurement in data key
TM.
– DigalogModel=1
All the measurement points are shown as logpoint-based data in data
key D irrespective of their actual base.
– DigalogModel=2
Data with non-consecutive block numbers or with a previous change to
the base interval are displayed as a separate data key T.
– DigalogModel=3
All the measurement points are shown in data key TM. The basis is
taken from the time stamp for the individual measurement points.

1.6.7.6 IFile
Entry: ExternalVolumeFile=File Path
Value: file path
In particular engine configurations it may be necessary to have the volume
curve calculated not from the parameterized engine geometries but by
accessing a separately stored file. This file can be set individually for each
data source (e.g. Acquisition or IFile) via the entry ExternalVolumeFile=File-
path in the concerto.dxv file.
The volume curve must be stored in an ASCII file which contains a column
each for the degrees CA (X-axis) and the volume values.
Currently, external volume curves are considered in RTP- and CalcGraf
functions, but not in burn and GCA calculations.
Changing the volume file during measurement operation:
If the volume file is exchanged during the measurement, the new volume
curve will only be taken over after the measurement parameters are
reloaded.

Data Explorer — User’s Guide

Data Explorer 85

1.6.7.7 MATLAB MAT File

Entry: MatlabTranspose=
Value: 0 (default), 1
If you set the entry MatlabTranspose=1, the columns and rows in the
MATLAB file to be read in are transposed.

1.6.7.8 MDF File

Information

These format-specific settings are also available in the Data Source Properties
dialog.

Fig. 58

Source for key description

Entry: MDFKeyDescription=
Value: 0 (default), 1, 2, 3, 4
This entry defines from which field in the MDF file the text for the data key
description is taken. The following options are available:
– Setting Concerto default (default) or
entry MDFKeyDescription=0
The base type of the data is used as data key description.
– Setting cg_tx_acq_name or
entry MDFKeyDescription=1
The data key description is taken from the field cg_tx_acq_name in the
MDF file.
– Setting si_tx_name or
entry MDFKeyDescription=2
The data key description is taken from the field si_tx_name in the MDF
file.

Data Explorer — User’s Guide

86 Data Explorer

– Setting si_tx_path or
entry MDFKeyDescription=3
The data key description is taken from the field si_tx_path in the MDF
file.
– Setting cg_md_comment or
entry MDFKeyDescription=4
The data key description is taken from the field cg_md_comment in the
MDF file.
Show measurements under data key
Entry: MDFShowMeasurement=
Value: 0 (default), 1
Only the ASAM-ODS file format has measurements within one data key. By
setting On or specifying the entry MDFShowMeasurement=1 CONCERTO
also displays measurements within the Recorder data key for this file
format.
Common data key for all channels
Entry: MDFSingleTM=
Value: 0 (default), 1
By setting On or specifying the entry MDFSingleTM=1, the signals are not
split up into several TM data keys on account of their resolution.
Channel names
Entry: MDFShowLongNames=
Value: 0 (default), 1, 2
– Setting Short Signal Name or
entry MDFShowLongNames=0 (default)
CONCERTO shows the channel block's signal names as channel
names.
– Setting Long Name or
entry MDFShowLongNames=1
By setting the entry MDFShowLongNames=1 you can display channel
names with a length of more than 32 characters.
– Setting Long (Asam) Name or
entry MDFShowLongNames=2
By setting the entry MDFShowLongNames=2 CONCERTO shows the
display name defined in INCA as channel name, if it is availabe in the
data file.
Numeric channels with text table
Entry: MDFStringChannels=
Value: 0 (default), 1, 2
– Setting Numerics or
entry MDFStringChannels=0 (default)
By setting the entry MDFStringChannels=2 data values of channels of
type String (in tables, form tables and cursor windows) are displayed
numerically.
– Setting Strings or
entry MDFStringChannels=1
By setting the entry MDFStringChannels=1 data values of channels of
type String (in tables, form tables and cursor windows) are displayed
alphanumerically.

Data Explorer — User’s Guide

Data Explorer 87

– Setting Both or
entry MDFStringChannels=2
By setting the entry MDFStringChannels=3 data values of channels of
type String are displayed numerically and alphanumerically.
In diagrams, numeric values are displayed as curves, in tables, form
tables and cursor windows they are shown as text.
Channel definition for channel group text
Entry: MDFChannelGroupText=
Value: <Name>
In MDF files, channel group texts may be defined. These texts describe
common properties of several channels.
By setting the entry MDFChannelGroupText=<Name> the channel group
texts are displayed as channel properties in Data Explorer.
Source for key name
Entry: MDFKeyName=
Value: 0 (default), 1, 2, 3, 4
This entry defines from which field in the MDF file the text for the data key
name is taken. The following options are available:
– Setting Concerto default (default) or
entry MDFKeyName=0
The base type of the data is used as data key name.
– Setting cg_tx_acq_name or
entry MDFKeyName=1
The text for the data key name is taken from the field cg_tx_acq_name
in the MDF file.
– Setting si_tx_name or
entry MDFKeyName=2
The text for the data key name is taken from the field cg_tx_name in
the MDF file.
– Setting si_tx_path or
entry MDFKeyName=3
The text for the data key name is taken from the field cg_tx_path in the
MDF file.
Language for header channels
Entry: MDFHeaderChannelLanguage=
Value: 0 (default), 1, 2, 3, MLG
This entry defines the language in which the HD data key's channel names
are displayed.
– Setting ENG or
entry MDFHeaderChannelLanguage=0 (default)
e.g. “$Date”, “$Time”, etc.
– Setting GER or
entry MDFHeaderChannelLanguage=1
e.g. “$Datum”, “$Zeit”, etc.
– Setting FRE or
entry MDFHeaderChannelLanguage=2
e.g. “$Date”, “$Heure”, etc.
– Setting MLG or
entry MDFHeaderChannelLanguage=3
In this case, the language set in CONCERTO is used in the user inter-
face.

Data Explorer — User’s Guide

88 Data Explorer

Still adjustable exclusively via an entry in the DXV file:

Entry: MDFVMThreshold=
Value: 10 (default)
By setting the entry MDFVMThreshold=file size, files exeeding the defined
file size can be read in with optimized memory utilization.

1.6.7.9 Multi ASCII File Types

Information

This format-specific setting is also available in the Data Source Properties dialog
(see Data Source Properties - Format on page 92).

Entry: Dictionary1=MULTIASCII, File Path

Value: multiascii.ini file path
This entry defines the path to the multiascii.ini file that has to be indicated
when creating a new data source.
When creating a data source, the path to multiascii.ini file is generated auto-
matically with the result that this entry does not normally need to be
changed.
Entry: MultiAsciiSettings=Subformat
Value: sub-format name
This entry defines the sub-format if several sub-formats are defined in the
multiascii.ini file. Sub-formats can be identified in the multiascii.ini file by
their square brackets.

1.6.7.10 PUMA Recorder File

Entry: TimeBase=
Value: base name, unit, description
If you set the entry TimeBase=BaseName,Unit,Description you can change
the basic information for files of this format.
When the entry is not set, TIME, sec. and Elapsed Time will still be
assumed to be the base name, unit and description.

1.6.7.11 RedLine (ACAP/CAS) File

Entry: DspSignalAsChannel=
Value: 0 (default), 1
CONCERTO displays the file name as the channel name by default. If you
set the entry DspSignalAsChannel=1, the attribute SIGNAL is used for
channel name display.

Data Explorer — User’s Guide

Data Explorer 89

1.6.7.12 Script-based Tests

Entry: LogptBase=
Value: base name, unit, description
If you set the entry LogptBase=BaseName,Unit,Description you can change
the basic information for files of this format.
If the entry is not set, Logpt and Logpoint based data will still be assumed to
be the base name and description.
Entry: TimeBase=
Value: base name, unit, description
By setting the entry TimeBase=BaseName,Unit,Description you can
change the basic information for channels of this format.
If the entry is not set, Time, sec. and Elapsed Time will still be assumed to
be the base name, unit and description.
Entry: CrankAngleBase=
Value: base name, unit, description
By setting the entry CrankAngleBase=BaseName,Unit,Description you can
change the basic information for channels of this format. If the entry is not
set, CDM, deg. and Crank Angle will still be assumed to be the base name,
unit and description.
Entry: CycleBase=
Value: base name, unit, description
By setting the entry CycleBase=BaseName,Unit,Description you can
change the basic information for channels of this format.
If the entry is not set, Cycle and Cycle Number will still be assumed to be
the base name and description.

1.6.7.13 VAX-based PUMA TRR File

Information

This format-specific setting is also available in the Data Source Properties dialog
(see Data Source Properties - Format on page 92).

Entry: TRRShowMeasurement=
Value: 0 (default), 1
Only the ASAM-ODS file format has measurements within one data key. If
you set the entry TRRShowMeasurement=1, CONCERTO also displays
measurements within the data key for this file format.

Data Explorer — User’s Guide

90 Data Explorer

1.6.8 Date Displays

1.6.8.1 ASAM-AODS
The entry AodsDateFormat=%Y %b %d %X in the concerto.ini file allows you to
format the display of the date type attributes. The format can be freely defined
using a format string. The format settings defined here relate only to ASAM
attributes of type Date in the Data Explorer list view and in the Attribute Editor.
The unformatted ASAM date is still used for date attributes in filters.
The Data Explorer list is sorted chronologically based on the formatted date.

Example
AodsDateFormat=%d %B %YI %X delivers:
03 Jan 2003 10:30:02

For the meaning of the various elements in the format string, see the list under
File System on page 90.

1.6.8.2 File System

You can format the date and time display in the file/test list by means of the File-
DateFormat=<date-fmt>|<time-fmt> entry in the concerto.ini file.
If a formatted date is used as the sort attribute in Data Explorer, the list is sorted
chronologically based on the formatted date.

Example
FileDateFormat=%Y-%m-%d|%I:%M%p
2003-01-03 2:06PM

The various elements in the format string are explained below:

%a abbreviated weekday name

%A full weekday name
%b abbreviated month name
%B full month name
%c date and time as in system settings
%d day of month as decimal number (01 – 31)
%H hour in 24-hour (00 – 23)
%I hour in 12-hour (01 – 12)
%j day of year as decimal number (001 – 366)
%m month as decimal number (01 – 12)
%M minute as decimal number (00 – 59)
%p a.m./p.m. indicator for 12-hour display
%S second as decimal number (00 – 59)
%s millisecond as decimal number (000 - 999)
%U week of year as decimal number, with Sunday as first day of week (00
– 53)
%w weekday as decimal number (0 – 6; Sunday is 0)
%W week of year as decimal number, with Monday as first day of week (00
- 53)
%x date as in system settings
%X time as in system settings

Data Explorer — User’s Guide

Data Explorer 91

%y year without century, as decimal number (00 – 99)

%Y year with century, as decimal number
%z time zone or abbreviation; no characters if zone is unknown
%Z
%% percent sign

Some of the formatting codes may be preceded by the flag #. In this case, the
meaning of the formatting codes is as follows:

%#c Long representation of date and time according to system settings

(e.g.: "Tuesday, March 14, 2010, 12:41:29")
%#x Long representation of date according to system settings (e.g.:
"Tuesday, March 14, 2010")
%#d Preceding zeros are removed (if any).
%#H
%#I
%#j
%#m
%#M
%#S
%#U
%#w
%#W
%#y
%#Y

1.6.9 Data Source Templates

Often many settings have to be specified when creating new data sources. For
this reason, it is possible to define data source templates in the DXV file so that
you only need to specify the settings once. Templates define dictionaries,
formulas and advanced settings, but without the definition for data path. Such
templates are offered for selection in the Data Source Properties dialog like
separate file formats.
These template entries in the DXV file look like normal data sources but are
distinguished by having a tilde (‘~’) as the first character of the section name.

Example
[DataExplorer]
Version=1

[~DataC Files]
Format=DATACFIL,ASCFILE
FileSpec=*.1
Dictionary1=GENERIC,DATAC,%ConcertoDescDir\datac.dsc
Converter=DATAC,c:\condata\AVL\DATAC\DATAC.PIF %1 %2
Formulas=FRM,Formulas,c:\formulas\steady\*.frm

[~IFiles]
Format=IFILE,IFILE
FileSpec=*.*
Formula1=CA,Crank Angle Formulae,%ConcertoTmpDir\IndiFormula\caf\*.frm
Formula2=CY,Cycle Based Formulae,%ConcertoTmpDir\IndiFormula\cyf\*.frm
Formula3=VAL,Result Values,%ConcertoTmpDir\IndiFormula\val\*.frm
Formula4=TM,Time Based Functions,%ConcertoTmpDir\IndiFormula\tmf\*.frm
Formula5=MSC,Miscellaneous,%ConcertoTmpDir\IndiFormula\msc\*.frm
Formula6=STA,Result Statistics,%ConcertoTmpDir\IndiFormula\sta\*.frm
Formula7=CAF,Crank Angle Formulae,%ConcertoTmpDir\IndiFormula\caf\*.frm
Formula8=CYF,Cycle Based Formulae,%ConcertoTmpDir\IndiFormula\cyf\*.frm

Data Explorer — User’s Guide

92 Data Explorer

With such template entries at the top of the DXV file, Data Explorer will now
present additional file types in the list of formats on the Format page of the Data
Source Properties dialog (see Data Source Properties - Format on page 92).
The Format= statement defines the default alias for this format (e.g. DATACFIL)
and the actual internal file format which is known to Data Explorer (ASCFILE).
The FileSpec= statement tells Data Explorer which data file suffixes to associate
with this entry. When you drag a data file from Windows Explorer and drop it on
the Data Explorer tree, its specification is matched against the definitions from
each registry entry. The first match is chosen as the most probable file type. The
Data Source Definition Wizard simply needs confirmation of the choice, and a
new data source is fully defined using the settings from the registry along with
the path of the data file.

1.7 Data Source Properties

Click this button or select Properties on the context menu to open the Data
Source Properties dialog.

This dialog is used to define all the attributes of a data source. The dialog
contains a list of data sources on the left so that you can select multiple groups
and apply the same changes to them all. You can also easily switch data sources
making various changes without returning to the Data Explorer window.
The dialog consists of the following tabs:

1.7.1 Data Source Properties - Format

The Format property page contains all the information required to tell Data
Explorer how to read the files in this group. If one or two Dictionaries are manda-
tory for the format, fields will be displayed for you to define them.

Fig. 59

Data Explorer — User’s Guide

Data Explorer 93

Data Source Title:

Enter a unique title for this data source. If the title is not unique, it will be
rejected. This field is disabled when multiple groups are selected to ensure
uniqueness.
Data Source Description:
Here you can enter a description text for the data source. The text is then
shown whenever you place your cursor on the data source.
Default Alias:
Enter a default alias name to be used for all tests opened from this group.
Series tests always use the default alias “SERIES”.
File Format:
Select a file format from the list. This list contains all AVL internal, cus-
tomer-specific and user-defined formats. In addition, formats defined by
data source templates are also displayed (see Data Source Templates on
page 91).
Dictionary 1:
Displayed only if the file format requires a dictionary to be defined.
– Type: Data Explorer displays the type of Dictionary which has to be
defined here. If there is more than one alternative, they are all dis-
played in a list so that you can choose one.
– Name (optional): If the Dictionary contains more than one definition,
enter a name here to specify which section to use. For Generic ASCII
and Binary descriptor files, this should correspond to the FILE state-
ment in the descriptor file (see Reading ASCII and Binary Files with
Descriptor (Syntax) on page 151). This field is hidden if it is not
required.
– Path: Enter the path of the Dictionary. The following button allows you
to browse for the correct path:

User variables (see User Variables on page 76) should be entered

manually if you want to define a flexible path.
Dictionary 2:
Displayed only if the file format requires a second Dictionary to be defined.
– Type: Data Explorer displays the type of Dictionary which has to be
defined here. If there is more than one alternative, they are all dis-
played in a list so that you can choose one.
– Name: If the Dictionary contains more than one definition, enter a
name here to specify which section to use. It should correspond to the
FILE statement for Generic ASCII and Binary descriptor files (see
Reading ASCII and Binary Files with Descriptor (Syntax) on page 151).
This field is hidden if it is not required.
– Path: Enter the path of the Dictionary. The following button allows you
to browse for the correct path:

User variables (see User Variables on page 76) should be edited man-
ually if you want to define a flexible path.
Format-specific settings:
The Format property page provides additional settings for the ATF, Horiba
VETS Export File, MDF and VAX-based PUMA TRR File formats.
For a description of the individual functions, see the following sections:
– Settings for All File Formats on page 80
– ATF Data Source on page 83
– Horiba VETS Export File on page 84

Data Explorer — User’s Guide

94 Data Explorer

– MDF File on page 85

– VAX-based PUMA TRR File on page 89
multiascii.ini path definition
(MultiAscii File Types format only)
On the Format property page of a data source of format MultiAscii File
Types you can define the path to the multiascii.ini interpretation file. When
creating a new data source, enter the path to the multiascii.ini interpretation
file.
Select the corresponding format from the MultiAscii Subformats list. This
enables you to set the data source to a certain multiascii.ini file and a fixed
ASCII sub-format, which, for example, is made available centrally or saved
in a layout or work environment.
For more on this topic, see Multi ASCII File Types on page 36.
Run Conversion Program
Activate this check box if the data file has to be converted to a format which
is supported by Data Explorer. When checked, the command line must be
defined:
Command Line
Enter the name of the program that will carry out the conversion, usually the
name of the EXE, BAT or PIF file. The following button allows you to browse
for the correct path:

The input and output argument wildcards, however, have to be added man-
ually, e.g. C:\CONVERT.EXE %1 %2.
Using this syntax, the input and output parameters are passed between
double quotes (") to the conversion program to ensure correct conversion
even if blanks occur in the arguments.
By setting the entry LegacyConverter=1 in the concerto.ini file the parame-
ters are passed to the conversion program between double quotes (").

1.7.2 Data Source Properties - Data Source

The Data Source property page is used to define where the engine test data is
located. The content varies, depending on whether the data is located in the file
system or on an ASAM Server.

Data Explorer — User’s Guide

Data Explorer 95

Fig. 60

Data Paths
This list defines all the paths to your data files.
The buttons at the top of the list allow you to add a new entry, delete an
entry, move an entry up and move an entry down.
You can edit entries directly by double-clicking them or click this button to
browse for the folder containing the files:

Path Definitions on page 76 describes how data paths can be defined.

Recurse into sub-folders
If you activate this check box, the files are displayed in a flat file structure,
without subfolders.
If you activate this check box, the data source is displayed in a hierarchy
together with all its subfolders. This makes it possible to also access data
files located in subfolders in the data source’s specified path. This setting is
the standard setting for newly created data sources.
– Hide Empty Branches
If you activate this check box, empty folders are hidden.
Please note that the hiding of empty folders may take more time, espe-
cially if you are working with network drives.
Enable Extended List
Activate this check box if you want the test list to contain additional columns
of attributes read from each file (see Test Attributes in File System Data
Sources on page 50).
Cache to File
If the extended list is enabled, you should enter a file here where Data
Explorer can cache the attributes. This button allows you to browse for the
correct path:

Data Explorer — User’s Guide

96 Data Explorer

Filter Conditions
This list defines all the conditions which should be applied to reduce the
number of tests presented. The buttons at the top of the list allow you to add
a new entry, delete an entry, move an entry up and move an entry down.

1.7.2.1 Data Source Property Page for ASAM-ODS Servers

Fig. 61

Server Name
Enter the name of the computer containing the database and ASAM-com-
pliant server.
Santorin Registry/RPC Number (RPC Interface):
Select a server name from the drop-down list or, if no Santorin Environment
is available, select the RPC number provided by the server. This is normally
a nine-digit decimal value.
For further details, contact your Test Bed Administrator.
Port (Corba Interface)
Number specified in the ASAM-ODS 5 server.
Context (Corba Interface)
Select the required environment.
Version
Select the version which corresponds to your ASAM server version.
Additional Parameters
Free-format edit box where you can enter additional parameters, for
example DB_LOGIN=, NameAttr1= etc.
Advanced
Click this button to open the dialog for advanced ASAM-ODS properties
(see Advanced ASAM Properties on page 106).

Data Explorer — User’s Guide

Data Explorer 97

1.7.3 Data Source Properties - Formulae

Formula Channel If a data key for a normname also contains a formula channel of the same name,
Precedence only the measurement channel is displayed.
Activate this check box to change the display priority and to display the formula
channel. The measurement channel is then hidden by the formula.
Formula Defini- The Formulae tab defines which formula groups should be made available for
tions the files of this data source. Via formula groups, packages of formula channels
can be shown in the tests under a separate or an existing data key. The buttons
at the top of the list allow you to add a new entry, delete an entry, move an entry
up and move an entry down.

Fig. 62

Double-click an entry or press the Ins key to open the Formula Definition dialog
box.

Fig. 63

Data Explorer — User’s Guide

98 Data Explorer

Name:
Name of the formula group. This is a text that describes the formula group
and is used as data key name.
Linked to Data Key:
Defines under which data key your formulas are displayed in Data Explorer.
Entering e.g. "D" in this field will display the formulas in all files containing a
"D" data key together with the measurement channels of "D". Entering a
new name like "FRM", for example, will automatically create a new, virtual
data key which will be displayed in all files of the data source. This data key
contains all formulas from the relevant folder. The name of the data key
should be as short as possible.
Formula Paths:
This list defines all the paths to the formula files. The buttons at the top of
the list allow you to add a new entry, delete an entry, move an entry up and
move an entry down. Path definitions can be entered directly or using the
following button:

If the All Formula Types box is checked, all formulas with the *.FR? exten-
sion are displayed. Otherwise, only the formulas with extension *.FRM are
filtered.
Formula Dependen- See Hiding Formulas that are Not to Be Calculated on page 145.
cy File

1.7.4 Data Source Properties - Advanced

The Advanced tab is used to define various settings that can be applied to a data
source. Under normal circumstances, these fields are empty as they are only
required when using the advanced features of Data Explorer.

Fig. 64

Data Explorer — User’s Guide

Data Explorer 99

Hide Data Source

Activate this check box if the data source is not to be displayed in the Data
Explorer window. This feature is useful, for example, if your data is
embedded in another data source and not to be displayed in isolation. This
can also be switched on from the Embed dialog box.
Group Channels:
Activate this check box if data in this group contains similar channels of mul-
tiple cylinders, typically used for indicating data where there are channels
ending with figures – for example, CYLPR1, CYLPR2 ... CYLPRn. The
trailing number is the cylinder number. When this check box is activated, the
cylinders are represented by CYLPR*(1..n) with an additional hierarchy
level below containing the individual cylinders. As long as these are not
expanded, the size of the channel list is dramatically reduced. If you drag
such a combined name into a diagram, all component channels will go with
it.
Raise Pen on Invalid
Activate this check box if normnames contain invalid measurement points.
The pen is then lifted at invalid measurement points when the normnames
are plotted in diagrams. No curves are then plotted for invalid measurement
points.
Embed Data from Data Source
This list defines the data sources from which data is to be embedded in this
data source's tests. The buttons at the top of the list allow you to add a new
entry, delete an entry, move an entry up and move an entry down.
The Embed dialog is used to edit an entry.
See Embedded Data on page 147 for information about embedding data.
Temporary Channel Table
If required, enter the parameters defining a table with temporary channel
names that are to be found in the tests.

Example
“$T,TMP_ORG,TMP_NAME,TMP_UNIT,TMP_DESC,TMP_NCD”.

See Temporary Channels on page 143 for information about temporary chan-
nels.

Measurement Splitting
If required, enter the parameters defining how data in this group should be
split into measurements.

Example
“D’CURVENUM;SD'$KEY,8,6”.

See Splitting Data into Artificial Measurements on page 129 for information
about splitting measurements.

Run Macros on loading channels

If required, enter the parameters defining macros to be executed when
channels are loaded:

Example
“D’approx3;KF’approx2”.

See Load Data Macros (Repeated Points Filter) on page 146 for information
about executing macros when loading channels.

Data Explorer — User’s Guide

100 Data Explorer

Only include these meas.types in opened measurements

When a measurement is opened as a virtual file, all the data keys in the test
are usually available. If you create a list of data keys separated by semico-
lons, the data keys available are restricted to the defined ones.

Example
„$M;!E“

See Measurements on page 45.

Translate Data Key Names

This setting is used to translate the data key names. The defined data key
names are then used instead of the data keys that are stored in the data.

Example
AD=$B;ED=$E;D=!E

Normnames that were previously displayed in data key AD, for example,
are now displayed in data key $B.
Wildcards, e.g. "StoreTest*=ST", can also be used.
This setting is particularly useful when you want to use a layout for different
data. You can also use it to compare data even if the measurement names
are different.
Translate Channel Names
Data Explorer provides powerful features for translating the channel names
used in tests for the display, and for converting units.
For more on this topic, see Translating Channel Names and Converting
Units on page 140.

1.7.5 Data Source Properties - Context

Fig. 65

Data Explorer — User’s Guide

Data Explorer 101

Data Source Context Scripts:

The scripts entered here are displayed in the context menu that appears
when you right-click the data source. You can start the scripts from here.
The parameters given below are assigned to the script:

Example
First line of the script:
arg Parameter1

Parameter1: Name of the data source.

Test Series Context Scripts:

Example
First line of the script:
arg Parameter1

Parameter1: name of data source and selected test series (data source/test
series).

Test Context Scripts

The scripts entered here are displayed in the context menu that appears
when you right-click a file in the data source. You can start the scripts from
here. The parameters given below are assigned to the script:

Example
First line of the script:
arg Parameter1

Parameter1: name of data source and selected test (data source/file name).

In addition, if you define names for the context scripts, you can assign cer-
tain functions on the file context menu with these scripts.
This function is available for the following options on the file context menu:

Test Context Command Name of the Context Script

Open _open.csf
Create Series of Log Point Data _openAsSeries.csf
Close _close.csf

Tab. 2

Example
If the following script is stored by the name _open.csf, the message "Custom
Open-Script is launched" is displayed when you open a file:
arg file
MsgBox("Custom Open-Script is launched",0,"CustomOpen")
aFile = SelFile(file)
aFile.Open

If the following script is stored by the name _close.csf, the message "Custom
Close-Script is launched" is displayed when you close a file:
arg file
MsgBox("Custom Close-Script is launched",0,"CustomOpen")
aFile = SelFile(file)
aFile.Close

Data Explorer — User’s Guide

102 Data Explorer

If a test context script is applied to a multiple selection, the script is

launched and executed for each element in the multiple selection by default.
If you insert the comment //Merging in the first line of the test context script,
you can change this by setting the test context script only to launch once,
even if there is a multiple selection.

Example
First line contains the comment //Merging:
//Merging
arg file

// from DE test or measurement

group = GetUserVar ("$CURRENT_GROUP")
TraceInfo ("Merging Script Example" + " - $CURRENT_GROUP = " + group)

for i = 1 to file.Count
TraceInfo ("Merging Script Example : file[" + i + "] = " + file.y[i])
TraceInfo ("Merging Script Example : file[" + i + "].FilePath = " +
file[i].FilePath)
TraceInfo ("Merging Script Example : file[" + i + "].FileName = " +
file[i].FileName)
TraceInfo ("Merging Script Example : file[" + i + "].ParentName = " +
file[i].ParentName)
TraceInfo ("Merging Script Example : file[" + i + "].MeasurementId = " +
file[i].MeasurementId)
next i

Channel Context Scripts

The scripts entered here are displayed in Data Explorer on the context
menu for the channel.
They are also displayed in the column context menu of the Composer
spreadsheet. {W}
The parameters given below are assigned to the script, depending on
whether it is launched in Data Explorer or the Composer spreadsheet:
– Call in Data Explorer

Example
First line of the script:
arg Parameter1, Parameter2, Parameter3

Parameter1: name of the data source and test (data source\file name) where the
selected normname is located
Parameter2: name of the data key where the selected normname is located
Parameter3: Data Key’Normname is returned

– Call in the Composer spreadsheet

Example
First line of the script:
arg Parameter1, Parameter2, Parameter3

Parameter1: name of the data source and the test (data source\file name\data
key\measurement) where the selected normname is located
Parameter2: name of the data key where the selected normname is located
Parameter3: Alias:Data Key’Normname is returned

Data Explorer — User’s Guide

Data Explorer 103

Measurement Point Context Scripts

The scripts entered here are displayed on the context menu if you right-click
a measurement point's base column on the Edit tab in a normname's prop-
erties dialog. You can start the scripts from here. The parameters given
below are assigned to the script:

Example
First line of the script:
arg Parameter1, Parameter2, Parameter3, Parameter4

Parameter1: name of data source and selected test (data source/file name).
Parameter2: name of the data key where the normname is located
Parameter3: Alias:Data Key’Normname is returned
Parameter4: point index

External File Editor

Enables an external editor to be opened.
The selected program is opened when you select the context menu option
External Editor.

1.8 Accessing ASAM-ODS Data

ASAM-ODS data can be accessed in the following ways:
From the My Computer / Network view (see Open on page 43)
From the data source view:
ASAM-ODS data can be accessed in the following ways in this view:
– Define an ASAM data source as described below.
– Open the data via the My Computer / Network view (see Open on
page 43) and then create a data source in a loaded data environment
(e.g. My Data Sources by using the Make New Data Source In con-
text menu option.

1.8.1 Creating an ASAM-ODS Data Source

There are the following ways to create a new ASAM data source:
Click the following toolbar button:

Alternatively Ins key

A new node is created and the Data Source Definition Wizard opens,
which guides you step by step through the process of defining a new data
source.

Data Explorer — User’s Guide

104 Data Explorer

The Wizard consists of several pages:

Fig. 66

1. On the first page, you are prompted to select which file format this group will
read. Select ASAM ODS Data Base.
The second page determines the source of the data.
2. Define the server properties:

Fig. 67

Basically, there are two possible scenarios:

– A Santorin Environment is available, with the Santorin Registry Server
controlling the load balancing (i.e. the load of several separate
servers). In this case, the name of the Santorin Environment is dis-
played; the RPC numbers are not shown.
– No Santorin Environment is available. In this case, the available RPC
numbers are listed.
Server Name
Specify the name of the computer which hosts the database.

Data Explorer — User’s Guide

Data Explorer 105

Santorin Registry Server/RPC Number:

Select the name of the Santorin Environment of a server from the
drop-down list or, if no Santorin Environment is available, select the 9-digit
RPC number available in the data administration tool SPACE.
For further details, contact your Test Bed Administrator.
Santorin Registry Server
If it is possible to establish connection via a registry server, this option
button is automatically activated.
ASAM Server
If no Santorin Environment is available, select this option button and enter
the relevant 9-digit RPC number in the edit field above.
If a Santorin Environment is available, this option is not available. When you
try to specify an RPC number, the Santorin Registry Server option will
automatically be selected and you can select the Santorin Registry Server
from the list box above.
ASAM Version
Enter the corresponding version based on the ASAM Server being used.
3. Click Next.

Fig. 68

4. Log-on to the server.

Next, ASAM data sources with a Santorin server need the default login
information. User name and password are always case-sensitive. You can
influence this behavior via an entry in the data environment file.
For more on this topic, see DXV File Settings on page 111, under "Entry:
LoginCaseSensitivity=".

Fig. 69

5. ASAM data sources must have at least one condition defined so the Condi-
tions dialog is now displayed. After checking/modifying the conditions, click
OK to exit the Wizard.
Then you will see the server contents accessible to you with its structural levels.
Like Windows Explorer, the right pane always shows the contents of the branch
selected in the left pane.

Data Explorer — User’s Guide

106 Data Explorer

1.8.2 Advanced ASAM Properties

This properties dialog is opened by clicking the button Advanced on the Data
Source page in the Data Source Properties dialog. If you wish to utilize the
Santorin server's benefits to the full without infringing the ASAM-ODS rules, you
can enter a number of settings in the Additional Parameters field on the Data
Source page. The Advanced ASAM-ODS Properties allow you to edit these
settings as an alternative to typing in the free text field.
After altering the Advanced ASAM Properties, the new settings are displayed in
the Additional Parameters text field. Since all default settings are hidden at this
time, the resulting text can be far shorter than before. In fact, for a Santorin
Server, it is not uncommon to be left with just a default login setting (DB_LOGIN).
Attribute names are not translated in the advanced settings. They still have to be
typed into the Additional Parameters field manually.
The properties dialog contains a picture on the left, and each page has a Help
text. Together, these fields follow your movements around the dialog and display
suitable information to guide you in making the right choice for each parameter.
The tab names shown in this properties dialog are retrieved from the data model
held in the database. Pages correspond roughly to the following model:

Page 1 Server
Page 2 Tests
Page 3 Measurements
Page 4 Quantities (Channels)
Page 5 Units

1.8.2.1 ASAM Properties - Server

Fig. 70

Data Explorer — User’s Guide

Data Explorer 107

On this page you can define general settings regarding the server.
Santorin
Check this box if you have a Santorin Registry Server. CONCERTO can use
this information to enable certain features which are not part of the
ASAM-ODS standard (DXV key SantorinServer).
Logon using Registry
Check this box if you have a Santorin Registry Server and the Windows
Registry contains your logon information (DXV entry UseLastLogin).
Default Login
If the Windows Registry does not contain your logon information, this button
will open the ASAM Login Dialog to set the default (DXV key DB_LOGIN).
Puma Data Model
This check box indicates that there is a PUMA Data Model on the server.
Some features, such as restructuring data, are only available for PUMA
(DXV key DataModel).
RPC Timeout
Enter the maximum time in seconds that CONCERTO should wait for
responses from the server (DXV key Rpc_Timeout).

1.8.2.2 ASAM Properties - Tests

Fig. 71

On this page you can define settings which enable CONCERTO to navigate to
and process tests.
Series Attribute 1/2
Data Explorer creates artificial series names based on two attributes from
the database, separated by a dot. The second attribute, if numeric, can
have an optional length specifier. For example, using iName Id 3 can pro-
duce the series name "Performance Tests.005". Select <Empty> for the
second attribute if none is required. Series names are important when refer-
encing tests from scripts (DXV keys SeriesAttr1 and SeriesAttr2).

Data Explorer — User’s Guide

108 Data Explorer

Test Attribute 1/2

Data Explorer creates artificial test names based on two attributes from the
database, separated by a dot. The second attribute, if numeric, can have an
optional length specifier. For example, using the setting iName Id 4 can pro-
duce the test name "Engine Map.0131". Select <Empty> for the second
attribute if none is required.
Deleted Tests use attribute
Data Explorer can logically delete tests from the context menu. Select the
name of the attribute which has to be set to indicate logical deletion. Tests
are not physically deleted from the database, but those where this attribute
is set to 1 are not displayed (DXV key DeletedTestFlag).
If the AODS data source is Oracle-based, the attribute should be defined as
"not null, default 0" in the data model.
Test Attributes which should be visible in the right-hand pane
Here you can define the test series attributes or test attributes that are to be
visible in the right-hand pane of Data Explorer.
Test Attributes which may be edited
Define the test series attributes or test attributes here that you want to be
available in the test series or Edit Attributes test context menu.
Filter Empty Test Series
Check this box if Data Explorer should hide all test series which have no
tests matching the current filter (DXV key FilterEmptySeries).
– Use standard queries to filter empty branches:
Normally, CONCERTO will use Extended Queries to see which
branches of the test hierarchy are empty. With some versions of San-
torin 3, however, there is a limitation regarding the number of tests
returned. In this case, check this box to force the system to use stan-
dard queries only. Santorin 5.2 no langer has this limitation.
Case Sensitive Filtering
If this field is activated, a distinction is made between upper and lowercase
when the filter conditions are evaluated.

1.8.2.3 ASAM Properties - Measurements

Fig. 72

Data Explorer — User’s Guide

Data Explorer 109

On this page you can define settings which enable Data Explorer to manage
measurements.
Measurement Name
Select the database attributes which Data Explorer is to use for the name of
the data key.
Measurement Ids
Select the database attributes which Data Explorer is to use for measure-
ment IDs. These should be unique within a data key (DXV key MeaVersion).
Measurement Description
Select the database attributes which Data Explorer should use for data key
descriptions (DXV key MeaDescription).
Deleted Measurements use attribute
Here you can define which attribute is used in the data model to mark mea-
surements as deleted. CONCERTO does not display measurements when
the attribute is set to 1.
If the AODS data source is Oracle-based, the attribute should be defined as
"not null, default 0" in the data model.
Base type for data key
Data Explorer uses this information to decide which measurements are
time-based, logpoint-based etc. The first attribute defines the type flag,
while the second defines the resolution when time-based. Check By
Attribute to use these attribute settings or force all data to be log-
point-based or time-based using the other buttons (Log Point Only, Time
Based Only). This is particularly useful when there is no type flag in the
data model (DXV keys MeaBase and MeaTime).
Show all measurements in test
When this field is enabled and a test is selected on the left pane of Data
Explorer, a list with all the measurements contained in that test is displayed
on the right-hand side.
– Measurement Attributes which should be visible in the right-hand
pane
Here you can define the measurement attributes that are to be dis-
played in the right pane of Data Explorer.
Attributes can only be selected if the Show all measurements in test
check box is enabled.
– Measurement Attributes which may be edited
Here you define the measurement attributes that are to be available in
the Edit Attributes measurement context menu.
Sort data according to base channel
Data Explorer can re-sequence data according to the values in the indepen-
dent channel. This is primarily for post-mortem data where the independent
channel contains the TRR key (DXV entry OrderOnIndependentChannel).
Explicit Independent (EI) Channel handling:
In order to define the handling of ASAM-ODS Explicit Independent Chan-
nels, the following options are provided:
– Replace EI base called AVL_INDEP_TIME with point number
(ExplicitIndependentLogpoint=0
ExplicitIndependentName=AVL_INDEP_TIM
This is the default setting and has to be used for AVL PUMA logpoint
measurements. If the EI channel name is AVL_INDEP_TIME, the log-
point number is used as base. The channel AVL_INDEP_TIME is
shown as a separate channel in the channel list. EI channels with other
names continue to be used as base.
– Replace all EI base channels with point number
(ExplicitIndependentLogpoint=1, ExplicitIndependentName=<empty>)
All EI channels are replaced with the point number, independent of
their name. The EI channel is displayed as a separate channel.

Data Explorer — User’s Guide

110 Data Explorer

– Never replace EI base channels

(ExplicitIndependentLogpoint=0, ExplicitIndependentName=<empty>)
EI Channels are used directly as base for all channels of the measure-
ment.

1.8.2.4 ASAM Properties - Channels

Fig. 73
On this page you can define settings which enable Data Explorer to process
channels correctly.
Data Type (Measurement Quantity)
Select the attributes from the MEQ table which Data Explorer is to use to
decide whether a channel is numeric or text (DXV key MeqDatatype).
Description (Measurement Quantity)
Select the attributes from the MEQ table which Data Explorer is to use as
the channel’s description (DXV key MeqDescription).
Data Type (Quantity) Select the attributes from the QTY table which Data
Explorer is to use to decide whether a channel is numeric or text (DXV key
QtyDatatype).
Description (Quantity)
Select the attributes from the QTY table which Data Explorer is to use as
the channel’s description (DXV key QtyDescription).
Numeric Display Width
This attribute in the MEQ and QTY tables defines the number of decimal
places to be displayed when viewing the channel’s data (DXV key DescF-
SizeAttrName).
Make measurement attributes available as virtual channels
Check this box to make measurement attributes appear as pseudo-chan-
nels in all measurements of the data key. These channels begin with '$'
(DXV key VirtualChannels).

Data Explorer — User’s Guide

Data Explorer 111

Show Temporary Names

Normally, CONCERTO uses the names found in the measurement quantity
table. You can override this by checking the box if your temporary names
(from the Quantity table) have a real significance (DXV key ShowTempo-
raryNames).

1.8.2.5 ASAM Properties - Units

Fig. 74
On this page you can define how CONCERTO should interpret the Unit table to
allow automatic conversion to alternative units.
Gain
Select the attribute in the Unit table which CONCERTO is to use as the gain
parameter (DXV key UnitGain).
Offset
Select the attribute in the Unit table which CONCERTO is to use as the
offset parameter (DXV key UnitOffset).
Unit conversion is activated on the Unit tab of a scale’s properties dialog.

1.8.3 DXV File Settings

Entry: AutoRefreshOpenTests=nn (in sec)
Value: seconds
When this entry is set, the data is re-read every nn seconds. This is neces-
sary to be able to access growing Recorder data (CONCERTO used in con-
junction with test bed).
Entry: BaseUnitFromQuantity=
Value: 0 (default), 1
For ASAM-ODS data a normname's unit can be defined both in the Mea-
surementQuantity itself and in the Quantity table.
If the defined units differ in these two tables, the unit from the Measure-
mentQuantity is displayed by default.

Data Explorer — User’s Guide

112 Data Explorer

Setting the entry BaseUnitFromQuantity=1 causes the unit from the Quan-
tity table to be used instead.
Entry: CaseSensitiveChannels=
Value: 0 (default), 1
CONCERTO basically tolerates upper and lowercase channel names. If the
same channel names however appear several times spellt differently, you
can distinguish between them more clearly by setting the entry CaseSensi-
tiveChannels=1, as a serial number is then added to the channel names.
Entry: EnableAodsSecurity=
Value: 0, 1 (default), 2
The AODS standard specifies querying the user's rights for every database
request. This feature can be disabled by setting the entry EnableAodsSecu-
rity=0, which results in faster data access, but in CONCERTO means that
all the menu options are free for all the tests. You can therefore change test
attributes, for example, but do not receive a message in the user interface
as to whether the actions are permissible. Only when the relevant command
is sent to the database will the server reject the action.
If you use the default setting EnableAodsSecurity=1, the rights to the
returned instances will be queried for every database request.
Setting the entry EnableAodsSecurity=2 means that the user's rights to the
relevant instances will only be queried on demand (e.g. when displaying the
context menu or in the Attribute Editor).
Entry: EncryptPasswords=
Value: 0 (default), 1
The password for the default login is stored encrypted in the concerto.dxv
file by setting the parameter EncryptPasswords=1. If EncryptPasswords is
activated, the data source cannot be read by CONCERTO V3.3.
Entry: LoadRange=
Value: data key, start value, number of measurement points, [relative]
or data key, unit, start time, measurement duration, [relative]
If you set the entry LoadRange=, CONCERTO only loads a definable mea-
surement range when accessing channels of a certain data key.
To access time-based data, use parameter Unit to define the unit for the
given start time or measurement duration.
If you set the optional Relative parameter (default = 0), you can define
whether the measurement range to be loaded is absolute (0) or relative (1)
to the start time.

Data Explorer — User’s Guide

Data Explorer 113

When the Relative parameter is set to -1, the measurement range to be

loaded is always relative to the end of the measurement channel.

Example
[ASAM-ODS Database]
.
.
LoadRange=D,30,50

When accessing measurement channels from data key D, 50 measurement

points are loaded from the 30th point.
[ASAM-ODS Database]
.
.
LoadRange=TM,ms,5000,1500,-1

When accessing measurement channels from data key TM, 1.5 seconds are
loaded after 5 seconds, taken from the end of the measurement channel.
[ASAM-ODS Database]
.
.
LoadRange=TM,sec,10,0,-1

When accessing measurement channels from data key TM, the last 10 seconds
are loaded.

Entry: LoginCaseSensitivity=
Value: 0 (default), 1, 2, 3, 4
CONCERTO passes on the login information entered, i.e. username and
password, taking upper/lowercase into consideration according to AODS
standard. If you wish to set case sensitivity in other data models (not PUMA
data model), the following options are available for sending the login
request to the server.
– LoginCaseSensitivity=0
Takes upper and lowercase into account.
– LoginCaseSensitivity=1
Sends the login entered (username and password) to the server in low-
ercase.
– LoginCaseSensitivity=2
Sends the login entered (username and password) to the server in
uppercase.
– LoginCaseSensitivity=3
Only sends the username to the server in lowercase.
– LoginCaseSensitivity=4
Only sends the username to the server in uppercase.
Entry: PhysicalDeleteMeas=
Value: 0 (default), 1
In the Advanced ASAM-ODS Properties you can select Deleted Measure-
ments use attribute from the drop-down list to define which attribute is set
to 1 by deleting a measurement so that CONCERTO does not continue to
display these measurements. If the box is checked, when the measurement
is deleted it is referred to as a logical deletion.
When it is cleared, you cannot logically delete the measurement from the
context menu either.
If, on the other hand, the PhysicalDeleteMeas=1 entry is set, the measure-
ment is deleted physically and data key _bck created.

Data Explorer — User’s Guide

114 Data Explorer

Entry: QueryFiles=
Value: query file path
You can define standard filter conditions in the CONCERTO user interface.
For more on this topic, see Extended Queries on page 56.
Entry: ResolveReferences=
If you set the entry ResolveReferences=, you can resolve and display refer-
ences to other ASAM database tables.
For more on this topic, see Reference Attributes on page 114.
Entry: TestValidIfEmpty=
Value: 0 (default), 1
Setting the entry TestValidIfEmpty=1 enables you to carry out For-
mula/Script Editor file operations (e.g. SelFile) also on empty tests that can
occur, for example, as a result of archiving.
Entry: UniqueTestNames=
Value: 0 (default), 1
If you copy tests using the Composer function, the copy is called "Copy
of..." as is the case in Windows.
When you copy tests to another test series, the original name is used by
default for the copy created if the test does not yet exist.
If you set the entry UniqueTestNames=1 you can change this by specifying
that the copy of a test in another test series is always called "Copy of...",
even if it does not yet exist.
Entry: VirtualChannels=
Value: 0, 1 (default)
Any ASCII character except 0 to 9.
Enabling or disabling the function "Make measurement attributes available
as virtual channels" in the advanced ASAM-ODS properties sets the entry
VirtualChannels= either to 1 or 0.
In addition, if you set this entry to any ASCII character you wish (any ASCII
character except the numbers 0 to 9) you can define translation of the vir-
tual channels to replace the $ character, which characterizes a virtual
channel, with this ASCII character.

1.8.4 Reference Attributes

ASAM databases very often contain references to other tables. Because refer-
ences are only numerical values, you have to look in the referenced table to see
the actual text (or value) of the attribute. However, you can specify that Data
Explorer should resolve the reference automatically and display the actual text
straight from the referenced table. These settings apply to the display in the Data
Explorer list and in the Attribute Editor.
You need to make an entry in the relevant section of the Data Environment file:
ResolveReferences
In the example below, the attributes rActiveTestBed and rLastTestBed are refer-
ences to the table called TestBed. The value corresponds to the value of the Id
column in the TestBed table. Instead of the ID, however, it would make more
sense to display the name of the test bed that appears in the iName column of
the TestBed table.
Extract from TestBed table:

Data Explorer — User’s Guide

Data Explorer 115

Fig. 75

You can do that with the following entry in the Data Environment file:
ResolveReferences=Test,rActiveTestBed,rLastTestBed

(=ResolveReferences=Test,rActiveTestBed=iName;Test,rLastTestBed=iName)
The original columns rActiveTestBed, rLastTestBed would then be replaced by
the new columns TestBed.iName(rActiveTestBed) and TestBed.iName(rLast-
TestBed).

Fig. 76

Any column of the reference table can be used, e.g. iNetworkName, if you
specify the appropriate column name
You can do that with the following entry in the Data Environment file:
ResolveReferences=Test,rActiveTestBed=iNetworkName

Fig. 77

Many data models contain references in different tables that reference the same
table. You can also define a reference table therefore for several tables at the
same time.

Example
In the example below, a data model has three different tables (Auftrag, Test,
Messart) which all contain a ProjectName column. ProjectName takes its
values from the ProjectId column in the ProjectGroups reference table.

Data Explorer — User’s Guide

116 Data Explorer

Fig. 78

Because the ProjectIds of ProjectName give you little information, instead of

ProjectName in CONCERTO you want to display the Description column
entries in the ProjectGroups reference table.
You can do that with the following entry in the Data Environment file:
ResolveReferences=Auftrag|Versuch|Messart|,PROJECTNAME = Description

Job:

Fig. 79

Test:

Fig. 80

Data Explorer — User’s Guide

Data Explorer 117

Fig. 81

Multiple definitions of reference attributes can be specified in a ResolveRefer-

ences line separated by ";".

Example
Here Auftrag, Versuch and Messart PROJECTNAME are first replaced by
"Description" and then the MessartID is replaced by the entries in the reference
table of the HAUPTMESSART column.

You can do that with the following entry in the Data Environment file:
ResolveReferences=Auftrag|Versuch|Messart,PROJECTNAME=
Description;Messung,MessartId=HAUPTMESSART

All the values of the reference attribute for PROJECTNAME can now be
selected in the Attribute Editor. If they are changed, the modification of the orig-
inal attribute is stored.

Fig. 82

Data Explorer — User’s Guide

118 Data Explorer

If the PROJEKTNAME is changed from "Otto-Katalysator" to "Sonden", Projectid

1 is saved for the selected test instead of 21 – as can be seen from the Project-
Group reference table.
All the entries for the table names and attribute names in the Data Environment
file are case-sensitive.

1.8.4.1 Concatenating Multiple Resolved Attributes

Sometimes, you might want to see more than one attribute from the resolved
table. For example, a test has the following attributes:

Fig. 83

At the measurement level, instead of the attribute rTest, we wish to see the
Name, Description and Owner) of the test itself. This is achieved by concate-
nating the attribute names using '|', as follows:

Example
ResolveReferences=Measurement,rTest=Name|Description|Owner

Now DataExplorer shows all three resolved values on the Measurement level:

Fig. 84

Unfortunately, we don’t know which part of the resolved value is Name, which is
Description, and which is Owner. So we define a separator string in
double-quotes as follows:

Example
ResolveReferences=Measurement,rTest=Name|Description|Owner"<>"

Data Explorer now shows

Fig. 85

Now the only remaining problem is that the header is not ideal. This too can be
defined with a string in double-quotes.

Example
ResolveReferences=Measurement,rTest"(#a) #r details"=Name|Description|Owner"<>"

Data Explorer — User’s Guide

Data Explorer 119

Data Explorer now shows

Fig. 86

The column header string can be anything – this one could have been fixed as
“(rTest) Test details”. However, it is more flexible to use the following tokens,
which are replaced by CONCERTO.

#s source table name (in this example: "Measurement")

#a source attribute name (in this example: "rTest")
#r resolved table name (in this example: "Test")
#1 resolved attribute name 1 (in this example: "Name")
#2 resolved attribute name 2 (in this example: "Description")
#3 resolved attribute name 3 (in this example: "Owner")
etc.

#n for the n’th resolved attribute name

Information

The separator string and column header string may not contain commas,
semi-colons or double-quotes!

1.8.4.2 Reference Attributes with Filter Conditions

If a reference attribute from the Test table is resolved in this way, then the
resolved value(s) may also be used in filter conditions. For example, the Test
table is called "Messart", and we have resolved the PROJECTNAME as before.

Example
ResolveReferences=Messart,PROJECTNAME=Description

Now, when you create a condition based on PROJECTNAME, the available

options are listed in a drop-down box:

Fig. 87

Simply select and de-select entries and press OK to alter the condition. The
resolved values will be translated back to reference IDs before the query is sent
to the server.

Data Explorer — User’s Guide

120 Data Explorer

Information

Reference attributes should not be deleted from the DXV file while a condition
depends on them. For example, suppose you resolve Test,rTestSerie=Name and
set condition rTestSerie € (ETC, GEM301H). If you now delete reference
attributes and re-start CONCERTO, the program will not be able to translate the
condition values "ETC" and "GEM301H" into reference IDs.

It makes no sense to define a user-variable in a resolved condition (e.g.

PROJECTNAME = %Project). That is prone to typing errors, and would negate
the comfort of selecting items from a drop-down list.

Information

Wild-cards are not allowed in the 'IN' condition.

1.8.5 Creating and Restructuring Tests

Data Explorer is capable of building and modifying the structure of tests in an
ASAM-ODS database. In combination with Composer spreadsheet windows for
editing data, this offers a powerful feature for generating artificial data.
To use this feature, you must have a Santorin server, a license to use the
Composer option and be operating CONCERTO at an adequate user level.
ISO 9000 Under ISO 9000 regulations, original engine data must not be destroyed. There-
Compliance fore, whenever Data Explorer has to re-save a measurement, it first preserves
the active measurement.
For example, for active measurements of data key D, the original data is stored
under D_org. A backup of the current measurement is stored under D_bck if it is
edited again. Using this convention, it is always possible to see the data as it
was before it was last edited and before it was first edited.
This strategy also means that confirmation dialogs do not have to be output
when something is about to be deleted and there are no "Undo" commands. All
you need to restore a measurement to its previous or original state is the
Restore Measurement command.

Data Explorer — User’s Guide

Data Explorer 121

Create Test Series Select the data source in which the test series is to be created and choose New
Folder on the context menu.
The dialog for creating the test series is then displayed:

Fig. 88

iName
Enter the name of the new test series consisting of alphanumeric characters,
spaces and underscore.
The test series is created when you click OK and confirmed by the output of an
information message in the message list.
Create a New Test Select the test series in which the new test is to be created and choose New
Test on the context menu. The create test dialog appears:

Fig. 89

Data Explorer — User’s Guide

122 Data Explorer

Name:
Enter the name of the new test consisting of alphanumeric characters,
spaces and underscore.
When you click OK, the test is created and confirmed by an information
message.
Delete a Test Select the test to be deleted and choose Delete Test from the context menu.
Tests are not physically deleted from the database. If defined in the Advanced
ASAM-ODS Properties (see ASAM Properties - Tests on page 107), there may
be a "deleted" flag as one of the test attributes. Choosing Delete Test simply
sets this flag and Data Explorer hides all the tests affected. Use the AVL SPACE
data administrator tool to clear the flag and make the test visible again.
The action is confirmed by an information message.
Add a New Mea- Select the test or data key in which the new measurement is to be created and
surement to a Test select the context menu option New Measurement. The dialog for creating
measurements is opened:

Fig. 90

Name:
Enter the name of the data key in which the new measurement is to be cre-
ated or select one of the existing data keys from the drop-down list. If known
from the current context, an existing data key is selected for you.
Description:
If the data key already exists, this field is disabled. Otherwise enter a
descriptive text for the new data key.
Measurement Id:
Enter the ID of the new measurement - it should be a numeric value greater
than 0. As you select existing data keys in the Name field, the ID is updated
to the first free number in the relevant data key.
When you click OK, the measurement is created and confirmed by an informa-
tion message.
Delete Measure- Select a measurement and choose Delete Measurement from the context
ments menu.
The measurement is deleted and the action confirmed by an information
message.

Data Explorer — User’s Guide

Data Explorer 123

Freeze Measure- Select a measurement which contains formulas and choose Freeze Measure-
ments ment from the context menu. All formulas in the measurement are calculated,
their results stored back in the database along with the raw data channels.
Restore Measure- Select a measurement in a backup or original data key (see also ISO 9000
ments Compliance on page 120) and choose Restore Measurement from the context
menu.
The selected measurement(s) are restored, overwriting the active measure-
ments, and confirmed by an information message.
Add Channel to a Select a data key or measurement in which the new channel(s) are to be created
Measurement and choose New Channel from the context menu. The create channel dialog is
displayed:

Fig. 91

Name:
Enter the name of the new channel or select an existing channel name from
the drop-down list. The list contains all known channel names from the data-
base.
Unit:
If the channel name is known, this field contains the channel’s units and is
disabled. If the channel name is not known, you can type in your own units
string.
Description:
If the channel name is known, this field contains the channel’s description
and is disabled. If the channel name is not known, you can type in your own
descriptive text.
Numeric:
If an existing measured quantity is selected, this check box is selected or
deselected, depending on its type. If a new measured quantity is entered,
you can use this check box to define whether the new measured quantity
should contain numeric values or strings.
Value:
In this edit field you can specify the value or string with which the new mea-
sured quantity is created. If the edit field is left blank, the measured quantity
is created with invalid measurement points.
Measurement Range:
If the current measurement contains more than one measurement table with
differing resolutions and/or measurement ranges, the data range of the new
measured quantity can be selected here. No selection can be made if the
measurement consists of only one measurement. "Single Value" is shown
in the selection dialog if the measurement table only contains one measure-
ment point.

Data Explorer — User’s Guide

124 Data Explorer

For every channel you wish to add to the measurement(s), click the Add button
to copy it to the right-hand list box. If you change your mind, select the entry in
the right-hand list box and click Remove.
When you click OK, the channel(s) listed in the right-hand box are added to
current measurement(s) (if not already there).
If you selected a measurement, the channel(s) are added to that measurement
only. If you selected a data key, the channel(s) are added to each of its measure-
ments.
Channels are created with the same number of points as all other channels in
the measurement. All points are set as "Invalid". A default size of 10 points is
applied if this is the first channel in a new measurement.
Each measurement affected is re-saved and confirmed by an information
message.
Delete Channels Select one or more channels and choose Delete Channel from the context
menu.
The selected channel(s) are deleted and the action confirmed by an information
message.
Freeze Channels Select one or more formula channels and choose Freeze Channels from the
context menu. The selected formula(s) are calculated, their results saved back to
the database along with the raw data channels and the action confirmed by an
information message.

1.8.6 Saving ASAM ODS Data

Two saving options are available in the context menu of an open test or
measurement in Channel Browser:
Save Data
Saves ASAM ODS measurements that have been edited using Composer
back to the database. A backup copy of the original measurement is cre-
ated.
Save Data As
Opens a save dialog where various storage settings can be made.

Fig. 92

Upon opening, the dialog shows the source measurement's or source test's
context. The last used path is saved in the concerto.ini file.

Information

The Data Key field is only available if you have opened the save dialog via an
open measurement.

Data Explorer — User’s Guide

Data Explorer 125

Save in field:
Shows the current context, which may be a test series or test.
Apply the Up Level button to navigate one level higher in the ASAM ODS
hierarchy, however no higher than the TestSeries. Double-clicking a test will
take you one level lower. Both tests and measurements may be saved in
the same or a different directory (i.e. test series or test).
Test Name / Data Key:
– File/Test:
Here you can define a name for the test to be saved.
If the test name already exists, CONCERTO will save a further test by
this name. If this is not allowed for this data model, CONCERTO will
save the test by the name "Copy of xxx".
– Measurement:
If you have opened the save dialog via an open measurement, the fol-
lowing scenarios are possible, depending on your definitions in the
Test Name and Data Key fields:
Test Name unchanged / Data Key unchanged:
A new measurement version is saved in the same test, with the same
name and with the [measurement version number] appended (e.g.
!E[1], !E[2], !E[3], etc.).
Test Name changed / Data Key unchanged:
A new test is created and the measurement is saved under the new
test.
Test Name changed / Data Key changed:
A new test is created and the measurement is saved under the new
test with the name specified for Data Key (e.g. MyMeas[1]).
OK:
This button remains disabled until a suitable save definition is made.

1.8.7 Copying Tests into an ASAM Database

Data Explorer is capable of storing complete tests of different formats in an
ASAM-ODS database. To use this feature, you must have a Santorin server, a
license to use the Composer option and be operating CONCERTO at an
adequate user level.
Due to the current limitations of the ASAM-ODS standard, not all data can be
stored. For example, the current standard does not define how to store indicating
data, so this is not yet possible. However, it should work for most other types
supported by CONCERTO.
1. Using drag and drop – select one or more tests or files and drag them onto
a test series in an ASAM-ODS group.
2. Select one or more tests or files and choose Copy from the context menu or
toolbar. Now select the Destination Test Series in an ASAM-ODS group
and choose Paste.
In either case, the test(s) will be stored in the Destination Test Series and
confirmed by information messages.

Data Explorer — User’s Guide

126 Data Explorer

1.8.8 Storing to Santorin with Channel Name Translation

In combination with the Composer, this feature allows you to alter the names of
channels when storing files in AODS. In addition, it is possible to move channels
into different data keys.
To use this feature, you have to define an XLAT translation file on your AODS
data source.

Fig. 93

The translation file is simply a table of the normnames to be translated: each

entry should have a complete syntax (data key'normname). The target norm-
name which is used when saving to an AODS server is typically defined in the
first column of the translation file. All other columns define the source channel
names. The column headers are used as keywords for the translation procedure.
CONCERTO will look in the Etdas column (Source Column) for a matching
normname and store it under the corresponding AODS name channel (Target
Column). If a channel has no mapping, it will not be stored.
The mapping process is always case-sensitive!
How do you create the translation file?
To ensure that the columns are properly aligned, we advise you to create an
Excel spreadsheet as the master. It should look something like this:
Aods Etdas
D'P_ACT D'ACT
D'P_AIR_BF_FLG D'AIRBFFLG
D'P_AIR_CHG_ST D'AIRCHGST
D'P_AM D'AM
D'P_BP D'BP
D'P_CHT D'CHT
D'P_CMAP D'CMAP
D'P_DELPR D'DELPR
D'P_ECT D'ECT
D'P_EGRACT D'EGRACT
D'P_EGRATE D'EGRATE
D'P_EGRDTY D'EGRDTY
D'P_EM D'EM
D'P_EPT D'EPT
D'P_EPTBAR D'EPTBAR
D'P_EPTZER D'EPTZER
D'P_EXT_SS_FL D'EXTSSFLN
D'P_F_A_RATIO1 D'AFRS
D'P_F_A_RATIO2 D'FARATIO2
D'P_FPW_AVG 'FPWAVG

Save the table as a tab-separated text file after editing. The resultant text file can
be used as the translation file.

Data Explorer — User’s Guide

Data Explorer 127

Your source file could be called D’DYNOSPD, D’N or D’DYN_SPD any of

which should be stored under D’SPEED. How?
You define multiple source columns as follows:
Dictionary1=XLAT,Aods=Etdas1|Etdas2|Etdas3,C:\CONCERTO\desc\TranslateNames.txt

Aods Etdas1 Etdas2 Etdas3

D'P_ACT D'ACT
D'P_AIR_BF_FLG D'AIRBFFLG D’AIR_FLAG
D'P_AIR_CHG_ST D'AIRCHGST
D'P_AM D'AM
D'P_BP D'BP
D'SPEED D’DYNOSPD D’N D’DYN_SPD

If the source channel is found in any of the 3 Etdas columns, it will map to the
corresponding AODS name.
All raw data channels and channels from embedded files are taken into consida-
tion when saving. Formula results are not stored.
You don’t want to define every possible source channel name, but you
don’t want to lose any channels. How?
You can use the ‘*’ wildcard as a channel name. Since the translation table is
processed sequentially, define all the ‘known’ channels first and put a wildcard
entry at the end:
Aods Etdas1
D’THROTTLE D’ALPHA
D’* D’*
!E’* ED’*

The channel D’ALPHA will be stored as D’THROTTLE; all other channels in data
key D will preserve the original normnames. All source channels in data key ED
will be stored in data key !E.
How can you see what the translation process is doing?
Define the following in concerto.ini:
ChannelTranslation=1,C:\CONCERTO\logs\XLATlog.txt

The values for trace level are:

1: log all errors.
3: as for 1 plus all channels which have no mapping.
5: as for 3 plus all channels successfully mapped

WedFeb28 13:40:19 2001 ChannelTranslation -5- Source D'ACT Target D'P_ACT Success

WedFeb28 13:40:19 2001 ChannelTranslation -5- Source D'AFR AIR+ Target D'AFR AIR+ Success

WedFeb28 13:40:19 2001 ChannelTranslation -1- Source D'AFR CALC Target D'P_ACT Target already
exists

WedFeb28 13:40:19 2001 ChannelTranslation -5- Source D'AFR CART Target D'AFR CART Success

WedFeb28 13:40:19 2001 ChannelTranslation -5- Source ED'DUR_HOURS Target !E'DURABHRS Success

WedFeb28 13:40:19 2001 ChannelTranslation -5- Source ED'ENG_HOUR Target !E'ENGHOURS Success

WedFeb28 13:40:19 2001 ChannelTranslation -5- Source ED'ENG_NO Target !E'ENG_NO Success
WedFeb28 13:40:19 2001 ChannelTranslation -3- Source !E'ANL_ZEIT[1] Target No mapping

Wed Feb28 13:40:19 2001 ChannelTranslatio -3- Source !E'ATL[1] Target No mapping

WedFeb28 13:40:19 2001 ChannelTranslation -3- Source !E'A_LEER[1] Target No mapping

Data Explorer — User’s Guide

128 Data Explorer

Trace output always refers to an existing output file.

Can you put comments in the translation file?
The # character defines a comment line. See next example.
Can one translation file support different source file formats?
One master translation table can be used as the basis for all translation
processes. For example.

Aods Etdas1 Etdas2 VDF Famos

# General data
D'P_ACT D'ACT
D'P_AIR_BF_FLG D'AIRBFFLG D’AIR_FLAG
D'P_AIR_CHG_ST D'AIRCHGST
D'P_AM D'AM
D'P_BP D'BP
D'P_CHT D'CHT
D'* D’*

# time-based
!0'P_EGRACT TM'egract
!0'P_EGRATE TM'egrate
!0’* TM’* TM’*

# Engine Parame-
ters
etc. etc. etc. etc. etc.

You define all possible source file formats in the relevant data source definitions.
Dictionary1=XLAT,Aods=Etdas1|Etdas2|VDF|Famos,C:\CONCERTO\desc\TranslateNames.txt

Here channel names are to be unique across all source file formats. The transla-
tion process will map the first match found in any of the source columns.
How is the translation process activated?
Drag and drop (or copy/paste) a test onto the target AODS data source (i.e. a
test series) or write a script:

Example
alias = LoadFile ("ETDAS Data","SEE\6TZ1205\ETRN\693.LOG")
StoreFile (alias, "Test Data Aods with name
translation","6TZ1205.Common\Etdas693")
RemoveFile (alias)

How do you disable channel name translation?

Delete the translation file path in the data source properties. Alternatively, you
can define two AODS data sources pointing to the same server, one with a XLAT
dictionary, the other without. Then you can drop a test on either group.

Data Explorer — User’s Guide

Data Explorer 129

1.9 Special Features for Accessing Data

1.9.1 Splitting Data into Artificial Measurements

In many cases, viewing the data as one cohesive stream of values is undesirable
or only part of the data is of interest.
For example, if an engine map is recorded, the dataset for Fuel Consumption will
typically look like shown below, where each line segment represents a constant
speed with increasing load:

Fig. 94

Over-plotted, the individual line segments would actually appear like this:

Fig. 95

Worse still, channels in a data key may each consist of more than one stream of
values multiplexed into a single dataset, giving the following picture for example:

Fig. 96

Data Explorer — User’s Guide

130 Data Explorer

However, what is often desired is the following representation:

Fig. 97

To view this sort of data correctly, we need to artificially separate values into
different measurements. This is the principle of Measurement Splitting.
CONCERTO offers two ways of splitting data into measurements:
via CONCERTO’s Channel Browser (the easier way)
via Data Explorer using the data source’s Properties dialog

1.9.1.1 Measurement Splitting via Channel Browser

The advantage of this method is that the measurement splitting applies to the
opened file only, which means it is file-specific and has no impact on the entire
data source. The same file opened for a second time will be shown undivided.
To use this feature, proceed as follows:

Information

Preconditions:
If the concerned data already contain natural measurements (ASAM ODS
data, ATF, MDF), first open the measurement with the data that are to be
split.
The existence of a channel (control channel) that contains curve numbers.
Each curve number is assigned a number of measurement points, which
indicates the control channel for splitting. If the suitable channel does not
exist, it can also be created with the help of a formula.

1. In Channel Browser, identify an arbitrary channel (control channel) from the

data key which can be used to decide the measurement each point should

Data Explorer — User’s Guide

Data Explorer 131

be placed in. This is called the Control Channel. The control channel values
must be positive integers.
The following figure shows three channels (undivided) and the control
curve:

Fig. 98

2. Select Split from this channel’s context menu:

Fig. 99

In the right-hand bottom corner of the application window a measurement

bar is shown with which you can navigate through each of the artificially cre-
ated measurements:

Fig. 100

Data Explorer — User’s Guide

132 Data Explorer

The following figure shows the values of artificial measurement 2 and the
control curve:

Fig. 101

After splitting, both a data key for the split data and a raw data key (D_raw) are
displayed in Channel Browser:

Fig. 102

Splitting can be canceled again by selecting the context menu option Unsplit.
Related Subject See the documentation about the User Interface Functionalities, under Special
Functionalities.

1.9.1.2 Measurement Splitting via Data Explorer

To use this feature, proceed as follows:
1. Identify an arbitrary channel from the data key which can be used by Data
Explorer to decide the measurement each point should be placed in. This is
called the Control Channel. The control channel values must be positive
integers.
2. Open the Advanced tab in the Data Source Properties dialog (see also
Data Source Properties - Advanced on page 98) and define the control
channel name in the box labeled Measurement Splitting....
The format of this definition is:
MT’CHAN [,start,length]
– MT:
Data key whose channels are to be split into measurements.
– CHAN:
Name of the control channel.
– start,length:
May be used if the control channel is of ASCII format. They define the
start and length of the substring to be used as the measurement ID.
Multiple definitions (to affect different data keys) are to be separated by a semi-
colon (";").

Data Explorer — User’s Guide

Data Explorer 133

Example
In a PUMA TRR file, the data key D is split based on D’CURVENUM:

Fig. 103

Example
The engine map in KF is split based on KF’SPEED:

Fig. 104

Example
The post mortem data in SD is split according to the curve number in $KEY
(characters 8 to 14):

Data Explorer — User’s Guide

134 Data Explorer

Fig. 105

The complete definition for measurement splitting of data in this data source will
therefore be:
D’CURVENUM;KF’SPEED;SD’$KEY,8,6

Note that, for PUMA TRR files, the Dictionary TRRKEY may also contain a defi-
nition for splitting data into measurements. This method is less flexible and
simply allocates sequence numbers as measurement IDs. Ensure that only one
method is applied to this file type, for example by defining TRRFLAT.DSC as the
TRRKEY dictionary.
If the data is stored in natural measurements, for example in an ASAM-ODS
database, splitting into artificial measurements is still possible. Every natural
measurement can be further split into artificial submeasurements according to
the defined control channel. You can work with such a submeasurement as if it
were a measurement. Submeasurements are addressed using the syntax [m,s].

Example
D’SPEED[5,3] represents the artificial submeasurement 3 of the natural
measurement 5. For backward compatibility, formulas and layouts referencing
artificial measurement IDs without a submeasurement will still work as expected.

1.9.2 Working with Long Recorder Data

1.9.2.1 Data Management by Blockwise Loading

When loading large data, CONCERTO uses an intelligent data-loading mecha-
nism that allows you to work with large data without having to keep all the data
inside the memory. The data is loaded in blocks, which helps you to avoid
extended loading times or any associated problems (timeouts) in the case of
ASAM-ODS data.
Blocks are loaded automatically, whenever CONCERTO requires data that has
not yet been loaded. Memory blocks that are not needed for a longer period of
time are outsourced to local cache files. These cache files are automatically
reloaded with the highest performance whenever CONCERTO needs any data
from them.
This mechanism enables you to work with optimal performance and efficient
memory utilization, even when data amounts are very large. At the same time,
this kind of management is fully transparent for users, both when it comes to
data display and formula calculation.

Data Explorer — User’s Guide

Data Explorer 135

1.9.2.2 Adaptive Loading

With regard to data from ASAM-ODS servers, CONCERTO is also capable of
working with very large data volumes by loading data adaptively. This mecha-
nism requires time-based data with unit "s" or "ms".
Working with When loading data, CONCERTO first checks its size. If it happens to be very big,
Preview Channels it is not loaded to its full extent to avoid long loading times. By reducing the reso-
lution, CONCERTO first only loads the preview channels, i.e. the data is only
shown in coarse resolution.
If the test bed system in use (e.g. AVL PUMA Open) supports the creation of
preview channels, these generated and stored preview channels are used by
CONCERTO. This has the advantage that the generated preview channels are
not just reduced channels but contain the complete information about signal
peaks in the form of an envelope curve.
The use of preview channels is fully transparent for users. If very large data is
involved, the data preview usually displays reduced data (preview channels or
reduced data).
To create a diagram, you drag datasets into a window or into the field provided
by the Object Wizard as usual. CONCERTO checks whether the data amount
that is to be loaded would lead to unacceptable loading times. If this is the case,
CONCERTO additionally checks whether there are any preview channels.
CONCERTO only loads the reduced data and uses it to build the required
diagram. In such a case, you will see the text ("Preview") next to the name on the
Y-axis. In this way, you can always tell that the displayed data is not the raw data.
In the preview window you can tell that preview data is being shown by the fact
that the data is displayed as an envelope curve.

Fig. 106

Data Explorer — User’s Guide

136 Data Explorer

If you work interactively with this diagram and zoom into a sub-area of the
X-axis, CONCERTO once again checks whether the data needed for this
sub-area is still too large. Only when the data volumes required fall below the
threshold will CONCERTO switch to full resolution.
In the preview window the blue curve color signals that only a sub-area of the
data is being displayed.
Threshold Settings You can adjust the threshold at which CONCERTO switches to preview channels
to suit your own network conditions.
The following entry in the DXV file sets the number of measured values to be
loaded before CONCERTO switches to preview channels:
HugeDataThreshold=500000
The default value for this setting is 500,000 values.
f you set the number to 0, adaptive loading is deactivated and all points are
always loaded regardless of the number of values.
Settings for When the test bed system generates preview channels, two channels are
Preview Channels created:
One with maximum values
One with minimum values
Together, these two curves form an envelope curve within which all points of the
raw data are located.
The preview channels’ names usually consist of the name of the original channel
and a postfix each for the minimum and maximum.

Fig. 107

To enable CONCERTO to find the preview channels automatically, you must

define a name convention. This is done by the following DXV entry:
PreviewChannels=%s_max,%s_min
Here %s is a placeholder for the channel name.

Data Explorer — User’s Guide

Data Explorer 137

If this entry is defined, CONCERTO automatically searches for the preview chan-
nels matching each channel. If they are available, they are used for adaptive
loading. At the same time, they are hidden in Data Explorer, because
CONCERTO now independently decides whether to use the preview channels or
the raw channels.

Fig. 108

Working with For an opened test, only one sub-area may be active. If you use data from a test
Several Sections in several diagrams, the diagram always shows the section that was last acti-
vated by zooming. If you want several diagrams to show different sections of the
same test, you can use Data Explorer to open the same test multiple times. This
behavior can be activated by the following DXV entry:
AllowMultiOpen=1
Calculating Formula calculation is always based on the currently loaded section of data. This
Formulas is useful, because data calculations based on full range and full resolution may
lead to very long waiting times. If you still want to do this, you can choose one of
the following options:
With the compiler switch LoadFullResolution you can specify within a for-
mula that the data is loaded in the full range with the full resolution. The
loading mechanism is applied (see Data Management by Blockwise
Loading on page 134).
For this purpose, insert the following command at the beginning of the for-
mula:
SetCompilerSwitch("LoadFullResolution",1)
You can open the same test multiple times (also via the DXV entry Allow-
MultiOpen=1). With the DXV entry SetLoadRangeOnPreview=0 you can
specify that the data is loaded in the full range with the full resolution and is
thus available for calculations.
Display in Tables In tables, data is normally displayed using preview channels. However, if you
wish to show the data with the full resolution, you can use the feature Don't use
Preview channels in the dataset properties of the table. When this function is
activated, the datasets for the table are always loaded with the full resolution.
Transformation macros in the table then also calculate based on full resolution.

Data Explorer — User’s Guide

138 Data Explorer

1.9.2.3 Loading Constant Segments

In order to avoid extended loading times for large recorder curves (e.g. 2 million
points) there is a way to divide these curves into shorter segments. These
segments appear in Data Explorer as submeasurements within the measure-
ment of the corresponding data key. In an overview you can choose the segment
to be examined in more detail from the complete recorder measurement.
Following this you can individually load the specific segment. This form of
segmentation is only possible for ASAM data.
Definition Segmentation is defined under Measurement Splitting on the Advanced tab in
the Data Source Properties dialog.

Fig. 109

You can also enter multiple definitions, separated by semicolons, each one
affecting a different data key. Each definition contains the following
comma-separated fields:
Data key:
The data key which is to be segmented.
Segment length:
The maximum size of a segment in the base unit of the data key.
Preview resolution:
The resolution of the Graphic Preview when viewing the Overview curve.
Overview All data keys in an ASAM-ODS database have at least one natural measure-
ment. When applying segmentation to such data, every natural measurement is
further divided into segments represented by submeasurements. In Data
Explorer, the structure appears like this:

Data Explorer — User’s Guide

Data Explorer 139

Fig. 110

1.9.3 Merging Measurement Types

Due to PUMA Open’s limitations with regard to the possible number of recorder
channels to be recorded, it may become necessary to carry out several recorder
runs to be able to record all the required channels. In Data Explorer these are
shown as separate measurement types.
As the data are spread out across several measurement types, identical channel
names may lead to problems when creating layouts.
By entering MergeMeasNames= in the DXV file, CONCERTO lets you merge
individual measurement types and their contents.
To do so, first enter the name under which the measurement types are to be
merged, and then, separated by comma, enter the measurement types that are
to be combined.
In the following example, the measurement types Secondary Recorder and
Recorder were combined under the joint measurement type RecResult:

Example
Entry in the DXV file under the relevant data source:
MergeMeasNames=RecResult=SecondaryRecorder,Recorder

After rereading, the data are shown as follows:

Data Explorer — User’s Guide

140 Data Explorer

Fig. 111

The measurement types Secondary Recorder and Recorder were merged into
the type RecResult. The measurements and the channels within the measure-
ments were merged too.
Identical channel names were extended by adding _1, _2, etc. and the original
measurement type is indicated in the Source Key column.
Several merge definitions can be realized if they are separated by semicolon.

Example
The entry
MergeMeasNames=RecResult=RecResult,SecondaryRecorder,Recorder; Dialogs=$B,$E
would additionally merge $B - beginning dialog and $E - end dialog into the
measurement type Dialogs.
If the names of different measurement types have the same beginning and only
differ from a certain character onward, it is also possible to use wildcards:
MergeMeasNames=RecMeas=Recorder*
would merge the already existing measurement types Recorder1, Recorder2,
etc., into the measurement type RecMeas.

1.9.4 Translating Channel Names and Converting Units

The Translate Channel Editor dialog enables you to edit the way channel names
are displayed in Data Explorer. Partial strings of a channel name can be
replaced by a defined string or channel names can be truncated from a defined
string.
You can open the Translate Channel Editor via the Advanced page in the Data
Source Properties dialog (see Data Source Properties - Advanced on page 98):

Data Explorer — User’s Guide

Data Explorer 141

Fig. 112

Translation Rules
The translation rules are entered in this field as SourceString=TargetString.
You can add additional translation rules by pressing Enter. The resultant list
of translation rules is managed separately for whichever Option Key Type
is set.
Option Key Type
Defines the mechanism of the translation rules.
The following translation operations are available:
– Replace: This function permits special characters or partial strings in
the channel name to be removed or replaced by defined strings.

Fig. 113

Example
If you enter the translation rule ":=" and "~=_", string ":" will be removed from the
channel name and string "~" will be replaced by string "_".

Fig. 114

Data Explorer — User’s Guide

142 Data Explorer

– Truncate: This function is used to truncate channel names from a

defined string, the truncated partial string being displayed as a further
column attribute.

Fig. 115

MDF files are saved in a format with additional information being

added to the actual channel name (e.g. measurement system).
If you enter the translation rule \=Measurement-System, the channel
names are truncated as of the last string \ and a column attribute called
Measurement-System is created which displays the truncated string.

Fig. 116

Enable File Map

When you activate this function, a translation file can be used to translate
the normnames in terms of their name, description and format and perform
a unit conversion.
– Mapping Dictionary: Defines the path to the translation file.
– Target Column: Name of the column in the translation file which con-
tains the resultant normnames.
– Source Column: Name of the column in the translation file where the
system searches for matching normnames. If there is more than one
source column, you can separate them with the ( | ) character.
Map file structure, using dico.txt as an example:
Your CONCERTO installation includes a map file (dico.txt) by default. This file
resides in the \StdLib\Desc folder.
You can fill this file to meet your own requirements.

Information

We recommend using MS Excel for editing the file.

The mapping process is always case-sensitive!

In the example of the dico.txt translation file below, the normname translation is
effective for all the data keys in the test. The process can also, of course, be
applied explicitly to a specific data key provided that the source normname
(SOURCE_A) is uniquely defined with the data key (e.g. D’POEL).

Data Explorer — User’s Guide

Data Explorer 143

Fig. 117

In addition to the definition of the channel name (TARGET column), its descrip-
tion and unit (and the converted unit) as well as the format can also be defined in
additional columns (Fx.y - where x stands for the field width and y for the number
of decimal places displayed). If you leave the columns empty, the source
attribute (SOURCE columns) is output.
If the unit is to be converted, the target unit must always be entered into the
TARGET.Unit column. If you additionally want to specify that only a specific orig-
inal unit is to be converted, you can specify that original unit in the field under
SOURCE.Unit. If the field in the SOURCE.Unit column remains empty, all units
will be converted to the target unit units. Unit conversion is performed based on
the relevant definitions in the units table (see the documentation about the User
Interface Functionalities, under Special Functionalities - Unit Conversion).

1.9.5 Temporary Channels

PUMA has the ability to freely allocate up to 99 channels during a test. This
means that, without specifically allocating a normname, the cell operator can
define the name of a channel according to the actual signal connected. These
channels are referred to as Temporary Channels.
In the test result file, the logged channels are named TEMP_01 to TEMP_99 by
default and the actual signal names for each channel are stored in the Tempo-
rary Channel Table in a special data key.
Data Explorer offers the ability to hide all the default TEMP_nn names replacing
those that were used with their corresponding signal names. To use this feature,
define the temporary channel table. Enter the string below in the Temporary
Channel Table field of the Advanced tab in the Data Source Properties dialog:
$T,TMP_ORG,TMP_NAME,TMP_UNIT,TMP_DESC,TMP_NCD
$T
Indicates the data key which contains the temporary channel table con-
sisting of the named datasets.
TMP_ORG
Is the dataset containing original names (“TEMP_nn”).
TMP_NAME
Is the dataset containing the actual signal names.
TMP_UNIT
Is the dataset containing the signal’s units.
TMP_DESC
Is the dataset containing the signals' descriptions.
TMP_NCD
Is the dataset containing the channels’ normcodes.

Data Explorer — User’s Guide

144 Data Explorer

1.9.6 Alias Channel Names

This feature allows you to replace channels names (normnames) of axes, tables,
etc., by your own channel names. For this purpose, you have to create a text file
that defines how to replace existing channel names by your own aliases.
Create a text file (using an arbitrary editor), as given in the example:

Example
[ALIAS]
ALIAS0=P_OEL; P_OIL; A; A; A; A; A
ALIAS1=DRZ; SPEED; A; A; A; A; A

First create a header.

[ALIAS]

Define an arbitrary number of lines in the following format:

ALIASn=real_name; replacement_name; dummy; dummy; dummy; dummy; dummy

ALIASn
For numbering (e.g. ALIAS10)
real_name
Channel name to be replaced (e.g. TRQ)
replacement_name
String to be displayed instead of real_name (e.g. Torque)
dummy
Currently not supported, but must be defined (e.g. A)

Information

The channel names must not contain blanks, use underscore characters ( _)
instead.
The length of replacement names must not exceed 64 characters.

To select the desired alias, use the menu option Extras | Layout Translation |
Alias Name File. A corresponding entry is created in the concerto.ini file (Alia-
sTableFile=path).
When loading a layout containing channels which are defined in the alias file,
you can change over to these alias names. The alias names are activated via
the menu option Extras | Layout Translation | Use Alias Name File.
All the channels for which replacements are defined in the alias file are renamed.
Select the menu option once again to switch back to the original names.
If you switch to alias names, this only affects output on screen and printer. The
dataset names inside objects and formulas remain unchanged.

Data Explorer — User’s Guide

Data Explorer 145

1.9.7 Hiding Formulas that are Not to Be Calculated

Further calculated quantities can be determined from measured channels using
formulas. If the required measured values are not available in the data file
currently in use, the result of the formula cannot be calculated and the formula is
useless for that data file.
When all the available formula channels are displayed for all existing data files,
there are several disadvantages:
The list of the formulas in Data Explorer may then be so long as to be con-
fusing. It takes too long to find a certain formula in the list.
Without calculating the formulas, it is not possible to find out whether a for-
mula can even be used for the current data file.
With the Formula Dependency File, however, the list of displayed formulas can
be reduced so that only those that can actually be calculated for a specific data
file are displayed under the file.
To activate this functionality, a Formula Dependency File has to be created and
defined in the command line provided for it (see Data Source Properties -
Formulae on page 97).

1.9.7.1 Formula Dependency File

A Formula Dependency File is needed to be able to ascertain that a formula can
be calculated. The file contains a list of the data channels for each formula that
are needed for the formula calculation. Using this file, Data Explorer can then
hide the formulas that cannot be calculated without having to calculate all of
them first.
Structure There is a line for each formula in the Formula Dependency File (see example
below). On the left of the “equals” sign is the name of the formula and on the
right are the names of the input channels (separated by semicolons) required to
calculate the formulas.

Example
AGR_SE=D'CO2_S;D'CO2_E;
AGR_SE_L=D'CO2_S_L;D'CO2_E_L;
AGR_SE_R=D'CO2_S_R;D'CO2_E_R;

Automatic Creation of the Formula Dependency File

The Formula Dependency File can be created manually with any ASCII text
editor (e.g. Notepad). If a large collection of formulas exists, however, it is more
sensible to create the Formula Dependency File using a script. A suitable script
(CreateFormulaDependencyFile.csf) is included in the scope of supply. This file
resides in the StdLib\Scripts subfolder of your installation folder.
This script uses the GetDependencyChannels(1) dataset function to determine
the list of necessary input channels for a formula.
For practical purposes, the script is defined as a Test Context Script of a data
source for which the formula dependencies are to be created. The Test Context
Script is then called up for one (or more) data files of that data source. All the
formulas should be visible for this purpose in the data source.
The script can also create all the dependencies, even if the formulas in the data
source cannot be calculated. One reason for the formulas not being calculable
might be that the assignment of a data channel to a variable does not have
access to the complete data channel path (e.g. var=D'CO2_S_R) but only to the
data channel (e.g. var=CO2_S_R). In such cases however, no data key is
entered in the Formula Dependency File for the necessary data channels. This
may mean that it takes longer for the system to check the formula dependencies.
It would be an advantage therefore if a data file were available for which the
majority of the existing formulas were calculable.

Data Explorer — User’s Guide

146 Data Explorer

That would guarantee that dependencies would be created for the majority of the
formulas with the necessary data channels fully defined (i.e. including the data
key). The Formula Dependency File can, of course, also be edited retrospec-
tively and the appropriate data keys entered manually for the data channels.

1.9.8 Load Data Macros (Repeated Points Filter)

There may be occasions when the data as stored is not usable in its raw state.
For example, suppose data key D contains a channel called LOGPOINT
containing the following data:
1, 2, 3, 4, 4, 4, 5, 6, 6, 7, 8
This means that, due to some fault on the test bed, the 4th point had to be
repeated twice and the 6th point was repeated once. The repeated points were
not overwritten, but simply appended.
Obviously, the true data of any channel in this measurement is formed by
discarding the 4th, 5th and 8th index points. This procedure is best applied when
the data is loaded.
To achieve this, you can define a macro which should be run on all channels
loaded from a particular data key. This is defined in the data source properties
dialog, Advanced page, Run macros on loading channels field.

Example
Clearly, almost any manipulation of the raw data can be achieved in the macro.
In this particular case, we can write the following macro:
NAME:RepeatFilter
arg ds
dsin=RemoveRepeatedPoints(ds,LOGPOINT)
// Get filtered Logpoint
dslog=RemoveRepeatedPoints(LOGPOINT,LOGPOINT)
// Sort dataset according to Logpoint
ysorted=sort(create(dsin,dslog))
return create(1..npoints(ysorted),xds(ysorted))

and store it as REPEATESPOINTSFILTER.MAC in the normal location for

macros. Finally, define this macro to be run on every channel loaded from data
key D:

Fig. 118

Data Explorer — User’s Guide

Data Explorer 147

Now, every channel we view in this data key will appear to have only 8 points –
only the latest of the 4th and 6th logpoints will be present. In addition, since the
macro also sorts the data, the values in LOGPOINT do not necessarily have to
be increasing values.

1.9.9 Embedded Data

1.9.9.1 ASAM-ODS Data External References (Attachments)

In ASAM-ODS, data files with different formats can be linked to ASAM-ODS
tests or measurements by so-called External References. This is applied if data
is recorded for an ASAM-ODS measurement using different measuring devices
and the measuring devices save their data in files. In order to link related files of
an ASAM-ODS measurement to the test for later evaluation, tables with these
links are created on the ASAM-ODS server. In such a case, therefore, the
ASAM-ODS test contains the information via the linked files.
CONCERTO uses this linked information to be able to directly access the linked
files for the evaluation.
In Data Explorer the linked files are then displayed at the ASAM-ODS test’s
measurement level.
External references may be files with different formats, e.g. IFiles or MDF Files.
The format of a reference is saved in the database. In Data Explorer you can
see a node for the data format below the test. Below you will see all files of this
format that are available for a test. Now you can open this file in Data Explorer in
the usual way. CONCERTO then automatically generates temporary data
sources for the different formats of the linked files.
Configuration Attributes for External References
Information about external references are stored in special attribute lists on the
ASAM-ODS Server. These lists also contain information about the data type of
every external reference, e.g. MDF, IFile, etc.
When CONCERTO loads a test, the attribute lists of the external references will
also be taken into account.
Settings in the concerto.dxv file
For every reference the file type is read. Then a data source is automatically
created depending on the file type. In the concerto.dxv you define how the data-
source name is to be generated from the file type:
MimeGroupName=Att_%s
The variable %s is automatically replaced by the file type according to this defini-
tion.
If the file type is e.g. Indicating_Ifile, the data source name will be
Att_Indicating_Ifile.
In addition, a data source template must exist in the concerto.dxv file for every
file type supported. The name of this template is formed as follows:
~Mime~<MimeType>

Example
Template for file type Indicating_Ifile:
[~Mime~Indicating_IFile]
Format=IFILE,ATTIFILE,DOS

Based on the defined data source template, CONCERTO can now automatically
create the appropriate data source and, thus, read the linked files of this data
type using this data source.

Data Explorer — User’s Guide

148 Data Explorer

Access to data files for external references

External references are always saved in files in the file system. Basically, data
files for external references can be accessed in two ways:
Access using the ASAM-ODS security system
If you want the access to external references and to the ASAM-ODS data
itself to be managed by the ASAM-ODS access control, you can access
them via a special component (FileStorageClient). Normally, CONCERTO
uses this method to access external references.
Access using the Windows security system
If the folder in which the external references are stored in the file system is
connected via a network drive, it is also possible to access the files using
the access mechanisms of the Windows file system. In this case the Win-
dows security system is applied, and not the ASAM-ODS security system.
For accessing the files, CONCERTO needs the following entry in the con-
certo.dxv file:
AttachmentPath=\\servername\dir|e:\dir
The entry consists of two parts, separated by a vertical line.
The first part of the path (\\servername\dir) describes the path as shown on
the CONCERTO PC. If you start e.g. Windows Explorer on the CONCERTO
PC, you can see the external references in this path.
The second part of the path (e:\dir) describes the path under which the
external reference files are stored on the ASAM-ODS server. This means
that if you start e.g. Windows Explorer on the ASAM-ODS server, you can
see the external references in this path.

1.9.9.2 Embedding Data from Other Data Sources

Engine testing in a typical automation system involves the acquisition of data by
multiple devices. Often, the raw data is processed to calculate additional results
which are stored separately. There might also be a distinct procedure for
entering comments by the cell operator or for maintaining cell and engine diaries.

Fig. 119

Clearly, the data from each source is related because it all refers to the same
test. However, the relationship is obscured because these data files are stored in
different places and in different formats. However, in all probability, there is some

Data Explorer — User’s Guide

Data Explorer 149

convention applied to the file and folder naming so that you can find the related
data yourself.
Data Explorer not only claims to read all these file formats, it is also possible in
many cases to make these relationships on your behalf and present a complete
view of all information acquired during a test. This is the principle of Embedding
Data.
The file into which data will be embedded is called the Primary File. This is the
starting point from which you normally begin analysis. There should be a
Channel in the Primary File which contains the names of the files to be
embedded. This is not as restrictive as it seems, since, with the aid of the
Formula Compiler, it is possible to construct a dataset containing almost
anything. Channels from the embedded file(s) will appear as additional channels
in the Primary File.
Example 1 During a steady-state test, a time-based recording of transient data is made and
stored in a separate file under data key TM. name of the recorder file is stored
with the steady-state results in the channel D’REC_NAME. Define a data source
to read the steady-state results and another to read the recorder files.
To embed the recorder data into the steady-state file, define the relationship to
Data Explorer. Using the Data Source Properties dialog, Advanced tab, insert a
new entry in the list Embed Data from Data Source – this will launch the
Embedding Definition dialog.

Fig. 120

In the list of data sources, select the data source containing the files to be
embedded. Channel containing file names in this example would be set to
D’REC_NAME: the Index field should be empty. Finally, if you do not want to
view the recorder data except in its related steady-state file, then activate the
Hide embedded data source check box.
Now, each file in the steady-state group will contain an extra data key TM
comprising all the channels from the recorder file.

Data Explorer — User’s Guide

150 Data Explorer

Example 2 During a steady-state test, data is acquired at each logpoint and stored in the
Primary File. At each logpoint, another device takes a measurement and stores
its data in a separate file – one file per logpoint. You therefore need to tell Data
Explorer to make a series from the secondary files: the channels in that series
are to be embedded into the Primary File as additional channels.

Fig. 121

The first step is to define two data sources – one to read the Primary Files, and
another pointing to the embedded files.
Step two is to identify the channel from the Primary File which contains the
names of embedded files. The Primary File possibly already contains such a
channel of file names but, more likely, you have to create one by defining a
formula. Suppose that, in the Primary File, we have a channel HD’TESTNUM
containing the test number and the embedded files are named after this test
number with logpoint as extension. The formula EMB_NAME, defined in data
key D as
inc=1..npoints(D'Chan) ; Chan is any channel in data key D
return “FILE” + cstr (HD’TESTNUM, "%04.0f") + "." + cstr (inc, "%03.0f")

will generate the dataset (if HD’TESTNUM has the value 123)
FILE0123.001
FILE0123.002
FILE0123.003

etc.
with as many points as all the other channels in data key D.
Now we can define the relationship to Data Explorer. Using the Data Source
Properties dialog, Advanced tab, insert a new entry in the list Embed Data from
Data Source – this will launch the Embedding Definition dialog.

Data Explorer — User’s Guide

Data Explorer 151

Fig. 122

In the list of data sources, select the data source containing the files to be
embedded. Channel containing file names in this example would be set to
D’EMB_NAME. Since we need to make a series of files from the embedded
group, the Index field should be set to the keyword “%logpt”. Finally, if you do
not want to view data from the embedded group except via primary files, then
activate the Hide embedded data source check box.
When viewing data key D in one of the primary files, we will now see the
embedded channels ChA, ChB and ChC as well as the original channels Ch1 to
Ch5. Embedded channels are indicated by a special icon in the Data Explorer
window.

1.9.10 Reading ASCII and Binary Files with Descriptor (Syntax)

Data Explorer is capable of reading column-based ASCII or binary files with a
more complex format by interpreting descriptor files which describe such files. In
this way, Data Explorer can support many customer-specific formats. The files
may contain data as well as parameters like engine geometry, user comments
etc.
To adapt to a specific file layout, a descriptor file which describes the structure of
the data file in detail, has to be set up. Furthermore, a data source with either
Generic ASCII File or Generic Binary File file format has to be defined
including a GENERIC Dictionary definition which contains the description of the
file format.
For typical ASCII files containing columns separated by tabs or semicolons,
standard descriptor files (conctab.dsc and concsemi.dsc) are supplied with Data
Explorer. These files reside in your CONCERTO folder under <Program
Version>\StdLib\Desc.
For convenience, if several similar but not identical data files are in use, the
descriptor file may hold the definitions for more than one data file format and can
therefore be allocated to more than one data source. In this case, the descriptor
file will contain several file sections.

Data Explorer — User’s Guide

152 Data Explorer

1.9.10.1 Identities
Descriptor files may contain attributes with the format "%NAME". This is called
an Identity and is substituted at runtime by actual values (strings) from the data
file.

Example
A record may contain the field definition
1 INTEGERCYLINDERS-Number of cylinders

which could subsequently be used in the File section

DETAIL No. of cylinders: %NCYLINDERS

or be used to generate channel names for each cylinder

%NCYLINDERS REAL IMEP BAR Indicated Mean Effective Pressure

which gives channels IMEP_1, IMEP_2 ...

In many cases, it is also possible to perform a simple calculation with Identities.
For example, if the following fields have been defined within a time-based data
file:
1 R4 nrecords
1 R4 hertz

then the X-axis may be defined with

BASELINE TIME sec. 0 %nrecords/%hertz 1/%hertz TIMEBASED Elapsed Time

Thus, if the file contains 2000 records recorded at 25 Hertz, the X-axis created
will have the range 0 to 80 seconds at 0.04 seconds resolution.
These calculations are restricted to one operator only, formulas such as
%NCYCLES*4+1 are not allowed.

One special Identity - %FILESIZE – returns the number of bytes in a file. For a
binary file, this may be useful when the number of records is not recorded but the
record size is fixed. For example, if every record has length 84 bytes, then
%FILESIZE/84 gives the number of records.

1.9.10.2 Descriptor File Structure

Empty lines in the descriptor file and lines beginning with a semicolon (for
comments) are ignored. Keywords should be entered in uppercase.
Basic Structure A descriptor file consists of a number of record descriptions followed by one (or
more) file description sections.
RECORD ....
RECORD ....
RECORD ...
FILE ....
Record Definition A record of an ASCII file may consist of one or multiple lines. Each line consists
of one or multiple fields, which might be numbers or text strings, and will be
separated by white space or other separator characters. The maximum length
for a record in Data Explorer is 32 KB.
A field description is necessary for every field of a record which tells Data
Explorer about the format of the field and the name under which the contents of
the field will appear as a channel in Data Explorer. Every field must be defined
and is read by Data Explorer. Fields that are not to be used as channels should
be given a field name in lower case (if it is to be used as an internal variable) or
no name at all (if it is to be skipped).
The complete record description therefore has the following format:
RECORD recordname [recordlength]
FieldDescriptor 1

Data Explorer — User’s Guide

Data Explorer 153

FieldDescriptor 2
FieldDescriptor 3
.
.
FieldDescriptor n
ENDRECORD

recordname
Is a suitable name for the record to reference it later in the File section.
recordlength
Defines the length of the record. For ASCII files, this is the number of con-
secutive lines comprising a single record. If record length is not specified, 1
is assumed (1 line). For binary files, the record length is the number of bytes
and should therefore be specified. Identities may be used in specifying the
record length.
Field Descriptor For every field (values and text strings) a field descriptor is required. A field
descriptor has the following format:
fieldcnt format [ [width ndec] fieldname units description]

fieldcnt
Is normally 1. If greater than 1, it defines the number of times this field is
repeated (array function). If greater than 1, Data Explorer uses the given
field name for every field with sequential numbers:
e.g. 3 REAL CH: would generate channels CH_1, CH_2 and CH_3, each
with the same input format, units and description.
For column-based ASCII files, fieldcnt may also be set higher than the
number of columns actually contained in one line. CONCERTO will only
read as many fields as are contained in the line. Thus a field descriptor may
be kept dynamic.
e.g. 100 REAL CH: reads up to 100 real values
fieldcnt may also be an Identity.
format
Tells Data Explorer how to read the field from the data file:
For ASCII files, the keywords ASCII, REAL and INTEGER may be used to
define the field format. Fields must be separated by a field separator, typi-
cally white space, tab characters or semicolons. For text fields (ASCII) the
separator is necessary to define the end of the field. Number fields (REAL,
INTEGER) are read up to the first non-numeric character, but you may also
use the separation characters as described for ASCII below. Leading white
space is removed when reading values.

ASCII a single word of text terminated by white space

ASCIIx a text string terminated by the character x: e.g. ASCII;
means all text up to the first ";"
ASCIIT a text string terminated by a TAB character
An a text string occupying n bytes (n < 256)
INTEGER free-format integer value (also INTEGERT, INTE-
GERx)
REAL free-format real value (also REALT, REALx)

Permissible formats for Binary Files:

I1, I2, I4 Integer value occupying 1, 2 or 4 bytes

L1 logical value occupying 1 byte
R4, R8 real (float, double) values occupying 4 or 8 bytes
An a text string occupying n bytes (n < 256)

Data Explorer — User’s Guide

154 Data Explorer

width, ndec
Are optional – they may be used in numeric fields to define how the num-
bers will be formatted for display within Data Explorer. width defines the
output field width and ndec the number of decimals. width must be non-zero
– if width is specified and ndec is not, ndec takes the default value of 0.
If width is not specified, Data Explorer estimates a suitable output format for
numeric channels:
If the data has been read from an ASCII File, the width and number of dec-
imal places is preserved. If it has been read from a Binary File, Data
Explorer uses its best guess.
fieldname
Is a suitable name for the field. Names may be up to 16 characters in
length, must start with an alphabetic character and may not contain spaces.
The field name is used as the channel name within Data Explorer. The con-
tents of the field is the data contents of this channel.
Fields that are not to be presented as channels should be given a name in
lower case. Data Explorer will still read the field and memorize its contents
in an internal variable for possible later use as Identity.
Fields that are not assigned a name at all will be skipped by Data Explorer.

Example
1 ASCIIT

would skip a string terminated by a TAB character.

units
Is the channel's units string: it must not contain spaces and must be speci-
fied if a channel description follows. In this case an 'empty' unit string is
defined by specifying a hyphen ("-") in its place.
description
Is the channel's long description. It may contain spaces as it will be termi-
nated by the end of the line. If not used it may be omitted.

Example
Suppose a line in an ASCII file contains 3 values: engine speed, torque and
power.
The following record definition would describe these fields with channel names
N, M and P:
RECORD Results 1
1 REAL N Rpm Engine Speed
1 REAL M NM Engine Torque
1 REAL P kW Engine Power
ENDRECORD

Data Explorer — User’s Guide

Data Explorer 155

File Description A file description has the following format:

Section FILE filename [fileformat]
[detaildefinitions]
[baselinedefinitions]
typedefinitions
record allocation 1
record allocation 2
.
record allocation n
ENDFILE
File Definition FILE filename [fileformat]
filename
Is a name identifying the file description section for Data Explorer – this
must correspond to the dictionary name in the Data Source Properties
dialog. It can be identical to the descriptor file name itself.

Example
For example, the standard descriptor file for a column-based ASCII file has the
name CONCASC.DSC and contains a section CONCASC:
FILE CONCASC
DETAIL etc.
....
....
ENDFILE

fileformat
Is necessary when describing a Binary File. Data Explorer is able to read
not only DOS binary files, but also VAX/VMS and Motorola files. These
differ in the storage format for integers and real values:
fileformat may take therefore take the values
– DOS
– VAX or
– MOTOROLA
Detail Definition detaildefinitions
Are optional: they are used by Data Explorer to display file information in the
file properties dialog. Multiple DETAIL lines may be defined to describe
many lines of information. Each DETAIL line is a free-format text which may
contain Identities.

Example
DETAIL User defined data file
DETAIL Test No. : %test_no
DETAIL Test Date : %date %time
DETAIL %TEST_TITLE

where the identities %test_no, %date, %time and %TEST_TITLE have been
read from certain fields in the data file.

The first line in the properties dialog window will always be the file name
supplied by Data Explorer.

Data Explorer — User’s Guide

156 Data Explorer

Baseline Defini- When data with more than one point is to be read, a baseline definition is neces-
tions sary to tell Data Explorer how to construct the abscissa. If a channel is drawn
over its natural baseline, then this abscissa will be used as the X-axis.
BASELINE basename [units start stop interval] type [description]
basename
Is a suitable short name for use in the type definition line (see below). If this
reflects a channel from the file, then the attributes units, start, stop, interval
and description should be omitted.
units
Is the units string for this X-axis. An empty string is defined using a single
hyphen ("-").
start, stop
Are numeric values which define the range of the X-axis. Identity strings
may be used if this information is available in the file. It is also possible to
leave stop undefined. Data Explorer will then calculate the stop value itself
from the number of available data points. In this case, use a hyphen ("-")
instead of a stop value.
interval
Interval between the abscissa (x) values, either specified or read from the
file using an Identity.
type
Defines the baseline type and may take the values:
– TIMEBASED
– CRANKANGLE
– CYCLE
– LOGPOINT
description
Is a descriptive text for the abscissa and occupies the remainder of this line.

Example
A data file just contains columns of logpoint data without any dedicated abscissa.
Then a suitable baseline definition would be:
BASELINE PNT - 1 - 1 LOGPOINT -

This means: no units, starting point = 1, end point depends on amount of data,
interval = 1, no abscissa description.

Example
A data file contains a number of records, 1 per engine cycle. The header
contains a field ncycles which defines the number of cycles. A suitable baseline
definition would be:
BASELINE CYCLE - 1 %ncycles 1 CYCLE Cycle Number

Example
A data file contains Combustion Data. The header record contains the following
fields
A_START (starting crank-angle);
A_STOP (ending crank-angle);
A_RESOL (resolution)

The baseline definition is:

BASELINE CDM deg. %A_START %A_STOP %A_RESOL CRANKANGLE Crank Angle

Data Explorer — User’s Guide

Data Explorer 157

Type Definitions The type definition line has the following format:
DATATYPE key basename nCycles nPoints description
ALL attributes of a DATATYPE definition must be present:
typedefinitions
Describes to Data Explorer what categories of data (data keys) are avail-
able.
key
Is a 1 to 3-character abbreviation identifying the data key.
basename
Refers to a BASELINE definition. It describes the abscissa (X-axis) for all
channels of this data key. If there is no BASELINE definition to assign (for
example, when this category contains only data consisting of one value, like
header data), then a hyphen ("-") is used to denote an empty attribute.
Sometimes the X-axis is available on the data file itself as an actual data
column (baseline channel). In this case it can be read into an internal vari-
able (lower case field name) and this name is used as the basename in the
DATATYPE definition. Then all channels of this data key will have this
abscissa. Note however, that the abscissa channel must be defined within
the same data key, i.e. you can only use a baseline channel from the file if it
is within the same set of records.
Only baseline channels with monotonic increasing values with an identical
interval are supported.
nCycles
Is only used for cyclic data to define the number of cycles expected. In all
other cases this parameter should be set to zero.
nPoints
Defines the number of points (records) for all channels of this category. You
can make this variable by specifying either the value 999999 or a hyphen (-)
for nPoints. In the first case Data Explorer will calculate the number of
points to the end of the data file and in the second case, it calculates them
until the end of the table (or the end of the file) is reached. The end of a
table is reached when Data Explorer encounters a line with a different
number of fields. It is valid only for ASCII files.
description
Is a descriptive text for this data key that will be displayed together with the
key in the Data Explorer frame. It occupies the remainder of this line.

Example
For standard column-based logpoint data, the baseline and data type definition
could be:
BASELINE PNT - 1 - 1 LOGPOINT -
DATATYPE D PNT 0 - Measured Data

PNT refers to the preceding baseline definition of the same name.

Example
BASELINE CYCLE - 1 %ncycles 1 CYCLE Cycle Number
DATATYPE CYC CYCLE 0 %ncycles Cycle Data
DATATYPE ST - 0 1 Setup Parameters

These two definitions will generate two data keys. If the "ncycles" field contains
the value 55, then you will get:
CYC - Cycle Data (55)
ST - Setup Parameters

The DATATYPE ST corresponds to fields which have only one value in the data
file (parameters). It is not necessary to assign a BASELINE for such data.

Data Explorer — User’s Guide

158 Data Explorer

Example
A data file contains time-based data starting at time zero and recorded at 5 Hz
resolution. The overall duration could be of any length (until end of file). The
baselinedefinition and typedefinition might be:
BASELINE TIME sec. 0 - 0.2 TIMEBASED Time
DATATYPE TM TIME 0 999999 Time-based Data

If the file contains 5000 records, these statements will create an X-axis called
TIME with the range 0..1000 seconds which is used for all fields in data key TM.
The data key will be:
TM - Time-based Data (5000)

Example
A data file contains a channel called time which contains the number of seconds
from the start of recording. By defining the channel with a lowercase name, it will
not be available for selection as a channel. time is part of the same set of
records for which it is used as a baseline. The baselinedefinition and typedefi-
nition might be:
BASELINE time TIMEBASED
DATATYPE TM time 0 999999 Recorder Data

CONCERTO will generate the start, stop and interval values for an X-axis
using information from the time channel - this necessarily generates a mono-
tonic dataset with regular interval. If the file contains 600 records and the time
channel contains the values 0.00, 0.05, 0.10, 0.15 ... 29.95, 30.00, these state-
ments will create an X-axis called time with the range 0..30 at interval 0.05 which
is used for all fields in data key TM. The data key entry will be:
TM - Recorder Data (600)

Record Allocation The Record Definition in Record Definition on page 152 represents a template of
fields in a record. We have not yet described the actual order in which these
records appear in the data file.
In the FILE section we now have to define the proper sequence and number of
defined records. Also, for each record we need to declare which of the data keys
defined earlier it belongs to.
A record allocation has the following format: repeat recName [dtKey]
repeat:
Is a numeric value (or Identity) which defines the number of records. It can
be made variable by specifying 999999 to indicate 'end of file', or a hyphen
("-") to indicate 'end of table'.
recName:
Is the name of the record description used.
dtKey:
Is the key of a DATATYPE definition to which these records belong. If no
key is given, the data contained in these records will not be available for dis-
play, i.e. they are read in but skipped.

Example
For the simple column-based ASCII file above, the following record allocation
line would be used:
999999 DATA D

For a simple column-based data file containing time-based data (resolution 5

ms) with variable number of values:
BASELINE TIME sec. 0.0 - 0.005 TIMEBASED Time
DATATYPE TM TIME 999999 Time-based Data
999999 DATAREC TM

Data Explorer — User’s Guide

Data Explorer 159

1.9.10.3 Examples
Simple time-based
data Example
This example shows a simple ASCII table with time-based data. The first data
column (the name is not fixed) defines the abscissa (X-axis).
t1 n sync_ctrcb_ptr...
seconds[b][p]no_units...
0 661 4 8 ...
0.0056614 8 ...
0.016614 8 ...
0.0156564 8 ...
.
.
30 630 16 8 ...

The names, units and data records are defined as follows:

RECORD NAMES
99 ASCII name
ENDRECORD

RECORD UNITS
99 ASCII unit
ENDRECORD

RECORD DATAX
99 REAL %name %unit
ENDRECORD

FILE ADATAFILE
1 NAMES
1 UNITS
999999 DATAX TM
ENDFILE

The baselinedefinition and typedefinition would therefore be:

BASELINE %name_1 TIMEBASED
DATATYPE TM %name_1 0 999999 Recorder Data

Data Explorer — User’s Guide

160 Data Explorer

Cycle-based data
with file header Example
As a complete example, consider the following (ASCII) data file:
Test number : 0055
Date/Time : 07-05-91 11:07
Test engine using special spark plugs
Engine Name : AVL1234
Stroke : 86.000
Bore : 92.00
Length : 135.00
Compression : 8.00
Cycles : 13

Cycle IMEP MAX_PRESS A_PRESS MAX_RISE A_RISE

1 13.050000 59.400002 18.000000 1.400000 0.000000
2 13.700000 64.500000 18.000000 1.800000 3.000000
3 11.706250 41.900002 16.000000 0.900000 -21.000000
4 10.793750 41.799995 17.000000 1.000000 -18.000000
5 9.200000 35.000000 9.000000 0.700000 -28.000000
6 12.918750 54.599998 21.000000 1.200000 -2.000000
7 8.293750 33.900002 3.000000 0.800000 -18.000000
8 10.037500 37.599998 16.000000 0.800000 -14.000000
9 12.400001 47.099998 24.000000 0.800000 -17.000000
10 13.481250 59.199997 21.000000 1.200000 1.000000
11 8.925000 37.199997 11.000000 0.800000 -20.000000
12 13.387500 59.400002 21.000000 1.300000 3.000000
13 12.987500 51.900002 21.000000 0.900000 6.000000

The header data is fixed-format. There may be any number of lines of actual
data (in this case 13): the first 4 columns are always as above but these may be
followed by up to 4 additional columns (in our example 2) of other data.
The descriptor file for such data might be as follows (additional) remarks
preceded by "!" are not part of the file):

Data Explorer — User’s Guide

Data Explorer 161

Example
; Example Data File Descriptor ! It is always a good idea
! to keep it well documented
; Created by A.N.Engineer
; Date 26-August-1993
;------------------------------------------------------------------
! The first 11 lines of header data are defined as 1 record. Only
! STROKE, BORE, LENGTH and COMPRESSION will be needed for display - the ! rest are
used only within the descriptor file (and therefore do not
! need units and descriptions).
! RECORD HEADER 11
1 A22 ! line 1
1 ASCII test_no
1 A22 ! line 2
1 ASCII date
1 ASCII time
1 A50 comment ! line 3
1 A22 ! line 4
1 ASCII engine
1 A22 ! line 5
1 REAL STROKE mm Stroke
1 A22 ! line 6
1 REAL BORE mm Bore
1 A22 ! line 7
1 REAL LENGTH mm Length
1 A22 ! line 8
1 REAL COMPRESSION - Compression Ratio
1 A22 ! line 9
1 INTEGER ncycles
1 ASCII ! line 11 "Cycle"
3 A16 ! "IMEP MAX_PRESS A_PRESS"
4 A16 cname ! other channel names
ENDRECORD
;-------------------------------------------------------------------
RECORD DATAREC ! default record length is 1 line
1 INTEGER ! ignore cycle number
1 REAL IMEP bar Indicated Mean Effective Pressure
! leave output field width and decimal
! places for IMEP as read (16 6)
1 REAL 6 1 PX bar Peak Pressure
1 REAL 6 0 AP degCA Angle of Peak Pressure
! give MAX_PRESS and A_PRESS new names, units
! and descriptions and limit the output
! precision to remove trailing zeros and
! rounding errors
4 REAL %cname ! %cname_1 = "MAX_RISE"
! %cname_2 = "A_RISE"
! %cname_3 and 4 not allocated
ENDRECORD
;------------------------------------------------------------------
FILE ACID_RTP
DETAIL Acid RTP File ! info. to display in Details ListBox
DETAIL Indiskop file: %filename ! using fields read from file
DETAIL Date/Time : %date %time
DETAIL Engine : %engine
DETAIL %comment
BASELINE CYCLE - 1 %ncycles 1 CYCLE Cycle Number
! define x-axis values 1 to 13 step 1
! as cycle number
DATATYPE CYC CYCLE 0 %ncycles Cycle Data
DATATYPE ST - 0 1 Setup Parameters
! define 2 DataTypes CYC and ST
1 HEADER ST ! file consists of 1 HEADER record
! containing Setup Parameters and
%ncycles DATAREC CYC ! 13 DATAREC records with Cycle Data
ENDFILE

This example shows many of the possibilities of descriptor files. It is difficult to

assess whether a data file may be incorporated into Data Explorer using this

Data Explorer — User’s Guide

162 Data Explorer

method. In general, if the data has a 'regular' format (column-based ASCII or

record-based Binary), then it should be possible. The best way is to try.

1.9.11 Scripting Data Source

The scripting data source allows you to have a data source filled with scripts in
Data Explorer. Data Explorer automatically launches appropriate scripts which
return the test list and data.
This way you can program customer-specific data to be read into scripts (from
files or from databases). It represents a simple alternative to programming a user
DLL and is much more flexible than working with descriptor files.
Furthermore, using ADO (Active X Data Objects) you can easily access ODBC
databases from scripts and execute SQL commands.

1.9.11.1 Defining a Scripting Data Source

To create a new scripting data source, open the Data Source Definition Wizard
as usual. Select Script-based Tests as the data source format.
If you want the list of tests also to be returned from a script (when you access a
database, for instance, or when you want to generate virtual tests which display
a combination of several files), select the Script Based option under Test List.
If, on the other hand, you want to work with real files accessing the contents from
scripts, you should keep the File Based option.
On the next page of the Wizard, you can define the paths to the various scripts:
Test List Script
Script which returns the test list (only if Script Based was selected before-
hand).
Test Attribute Script
Script which returns attributes of the test for displaying in Data Explorer or
for filtering (only if Script Based was selected beforehand). Do not define
test attribute script if you want to extract the attributes from the data using
the file scan mechanism. Just leave the field empty.
Measurement Script
Script which returns all the data keys available in the test.
Channel Script
Script which returns the names of the channels.
Data Script
Script which returns the data contents of a channel.

1.9.11.2 General Structure of a Script

These scripts basically have the same function as macros. They are assigned a
certain number of arguments and return a result dataset.
To be able to receive arguments, the first line of the script has to contain an arg
statement and an appropriate number of variables has to be specified for the
arguments:
arg var1, var2, var3

Since multiple datasets have to be or may be returned for different scripts, an

array dataset is always used as the return format. You can create an array
dataset with the newDSArray function and insert the datasets as cell datasets in
the first row using PutCell.

Data Explorer — User’s Guide

Data Explorer 163

1.9.11.3 Script for Test List

Function This script returns the list of tests to be displayed to Data Explorer. It is also
possible to structure the data source hierarchically.
The script is then launched separately for each level.
Structure Passed parameters
– path: this is the string that is defined as the path (String) in the Data
Source Properties dialog. The entry is only used in the script itself. It
can therefore be used for any text information which is to be passed to
the test list script from elsewhere.
– selPath: contains the complete path string of the user’s current selec-
tion in Data Explorer. The path permits the use of structure levels
between the data source and the file. The script is assigned the path
and can decide from that whether it returns a finished list of test names
or another structure level (i.e. folder list) to Data Explorer. If the path is
empty, the data source node itself was selected in the Data Explorer
tree. The script then has to return the list for the uppermost level.
The option flag has to be set accordingly and returned at the same
time in order to communicate to Data Explorer whether the returned list
is a test list or a folder list (see below $OPTIONS$).
– condition: this string contains the current filter condition which is nec-
essary to be able to create a suitable database query, for example. The
script then carries out the filtering itself, as it were. If, on the other
hand, Data Explorer does the filtering, the condition argument can be
ignored. Either way, the option flag has to be set accordingly.
Return dataset
The script returns lists with names of tests but (if the file scan method is not
applied) it returns lists of the test attributes. Every list has to be structured
as a normal text dataset.
All the datasets also have to be grouped into a dataset array, i.e. a dataset
array has to be created and the datasets inserted in the cells of the first line
of the array.
The name of the dataset that contains the test names has to be Name.
It is displayed in Data Explorer as the first column of the test list. The other
attribute datasets also have to be given names which designate the
headers of the Data Explorer columns.
Finally, the option flag has to be inserted in the array as a dataset. The com-
plete dataset array is returned to Data Explorer via the return statement.
Option flag ($OPTIONS$):
The reserved option flag $OPTIONS$ is used to pass additional information
to Data Explorer from the scripts. To use $OPTIONS$, you have to create a
dataset with this name in the script and insert it in the dataset array to be
returned. Data Explorer finds it via the reserved name and evaluates the
content accordingly.
The option flag is a dataset which consists of two values, the structure flag
and the filter flag.
– Structure flag: defines whether the test list script returns structures or
tests.
Value=0: indicates that the script returns a list of test names ("file list").
Value=1: indicates that the script does not return a test list but a list of
names from a higher hierarchy level ("Folder list").
– Filter flag: defines whether defined filters are executed by the script or
by Data Explorer.
Value=0: indicates that the script has filtered the returned test or folder
list itself based on the condition argument.
Value=1: indicates that the script returns an unfiltered list.
If no $OPTIONS$ dataset is created, the following defaults apply:

Data Explorer — User’s Guide

164 Data Explorer

Opt= {0,1}, i.e. the script returns a test list and filtering is done in Data
Explorer.

Example
With subfolders
arg aPath, selPath, condition

if selPath = "" then

iTestSeries = {"Sub_1","Sub_2"}
iTestSeries.Name = "Name"
output=NewDSArray (1,1)
output.PutCell(iTestSeries,1,1)

output.AddColumn ("$OPTIONS$")
opt = {1,0}
output.PutCell (opt, 0, output.ColCount)
else
if selPath = "Sub_1" then
iTest = {"Test_1","Test_2"}
iTest.Name = "Name"
output=NewDSArray (1,1)
output.PutCell(iTest,1,1)
else
iTest = {"Test_3","Test_4"}
iTest.Name = "Name"
output=NewDSArray (1,1)
output.PutCell(iTest,1,1)
endif
output.AddColumn ("$OPTIONS$")
opt = {0,1}
output.PutCell (opt, 0, output.ColCount)
endif

return output

This script creates the following test list in Data Explorer:

Fig. 123

Example
With no subfolders
arg aPath, selPath, condition

iTest = {"Test_1","Test_2"}
iTest.Name = "Name"
output=NewDSArray (1,1)
output.PutCell(iTest,1,1)

return output

This script creates the following test list in Data Explorer:

Fig. 124

Data Explorer — User’s Guide

Data Explorer 165

Only defined test names are set in the simple example above. In practice,
the data access to the data source has to be programmed here in the script.

1.9.11.4 Script for Test Attributes

Function This script returns a list of the attribute names that are to be displayed in the
Data Explorer filter dialog.
Structure Passed parameters
None
Return dataset
A dataset has to be created that contains the attributes to be used as the
string list. The name of the dataset must be set to Name. Even though there
is only one dataset, an array still has to be created for returning and the
attribute list dataset has to be inserted in cell 1,1.

Example
Attr_List = New (1, "")
Attr_List.y[1] = "Name"
Attr_List.Name = "Name"
output=NewDSArray (1,2)
output.PutCell(Attr_List,1,1)
return output

1.9.11.5 Script for Data Keys/Measurements

Function This script has to return the data keys to be displayed for the selected test
together with their descriptions. It is launched when you click on a test in Data
Explorer. If the test is to divide the data further into measurements (as is
customary with ASAM), the data key and measurement ID have to be returned
for each measurement.
Structure Passed parameters
– path: Full data source path of the selected test
– testName: Name of the selected test
Return dataset
The script returns a list of all the data keys that are to be visible under the
test. An abbreviation, the data key, as well as a description text for display in
Data Explorer has to be returned in each case.
If the test is to be made up of individual measurements (as in the ASAM
data model), a further dataset has to be created with the measurement
numbers (i.e. measurement IDs). If more than one measurement is of the
same data key, there is more than one identical entry in the data key
dataset (or in the description dataset) because there has to be an entry for
each measurement.
Data keys are displayed as logpoint by default. If you create a dataset with
the name Type, you can define the type of the individual measurements by
setting the following attributes:
– "Logpoint"
– "Timebased"
– "Crankangle"
– "Cycle"
As a result, at least two of the four datasets have to be returned which in
turn have to be packed into an array. The dataset that contains the data key

Data Explorer — User’s Guide

166 Data Explorer

strings has to have the name Name and the dataset that contains the
descriptions must have the name Description.

Example
With no measurements
arg path, testName

iMeasName = New(7,"")
iMeasName.Name = "Name"
iMeasName.y[1] = "$B"
iMeasName.y[2] = "D"
iMeasName.y[3] = "D"
iMeasName.y[4] = "D"
iMeasName.y[5] = "TM"
iMeasName.y[6] = "CA"
iMeasName.y[7] = "CYC"

iDescription = New(7,"")
iDescription.Name = "Description"
iDescription.y[1] = "Beginning Dialog"
iDescription.y[2] = "General Data"
iDescription.y[3] = "General Data"
iDescription.y[4] = "General Data"
iDescription.y[5] = "timebased Data"
iDescription.y[6] = "crankangle Data"
iDescription.y[7] = "cyclebased Data"

iType = New(7,"")
iType.Name = "Type"
iType.y[1] = ""
iType.y[2] = "Logpoint"
iType.y[3] = ""
iType.y[4] = ""
iType.y[5] = "Timebased"
iType.y[6] = "CrankAngle"
iType.y[7] = "Cycle"

output=NewDSArray (1,3)
output.PutCell(iMeasName,1,1)
output.PutCell(iDescription,1,2)
output.PutCell(iType,1,3)

return output

This script creates the following in Data Explorer:

Fig. 125

Data Explorer — User’s Guide

Data Explorer 167

Example
With measurements
arg path, testName

iMeasName = New(7,"")
iMeasName.Name = "Name"
iMeasName.y[1] = "$B"
iMeasName.y[2] = "D"
iMeasName.y[3] = "D"
iMeasName.y[4] = "D"
iMeasName.y[5] = "TM"
iMeasName.y[6] = "CA"
iMeasName.y[7] = "CYC"

iId = {1,1,2,3,1,1,1}
iId.Name = "Id"

iType = New(7,"")
iType.Name = "Type"
iType.y[1] = ""
iType.y[2] = "Logpoint"
iType.y[3] = ""
iType.y[4] = ""
iType.y[5] = "Timebased"
iType.y[6] = "CrankAngle"
iType.y[7] = "Cycle"

output=NewDSArray (1,4)
output.PutCell(iMeasName,1,1)
output.PutCell(iId,1,2)
output.PutCell(iDescription,1,3)
output.PutCell(iType,1,4)

return output

Data Explorer — User’s Guide

168 Data Explorer

This script creates the following in Data Explorer:

Fig. 126

Only defined data keys are set in the simple example above. In practice, the
data access to the data source has to be programmed here in the script.

1.9.11.6 Script for Measurement Channels

Function This script returns the channel names to be displayed for each data
key/measurement. It is launched when you click on a data key in Data Explorer.
Structure Passed parameters
– path: Full data source path of the selected test.
– testName: Name of the selected test
– dt: Name of the active data key
– measId: ID of the active measurement
A variable is set in the measurement channel script which contains a string
list of the names (iName in example below).
The name of the variable must be set to Name. A variable with the name
Units is created for the units which contains a string list with the names of
the units to be displayed for the measurement channels. The assignment
between measurement channel names and units is index-based. The same
applies to the description (the name of that variable must be Description)
and the channel type displayed, which is "Numeric" by default. Further
channel types include "Text", "DATE" and "TIME" which have to be defined
in a variable named Type. The datasets are packed into a matrix dataset.

Data Explorer — User’s Guide

Data Explorer 169

Return dataset
The script has to return both a dataset with a list of the channels of the
assigned data key (measurement) (dataset name: Name), and a dataset of
the corresponding units (dataset name: Unit) in an array.

Example
arg path, testName, dt, measId

if(dt = "$B") then

iName = {"Eng_Code","Tst_Strt"}
iDescription = {"Engine Code","StartDate"}
iUnit = {"-","-"}
iType = {"String","Date"}
elseif(dt = "D") then
iName = {"Speed","Torque","P"}
iDescription = {"Actual Speeed","Actual Torque","Actual P"}
iUnit = {"rpm","Nm","kW"}
iType = {"","",""}
elseif(dt = "TM") then
iName = {"N","Alpha"}
iDescription = {"Speed","Throttle Position"}
iUnit = {"1/min","%"}
iType = {"",""}
elseif(dt = "CA") then
iName = {"PCYL1","V"}
iDescription = {"",""}
iUnit = {"bar","-"}
iType = {"",""}
elseif(dt = "CYC") then
iName = {"CURTIME","Speed"}
iDescription = {"Cycle Duration","Engine Speed"}
iUnit = {"ms","rpm"}
iType = {"",""}
endif

iName.Name = "Name"
iUnit.Name = "Units"
iDescription.Name = "Description"
iType.Name = "Type"

output=NewDSArray (1,4)
output.PutCell(iName,1,1)
output.PutCell(iUnit,1,2)
output.PutCell(iDescription,1,3)
output.PutCell(iType,1,4)

return output

Only defined channel names are set in the simple example above. In prac-
tice, the data access to the data source has to be programmed here in the
script.

Data Explorer — User’s Guide

170 Data Explorer

1.9.11.7 Script for Measurement Data

Function This script delivers the data values to be displayed for one or more measure-
ment channels. It is launched automatically when you open a preview of a
channel in Data Explorer or when a channel or a set of channels is used in a
display object or a calculation.
Structure Passed parameters
– path: Full data source path of the selected test
– testName: Name of the selected test
– dt: Name of the active data key
– measId: ID of the active measurement
– dsNameList: list of the names of each channel for which data is to be
returned
Return dataset
Datasets have to be generated for all the names in the passed channel
name list (dsNameList) and filled with the corresponding values (numeric or
ASCII).
The names of the datasets have to correspond to the passed channel
names. All the datasets must be returned again in the form of an array
dataset.

Example
arg path, testName, dt, measId, dsList

output = NewDSArray (1, dsList.Count)

for i = 1 to dsList.Count
Values = {1..10}
Values.Name = dsList.y[i]
output.PutCell(Values, 1, i)
next i

return output

In the simple example above, exactly 10 points with the values 1 to 10 are
returned for all the channels. In practice, the data access to the data source
has to be programmed here in the script.
The base of the returned data is derived from the data key, unless the base
was defined differently in the script for measurement data or inherited from
a referenced channel.
Base name Base unit Base description
Logpoint: "Logpt" "" "Logpoint based data"
Time: "Time" "sec." "Elapsed Time"
CA-based: "CDM" "deg." "Crank Angle"
Cycle: "Cycle" "" "Cycle Number"

These default values can be changed manually in the data environment file.
For more on this topic, see Script-based Tests on page 89.

Data Explorer — User’s Guide

Index 171

Index
Symbols B
$-character … 49 binary format
$OPTIONS$ … 163 read … 40
$T … 143 BOBCAT Data File … 33
BORE … 39
A
ACAP/CAS … 88 C
acquisition unit … 39 CA … 37
AdditionalText … 31 CAF … 40
alias calculable formulas … 145
channel names … 144 calibration
name … 7 factor … 31
open with new alias … 19 offset … 31
amplifier Cameo Optimisation Results … 33
attributes … 31 CAO … 38
calibration date … 32 CycleCountConstant … 38
channel position … 32 CAOAbscissaRelatedtoCycle1 … 38
filter … 31 CAOCycleCountConstant … 38
measurement range … 31 CAOIndividualZeroLevel … 38
offset … 31 CDMRNGST … 39
channel
rack type … 32
copy … 30
range … 31
preview … 26
RangeUnit … 31
translate … 100
sensor sensitivity … 31
validate/invalidate … 30
serial number … 32
channel context script … 102
serial number of sensor … 31
channel group text … 87
temperature … 32 channel list
type … 31 show as test attribute … 50
unit … 31 channel name … 112
AmplifierCalibrationDate … 32 ChannelGroupText … 87
AmplifierChannel … 32 Composer … 120, 125
AmplifierGain … 32 ComposerFile
AmplifierRackSerialNumber … 32 generate from search query … 70
AmplifierRackType … 32 concerto.dxv entries
AmplifierTemperature … 32 ~Mime~ … 147
API … 42 AllowMultiOpen … 137
ASAM ODS
Ascii2Time … 80
Data Base … 32
ATFSingleTestMode … 32, 83
data, save … 124
AttachmentPath … 148
saving dialog … 124
AutoRefreshOpenTests … 111
ASCII
BaseUnitFromQuantity … 111
interpretation file … 94
BitChannels … 80
ASCII file
read … 40 CaseSensitiveChannels … 112
AST DataModel … 107
Gid File … 32 DB_LOGIN … 107
Rep File … 32 DeletedTestFlag … 71, 108
AST Simulation … 32 DeleteTestFlag … 122
ATF DescFSizeAttrName … 110
export … 19 Dictionary1 … 88
ATF (ASAM Transport Format) … 32 DigalogModel … 84
ATIVISION MAT File … 33 DspSignalAsChannel … 88
attachments … 147 EnableAodsSecurity … 112
attribute EncryptPasswords … 112
test … 52 ExplicitIndependentLogpoint … 109
attributes … 31 ExplicitIndependentName … 109
AveragedIFiles … 33 ExternalVolumeFile … 84
AVL InMotion … 33
FilterEmptySeries … 108
HideEmptyMeas … 81

Data Explorer — User’s Guide

172 Index

HideMeas … 81 crank angle data … 8

HoribaLineOriented … 84 CreateFormulaDependencyFile.csf … 145
HugeDataThreshold … 136 CTF
LoadRange … 112 export … 19
LoginCaseSensitivity … 113 cursor window
MatlabTranspose … 85 channels, alphanumeric … 86
MDFChannelGroupText … 87 CY (result values) … 39
cycle-based data … 8
MDFHeaderChannelLanguage … 87
CYF (cycle based formulas) … 40
MDFKeyDescription … 85
Cylinder volume, absolute … 37
MDFKeyName … 87
MDFShowLongNames … 86 D
MDFShowMeasurement … 86, 89
data
MDFSingleTM … 86
change using cursor … 28
MDFVMThreshold … 88
create artificial data … 120
MeaBase … 109
edit … 28
MeaDescription … 109
embed data from data source … 149
MeaTime … 109
filtering … 48
MeaVersion … 109
measurement splitting … 129
MeqDatatype … 110
refresh … 111
MeqDescription … 110
search for data contents … 58
MergeMeasNames … 139
data environment … 73
MimeGroupName=Att_%s … 147 close … 14, 26
MultiAsciiSettings … 88 global … 73
OrderOnIndependentChannel … 109 open … 14
PhysicalDeleteMeas … 113 reload … 14, 26
PreviewChannels … 136 replace … 14, 26
QtyDescription … 110 save … 14
QueryFiles … 82, 114 data environment file (DXV) … 7, 73, 79
QueryName … 82 data source
Recursive … 82 create … 74
ResolveReferences … 114 definition … 7, 12
Rpc_Timeout … 107 separating line … 13
SantorinServer … 107 data source context script … 101
SeriesAttr1/2 … 107 data source definition wizard … 74, 103
SetLoadRangeOnPreview … 137 date display … 90
ShowChannelAttributes … 82 DCM Data File … 33
ShowTemporaryNames … 111 Description … 31
TestValidIfEmpty … 114 descriptor file … 40
TimeBase … 88 DIAdem DAT File … 33
DIAdem TDM/TDMS File … 33
UniqueTestNames … 114
dico.txt … 142
UnitGain … 111
DIGALOG Data File … 33
UnitOffset … 111 display options (filtered tests) … 68
UseLastLogin … 107 drift compensation … 32
VirtualChannels … 110, 114 DXV … 73
concerto.ini entries DXV entries
AliasTableFile … 144 FileSpec … 92
AodsDateFormat … 90 format … 92
CAOAbscissaRelatedtoCycle1 … 38 DXV file … 7
CAOIndividualZeroLevel … 38
DialogOnNavigateFail=0 … 71 E
EnvironmentFile … 73 ENG_TYPE … 39
FileDateFormat … 90 EPSILON … 39
GlobalEnvironmentFile=*.DXV … 73 Explicit Independent channel … 109
IFileTimeBase … 39 Explorer bar
LegacyConverter=1 … 94 change view … 95
ScannerFile … 50 separating line … 13
concsemi.dsc … 151 export
conctab.dsc … 151 ATF, MDF4, CTF … 19
CONROD … 39 extended query … 56
context script … 100 selection … 56
conversion program … 41, 94 syntax … 57

Data Explorer — User’s Guide

Index 173

external file editor … 103 IFileCAOCylcles … 38

external references … 147 INI File … 34
Intermediate Recorder Results … 34
F invert selection
FAMOS Data File … 33 channel … 30
file record … 30
format (ASCII) … 40
format (binary) … 40 L
format settings … 79 load measurement range … 112
read in with optimized memory utilization … 88 loading large amounts of data … 134
replace … 43 log-in … 105, 113
file editor … 103 logpoint data … 8
file format settings … 80
file format specific functions … 79 M
FILESCAN.TXT … 50 Magic Analysis Result File … 34
FileSpec … 92 map file … 142
FileStorageClient … 148 MATLAB MAT File … 34
filter … 31, 48 MDF
by attributes (ASAM host) … 62 export … 19
by data (ASAM host) … 62, 64 MDF File … 34
by test … 48 measurement
by test (ASAM Host) … 52 delete … 113
by text … 49 save … 125
edit … 14 split … 130
extended … 56 measurement point context script … 103
for data contents … 58 measurement type
filter condition … 15 merge … 139
activate/deactivate … 51 rename … 139
delete … 52 MSC (formulas) … 40
extended … 56 Multi ASCII … 36
Multi ASCII File Types … 34
filter conditions editor … 70
MultiASCII
firmware version … 39
interpretation file … 94
folder
hide empty folders … 95 multiascii.ini
path definition … 94
form table
channels, numeric/alphanumeric display … 87 path definition (DXV entry) … 88
format settings … 79-80
format specific functions … 79 N
formula normname
calculable … 145 change … 126
display … 23 replace … 144
display priority … 23 translation … 142
path … 98 normname unit … 111
formula dependency file … 145 NRSTROKE … 39
Formula/Script Editor operations on empty tests
… 114 O
open … 43
G OR operation … 56
GCA Rep File … 33 original file name … 39
Generic ASCII File (auto-detect format) … 35 output offset … 31
GEO … 39
GEOUNIT … 39 P
global data environment file … 79 PAR (parameters) … 39
GTPower … 33 password … 105
encrypt … 112
H path definition
Horiba VETS Export File … 34 consistent path … 79
formulas … 98
I path variable
icons … 15 change … 14-15
IFAV.EXE … 33 editor … 14-15
IFile … 34, 37 PAtools Erg (Kratzer Automation) … 34
averaged … 33 PC Indiskop Work File (MTF) … 34

Data Explorer — User’s Guide

174 Index

PC-based PUMA TRR File … 34 delete … 108, 122

picture hide … 108
preview … 27 replace … 43
PINOFF … 39 save … 125
PinOffType … 31 test attribute … 52
POLY_COEFF … 39 add … 50
preview channels … 135 test context script … 101
properties … 9 test copy … 114
PUMA Recorder File … 34 test series context script … 101
text filters … 49
Q time display … 90
QtyDatatype … 110 time-based data … 8
query TIMESTAMP … 39
default … 56 TM (time-based measurement channels) … 39
extended … 56 TMF (time based formulas) … 40
file … 57, 82 Transport File … 34
for all data sources … 56
for one data source … 56 U
UNC … 79
R unit
record … 8 convert … 143
validate/invalidate … 30 unit conversion
RedLine File (DSP) … 34 dico.txt file … 142
reference Universal File Format (Type58) … 34
to ASAM-DB tables … 114 user license … 39
reference attributes … 114 user rights
concatenate … 118 suppress query … 112
in filter conditions … 119 user variable
in data source … 76
Registry Server … 104
in filter conditons … 71
S in layout … 76
in work environment … 76
Santorin Registry Server … 104
path … 14-15
Script-based Tests … 34
sensor uservariables.ini … 76
sensitivity … 31
SensitivityUnit … 31 V
SerialNumber … 31 V … 37
serial number … 39 V_ABS … 37
series VAL (result values) … 40
create from logpoint data … 19, 24 value
create from time-based data … 19, 24 edit … 28
server load balancing … 104 validate/invalidate … 29
SignalType … 31 VAX Indiskop Work File … 34
software options … 39 VAX-based PUMA TRR File … 35
software version … 39 VOFF2n … 37
STA (statistics values) … 40 VOFF2n_ABS … 37
static data … 8 VOFF2p … 37
step VOFF2p_ABS … 37
factor … 31 VOFFn … 37
offset … 31 VOFFn_ABS … 37
VOFFp … 37
STROKE … 39
VOFFp_ABS … 37
SYS … 39
volume channels (V) … 37
system variable … 49
volume curve … 84
volume, external … 84
T
table Y
channels, numeric display … 86
Yokagawa DL9000 … 35
TDC
Yokagawa WT1600/WT300 Trace … 35
offset … 31
value … 31
TDM File … 33
TDMS File … 33
test … 7

Data Explorer — User’s Guide

Index 175

Z
zero level correction
all cycles … 38
ZIP format … 41
zipped files … 41

Data Explorer — User’s Guide

176 Index

Data Explorer — User’s Guide

FOR FURTHER INFORMATION PLEASE CONTACT:

AVL List GmbH, Hans List Platz 1, 8020 Graz, Austria

Phone: +43 316 787-0, Fax: +43 316 787-400, eMail: [email protected], http://www.avl.com

EndoScan-V User Manual
No ratings yet
EndoScan-V User Manual
195 pages
Scripting in Puma Open Avl Puma Open 201 PDF
100% (1)
Scripting in Puma Open Avl Puma Open 201 PDF
384 pages
Progress Programming Handbook
No ratings yet
Progress Programming Handbook
1,024 pages
OpenText ContentBridge CE 21.2 - User Guide English (EDCCM210200-UGD-En-1)
No ratings yet
OpenText ContentBridge CE 21.2 - User Guide English (EDCCM210200-UGD-En-1)
456 pages
Assembly Process
No ratings yet
Assembly Process
169 pages
Wis Asra User Manual e
No ratings yet
Wis Asra User Manual e
144 pages
openLCA 1.10.2 User-Manual
No ratings yet
openLCA 1.10.2 User-Manual
127 pages
Case Study Example Kodak
0% (1)
Case Study Example Kodak
19 pages
As 3688-2005 Water Supply - Metallic Fittings and End Connectors
0% (1)
As 3688-2005 Water Supply - Metallic Fittings and End Connectors
8 pages
Progress SQL 89
No ratings yet
Progress SQL 89
156 pages
Spnu151j PDF
No ratings yet
Spnu151j PDF
202 pages
Optimizing C C++ Compiler
No ratings yet
Optimizing C C++ Compiler
201 pages
Thermal Images Analysis Report Software: User's Manual
No ratings yet
Thermal Images Analysis Report Software: User's Manual
42 pages
Results User Guide Windows
No ratings yet
Results User Guide Windows
192 pages
Database System Design Term Project12
No ratings yet
Database System Design Term Project12
99 pages
Introduction to Bioinformatics and Clinical Scientific Computing 1st Edition Instant DOCX Download
100% (3)
Introduction to Bioinformatics and Clinical Scientific Computing 1st Edition Instant DOCX Download
17 pages
Tf6100 Tc3 Opc-Ua en
No ratings yet
Tf6100 Tc3 Opc-Ua en
266 pages
NeroExpress Eng
No ratings yet
NeroExpress Eng
121 pages
Visualization Environment For Rich Data Interpretation (VERDI 1.4.1) : User's Manual
No ratings yet
Visualization Environment For Rich Data Interpretation (VERDI 1.4.1) : User's Manual
130 pages
DataManipulation GettingStarted en
No ratings yet
DataManipulation GettingStarted en
76 pages
Actix Analyzer CDMA1 X Training Manual
0% (1)
Actix Analyzer CDMA1 X Training Manual
163 pages
OpenLCA 1.10 User-Manual
No ratings yet
OpenLCA 1.10 User-Manual
126 pages
Java TM Application Development on Linux R 1st Edition Carl Albing pdf download
No ratings yet
Java TM Application Development on Linux R 1st Edition Carl Albing pdf download
54 pages
Win Hex Manual
No ratings yet
Win Hex Manual
123 pages
IWF Metadata Harvester Manual: Laurence D. Finston
No ratings yet
IWF Metadata Harvester Manual: Laurence D. Finston
181 pages
Administracion de Bases de Datos en Progress PDF
No ratings yet
Administracion de Bases de Datos en Progress PDF
742 pages
UserManual PDF
No ratings yet
UserManual PDF
370 pages
ERASOFT RCS Manual v3.1
No ratings yet
ERASOFT RCS Manual v3.1
74 pages
Opensupport Eng
No ratings yet
Opensupport Eng
78 pages
JasperServer Admin Guide
100% (1)
JasperServer Admin Guide
98 pages
Xlate Evolution User Guide
No ratings yet
Xlate Evolution User Guide
352 pages
Pan Sys UG
No ratings yet
Pan Sys UG
674 pages
AntManual1 5
No ratings yet
AntManual1 5
305 pages
Tutorial
No ratings yet
Tutorial
56 pages
FSWP UserManual en 12
No ratings yet
FSWP UserManual en 12
662 pages
MSP430 Optimizing C - C++ Compiler
No ratings yet
MSP430 Optimizing C - C++ Compiler
184 pages
Assignment - Database Design and Development
No ratings yet
Assignment - Database Design and Development
47 pages
OpenLCA 1 9 User Manual
No ratings yet
OpenLCA 1 9 User Manual
127 pages
Man Vlocpro2 en 03-4
No ratings yet
Man Vlocpro2 en 03-4
78 pages
User's Guide: MSP430 Optimizing C/C++ Compiler v18.1.0.LTS
No ratings yet
User's Guide: MSP430 Optimizing C/C++ Compiler v18.1.0.LTS
181 pages
Opentext Tableau tx1 User Guide 22 1 en
No ratings yet
Opentext Tableau tx1 User Guide 22 1 en
180 pages
User Guide Persistence Client Library
No ratings yet
User Guide Persistence Client Library
41 pages
FE SizerUserManual
No ratings yet
FE SizerUserManual
144 pages
Compass Reference
No ratings yet
Compass Reference
206 pages
Yea Sia c887 1.4b SFTWR Man
No ratings yet
Yea Sia c887 1.4b SFTWR Man
461 pages
(Ebook) Programming Fundamentals: A Modular Structured Approach Using C++ by Kenneth Leroy Busbee ISBN 9781616100650, 1616100656 - The ebook in PDF format with all chapters is ready for download
100% (1)
(Ebook) Programming Fundamentals: A Modular Structured Approach Using C++ by Kenneth Leroy Busbee ISBN 9781616100650, 1616100656 - The ebook in PDF format with all chapters is ready for download
46 pages
As Info
No ratings yet
As Info
308 pages
Disksavvy Manual
No ratings yet
Disksavvy Manual
98 pages
MSC 1210 Ug
No ratings yet
MSC 1210 Ug
280 pages
Benefits of semantic data models. A study in the European goods transport industry
From Everand
Benefits of semantic data models. A study in the European goods transport industry
Andreas A. Pelekies
No ratings yet
Facility Management: Business Process Integration
From Everand
Facility Management: Business Process Integration
Alexander Redlein
No ratings yet
Smart Card Applications: Design models for using and programming smart cards
From Everand
Smart Card Applications: Design models for using and programming smart cards
Wolfgang Rankl
No ratings yet
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
From Everand
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
Michael Basler
No ratings yet
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Prediction of Burnout: An Artificial Neural Network Approach
From Everand
Prediction of Burnout: An Artificial Neural Network Approach
Felix Ladstätter
No ratings yet
Programming the Photon: Getting Started with the Internet of Things
From Everand
Programming the Photon: Getting Started with the Internet of Things
Christopher Rush
5/5 (1)
Pollution Prevention: Methodology, Technologies and Practices
From Everand
Pollution Prevention: Methodology, Technologies and Practices
Kenneth L. Mulholland
No ratings yet
Analyzing Food Security Using Household Survey Data: Streamlined Analysis with ADePT Software
From Everand
Analyzing Food Security Using Household Survey Data: Streamlined Analysis with ADePT Software
Ana Moltedo
No ratings yet
Analyzing Food Security using Household Surveys
From Everand
Analyzing Food Security using Household Surveys
World Bank Staff
No ratings yet
Unlocking Statistics for the Social Sciences
From Everand
Unlocking Statistics for the Social Sciences
Norma Sinclair
No ratings yet
Programming Arduino: Getting Started with Sketches
From Everand
Programming Arduino: Getting Started with Sketches
Simon Monk
3.5/5 (5)
Companies and Environmental Impact: Identification and Visualization of Key Ecological Indicators
From Everand
Companies and Environmental Impact: Identification and Visualization of Key Ecological Indicators
Martin Knura
No ratings yet
A Method of Fuel Testing in A CFR Engine
No ratings yet
A Method of Fuel Testing in A CFR Engine
63 pages
MEC126 - COMBUSTION - List 3 / Reactors: 1 Problem 6.12 (Turns, 2013) - Fixed Volume Reactor
No ratings yet
MEC126 - COMBUSTION - List 3 / Reactors: 1 Problem 6.12 (Turns, 2013) - Fixed Volume Reactor
17 pages
MEC126 - Combustion I - Program 2015
No ratings yet
MEC126 - Combustion I - Program 2015
2 pages
Steam Engine Indicator Diagram: Effect of Piping Arrangements
No ratings yet
Steam Engine Indicator Diagram: Effect of Piping Arrangements
54 pages
List 1 - Stoichiometry
No ratings yet
List 1 - Stoichiometry
2 pages
Rate Constants For Formation Mechanism1: Nitrogen
No ratings yet
Rate Constants For Formation Mechanism1: Nitrogen
3 pages
Series Quality System Product Certification: ISO9001 / ISO14001 / ISO45001
No ratings yet
Series Quality System Product Certification: ISO9001 / ISO14001 / ISO45001
2 pages
Tor and The Deep Web - How To Be Anonymous Online in The Dark Net The Complete Guide PDF
0% (1)
Tor and The Deep Web - How To Be Anonymous Online in The Dark Net The Complete Guide PDF
76 pages
Mathematical Induction PDF
No ratings yet
Mathematical Induction PDF
8 pages
Asmea - Ba Ms - Jan 2023 - Isoiec 27001 Isms Whitepaper
No ratings yet
Asmea - Ba Ms - Jan 2023 - Isoiec 27001 Isms Whitepaper
14 pages
OTC in ECC vs S4 HANA - A Comparative Study
No ratings yet
OTC in ECC vs S4 HANA - A Comparative Study
10 pages
Claimant Information: Funds/claimants/contact-Us#form
No ratings yet
Claimant Information: Funds/claimants/contact-Us#form
1 page
Full download The Use Case and Smart Grid Architecture Model Approach The IEC 62559 2 Use Case Template and the SGAM applied in various domains 1st Edition Marion Gottschalk pdf docx
100% (1)
Full download The Use Case and Smart Grid Architecture Model Approach The IEC 62559 2 Use Case Template and the SGAM applied in various domains 1st Edition Marion Gottschalk pdf docx
65 pages
Cellrefs 3G Adel Ericsson
No ratings yet
Cellrefs 3G Adel Ericsson
620 pages
Activity 9 Alcala
100% (1)
Activity 9 Alcala
5 pages
Literature Review: Modern Public Library
100% (3)
Literature Review: Modern Public Library
8 pages
BEC Vantage Answer Sheet Reading
No ratings yet
BEC Vantage Answer Sheet Reading
1 page
Multiple Access Techniques
No ratings yet
Multiple Access Techniques
54 pages
LAWS Affirm-Traditional Cut
No ratings yet
LAWS Affirm-Traditional Cut
6 pages
TD10008
No ratings yet
TD10008
5 pages
Manoj Kumar: Core Knowledge and Functional Skill Areas
No ratings yet
Manoj Kumar: Core Knowledge and Functional Skill Areas
4 pages
10 HTML Quotations
No ratings yet
10 HTML Quotations
5 pages
Lecture - 1
No ratings yet
Lecture - 1
46 pages
Lesson 3 Operators (Các Phép Toán)
No ratings yet
Lesson 3 Operators (Các Phép Toán)
3 pages
NT Acou 082 - Buildings - Vibration and Shock - Evaluation of Annoyance - Nordtest Method
No ratings yet
NT Acou 082 - Buildings - Vibration and Shock - Evaluation of Annoyance - Nordtest Method
9 pages
Flare System Design - Basics & Familiarization Module PDF
No ratings yet
Flare System Design - Basics & Familiarization Module PDF
63 pages
Our-findings-pdf
No ratings yet
Our-findings-pdf
31 pages
Data Security Course
No ratings yet
Data Security Course
86 pages
506 Lab On Internet Technology and C Sharp 101020
No ratings yet
506 Lab On Internet Technology and C Sharp 101020
4 pages
Aws Certified Ai Practitioner Aif c01 (1)
No ratings yet
Aws Certified Ai Practitioner Aif c01 (1)
50 pages
Does IT Payoff? Case Study
No ratings yet
Does IT Payoff? Case Study
4 pages
AIRs-LM - Math 10 QUARTER 4-Weeks 6-7 - Module 5
100% (5)
AIRs-LM - Math 10 QUARTER 4-Weeks 6-7 - Module 5
20 pages
SLX SX Elevator Maintenance Manual
No ratings yet
SLX SX Elevator Maintenance Manual
7 pages

3 Data Explorer

Uploaded by

3 Data Explorer

Uploaded by

October 2013

All rights reserved.

1 Data Explorer .................................................................................................................... 7

1.2 Data Explorer Window............................................................................................................ 11

1.4 Working with Data Files/Tests ................................................................................................ 43

Data Explorer — User’s Guide

1.4.4 Further Actions ..................................................................................................................47

1.6 Adjusting the Data Environment ............................................................................................. 73

1.7 Data Source Properties .......................................................................................................... 92

Data Explorer — User’s Guide

1.7.4 Data Source Properties - Advanced ................................................................................. 98

1.8 Accessing ASAM-ODS Data ................................................................................................ 103

1.9 Special Features for Accessing Data ................................................................................... 129

Data Explorer — User’s Guide

Data Explorer — User’s Guide

1.1 Data Model

1.1.1 Data Source

The temporary data source can be converted to a permanent data source

1.1.2 Files and Tests

Data Explorer — User’s Guide

1.1.3 Base Types

1.1.4 Data Keys

Data Explorer — User’s Guide

1.1.6 Channels and Datasets

Data Explorer — User’s Guide

1.1.7 Dataset Names

1.1.8 Formula Channels

Data Explorer — User’s Guide

1.2 Data Explorer Window

1.2.1 My Computer / Network View

Data Explorer — User’s Guide

1.2.2 Data Source View

1 .... Explorer Bar

Data Explorer — User’s Guide

Data Explorer — User’s Guide

1.2.3.1 Filtering, Properties and View Operations

1.2.3.2 File Operations

Data Explorer — User’s Guide

1.2.4 Address Bar

1.2.5 Path and Conditions

Data Explorer — User’s Guide

Data key: formulas

1.2.7 Explorer Bar

Data Explorer — User’s Guide

1.2.8 Test List

1.2.9 Context Menus

1.2.9.1 My Computer / Network View

Data Explorer — User’s Guide

1.2.9.2 Data Source View

Data Explorer — User’s Guide

Files (Tests)  Open with New Alias

See also Test Series on page 46.

Data Explorer — User’s Guide

– Raw data from a split measurement

Changes should only be made by trained personnel to avoid data loss.

Data Explorer — User’s Guide

 Open Using Key

Data Explorer — User’s Guide

Data Explorer — User’s Guide

Data Explorer — User’s Guide

See also Series of Measurements on page 46.

Data Explorer — User’s Guide

Data Explorer — User’s Guide

1.2.9.3 Data Environment

1.2.10 Data Preview

1.2.10.1 Channel Properties

Data Explorer — User’s Guide

Graphic This page shows the curve(s) of currently selected channel(s).

Data Explorer — User’s Guide

Cell Operations Change value

Alternatively: Change data values using a cursor

Data Explorer — User’s Guide

5. Right-click to open the context menu:

Data Explorer — User’s Guide

Measurement Point Context Script

Data Explorer — User’s Guide

Files (Tests) Open with New Alias

Open Using Key

Horiba VETS Export File

VAX-based PUMA TRR File