Joint Astronomy Centre
Show document only
JAC Home
JCMT
UKIRT
Contact info
JAC Divisions
OMP
Outreach
Seminars
Staff-only Wiki
Weather
Web Cameras
____________________

Observing at UKIRT
Service Observing
UKIDSS Survey Operations
Target of Opportunity
Calibration & Utilities
UKIRT Archive
Public wiki
Accessing Flexed Data
Accessing UKIDSS Data
Reduction Cookbooks
Telescope
Site Quality
Instruments
Newsletter/Publications
UKIRT Faults
JAC Safety Manual
runup
QUICK RUNUP and RUNDOWN NOTES UKIRT



These instructions are not exhaustive; they are intended to be memory-joggers to get you started. This document is regularly reviewed; please let your TSS know if you find it is out of date.

Order-specific items

  1. Any external component that is needed for a particular observation must be run up before sending the observation for execution from the QT. Two examples: CGS4 needs to be run up (on the VAX Side, by the TSS), and datummed, before sending a CGS4 observation, and the telescope needs to be run up before sending an observation that needs the telescope.
  2. No sequence console will run up until the observer has typed ocs_up (to start the ukirt_inst task).

Most run down sequences involve no more than typng ocs_down on ohi (this runs the respective instrument tasks down and cleans up) and exiting the DR and QT on kauwa. Exceptions are listed below.



WFCAM
Run Up
1
(normally done by the TSS)

Run up WFCAM.
  • log onto Hokulea as yourself
  • run up wfcamControl by typing "wfcamControl"
  • from wfcamControl
- run up the wfcamMain screen
- run view/monitor log which launches an xterm for messages
- run up low level software


2
(normally done by the observer from an xterm on ohi) 
Wait for the TSS to complete startup tasks, then run the WFCAM Observation controller: click the "UKIRT Obs (ohi)" button on the task bar.
(done by the TSS)

From wfcamControl, add inst
enable the arrays

(by the Observer on ohi)
Run up the OCS: click ocs_up in the wfcamObs panel

3
If the DR gaias are not present on the four big WFDR displays:

(as observer in front of the four DR screens)

Switch on WFDR1/2/3/4 displays:

For each DR machine (wfdr1,2,3,4) press scroll lock, scroll lock, n, <enter> (e.g. lock,lock,1,<enter>) to get the cursor into that DR screen. Login as observer, and type startx. Maximise the gaia that results.

4
(as observer on kauwa)

Start the WFCAM Observing controller: click the WFCAM Obs (kauwa) button on the taskbar. We suggest you make this item sit in each workspace (DR, OT etc.; do this from the "X" menu in the top left of this window).

Start ORACDR for each camera: Press the wfcamReduce button

Results should now be being plotted to the four gaia displays. If they aren't, call your support scientist.

Start the gaia control system: press the wfcamDisplay button

...and click "all Defaults" to set the axis rotations and flips such that the arrays are displayed in normal astronomical orientation.
5
(as observer on ohi)

Start taking data: from the QT calibrations menu (WFCAM section), run a WFCAM Flush, then a Readnoise test, then Darks. If time permits, run the darks more than once. Note that your final set of darks should be commenced ten minutes before you would normally expect to be able to guide, as this will guarantee that the long-exposure NDR darks are done in genuinely dark conditions and minimise light leaks.

While doing this, inspect the data directories (/ukirtdata/raw/wfcam<n>/<utdate> and /ukirtdata/reduced/wfcam<n>/<utdate>) and run a gaia on kauwa for inspecting individual frames and group mosaics through the night.

6
(as observer on kauwa)

Run the WFCAM logging windows: press the wfcamLog button
Run the data quality stripchart: press the wfcam_stripchart.
Run the ompobslog tool (it's on the task bar).

Run Down
1
  • Observer (on ohi) runs an "end of night sequence" - a set of Darks will do. This will set a blank filter in place. Note that you don't have to complete the darks, this is run just to get the dark filter in place.
  • TSS disables array from wfcamControl gui (this needs to be done while WFIS and the low level software are still running)
  • Observer runs ocs_down from wfcamObs gui
  • TSS runs down low level software from wfcamControl (this can be done before or after ocs_down)
  • Observer ctrl-c's each pipeline, then types "oracdr_nuke -nogaia" in each of the 4 WFDR windows to kill the DR and then exists from them. Please leave the gaias running.
  • Observer (on kauwa) runs msb check: type limit coredumpsize 0 and then ompmsbcheck -tel ukirt -ut <yyyymmdd> and resolve any discrepancies.







Cassegrain

Run Up
1
(This set is done by the TSS)

Run up uist
ssh into ohi as observer
run cassControl to get the control gui
dm uist_oper.dl &

  • Then follows left to right along the top to datum the motors, move the mirror out of the beam, turn on the blackbody and enable the array.
  • Each button must be clicked followed by the start button, and each step must be completed before the next is started.
  • Final step: enable the array

Run up ufti from menu in the topend.dl screen
  • if you are using the FP, type dm fp.dl&
  • if you are using irpol, type dm irpol.dl&
  • In normal circumstances the IRPOL HP does not require reloading, but IRPOL should be datumed before one starts using it

Run up cgs4

On hokulea: login to irtcon from an xterm. In that session, type xdecterm (creates an IRTCON DECTERM)
In the IRTCON DECTERM window:
cgs4_dev
Run IRPOL if it's going to be used
  • type dm irpol.dl& (usually the TSS does this). 
  • In normal circumstances the IRPOL HP does not require reloading, but should be datumed.
2
(This is normally done by the observer from an xterm on ohi. Wait for the TSS to complete step 1 first)
  • Run the ukirtObs (ohi) item on the task bar
  • When the TSS tells you it's ok, click the ocs_up button in the resulting gui. Say "no" if offered any deferred observations.
  • Run the UFTI Array Tests sequence from the Calibrations menu on the QT (right-click and send for engineering from the deferred area)
3
(This is normally done by the TSS on hokulea)
ukirtmon
4
(This is normally done by the observer on kauwa)

Run the data reduction pipelines
  • Run the CassObs (kauwa) gui on the task bar
  • Click the CasReduce button on the resulting gui, and select to run all three.
5
(This is normally done by the observer on ohi)
  • when the TSS says UIST is ready, run the UIST Calculate Read Noise sequence from the Calibrations menu in the QT (send to queue from the deferred area).
  • Run the UIST Determine Bad Pixel Mask sequence from the Calibrations menu in the QT (as above)
  • Run the CGS4 Array Tests sequence from the Calibrations menu on the QT (right-click and send for engineering from the deferred area)
Run Down
1
(As observer on ohi)
  • Run the UFTI End of Night sequence from the Calibrations menu on the QT (alternative: the TSS can just ensure that the shutter is closed from the UFTI dm screen).
  • Run the UIST End of Night sequence from the Calibrations menu on the QT (alternative: the TSS can just ensure that the shutter is closed from the UFTI dm screen).
  • If cirrus around, run the CGS4 End of Night sequence from the Calibrations menu on the QT. If clear, run the CGS4 emissivity.
  • Click ocs_down on the ukirtObs gui

(As observer on kauwa)
  • Exit the OT
  • Exit each oracdr (button top left of the oracdr reporting window) and all the associated graphics windows.
2
run down CGS4 (TSS)
  • Ensure that the black body is off
  • Run down the sms system and kill motor tasks
run down uist (TSS)
  • using the dm screen, following the second line left to right, one button at a time, to blank off the filter wheel, turn off any arc lamps that may be on, put the mirror in the beam (this protects the window), turn off the   blackbody and disable the array.








Michelle
(Steps 1-6 are done by the TSS on hokulea)
1
From an xterm, type michelleMenu&. This will bring up a button box with various Michelle functions.
2
Click on Michelle_oper Screen to bring up the Michelle main operator screen.
3
Take michelleMenu screen into another workspace, and click WFG serial console only to bring up the wfg monitoring or All EDICT Serial consoles if you want to see them all.
4
Reboot the EDICT crate (hard reboot in the computer room)
5
In the Main Michelle operator screen, click enable to enable the array
6
(by the observer on ohi)
ocs_up
into an xterm window, retrieve your programme and proceed to send observations for execution. 
7
(by the TSS on hokulea)

run up the monitor: type   
ukirtmon
8
(by the observer on kauwa)

into an xterm window, type 
oracdr_michelle
oracdr -loop flag
Run Down
1
The most important thing to remember is to close the cover - this is vital for the health of the instrument. You should always do this at the end of the night or when there are long periods when no Michelle observations are
being carried out. Until the close button is implemented in the CCS control, you will have to click on the "calibration" button in the cryostat control system window, which will bring up the Calibration Unit control window.
2
To close the cover, click on the "clear" button then click on the "flat/cover" button (this ensures that the request gets picked up). Then simply hit the "START" button. You will see the shutter step positions change at the top of this window, and after a few seconds, "flat/cover" will appear in the setting field at the top left.
3
Next, disable the array from the main michelle operator window, then go back to the Edict serial consoles and hit <RETURN> in the WFG console (bottom left) in order to bring up a prompt. You can now close the consoles by typing "crtl-]" (that's a closing square bracket) in each window to bring up a telnet prompt and then typing "quit".
4
To close the Edict contol window, simply click on the "Close" button, and to close the CCS control window (if open), hit the "Exit" button. Finally, click on  the "exit" button in the Michelle menu window.




Tasks etc.

This section details what happens when the system is run up; it is not part of the quick-start lists above but should serve as background to help understand why the lists are as they are.

The system structure has been significantly changed so there are now three, largely independent, components. These are:

ukirt_inst This task acts as a master controller that manages all UKIRT instruments.
All instrument run-up, run-down, exec loading and beam control is handled by this task.
There can only be one ukirt_inst task running at a time.
Note that it doesn't have a gui and works in the background so it isn't very obvious, but does quite a bit of the work.

ukirtqt

This is the familiar query tool that gets the observations from the database. On sending an observation for execution, the QT asks the ukirt_inst task to load an exec, and the ukirt_inst task works out which instrument it needs, and loads the instrument before sending the exec, if it needs to.

ukirtmon

All consoles are slave consoles which get information from the ukirt_inst task. As such they can be run up and down at will. However, note that obviously the ukirt_inst task must be running before any console is runup (you will be reminded of this if it's not).


The ocs_up script just runs four commands which:

1. Start DRAMA networking.
2. Start the ukirt_inst task.
3. Starts a copy of the ukirtqt task.
4. Starts a copy of the ukirtmon task.

The ocs_down script essentially does the opposite.

The ukirtqt task and ukirtmon tasks are highly independent from the rest of the system:

 - You can have multiple ukirtqt's run up, and multiple ukirtmon's.
 - You can run any ukirtqt or ukirtmon down and up without disturbing the rest of the system.
 - There is no difference between the observers ukirtmon and the tss's.

This means you can actually run down the observer's ukirtmon console whilst observing and there should be no ill effects. It should also help keep the
effects of problems within these systems contained so they don't knock on to the rest of the system.


Contact: Andy Adamson. Updated: Fri Oct 19 17:43:04 HST 2007

Return to top ^