visual3d:documentation:pipeline:signal_commands:mimicking_temporal_distance_command
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| visual3d:documentation:pipeline:signal_commands:mimicking_temporal_distance_command [2024/06/14 17:30] – created sgranger | visual3d:documentation:pipeline:signal_commands:mimicking_temporal_distance_command [2024/11/15 19:03] (current) – wikisysop | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | |===== Contents | + | ====== Mimicking Temporal Distance Command ====== |
| This is an example pipeline that mimics the temporal distance metrics command. The script allows the user to customize the metrics computed. This is only an example because the computed values are not identical with the metrics computed by Visual3D temporal distance command. | This is an example pipeline that mimics the temporal distance metrics command. The script allows the user to customize the metrics computed. This is only an example because the computed values are not identical with the metrics computed by Visual3D temporal distance command. | ||
| Line 387: | Line 387: | ||
| </ | </ | ||
| - | ===== Example : Modification | + | ==== Example : Modification ==== |
| **Customer Request:** | **Customer Request:** | ||
| I am using the temporal distance (with metric pipeline commands) script from your website, however, I'd like to calculate the parameters by stride instead of using the Global StrideVectors_MEAN. First, I calculated vector between events to create a Right StrideVectors and Left StrideVectors. To compute stride width, do I cross the LeftStep vectors with the Left StrideVectors or Right StrideVectors. | I am using the temporal distance (with metric pipeline commands) script from your website, however, I'd like to calculate the parameters by stride instead of using the Global StrideVectors_MEAN. First, I calculated vector between events to create a Right StrideVectors and Left StrideVectors. To compute stride width, do I cross the LeftStep vectors with the Left StrideVectors or Right StrideVectors. | ||
| + | |||
| **Response: | **Response: | ||
| Line 399: | Line 400: | ||
| For example, for the left step length and width calculations you would create new events RS_LHS, RS_LTO, such that the left side events are created from Event_Copy using LHS and LTO as the event to copy, but only if it occurs in the Right Stride (RS) EVENT_SEQUENCE RHS+RHS. Do the same for the right side. Calculate the left strides using LHS, right strides using RHS. Calculate the left steps metrics using RS_RHS to RS_LHS against the right strides, and the right step metrics using LS_LHS to LS_RHS against the left strides. | For example, for the left step length and width calculations you would create new events RS_LHS, RS_LTO, such that the left side events are created from Event_Copy using LHS and LTO as the event to copy, but only if it occurs in the Right Stride (RS) EVENT_SEQUENCE RHS+RHS. Do the same for the right side. Calculate the left strides using LHS, right strides using RHS. Calculate the left steps metrics using RS_RHS to RS_LHS against the right strides, and the right step metrics using LS_LHS to LS_RHS against the left strides. | ||
| You will end up with fewer metrics this way than with our default way of calculating metrics against the average motion file walking direction. Your method will be more accurate if the subject is walking a curved path. | You will end up with fewer metrics this way than with our default way of calculating metrics against the average motion file walking direction. Your method will be more accurate if the subject is walking a curved path. | ||
| - | |||
| - | Retrieved from "" | ||
visual3d/documentation/pipeline/signal_commands/mimicking_temporal_distance_command.1718386216.txt.gz · Last modified: 2024/06/14 17:30 by sgranger