Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- analysistools:motiondataminer [2020/03/13 17:20] – [Issues] oliver
+++ analysistools:motiondataminer [2021/09/13 12:20] (aktuell) – [Parameter definition] oliver
@@ Zeile 63: / Zeile 63: @@
 </code>
+==== Expected trial content definition====
+All possible data types which are expected in the trials and possibly should be extracted are listed as children of the <expectedTrialContent>-element.
+The element <phaseTypes> defines a blank separated list of phase type names in its "name"-attribute. The element <eventTypes> equivalent for event-types.
+The <timeserie>-element includes a list of <timeserie>-elements where the attribute "components" defines the count of components of the timeserie and the attribute "name" the name of the timeserie.
+The element <properties> defines a list of properties as children. Each property defines a data type e.g. "String" and a name:
+<code xml>
+<properties>
+  <propertygroup name="TRIAL_INFO">
+       <property type="String" name="cycle_nr"/>
+       <property type="String" name="pose_x"/>
+       <property type="String" name="pose_y"/>
+       <property type="String" name="pose_z"/>
+  </propertygroup>
+</properties>
+</code>
 ==== Parameter definition ====
 After the **<expectedTrialContent>**-element you can find a list of so called **parameters**. Each **parameter** has an **id**, which is referenced in the **scopes**. The **name**-attribute specifies the name of a timeserie, as it is saved in the trials. The **component** attribute specifies the component. If the timeserie is a timeserie of only doubles the component is zero, in other cases it counts the component, starting by zero.
@@ Zeile 70: / Zeile 89: @@
 ^ Type name ^ Description ^ Available for ^
 ^ max | maximum in the case of application to a "phase", "value at" in the case of an event | phases or events |
-^ min | minimum | phases|
+^ min | minimum | phases |
-^ mean | mean | phases|
+^ mean | mean | phases |
+^ std | Square root of the variance from the mean. **Not yet tested.** | phases |
 ^ minframe | frame position, where the minimum is reached | phases|
 ^ maxframe | frame position, where the maximum is reached in the case of application to a "phase", "frame at" in the case of an event | phases or events|
+^ frames | Count of total frames of a phase. These includes frames at which some values can be NaN. **Not yet tested.** | phase |
+^ dist | | |
 ==== Definition of Scopes ====
@@ Zeile 84: / Zeile 107: @@
 ^ type  | "phase" or "event" |
-Each **scope** can have one or more **variables**.
+Each **scope** can include one or more **variables** and **properties**:
+<code xml>
+ <variable id="LeftScapulaPositionShiftLengthMax"
+           name="LeftScapulaPositionShiftLengthMax"/>
+ <property path="TRIAL_INFO/cycle_nr"/>
+</code>
 ==== Definition of Processing Groups====
 This feature is used only, if datamining is based on a folder.
@@ Zeile 111: / Zeile 139: @@
 In the "visual view of resulting data" you can right-click on the datas root node to open a context menu. The action "export" opens a file chooser dialog.
-{{:analysistools:dataminer_export_filechooser.png?600|}}
+{{:analysistools:dataminer_export_filechooser.png?500|}}
 You can choose the path and the file, where to export the data as a csv-file. The exported file can be opened with spreadsheet calculation software. In the case of Excel you can use the suffix ".xsl" and it can be opened directly. Keep in mind that this is typcically a subset of the data shown in the view.
-=====Issues=====
+=====Known Issues=====
-  * ListenpunktEvent- and Phase-Type-Names are shown as "scope type" in the exported exelsheet and also as node name in the node-hierarchie of the UI. It is allowed to use the same name as event and phase type name. But in this case they can not be distinguished. As a workaround use only different names. In a future release the type "event" or "phase" should be added as a suffix between brackets, e.g. RGrasp[event] amd RGrasp[phase].
+  * Event- and Phase-Type-Names are shown as "scope type" in the exported exelsheet and also as node name in the node-hierarchie of the UI. It is allowed to use the same name as event and phase type name. But in this case they can not be distinguished. As a workaround use only different names. In a future release the type "event" or "phase" should be added as a suffix between brackets, e.g. RGrasp[event] amd RGrasp[phase].