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:34] 148.251.120.201 alte Version wiederhergestellt (2021/07/27 11:26) |
tools [2024/04/26 14:52] 47.128.19.21 alte Version wiederhergestellt (2017/02/27 20:58) |
||
---|---|---|---|
Zeile 3: | Zeile 3: | ||
=====Features===== | =====Features===== | ||
- | For a long time in the Gaitlab Heidelberg the matlab | + | For a long time in the Gaitlab Heidelberg the Matlab |
- | * Works for arbitrary filetypes, not only normalized data saved as HD-ASC. | + | * It works for arbitrary filetypes, not only normalized data saved as HD-ASC. |
- | * The file with the paths to the input data is saved as xml. | + | * 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 characters any more. | + | * 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 " | ||
- | ===== limintations of Parametersuche ===== | + | |
- | * Multiple " | + | ===== Advantages in comparison to Parametersuche ===== |
- | * Calculation of data for both sides in one step. | + | * Multiple " |
- | * The data processing settings can be saved as an xml-file for future use. | + | * Calculation of data for both sides in one step. |
- | * Possibility to select multiple gait phases for calculations | + | * 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. | + | |
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||