Benutzer-Werkzeuge

Webseiten-Werkzeuge


analysistools:motiondataminer

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
analysistools:motiondataminer [2017/02/28 20:04] – [Scope definition] oliveranalysistools:motiondataminer [2021/09/13 12:20] (aktuell) – [Parameter definition] oliver
Zeile 10: Zeile 10:
  
 {{ :analysistools:create_datamining_filter.png?500 |}} {{ :analysistools:create_datamining_filter.png?500 |}}
 +**
 +Hint:** The example trial must be a file recognized as a trial. So a processed ".d3d"-file does not work.
  
 The action automatically creates the "**expectedTrialContent**" based on the **example trials content**. In most cases this includes more than you want, so you have to delete the not needed parts. The action automatically creates the "**expectedTrialContent**" based on the **example trials content**. In most cases this includes more than you want, so you have to delete the not needed parts.
Zeile 61: Zeile 63:
 </code> </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 ==== ==== 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. 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 66: Zeile 87:
 The most interesting is the "**type**" attribute. Have a look at the following table to see, which types are currently available. Additionally types can be implemented easy, if needed. The most interesting is the "**type**" attribute. Have a look at the following table to see, which types are currently available. Additionally types can be implemented easy, if needed.
  
-^ Type name ^ description available for ^+^ 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 | ^ 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| ^ 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| ^ 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 | | |
  
-==== Scope definition ====+ 
 +==== Definition of Scopes ====
  
 The **scope** defines event-types or phase-types, for which the **parameters** are determined. Have a look at the following table to learn about its attributes. The **scope** defines event-types or phase-types, for which the **parameters** are determined. Have a look at the following table to learn about its attributes.
  
 ^ Attribute name ^ Description ^ ^ Attribute name ^ Description ^
-^ id  | phases or events |+^ id  | id to determine between different scopes, typically numbers starting with zero |
 ^ name  | name of phase- or event-type | ^ name  | name of phase- or event-type |
 ^ type  | "phase" or "event" | ^ type  | "phase" or "event" |
  
 +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.
 +
 +^ Attribute name ^ Description ^
 +^ id  | name of processing group as defined in the job config file |
 +^ fileSuffix  | If datamining is based on all trials of an selected folder, the trial data is read from the file with the given file suffix. |
 +^ selected  | true or false, depending of the trials defined by this group are included or excluded from the datamining.|
 ===== Visual view for the configuration ===== ===== Visual view for the configuration =====
  
Zeile 91: Zeile 130:
  
 ===== Visual view of the resulting data===== ===== Visual view of the resulting data=====
-If the data to be analysed is defined by selection the GUI shows the extracted data directly:+Data can be selected by left-click on a trial child node of a processed d3d-file. Right-click   
 +on the selected node opens the context-menu and you can execute the action "Open Datamining sheet". This opens a View to min/rom/max of all timeseries which are defined as available in the configuration for all phases as defined in the configuration.
 {{:analysistools:upperlimb_datamining.png?700|}} {{:analysistools:upperlimb_datamining.png?700|}}
 +
 +
  
 ===== Export of CSV-files ===== ===== Export of CSV-files =====
-In the case of application on a list of datasets the extracted data is written into files which can be opend with spreadsheet calculation software like Excel.+In the "visual view of resulting data" you can right-click on the datas root node to open context menu. The action "export" opens a file chooser dialog.  
 + 
 +{{: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. 
 + 
 +=====Known Issues===== 
 +  * 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].
analysistools/motiondataminer.1488308645.txt.gz · Zuletzt geändert: 2017/02/28 20:04 von oliver

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki