From 7f21f5420ea91d19112907780a5a12faa87c348a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Arne=20K=C3=BCderle?= Date: Tue, 19 Sep 2023 15:48:40 +0200 Subject: [PATCH] Linting --- .../full_pipeline/sensor_position_comparison_instep.py | 4 ++-- .../spatial_parameters/egait_adidas_2014.py | 3 ++- .../spatial_parameters/egait_parameter_validation_2013.py | 3 ++- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/gaitmap-challenges/gaitmap_challenges/full_pipeline/sensor_position_comparison_instep.py b/gaitmap-challenges/gaitmap_challenges/full_pipeline/sensor_position_comparison_instep.py index 200316d..440a4d3 100644 --- a/gaitmap-challenges/gaitmap_challenges/full_pipeline/sensor_position_comparison_instep.py +++ b/gaitmap-challenges/gaitmap_challenges/full_pipeline/sensor_position_comparison_instep.py @@ -11,8 +11,8 @@ Dataset The `Sensor Position Comparison 2019 `_ dataset [1]_ - (`usage example `_, `download `_) contains 4x10m, 2x20m and a long walk (5 min) - gait tests of 14 participants. + (`usage example `_, `download `_) contains 4x10m, 2x20m and a long walk + (5 min) gait tests of 14 participants. The 4x10m and 2x20m tests are performed at 3 different speeds (slow, normal, fast). The dataset uses sensors at 6 different positions of each foot. However, for this challenge only the instep sensors are used. diff --git a/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_adidas_2014.py b/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_adidas_2014.py index a63f14d..a64aa5c 100644 --- a/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_adidas_2014.py +++ b/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_adidas_2014.py @@ -23,7 +23,8 @@ The motion capture system only covers a small part within each trial (usually 2-3 strides). The provided segmented stride list also only covers this part. The pipeline is only expected to return results for these strides. -The start and end value of each stride in the provided segmented stride list follow the stride definitions by Barth et al. [2]_. +The start and end value of each stride in the provided segmented stride list follow the stride definitions by Barth et +al. [2]_. This means the start and end-values are defined by the minimum in the gyr_ml axis right before the toe-off. The ground truth stride length is calculated from the marker position at the heel marker by calculating the distance traveled by this marker in the ground plane between the heel strike right before a stride and the heel strike within diff --git a/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_parameter_validation_2013.py b/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_parameter_validation_2013.py index d76b842..0a9634c 100644 --- a/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_parameter_validation_2013.py +++ b/gaitmap-challenges/gaitmap_challenges/spatial_parameters/egait_parameter_validation_2013.py @@ -20,7 +20,8 @@ The IMU data is cut to the region on the carper, where the reference system is valid. This means, that the data starts mid-movement and there is no resting period within the signal. -The start and end value of each stride in the provided segmented stride list follow the stride definitions by Barth et al. [2]_. +The start and end value of each stride in the provided segmented stride list follow the stride definitions by Barth et +al. [2]_. This means the start and end-values are defined by the minimum in the gyr_ml axis right before the toe-off. The ground truth stride length is calculated from the marker position at the heel marker by calculating the distance traveled by this marker in the ground plane between the heel strike right before a stride and the heel strike within