TABLE File format

<< Click to Display Table of Contents >>

Navigation:  Problem Descriptor Reference > The Sections of a Descriptor > Definitions > TABLE Import Definitions >

TABLE File format

Previous pageReturn to chapter overviewNext page

Data files for use in TABLE or TABLEDEF input must have the following form:

 

{ comments }

name_coord1   datacount1

  value1_coord1   value2_coord1   value3_coord1 …

name_coord2   datacount2

  value1_coord2   value2_coord2   value3_coord1 …

name_coord3   datacount3

  value1_coord3   value2_coord3   value3_coord3 …

data { comments }

data111   data211   data311 …

data121   data221   data321 …

data131   data231   data331 …

 …            …            …

 …            …            …

data112   data 212   data312 …

data122   data 222   data322 …

data132   data 232   data 332 …

 …            …            …

 …            …            …

 

where

 

name_coordN

is the coordinate name in the N direction.  Names must match defined names in the importing script unless table coordinate redefinition is used.

 

 

valueN_coordM

is the Nth value of the Mth coordinate. These must be in monotonic increasing order.

 

 

datacountN

is the number of data points in the N direction.

 

 

DataJKL

is the data at coordinate point (J,K,L)

 

 

…  

ellipses indicate extended data lists, which may be continued over multiple lines.

 

Note that in presenting data, coord1 is cycled first, then coord1, then coord3.

Coordinate lists and data lists are free-format, and may be arbitrarily spaced, indented or divided into lines.

 

Example:

 

{ this is an example table.  }

x   6

-0.01 2 4 6 8 10.01

y   6

-0.01 2 4 6 8 10.01

data

1.1

2.1

3.1

4.1

5.1

6.1

1.2

2.2

3.2

4.2

5.2

6.2

1.3

2.3

3.3

4.3

5.3

6.3

1.4

2.4

3.4

4.4

5.4

6.4

1.5

2.5

3.5

4.5

5.5

6.5

1.6

2.6

3.6

4.6

5.6

6.6