TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will...

25
SALT Operational Requirements Doc No. SALT1000AS0040 Issue B 1 APPROVAL SHEET TITLE : SALT Operational Requirements DOCUMENT NUMBER : 1000AS0040 ISSUE: B SYNOPSIS : This document describes the operational requirements for SALT, primarily regarding their impact on the TCS. It defines the tasks of the SALT Operator (SO), SALT Astronomer (SA) and Principle Investigator (PI) during operation. KEYWORDS : Telescope Control System, Integrated control system, Telescope Software, Telescope Operation PREPARED BY : Gerhard Swart APPROVED : David Buckley SALT PROJECT SCIENTIST Kobus Meiring SALT PROJECT MANAGER DATE : February 2001

Transcript of TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will...

Page 1: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

1

APPROVAL SHEET

TITLE : SALT Operational Requirements

DOCUMENT NUMBER : 1000AS0040 ISSUE: B

SYNOPSIS : This document describes the operational requirements forSALT, primarily regarding their impact on the TCS. It definesthe tasks of the SALT Operator (SO), SALT Astronomer(SA) and Principle Investigator (PI) during operation.

KEYWORDS : Telescope Control System, Integrated control system,Telescope Software, Telescope Operation

PREPARED BY : Gerhard Swart

APPROVED :David BuckleySALT PROJECT SCIENTIST

Kobus MeiringSALT PROJECT MANAGER

DATE : February 2001

Page 2: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

2

This issue is only valid when the above signatures are present.

Page 3: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

3

ACRONYMS AND ABBREVIATIONS

arcsec Seconds of arcBITE Built-in Test EquipmentCCAS Centre-of-Curvature Alignment SensorCCD Charge-coupled Device (Camera)COTS Commercial off the shelfDec DeclinationEE(50) Image diameter containing 50% of Enclosed EnergyFoV Field-of-ViewFWHM Full Width Half MaximumHET Hobby-Eberly TelescopeHRS High-resolution SpectrographI/O Input/Output (Device)ICD Interface Control DossierIR InfraredLRS Low-resolution SpectrographMMI Man-Machine InterfaceMTBF Mean Time Between FailuresMTTR Mean Time to Repairnm nano-metreOEM Original Equipment ManufacturerPC Personal ComputerPFIS Prime Focus Imaging SpectrographPI Principal Investigator (Astronomer)RA Right AscensionRMS Root Mean SquareSA SALT AstronomerSAC Spherical Aberration CorrectorSALT Southern African Large TelescopeS/N Signal-to-Noise (Ratio)SO SALT OperatorSW SoftwareTAC Time Assignment CommitteeTBC To Be ConfirmedTBD To Be DeterminedTCS Telescope Control SystemUPS Uninterruptible Power SupplyUV Ultraviolet (light)“ Arc-second‘ Arc-minute

Page 4: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

4

DEFINITIONS

Acquisition time This is the length of time required to put the target at adesired position, within the offset pointing requirement,from end-of-slew, until start of the integration

Growth Path This includes concepts that have not been fully explored,and do not form part of the deliverable. However, theseconcepts have to form part of the decision makingprocess in reaching the Technical or Cost Baselines.

Target This is a point in the sky. If the target is not visible to theacquisition imager, then the target is defined as an offsetfrom a visible star that is within the focal plane field ofview.

Page 5: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

5

TABLE OF CONTENTS

1 Scope ..........................................................................................................71.1 Identification..................................................................................................................................71.2 Document overview.....................................................................................................................7

2 Referenced documents .............................................................................83 Customer Furnished Equipment and Responsibilities ..........................94 Functional Requirements........................................................................104.1 Functional definition...................................................................................................................104.1.1 Operational Concept.................................................................................................................10

4.1.1.1 Application for Science Time................................................................................................104.1.1.2 Approval of observation.......................................................................................................104.1.1.3 Observation Scheduling .......................................................................................................104.1.1.4 Observation Preparation.......................................................................................................104.1.1.5 Object Acquisition.................................................................................................................104.1.1.6 Object Tracking.....................................................................................................................114.1.1.7 Science data acquisition.......................................................................................................114.1.1.8 Science Data management...................................................................................................114.1.1.9 Day-time tasks......................................................................................................................11

4.1.2 Functional Diagrams.................................................................................................................124.1.2.1 Timeline Diagram...................................................................................................................12

5 Roles and responsibilities ......................................................................145.1 SALT Operator.............................................................................................................................145.2 SALT Astronomer ......................................................................................................................14

6 Task Descriptions....................................................................................146.1 Principle Investigator TCS-related Tasks..............................................................................146.2 SALT Operator and Astronomer TCS-related Tasks ..........................................................166.3 Maintenance Staff TCS-related Tasks....................................................................................21

7 Control Room Layout ..............................................................................227.1 Common Work Area ..................................................................................................................227.2 SO Workstation ...........................................................................................................................227.3 SA Workstation ...........................................................................................................................237.4 Future Growth.............................................................................................................................23

Appendix A: Control Room Layout

Page 6: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

6

Modification History

Revision Changes Pages effectedA New Document All

Page 7: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

7

1 Scope

1.1 Identification

This document specifies the operational requirements for the Southern African Large Telescope(SALT) and provides an input into the design of the Telescope Control System (TCS).

SALT is a segmented mirror optical astronomical telescope of the tilted Arecibo type, based on thedesign of the HET. The telescope operation involves a combined effort by the Principle Investigator(PI), SALT Astronomer (SA) and SALT Operator (SO). This document identifies the TCS-related rolesof each of these people and those of the maintenance staff during normal operation. The TCS formsthe integrating node of the telescope and provides the Man-Machine Interface (MMI) to theseoperators.

This document has been written in a descriptive format using words such as “will”, “should” and“must” rather than “shall”. This has been done to show that an operational philosophy is beingconveyed and that the particular detailed requirements will be finalised during the developmentprocess. An MMI prototype will be used to facilitate this process.

1.2 Document overview

Section 3 of this document identifies operational requirements that are not addressed by the SALTproject, being either part of existing facilities or provided by partner institutions. Section 4 definesoverall functional requirements pertaining to the operation of the telescope, such as a timeline of theoperation. Sections 5 and 6 provide detailed task descriptions for the PI, SA, SO and maintenancestaff in a step-wise fashion and indicates the computer tools required to perform these tasks. Section7 defines the layout of the SALT control room.

Page 8: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

8

2 Referenced documents

Keck Visit Report dd. July 2000 GS, JS, KM, DBScience with SALT, DAH Buckley, March 1998SPIE proceedings (various)SALT Astronomer: Functions and Requirements, Draft Issue, DAHBuckley, 21 July 2000

SALT1000AS0007 SALT System SpecificationSALT1700AS0001 SALT TCS SpecificationSALT1000AS0013 SALT Electrical Interface Control DossierSALT1000AS0014 SALT Physical Interface Control DossierLWR95055 Hobby-Eberly Telescope Operations Requirements Document, L.W.

Ramsey, dd. 27/11/95, edited by D BuckleySALT DB000531 SALT Observatory Science Requirements, Issue 7.1, D.A.H. Buckley,

dd. 31 May 2000

Page 9: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

9

3 Customer Furnished Equipment and Responsibilities

Some of the requirements defined in this document place constraints on the Science Instruments whichare “Client Furnished Equipment” to the SALT project. Details of the interfaces and requirements willrecorded in the Interface Control Document, the TCS Specification and the specification for theappropriate Science Instrument.

Page 10: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

10

4 Functional Requirements

4.1 Functional definition

4.1.1 Operational Concept

4.1.1.1 APPLICATION FOR SCIENCE TIME

In order to use SALT, a PI has to complete an on-line application form(s) providing details of theobservation that is required. Software tools are used to determine the most suitable times toview the object using SALT and various other requirements, such as Instrument configuration,image quality (i.e. seeing), integration time, photometric conditions and moon phase. Specialinstructions to the Resident Astronomer are specified.

In addition, these tools will be used to estimate the exposure time required to achieve a specificS/N ratio in given conditions (e.g. seeing, transparency etc.).

4.1.1.2 APPROVAL OF OBSERVATION

Each Partner’s Time Assignment Committee (TAC) meets regularly to review the applications,define their priorities and then allocate a priority to those that are approved. Approvedobservations are entered into a queue which is serviced by SALT.

4.1.1.3 OBSERVATION SCHEDULING

The SALT Astronomer (SA) uses scheduling tools (which form part of the Telescope ControlSystem) to sort the observations into a likely sequence using the following criteria:• Object RA and DEC (visibility to SALT)• Observation priority• Percentage of PI institution’s allocated time already used• Moon phase• Anticipated observing conditions (e.g. weather and seeing)• Instrument configuration• Optimisation of telescope efficiency (minimum azimuth moves)The result is a schedule for a particular night, with back-up objects in the event of poorconditions.

4.1.1.4 OBSERVATION PREPARATION

Prior to observing (and possibly again, during observing), the telescope and instrument arechecked and calibrated/set-up to the planned observing. This includes the following:• Primary Mirror alignment• Tracker functional checks• Instrument calibration and checks• Opening of dome shutter• Opening/adjusting of louvers

4.1.1.5 OBJECT ACQUISITION

An observation starts by the SA selecting a particular object that is available in the observingwindows, from the night’s schedule on the SA workstation or enters the details of an“opportunity target”. An appropriate guide-star is selected automatically or from the observationplan. The selection is relayed to the SALT Operator workstation via the TCS server, where theSO activates the telescope acquisition function, which automatically rotates the structure to the

Page 11: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

11

optimal azimuth (if required) and the tracker to the correct X,Y,Z, tip, tilt and Rho position andpositions the guide probes at the appropriate positions.

4.1.1.6 OBJECT TRACKING

The tracker automatically starts tracking the objected selected in 4.1.1.5 at the sidereal rate (orprogrammed alternative trajectory), in an open-loop fashion. The SO selects the science objectby clicking on its image from the acquisition camera FoV, and it is automatically centred bymoving the Optical Payload. The SO also centres the guidance object in the guidance field byclicking on it’s image in the a guidance FoV which then adjusts the guidance probes accordingly. After this closed-loop tracking is performed, keeping the guidance object image at the desiredposition and orientation.

4.1.1.7 SCIENCE DATA ACQUISITION

While the telescope is tracking the object, the SA selects the desired instrument and the light isre-directed at that instrument and its associated guide probe. He ensures that the appropriateobject’s light is optimally entering the selected science instrument correctly and performs anyfine adjustments that may be required. If necessary, test exposures are performed where afterthe science data is acquired using the appropriate Instrument Computer and pipeline data-reduction performed. Previews of the data are automatically made available on a web server,for access by the PI during and after the observation (growth path).

Upon completion of a specific observation, the calibration and science data are stored and thenext object is acquired (step 4.1.1.5).

The appropriate institution’s account is updated according to the actual time used for theobservation.

4.1.1.8 SCIENCE DATA MANAGEMENT

Some time after the completion of an observation all the calibration and measurement data of aparticular observation are stored on an ftp server (Typically the next day). The PI downloadsthe data from the server using the internet.

4.1.1.9 DAY-TIME TASKS

Several parallel tasks are performed to facilitate the steps above:• At dawn the telescope is returned to its “day” state, during which maintenance is performed

and the telescope enclosure is air-conditioned.• The SALT day staff ensure that the Telescope temperature is controlled to the expected

night-time ambient temperature.• Routine maintenance is performed and reported problems addressed.• Calibration of the instruments may be performed• At twilight the SO prepares for the observation by allowing natural ventilation and checking

the telescope functions.

Page 12: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

12

4.1.2 Functional Diagrams

4.1.2.1 TIMELINE DIAGRAM

Figure 1 shows the flow events before, during and after a typical observation while Table 1presents a provisional timeline for the Acquisition of an object in more detail. The times shownexclude the time required for human interaction with the system.

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7Tracker Slew to destination

(120s)Open-loop tracking

of object andimplementation oftracking offsets

(within 60s).

Closed-loop

trackingof guideobject

Structure

Lift up(20s)

Rotate(130s)

Lower(30s)

Dome Rotate(180s)

PM Stop alignment maintenance Continuealignment

(15s)SO or SAactions

SelectObjectsfrom list(120s)

Setting to guidanceobject (360s)

Integratescienceobject

(1s to 1h)

Selectnext

objectfrom list

Table 1: Typical Steps and 90th percentile maximum times to Acquire and Observe an object

Page 13: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

13

Timeline for Telescope Operation

Date: 15/5/00Issue: A

Months before Week before

Day of observation

Sunset to Twilight

Twilight to Science twilight

Dawn to sunrise

Next day Next week Next month

Principal Investigator

Plan observation time window, RA

& dec , conditions, comlete rqd internet form

Time Assignment Committee

Review request and allocate priority

Scheduling SW

Provide planning tools and capture

request, show partner account

status

Change status of request if approved,

allocate initial viewing slot

Generate week's 1st

pass schedule

from database

What-if analysis on each scenario

Implement tonight's schedule

Resident Astronomer

View long term planning plus

detailed observation information

Plan this week's viewing

Review tonight's list, plan

scenario's, configure science

instrument(s)

Finish daily log

Check data transfer

InstrumentCollect science data and spool to data server

Calibrate Spool data to server

Telescope Operator and day-time staff

View long term planning and plan

maintenance

Plan this week's viewing

Control dome to predicted

temperature, perform system

maintenance

Finish daily log

Check data transfer

Telescope System

Open dome and ventilate,

perform system checks

Calibrate Telescope

System if rqd.

Rotate to object azimuth

Aquire viewing object and guide

stars

Observe objectrecord

performance stats

Close Dome Collate data and publish on server

Archive data

Operate acquisition and guidance, monitor system performance, monitor system faults, log problems

Calibrations, configuration changes and setting up filter wheels etc.

Retreive observation data

Science twighlight to Dawn

Repeat until night is over

Re-schedule according to actual events, perform what-if analysis as rqd. Perform accounting of science

time

Operate and calibrate Instrument, log science problems, evaluate sample data, re-schedule as required, communicate with PI

Figure 1: SALT System Timeline

Page 14: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

14

5 Roles and responsibilities

The responsibilities of the some of the SALT operational staff are summarised below (responsibilities ofother staff are to be determined later):

5.1 SALT Operator

The SO’s primary objective is to ensure that the telescope performs optimally (Image Quality, pointingand tracking). Secondly he must perform all the tasks required to acquire an object, position it onto theinstrument aperture (i.e. slit mask or fibres), keep it there and maintain adequate image quality. Toachieve this, the operator will have both day and night-time tasks (day tasks may possibly bedelegated to maintenance staff). Section 6.2 describes these tasks in further detail.

5.2 SALT Astronomer

The SA’s primary objective is to perform the science observation requested by the PI while optimisingthe use of the telescope by appropriate scheduling of observations. During this process the SA mustperform calibration observations (arcs, flats etc.), ensure adequate quality of the data and mustprovide this information to the PI. He must also maintain the Observation Planning/Scheduling toolsrequired by the PI. Section 6.2 provides further details in this regard.

6 Task Descriptions

This section identifies the TCS-related tasks to be executed by the SALT operational and maintenancepersonnel. The tasks have been described in the form of a detailed event sequence. The TCS-relatedtools identified are not intended to be a complete list but serve to prompt the designers in providing therequired functionality. Not all the tools and functions are required for First Light operation.

Although the tasks identified assume that the SO and SA are working in close co-operation in thecontrol room under the observing floor, it should be borne in mind that remote operation of SALT fromCape Town is a growth path that must be catered for, which means the SO and SA may be inseparate locations.

6.1 Principle Investigator TCS-related Tasks

Process Step Action Tools used1. Prior toObservationPHASE 1

Decide on object to be viewed Own tools

2. Check whether SALT can view the object SALT observation planning tool3. Check whether SALT’s instruments can do

the science required (Check adequateintegration time, S/N ratio, spatial, time andwavelength resolution)

SALT Instrument tool

4. Motivate scientific case for observation.5. Complete on-line application with motivation

and object details: Name, RA, Dec, Epoch,proper motion (e.g. orbit of comet).

SALT observation planning tool

6. Submit form to Partner TAC By hand, e-mail, mail asappropriate

Page 15: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

15

7. PHASE 2 Determine and specify possible observationdate and time ranges (taking into accountSALT fixed elevation, observation envelope,moon phase, object position etc)

SALT observation planning tool

8. Determine and specify SALT and instrumentconfiguration requirements (incl. Rqd. S/Nratio, integration times, resolution, filters,wavelength, image quality…)

SALT observation planning tool,SALT Instrument tool

9. Complete SALT application form containingdetails from 4, 5, 7 and 8 above.

10. Submit form to SALT electronically ifapproved

Own E-mail SW and/or SALTobservation planning tool

11. Receive e-mail confirmation that observationwas scheduled

Automatic function by server.

12. Check SALT on-line schedule to see whenobservation is planned

Own Web browser

13. DuringObservation

Monitor progress of observation andpossibly correspond with SA regardingspecific queries (by exception)

Own Web browser/ chatprogram

14. See sample data and/or pipe-line reducedsample data (future growth)

Own Web browser, SALT datadecompression tool.

15. AfterObservation

Receive e-mail notification that data isavailable

E-mail

16. Download data and Observation log/reportfrom SALT website

Own FTP s/w or browser

17. Complete assessment form for SALT qualitycontrol

SALT observation planning tool

Page 16: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

16

6.2 SALT Operator and Astronomer TCS-related Tasks

NOTES: Italics are used to indicate tasks that can be performed by either the SO or SA.

Salt Day/Night Operators onSO Workstation

Salt Astronomer on SA WorkstationProcess Step

From/to TCS and SALTsubsystems

From/to TCS and SALTsubsystems

From/to Instrumentcomputer(s)

1. Pre-twilightpreparation

Monitor weather forecastsand predicted temperature,audible and visible alarms

Check scheduledobservations and selectshort-list for this nightaccording to telescopeperformance, required,weather etc. Selectrequired instrument fromlist so TCS knows.

Check/changeInstrumentconfiguration, checkdisk space

Weather displayTemp prediction displayScheduling list/sorter, auto-sorterSALT configuration changer/monitorInstrument configuration changer/monitor

2. Monitor telescopetemperature and adjust A/Cset-points if required.

Conduct Instrumentcalibrations

Weather displayTemp prediction displayA/C control page

3. Twilightpreparation

Check that all equipment isokay to be powered up, notools still connected andpersonnel off telescope.Read instructions from daycrew.

Check instrument isclosed, connected and nopersonnel there.

CCTV, audioFailure report database (FRACAS)System and subsystem status displayInstrument status display

4. Power-up telescope andexercise Tracker and checkthat all is okay.

Power-up Instrumentand check all is okay

CCTV, audioSystem and subsystem status displayInstrument status display

5. Check outside environmentokay for Dome opening.

Perform calibration ofinstrument and set up.Save calibration data.

Weather displayInstrument calibration set-up, data savingCalibration source control/status display

6. Select “Open Telescope”.This will open dome andlouvers and turn off air-conditioning.

Telescope control display

7. Monitor telescopetemperatures, humidity,wind and adjust louvres asrequired.

Telescope status display, internalenvironment display (same as weatherpage??), ventilation control

8. Set up Operator log. Set up Astronomer log andenter configuration andcalibration details.

Operator and Astronomer logs anddisplays, with auto-entered fields.

9. Check that all personnel areout of telescope chamber,turn off lights

CCTV, audio, light control/status display

Page 17: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

17

Salt Day/Night Operators onSO Workstation

Salt Astronomer on SA WorkstationProcess Step

From/to TCS and SALTsubsystems

From/to TCS and SALTsubsystems

From/to Instrumentcomputer(s)

10. PrimaryMirrorAlignment(if rqd):

If required and dark enough,select “Align Primary Mirror– part 1” on TCS. This willdo the following:

• Open CCAS shutter• Turn ON CCAS

instrument• Rotate structure to

CCAS and allow it tosettle

• Move Tracker to oneside

The operator then aligns thefirst half of the PM Array andselects “finished part 1”.

PM alignment display incl. CCAS imagedisplay, alignment visualisation, PMcontrol/status display, CCAS status/controldisplay, shutter control/status display,structure status/control, trackerstatus/control

11. The system moves Trackerto other side

Tracker status/control,

12. Operator performsalignment activity part 2 andhits “finished part 2”.

Progress display, plus displays as above

13. Any related calibrations(e.g. Tracker sweep of PM)follow automatically

Calibration status/control display

14. Checks results and enterinto night log. Operator exitsPM alignment

Night log page with auto fields, PMalignment and visualisation display

15. Pointingcalibration(provisiononly,systemdesigned tonot requirethis)

Perform pointing calibrationby selecting a few pre-defined objects from a list.In each instance the systemautomatically lifts thestructure, rotates it to therequired azimuth, positionsthe tracker. Offsetcorrections areautomatically calculated andincorporated into thepointing model. Enter resultsinto night log.

Check instrument okayand gathering data

Tracker status/control, Payloadstatus/control, acquisition and guidanceimages and status/control, optical pathdisplay, image evaluation functions, starcatalogue, structure status/control,pointing status/control, night log page,calibration standards list.

16.Observationpreparation

Check Tracker focus, imagequality and seeing using anacquired object. Make anyadjustments that may berequired.

Tracker status/control, Payloadstatus/control, acquisition and guidanceimages and status/control, optical pathdisplay, image evaluation functions.

Page 18: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

18

Salt Day/Night Operators onSO Workstation

Salt Astronomer on SA WorkstationProcess Step

From/to TCS and SALTsubsystems

From/to TCS and SALTsubsystems

From/to Instrumentcomputer(s)

17. ObjectAcquisition

Open list of plannedobservation objects, selectthe first object. or type inRA&Dec and hit “acquireobject”. A star-finder chartmay be incorporated hereas an option. This selectsthe science and guidanceobjects.

Open list of plannedobservation objects,select the first object. ortype in RA&Dec and hit“acquire object”. A star-finder chart may beincorporated here as anoption. This selects thescience and guidanceobjects .Enter observationdetails into observation log.

Scheduling list/sorter, auto-sorter, selection control, star catalogue,observation log page

18. The system automaticallylifts the structure, rotates inazimuth, lowers thestructure and moves thetracker to place the object inthe acquisition FoV centre. Itfollows the object atsidereal of a pre-definedrate.

Status control of structure, tracker andpayload. Acquisition display and control

19. The Tracker Payload opticsare automatically set todirect the science field lightinto the acquisition camera.The appropriate instrumentguide probe is moved to thepre-defined or automatic(from sky catalogue) guide-star position.

Acquisition and guidance display andcontrol, star catalogue, image and mathtools

20. ObjectSetting

A finder chart overlay isdisplayed over theacquisition image and theoperator checks that thecorrect object has beenselected in acquisition FoV.

A finder chart overlay isdisplayed and the operatorchecks that the correctobject has been selectedin acquisition FoV.

Acquisition and guidance display andcontrol, star catalogue, image and mathtools

21. The operator selects “showscience overlay” and anoverlay of the slit or fibrepositions is shown insteadof the finder chart. Theoperator adjusts the trackeroffsets to place the objectsat the desired slit/fibrelocations.

The operator selects“show science overlay”and an overlay of the slitor fibre positions is showninstead of the finder chart.The operator adjusts thetracker offsets to place theobjects at the desiredslit/fibre locations.

Acquisition and guidance display andcontrol, star catalogue, image and mathtools, tracker status/control display,science overlay data from instrument

22. The operator selects“Direct light at Instrument”and the Optical Payloadfold mirror moves to directthe light to the instrument.

The operator selects“Direct light at Instrument”and the Optical Payloadfold mirror moves to directthe light at the instrument.

Calibration source status/control display,guidance status/control display, instrumentstatus/control display, instrument datadisplay (image..)

Page 19: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

19

Salt Day/Night Operators onSO Workstation

Salt Astronomer on SA WorkstationProcess Step

From/to TCS and SALTsubsystems

From/to TCS and SALTsubsystems

From/to Instrumentcomputer(s)

23. Closedloopguidance

The operator clicks on theguidance object image andselects “enable closed loopguidance” (could havestarted automatically). Thetracker performs closed-loop guidance. Guidanceerror and image quality aredisplayed. Guidance offsetscan be made.

The operator clicks on theguidance object imageand selects “enableclosed loop guidance”(could have startedautomatically). Thetracker performs closed-loop guidance. Guidanceerror and image qualityare displayed. Guidanceoffsets can be made.

Guidance status/control display,instrument status/control display,instrument data display (image)

24. If feedback is available fromthe instrument (e.g. slitcamera or exposure test),add offsets to guidanceposition to find optimalposition and orientation(possibly directly from theinstrument).

Perform test exposure(if rqd.) to check ifobject is entering theinstrument aperture.Further calibration isperformed if rqd (e.g.flat-field, arc-lamp).Save calibration datato data processor

Calibration source status/control display,guidance status/control display, instrumentstatus/control display, instrument datadisplay (image), data/image manipulationtools

25. Assess the quality ofguidance, image, focus, etc.Check.

Assess the quality ofimage, focus, S/N andexposure time.

data/image manipulation tools

26. ScienceExposure

As above, plus monitortelescope environment (esp.humidity, temperature andwind speed) and telescopehealth status. Take actionsrequired.

Check telescope status,available and requiredtracking time before nextAz move. Correspond withPI if appropriate.

Perform scienceexposures andassess quality ofdata. Save data locallyand/or to DataProcessor (TBC).

Weather display, status display, trackingtime available display, relay-hat program,data pre-processing tools, data evaluationtools, data/file manipulation tools

27. Update night log with allevents

Update observation logwith details of observation.Telescope parameters areautomatically entered.Perform pipeline datareduction if required (usingdata reduction PC). Checkdata meets PI’srequirements.

Operator Log and Observation log editors

28. Complete the observationlog.

At the end of theobject’s observation,close data files and“package” data onData Processor.

Log page, data/file tools

29. Further calibration isperformed if rqd (e.g.flat-field, arc-lamp).Save calibration datato data processor

Calibration source status/control display,instrument status/control display,instrument data display (image)

Page 20: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

20

Salt Day/Night Operators onSO Workstation

Salt Astronomer on SA WorkstationProcess Step

From/to TCS and SALTsubsystems

From/to TCS and SALTsubsystems

From/to Instrumentcomputer(s)

30. Nextobject.

Go to step 17 Go to step 17 Go to step 17

31. Dawnclose-out

Complete the night log andnote urgent actions for daycrew.

Select/activate calibrationsource

Perform finalcalibrations if rqd andsave data.

Log page, log tools, e-mail and white-board, log book, calibration status/controldisplay

32. Select “Close Telescope”.This will close Dome andlouvers.

Telescope control display

33. The dayafter thenightbefore

Turn on A/C at anappropriate time. Monitortelescope internal temp.Asses image quality fromlogged data and decidewhen mirror alignmentrequired.

Sort data, performpreliminary data analysis,compress data, send toFTP site, inform PI that dataavailable.

Weather display, IQ display/graph, datasorting tools, data analysis tools, webbrowsing/FTP tools,

34. Anytime Maintain Observation logs.Schedule telescopeEngineering, Science,Instrument Commissioningtimes. Evaluate ImageQuality trends and initiatecorrective actions. Respondto system failures andwarnings.`

Maintain observing logs.Assess partner accountsand priorities. Performarchive of old data.Maintain FTP site and PItools

Data sorting tools, data analysis tools,web browsing/FTP tools, e-mail, logsorting/reporting tools, scheduling tools

35.Emergency

Use emergency stops ifsudden stopping required.

E-stop in control room

36. Close shutter manually ifTCS and Dome Controllerfails to do so.

Electrical operation of shutter in electricalroom.

37. Close shutter by hand ifpower fails totally or ifshutter drive fails

None

38. Shut down TCS and allsubsystem computers ifextended total power failure(no standby power) or ifUPS fails.

Well-define shut-down procedure orscripts.

Page 21: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

21

6.3 Maintenance Staff TCS-related Tasks

Action Tools usedView night logs and problem reports. Decide on priorityactions for the day. Update problem reports with taskstatus.

Observation and operator log view,update and reporting tools.

Place subsystems into “maintenance mode” as requiredto perform specific manual tasks, calibrations,configuration changes and adjustments.

Detailed subsystem pages viewablefrom the TCS workstations, or othernetwork locations (desirable).

Perform manual movement of the dome, structure,tracker and payload while in the telescope chamber.

Remote TCS (manual control panel)

Perform emergency-stops when required Distributed e-stop buttonsCommunicate with personnel located throughouttelescope

Two-way radio’s

Backup data and software periodically Mass storage devices, appropriatesoftware

Summarise telescope serviceability status and transferto night crew

White board and bulletin board.

Page 22: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

22

7 Control Room Layout

The control room layout must support the information visibility, ergonomics and communication requiredfor the operation of the telescope in accordance with the tasks defined in section 5. Appendix A showsthe proposed layout of the control.

The following primary work areas are defined:

7.1 Common Work Area

This area is shared by both the SO and the SA and contains information and facilities that are requiredby both but that need not be fully duplicated. The following resources are planned to reside in thisarea:

• CCTV display and control providing visual indication of the status inside the TelescopeChamber.

• Audio speakers, amplifier and mixer providing feedback of sounds at pre-defined locationsinside the Telescope Chamber

• Two-way radio for communication with maintenance crew and any staff working on theTelescope

• Large TCS monitor providing outside weather and internal environmental information• Large TCS monitor providing the most important overall status information of the telescope.

E.g.:o Warning Failures of High or Moderate seriousnesso Status of safety interlocks or lock-outso Telescope RA and Dec.o Sidereal and Universal timeo Maximum time left to end-of-track

• Telephone(s)• Fire alarm enunciator panel

The equipment must be positioned to allow optimal viewing and use primarily by the SO and SA butalso by any other person working in the control room.

7.2 SO Workstation

The primary tool available to the SALT Operator is the SO Workstation, comprising a PC with two largemonitors. This workstation must be located so that the SO can utilise/view the Common Work Areaand have sufficient space for documents in his work area. It must be possible to duplicate thisworkstation at Cape Town for remote operation in future.

In order to facilitate maintenance and commissioning, it must be possible to partially duplicate thisworkstation at several remote locations simultaneously (e.g. at the Top Hex), albeit with reducedfunctionality.

The SO Workstation will run the TCS MMI software which communicates with the TCS server andother processors as required. Additional software such as spreadsheet software, reporting toolsand mathematical analysis tools may be required.

Page 23: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

23

7.3 SA Workstation

The SA requires access to the TCS for certain functions while other tasks are performed on theappropriate instrument computer. The TCS SA workstation will comprise a PC with two large monitors,preferably running the same TCS MMI software as the SO workstation, albeit in another configuration.Additional software tools to perform observation planning and scheduling and data analysis will berequired.

Although full integration of the Instrument and the TCS is not envisaged at this stage, it is arequirement to integrate these at an MMI level by allowing operation from separate windows/framesvisible from the same monitor and using the same keyboard and mouse.

A PC for performing initial data-reduction is also required. This PC shall contain the appropriate SWtools required to perform this function and shall have access to the science data repository.

7.4 Future Growth

Space and network provision must be made for growth by the addition a further four computers (e.g.for a visiting instrument), both in the control room and in the computer room.

Page 24: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

24

Appendix A: Control Room Layout

Figure A1: Control Room Floor Plan

NOTE: The main entrance to the control room is the bottom left corner.

Page 25: TITLE : SALT Operational Requirements...conveyed and that the particular detailed requirements will be finalised during the development process. An MMI prototype will be used to facilitate

SALT Operational Requirements

Doc No. SALT1000AS0040 Issue B

25

Figure A2: Isometric View of Control Room