Differences

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

--- visual3d:documentation:pipeline:metric_commands:metric_signal_value_at_event [2025/09/18 19:31] – wikisysop
+++ visual3d:documentation:pipeline:metric_commands:metric_signal_value_at_event [2025/10/03 18:00] (current) – [Example: Calculate the Time of an Event] wikisysop
@@ Line 49: / Line 49: @@
 |**/Append_To_Existing_Values=**                                                          |(True or False) If the metric exists, the new values will be appended to the metric, retaining all of the previous values.                                               |
 |**/Generate_Metric_Length_Metric=**                                                      |(True or False) If the metric is a vector quantity (e.g. has 3 components), compute the magnitude of the vector.                                                         |
-|**/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.                                                                           |
 ====Dialog====
@@ Line 78: / Line 78: @@
 </code>
+The resulting values can be found in the **METRIC:PROCESSED** folder and should look similar to below:
+{{:visual3d:documentation:pipeline:metric_commands:rtoe_track.png?600|}}
 ==== For a single Component ====
@@ Line 124: / Line 127: @@
 </code>
+The processed time value can be found in the **METRIC:PROCESSED** folder:
+{{:visual3d:documentation:pipeline:metric_commands:ron_time.png?600|}}
 ===== P2D Signals =====
-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.
+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).
 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).