MDM Observatory Observing Run Startup Procedure

2005 December 1 

updated 2012 October 18 [Barr/MDM]

This document describes the startup procedures that must be followed with the new system. They are meant to be executed by the mountain staff at the start of every observing run or after every instrument change, regardless of whether the same observer is using the new instrument.


Startup Procedure

The startup procedure should be followed by the mountain staff every time there is

  1. A new observer.
  2. A new instrument.
  3. Both a new observer and a new instrument.
The steps below ensure that no "stale" system configuration files are left on the system after the previous observer has left or an instrument removed. This prevents "configuration creep" in the system, and accidental misconfiguration that might result in loss of observing time.

The startup procedures are to be carried out on the Observer's Workstation, after ssh in an xterm window to hiltner at the 2.4-meter telescope, or ssh in an xterm window to mcgraw at the 1.3-meter telescope.

Step 1: From an xterm window on MDM 2.4m Observing Worstation 1 or at the 1.3m it's 1.3m MDM Observing Workstation ssh to hiltner/mcgraw

If the console was left logged in, first log off all the way, and then log back in again as user "obs24m" at the 2.4m, or "obs13m" at the 1.3m. Then open an xterm window on the Observing Workstation and ssh either hiltner or mcgraw for the corisponding telescope.
Step 2: Create the telescope configuration (tel_config) file

The telconfig script is used to create the tel_config file used by xtcs and xmis. Run it by typing
 telconfig
at the Unix prompt. You are first asked if you wish to proceed. This prevents you from accidentally starting the script.

The prompts are self-explanatory. All inputs are case-insensitive, so that "direct" and "Direct" are the same to the script.

When telconfig is done, the observer's workstation is now ready to use xtcs and xmis with this instrument.

At the 1.3m (MDM 1.3m TCS).

Note: you should do this even if the instrument has not been changed. This ensures that the next observer starts with a "fresh" telescope configuration file.

Step 3: Create the MIS filter table (filter.info)

If the instrument uses the OSU Buckeye (4 inch) filter wheel, you next need to create the "filter.info" file with the list of the filters that are loaded.

If the instrument has its own filter wheel (e.g., CCDS, TIFKAM, R4K, 4K, OSMOS(at 2.4m) and the MDM 8K imager), you may skip Step 3 

To create the filter.info file, enter the command:

 misfilter
This is a script which will prompt you for the number of slots in the filter wheel (e.g., 8 for the MIS or 12 for the OSU filter wheel at the 1.3m and 2.4m) and then will ask you which filter is in slot 1 thru N.

NOTE: an important change with the new Linux system is that filters are numbered 1..N, not 0..N-1 as before. This is a more "logical" numbering system.

Respond with the filter name at each prompt. Case counts, so please use B, V, etc., up to 8 characters maximum. If a filter slot is empty, MDM tradition is to enter * (asterisk) for the filter name.

Once misfilter is done, the filter.info file for this run will be created in the proper place.

Note that if the observers requests a filter change during their run, you can run misfilter again to update the MIS filter.info file. There is no need to repeat any of the other steps in the usual startup procedure in that case.

Summary:

This is the short form of the procedure above:

  1. On the MDM 2.4m Observing Workstation 1 in an xterm window ssh to (hiltner) on the MDM 1.3m OBserving Workstation 1 in an xterm window ssh to (mcgraw)
  2. telconfig to build the tel_config file.
  3. misfilter to create the filter.info file.


Return to the MDM Observatory Mountain Webpage
Updated: 2005 August 17 [rwp/osu] Modified 2012 October 18 [Barr/MDM]