fileformats:d3d
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungLetzte ÜberarbeitungBeide Seiten der Revision | ||
fileformats:d3d [2017/02/16 16:17] – oliver | fileformats:d3d [2021/02/11 12:30] – oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | ====== The .d3d motion data file format====== | + | ====== The Motiondata |
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 158: | Zeile 158: | ||
</ | </ | ||
</ | </ | ||
- | |||
- | FAQ | ||
**How to save periods of missing data?** | **How to save periods of missing data?** | ||
Zeile 167: | 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 193: | Zeile 191: | ||
</ | </ | ||
</ | </ | ||
+ | |||
+ | **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 d3d, v3d, rps, rtde and r3d are recognizes. In a future version of the software a better method which allows the user itself to add further suffixes will be added. | ||
fileformats/d3d.txt · Zuletzt geändert: 2021/02/11 17:47 von oliver