analysistools:motiondataminer
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
analysistools:motiondataminer [2017/03/27 17:28] – [Visual view of the resulting data] 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 82: | Zeile 107: | ||
^ 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. | This feature is used only, if datamining is based on a folder. | ||
Zeile 103: | Zeile 133: | ||
on the selected node opens the context-menu and you can execute the action "Open Datamining sheet" | on the selected node opens the context-menu and you can execute the action "Open Datamining sheet" | ||
{{: | {{: | ||
- | Right-click on the root-node of the shown data hierarchy opens a context menue. There you can execute the " | + | |
Zeile 109: | Zeile 139: | ||
In the " | In the " | ||
- | {{: | + | {{: |
+ | |||
+ | 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 " | ||
- | You can choose | + | =====Known Issues===== |
+ | * Event- and Phase-Type-Names are shown as "scope type" in the exported exelsheet |
analysistools/motiondataminer.1490628500.txt.gz · Zuletzt geändert: 2017/03/27 17:28 von oliver