14.02.2013 Views

Thesis - Leigh Moody.pdf - Bad Request - Cranfield University

Thesis - Leigh Moody.pdf - Bad Request - Cranfield University

Thesis - Leigh Moody.pdf - Bad Request - Cranfield University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 8 / Simulation<br />

_ _<br />

8.5.1 Global Common Block Consistency Checking<br />

Stand-alone software has been developed to check the GCB code segment.<br />

The software checks for consistency, multiple mappings to a single common<br />

block variable, multiple use of common block locations, and text alignment.<br />

The latter is important as the text is read and decomposed by the simulation<br />

for automated printing, graphics, and windows interface presentation, where<br />

field widths are critical. The program is stored in CMS group [SUPPORT]<br />

and comprises two source modules and a DEC DCL command file:<br />

COMMON_CHECKER.FOR<br />

CB_SORT.FOR<br />

COMMON_CHECKER.COM<br />

The command file builds an executable image directly from the CMS<br />

library, assigns the common block file to input channel 10, runs the image,<br />

and deletes both the image and all files used to build the program. Three<br />

ASCII data files are produced:<br />

FOR016.DAT<br />

A data file produced in response to variables failing the tests.<br />

FOR017.DAT<br />

List of variable names, units, and scaling factors ordered by their position in<br />

the GCB real and integer vectors (their ID number).<br />

ORDERED_COMMON_BLOCK.DAT<br />

List of variable names, location, units and definition ordered alphabetically.<br />

Similar consistency checks are carried out during simulation initialisation.<br />

If errors are detected at this stage the program is terminated by setting<br />

ISTOP to 1, with a diagnostic message written to the Data Logging file<br />

described later.<br />

8.6 Simulation Infrastructure Control<br />

SIMULATOR controls the program infrastructure invoking DF_CONTROL<br />

that in turn controls the loading of pre-set default data, as shown in Figure<br />

8-6. The stored information is sufficient to run the program in conjunction<br />

with control data provided by the user. The data is loaded ignoring later<br />

restrictions imposed on program functionality by the user, and includes:<br />

• I/O data channel identifiers<br />

• Threshold for comparing real values<br />

• Integration order set to 2, and the integration state range [1(1)28]<br />

• Initial value of in-run real and integer common block change indices<br />

• Number of lines per page to the Data Logging file<br />

• Commonly used constants and unit conversions<br />

8-9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!