10.1.1.1 Input

1)     FILES MENU

The FILES option allows the user to: (a) define new input matrices (10.3.1); (b) to request basic information on these files (e.g. matrix title); (c) to introduce a supplementary network UFS or GIS file (10.3.3) to supply, e.g., sector definitions (10.2.5.3) or zone names (10.3.3) and (d) to declare a matrix as following TfL zone name conventions (5.1.7). It may also, post 11.5.2, give access to general SATURN parameters such as the random number seed value (see 10.8.1).

2)     COPY/TRANSPOSE/RE-CODE AN INPUT .UFM FILE; REDEFINE ZONES

Transfer an external input matrix into the internal memory where it can be manipulated, analysed, etc., etc.  The matrix may be either read “as is” or transformed in various ways, e.g. by adding new zones or aggregating existing zones.  Using a simple “trick” this also allows the zonal structure of the internal matrix to be edited.

3)     BUILD/UPDATE THE INTERNAL MATRIX FROM A .DAT FILE

Construct a matrix from an external ascii data file.  This may be either in a “standard” SATURN format or in one set by the user, e.g., to facilitate matrix transfer from other suites of programs or from a spreadsheet program.  In particular this function may be used in conjunction with the “dump” facility under 13 below to transfer a SATURN matrix file into, say, EXCEL, edit it and re-read it within MX.

Under “Update” the matrix may be only partially set, e.g. within a selected area, from the input .dat file or an existing matrix may be “incremented”.