This pipeline computes the Gait Temporal Distance values consistent with the Visual3D report item. Note that the results consist of data from multiple files, so the results are stored in the Global_Workspace. As with most other pipeline commands, this command acts on the Active_Files. Compute Temporal Distance might be used when computing stride length, or other similar values.

If, for example, you have two groups of files (e.g. 2 TAGS) and you want to compute temporal distance metrics independently for each group.

• First, make one TAG active and set the output folder (GLOBAL_RESULT_METRIC_FOLDER) with a name reflecting the TAG.
• Second, make the other TAG active and set a unique output folder.

Command including default values. This command can be found in the Pipeline Workshop within the Metric folder.

Metric_Compute_Temporal_Distance
! /GLOBAL_RESULT_METRIC_FOLDER=TEMPORAL_DISTANCE
! /CALCULATE_PER_FILE=FALSE
! /CALCULATE_PER_ALL_CMO_GLOBALS=FALSE
! /CREATE_ALL_INSTANCES=FALSE
! /CREATE_EMPTY_VALUES=TRUE
! /RIGHT_FOOT_LOCATION=KINETIC_KINEMATIC::RFT::ProxEndPos
! /LEFT_FOOT_LOCATION=KINETIC_KINEMATIC::LFT::ProxEndPos
! /HEIGHT=METRIC::PROCESSED::HEIGHT
/RHS_EVENT=RHS
/LHS_EVENT=LHS
/RTO_EVENT=RTO
/LTO_EVENT=LTO
! /STRICT_EVENT_SEQUENCE_VALIDATION=FALSE
! /RSTRIDE_EXCLUDE=
! /LSTRIDE_EXCLUDE=
! /INCLUDE_EVENTS=
! /EXCLUDE_EVENTS=
! /EVENT_INSTANCE=0
! /COMPUTE_SPEED=TRUE
! /COMPUTE_STATURES_PER_SECOND=TRUE
! /COMPUTE_STRIDE_WIDTH=TRUE
! /COMPUTE_STRIDE_LENGTH=TRUE
! /COMPUTE_CYCLE_TIME=TRUE
! /COMPUTE_STEP_LENGTH=TRUE
! /COMPUTE_STEP_TIME=TRUE
! /COMPUTE_STANCE_TIME=TRUE
! /COMPUTE_SWING_TIME=TRUE
! /COMPUTE_STEPS_PER_MINUTE=TRUE
! /COMPUTE_STRIDES_PER_MINUTE=TRUE
! /COMPUTE_DOUBLE_LIMB_SUPPORT_TIME=TRUE
! /COMPUTE_RIGHT_INITIAL_DOUBLE_LIMB_SUPPORT_TIME=TRUE
! /COMPUTE_RIGHT_TERMINAL_DOUBLE_LIMB_SUPPORT_TIME=TRUE
! /COMPUTE_FLIGHT_TIME=FALSE
! /TREADMILL_SPEED=
! /LEFT_TREADMILL_SPEED=
! /TREADMILL_DIRECTION=
;

Note that the treadmill direction is new, and is specified as a unit vector.

If the subject is walking in the y-direction of the laboratory the unit vector would be:

Give the following legacy parameters

/TREADMILL_DIRECTION_X=0
/TREADMILL_DIRECTION_Y=1
/TREADMILL_DIRECTION_Z=0

The new parameter is:

/TREADMILL_DIRECTION=UNIT_VECTOR(0,1,0)

The following table shows the command parameters seen above and their descriptions:

The below dialog has been used within Visual3D as of v5.

Dialog	Description
	- 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.
	- 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 statures/second
	- 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 here.
	- 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
	- The treadmill unit vector refers to the Anterior Direction of walking - Speed, (left/right/average) stride and step length, and statures/second are dependent on belt speed.\\- The result folder may have any name and will be a subfolder of the METRIC folder.

To use the Compute Temporal Distance command on gait cycle trials we must first identify key gait events. This can be done using the Automatic Gait Events command as shown below.

Automatic_Gait_Events
! /FRAME_WINDOW=8
! /USE_TPR=TRUE
! /TPR_EVENT_INSTANCE=1
;

Now that key events in the gait cycle have been identified we can use the Compute Temporal Distance command to compute the mean left and right flight time for each trial.

Flight time is the average time from LTO to RHS (ensuring no LHS or RTO events occur between LTO and RHS) and RTO to LHS (ensuring no RHS or LTO events occur between RTO and LHS).

• Left flight time is calculated from LTO to RHS.
• Right flight time is calculated from RTO to LHS.

Metric_Compute_Temporal_Distance
! /GLOBAL_RESULT_METRIC_FOLDER=TEMPORAL_DISTANCE
/CALCULATE_PER_FILE=TRUE
! /CALCULATE_PER_ALL_CMO_GLOBALS=FALSE
! /CREATE_ALL_INSTANCES=FALSE
! /CREATE_EMPTY_VALUES=TRUE
! /RIGHT_FOOT_LOCATION=KINETIC_KINEMATIC::RFT::ProxEndPos
! /LEFT_FOOT_LOCATION=KINETIC_KINEMATIC::LFT::ProxEndPos
! /HEIGHT=METRIC::PROCESSED::HEIGHT
/RHS_EVENT=RHS
/LHS_EVENT=LHS
/RTO_EVENT=RTO
/LTO_EVENT=LTO
! /STRICT_EVENT_SEQUENCE_VALIDATION=FALSE
! /RSTRIDE_EXCLUDE=
! /LSTRIDE_EXCLUDE=
! /INCLUDE_EVENTS=
! /EXCLUDE_EVENTS=
/EVENT_INSTANCE=ALL
/COMPUTE_SPEED=FALSE
/COMPUTE_STATURES_PER_SECOND=FALSE
/COMPUTE_STRIDE_WIDTH=FALSE
/COMPUTE_STRIDE_LENGTH=FALSE
/COMPUTE_CYCLE_TIME=FALSE
/COMPUTE_STEP_LENGTH=FALSE
/COMPUTE_STEP_TIME=FALSE
/COMPUTE_STANCE_TIME=FALSE
/COMPUTE_SWING_TIME=FALSE
/COMPUTE_STEPS_PER_MINUTE=FALSE
/COMPUTE_STRIDES_PER_MINUTE=FALSE
/COMPUTE_DOUBLE_LIMB_SUPPORT_TIME=FALSE
/COMPUTE_RIGHT_INITIAL_DOUBLE_LIMB_SUPPORT_TIME=FALSE
/COMPUTE_RIGHT_TERMINAL_DOUBLE_LIMB_SUPPORT_TIME=FALSE
/COMPUTE_FLIGHT_TIME=TRUE
! /TREADMILL_SPEED=
! /LEFT_TREADMILL_SPEED=
! /TREADMILL_DIRECTION=
;

Once the pipeline has been executed you should see a new TEMPORAL_DISTANCE folder in the METRIC section of the Signals and Events tab. Within this folder you can find the mean flight time for the left and right sides.

Combine with other commands and show step-by-step process for frequent use case

Versions of Visual3D more recent than v2022.08.1 support multiple subjects within the same workspace, and across CMO/Z library workspaces. Visual3D with multisubject support extends these metric calculations to be computed for each subject that is identified in the .C3D parameters SUBJECT section. In this way, the a single CMO/Z GLOBAL workspace will contain the computed metrics for each subject within the CMO/Z file, prefixed with the subject's prefix identifier contained in the .C3D parameters. The GLOBAL workspace of the CMO/Z will also contain an unprefixed set of metrics for the average across the subjects contained inside the CMO/Z file. When working across CMO/Z files in the CMO/Z library, multisubject support for this command will treat each subject mean in each CMO/Z file as separate subject averages to be included for calculating the temporal and distance metric averages across all the subjects in the CMO/Z library.

Older versions of Visual3D will not support the subject prefix extensions of this command and will treat 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.

The following are useful resources for temporal data metrics for Control Data Sets.