This Appendix describes how to install and run the UCLES data acquisition software at your home institution. The software is supplied as a backup saveset that occupies approximately 3400 blocks (the ECHWIND program occupies about 900 blocks of this). The saveset should be put into a single directory and the logical name UCLES_DIR should point to it (it is probably best to make this a job logical name defined in the local Starlink login procedure). You should also arrange for symbols UCLESSTART and UCLES to execute command files of the same name in UCLES_DIR.
If you want to allow ECHWIND to be run by itself, then you only need the files BALMER.DAT, ECHWIND.COM, ECHWIND.EXE and ECHWIND.IFC. You should arrange for the symbol ECHWINDSTART to execute ECHWIND.COM. You may need to edit ECHWIND.COM to change the names of the image display devices (ECHWIND uses an early version of IDI for its image display; the necessary changes should be obvious).
No abnormal quotas should be required in order to run ECHWIND. However, to run the full system quite a lot of quotas are needed and you may choose to create a username specifically for running the UCLES software. The quotas given to the UCLES username at the AAT are listed below:
Maxjobs: 0 Fillm: 40 Bytlm: 40000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 18 JTquota: 10000
Prclm: 10 DIOlm: 18 WSdef: 400
Prio: 4 ASTlm: 150 WSquo: 800
Queprio: 0 TQElm: 150 WSextent: 1024
CPU: (none) Enqlm: 30 Pgflquo: 50000
The important ones are Prclm (number of sub-processes), Fillm (number of open files), ASTlm (number of outstanding ASTs), TQElm (number of timer queue entries), Bytlm (buffered byte limit) and JTquota (job logical name table quota).
Once the system is installed as described above, it can be run exactly as
described in Section 
and will automatically come
up in simulation mode. The initial state of the spectrograph will be arbitrary,
but all commands will work as expected and timing will be realistic.