fileformats:c3d
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
fileformats:c3d [2018/01/04 14:31] – oliver | fileformats:c3d [2018/01/04 14:59] (aktuell) – oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
+ | ===== Vicon c3d file format ===== | ||
+ | |||
**Mime Type:** application/ | **Mime Type:** application/ | ||
Zeile 7: | Zeile 9: | ||
The usage of the c3d format is not recommended due to its restrictions and the manifold of unspecified workarounds to overcome them. | The usage of the c3d format is not recommended due to its restrictions and the manifold of unspecified workarounds to overcome them. | ||
- | Some examples: | + | **Some examples:** |
- | * Vicon stores Events in a prprietary | + | * Vicon stores Events in a proprietary |
- | * The count of timeseries is saved in one byte. This results that it also needs a workaround if you want to save more e.g as the CLEVE model do. To mange this additional parameters are defined: DESCRIPTIONS2, | + | * The count of timeseries is saved in one byte. This results that it also needs a workaround, if you want to save more e.g as the CLEVE model do. To manage |
- | * The length of the timeseries is restricted due to the fact that it is saved as INT16 or UINT16 | + | * The length of the timeseries is restricted due to the fact that the number |
+ | |||
+ | **The following list reports the parameters' | ||
+ | * A null frequency (POINT: | ||
+ | * The description of each point (POINT: | ||
+ | * The description of each analog channel(ANALOG: | ||
+ | * The description of the parameter in the analysis (ANALYSIS: | ||
+ | * The subject associated which each parameter in the analysis (ANALYSIS: | ||
+ | |||
+ | **Informations display** | ||
+ | |||
+ | Vicon products (Workstation and Nexus) use the parameter EVENT: | ||
+ | |||
+ | General event: 0 | ||
+ | Foot Strike: 1 | ||
+ | Foot Off: 2 | ||
+ | |||
+ | Without the use of these values, it is known that Workstation and Nexus put all events in general. For Polygon, one user reported that some points had their values set to 0 when all events have their id set to 0. |
fileformats/c3d.1515072679.txt.gz · Zuletzt geändert: 2018/01/04 14:31 von oliver