# Import Network Description from Tables¶

The Import Network Description From Tables wizard can import network descriptions on a primitive table based format.

As most computer software is able to export data to a primitive table based format, this wizard may be the only option for importing network information from, or integrating HUGIN with a thirdparty program unaware of the HUGIN Net language.

A primitive table consists of rows and columns. Individual columns are separated by symbols <SPACE>, <TAB> or comma (‘,’). Rows are separated by either <NEW-LINE> or <CARRIAGE-RETURN><NEW-LINE>.

Importing a network description is performed in three steps:

1. Parse variable definitions

2. Parse link definitions

3. Parse table descriptions

Each kind of description is a file containing a primitive table with only a few formatting conventions.

## Variable definitions¶

The variable definitions table consists of three columns:

<NAME> <TYPE> <STATE>


The first column <NAME> indicates node name. A node name must begin with a letter and only contain characters [a-z][A-Z][0-9].

The second column <TYPE> indicates node type. Valid values are:

L (labelled node)
B (boolean node)
N (numbered node)
I (interval node)
C (continuous node)
F (function node).

The third column <STATE> specify information about node states and is required for labelled, numbered and interval nodes. The specific number of states for a node is determined by the number of lines pertaining to specifying the particular node. States are created in the order they appear in the file. Values have different meaning depending on node type:

Labelled nodes: Value specify state label. The label must be enclosed in quotation marks (“) if it contains any whitespace characters or characters outside the range [a-z][A-Z][0-9]. To specify n states, the node must appear in n lines in the file.

Numbered nodes: Value specify numeric state value. Value must be a number which can be specified using characters [0-9] and dot (‘.’). To specify n states, the node must appear in n lines in the file.

Interval nodes: Value specify state interval endpoints. Value must be a number which can be specified using characters [0-9] and dot (‘.’). Positive and negative infinity is specified by the string ‘infinity’ and ‘-infinity’. To specify n states, the node must appear in n + 1 lines in the file. First line indicate lower bound for first interval, following lines indicate upper bound for previous interval and lower bound for current interval. The last line n + 1 indicate upper bound for state n.

## Table descriptions¶

Node table descriptions are specified in a number of separate files, one per node. Each file contains a primitive table describing the CPT for a particular node. Table descriptions distinguish between tables with model nodes and tables without model nodes.

Tables without model nodes:

 first line second line following lines

The <PARENT-LIST> is a list of parent node names:

<PARENT-LIST> := (<PARENT-NODE> )*


The <NODE-STATE-LIST> is a list of states for the node specified in <NODE>. A state can be either a state number or a state label:

<NODE-STATE-LIST> := (#<STATE-NUMBER> |<STATE-LABEL> )+


When specifying tables for continuous nodes the <NODE-STATE-LIST> instead denotes alpha and variance:

<NODE-STATE-LIST> := alpha variance


The <PARENT-CONFIGURATION> specify a unique configuration of the parent nodes. The list identifies, in parent node order, a state for each parent node specified in <PARENT-LIST>. A state can be either a state number or a state label:

<PARENT-CONFIGURATION> := (#<PARENT-STATE-NUMBER> |<PARENT-STATE-LABEL> )*


The <PROBABILITY-LIST> specifies the probabillity for the particular configuration in <PARENT-CONFIGURATION> for each state in <NODE-STATE-LIST>:

<PROBABILITY-LIST> := (<NUMBER> )+


In the case of continuous nodes, the <PROBABILITY-LIST> specifies the values for mean and variance:

<PROBABILITY-LIST> := <NUMBER-MEAN> <NUMBER-VARIANCE>


Tables for function nodes without model nodes

Specifying a table for a function node is even simpler, as only an expression must be supplied in the form of a quoted string. The table thus consists of a single line with two columns:

 single line

Tables with model variables Specifying a table for a node with model variables is almost the same as without model variables. The difference is the second line, which only contains a <PARENT-LIST> and the following lines which instead of a <PROBABILITY-LIST> contains the expression for the node based on the given parent configuration:

 first line second line following lines

## Example¶

This example is based on the Chest Clinic example and demonstrates what the Chest Clinic network would look like on primitive tables form.

Variable definitions

File: asia.nodes
A L yes
A L no
S L yes
S L no
T L yes
T L no
L L yes
L L no
B L yes
B L no
E L yes
E L no
X L yes
X L no
D L yes
D L no

Link definitions

File: asia.parents
T A
L S
B S
E L T
D B E
X E

Table descriptions

File: A.table
A
yes no
0.01 0.99
File: B.table
B
S yes no
yes 0.6 0.4
no 0.3 0.7
File: D.table
D
B E yes no
yes yes 0.9 0.1
yes no 0.8 0.2
no no 0.1 0.9
no yes 0.7 0.3
File: E.table
E
T L yes no
yes yes 1 0
yes no 1 0
no no 0 1
no yes 1 0
File: L.table
L
S yes no
yes 0.1 0.9
no 0.01 0.99
File: S.table
S
yes no
0.5 0.5
File: T.table
T
A yes no
yes 0.05 0.95
no 0.01 0.99
File: X.table
X
E yes no
yes 0.98 0.02
no 0.05 0.95

## Importing in HUGIN¶

To import the network description click File -> Import -> Import network from tables. The Import From Tables Wizard appears, see Figure 1.

Figure 1: Import From Tables Wizard

Importing:

1. Browse for primitive table files by clicking the Browse button.

2. Arrange files onto appropriate lists using the << and >> buttons to move files between the Available Files list and Node definitions, Network Structure and Tables lists. Clicking the Auto-Arrange button arranges the lists based on file endings (.nodes, .parents, .table).

3. Click on a file to preview its contents.

4. Finally click Import.