analysistools:motiondataminer
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
analysistools:motiondataminer [2017/02/28 22:46] – [Parameter definition] oliver | analysistools:motiondataminer [2021/09/13 12:20] (aktuell) – [Parameter definition] oliver | ||
---|---|---|---|
Zeile 10: | Zeile 10: | ||
{{ : | {{ : | ||
+ | ** | ||
+ | Hint:** The example trial must be a file recognized as a trial. So a processed " | ||
The action automatically creates the " | The action automatically creates the " | ||
Zeile 61: | Zeile 63: | ||
</ | </ | ||
+ | ==== 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 < | ||
+ | |||
+ | The element < | ||
+ | |||
+ | The < | ||
+ | |||
+ | The element < | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
==== Parameter definition ==== | ==== Parameter definition ==== | ||
After the **< | After the **< | ||
Zeile 68: | Zeile 89: | ||
^ Type name ^ Description ^ Available for ^ | ^ Type name ^ Description ^ Available for ^ | ||
^ max | maximum in the case of application to a " | ^ max | maximum in the case of application to a " | ||
- | ^ min | minimum | phases| | + | ^ min | minimum | phases | |
- | ^ mean | mean | phases| | + | ^ mean | mean | phases | |
+ | ^ std | Square root of the variance from the mean. **Not yet tested.** | ||
^ 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 " | ^ maxframe | frame position, where the maximum is reached in the case of application to a " | ||
+ | ^ 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 ==== | ==== Definition of Scopes ==== | ||
Zeile 78: | Zeile 103: | ||
^ 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 | " | ^ type | " | ||
- | Each **scope** can have one or more **variables**. | + | Each **scope** can include |
+ | <code xml> | ||
+ | < | ||
+ | | ||
+ | < | ||
+ | </ | ||
==== Definition of Processing Groups==== | ==== Definition of Processing Groups==== | ||
+ | This feature is used only, if datamining is based on a folder. | ||
^ Attribute name ^ Description ^ | ^ Attribute name ^ Description ^ | ||
^ id | name of processing group as defined in the job config file | | ^ id | name of processing group as defined in the job config file | | ||
- | ^ fileSuffix | + | ^ fileSuffix |
- | ^ selected | + | ^ selected |
===== Visual view for the configuration ===== | ===== Visual view for the configuration ===== | ||
Zeile 99: | Zeile 130: | ||
===== Visual view of the resulting data===== | ===== Visual view of the resulting data===== | ||
- | If the data to be analysed is defined | + | 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" | ||
{{: | {{: | ||
+ | |||
+ | |||
===== Export of CSV-files ===== | ===== Export of CSV-files ===== | ||
- | In the case of application | + | In the " |
+ | |||
+ | {{: | ||
+ | |||
+ | You can choose the path and the file, where to export | ||
+ | |||
+ | =====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 " |
analysistools/motiondataminer.1488318412.txt.gz · Zuletzt geändert: 2017/02/28 22:46 von oliver