Differences

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

--- visual3d:documentation:pipeline:metric_commands:metric_compute_temporal_distance [2024/11/15 18:39] – wikisysop
+++ visual3d:documentation:pipeline:metric_commands:metric_compute_temporal_distance [2024/11/15 18:52] (current) – [Subject computation using subject name/prefix parameters] wikisysop
@@ Line 79: / Line 79: @@
 ==== Files for computing temporal distances ====
-|{{:EditTemporalDistancev5_FILES2.png}}  |- The default command will create average temporal distance values for the ACTIVE files and results can be found in the GLOBAL workspace\\ - **Calculate For Each File:** Calculate average values across entire trial\\ - **Create All Instances:** value for each sequence (multiple values per trial)\\ \\ **NOTE:** To use the Calculate For Each File option, Calculate for Each Trial must be selected as well.  |
+|{{:EditTemporalDistancev5_FILES2.png}}  |- The default command will create average temporal distance values for the ACTIVE files and results can be found in the GLOBAL workspace\\ - **Calculate For Each File:** Calculate average values across entire trial\\- **Calculate For All Cmo Globals:** Calculate global average \\ - **Create All Instances:** value for each sequence (multiple values per trial)\\ \\ **NOTE:** To use the Calculate For Each File option, Calculate for Each Trial must be selected as well.  |
 |{{:EditTemporalDistancev5_Signal.jpg}}  |- If the user would like to define temporal distance metrics using a signal other than the default signal (such as the proximal end of the foot), the user can select a different signal (such as the heel target).\\ \\ - The height is used to calculate [[Visual3D:Documentation:Pipeline:Metric_Commands:Temporal_Distance_Calculations_for_Gait#Statures.2FSecond|statures/second]]  |
-|{{:EditTemporalDistancev5_PROPERTIES.png}}  |- The event labels may be changed to any events desired.\\ \\ - Selecting **Strict Event Label Sequence** will create temporal distance measures for events that occur within a gait cycle. For example Swing Time which occurs between RTO and RHS will only be calculated if the event sequence is RHS+RTO+RHS.\\ \\ - Explanations of the calculations of the temporal distance items can be found [[Visual3D:Documentation:Pipeline:Metric_Commands:Temporal_Distance_Calculations_for_Gait|here]].  |
+|{{:EditTemporalDistancev5_PROPERTIES.png}}  |- The event labels may be changed to any events desired.\\ \\ - Selecting **Strict Event Label Sequence** will create temporal distance measures for events that occur within a gait cycle. For example Swing Time which occurs between RTO and RHS will only be calculated if the event sequence is RHS+RTO+RHS.\\- **[SIDE} String Exclude** will exclude event sequences with that event.\\ \\ - Explanations of the calculations of the temporal distance items can be found [[Visual3D:Documentation:Pipeline:Metric_Commands:Temporal_Distance_Calculations_for_Gait|here]].  |
 |{{:EditTemporalDistancev5_RANGE.jpg}}  |- **Event Instance:** 0 indicates all instances, 1 indicates the first event sequence\\ \\ - **Exclude Sequence:** Creating an event BAD would exclude the trial during which the event occurred  |
@@ Line 93: / Line 93: @@
 ===== Subject computation using subject name/prefix parameters =====
-Visual3D is in the process of supporting multiple subjects within the same workspace, and across CMO/Z library workspaces. Older versions of Visual3D will not support the subject prefix extensions of this command.
+Visual3D now supports multiple subjects within the same workspace, and across CMO/Z library workspaces. Older versions of Visual3D will not support the subject prefix extensions of this command.
 When using a version of Visual3D prior to implementing multisubject support, Visual3D treats each CMO/Z file as a single subject. In this way, the temporal and distance metrics are computed in the CMO/Z GLOBAL for the subject processed within that CMO. In the same manner, when computing the temporal and distance metrics across a library of subjects, each CMO/Z is treated as a single subject and then the subject averages are computed across CMO/Z files and placed into the workspace GLOBAL for the overall mean values across subjects.