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.
Replace any defective lamps with new replacements (28v)
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:
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.
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:
SYS> shutdownobssys
Do you want to wipe out the system Y/N? y
SYS> exit
DAS> shutdownobssys
DAS> exit
Follow this procedure for each WHTDAS(#)window.
Shut down any remaining windows and exit the system as per the System computer.
USER> tcsexit
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)
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.
Two main windows will appear. One being the TCS INFO DISPLAY, the other the
USER interface.
When the prompt with the time stamp is displayed, ( e.g. 14:15:30> ) the ICL is ready.
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.
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.
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.
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
USER> next
USER> page enc
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.
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
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?
USER> focus 96.25
USER> focus 97.45
USER> PARK ZEN
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.
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.
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
Several windows should then appear.
n.b. A blue Xterm will be generated also, but this will be minimised.
n.b. The above procedure must be done in EACH orange DAS window for the detector(s) in use.
The option number selected must be the same as what was used for the DAS
During start-up, various windows will be generated. The important ones being:
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.
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.
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:
prag 15000 50000
(moves the Cass autoguider probe)
compnd 1 (put
in a neutral density filter)
compnd 0 (remove
it)
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)
agaux
(divert beam to aux port)
auxfilter 3
(range is 0 to 5)
agmirror out
(remove mirror)
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.
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
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.
cd /obsdata/whtd/20010613
and display the image on ximtool with:
display rnnnnnn[1] 1
Check that arc lines from ISIS are present
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.
More detail can be found on this system at www.ing.iac.es/~eng/ops/wht/SDSU_Autoguider_Software_User_Manual_02.htm
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.
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.
autofilt opaque
agcomp
complamps w
field
After reading out, the artificial guide star will be clearly visible with a guide box and cross positioned over it.
fon (from the ICL command line) or
GUIDE ON
(from the autoguider window)
autoguide on (from either the ICL or TCS interface)
Check the TCS Infodisplay to see that autoguiding has been enabled.
autoguide off
foff
complamps off
(if on)
autofilt clear
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.
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!
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.
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.
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