HAS-Motion Software Documentation

This is an old revision of the document!

---

tutorial:_advanced_command_pipeline#metric_time_between_events]] ===== metric_time_between_events command details ===== below are the details for this command: |**metric_time_between_events** | | |**/result_metric_name==** |the name of the metric signal | |**! /result_metric_folder=processed** |the metric signal folder for the result. | |**/[[visual3d:documentation:c3d_signal_types:event_label_data_type#event_sequence|event_sequence]]=**|a list of events (separated by "+" signs). | |**/[[visual3d:documentation:c3d_signal_types:event_label_data_type#exclude_events|exclude_events]]=**|this event_sequence must not be during the sequence requested. | |**! /generate_mean_and_stddev=true** |(true or false)generate the mean and standard deviation for all of the metrics created | |**! /append to existing values=false** |(true or false)append this list of metrics to an existing metric of the same result name| \\ in this example, consider the metric **right_terminal_double_limb_support** which is the time between **lhs** and **rto**. <code> metric_time_between_events /result_metric_name=right_terminal_double_limb_support ! /result_metric_folder=processed /event_sequence=lhs+rto /exclude_events=lto+rhs ! /generate_mean_and_stddev=true ! /append_to_existing_values=false ; </code> below is the dialog that pops up when pipeline selection is edited by double clicking with the left mouse button. timebetweeneventsdlg.png **note: event_sequence** - it is important to note that this command assumes that the events are specified in the correct order chronologically. for example, if the event sequence is e1+e2 e1 must occur before e2 or no metric signal will be created. if it is not always possible to ensure the chronological order, a series of pipeline commands may be necessary. ===== example 1 : there is only one occurrence of e1 and e2 ===== execute the **metric_time_between_events** twice in succession, once with the range e1+e2, then the second one with the range e2+e1 and set the option /append_to_existing_value=true on the second call. <code> metric_time_between_events /result_metric_name=diff ! /result_metric_folder=processed /event_sequence=e1+e2 /exclude_events= /generate_mean_and_stddev=false ! /append_to_existing_values=false ; metric_time_between_events /result_metric_name=diff ! /result_metric_folder=processed /event_sequence=e2+e1 /exclude_events= /generate_mean_and_stddev=false /append_to_existing_values=true ; </code> **note:** if there are multiple events, and they can occur in any sequence, then there would be no way of telling which sequence you really wanted. if this is the case, you would need to add an event in the middle of the sequence to be explicit about which sequences that you really want, such as e1+mid+e2, and e2+mid+e1 ===== example 2 : there is always the same number of occurrences of e1 and e2 ===== an alternative to the **metric time between events** would be to use the command **evaluate_expression**. in this case you can use **evaluate_expression** to compute the time differences between e2 and e1. <code> evaluate_expression /expression=event_label::original::e2-event_label::original::e1 /result_name=diff /result_type=metric ! /result_folder=processed ; </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.