Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung Nächste Überarbeitung Beide Seiten der Revision | ||
tools [2022/01/07 10:35] 148.251.120.201 alte Version wiederhergestellt (2021/07/29 02:16) |
tools [2024/04/26 14:52] 47.128.19.21 alte Version wiederhergestellt (2017/02/27 20:58) |
||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | =====Dataminer===== | + | ======Dataminer====== |
The datamining tool determines and extracts specific defined parameters (single values) from timeseries data, e.g. maximum, minimum or mean values of specific phases or at specific positions (events). Details are described in the [[http:// | The datamining tool determines and extracts specific defined parameters (single values) from timeseries data, e.g. maximum, minimum or mean values of specific phases or at specific positions (events). Details are described in the [[http:// | ||
+ | =====Features===== | ||
+ | For a long time in the Gaitlab Heidelberg the Matlab based tools " | ||
+ | |||
+ | * It works for arbitrary filetypes, not only normalized data saved as HD-ASC. | ||
+ | * The input-file with the paths to the input data is saved as xml. | ||
+ | * The legacy file type - ASCII tab-delimited format (e.g. created from the **Parametersuche** of **HeiDataProViT**) - can be imported. No problems caused by unvisible/ | ||
+ | |||
+ | |||
+ | =====Advantages in comparison to GDMiner===== | ||
+ | * GDMiner can work only with Heidelberg-ASCII average files (gla) and it assumes, that all timeseries are time-normalized and have a prefix " | ||
+ | * It has its own robust xml-file type to define path lists, no problems with unvisible/ | ||
+ | * More flexibility in definition of phases: E.g. phases can start with " | ||
+ | |||
+ | |||
+ | ===== Advantages in comparison to Parametersuche ===== | ||
+ | * Multiple " | ||
+ | * Calculation of data for both sides in one step. | ||
+ | * The data processing settings can be saved as an xml-file for future use. | ||
+ | * Possibility to select multiple gait phases for calculations | ||
======Gait indizes====== | ======Gait indizes====== | ||
=====Gait profile score====== | =====Gait profile score====== | ||
=====Gait deviation index====== | =====Gait deviation index====== | ||
- | ======Generic data mining====== | ||
- | This datamining tool was orginally implemented for the application " | ||
- | =====Advantages in comparison to GDMiner===== | ||
- | * GDMiner can work only with Heidelberg-ASCII average files (gla) and assumes that all timeseries are time-normalized and have a prefix " | ||
- | * Its own robust xml-file with path lists, no problems with non printable characters (import function for old csv-file is available) | ||
- | * More flexibility in definition of phases. Phases can start with RTO. This was needed for Evas project. | ||
- | ======Working with Session Sets====== | ||
- | A Session Set defines a list of paths to data sessions and can include additional columns with allocated data. The data is organized as a table with rows and columns. | ||
- | =====Import of csv-files====== | ||
- | A csv-file as it can be exported via Excel or HeiDataProVIT can be imported in a Nimue-Platform Project. It is saved as an xml-file in the subfolder "Data Sets" in the project. | + | |
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||