BOX INFORMATION Table Differences

Double-click on the 'mult' box and open its "Box Information" dialog. This gives you the 'mult' box's execution parameters. You can also double click on any other host function box. You should notice that the information in each of the dialogs is specific to that single function box. If you opened multiple dialogs, leave one function's "Box Information" dialog open, but close the rest.

For the open dialog window you have, double-click on the matching embeddable boxes. A "Box Information" dialog opens. You should notice a number of differences between the two dialogs. The hierarchical box "box _information" explains these differences.

Working our way top to bottom, Table 2 highlights the differences between the information presented in the two "Box Information" dialogs.

 

host dialog

embeddable dialog

Graphic:

selected box (See Note 1.)

representative group element (See Note 2.)

Box Stuff:

   

Name:

function name

group identification

Library:

directory location of function

"internal/"

Description:

comment of the box's function

"no documentation on the functionality of the group"

Flags:

status of individual function

status of entire group

Mapping:

 

Cannot map embeddable boxes using this button.

 

Queues:

I/O queues of this one function default "Firing Granularity" and "Threshold" of 2048

I/O queues of the group. Default "Firing Granularity" of 1, minimum default "Threshold" of 64 (See Note 3.)

Parameters:

Parameters for this one function

All parameters needed by the group.

Table Notes:

  1. For a host function box the graphic's border takes on the color code of the workstation it is executing. The color code is assigned in the "Server Key" dialog.
  2. The name of the representative group element is used through Gedae to refer to this collection of function boxes. This name is used in all the tables and references to the group and its execution.
  3. The "Threshold" values for the embedded boxes has a minimum value of 64. This means that the input queues to the group are of size 64, forcing the group to collect 64 data elements before execution. For a "Firing Granularity" of 1, the "Static Schedule" for the group will fire 64 times.

Return to the main page