HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » metric_commands » Metric Signal Value At Event
visual3d:documentation:pipeline:metric_commands:metric_signal_value_at_event

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:pipeline:metric_commands:metric_signal_value_at_event [2024/06/17 18:20] – created sgrangervisual3d:documentation:pipeline:metric_commands:metric_signal_value_at_event [2025/05/21 17:36] (current) – Cleaned up page for a customer. Still needs to be put into Pipeline project format. wikisysop
Line 1: Line 1:
 +====== Metric Signal Value At Event ======
  
 +The Metric_Signal_Value_At_Event command provides the value of the specified signal at the specified frame of data is stored as a metric.
  
- +Notes: 
- +  * All components of the specified signal will be stored in the metric signal. The user also has the option to select an individual component
-===== Legacy Command ===== +
- +
-**Metric_Signal_At_Event** replaced the command **Signal_Value_At_Event** +
- +
-===== Description ===== +
- +
-The value of the specified signal at the specified frame of data is stored as a metric. +
- +
-  * All components of the specified signal will be stored in the metric signal. +
-    * **Since version 5:** the user has the option to select an individual component+
   * If there are multiple occurrences of an EVENT, there will be multiple entries in the metric that is created.   * If there are multiple occurrences of an EVENT, there will be multiple entries in the metric that is created.
   * There is an option to calculate the mean and standard deviation for metrics that have multiple values.   * There is an option to calculate the mean and standard deviation for metrics that have multiple values.
 +  * In cases where there is **NO_DATA** at an event, you need to specify the parameter **/Retain_No_Data_Values=TRUE** should you want this included in the resulting signal.
 +  * **Metric_Signal_At_Event** replaced the legacy command **Signal_Value_At_Event**
 +
 +{{:MetricSignalValueAtEvent.png}}
  
-[[MetricSignalValueAtEvent.png]]+===== Parameters =====
  
-|**Metric_Signal_Value_At_Event**                                                         |                                                                                                                                                                         |+^ Parameter ^ Description ^
 |**/Result_Metric_Name=**                                                                 |The name of the resulting signal.                                                                                                                                        | |**/Result_Metric_Name=**                                                                 |The name of the resulting signal.                                                                                                                                        |
 |**/Result_Metric_Folder=**                                                               |The folder that will contain the resulting signal                                                                                                                        | |**/Result_Metric_Folder=**                                                               |The folder that will contain the resulting signal                                                                                                                        |
Line 30: Line 26:
 |**/Retain_No_Data_Values=**                                                              |(True or False) If the result is no_data, retain the value.                                                                                                              | |**/Retain_No_Data_Values=**                                                              |(True or False) If the result is no_data, retain the value.                                                                                                              |
  
-===== Example Value of a Target =====+===== Example: Find Value of a Target =====
  
 This example calculates the value of the TARGET **RFT1** at the Event_Label **RON** This example calculates the value of the TARGET **RFT1** at the Event_Label **RON**
  
-**Metric_Signal_Value_At_Event**+<code> 
 +Metric_Signal_Value_At_Event
 /Result_Metric_Name=RFT1_ON /Result_Metric_Name=RFT1_ON
 /Result_Metric_Folder=PROCESSED /Result_Metric_Folder=PROCESSED
Line 45: Line 42:
 /Generate_Metric_Length_Metric=FALSE /Generate_Metric_Length_Metric=FALSE
 /Retain_No_Data_Values=TRUE /Retain_No_Data_Values=TRUE
-**;** +; 
-**Note:** In cases where there is **NO_DATA** at an event, you need to specify the parameter **/Retain_No_Data_Values=TRUE** should you want this included in the resulting signal.+</code>
  
-===== Example Time at an Event ===== +==== For a single Component ====
- +
-This example calculates the time of the Event_Label **RON** +
- +
-**Metric_Signal_Value_At_Event** +
-/Result_Metric_Name=RON_TIME +
-/Result_Metric_Folder=PROCESSED +
-/Signal_Types=FRAME_NUMBERS +
-/Signal_Names=TIME +
-/Signal_Folder=ORIGINAL +
-/Event_Name=RON +
-/Generate_Mean_And_Stddev=FALSE +
-/Append_To_Existing_Values=FALSE +
-/Generate_Metric_Length_Metric=FALSE +
-/Retain_No_Data_Values=FALSE +
-**;** +
-===== Component Workaround =====+
  
 Since Metric_Signal_Value_At_Event outputs all three components, here is a workaround of the previous example that will output one component. Evaluate_Expression is used to create a signal with one component, the z component for **RFT1**. Then the Metric_Signal_Value_At_Event will calculate the value of the TARGET **RFT1** at the Event_Label **RON**. Since Metric_Signal_Value_At_Event outputs all three components, here is a workaround of the previous example that will output one component. Evaluate_Expression is used to create a signal with one component, the z component for **RFT1**. Then the Metric_Signal_Value_At_Event will calculate the value of the TARGET **RFT1** at the Event_Label **RON**.
Line 88: Line 69:
 /Generate_Metric_Length_Metric=FALSE /Generate_Metric_Length_Metric=FALSE
 /Retain_No_Data_Values=TRUE /Retain_No_Data_Values=TRUE
 +;
 +</code>
 +
 +===== Example: Calculate the Time of an Event =====
 +
 +This example calculates the time of the Event_Label **RON**
 +
 +<code>
 +Metric_Signal_Value_At_Event
 +/Result_Metric_Name=RON_TIME
 +/Result_Metric_Folder=PROCESSED
 +/Signal_Types=FRAME_NUMBERS
 +/Signal_Names=TIME
 +/Signal_Folder=ORIGINAL
 +/Event_Name=RON
 +/Generate_Mean_And_Stddev=FALSE
 +/Append_To_Existing_Values=FALSE
 +/Generate_Metric_Length_Metric=FALSE
 +/Retain_No_Data_Values=FALSE
 ; ;
 </code> </code>
Line 93: Line 93:
 ===== P2D Signals ===== ===== P2D Signals =====
  
-Consider a P2D signal created using [[Visual3D:Documentation:Pipeline:Signal_Commands:Global_Normalized_Signal_Mean|Global_Normalized_Signal_Mean]]. +Consider a [[visual3d:documentation:definitions:file_formats:p2d_format|P2D]] signal created using [[Visual3D:Documentation:Pipeline:Signal_Commands:Global_Normalized_Signal_Mean|Global_Normalized_Signal_Mean]]. The resulting signal has three components, an index, a mean signals, and a standard deviation signal. It is possible to compute the maximum value of the 3 components using [[Visual3D:Documentation:Pipeline:Metric_Commands:Metric_Maximum|Metric_Maximum]] but it isn't possible to directly identify the standard deviation at that index because it isn't possible to define an Event for a time normalized signal (e.g.it has no frame rate or time. 
-The resulting signal has three components, an index, a mean signals, and a standard deviation signal + 
-It is possible to compute the maximum value of the 3 components using [[Visual3D:Documentation:Pipeline:Metric_Commands:Metric_Maximum|Metric_Maximum]] +Without having an event you cannot get the value of a signal at that event using Metric_Signal_Value_At_Event. One solution, albeit a non-intuitive solution is to [[Visual3D:Documentation:Pipeline:Expressions:Expressions_Overview#Signal_Functions|SORT]] (descending) the P2D signal by the second component (eg. the MEAN). 
-It isn't possible to directly identify the standard deviation at that index because it isn't possible to define an Event for a time normalized signal (e.g.it has no frame rate or time. + 
-Without having an event you cannot get the value of a signal at that event using Metric_Signal_Value_At_Event +<code> 
-One solution, albeit a non-intuitive solution is to [[Visual3D:Documentation:Pipeline:Expressions:Overview#Signal_Functions|SORT]] (descending) the p2D signal by the second component (eg. the MEAN). +Evaluate_Expression
-**Evaluate_Expression**+
 /EXPRESSION=SORT(P2D::TEST::LHIP_ANGLE, -1.0, 2) /EXPRESSION=SORT(P2D::TEST::LHIP_ANGLE, -1.0, 2)
 ! /SIGNAL_TYPES= ! /SIGNAL_TYPES=
Line 108: Line 107:
 /RESULT_NAME=LHIP_ANGLE_SORTED /RESULT_NAME=LHIP_ANGLE_SORTED
 !/APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE !/APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE
-'//;// +; 
-For the resulting signal, the maximum value and the associated standard deviation will be in the first frame +</code>
- +
  
 +For the resulting signal, the maximum value and the associated standard deviation will be in the first frame.
  
visual3d/documentation/pipeline/metric_commands/metric_signal_value_at_event.1718648442.txt.gz · Last modified: 2024/06/17 18:20 by sgranger