- complete the demand schedule currently in memory (as part of the plant model); or

Transcription

1 page G7 - complete the demand schedule currently in memory (as part of the plant model); or get a different demand schedule from the.disk. In this case, the demand schedule from the disk will replace the one currently in memory. If you request a demand schedule from the disk, you will first be given a list of what scnedules are stored on disk. G.3.2 Saving the Input Data on Disk Plant Model Once you are satisfied with the pianl model, you irruct save it in a 'plant file' on the disk (step E). The file must have a name (8 characters max - see the DOS Manual if you are not sure what constitutes a legal file name). If you do not save the plant model on disk, you will not be able to optimise it later. Market-Demand Schedule Note that when you save the current plant-model on disk (step E), the current demand-schedule, which is part of the plant model, is automatically saved as part of the plant-model file. However, in order that the plant model can be optimised, it is also necessary to save the current d e m a n d - B c h e d u l e, separately, in a 'schedule file' on disk (step F). The file must have a name (8 characters max). G.3.3 Return to MAIN MENU Once you have saved a plant model and a dfmand-schedule on disk, you can return (step G) to the MAIN MENU to continue the program. Of course, you can choose to return to the MAIM MENU at any stage before this.

2 page HI H SOFTWARE The following files are contained on the- PROGRAM diskette: CONFIG.SYS ANSI.SYS These two files are automatically read by DOS whenever the PC starts up. The listing of CONFIG.SYS is: DEVICE=ANSI.SYS BREAK=ON BUFFERS=20 KiLKS-iiO These two files must be read on power up if Apollo is to function properly. ASSIGN.COM MODE.COM Standard DOS programs required by Apollo. AUTOEXEC.SFT AUTOEXEC.HPD AUTOEXEC.BAT AUTOEXEC.BAT is used to automatically start Apollo on power up. Tht. #.BAT program i3 identical to the *.SFT program and is for starting up with a two diskette system. Its listing is KEYBUK MODE 80 APOLLO

3 pa.^e H2 When setting up Apollo to run on a disk system, the *.BAT file is modified to be identical to the *.HRD file. The *.HRD file listing ir, KEYBUK MODE 80 C: CD \ CD AGMODEL APOLLO APOLLO.SFT APOLLO.HRD APOLLO.BAT AP0LL0.BAT is a batchfile which serves to control the execution of the main Apollo programs, HAUPTPRO and OPTIMA. Its listing (similar to *.HRL, is identical to *SFT: ASSIGN ASSIGN B=C ECHO OFF :LOOP CLS IF EXIST MATRIX.MAT DEL MATRIX.MAT IF EXIST STOP.STP DEL STOP.STP HAUPTPRO IF EXIST MATRIX.MAT OPTIMA IF NOT EXIST STOP.STP GOTO L<X>P ECHO ON ASSIGN REM You are now outside the program. REM To continue, enter APOLLO. (only APOLLO.HRD) (only APOLLO.HRD) (only APOLLO.HRD) * files on the original PROGRAM diskette are configured for a dual-diskette system: when Apollo operates, all plant model and demand schedule data files are directed to drive B:. However, when using a fixed disk, it is preferable that these data files are directed to the fixed disk (C:).

4 page H3 To accommodate this, the file APOLLO.BAT has to be reconfigured. This is done automatically when the contents of the original PROGRAM diskette are initially copied to the fixed disk using the H\RDDI3K.BAT driver program: the contents of APOLLO.BAT are, at the same time, replaced by the contents of APOLLO.HRP. HARDDISK.BAT HARODISK.BAT creates a new directory called AGMODEL on the fixed disk and copies the contents' of the PROGRAM diskette to this directory. HARDDISK.BAT then modifies some of the files on the AGMODEL directory to configure Apollo for fixed-disk operation: AUTOEXEC.BAT is modified to be the same as AUTOEXEC.HRD and APOLLO.BAT is modified to be the same as APOLLO.HRD. Its listing is: C: CD \ MD AGMODEL CD AGMODEL COPY A:*.* COPY AUTOEXEC.HRD *.BAT COPY APOLLO.HRD *.BAT HAUPTPRO.EXE This is the main program. OPTIMA.EXE This is the program that carries out the simplex iterations.

5 page H4 STOP.STP This is a 'dummy' file used by APOLLO.BAT to signal termination. MAINMENU.MAS PLNTMENU.MAS SiLECTFI.MAS PARAMETR.MAS CRUSHERS.MAS SCREENS.MAS DEMANDS.MAS These are data files which contain the 'Masks' and menus that appear on the screen during program cxccution. Intarmediate data files created during execution of the Apollo program: FLOWFILE.FIL A list of flows (variables) generated for a model. MODEL.FIL A complete list of the nodes (equations), flow? (variables) and coefficients making up the tableau of equations to be solved by the OPTIMA elgorithm. This file can be large: it is only generated if the first character of the plant title in Mask 1 is a "$" symbol. MATRIX.MA^ The tableau of linear equations used by the simplex algorithm OPTIMA. PROTOCOL.LST Contains the iterations of the simplex algorithm, detailing variables entering and leaving the basis.

6 page H5 DIAGNOSE.LST Containing error diagnostics. RESFILE.RES The solution of the most recent optimisation run. EXAMPLE.PLT EXAMPLE.SCD These are data files of an example plant-model and a corresponding market-demand schedule.

7 page J USEFUL DOS OPERATIONS What follows ire a few examples of some of the operations that can be pc formed using DOS (Disk Operating System). For more details, the reader is referred to the DOS manual that is supplied with the IBM PC/XT. Note that a file or a diskette is refarred to by a filename of up to 8 characters and an extension FILENAME.EXT of up to 3 characters, for example: DIR A: List all the files on the diskette in drive A on the screen DIR A:/P List all the files in drive A. The /P facility causes a pause when the screen gets full (useful when there is a long list of files) DIR B :*.PLT List all files in drive B which have the extension.plt DEL A:FILENAME.EXT Delete the file called FILENAME.EXT in drive A DEL B-EIK*.* Delete all files which have a filename starting with EIK in drive B DEL A:*.* Delete all files in drive A. thio command cautiously! Use REN B :EXAMPLE.PLT TEST.PLT Rename the file called EXAMPLE.PLT in drive B. New name is TEST.PLT

8 page COPY A :FILENAME.EXT B: Copy the file called FILENAME.EXT from the diskette in drive A to the diskette in drive B COPY A: *P1.T B: Copy all files with the extension.plt in drive A to drive B COPY B:*.* A. Copy all filer: in drive B to drive A The following commands refer specifically to a fixed-ui»k system (IBM XT). Note that the fixed disk is known as drive C and that the diskette dri/e serves as both drive A and drive B. Note also that the fixed dink is organised into a series of "directories" which are not unlike a series of filing cabinets in an office The first directory is known as the 'root iirectory', referred to by the symbol "\": it contains some files, and the 'keys to get into the other directories. called AGMODEL. The Apollo files are kept in a directory C>CD Determine which directory you are in C>CD \ Get into the root directory C>CD \AGMODEL Get into the AGMODEL directory C>DIR C:\AGMODELN*.PLT List all files with the extension.plt in the AGMODFL directory (if you are already in the AGMODEL directory you only need type DIR *.PLT) O C O P Y C:\AGMODEL\EIK*.* A: Copy all files which have a file name starting with EIK from the AGMODEL directory on drive C to drive A. (If you are already in the AGMODEL directory, you only need type COPY EIK*.* A:)

9

10 Author Hayden John Samuel Name of thesis The Modelling And Optimisation Of Aggregate Plants, And The Use Of The Apollo Computer Program PUBLISHER: University of the Witwatersrand, Johannesburg 2013 LEGAL NOTICES: Copyright Notice: All materials on the University of the Witwatersrand, Johannesburg Library website are protected by South African copyright law and may not be distributed, transmitted, displayed, or otherwise published in any format, without the prior written permission of the copyright owner. Disclaimer and Terms of Use: Provided that you maintain all copyright and other notices contained therein, you may download material (one machine readable copy and one print copy per page) for your personal and/or educational non-commercial use only. The University of the Witwatersrand, Johannesburg, is not responsible for any errors or omissions and excludes any and all liability for any errors in or omissions from the information on the Library website.