Operations Table

The Operations table displays a list of all the operations the Execution Profiler recorded. Each row in the table displays the following information about an operation:

• Index —The zero-based index of the operation. The profiler assigns indexes in the order in which it encounters operations.
• Operation —The source of the operation, such as Step, UUT, Lock, Step Module, etc, followed by a description of the action performed. Examples: Step Module: Execute , Step Module: Load , Notification: Set , Queue: Enqueue .
• State —The current state of the operation. Possible states are Blocked, In Use, Aborted, Timed Out, and Completed.
• Item Name —The name of the item the operation acts upon.
• Events —The number of events the profiler recorded for the operation.
• Completed —Displays True if the operation completed, which a state of Completed, Timed Out, or Aborted indicates.
• Start Time —The time of the first event in the operation, measured since the first recorded event.
• End Time —The time of the last event in the operation, or the current time if the operation is not complete, measured since the first recorded event.
• Duration —The time between the values of the Start Time and the End Time columns.
• Time Blocked —The time the operation blocked its thread while waiting to acquire a synchronization item.
• Time in Use —The length of time the operation used its item.
• Test Socket —The zero-based test socket index, if any, for the thread in which the operation takes place. The test socket index indicates the UUT position or test fixture on which the thread operates.
• Thread ID —The TestStand thread ID. This value is unique to each thread.
• Thread —The display name of the thread in which the operation takes place.
• Step —The name of the step that generated the events in the operation. The column displays ellipses ( … ) if the events are from multiple steps.
• Step Index —The index in a step group of the step that generated the events in the operation. The column displays ellipses ( … ) if the events are from different step indexes.
• Step Group —The step group of the steps that generated the events in the operation. The column displays ellipses ( … ) if the events are from multiple step groups.
• Sequence —The name of the sequence that contains the steps that generated the events in the operation. The column displays ellipses ( … ) if the events are from multiple sequences.
• File —The base name of the sequence file that contains the steps that generated the events in the operation. The column displays ellipses ( … ) if the events are from multiple files.
• Resource Alternative Index —The zero-based index of the resource alternative the Use Auto Scheduled Resource step selects. Use the Use Auto Scheduled Resource steps to specify alternative sets of resources. The resource set the step actually acquires varies according to the availability of resources at the time the step executes. This column is empty when the event is not for a Use Auto Scheduled Resource step or when the step specifies only one resource alternative.
• Module Path —The file path of the code module associated with the operation. To populate this column, select File»Configure Data Collection , then enable Module Paths and Environments .
• Module Environment —Information about the module execution environment that might affect performance. To populate this column, select File»Configure Data Collection , then enable Module Paths and Environments .
• Module Inputs and Outputs —A JSON representation of the values passed to and from the code module. To populate this column, select File»Configure Data Collection , then enable Module Inputs and/or Module Outputs .

See Also

Profiler Window Tables

Synchronization Step Types

Using the Configure Data Collection Dialog Box