glue:processconfiguration
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungNächste ÜberarbeitungBeide Seiten der Revision | ||
glue:processconfiguration [2017/02/16 13:45] – [Process Config XML: Groups of trials] oliver | glue:processconfiguration [2021/07/05 13:04] – [Output:] oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
======Process Configuration====== | ======Process Configuration====== | ||
- | This component arranges the processing of multiple measurement trials by the **Math Engine** based on a model description. Typically | + | =====General features===== |
+ | This component arranges the processing of multiple measurement trials by the [[modellingcomponents: | ||
E.g. there is a 001.c3d file, which includes timeseries of marker positions of a 3d motion analysis system, a 001.mpg file with a synchronous measured video, 001.enf (Vicon file type) with meta data and so on. The file types are free configurable. | E.g. there is a 001.c3d file, which includes timeseries of marker positions of a 3d motion analysis system, a 001.mpg file with a synchronous measured video, 001.enf (Vicon file type) with meta data and so on. The file types are free configurable. | ||
Zeile 67: | Zeile 68: | ||
The < | The < | ||
- | Attributes of the < | + | Attributes of the **< |
- | ^ name ^ Default ^ Description | + | ^ name ^ Default ^ Description |
- | ^ name | Name of this group | | | + | ^ name | Name of this group | |
+ | ^ sheet | | A Sheet definition which is used to plot sheets of time series of data assigned to this group. | ||
^ view | | A View 4d defintion which is used to visualize time series of data assigned to this group. | | ^ view | | A View 4d defintion which is used to visualize time series of data assigned to this group. | | ||
^ normaldatagroup | | If normaldata based on an other CalcGroup should be used. If this attribute is not set, it is assumed that the group on his self is the normdata group. | | ^ normaldatagroup | | If normaldata based on an other CalcGroup should be used. If this attribute is not set, it is assumed that the group on his self is the normdata group. | | ||
^ normaldata | (not implemented yet) | Explicit name of a normal data file if the default is not sufficient. | | ^ normaldata | (not implemented yet) | Explicit name of a normal data file if the default is not sufficient. | | ||
- | ^ calibrationstep | -1 | (not implemented yet) Used, if this group is used for calibration. -1 if it is not used. Small numbers, starting with 0, the numbers must be different for different groups. If there is no group with calibrationstep != -1, then single trials can be processes. | + | ^ calibrationstep | -1 | (not implemented yet) Used if this group is used for calibration. -1 if it is not used. Small numbers, starting with 0, the numbers must be different for different groups. If there is no group with calibrationstep != -1, then single trials can be processes. The defined order cauld be used instead of the implicit order in the < |
- | The defined order cauld be used instead of the implicit order in the < | + | |
- | calibrationsequence zusätzlich einführen | | + | |
- | To define which trials are assigned to a group the element < | + | |
- | Identification of trials: | + | To define which trials are assigned to a group the element < |
- | The < | + | |
+ | ====Identification of trials:==== | ||
+ | The < | ||
The keys and the values are case sensitive. Have a look at the following example: | The keys and the values are case sensitive. Have a look at the following example: | ||
Zeile 86: | Zeile 88: | ||
<code xml> | <code xml> | ||
< | < | ||
- | <entry key=" | + | <entry key=" |
- | | + | |
</ | </ | ||
</ | </ | ||
Zeile 94: | Zeile 96: | ||
A trial is assigned to the group of trials, if the conditions defined by all < | A trial is assigned to the group of trials, if the conditions defined by all < | ||
- | Process Configurations: | + | ====Process Configurations: |
The < | The < | ||
Zeile 104: | Zeile 106: | ||
</ | </ | ||
- | Input: | + | With the key=" |
- | Output: | + | |
- | Attributes of the < | + | <code xml> |
+ | < | ||
+ | </ | ||
+ | |||
+ | ^ Name ^ Values ^ Description | | ||
+ | ^ EVENTS | true or false | If set to false, no events are read. | | ||
+ | ^ POINTS | true of false | If set to false, no position data is read. | | ||
+ | ^ FORCES | true of false | If set to false, not force plat data is read. | | ||
+ | ^ inputpath | path to the data set e.g. inside a r3d-file | If set to a path, than this is used to find the input dataset. if the attribute is not used per default the dataCollections are searched in the " | ||
+ | ^ outputpath | path to the data set e.g. inside a d3d-file | If set to a path, than this path is created to store the dataset. (This functionality is not yet implemented completely in the MotionDataStorageHandler class.) | | ||
+ | |||
+ | |||
+ | ====Input: | ||
+ | |||
+ | Attributes of the **< | ||
+ | ^ Attribute ^ Default ^ Description ^ Required | | ||
+ | ^ labelset | Labelset as defined with the attribute " | ||
+ | |||
+ | ====Output: | ||
+ | |||
+ | Attributes of the **< | ||
^ Attribute ^ Default ^ Description ^ Required | | ^ Attribute ^ Default ^ Description ^ Required | | ||
- | ^ labelset | The labelset which defines which parts of the data should be written to the output and also meta data e.g. the mime type and the file suffix. | Yes | | + | ^ labelset |
- | ^ mimetype | (deprectated) | Mimetype to define the output file format. This is set normally inside the labelset file. | No | | + | ^ mimetype | (deprecated) | Mimetype to define the output file format. This is set normally inside the labelset file. | No | |
- | ^ filesuffix | | suffix of the outputfile normally this is defined inside the labelset (deprecated) | No | | + | ^ filesuffix | | suffix of the outputfile normally this is defined inside the labelset (deprecated) | No | |
^ dir | | dir of the input session of trials Absolute path of the directory, where the outfile should be written. | No | | ^ dir | | dir of the input session of trials Absolute path of the directory, where the outfile should be written. | No | | ||
^ name | | Can be used to define the name of the output file. (currently not used) | No | | ^ name | | Can be used to define the name of the output file. (currently not used) | No | | ||
Zeile 117: | Zeile 138: | ||
^ handlerclass | | Use a customer defined output handler class. (changes are needed to be able to use more than one handler class) | No | | ^ handlerclass | | Use a customer defined output handler class. (changes are needed to be able to use more than one handler class) | No | | ||
- | If the < | + | If the **< |
| | ||
- | The < | + | The **< |
- | These Properties can be used from the output handler. But this feature is currently not used. | ||
+ | ===MotionDataOutputHandler=== | ||
+ | To write output to a file a so called " | ||
+ | |||
+ | The following properties are read as < | ||
+ | |||
+ | ^ Attribute ^ Default ^ Description | | ||
+ | ^ fileName | <session id>.d3d | Output file name inclusive suffix, e.g. " | ||
+ | ^ overwrite | false | If set to " | ||
+ | ^ outputDir | The session folder currently processed. | Absolute path to the folder, where to save the output. | | ||
+ | ^ trialsGroupName | " | ||
+ | ^ renameExistingTimeSeries | false | If set to true, existing data timeseries are renamed instead overwritten with the current ones. | | ||
+ | ^ seperateGroupFiles | false | If set to true for every calcgroup a seperate output file is written. The name of the corresponding output files has the format <session id>#< | ||
+ | |||
+ | If no properties at all are defined a warning is written. | ||
+ | |||
+ | ===TXTTableOutputHandler=== | ||
+ | |||
+ | ^ Attribute ^ Default ^ Description | | ||
+ | ^ header | | | | ||
+ | ^ filename | | | | ||
=====Process Config XML: Model Switches===== | =====Process Config XML: Model Switches===== | ||
+ | With a switch, the calculation of a modelling element can be switched of or on. One ore more switches can be defined. In the model elements, with the attribute " | ||
+ | |||
+ | A on-switch is created only, if all defined keys are available in the trial and if the values of all keys matches the regular expression as defined as content of the < | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | <switch name=" | ||
+ | <entry key=" | ||
+ | </ | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | In the above example the switch " | ||
+ | |||
+ | The content of the < | ||
+ | |||
=====Process Config XML: Model Parameters===== | =====Process Config XML: Model Parameters===== | ||
=====Process Config XML: Normal Data Definition===== | =====Process Config XML: Normal Data Definition===== | ||
- | =====Example XML Process | + | =====Process |
<code xml> | <code xml> | ||
Zeile 234: | Zeile 290: | ||
</ | </ | ||
</ | </ | ||
+ | |||
+ | =====Labelsets===== | ||
+ | LabelSets are defined in the folder " | ||
+ | |||
+ | ====General structure==== | ||
+ | The structure of a labelset file looks like follow: | ||
+ | |||
+ | <code xml> | ||
+ | <?xml version=" | ||
+ | < | ||
+ | | ||
+ | <Labels name=" | ||
+ | |||
+ | <Filter name=" | ||
+ | | ||
+ | <!-- Objects --> | ||
+ | |||
+ | <Label name=" | ||
+ | <Label name=" | ||
+ | ... | ||
+ | </ | ||
+ | | ||
+ | <!-- Mapping of label names after reading or before writing to a file --> | ||
+ | < | ||
+ | <Label from=" | ||
+ | </ | ||
+ | ... | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | ====File formats==== | ||
+ | A labelset can be used to define the input or output file format. To do this to the element < | ||
+ | |||
+ | <code xml> | ||
+ | <?xml version=" | ||
+ | < | ||
+ | <Labels mimeType=" | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | The following file formats are available: | ||
+ | |||
+ | ^ Mime Type ^ Description | ||
+ | ^ application/ | ||
+ | ^ text/ | ||
+ | ^ text/x-json | json | | ||
+ | ^ text/ | ||
+ | ====Timeseries properties==== | ||
+ | Properties of the timeseries can defined by attributes of the < | ||
+ | |||
+ | |||
+ | ^ Attribute name ^ Description | ||
+ | ^ name | Name the label | no | | ||
+ | ^ mathType | The math type of the referenced data. Default is Vector3d | yes | | ||
+ | ^ differentiations | The number of differentations to be calculated. For each differentiation a prefix " | ||
+ | |||
+ | The following math types are available: | ||
+ | |||
+ | ^ Math type name ^ Description | ||
+ | ^ REAL | double timeserie | | ||
+ | ^ COLUMN_VECTOR_3D | timeserie of Vector3d objects | | ||
+ | ^ MATRIX_3X3D | timeserie of Matrix3d objects | | ||
+ | ^ QUATERNION_D | timeserie of quaternion objects | | ||
+ | ^ STRING | | | ||
+ | ^ CELL_STRING | | | ||
+ | ^ COMPLEX | | | ||
+ | ^ INTEGER | | | ||
+ | ^ UNKNOWN | | | ||
+ | ^ TYPELESS | | | ||
+ | ====Filtering==== | ||
+ | The labelset can be used to define a filter chain. Currently this filter chain is used only during loading of trial in the MultiTrialFileWrapper (module EasyCalc) and MultiTrialFileProvider (module MultiTrialFile API). | ||
+ | |||
+ | - First of all, the filters defind as children-elements of the data labels are executed in its definition sequence. | ||
+ | - Second the filters, which are defind as children of a < | ||
+ | - and last the filters, which are defined as children of the < | ||
+ | |||
+ | Independend from the filter chain, calculation of differentiation defined by the " | ||
+ | |||
+ | ====Mapping timeseries names==== | ||
+ | If timeseries are read from files to be processed or written to files after processing, their names can be mapped to an other name based on the labelset configuration. | ||
+ | |||
+ | If the corresponding label in the labelset defines derivatives, |
glue/processconfiguration.txt · Zuletzt geändert: 2021/07/05 15:34 von oliver