Skip to content. | Skip to navigation

Personal tools

Startup on the First Night

The non privileged user account for both DEBONAIR and DUKE is:
  • username: panic

The current password should be posted on the whiteboard in the control room.


Any function requiring the administrator or root password will be handled by the local staff. Although this does provide some protection for the basic system configuration, it is still possible to make substantial changes to the computers. We therefore ask that you please do not make substantial and unnecessary changes to the system configuration. This includes the installation of software packages by anyone other than the local staff.


DEBONAIR and DUKE are accessed remotely from one of the two linux workstations in the control room. DUKE can be connected to via ssh and DEBONAIR with VNCviewer.


Startup Procedure: Connect to DEBONAIR


To connect to DEBONAIR type the following on one of the linux workstations in the control room:


  • %: vncviewer panicfw

and type the panic user account password when prompted. If this is the beginning of your run (and you are not simply restoring the network connection) you should close all of the open windows. This can be easily done by selecting Shutdown from the File pull down menu on the Camera-Control GUI. Start the software by double clicking on the Panic icon.


Note: if you get an error message which reads "Camera-Control [PANIC]: Error. Nyden-Motor-Controller initialization error (err=31)," just say okay and restart the software again.


The Database Initialization Window will now open.


Figure 2: Database Initialization Window


Make sure all six of the menu options are set to online, enter your observer name, and press OK to start up software. The main Control Window for PANIC will now open.


Figure 3: Main PANIC Control Window


This is the main window for PANIC and is used to control exposures and launch additional utilities. The additional utilities that should be launched at this time can all be accessed from the Modules pull-down menu. Start these three modules:


  • TeleGUI


  • Display


  • ThermControl


    The first two utilities, TeleGUI and Display, are described in the next subsection.

The other GUI reports the internal temperature of various positions inside the instrument.


Figure 4: Thermometer


The Thermometer Window displays the output of nine internal temperature sensors in the dewar, as well as the gradient, and also controls the internal heater (used to keep the optics at a stable temperature).


At the start of the run, it is a good idea to make sure that the heater is turned on and the set-point is 200 C. When the thermometer GUI opens, the heater will be off. Turn the heater on with the pull down menu.


Several times per night it is a good idea to check the temperature values, as substantial changes may be the first indicator of a problem. The values shown above are typical operating temperatures. Channel 1 reads the temperature right next to the detector and should be at approximately 77 K. If it is increasing, the dewar needs to be refilled with LN2. Channels 2, 3, 4, and 9 should read very close to 200 K when the heater is on. Channels 5, 6, 7, and 8 will be lower and their exact value is more sensitive to ambient conditions.


A graph of these temperatures can be displayed from the Options pull-down menu by selecting Graph. This will open a window with the graph parameters.


Figure 5: Thermometer Graph Parameters


All of the parameters should be checked in order to plot all the temperatures. A useful x-axis scale is to track the last 24 hours. For the y-axis, a temperature range of 160 to 220 K is useful to monitor all of the internal temperature sensors except the one next to the detector. Once selected, press OK and the temperature graph. will appear.


Figure 6: PANIC Internal Temperature Graph



The temperature monitor should be started at the beginning of the run and left open. Please try to check them periodically throughout the night as a first warning of temperature control problems.

Finally, you may wish to increase the size of the Display GUI. To do this go to the Options pull down menu and select Size -> 512x512.


 Startup Procedure: Connect to DUKE


To connect to DUKE type the following on one of the linux workstations in the control room:

  • %: ssh panic@panicfw

At this point you may be asked about host authentication. If so, type yes. You will then need to enter the panic user account password.


This will open an xterm from DUKE. The next step is to open the data analysis tools. Type the following into the xterm from DUKE:

  • %: startpanic &

This will open ds9 and IRAF in an xgterm. It will also start an xclock (whose sole purpose is to keep the network connection through the PANIC firewall from timing out).


Now create directories on DUKE for your raw data and for your reductions. DUKE has five data disks: /data1 through /data5, so for example in the xterm on DUKE type

  • %: cd /data1
  • %: mkdir ut041121
  • %: mkdir reduce

Now you need to change the permissions of the raw data directory so the data acquisition software can write to it. Type:


  • %: chmod a+rwx ut041121

And on DEBONAIR set the data path with the Camera-Control GUI. The data path is set by selecting DataPath in the Options pull down menu. No trailing slash is necessary here.


 Setup for Data Analysis


PANIC has many quick-look analysis tools, as well as a fairly robust and complete data pipeline. These are all contained in an IRAF package, which is also named panic. In the IRAF window, load the panic data analysis package by typing:

  • cl> panic

The panic package has been set up so that one can perform data reduction in a separate directory from the raw directory. The path to the raw data directory is set with the parspanic parameter file in the panic package. Once it is set, the raw data are accessible from any other directory without retyping the full path name. To set the raw data path type:

  • cl> epar parspanic

and for rawpath enter the directory you specified above, for example:

  • /data1/ut041121/

Note that the trailing slash is important! Now exit epar with :wq to save this path. All routines within the panic package only require specifying the file number to access the raw data. An introduction to the tasks within the panic package is provided later in this manual. The package is also well-documented within IRAF, so one may also type:

  • cl> help panic

to get started. The package is available for download from the main PANIC web page.

Document Actions