HAS-Motion Software Documentation

This is an old revision of the document!

---

**metric_vector_between_events** | | |**/metric_name=** |the name of the resulting metric signal. | |**/generate_vector_length_metric=** |(true or false)compute the length of the vector (e.g. a scalar). | |**/start_signal_name=** |the name of the signal whose value will be obtained from the start event. | |**/start_signal_type=** |the type of the start signal. | |**/end_signal_name=** |the name of the signal whose value will be obtained from the end event. | |**/end_signal_type=** |the type of the end signal. | |**/end_signal_folder=** |the folder of the end signal. | |**/[[visual3d:documentation:c3d_signal_types:event_label_data_type#event_sequence|event_sequence]]=**|a list of events (separated by "+" signs). for example, lhs+rto | |**/[[visual3d:documentation:c3d_signal_types:event_label_data_type#exclude_events|exclude_events]]=**|exclude sequences containing these events. | |**/generate_mean_and_stddev=** |(true or false)generate the mean and standard deviation for all of the metrics created | |**/append to existing values=** |(true or false)append this list of metrics to an existing metric of the same result name| \\ the command can be edited in the text editor of the pipeline workshop or can be edited from a dialog. the dialog that pops up when pipeline selection is edited by double clicking with the left mouse button. the example below shows the dialog. ===== example: stride length vector for gait ===== the dialog below contains the values for creating the stride length vector on the right side during gait. metricvectorbetweeneventsdlg.png the command looks like this in the text editor: <code> metric_vector_between_events /result_metric_name=stridevectors ! /result_metric_folder=processed /generate_vector_length_metric=false /start_signal_type=kinetic_kinematic /start_signal_name=proxendpos /start_signal_folder=rft /end_signal_type=kinetic_kinematic /end_signal_name=proxendpos /end_signal_folder=rft /event_sequence=rhs+rhs /exclude_events= ! /generate_mean_and_stddev=true /append_to_existing_values=true ! /retain_no_data_values=false ; </code> **note:** to get stride length, use the parameter /generate_vector_length_metric=true to create the scalar of the stride vector. \\ ===== example: stride length vector for throwing ===== a stride length vector (or scalar) can also be calculated in throwing. events are created that define the particular phases of the throwing motion. below is an example of calculating a stride length between **arm cock start** and **lead foot contact**. <code> metric_vector_between_events /result_metric_name=stride length ! /result_metric_folder=processed /generate_vector_length_metric=true /start_signal_type=kinetic_kinematic /start_signal_name=proxendpos /start_signal_folder=rft /end_signal_type=kinetic_kinematic /end_signal_name=proxendpos /end_signal_folder=lft /event_sequence=arm cock start+lead foot contact /exclude_events= ! /generate_mean_and_stddev=true /append_to_existing_values=true ! /retain_no_data_values=false ; </code> ===== visual3d versions supporting subject prefixes ===== note: when using events in a command, the commands will iterate across subjects contained in the current workspace. as such, events and sequences listed as command parameters should not contain a prefix. as each subject is processed, the event range/sequence specified will automatically use the specific events prefixed for each subject as they are processed.