This file gives technical information about all the routines contained within UCINET.

The manual assumes that users have certain rudimentary knowledge of the Windows operating system and of network terminology. Elementary information on UCINET is available in the accompanying users guide.

Each routine is documented in a standard way. This should help the user to understand some of the non-standard routines once documentation for which they are familiar has been thoroughly digested.

Each routine is documented using the following keywords:

For each entry on the form the manual gives the defaults provided by UCINET. This can be useful in trying to locate files that have been created by the software, or when re-running a particular routine with different parameters.

In addition the manual gives additional information (to the help line on the form) about how to complete each entry on the form.

If the routine requires a dataset (which most usually do) then the manual specifies precisely which type of data can be analyzed. These are as follows:

Graph - an n´n symmetric binary adjacency matrix.

Digraph - an n´n not necessarily symmetric binary adjacency matrix.

Valued graph - an n´n matrix. The entries are usually reals, sometimes there are restrictions on the values to integers or the matrix to symmetric.

Square matrix - an n´n matrix. The entries are usually reals, sometimes there are restrictions on the values to integers or probabilities. Obviously valued graph and square matrix are the same data type, it is just convention which dictates usage.

Matrix - an n´m matrix. The entries are usually reals. These can be restricted to binary or integer.

Each data type is contained within the next. So, for example, any routine that accepts valued graphs will run on digraphs or graphs.

Some routines contain options which will run on different data types. In this case the data type given in the manual is the

Routines which take specific action on multirelational data have this indicated in the data type specification. For example, the routine specified by

has as its data type Digraph.Multirelational. This indicates that this routine acts on multirelational data in a particular way. If this data type is not included and a multirelational data set is submitted for analysis then UCINET will perform the analysis on each relation separately, if possible. In some cases such an action would not make network sense, and in other cases it is simply not technically possible to do this. In these cases the routine only acts on the first relation.

Whilst caution is wise for a strict interpretation, it will be true that for O(N^3) routine doubling the size of N will probably cause the execution time to increase by approximately a factor of 8. Timings which are exponential mean that the user should be aware that small increases in N may cause very large increases in execution time.