Lets you indicate which processes TotalView should attach to when these processes begin executing. Limiting the processes to which TotalView attaches is beneficial as TotalView does not have to be concerned with unattached processes. That is, because you know that you will not be interested in what goes on in within a process, you can cut down on the time that TotalView uses to attach to all or most of your processes.
Use the controls in this area to specify the processes to which TotalView should attach when they are created. You have three choices:
After selecting Attach All or
Detach All, you can individually select or unselect processes. That is, if you only want to select a couple of processes, begin by clicking
Detach All, then select the few to which TotalView should attach.
You can restrict the list of what is displayed by selecting the controls in this area. Filters do not control attaching or detaching. They are a mechanism for limiting the list of processes that are displayed.
Selecting one of the communicators from this list will display only processes using this communicator. You can then select or clear these values in one of the three ways just discussed.
TotalView will limit the display to communicators that receive messages from the indicated ranks. In addition to your rank numbers, TotalView includes two special variables:
All and
MPI_ANY_SOURCE.
This checkbox is automatically selected and the array name displayed if you have invoked
Tools > Attach Subset (Array of Ranks) from the Variable Window. In this case, the dialog box will only display the list of processes whose ranks match the array elements.
Enter rank numbers to filter on. Use a dash to indicate a range of ranks, and commas to indicate individual ranks. For example: 3, 10-16, 24.
Selecting this button tells TotalView to stop all of the processes in the control group after it attaches to a process. If it isn’t selected, TotalView will immediately execute the control group after it attaches to them. The button is not active if the dialog box is launched after the job is already started. It is active only at the initial startup of a parallel job. You typically want to halt processes to allow the setting of breakpoints.