Documentation Site Map Main Page Reference List Motion Capture Visual3D Overview Visual3D Installation License Activation Getting Started Visual3D Documentation Overview Pipeline Commands Reference Expressions Overview CalTester Mode Overview List of Tutorials Visual3D Examples Overview Troubleshooting Sift Sift Overview Installation Getting Started Sift Documentation Overview Knowledge Discovery for Biomechanical Data Tutorial Overview Troubleshooting Inspect3D Inspect3D Overview Inspect3D Installation Overview Inspect3D Getting Started Overview Inspect3D Documentation Overview Knowledge Discovery in Inspect3D Inspect3D Tutorials Overview Troubleshooting DSX Suite DSX Overview DSX Definitions DSX Suite Installation DSX Tutorials DSX Release Notes xManager Overview PlanDSX Overview Surface3D Overview Orient3D Overview CalibrateDSX Overview Locate3D Overview X4D Overview
This is an old revision of the document!
gait parameters]]]. create user defined statistics for a set of signals. the following stats are computed for the signals selected for each side of the body selected. ====== signal_stats ====== signal value at heel strike hs avg - average value at heel strike hs sd - standard deviation of the value of the signal at heel strike signal value at toe off to avg - average value at heel strike to sd - standard deviation of the value of the signal at heel strike values during stance phase avg stance = sd stance min stance min stance sd time at min stance (avg) time at min stance (sd) max stance max stance sd time at max stance (avg) time at max stance (sd) values during swing phase avg swing sd swing min swing min swingsd time at min swing(avg) time at min swing(sd) max swing max swingsd time at max swing(avg) time at max swing(sd) occurences of stance, swing, and cycle stance (count) = number of stance phases used swing (count)= number of swing phases used cycle (count)= number of cycles used. ====== command_dialog ====== gaitsignalstatsdlg.jpg ====== pipeline_command ====== the pipeline command is as follows: **metric_compute_gait_signal_stats** /signal_types= ! /signal_names= ! /signal_folder=original ! /signal_components= ! /component_sequence= ! /compute_left_side= ! /compute_right_side= ! /result_folder=signal_stats ! /rhs_event=rhs ! /lhs_event=lhs ! /rto_event=rto ! /lto_event=lto ! /left_side_result_name_prefix=l_ ! /right_side_result_name_prefix=r_ ! /result_name_suffix=_stats ! /append_component_to_result_name=false ! /merge_components=false **;** ====== resulting_signals ====== several of the command parameters affect the signal that is created. ===== example1 ===== this group of commands results in a metric signal being created in the signal_stats folder that is the same name as /signal_names parameter and it contains values related to the x-component of the signal. /result_folder=signal_stats /append_component_to_result_name=false /result_name_suffix= /component_sequence=x /merge_components=false \\ ===== example2 ===== this group of commands results in a metric signal being created in the signal_stats folder that appends the string _stats to the name in the /signal_names parameter and it contains values related to the x-component of the signal. /result_folder=signal_stats /append_component_to_result_name=true /result_name_suffix=_stats /component_sequence=x /merge_components=false \\ ===== example3 ===== this group of commands results in a metric signal being created in the signal_stats folder that appends the string "_stats_x" to the name in the /signal_names parameter and it contains values related to the x-component of the signal. /result_folder=signal_stats /append_component_to_result_name=true /result_name_suffix=_stats /component_sequence=x /merge_components=false \\ ===== example4 ===== this group of commands results in a metric signal being created in the signal_stats folder that appends the string "_stats_x" to the name in the /signal_names parameter containing values related to the x-component of the signal; "_stats_y" to the name in the /signal_names parameter containing values related to the y-component of the signals.;"_stats_z" to the name in the /signal_names parameter containing values related to the z-component of the signals.. /result_folder=signal_stats /append_component_to_result_name=true /result_name_suffix=_stats /component_sequence=all /merge_components=false ===== example5 ===== this group of commands results in a metric signal being created in the signal_stats folder that appends the string "_stats" to the name in the /signal_names parameter containing values related to the x-component of the signal; the resulting signal contains 3 frames of data. the first row is related to the x-component, the second row is related to the y-component and the third row is related to the z-component. /result_folder=signal_stats /append_component_to_result_name=false /result_name_suffix=_stats /component_sequence=all /merge_components=true