SATURN MANUAL (V10.

9)

The Basic SATURN Model

3. The Basic SATURN Model

3.1 The Network Model Structure

3.1.1 The SATURN Network Modules

Conceptually the basic network model has seven main “functions” (in addition to a
wide range of supplementary network programs plus matrix manipulation), the first
three of which are concerned with getting traffic flows onto the network, and the
last four more generally with the analysis of loaded networks.

Originally each “function” was contained within a single program or module.

However in more recent versions (9.3 and beyond) the basic “functions” are
aggregated into single very large programs such as SATALL and PIX below that
carry out a wide range of functions.

Those which deal with loading traffic are:

 The Network Build program, SATNET, which checks network data input and
sets up the files required by:

 The combined simulation-assignment program SATALL whose functions

were originally provided by two separate programs:

 The Assignment, SATEASY, which assigns traffic on the basis of the delays
given by the simulation.

 The Simulation, SATSIM, which models in detail the passage of traffic

through the network and the resulting delays.

The „analysis‟ and display programs comprise:

 The network general analysis and plot program P1X which displays link-
based data either to a terminal or on a hard-copy device (and includes
virtually all the functions contained in the following three original programs).

 The analysis program, SATLOOK, which enables a detailed description of

traffic conditions to be printed in text format.

 The node editing program SATED which allows nodes to be simulated on an

individual basis using interactive commands.

 The data base analysis program SATDB which allows an essentially free-
format manipulation and display of data.

5101396 / May 11 3-1

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Figure 3.1 and Figure 3.2 illustrate the inter-relationships of these functions
represented by discrete programs. Programs are enclosed by boxes and the files
passed between the programs and/or inputs to them are also indicated. Section
3.3 describes the file name conventions.

How to create the trip matrix file to be assigned, trips.ufm in Figure 3.1 and Figure
3.2, is dealt with in Section 4.

3.1.2 The Iterative Structure

A single „run‟ of SATURN to achieve a loaded network will usually be

accomplished by a single call to a SATURN control file (see 14.3). Parameters
are used to indicate the network and (optionally) trip matrix file names; e.g.

SATURN Netname Tripname

This causes the network build module SATNET to be activated followed by

SATALL to perform the assignment and simulation functions, as illustrated in
Figure 3.1.

Historically SATURN made use of an automatic loop between two separate

programs SATASS (or SATEASY) and SATSIM (Figure 3.2) and this may still be
done - although not recommended in normal circumstances. The choice of the
external or internal loop is dictated by the procedure used: SATURN and
SATURN9 use SATALL, SATURN8 uses the explicit loop. See Sections 9.1 and
14.3.

SATNET checks all input data, outputs error messages and sets up the internal
structural networks as required by (a) the simulation and (b) the assignment. The
precise structure of these networks or of the .uf* files which are passed between
programs need not concern the normal user; a general description is given in
Section 5. Data format specifications are given in Section 6.

The primary objective of the simulation is to determine junction delays resulting

from a given pattern of traffic. A general description of the assumptions made and
the procedures followed is given in Section 8. The information on delays is input
to the assignment which selects appropriate routes through the network for each
element in the trip matrix, bearing in mind relationships between travel time and
flow as determined by the simulation. By default the model uses an „equilibrium‟
technique based on an optimum combination of all-or-nothing assignments, so
that for a given O-D pair a range of routes is normally used but each has the same
minimum O-D cost. Alternative assignment techniques, e.g., all-or-nothing, Burrell
multiple-route, may also be used. Section 7 provides details.

The flows generated by the assignment model are then returned to the simulation
model which in turn re-calculates junction delays for re-input to the assignment.
The resulting iterative procedure is illustrated in Figure 3.1. While in principle the
loop can begin with either a simulation using default flow values or an assignment,
using default flow-delay relationships, in practice it is found to be better to start
with the assignment. The procedure terminates when the re-assignment of traffic

5101396 / May 11 3-2

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

is sufficiently small or a (user-specified) maximum number of iterations (MASL) is

exceeded. Normally the sequence concludes with a run of the simulation.

In the case of “buffer-only” networks, i.e., networks coded without any simulation
network (see 5.3), it is not necessary to run the simulation, in which case
convergence is reached by running the assignment once and proceeding directly
to the analysis programs.

Apart from the iterative loops between the simulation and assignment stages there
are also internal iterative loops within both stages which need to converge.
Generally speaking users should allow a sufficient number of internal iterations
(as governed by the parameters NITA and NITS described in 6.3) for the
individual programs to converge.

3.1.3 The Analysis and Display of Results

The analysis programs P1X etc. (see Section 11) enable users to examine output
from the assignment or simulation using interactive commands.

In addition PIX/PMAKE also provides for on-line network editing. While not
shown in Figure 3.1 there are two “feedback” loops from PIX. Firstly, a new
network data file suitable for input to SATNET may be produced by PIX by editing
existing network files. Secondly an edited version of the .ufs file may also be
produced and fed directly back to SATALL.

In older versions of SATURN (Figure 3.1) the analysis functions of P1X were
contained in four separate programs, P1, SATLOOK, SATDB and SATED. The
latter three still exist as distinct programs and in certain situations are best run in
that mode rather than within P1X.

5101396 / May 11 3-3

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Figure 3.1 – Running the Basic Saturn Model using SATALL; the current methodology

5101396 / May 11 3-4

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Figure 3.2 – Running the Basic SATURN Model using separate programs; the original
methodology

5101396 / May 11 3-5

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.2 Data Requirements

The input data to be prepared by the user consists of: (i) trip matrix data as
described in Section 4, and (ii) network data as described in Section 6.

Simulation network data requirements may be summarised as follows:

a) Universal parameters such as minimum gap acceptance, etc;

b) Junction data - type of junction (signals/priority/roundabout); co-ordinates;

c) Link data - distance, time or speed, number of lanes, stacking capacity

(optional);

d) Turn data - a saturation flow, lanes available, a priority marker indicating

give ways, etc;

e) Traffic signal data - stage lengths; offsets; cycle time

Thus all data input, with the exception of saturation flows which require some
degree of “engineering judgment”, are well defined parameters which may be
obtained by relatively simple observation.

Buffer network data consists of link-based data only, e.g., as under (c) above.

Additional network-based data is also contained (optionally) within both GIS files
(see 5.6) and network X-files (see 6.13).

Users who wish to re-code existing networks and matrices to run on SATURN
should refer to Section 15.8.

3.3 File Name Conventions

Running SATURN programs involves the creation and manipulation of a large

number of files. This section describes a recommended standard method for
handling file names

3.3.1 General Principles

Files may be classified in a number of different ways; e.g. by their computer-

based characteristics

 Input/output files,
1
 “Unformatted binary” vrs. “text” or “ascii”,

* As far as the normal user is concerned the essential difference between text and binary files is
that a text file may be created using the keyboard and/or viewed on the screen, (e.g., using a

5101396 / May 11 3-6

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

 Scratch/permanent or by function-based characteristics such as

 Network data,

 Trip matrices

The filename conventions should try to reflect these differences.

File names differ considerably between different computers and different

operating systems. SATURN follows standard DOS and WINDOWS conventions
whereby every file must have

 a “name” (or, more generally, a “pathname”, see 3.3.3 below)

 and an “extension” (with a maximum of 3 characters)

Typically the name indicates the network/matrix/etc., and the extension indicates
the process/program which has produced that particular file.

Thus a network “named” LIVNET might spawn a number of files with extensions
such as LPA denoting the Line Printer output from the Assignment, UFS indicating
the “Unformatted” output from the Simulation, etc. etc. The documentation
assumes the DOS/WINDOWS “dot” convention, e.g. LIVNET.UFS.

3.3.2 Extensions

The following rules govern the standard or “default” files extensions:

All unformatted binary files have extensions beginning with UF. In particular:
UFN An unformatted file output (only) by SATNET
UFS An unformatted file produced by SATSIM or SATALL
UFA “ “ “ “ SATEASY
UFM An unformatted matrix file
UFP A file containing “pija” factors as passed from SATPIJA to SATME2
UFT An unformatted file output by SATSUMA; see 17.5
UFX Scratch files.
UFC An unformatted file of costs used to re construct routes see 15.23.
“Text” files used as control or data files:
DAT All basic data or control files created by the user, e.g., using a text editor such
as Notepad or Wordpad (not MS Word) and used as input
KP A “card punch” file output by a program.
HLP Help files used by all interactive programs.
LOG A file containing a list of all terminal input commands from the run of an
interactive program; see 14.5.1.

standard edit program such as Notepad), whereas a binary file is passed between programs and is
only “intelligible” to a program. Thus if you try to “type” a binary file on the screen you will get - at
best - gobbledygook and - at worst - a “stalled” computer. You have been warned !

5101396 / May 11 3-7

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

KEY A “dummy” terminal file used to run an interactive program; see 14.5.1.
VDU A “dummy” terminal output file from an interactive program; see 14.5.1.
XY A supplementary node co
GIS A supplementary “Geographical Data” file; see 5.7.
MCC A supplementary file containing link counts.
BUS A supplementary file containing bus route data.
DBD A “Data Base Dump” file output/input by SATDB.

Conventionally, all the above files might be assigned the extension “.txt”, e.g. by a
word processor such as Microsoft Word.

All output line printer files have extensions “LP-” with the third letter/number
indicating the program that produced it as follows:
LPN SATNET
LPA SATEASY
LPS SATSIM
LPT SATALL
LPL SATLOOK
LPE SATED
LPP P1X
LPD SATDB
LPM SATME2
LPU SATU2
LPF SATOFF
LPC SATCH
LPX MX

The “standard” extensions above are used by the programs themselves to create
new files and/or to suggest extensions to the user on input. They are also
frequently used as a convenient shorthand to refer to files; e.g., the “LPN file”
would imply the line printer file produced by SATNET, a “DAT” file implies a
control file prepared by the user, etc. “UF files” refer in general to all UF*
unformatted files, while UFA/S refers to either UFA or UFS which may, in a
number of circumstances, be used interchangeably.

In addition there are a number of “system” files within the Suite itself which should
in some sense be inaccessible to users (i.e., they should not be accidentally
erased!). These will have conventional extensions as well as indicated below:

 FORTRAN source code files

 Executable code files (.EXE files)

 Procedures to run programs (.BAT files)

 Basic data files (.DAT files)

5101396 / May 11 3-8

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

 Help files (Extension .HLP)

 Salford library files (Extension .DLL)

N.B. The extensions .DAT and .HLP are SATURN standards whereas extensions
such as .EXE and .BAT above are DOS standards; other operating systems will
therefore have their standard extensions for such files.

3.3.3 Pathnames

Every file has a full “pathname” associated with it. Thus the file net3.ufs on your
working directory may have the full name c:\SATURN\NEWTOWN\2005\net3.ufs.
In certain circumstances net3.ufs (or even net3 if SATURN expects the extension
.ufs) may be enough to identify it, in other circumstances the full pathname may
be required.

SATURN binary files store both filenames and pathnames and use both when
trying to open files.

Path/filenames may contain up to 256 characters. (Versions prior to 10.1 were

limited to 96.)

3.4 32-Bit SATURN Versions

PC versions of SATURN prior to 10.1 (9.5 and earlier) were all compiled as 16-bit
code which, in practical terms, meant that they needed to be run under MS-DOS
as opposed to “pure” MS Windows. Version 10.1 catered for both. By contrast
versions 10.2 and beyond are specifically designed for 32-bit applications and
may be run using the SATWIN Windows front-end program. Note, however that
the 32-bit versions may also be run under Command Prompt which may be
accessed through SATWIN.

The following two sections describe the two alternative methods in somewhat
general terms.

3.5 Running Programs Under DOS (or Command Prompt)

In order to run one program - or a linked set of programs - it is necessary for the
user to specify: (a) the program(s) and (b) the files to be used. Thus for every
individual program in the Suite there is a corresponding “procedure file” (e.g., a
.BAT file under DOS) with the same “name” as the program; e.g., SATLOOK.BAT.
Thus in order to run, say SATLOOK, the user types in “SATLOOK” followed by a
series of file names and/or key words. For example typing:

SATLOOK LIVNET

5101396 / May 11 3-9

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

would run the program SATLOOK in order to analyse data for a “LIVNET”
network. To look at another network you would type:

SATLOOK EVERTON

The precise file to be analysed in the first case would be LIVNET.UFS, the
extension .UFS being implied. Output files are automatically created as
necessary with standard extensions as well. Thus the line printer output file
above would be LIVNET.LPL.

Note that simply typing the name of the program prints a brief “help file” to the
screen with instructions how to use that procedure:

In addition to .bat files that run individual programs there is also a set of “special
purpose” bat files (termed “batch procedures”, section 14.7) that perform specific
“one-off” functions. For example, the procedure SATCOST (15.27.4) uses the
program SATLOOK in order to produce a matrix of o-d costs. Similarly there are a
number of procedures based on the matrix manipulation program MX which, e.g.,
add two matrices together or factor a single matrix; see 10.20.

The big advantage of batch procedures is that they allow the user to run certain
standard “bread and butter” operations based on programs which are normally run
interactively but in a totally off-line or batch mode. In addition the user may then
create their own “super-bat” files which string together a sequence of calls to
individual .bat files in order to run a series of operations off-line (e.g., overnight).

Full instructions for running both styles of batch procedures are found in Section
14.

3.6 Running Programs under WINDOWS: SATWIN

This section shows you how to install SATURN and, briefly, how to run the latest
version. In doing so, we introduce you to a new version of SATWIN, SATURN
Ten‟s User-friendly Interface.

SATURN 10.9 is the current release version and is the successor to all the
previous versions of SATURN. A much earlier release, 10.2, introduced the
(then) fairly revolutionary change to a 32-bit rather than a 16-bit suite; 10.3 to date
are straightforward evolutions in this respect. As a consequence, the latest
release builds on a strong existing base whilst offering significant enhancements;
see. the latest sub-section in Appendix D of the documentation for a full list of
changes.

3.6.1 The SATURN Install Procedures

As for earlier versions of SATURN Ten, a Windows style SETUP utility is supplied.
To install SATURN 10.7 load the CD and, if the CD does not auto-run the install
process, double-click on:

5101396 / May 11 3-10

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Setup.exe

You will be led through a series of install screens which will allow you either to
accept the standard folder setup or to select your own.

With the release of SATURN v10.9, the installation may also be undertaken using
the Microsoft Installer (ie .MSI) package – these are available on request

From SATURN 10.2 onwards, users may, if they prefer, install SATWIN under
\Program files\ rather than the default \satwin folder. This, and indeed installation
under any folder containing a space, was previously prohibited but this limitation
has now been corrected.

However, once a suitable home has been chosen, program executables and
assorted DLLs, bat and control files, help and PDF-based documentation will be
automatically installed on your hard disk. You can then run SATURN as
previously from a Command prompt (remembering to set the Path to the directory
chosen for EXE and BAT file, \SATWIN\XEXES\ by default and check preferences
in SAT10KEY.DAT), or to use SATWIN which can be accessed through the
desktop icon.

If you have a previous version of SATURN, this will be overwritten during the
installation process. However, users can keep previous versions of SATURN
(before installing the current version) by renaming the existing XEXES folder. This
could be renamed to say “XEXES 10.7.10” (where 10.7.10 indicates the version
number).

If multiple versions of SATURN are detected when SATWIN is launched, the

dialog box below will appear, enabling you to select the version to use in the
current session.

5101396 / May 11 3-11

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.2 SATWIN

SATWIN is a front end for SATURN with six principle functions:

 to run a single Module, e.g., SATNET or P1X

 to set up a Batch run (to run modules successively)

 to run from a command line

 to run the test network

 to enable other standard Windows “tools” to be invoked

 to interactively access the Manual

These are selected from the main screen as below

The File menu is used to exit from SATWIN, for consistency with other Windows-
based software.

5101396 / May 11 3-12

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.2.1.1 SATWIN and Windows NT/2000/XP/Vista/7

If SATWIN is launched on a Windows NT (or later) when logged in as a user

without write-access to the drive where SATWIN is installed, the following error
could occur:

Run-time error 75 - Path/File access error

SATWIN normally creates and updates some ASCII text files during use;
consequently, it needs to be able to write to the drive where it is installed as well
as to the drive (if different) where "Working Folders" are located.

To address this problem the user should ask the system administrator to provide
write-access to the folder where SATWIN is installed as well as "Working Folders"
or log in as administrator.

3.6.2.2 Setting Folders

The Settings menu is used to select four standard folders where SATURN files
are stored

 the “working folder”,

 the “Program folder” where the .exe and .bat files etc. are stored,

 the “Control Files folder” (e.g. SATALL0.DAT etc),

 the “Manual folder”.

These are set automatically to correspond to the folders set during installation,
either by default or by explicit choice. Any later changes made are “remembered”
by SATWIN the next time you use it.

The latter three folders probably never need to be re-set once they have been
initialised for your installation. However the first “working” folder, which defines
the folder from where, by default, current data files are selected, tends to be
changed frequently as users shift between different projects. The current working
folder is displayed on the main SATWIN screen at all times.

3.6.2.3 Running a Single Module

From the main screen (see below), select Module Run using the mouse, followed
by “SATURN” and the selection of a specific module:

5101396 / May 11 3-13

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

A new module-specific template will be displayed allowing you to select the

necessary files. For example, if you select the module SATURN (which runs
SATNET followed by SATALL), the template allows you the basic selection of a
network .dat file and a matrix .ufm file as below plus, optionally, UPDATE and/or
PASSQ files.

5101396 / May 11 3-14

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Once files have been selected, click on Run and the module executes. Upon
completion you have the option to view the output LP file or to run further
modules.

You can also run modules directly from the Events log in one of three ways:

1) Click and existing command in the Events log to highlight it, then press the
F2 or Insert key to enter Edit mode, then type a new command or edit the
existing command and press the ENTER key to stop editing. (Alternatively,
click the command to highlight it, then click it again to enter Edit mode.
Note that this is not the same as double-click, there is a pause between
clicks).

2) Click the entry <Click Here To Select, Then Press F2 Key or Click
Again To Enter A New Command> in the Events Log to highlight it, then
press the F2 or Insert key to enter Edit mode, then type a new command
and press the ENTER key to stop editing. Alternative is similar to option 1
above.

3) Drag a batch file (from the Desktop, Windows Explorer, etc.) and drop it on
the Events log.

4) After entering a command you can Double-click it, click the Run Items(s)
button, or press the F4 key to run it

5101396 / May 11 3-15

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Note: the Events Log now indicates the Program Folder (see below, fourth
column) containing the version of SATURN used to execute a command (in
addition to the Working Folder where data files reside, see below third
column).

The image above for examples shows the following:

 The current “Working Folder” is D:\TEMP\SATURN MULTI-CORE\DMB312

 The first command SATNET CNET uses CNET data file from “Working
Folder” C:\SATWIN\TEST\CORDONSRN and SATNET v10.8.22 from
“Program Folder” C:\SATWIN\XEXES 10.8.22.

 The second command SATURN LIV10 LIVTRIPS uses data files from
“Working Folder” C:\SATWIN\TEST and SATURN (i.e. SATNET/SATALL
v10.8.22) from “Program Folder” C:\SATWIN\XEXES 10.8.22.

 The third command SATURN LIV10 LIVTRIPS uses data files from “Working
Folder” C:\SATWIN\TEST and SATURN (i.e. SATNET/SATALL v10.9.10)
from “Program Folder” C:\SATWIN\XEXES 10.9.10.

 The last entry in the Event Log indicate the current “Working Folder” (i.e.
D:\TEMP\SATURN MULTI-CORE\DMB312) and “Program Folder” (i.e.
C:\SATWIN\XEXES 10.8.22. This means that any commands issued within
SATWIN will use data files and SATURN modules from the respective folders.

You can change “Working Folder” and “Program Folder” at any time via the
Settings/Folders menu option.

3.6.2.4 Preparing a Batch Run

The “Batch Run” menu option may be used to prepare, edit and execute a number
of modules in sequence. This is done using the ‟Batch Run Setup‟ Dialog box as
shown below.

5101396 / May 11 3-16

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Double-clicking a SATURN module category from the displayed list will reveal the
available modules, a subsequent click to the module will select it. The “Set Module
Parameters” and “Module Help” buttons will also be enabled.

Resting the mouse button inside the box with the list of SATURN modules will
provide a one line description of the selected module.

Clicking the “Set Module Parameters” button will set the required parameters for
the selected module with the “Module Help” button provide additional supporting
information on that module.

After setting the module parameters, the command line will be displayed in the
editable batch file contents box. Further modules may be manually added to the
batch file contents text box.

5101396 / May 11 3-17

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

The „Run‟ button will start the the module(s) in the batch file contents text box
whilst the „Save‟ button will save the contents to a batch file for later re-use. The
„Edit‟ button will open the batch file in Notepad and the „Clear‟ button to remove
information from the text box.

Previously created batch files may also be used by selecting via the “Select Other
Batch Files” button.

Note: instead of using the Batch Run menu, you may also drag batch files or the
SATURN executables (from Windows Explorer) and drop them into the Events log
to run them automatically.

3.6.2.5 Running from Command Line

This is perhaps the nearest equivalent to running SATURN from a „traditional‟

DOS-type command prompt.

SATURN commands can be typed directly into the command line box or individual
modules and input files may be selected from pull down menus using the Select
Command and Select Parameter buttons respectively. This approach can be used
for interactive runs of modules e.g. MX I

To get help on supported DOS commands, press the F2 key on the keyboard.
Help on a selected SATURN command is automatically displayed on a side box to
the right of the Command Line dialog box. Using the Hide button will conceal the
help box. Pressing the F2 key after selecting a command will display the
command‟s help information in a separate Help dialog box. You can press the
up/down arrow keys on the keyboard to step through previous commands if the
cursor is on the command entry box or use the „Previous Commands‟ button to
display the list of previously used commands.

3.6.2.6 Running the Test Network

Possibly the first thing you would want to do on loading SATURN and SATWIN
would be to run the test network.

Choosing a test network from the Test Network menu presents you with the Test
Run Template below corresponding to the network.

5101396 / May 11 3-18

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Test Network 1 will run MXM1 to build trip matrix HAT, followed by SATNET,
SATALL and P1X for network HEADE, leaving you in P1X interactive mode.
Upon exit from P1X, the following screen will allow you to view any of the LP files
generated

Test Network 2 will run SATNET, SATALL and P1X for network N10, leaving you
in P1X interactive mode, which in this example will show a background bitmap of
the network.

3.6.2.7 Other Tools

SATWIN also allows access to Notepad editor or a command line prompt through
the toolbar as below.

If the full or demo version of DRACULA is included with SATURN, the menu
option DRACWIN will appear on the SATWIN menu bar (see above). This
provides access to DRACULA through its front-end program DRACWIN.

5101396 / May 11 3-19

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.3 Other Features OF SATWIN

3.6.3.1 Quick Access to Modules

SATURN modules (or other modules for PT-SATURN and DRACULA if installed)
may be accessed by right-clicking on the event log.

3.6.3.2 Selective Deletion of Event Log Runs

When several runs are displayed on the event log, you can delete selected runs.
The options are available to remove all commands in the log or a set of cursor
selected commands. Individual commands can also be deselected as above.

3.6.3.3 Batch Runs from modules selected in Event Log

You can also select modules or commands from the event log and run them in
batch mode. Simply hold down the CTRL key, click the modules you wish to run in
batch mode, then click Run Item(s) or press the F4 key. You will have the option
to save your selection as a batch file before the run proceeds. This provides the
opportunity to be able to re-run the batch file again later if necessary.

3.6.3.4 Changing Working Folder

Double-click the Working Folder display bar to change folders. You can also type
in or copy and paste a folder in the folder display bar.

5101396 / May 11 3-20

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.3.5 Editor of choice

SATWIN uses NotePad or WordPad to view LP files by default. You may specify a
different default editor by clicking Set Default Editor from Settings menu. The
default editor is used automatically when viewing LP files through SATWIN. The
editor can be accessed through the Tools menu

3.6.3.6 Saturn Manual

An Index to and Individual Chapters from the SATURN User Guide can also be
accessed directly from SATWIN.

3.6.3.7 An Integrated Front End

SATWIN from version 10.3 of SATURN has also been designed to perform as an
integrated front-end for a range of transport planning software including not only
SATURN, but also DRACULA and PT-SATURN. The DRACULA Demonstration
is now integrated with the release of SATURN and access to the full program will
be through SATWIN. Similarly, PT-SATURN modules will execute in the same
way as those from SATURN.

3.6.3.8 SATURN Version Information

SATURN version information can be found on the bottom left of SATWIN window
as illustrated below.

5101396 / May 11 3-21

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Detailed SATURN version information (shown in the dialog box below) is available
through “SATURN Version Info” from the Help menu or by double-clicking the
version information area indicated above.

5101396 / May 11 3-22

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

If the user wishes to Detailed SATURN version information (shown in the dialog
box below) is available through “SATURN Version Info” from the Help menu or by
double-clicking the version information area indicated above.

If “Version Unknown” appears in the selection box, SATWIN was unable to identify
the specific version (eg a version of SATURN previously installed under the
XEXES directory).

The reference to the “SATURN Version Unknown” may be removed by the user
by:

 Determining the SATURN version and level in use. This may be readily
achieved by viewing any output Line Printer file using the executables – the
version and level in use will be reported at the top of the file (eg Version
„10.5.12‟ and Level „N3‟); and

 Creating a new text file called “SATURN.VER”, in the same directory as the
executables, containing at least one line of text that says “SATURN <version>
Level <level>” – for example “SATURN v10.5.12 Level N3”

5101396 / May 11 3-23

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.3.9 Using Other Programs from SATURN DOS Command Shell

Access to other non-SATURN (user) programs from the SATURN DOS Command
Shell is possible by specifying the full paths containing the user programs via
“SATURN DOS Command Shell Paths” from the Settings menu.

This will bring up the dialog box below. You can add paths containing other
programs you wish to have access to in the “Paths Containing User Programs”
text box by copy and paste or selecting a path through “Add Path” button.

5101396 / May 11 3-24

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.4 Recent Event Log Commands

You can access the previous 15 commands issued on the Events Log via the File
menu.

The list can be cleared via the “Settings/Clear Recent Command List” menu
option

5101396 / May 11 3-25

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.5 Save Events Log Commands for Later Use

Select the commands you wish to save from the Events Log, then click “Save
Item(s)” button on the Toolbar or “Save EventLog” from the File menu. The
commands are saved to a file you specify with the file extension .CMD. If you click
“Save Item(s)” without selecting a command, all the commands currently on the
Events Log will be saved.

To use previously saved commands, load an Events Log file via “File/Open
Eventlog File” menu option or drag and drop the file onto the Events Log.

3.6.6 SATURN File Associations

SATURN data files can be associated to SATURN modules including a description

of each file type when viewed in Windows Explorer via “Settings/SATURN File
Association” menu option. When active, a tick appears next to the menu item. You
can deactivate the association by clicking the menu option.

Screen shot of a “Working Folder” C:\SATWIN\TEST in Windows Explorer with no

file association

5101396 / May 11 3-26

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

Screen shot of a “Working Folder” C:\SATWIN\TEST in Windows Explorer with

SATURN file association.

5101396 / May 11 3-27

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

LIV10L.UFS for example is described as “SATURN Loaded network binary file”

and is associated with P1X as indicated by icon. Unlike the description of UFS file
in screen shot without association.

When file association is active, double-clicking on a UFS or UFM file for example
will automatically open the file with P1X and MX respectively.

5101396 / May 11 3-28

10_09_24_Section 3.doc
SATURN MANUAL (V10.9)

The Basic SATURN Model

3.6.7 Version Control

JOB NUMBER: 5101396 DOCUMENT REF: Section 3.doc

Revision Purpose / Description

Originated Checked Reviewed Authorised Date

1 Re-formatted (Final to DVV) TF / BG NS IW IW 06/05/06

3 Upgrade to V2 Templates IW 22/06/06

3.1 Update Figure 3.1/2 IW 13/07/06

3.2 Web release – Sept 06 DVV NP IW IW 08/09/06

3.3 Web release – Jan 07 DVV NP IW IW 04/01/07

3.4 SATURN v10.7 Release DVV NP IW IW 12/03/07

3.5 Web release – Jan 07 DVV NP IW IW 04/01/07

3.6 SATURN v10.8 Release DVV NP IW IW 31/03/08

3.7 Web release – Jul 08 DVV NP IW IW 07/07/08

3.8 Web release – Dec 08 DVV NP IW IW 12/12/08

3.8.21 Web release – Feb 09 DVV NP IW IW 16/02/09

3.8.22 Web release – Jun 09 DVV NP IW IW 16/06/09

10.9.10 SATURN v10.9 Release DVV DG IW IW 04/09/09

10.9.12 SATURN v10.9 Release (Full) DVV DG IW IW 27/10/09

10.9.17 Web release – Jun 10 DVV NP IW IW 22/06/10

10.9.22 Web release – Dec 10 DVV AG IW IW 06/12/10

10.9.24 SATURN v10.9 Release (Full) DVV AG IW IW 06/05/11

5101396 / May 11 3-29

10_09_24_Section 3.doc