Create a Testdefinition
Introduction
A test needs to be formally described by a Testdefinition. This file contains information about the data obtained, the procedures followed and sensors used.
A Testdefinitions does not contain the data itself and can be reused for more than one run of the same type of test. It is needed as a basis for the STREAM Library for reading and writing the datafile.
Description
A Testdefinition can be composed using the Deltares tool Testdefiner, see Downloads.
Phase Specific
Per phase the next types of information can be defined.
Note: It is not always clear in what phase a variable is to be defined.
All items require a unique shortname.
Number
Numerical values are to be defined as datatype Number. Items are grouped in folders.
Numbers require a quantity and a unit.
For a number a minimum and maximum value can be given.
Text
Textual or mixed values are to be defined as datatype Text. Items are grouped in folders.
System
The system folder contains predefined items.
Columns
Each datafile can contain a 2x2 datablock, containing columns, which are vertical arrays of numerical values.
Each column requires a quantity and a unit. Also a quantity number is to be given, to relate calibrations and locations to the correct column.
Sensor Location
On the tab Location the transducer location can be entered, relative to a defined coordinate system, see Coordinate Systems and Locations.
Sensor Calibration
On the tab Calibration the transducer calibration can be entered, see Calibrations.
General
Next types of information are defined phase independent:
RVU Settings (Version)
A procedure and each of the five phases need to be identified uniquely. This is done by a name with a version, expressed in a Release number, Version number and Update number.
The name of the should express the owner and the type of the definition, e.g. "Deltares.nl:PlasticityIndex". The phases are regulary named after the procedure, but with a phase specific suffix, e.g. "Deltares.nl:PlasticityIndex-S".
Each modification in a Testdefinition should lead to a change in version, depending on the nature of the change:
- Release number: Major change, impacting the whole execution of the test or phase.
- Version number: Moderate change, impacting considerable part of the execution of the test or phase.
- Update number: Small change, slightly impacting the execution of the test or phase.
If one of the phases changes, only the RVU of that phase and the Procedure have to be increased.