Page History

...

A coordinate system can have one predecessor coordinate system, what can be seen as its parent system.
A coordinate system with predecessor 'none' is being seen as the root system, which usually is an inert system.
The rotation axis doesn't have to be normalized.
To transform from the predecessor system to the successor system, both the translation and the rotation are expressed in the predecessors system.
The right-hand rule is applied for defining the rotation angle.
For coordinate systems a shortname starting with 'coo_' is created. The first system has number 1500, successor systems have decreasing numbers down to 1451. Upon this, 50 coordinate systems are allowed.
The next fields are stored in this shortname, separated by a semicolon (';'):
- name of predecessor coordinate system
- x-translation with respect to predecessor system
- y-translation with respect to predecessor system
- z-translation with respect to predecessor system
- x-rotation with respect to predecessor system
- y-rotation with respect to predecessor system
- z-rotation with respect to predecessor system
- rotation angle with respect to predecessor system

The next functions are dealing with coordinate systems:

Function	Description
streamRead	Read coordinate systems from the Testdefinition when reading a file
streamPutCoordSystems	(Re)define the relations between coordinate systems TBD

Locations

...

A location is coupled one by one to a column. Therefore it can be defined on the Locations tab of a column, when indicated as sensor.
Notes:

The next functions are dealing with coordinate systems:

Function	Description
streamRead	Read sensor locations from the Testdefinition when reading a file
streamPutLocations	(Re)define the location of the sensors relative to coordinate systems
streamCoordTransform	Transform coordinates of locations between coordinate systems

TBD

...