LMS Test.

Lab Configuration and Unit

System

User manual

16A

Copyright Siemens Industry Software NV

 Table of Contents

Chapter 1 The LMS Configuration and Unit System .................................................... 5

Section 1.1 Concept of the LMS Configurations System ....................................... 5
Section 1.1.1 Write strategy....................................................................................... 7
Section 1.1.2 Read strategy ....................................................................................... 7
Section 1.2 Concept of the LMS Unit System ........................................................ 8
Section 1.2.1 Unit ...................................................................................................... 8
Section 1.2.2 Label Unit ............................................................................................ 9
Section 1.2.3 Base Quantity....................................................................................... 9
Section 1.2.4 Quantity ............................................................................................... 9
Section 1.2.5 Quantity Case ....................................................................................... 9
Section 1.2.6 Unit Case ........................................................................................... 10
Section 1.2.7 Unit system ........................................................................................ 10
Section 1.3 Editing LMS Units ............................................................................. 10
Section 1.3.1 Versioning of LMS Unit System ....................................................... 10
Section 1.3.2 Main panel logic ................................................................................ 11
Section 1.3.3 Menu bar ............................................................................................ 12
Section 1.3.4 Unit Cases panel ................................................................................ 16
Section 1.3.5 Unit Rules panel................................................................................. 22

16A 3
 Chapter 1 The LMS Configuration and Unit System

Chapter 1 The LMS Configuration and Unit System

In This Chapter
Concept of the LMS Configurations System......................5
Concept of the LMS Unit System ......................................8
Editing LMS Units .............................................................10

Section 1.1 Concept of the LMS Configurations System

In the LMS Configuration System, different files and settings that are relevant
for the LMS TEST applications, will be managed automatically by the software.
The system consists of 3 management levels :

16A 5
 Chapter 1 The LMS Configuration and Unit System

 Central or Factory level : this level will always be available and it contains
the LMS Factory files and settings. This level will be installed through the
install procedure and its content should never be updated manually.
 Group level (which is optional): this level can be enabled (optional) by the
user or administrator and it contains the configuration files and settings that
you want to share within a certain team.
 User level: this level will always be available and it contains all individual
configuration files and settings of a specific user.
For every level, a specific location (folder) needs to be defined. During
installation of the "LMS Configuration and Units Editor" tool, the administrator
has the possibility to define these locations for all users on that system.
You can change these locations for yourself with the command
"File->Configuration …". You will get the following dialog where you can
change it.

The typical configuration files which are managed by this system are :
 The Active Units system: ActiveUnitSystem.xml
 Tools->Options …. Settings: Configuration\Loader.cfg
 Column visibility of Time data selection:
Configuration\DynamicAttributes.txt
 Column visibility of Block processing:
Configuration\DataBlockProcessingVisibilityMap
 User attribute visibility: Configuration\UserAttributes.txt
 User attribute List types: Configuration\ListAttributes.txt
 Favorite Displays: Layout\SelectedLayoutFiles.txt
 Template for Documentation: Attachment Templates\MemoInventory.txt
The typical file types which are managed by this system are :

6 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

 Units files: *.lu5

 Project templates: Project Templates\*.tpl
 Time Data Selection Datasets: Dataset\*.tds
 Different Calculator Formulasets: FormulaSet\*.*FS
 Time Data Processing Processingsets: ProcessingSet\*.TPS
 Display layouts: Layout\*.lay
 Print formats: PrintFormats\*.doc(x)
 Column visibility files: GridFilters\*.txt
 Templates for Documentation: Attachment Templates\*.doc (html)

Section 1.1.1 Write strategy

When you are running one of the LMS Test applications (LMS Configuration
and Unit System tool, Test.lab), these applications will always write the
configuration files and settings on the User level.

Section 1.1.2 Read strategy

When you are running one of the LMS applications and when it needs a specific
setting (or file that contains that setting), then the following strategy will be
handled by default (File access priority = Local) :
Step 1
First the system will look on Local level. If it is found, it will be used.
Step 2
If it is not found, then the system will look on Group level. If it is found, it will
be used.
Step 3
If it is not found, then the system will use the Factory value which is always
available on central level.

Note: If File access priority = Group, then the system will first look on Group
and then on Local level.

When you are running one of the LMS applications and when you need a list of
available configuration files of a specific file type, then the following strategy
will be handled by default (File access priority = Local) :
Step 1
First the system will look which files are available on Local level. These are
always added to the list.
Step 2

16A 7
 Chapter 1 The LMS Configuration and Unit System

Then the system will look on Group level. These are added to the list, except
when a version of this file was already available on Local.
Step 3
Then the system will look on Central level. These are added to the list, except
when a version of this file is already available.

Note: If File access priority = Group, then the system will first look on Group
and then on Local level.

Section 1.2 Concept of the LMS Unit System

In the LMS Unit System, quantities are determined by their base quantity terms:
length, mass, time, angle, current, temperature, light, and mol. For the same
quantity multiple quantity cases can exist. One of these quantity cases is the
default quantity case, the others are defined by a number of unit rules. Each
quantity case maps with a set of unit cases. One of these unit cases is the default
unit case, the others are visible or invisible. A unit system (lu5) file contains all
the quantity cases, the unit rules, the lists of unit cases and their unit case status.

Section 1.2.1 Unit

Unit label:
 Linear conversion: scale factor, offset
User(si) = si * <scale factor> + <offset>
 Level conversion: log reference, log scale factor, log base, level string, flag
for power or linear unit.
Examples:
 Sound pressure’: unit label: “Pa”
scale factor: 1, offset: 0 Pa
log reference: 2e-5 Pa, log base: 10, log scale factor: 20, level string “dB
(2e-5)”, power: no
 ‘Temperature’: unit label: “deg C”
scale factor: 1, offset: -273.15 degC (0 K = -273.15 degC),
log reference: 1 degC, log base: 10, level scale factor: 20, level string “dB”,
power: no

8 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

Section 1.2.2 Label Unit

Same as unit, except no info about linear conversion (level conversion is

defined). Label units are weak units in the sense that they disappear when they
are used in computations together with other units. They are only meant for
associating user defined units with very specific semantics with the data.

Example:
 Label Unit Loudness
Unit label: "sones", Level label: "phones", Log reference: 0.0625, Log base:
2, Level scale factor: 10, Power: yes

Section 1.2.3 Base Quantity

 Base quantities: length, mass, time, angle, electric current, thermodynamic

temperature, luminous intensity, amount of substance
 See http://physics.nist.gov/cuu/Units/units.html
The reason to consider angle a base quantity is historical.

Section 1.2.4 Quantity

 Unique combination of Base Quantities:

rational powers for length, mass, time, angle, current, temperature, light, mol

can be all zero (for instance ratio)

 Multiple Quantity cases can exist for one Quantity (see later)
Example:
 Quantity acceleration: base quantity length = 1, base quantity time = -2

Section 1.2.5 Quantity Case

 Belongs to one Quantity: unique combination of rational powers for Base

Quantities
 A Quantity Case has a specific name.
 A Quantity Case is the default for the Quantity involved or can be defined
by a number of Unit Rules
Examples:

16A 9
 Chapter 1 The LMS Configuration and Unit System

 Quantity case Velocity: base quantiies: length=1, time -1, default

 Quantity case Speed: base quantities: length=1, time=-1, rules:
Distance*Time–1, Distance*Frequency

Section 1.2.6 Unit Case

 A Quantity Case has a related list (1 or more) of Units. We call this list of
Units belonging to the same Quantity Case the Unit Cases of this Quantity
Case.
 There is one and only one default unit case for each quantity case.
 Unit Case can be set to be visible or invisible. The default unit case has to
be visible.
 The unit labels of all Unit Cases belonging to one Quantity Case have to be
unique.
Example:
 Unit cases km and hm for quantity case Distance

Section 1.2.7 Unit system

 A unit system contains all the quantity cases, the unit rules, the lists of unit
cases and their unit case status.
 A unit system is not saved in the project database of the application, but in a
separate (lu5) file with a specific format. This unique unit system file is
accessible by each LMS Test application.
 The predefined unit system files: SI, Technical, English, ISO 1683-1983

Section 1.3 Editing LMS Units

The stand-alone LMS Configuration and Unit System tool can be used to create
and modify unit system (lu4 and lu5) files. The LMS Configuration and Unit
System tool is also used to select the active unit system file. This active unit
system is notified when the LMS Test application like Test.Lab is started. When
changing this active unit system the LMS Test application needs to be re-started
in order to be aware of this change.

Section 1.3.1 Versioning of LMS Unit System

LMS Unit System version 1.0.0 includes Factory unit system files of type ‘lu4’.

10 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

LMS Unit System version 2.0.0 includes new Factory unit system files of type
‘lu5’ and an upgrade of the LMS Configuration and Unit System tool. In these
new Factory unit system files, the name of the existing ‘MicroStrain’ quantity
cases into ‘Strain’ quantity cases has been changed. The new Factory unit
system files also contain extra quantity cases, extra unit cases, and a number of
improved unit parameters.

LMS Unit System version 2.1.0 includes extended Factory unit system files of
type ‘lu5’ and a minor upgrade of the LMS Configuration and Unit System tool.

LMS Unit System version 2.2.0 includes extended Factory unit system files of
type ‘lu5’.

Section 1.3.2 Main panel logic

The main panel consists:

 A single menu bar
 Two tabs, one for the units and one for the unit rules
 Checkboxes to manage the visibility in the Units tab
 Four action buttons in case of Units tab:
 Add Unit…
 Add Label…
 Edit…
 Delete…
 Two action buttons in case of Unit rules tab:
 Add…
 Delete…
The general concept is that all information in the tabs is read-only and that the
unit- or rule information can only be edited from a pop-up panel.

16A 11
 Chapter 1 The LMS Configuration and Unit System

Section 1.3.3 Menu bar

Section 1.3.3.1 File =>Configuration

You will get the following dialog which is used to change the user configuration
folder, the group configuration folder and the settings of the group
configuration.

Note: Please refer to the section about the concept of the LMS configuration.

Section 1.3.3.2 File => Select active unit system

This is menu is used the select the active unit system and open it in the LMS
Configuration and Unit System tool.

On File => Select active unit system…, a list is shown with all available unit
system files. Unit system files only appear once in the list and on selection, the
priority Local=>Group=>central is followed. An example of this logic is given
below:

12 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

Unit system file Location Unit system file Visibility status

Name

central Technical.lu5 Not visible, overruled by Group

Configuration

English.lu5 Visible

SI.lu5 Visible

ISO_1683_1983.lu5 Visible

GroupConfiguration Technical.lu5 Not visible, overruled by

UserConfiguration\user1

Company.lu5 Visible

UserConfiguration\user1 Ultimate.lu5 Visible

Technical.lu5 Visible

The above situation for user ‘user1’ will result in a list with the following four
items listed in alphabetic order:

Company.lu5 (GroupConfiguration)

English.lu5 (central)

SI.lu5 (central)

ISO_1683_1983.lu5 (central)

Technical.lu5 (UserConfiguration)

Ultimate.lu5 (UserConfiguration)

One of these six unit system files can be made active.

Section 1.3.3.3 File => Upgrade unit system

Section 1.3.3.3.1 Major upgrade

The latest versions of the LMS Configuration and Unit System tool can only
open ‘*.lu5’ unit system files."

Old unit system files of type ‘lu4’ can be imported and upgraded into type ‘lu5’
starting from a chosen unit system on the Central folder (Technical, SI, English,
or ISO 168301983):

16A 13
 Chapter 1 The LMS Configuration and Unit System

 The ‘MicroStrain’ quantity cases will be transformed into the ‘Strain’

quantity cases.
 Missing quantity cases with all their unit cases will be added.
 Missing unit rules will be added.
 Optionally (option 1, by default on), the unit parameters can be updated.
 Optionally (option 2, by default off), the missing unit cases of existing
quantity cases can be added.
After upgrade the modified unit system will be saved on the UserConfiguration
folder and it will be made active. Also a logging will be listed about:
 Added quantity cases
 Added unit cases
 Added unit rules
 Modifies unit cases (happens when option 1 is on)
 Ignored unit cases, being new unit cases of existing quantity cases which
have not been added (happens in case option 2 is off).

Section 1.3.3.3.2 Minor upgrade

In a similar way a minor upgrade of the unit system files can be performed
when needed. For instance 2.0.0 lu5 unit system files can be upgraded to 2.1.0
or 2.2.0 lu5 unit system files.

Section 1.3.3.4 File => Import dynamic units

The unit system files containing the newly created dynamic units are loaded
from the UserConfiguration folder (dynamic rules are not loaded). All dynamic
quantity cases and unit cases are added (read inserted) to the lists of units.

Dynamic quantity cases and dynamic unit cases can be recognized by the unit
case status ‘Dynamic’. The user can change this status into ‘Default’, ‘Case
default’, Visible, or ‘Invisible’ to make this case static. Only the static units will
be saved afterwards (see later).

Section 1.3.3.5 File => Save

When saving the current status, all units and rules will be saved with the same
filename as the one that was opened, but always on the UserConfiguration
folder. This implies that a file loaded from the Central or Group folder will be
saved with the same name on the UserConfiguration folder.

When dynamic quantity cases and/or unit cases have been imported, they will
not be saved unless they have been made static by the user (by changing the
Unit Case Status field).

Section 1.3.3.6 File => Save as…

When saving the current status, all units and rules will be saved with a filename
that needs to be specified by the user. For that purpose a flat list of all unit

14 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

system files is shown including an input field containing the name of the unit
system file that was opened originally. The unit system file is saved on the
UserConfiguration folder.

Section 1.3.3.7 File => Exit

When closing the application, a message box pops up to ask if the user wants to
keep the changes (only if changes have been made).

Section 1.3.3.8 Edit => Find

On Find, a panel pops up with an input field ‘Find what:’. For units, the user
defined string will be searched for in the Quantity Case Name and the Unit Case
Name. For rules, all Quantity Case Names will be part of the search.

With Find Next, the next row will be highlighted containing a hit. This row will
be in the center of the visible list or higher when the list is too short.

The direction can be specified ‘Down’ or ‘Up’.

Search conditions which can be specified:

 Match case
 Match whole word
 Wrap searches
Continue searching from the beginning list, after reaching its end, when
searching down, or the end after reaching the beginning, when searching up.

Section 1.3.3.9 Edit => Add unit…

This action maps on the Add Unit button in case of Unit panel. You may check
on it later.

Section 1.3.3.10 Edit => Add label…

This action maps on the Add Label button in case of Unit panel. You may check
on it later.

Section 1.3.3.11 Edit => Add rule…

This action maps on the Add Rule button in case of Unit rule panel. You may
check on it later.

Section 1.3.3.12 Edit => Edit…

This action maps on the Edit button. You may check on it later.

Section 1.3.3.13 Edit => Delete…

This action maps on the Delete button and deletes the selected rows after

16A 15
 Chapter 1 The LMS Configuration and Unit System

confirmation.

Section 1.3.3.14 View => Toolbar

The toolbar can be shown or not.

Section 1.3.3.15 View => Show

The items in this View => Show Menu map on the checkboxes of the Units tab.
The ‘Checked/Not Checked’ status of the checkboxes is reflected in the menu
bar pull down.

Section 1.3.3.16 View => Sort

The items in this View => Sort menu map on the radio buttons of the Units tab.
The ‘Checked/Not Checked’ status of these radio buttons is reflected in the
menu bar pull down: According to base quantities / According to name.

Section 1.3.3.17 Help => LMS Configuration and Unit System Help
Launches the help of the LMS Configuration and Unit System tool application.

Section 1.3.3.18 Help => About LMS Configuration and Unit System
tool
Shows the ‘About’ of the LMS Configuration and Unit System tools
application.

Section 1.3.4 Unit Cases panel

Section 1.3.4.1 Sorting of the Unit Cases

The unit cases can be sorted in two different ways depending on the chosen
sorting option set in the menu or set by radio buttons below the panel:
 Sorting according to base quantities
 Sorting according to name

Section 1.3.4.1.1 Sorting according to base quantities

In this case, the sorting is using the following priorities:
Step 1
First the regular unit cases, then the label units. The regular unit cases are sorted
according to:
Step 2
Base quantities: from lowest fractional power to highest

16 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

 Length
 Mass
 Time
 Angle
 Temperature
 Electric current
 Luminous intensity
 Mole
Step 3
Quantity Case Name (*): first default quantity case, then the static ones in
alphabetic order; case sensitive, then the dynamic ones in alphabetic order; case
sensitive.

Note: A set of compatible quantity cases belong to the same quantity when they
all have the same base quantity terms (Length, Mass, Time, Angle,
Temperature, Electric current, Luminous intensity, and Mole). One quantity
case of such a set is the Default quantity case. The corresponding default unit
has status ‘Default’ (standing for general default unit). The corresponding
default units of the other (not-default) quantity cases have status ‘Case default’
(standing for case specific default unit).

Step 4
Unit Case Status (**) in sequence:
 Default
 Case default
 Visible
 Invisible
 Dynamic

Notes: A Label Unit can only have Label Status Visible or Dynamic. The
Dynamic option for the Unit Case Status is only available in case of an
imported unit case. (The option is Dynamic after importing the unit case and
can be changed by the user into another option.)

Step 5
Unit Case Name: alphabetic order; case sensitive
1.3.4.1.1.1 Presentation of unit cases per Quantity
The sorting algorithm makes sure that all unit cases of the same quantity are
next to each other. These groups of unit cases belonging to the same quantity
are displayed with alternating background colors: white and light grey.

The font colours are also optimized: red for all dynamic info and green for all
dynamic info which has been changed into static (Default, Case default, Visible,
or Invisible) by the user.

16A 17
 Chapter 1 The LMS Configuration and Unit System

Section 1.3.4.1.2 Sorting according to name

In this case, the sorting is using the following priorities:
Step 1
First the regular unit cases, then the label units. The regular unit cases are sorted
according to:
Step 2
Quantity Case Name: alphabetic order; case sensitive
Step 3
Unit Case Status (*) in sequence:
 Default
 Case default
 Visible
 Invisible
 Dynamic

Note: A set of compatible quantity cases belong to the same quantity when they
all have the same base quantity terms (Length, Mass, Time, Angle,
Temperature, Electric current, Luminous intensity, and Mole). One quantity
case of such a set is the Default quantity case. The corresponding default unit
has status ‘Default’ (standing for general default unit). The corresponding
default units of the other (not-default) quantity cases have status ‘Case default’
(standing for case specific default unit). The default quantity case is the quantity
case for which the default unit case is the quantity default, called ‘Default’ and
not only the default unit case for the quantity case, called the ‘Case default’.

A Label Unit can only have Label Status Visible or Dynamic.

The Dynamic option for the Unit Case Status is only available in case of an
imported unit case. (The option is Dynamic after importing the unit case and
can be changed by the user into another option.)

Step 4
Unit Case Name: alphabetic order; case sensitive
1.3.4.1.2.1 Presentation of unit cases per quantity case
The sorting algorithm makes sure that all unit cases of the same quantity case
are next to each other. These groups of unit cases belonging to the same
quantity case are displayed with alternating background colors: white and light
grey.

The font colours are also optimized: red for all dynamic info and green for all
dynamic info which has been changed into static (Default, Case default, Visible,
or Invisible) by the user.

18 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

Section 1.3.4.2 Format of the Level String

The level conversions include the acoustic weighting applied on the data. The
LMS unit system allows managing this aspect globally. For this purpose the
characters ‘<’, ‘W’, and ‘>’ are used. Whatever is between < and > will be
shown when the weighting is not Linear. When the weighting is Linear nothing
is shown. The common example for [Pa] to [dB] is given below:

Level String Linear data A-weighted data

dB dB dB

dB<(W)> dB dB(A)

dB<[W]> dB dB[A]

dB<(W)> re 20e-6 dB re 20e-6 dB(A) re 20e-6

Section 1.3.4.3 Edit…/Add...Unit Cases panel

When editing a unit, all information is loaded in the Edit Unit panel. The user
can edit all fields and Apply consistency is checked on.

When adding a unit, the values of the active selection are taken over in case a
unit is selected (and not a label). If no such selection is made, all values are put
to the defaults.

The formats of the parameters in the panel are:

16A 19
 Chapter 1 The LMS Configuration and Unit System

Panel Parameters Input format and values Default values

Quantity Case Name String – Should not be empty ‘<to be defined>’

Fractional Powers Integer values –positive or All set to 1

negative, non-zero for the
denominator

Unit Case Name String – Should not be empty ‘<to be defined>’

Unit Case Status Combo-box – either Default, Default

Case default, Visible, Invisible,
or Dynamic
Only one Unit Case can be the
Default.

Scale Factor Strict positive double 1.0

Scale Offset Double 0.0

Level Label String – ‘<W>’ is used to dB<(W)>

manage the acoustic weighting

Reference for Level 0 Strict positive double 1.0

Linear or Power Combo-box – either Linear or Linear

Power

Logarithmic Base Strict positive double – in 10.0

practice limited to 10 or 2.

Logarithmic Scale Factor Strict positive double – in 20.0

practice limited to 10 or20.

Table: Panel Parameters for Edit Units panel

The consistency check will be the verification of the uniqueness of the quantity
case name and the unit case name for the given quantity case and the validation
of the input parameters according the table above.

Section 1.3.4.4 Edit…/Add... Labels panel

When editing a label, all information is loaded in the Edit Label panel. The user
can edit all fields and Apply consistency is checked on.

When adding a label, the values of the active selection are taken over in case a
label is selected (and not a unit). If no such selection is made, all values are put
to the defaults.

The formats of the parameters in the panel are:

20 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

Panel Parameters Input format and values Default values

Quantity Case Name String – Should not be empty ‘<to be defined>’

Label Name String – Should not be empty ‘<to be defined>’

Label Status Combo-box – either Default or Default

Dynamic

Level String String – ‘<W>’ is used to dB<(W)>

manage the acoustic weighting

Reference for Level 0 Strict positive double 1.0

Linear or Power Combo-box – either Linear or Linear

Power

Logarithmic Base Strict positive double – in 10.0

practice limited to 10 or 2.

Logarithmic Scale Factor Strict positive double – in 20.0

practice limited to 10 or20.

Table: Panel Parameters for Edit Labels panel

The consistency check will be the verification of the uniqueness of the quantity
case name and the label name and the validation of the input parameters
according the table above.

Section 1.3.4.5 Visibility Checkboxes of the Unit Cases tab

The Show options can be set in the menu or set by check boxes below the panel:

Section 1.3.4.5.1 Columns selection

 Show Base Quantity Powers: 8 columns with the base quantity powers will
be inserted after the visibility column. These columns will contain the
fractional powers as ratios, e.g.:’2/3’.
 Show Linear Conversion Parameters: inserts the linear conversion
parameters after the base quantity columns (if selected to be visible in the
list).
 Show Level Conversion Parameters: inserts the level conversion parameters
after the linear conversion parameters (if available) or after the base
quantity columns (if selected to be visible in the list).

Section 1.3.4.5.2 Rows selection

 Show All Visible Unit Cases: All Default and Visible items of the unit
system are displayed.
 Show All Unit Cases: All items of the unit system are displayed.
 Show Dynamic Unit Cases Only: Only the imported items, recognized by

16A 21
 Chapter 1 The LMS Configuration and Unit System

the ‘Dynamic’ Status type will be shown.

Section 1.3.5 Unit Rules panel

Section 1.3.5.1 Sorting of the Unit Rules

The Unit Rules are sorted in a fixed way. The user has no impact on it. The
sorting is using the following priorities:
 Resulting Quantity Case: alphabetic order; case sensitive
 Quantity Case 1: alphabetic order; case sensitive
 Fractional Power 1: from lowest fractional power to highest
 Quantity Case 2: alphabetic order; case sensitive
 Fractional Power 2: from lowest fractional power to highest

Section 1.3.5.2 Presentation of unit rules per resulting quantity case

The sorting algorithm ensures that all unit rules of the same resulting quantity
case are next to each other. These groups of unit rules belonging to the same
resulting quantity case are displayed with alternating background colors: white
and light grey.

Section 1.3.5.3 Edit…/Add... Unit Rules panel

When editing a rule, all information is loaded in the Edit Rule panel. The user
can edit all fields and on Apply consistency is checked.

When adding a Rule, the values of the active selection are taken over. If no
selection is made, all values are put to the defaults.

The formats of the parameters in the panel are:

Panel Parameters Input format and values Default values

Quantity Case Names Combo-box showing a saved Ratio

Quantity Case

Fractional Powers Integer values – positive or Both set to 1

negative

Table: Panel Parameters for Edit Rules panel

The list of resulting quantity cases is adapted in the combo-box depending on

the above selected quantity cases, operations or powers. All quantity case names
are listed in alphabetic order.

The calculation of this list of resulting quantity cases depends on the base
quantities obtained from the proposed unit calculation. All quantity cases that

22 User manual LMS Test.Lab Configuration and Unit System

 Chapter 1 The LMS Configuration and Unit System

have the matching base quantities will appear in the list.

Only multiplication is supported as operation between units. When the second

fractional power is negative, then the operation will become the division. An
example could be speed (length / time): the unit rule will be: ‘length * time-1’.

The consistency check will be limited to the verification of the uniqueness of

the rule.

16A 23
 Presentation of unit cases per quantity case •
Index 18
Presentation of unit rules per resulting quantity
B case • 21

Base Quantity • 9 Q

C Quantity • 9
Quantity Case • 10
Columns selection • 21
Concept of the LMS Configurations System • R
5 Read strategy • 7
Concept of the LMS Unit System • 8 Rows selection • 21
E S
Edit => Add label… • 15 Sorting according to base quantities • 17
Edit => Add rule… • 15 Sorting according to name • 18
Edit => Add unit… • 15 Sorting of the Unit Cases • 16
Edit => Delete… • 16 Sorting of the Unit Rules • 21
Edit => Edit… • 16
Edit => Find • 15 T
Edit…/Add... Labels panel • 20 The LMS Configuration and Unit System • 5
Edit…/Add... Unit Rules panel • 22
Edit…/Add...Unit Cases panel • 19 U
Editing LMS Units • 10 Unit • 8
F Unit Case • 10
Unit Cases panel • 16
File => Exit • 15 Unit Rules panel • 21
File => Import dynamic units • 14 Unit system • 10
File => Save • 14
File => Save as… • 15 V
File => Select active unit system • 12 Versioning of LMS Unit System • 11
File => Upgrade unit system • 13 View => Show • 16
File =>Configuration • 12 View => Sort • 16
Format of the Level String • 19 View => Toolbar • 16
H Visibility Checkboxes of the Unit Cases tab •
21
Help => About LMS Configuration and Unit
System tool • 16 W
Help => LMS Configuration and Unit System Write strategy • 7
Help • 16
L
Label Unit • 9
M
Main panel logic • 11
Major upgrade • 13
Menu bar • 12
Minor upgrade • 14
P
Presentation of unit cases per Quantity • 17

16A 25