fileformats:d3d
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
fileformats:d3d [2017/02/16 16:01] – oliver | fileformats:d3d [2021/02/11 17:47] (aktuell) – oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | ====== | + | ====== |
This is the recommended file format to store any **time series** data and additional parameters or meta data. | This is the recommended file format to store any **time series** data and additional parameters or meta data. | ||
- | The **c3d file format** and also the **HD ASCII format** | + | The **c3d file format** and also the **HD ASCII format** |
In contrast to the .c3d file format it allows to save multiple trials as a tree of data. E.g. for managing normal gait data, the time series for all joint angles of all strides from all sessions of all subjects | In contrast to the .c3d file format it allows to save multiple trials as a tree of data. E.g. for managing normal gait data, the time series for all joint angles of all strides from all sessions of all subjects | ||
Zeile 12: | Zeile 12: | ||
If a "Vicon trial" is converted to .d3d, all of its properties, saved in the corresponding .enf file, are copied in the **< | If a "Vicon trial" is converted to .d3d, all of its properties, saved in the corresponding .enf file, are copied in the **< | ||
- | If the flag **singlePrection** is set to **true**, then all of the data is saved in float values. | + | If the flag **singlePrecision** is set to **true**, then all of the data is saved in float values. |
<code xml> | <code xml> | ||
Zeile 63: | Zeile 63: | ||
</ | </ | ||
- | Working with properties corresponding to different files in the save file format | + | Working with properties corresponding to different files in the same file format |
- | abc.d3d | + | abc.d3d, abc.avi, abc.1.avi |
- | abc.avi | + | |
- | abc.1.avi | + | |
E.g you have different avi files attached to the same trial and you want to save the offset delay of each of the movies to the data saved in the abc.d3d file, you have to follow this convention: | E.g you have different avi files attached to the same trial and you want to save the offset delay of each of the movies to the data saved in the abc.d3d file, you have to follow this convention: | ||
Zeile 79: | Zeile 77: | ||
</ | </ | ||
- | Common Attributes | + | **Common Attributes:** |
- | | + | ^ name ^ Default |
+ | ^ name | | | | ||
+ | ^ used | true | If this attribute is set to false, the element should be excluded from any calculations or visualization. | | ||
+ | ^ comment | | A free comment, to describe what is the meaning of the elements corresponding data. | | ||
+ | ^ frames | -1 | For a **< | ||
- | name | + | **Events and phases** |
- | |||
- | |||
- | |||
- | |||
- | used | ||
- | |||
- | |||
- | |||
- | true | ||
- | |||
- | If this attribute is set to false, the element should be excluded from any calculations or visualization. | ||
- | |||
- | comment | ||
- | |||
- | |||
- | |||
- | A free comment, to describe what is the meaning of the elements corresponding data. | ||
- | |||
- | frames | ||
- | |||
- | |||
- | |||
- | -1 | ||
- | |||
- | For a < | ||
- | |||
- | Events and phases | ||
- | |||
- | | ||
Phases and events data are saved as subelements of a element which corresponds to a trial. Have a lot at the following example: | Phases and events data are saved as subelements of a element which corresponds to a trial. Have a lot at the following example: | ||
Zeile 185: | Zeile 158: | ||
</ | </ | ||
</ | </ | ||
- | |||
- | FAQ | ||
**How to save periods of missing data?** | **How to save periods of missing data?** | ||
Zeile 194: | Zeile 165: | ||
**Conventions** | **Conventions** | ||
- | | + | To save raw data a naming and structure convention is given as shown in the following example: |
<code xml> | <code xml> | ||
Zeile 221: | Zeile 192: | ||
</ | </ | ||
+ | **Data Types** | ||
+ | |||
+ | ^ Name ^ doubles ^ Description ^ | ||
+ | ^ Double | 1 | | | ||
+ | ^ Tuple3d | 3 | | | ||
+ | ^ Quat4d | 4 | sequence of the values w,x,y,z | | ||
+ | ^ Matrix3d | 9 | | | ||
+ | |||
+ | **How to add motiondata files with different suffix than "d3d** | ||
+ | |||
+ | There is currently no elegant mechanism available. The possible suffixes of motion data file are hardcoded in the follwing two modules: MotionDataFileType2 and Trial2MotionData. Currently the suffixes defined in the following table are recognized. In a future version of the software a better method which allows the user itself to add further suffixes will be added. | ||
+ | |||
+ | ^ Suffix ^ Description ^ | ||
+ | ^ r3d | Raw data collected with JDAQ, e.g. from ROS | | ||
+ | ^ d3d | Processed data | | ||
+ | ^ rps | Raw data collected from Artiminds RPS | | ||
+ | ^ rtde | Raw data collected via the RTDE interface from Universal Robotics | | ||
+ | ^ v3d | Raw data collection by the Vicon system via DataStream API | |
fileformats/d3d.txt · Zuletzt geändert: 2021/02/11 17:47 von oliver