Kinematics raw data of treadmill walking, running and gait transitions at different speed
<p> The dataset includes kinematics data recorded by a Motion Capture System (Vicon Motion System, Oxford, UK) at 100Hz. Data were filtered (fourth-order zero-lag Butterworth low-pass filter with a cutoff frequency of 6 Hz) and exported with Vicon’s Nexus 2.15 software.</p> <p><b> xx (JSON Dataset)<...
Saved in:
| Main Author: | |
|---|---|
| Other Authors: | , |
| Format: | dataset |
| Published: |
2026
|
| Subjects: | |
| Online Access: | https://doi.org/10.60895/redata/PK1DCE |
| Tags: |
No Tags, Be the first to tag this record!
|
| Summary: | <p> The dataset includes kinematics data recorded by a Motion Capture System (Vicon Motion System, Oxford, UK) at 100Hz. Data were filtered (fourth-order zero-lag Butterworth low-pass filter with a cutoff frequency of 6 Hz) and exported with Vicon’s Nexus 2.15 software.</p> <p><b> xx (JSON Dataset)</b></p> <p>These datasets contain gait trial data collected across different subjects, gaits, speeds. The data is stored as a hierarchical JSON file for ease of parsing, analysis, and expansion.</p> --- <p><b> Structure</b></p> <p>Subject ID: is the JSON filename.</p> <p>The data of each JSON file is organized in these hierarchical levels:</p> <p>Gait/Speed → Trial Number → Kinematic Variables (markers 3D position)</p> <p><b>Where:</b></p> <p>- **Subject ID**: A numeric string (e.g., `"7"`), - **Gait/Speed**: String representing the gait (W = walking; R = running) and the speed in hm/h (e.g., `"18"` means 1.8 km/h; "11" means 11 km/h) ). Speed values can be easily converted to m/s by dividing for 36 (e.g. 18/36 = 0.5 m/s). - **Trial Number**: A string ID for each gait tril (e.g., `"1"`, `"2"`, etc.)</p> <p><b> Trans_VSP_kinematics_data (JSON Dataset)</b></p> <p>This dataset contains variable speed protocol data collected across different subjects and trials. The data is stored as a hierarchical JSON file for ease of parsing, analysis, and expansion.</p> --- <p><b> Structure</b></p> <p>The data is organized in four hierarchical levels:</p> <p>Subject ID → Trial Number → Kinematic Variables (markers 3D position)</p> <p><b>Where:</b></p> <p- **Subject ID**: A numeric string (e.g., `"7"`), - **Trial Number**: A string ID for each gait tril (e.g., `"1"`, `"2"`, etc.)</p> <p>Each trial contains a cycle at variable speed, with walking and running legs. A customized ascent and descent speed ramp was designed, centred on the individual transition speed (Ts), with other 4 steps: Ts -20%, -10% and Ts +10%, +20%, lasting 5 s each step. The complete ramp cycle lasted 50 s.</p> <p>Individual Ts (km/h) where: 6.0: Participant IDs: 16, 24 6.5: Participant IDs: 02, 11, 12, 22, 28 7.0: Participant IDs: 04, 06, 07, 13, 17, 21, 23, 26 7.5: Participant IDs: 03, 08, 09, 10, 15, 18, 19, 20, 25 8.0: Participant IDs: 05, 14</p> <p>Each trial entry contains a dictionary of 55 sampled variables over time: Frame is an index var - The following variables are grouped by three, and named as right or left (R, L) + the name of the body marker + the axis (e.g. RLOBx, RLOBy, RLOBz, for a total of 9 anatomical positions and 18 markers). LOB = Temporal lobe SH = Acromion ELB = Elbow WR = Ulnar stiloyd process GT = Great Trochanter KN = Knee (lateral) AN = Malleolus lateral HEE = Heel MT = 5th Metatarsal The 3D sapece were calibrated following the right hand rule, with the axis "X" = mediolateral; "Y" = anteroposterior; "Z" = vertical. Values are in mm.<p> --- </head> <body> <p><b> Example</b></p> <pre><code>{ "07": { "W40": { "4": { "RLOBx": [61.44, 61.92, 60.88, ...], "RLOBy": [56.09, 56.09, 54.58, ...], ... } } } }</code></pre> </body> </html> |
|---|