WHT Duty Engineer Checks

For ISIS, Aux port and Prime Focus imaging using UltraDAS


Ver 9.0

Note
When INGRID or INTEGRAL is in use, please refer to the documents: INGRID daily checks or INTEGRAL daily checks
These additional docs give the full check-out procedure for these instruments.

Hot Links


Preliminaries

  1. First check the Operations Logbook for any restrictions that may be still in force. Turn on the DOME LIGHTS from the console and raise the control room blind.
  2. Make a visual inspection of the observing floor to check that the telescope is free to move. e.g. No ladders or steps are close to the telescope or test instruments connected.
  3. Push the LAMP TEST button on the console. Check that all used indicators are working (e.g. the ALARMS).


Replace any defective lamps with new replacements (28v)

  1. Push the MIRROR OPEN button. Check the mirror petals open fully then push the MIRROR CLOSE button.

Preparing the telescope for checking

  1. Check that the MODE key on the engineering desk is set to ENG.
  2. Switch the BEARING OIL PUMP and G/B OIL on and wait for the lamps on the alarm panel to go out.
  3. At the bottom of the blue Marconi cabinet (Bay 6) containing the power amplifiers, switch on the following breakers:

If working at Cassegrain focus:

If working at Prime focus then switch on ONLY the breakers:

If working at either of the Nasmyth foci, the breakers for the Nasmyth rotators (Bay 4) are switched on:

New procedure

When starting ICL, the Telescope Control System (TCS) should be automatically invoked. It is better NOT to start the TCS manually unless there is a problem.


Logging out from the WHT Observing System

Note:
If the WHT Observing System is running, it is best to bring it down to ensure a clean startup each day. This especially applies to the DAS and ICS computers where memory leaks can cause problems.

The WHT observing system comprises of several computers. These being:

Logging out from the CI and DAS computers

  1. On the System computer, enter in the pink window at the SYS> prompt:
SYS> shutdownobssys
Do you want to wipe out the system Y/N? y
SYS> exit
  1. On a second screen of the System computer there is a group of orange windows; one for each DAS, enter in the orange window at the DAS> prompt :
DAS> shutdownobssys
 
DAS> exit

Follow this procedure for each WHTDAS(#)window.

  1. To log out from the System computer. Click the right mouse button when the mouse pointer is over the blue background window and choose the "exit" option at the bottom of the menu. This will log you out completely. Any residual windows will be killed off in the process.

Logging out from the ICL

  1. At the 'date' prompt, type: exit
    The response will then be: Remove system tasks?(yes/no) enter 'y'
    The ICL will now run down. When the $ prompt appears type: logout
    You are now logged out from ICL. To log out of LPVG (or LPVF) type: logout again
    To log out from the Vax workstation (lpvs1), click on session on the tool bar then end session.
    This takes you out completely and after a short time the Vax Login window will appear.

Logging out from the Data Reduction Sparc

  1. In the IRAF window, at the  cl>  or  in>  prompt. To exit type: lo

Shut down any remaining windows and exit the system as per the System computer.

Logging out from the TCS

  1. The TCS is run from the X terminal in the console. In the User window, enter:
USER> tcsexit
  1. Exit any other windows and click on the "cancel" button at the bottom right.
  2. When the only remaining window is the console bar, click on Console (at left) and Reboot (bottom of that menu) and OK. This will reboot the X terminal. n.b. Rebooting the terminal works around a memory leak in the X-terminal software.

Starting the Instrument and Telescope Control Systems (ICS/TCS)

The ICS uses an old ADAM type observing system (ICL) and runs on a VAX 4000 computer. n.b. This will be changed in the future.

NOTE: With the new UNIX PFIP Control system, it is no longer necessary to perform any of the steps in this section, all control is effected from the taurus console.

The TCS runs using VMS on a DEC ALPHA computer. Generic name: whttcs (lpas4)

  1. Logon to the Vax workstation lpvs1 as:  observer (password on terminal)
    Once logged in, a DECterm will be displayed prompting what system is required. These being LPVG or LPVF.
  2. Check the white board for the ICL observing system currently in use. This is usually LPVG, but there are occasions it could be LPVF.
    Enter the machine name required: e.g. lpvg
  3. From the DECterm, logon on to LPVG (or LPVF) as:  observer (password as above)
  4. When logged in :

At this point you will be prompted if you need to change the CONFIG file. As this will have already been setup for the instrument and camera(s) in use. Type 'no' to this message. However:

Important note

There are currently no change documents for private instruments. e.g. PNS, SAURON, etc.

If a private instrument is in use, THE CONFIG FILE MUST BE EDITED to use the appropriate channels SPARE1 and/or SPARE2. These are used to collect FITS headers.

FOR PNS, THE CONFIG FILE MUST BE EDITED WHEN STARTING ICL

Channels Spare 1 (17) and Spare 2 (18) must be to selected along with the Auxport option (7) for PNS to work and collect FITS headers. Therefore when selecting camera options, choose 7,17,18 for PNS. Note at this point in time when spare 1 & 2 are used, WYFFOS error messages will be generated at ICL, but you will have to live with this.

  1. The ICL will continue to load the various D-tasks and bring up the instrument mimic display appropriate to the current observing configuration. n.b. For private instruments, check that the appropriate subsystems are loaded, e.g. Sauron uses CAGB. In the event of problems, call the Duty Software Engineer.
  2. The ICL will continue to load the various D-tasks and bring up the instrument mimic display appropriate to the current observing configuration.
  3. The ICL will also start the TCS.   Check this happens on the TCS Xterminal


Two main windows will appear. One being the TCS INFO DISPLAY, the other the USER interface.

  1. Wait until the message :  ICL start-ups have completed  is displayed

When the prompt with the time stamp is displayed, ( e.g. 14:15:30> )  the ICL is ready.

  1. At the ICL prompt, type:   PAGE
    The display on the TCS window should change to the next page (encoders).

Type:   PAGE INFO   to return.

This checks that the DECNET link to the TCS is up. This is necessary for collecting TCS header information for CCD observations.


Checking the telescope

     0.  The TCS must be running. If you have started ICL in section above, the TCS will already have been started. If ICL is not required (e.g for new PFIP system)  you must start the TCS manually:
               a)  On TO xterm bring up "NCD User Services Console" by holding down <Compose Character> key and pressing <F3> key.
               b)  Click on Terminals, then Telnet. Then connect to lpas4.
               c)   At the username: prompt log in as  WHT_LOGIN, with the usual password.
               d)   Enter  START<return>
               e)   This window will disappear and you should the see two TCS windows, one with USER> prompt and the other with TCS INFO display.             

  1. On the Engineering console, turn the MODE key to COMP and press COMP RESET.

n.b. Check that the meters showing the AZIMUTH and ALTITUDE motor currents are registering. One showing a +ve current, the other the same value, but in the -ve direction. These should be steady with no oscillations.

All the commands below are entered in the TCS User window.

  1. Enter the coordinates of a position near the intersection of the meridian ( i.e. current Local Sidereal Time) and the equator (0 degs declination). Format for entering telescope co-ordinates is :
USER> source name hh mm ss dd mm ss equinox

Where:

name        No more than 20 characters
hh mm ss    RA  hrs mins secs
 
dd mm ss    DEC +/- degs mins secs
equinox     Usually J2000 or A (apparent)

Example: LST is at 21:30:15

USER> source TEST 21 30 15 00 00 00 J2000
 
USER> add
  1. Instruct the telescope to move to the demanded position with:
USER> next
  1. The telescope should slew to the demanded position with the dome moving also.
  2. When TCS Infodisplay indicates that the telescope is TRACKING, check the ENCODERS page by entering:
USER> page enc
  1. Check that the azimuth and altitude incremental (gear) and absolute encoders are in close agreement and updating and that the dome is tracking. The dome and telescope azimuth positions on the TCS Infodisplay should be similar within a few degrees.

  2. Entering:
USER> page info

will return the TCS Infodisplay window to the default page.

n.b. If the dome does not move, it may have been overriden? On the console there is a bank of five push buttons labelled SELECT MANUAL CONTROLS. Check that the button DOME/SHUTTERS has not been set. If the dome still doesn't move, check that the keyswitch on the grey dome control cabinet (which rides with the dome) is in the REMOTE position. It may have been switched to LOCAL.

Checking out the rotators

  1. The TCS on startup defaults to the CASS rotator in 'rot sky' mode. If the telescope is not tracking, but computer control is still enabled, enter:
USER> rot float

The TCS will pick up the current position of the rotator and put it into TRACKING mode. Make sure this happens.

If working at Prime focus, enter:

USER> station prime
USER> rot float

If a DS or CWS Nasmyth rotator is required then enter:

USER> station name
USER> rot float
  1. Ensure that the selected instrument rotator goes into TRACKING mode. Check that the incremental and absolute encoders for the selected rotator are in close agreement by accessing the ENCODERS page as previously described and are updating at regular intervals.

n.b. If the DS (or CWS) rotator does does NOT move? Has the DS or CWS breaker on the Nasmyth cabinet power control panel tripped or perhaps it has not been switched on?

  1. When you have established that the telescope and rotators move and go into  ”TRACKING” carry out a servo test of the Alt, AZ and rotator which is current selected. At the TCS promt type “RMS servo ON” leave it running for 1 minute the type “RMS servo OFF” this will then display the results. Record the RMS values in the LOG book. This test should always be carried out at elevations below 75 degrees. In any case may a note in the log book of the elevation angle when carrying out this test.

 

Checking out the focus drive

  1. Before doing this, make a note of the current position of the focus. Move the focus a small amount then return it to it's previous value e.g. Focus is at 97.45 then enter say:
USER> focus 96.25
  1. Check that it gets there then return it back.
USER> focus 97.45

Completion of Telescope Checks

  1. Put the telescope back to zenith park by entering:
USER> PARK ZEN
  1. To return the TCS to engineering mode, type:
USER> eng

n.b. You can also return the TCS to engineering mode by turning the MODE key to ENG. If the is done type ACK at the user prompt to cancel the alarm.

  1. Switch off the BEARING OIL PUMP and G/B OIL pump and press the ACCEPT button to cancel alarms as they sound (usually 3 times).
  2. Switch off the power amplifier circuit breakers

n.b. In bad weather, the dome upper shutter should be exercised to prevent icing up, by slightly raising and then re-closing it in micro-drive. It isn't necessary to test dome shutter operation when doing the daily checks.


WHT UltraDAS startup

The WHT observing system comprises of many computers. These being some examples:

Check the magnetic CCD board in the WHT control room which gives up to date allocations of machines and CCd’s.

Generic machine name

Camera or instrument

whtdas

INGRID only

whtdas3

ISIS red

whtdas4

ISIS blue

whtdas9

PRIME or GHRIL

whtdas6

AUX

whtics

SYS (Central Intelligence)

n.b. The system computer runs the terminal windows and displays, but does not at this stage of  the development of the system, run the instruments. The ICS is part of the ADAM system, running on a VAX computer and will later be ported across to a Unix based ICS. More info can be found in the:  Operations manual for UltraDAS

Procedure

  1. Login to whtics (taurus) as:   whtobs


Several windows should then appear.

n.b. A blue Xterm will be generated also, but this will be minimised.

  1. Select the DAS window for the camera(s) in use i.e.
  2. In the DAS window, enter :  obssys
  3. Select the option number for the observing system in use.
  4. Now type:   startobssys
    The DAS software will be loaded and the  DAS>  prompt returned when completed.

n.b. The above procedure must be done in EACH orange DAS window for the detector(s) in use.

  1. In the WHTOCS window enter:  obssys


The option number selected must be the same as what was used for the DAS

  1. Now type:  startobssys

During start-up, various windows will be generated. The important ones being:

  1. When the SYS> prompt is returned. The observing system is ready to rock n'roll!
  2. To avoid screen clutter, minimise the DAS windows and other windows that are not being used.

Taking a test bias image

  1. To take an image, enter at the prompt:
    SYS> bias channel    (where channel = red; blue; aux; pfip; integral; etc)
  2. Wait until the CCD status monitor indicates that the CCD has been read out and has been 100% processed. Make sure the image gets written (with  TCS header information) to the Observing Log.

Displaying the image

  1. Login to the WHT Data Reduction Sparc (whtdr) as:  whtguest
  2. Open the programs menu by clicking on the background and start an xgterm and ximtool session.
  3. In the xgterm, start an IRAF session using the command: cl
  4. Within IRAF, change to the obsdata directory where the images are being stored. Note, a new ’date’ directory is generated at 12:00 UTC daily. e.g.

cd /obsdata/whtb/20010508

The CCD status monitor window(s) will contain information on which disc the images are being stored. The main discs currently being:  whtb; whtc & whtd.

Each image (or image pair if using the Mosaic camera) is contained in a single FITS file with: rnnnnnn  being the last run number.

  1. e.g.  To display the image, enter at the IRAF prompt:

display r345678[1]1 fill+

In the case of the Mosaic camera: To display the image from chip 2

display r345679[2] 2 fill+

n.b. Both images can be displayed side by side by then selecting the 'Tile Frame' option on the ximtool control panel.

Examining the image

  1. At the IRAF prompt, enter:  imexam
  2. Move the mouse into the area of the displayed frame and left click. Move the mouse around the image area, typing "m".  This will produce statistics for a box containing 25 pixels centred on the mouse cursor. Check that the noise(e) levels correspond to the CCD data held in:
    http://www.ing.iac.es/ Engineering/engweb6a.htm
  3. To exit imexam, leave the mouse cursor over the image area and type:  q

Instrument Checks

IMPORTANT
When checking out the instruments, use commands that will NOT move mechanisms that have been setup by the observers. This particularly applies to COLLIMATORS and GRATINGS. Moving filters, autoguider probes etc. is the safest option.

Examples:

  1. Cass A&G Box


prag 15000 50000  (moves the Cass autoguider probe)
compnd 1 (put in a neutral density filter)
compnd 0 (remove it)

  1. ISIS


dekker 3  (move dekker slide to postion 3)
dekker 0  (remove it)
hwin  (move in the half wave plate (ISIS P check)
hwout  (remove it)

  1. AUX PORT


agaux  (divert beam to aux port)
auxfilter 3  (range is 0 to 5)
agmirror out (remove mirror)

  1. PFIP


Execute the following from the taurus WHTOCS console observing window. Note that with the new Solaris based PFIP controller system, there is no need to start anything on the old VAX/ICL system. All of the instrument control processes will be started when the startobssys is executed from the taurus WHTOCS console.

agprobe 50000 10000  (moves the PF autoguider probe)
pfilter 3  (moves main filter wheel. Range is 1 to 7)
pfip_status (displays the status of the system)

With the TCS running, move the telescope to different altitudes and check that the ADC elements move from the graphical application labelled 4MSControl which can be used to control PFIP. The status associated with the position of either of the ADC elements should be blue as the ADC changes position.  

On the TO terminal, start up a telnet session on taurus as whtobs. Next type obssys and select the same option as was selected when the observing system was selected on taurus.

Execute a pfip_status command from this terminal to ensure that all is working correctly. A display of the status of the instrument should be displayed.


Setting up ISIS to take a test spectra

  1. At the ICL user interface, for ISIS move in the comparison mirror and switch on both arc lamps:
agcomp
 
complamps CuNe+CuAr

n.b. ONLY if this is the first night of an ISIS run, set the GRATING and SLIT to these values:

cenwave red 6400
slit 200
  1. At the SYS> prompt, take an exposure (preferably with dome lights out) in each arm deemed to be available for the night e.g.
arc red 10
arc blue 10 

The CCD status window(s) will show the state of progress as the exposure is read out and is processed. Make sure the image gets written (with TCS header information) to the Observing Log.

  1. From the IRAF window, change to the current data directory e.g.

cd /obsdata/whtd/20010613

and display the image on ximtool with:

display rnnnnnn[1] 1

Check that arc lines from ISIS are present

Examining the image

  1. At the IRAF prompt, Type:  imexam

For ISIS exposures, if CENWAVE has been set to 6400, check that the bright line or lines in the centre of the spectrum have about 30000 counts for a 10-sec exposure with a 200-micron slit.

  1. To check that the arc lines are in focus (1.5 - 2 pixels FWHM), position the cursor over an arc line (avoid blends) and use the  j  or  k  keys to fit a horizontal or vertical gaussian profile. The number at the bottom right of the graphics window is the FWHM value.
  2. To exit imexam, ensure the cursor is still sitting over the image and enter:   q

Checking out the SDSU autoguider / TV systems.

Note all systems are now SDSU.

 

More detail can be found on this system at    www.ing.iac.es/~eng/ops/wht/SDSU_Autoguider_Software_User_Manual_02.htm

 

1.    Setting up the System

Use the ‘obssys’ or ‘obssys dev’ command to set up the system. Select the required autoguider camera to be used for TV/autoguiding. If the autoguider is to be run on the DAS machine used for the autoguider camera, then the UltraDAS camera server should be started with the ‘startobssys’ command.

If the autoguider is to be run on a different machine from the DAS computer, then ensure that the autoguider camera is running on the remote DAS machine.

2.   Starting the System

Start the autoguider using the ‘startsdsuag <autoguider_name>’ script provided. For example to start the ag2 autoguider, then type:

startsdsuag ag2

This script will start up the following items:

SDSUAutoguider – This is the SDSU autoguider server. The message “The autoguider is starting up” should appear in the talker window.

SDSUAutoguiderGUI – This is the SDSU autoguider control GUI.

ds9 – This is the display tool used by the autoguider for displaying TV/autoguider images.

talker – This provides log, informational and alarm information on the autoguider.

3.    Restarting the System in the Event of Problems

Shutdown the camera server on the DAS machine on which the camera is running by typing ‘shutdownobssys’, and then type ‘cleanup’ to clean up DRAMA. Restart the camera server by typing ‘startobssys’ on the DAS machine.

On the autoguider machine, type ‘startsdsuag <autoguider_name>‘ to restart the autoguider tasks. For example to restart the ag2 autoguider, then type:

startsdsuag ag2

4.   Reverting to the original UltraDAS Autoguider

Close down the SDSUAutoguider by typing ‘murder SDSUAutoguider’. Start up the UltraDAS Autoguider with the command ‘startag <camera>’. For example:

1.     The Artificial Guide Star Test at Cass (optional)

A more in-depth test for the autoguider is using the artificial guide star. It should be noted that this facility is only available for the CASS autoguider, but it does at least allow the autoguider error correcting loop to the TCS to be closed.
n.b. The TCS must be running with the telescope TRACKING to close the loop.

  1. To use this, enter in the ICL user window:

autofilt opaque

  1. To see the artificial star, some stray light is required. Turning on just the MOUNT lights on the telescope should suffice. If more counts are required, move in the comparision lamp mirror and turn on the tungsten (white) lamp and take an exposure. The ICL commands being:

agcomp
complamps w
field

After reading out, the artificial guide star will be clearly visible with a guide box and cross positioned over it.

  1. To initiate guiding, enter:

fon  (from the ICL command line) or
GUIDE ON  (from the autoguider window)

  1. With the TCS running and the telescope tracking, to close the guide loop enter:

autoguide on  (from either the ICL or TCS interface)

Check the TCS Infodisplay to see that autoguiding has been enabled.

  1. To restore the autoguider for normal operations after carrying out this test. Enter the commands:

autoguide off
foff
complamps off   (if on)
autofilt clear


 


FINALLY

Filling the WHT Cryostats

This can take a considerable time depending on how many detectors are in use. Although some detectors may not be required for observing, they may need to still be kept cold. If you have any doubt, check the CCD status board in the middle of the console to see what cryostats need to be filled.

Saving time

To save time, cryostats can be filled when running up the computers, but be aware that they can empty out when moving the telescope to certain positions!

Procedure


Check the pressure does not exceed 20psi for a armoured steel hose. 10psi if the hose is silicon.

VERY IMPORTANT!
Always remember to leave the PRESSURE RELEASE valve on the dewar OPEN. If this is forgotten, pressure can build up over time and burst the relief valve on the dewar. Especially if the dewar is close to full.

Before leaving the WHT

Back in the control room. Turn OFF the dome lights and don't forget to tick off the checks as completed and to sign off in the logbook.


Document History

Rev 3.0 July 27th 1992 CRB
Rev 5.0 Feb 12th 1994 CRB
Rev 6.0 Feb 19th 1999 CRB
Rev 7.0 Sep 16th 1999 EJM  CRB's edition re-written in HTML format
Rev 8.0 Jun  14th 2001 EJM  Completely revised to cover UltraDAS
Rev 8.1 Jun  27th 2001 EJM  Minor changes made
Rev 8.2 Oct 15th 2001 EJM/SHEILA  Config file check added
Rev 8.3 Dec 12th 2001 EJM   Aux port is now on UDAS
Rev 8.4 July 16th 2002 EJM   Machine names removed. Generic names only now
Rev 8.5 Sep 12th 2002 EJM   Logging off WHT Observing System added
Rev 8.6 Sep 17th 2002 EJM   References to UES removed
Rev 8.7 Oct 9th 2002 EJM   PNS channel selection added
Rev 8.8 Dec 18th 2003 CB/FJG Added details relating to new UNIX PFIP control system & TCS start

Rev 8.9 Jun 28th 2004 KMD/RAB Added details of SDSU autoguiders and TVs. Westinghouse info removed.

Rev 9.0 Dec 9th 2004. KMD added RMS servo Checks and removed cryocam instructions.

 

Click here for the WHT home page.

THIS FILE: http://www.ing.iac.es/~eng/ops/wht/wht_checks.html