Closed rmndrs89 closed 11 months ago
Hi Robbin,
First some background for the decisions we made:
With that background, the RamppEventDetection expects the strides to be segmented from this pre-toe-off minima to the next pre-toe-off minima, as it divides each stride into several regions of interest to search the respective events. E.g. we expect the toe off to be the first zero-crossing of the gyr_ml signal and the initial contact to min-vel event to occur in the second half of the stride.
A couple of options how to solve your issue:
In case you go with option 2, there is a function (which is not public API, but I think is fine to use for this), that can do that shift for you in one step: snap_to_min. Just supply an asymmetric window.
If you want to go a little more low-level, this function is based on gaitmap.utlis.array_handling.find_extrema_in_radius
Hi @AKuederle,
super, thanks for the elaborate clarification!
It makes a lot of sense to me to go with the local minima before toe-off, as this signal is --as you mention-- quite consistent across different gait patterns (speeds, neurological disorders).
Thanks, Robbin
Dear all,
if I remember correctly, then in the Hannink et al. (2018) paper different definitions for the strides were used (e.g., midstance-to-midstance versus initial contact-to-initial contact versus msDTW).
Now, when I want to detect specific gait events from my inertial sensor data, I need to supply the event detection algorithm, e.g., RamppEventDetection, with the
stride_list
. Does it matter which definition I use for the strides? Or is the only requirement that there are no gaps between subsequent strides? So could I theoretically also define my strides from midswing-to-midswing, for example?Best regards, Robbin