Published on CTIO (http://www.ctio.noao.edu/noao)

Inicio > DECam Cookbook

DECam Cookbook

CTIO DECAM COOKBOOK

November 2012
by A. Kunder
 

SETUP

Go to the observer1 station, which is the desk with eight monitors.  It is pictured below.

[1]

At the beginning of your run, you will see DECam GUIs, with a login prompt.
[2]
 

In order to begin taking any images, you must login.  The user name is DECamObserver and the password is the proposal id of the observations taking place.  This password is valid only during the days of the run and will expire automatically afterwards. 

Once you login, a number of windows will pop-up.  These windows can also be accessed here (note that these are only visible if you are on the CTIO network):

http://system1.ctio.noao.edu:7001/apps/ [3]

This is the screen shot of the GUI that you will use to acquire your images with and with which you will operate the system.  More details on the Observer Console GUI can be found here [4].

[5]

First you have to provide information regarding your program. To do this, make sure you are under the System Control tab. 

[6]
 

Click on the Edit button to edit values in the text fields. Click Save where you are done. The values you enter here will be reflected in the primary FITS header of your images. Unless this step is completed, you can not configure DECam.
  • Prop-Id is your NOAO/CTIO proposal Id (eg, 2013A-3013)
  • Under Observers enter the names of the people on shift
  • Program is the name you want to use for this project
  • Proposer is the name of the projects' PI
Now configure SISPI by clicking the Configure button.  Configuration might take 30 seconds to a minute. Check these indicators:
  • Monitor has to be green
  • Interlock has to be green
  • Setup has to be green
  • OCS has to be green and (READY)
  • In the title bar check that DECam is Ready.
  • The vsub and exposure loop indicators can be either green or red at this point.
The Vsub button controls the CCD substrate voltages--press this button to turn this on.

Once all lights are green, as shown below, you are good to go!


[7]

TAKING EXPOSURES--GETTING STARTED

WHERE ARE MY EXPOSURES?

All of your images are copied over to the observer2 console, pictured below.

[8]

They are located in this directory:

/home4/images/fits/2012B-9999

where 2012B-9999 is your proposal ID (replace 2012B-9999 with your proposal ID). 

TAKING AN EXPOSURE

To take an exposure select the Exposure Control view.  

[9]

Select the desired exposure type, time, and filter.  The other fields are optional. 

  • Filter - Select the filter from the pull down menu. Block is the solid metal plate that blocks all light. Pin hole is the metal plate with a single, small hole. When using the exposure form you can not select multiple filters.
  • Time - requested exposure time in seconds
  • Type - Select the exposure type from the pull down menu (e.g. "object").
  • RA - Select the RA type coordinate from the pull down menu. Options include:

    • (Dec) Coordinate - Enter the coordinate in DD:MM or degree format (dec option) or degrees (delta DEC, EL options)
    • (RA) Coordinate - Enter the coordinate in HH:MM or degree format (RA, HA options) or degrees (delta RA, AZ options).
    • AZ (Azimuth). The dec label will change to EL.
    • HA (hour angle)
    • delta RA - choose this for relative coordinates. The dec label will change to delta dec.
  • Count - If set to n the same exposure request will be submitted n times.
  • Object - Name or identifier of the field to be observed.
  • Focus - Enter either a single value to set the focus (hexapod z parameter) or a sequence of six floats separated by commas for the 6 hexapod degrees of freedom (x, y, z, theta, phi, 0) [The last value has to be 0]
  • Exclude - Explicitly disable a DECam component from participating in the exposure. Use carefully!

    • Hexapod - If checked do not adjust the hexapod (excludes both the look up table and the AOS tweaks)
    • Guider - If checked do use ther guider. No corrections will be sent to the TCS.
    • Bcam - If checked do not fire the Bcam. No Bcam information will be sent to the AOS.
    • AOS - If checked the AOS is not used and no tweaks are sent to the hexapod.
  • Comment - Comment to be added to the exposure FITS header.
You can take your desired exposures by (1) adding these to the observing queue by clicking the "Add" button, or
(2) hit the "Expose" button to take the image.  If you add images to the queue, you start running the queue, by hitting "Go".

TEST EXPOSURE
The first image after Vsub is turned on will not usable.  Make sure you take a test exposure (for example, a zero) before trying to acquire any images that are important to you.
ZEROS
Select the exposure type "zero" and specify the quantity of zeros you would like to take.  Hit either the "Expose" button, or add the images to the queue by hitting the "Add" button.  Run the queue by hitting the green "Go" button.
FLATS
Select the exposure type "flat" and specify the quantity of flats you would like to take.  Hit either the "Expose" button, or add the images to the queue by hitting the "Add" button.  Run the queue by hitting the green "Go" button.  The recommended flat exposure times are given below.
 
Filter
Exposure time (seconds)
ADU per pixel
u
15
15000
g
20
15000
r
10
16000
i
22
16000
z
10
19000
Y
10
17000
 
The flat field LED lights will turn on automatically when you take your first flat field image.  They will shut off automatically when the first "object" image is taken.

TAKING EXPOSURES--OBSERVING YOUR TARGETS

Observer support will open the dome 1 hour before sunset to clear the air out of the dome. Important: Vsub must be off and filter mechanism blocked while dome is open until 30 min after sunset.

POINTING

Once ready to observe, ask the night assistant to move to a bright star to zero point the telescope.  Take a 1-second object exposure.  To calculate the offset needed to bring the star to the center, go to the observer2 console (or ssh to observer2).  Open up a terminal and type:

> observer

to run the observer tool (aka "Kent Tools"). Type <commands> to see a list of commands, several of which are described below:

prompt> load <exp num> [ccd-id]

loads the image given by unique exp number, e.g., 149001  and ccd, e.g. "S4" (do not include []'s in cmmand). If no image is given, defaults to the last image delivered.
 

prompt> center <exp num>

center is a useful command that will calculate a RA and DEC offset from the current telescope position as measured from a catalog query and positions of objects on the image "exp num."  You may execute these offsets from the exposure control tab in sispi or ask the operator to execute them. You may ask the operator to make a telescoep zero point after making the offset.


prompt> seeing

This will allow an interactive measurement of the FWHM of a single star on the frame.
 

FOCUS
 
To verify your images are in focus the telescope, display one of the focus and alignment sensor CCDs and check that the zernike terms is appropriate.  To do this, go to a terminal and type:
> observer
> load "" FS1
Note that you can type two double-quotes to load the latest image.  Otherwise replace the two double-quotes with the image number you are interested in.
> plotInit
This makes sure that a plotting window is open
> donutfit [saoDonutGet]
This command will pause - you position the cursor in the center of a donut and left-click.  It should cut out the donut, do a quick fit, and print out some numbers.  The first number of the last line should be something in the range 10-14 and is the radius of the donut in pixels. Images when the telescope is in-focus will have a value around 12.
 
 
 
To manually focus the telescope (not recommened, the automatic focus is working very well), first turn the automatic focus finder off by clicking on the "none" button in the Hexapod gui.

[10]

Then go back to the Observer Console gui, click on the Exposure Control tab, and start the focus procedure by selecting "focus" from the exposure type selection.

[11]

Choose an exposure time of 5-15 seconds and your desired filter (for example, r).  Choose a shift of 30 rows, your desired number of focus steps and your desired focus step size.  An image will be taken of N expsosures (number of focus steps specified), stepping the focus and shifting the charge by a number of rows between each one.  A good focus increment is 75 microns and a good number of focus steps is 7.  Then click the "Add" button.

After the exposure is done reading out, you will see an image containing lines of stars like this. 

[12]

Open a terminal on observer2 and load iraf and mscred by typing:

> cl
vocl> mscred

display the image and run the mscfocus command by typing:

mscred> cd /data_local/images/fits/2012B-9999/
(change 2012B-9999 to your proposal ID)
mscred>!ds9 &
mscred>!funpack DECam_00123456.fits.fz
mscred> mscdisp DECam_00123456.fits 1
vocl> mscfocus DECam_00123456.fits
(change DECam_00123456.fits to the focus image you just took)

You will now select stars to use to calucalate the best focus.  Place the cursor on the top star in a cleanly separated and unsaturated sequence and type the "g" key (always use the top star, regardless of whether or not there is a double step between it and its neighbor).  A window will appear displaying the FWHM as a function of focus for that star.  Type "q", place the cursor on the top star of another column, and type "g" again.  Repeat this sequence for a number of different stars.  With the cursor in the ximtool, finally type "q".  You will now see a window overlaying the focus sequences for all the stars you just measured.  If there are large outlying points, place the cursor on them and type "d", which deletes the whole star associated with that point.  Once you are satisfied, type "q", and the program calculates the best focus for you.

You can also use the command:

mscred> mscexam DECam_00123456.fits

Move the mouse over a star and type "r" and/or "e" to see the radial profise and ellipticity of the star.
 

TAKING SCIENCE OBSERVATIONS

The most efficient way to take your observations is by loading a pre-written script of your desired observations.  Writing scripts for DECam uses a friendly ScriptsEditor tool.

To use this tool, on the observer2 or observer1 console, type:

>setup ScriptsEditor
>ScriptsEditor

Then you can fill out the gui as explained here [13] and save your script. 

You may download the stand alone ScriptsEditor code [13] and install it on your computer.  Python (with Tkinter support) is the only requirement. 

END OF THE NIGHT

  • Important: when done for the night, ensure the Vsub is off, and filter mechanism is in Blocked position.
  • Please fill out the Blanco 4m night report form [14],  username: astronomer; password: check white board in the observing room.
  • Your night lunch form is due at 2:00 PM, but if you don't wake up in time, usually the kitchen staff is merciful.
  • Your observing assistant will close the dome, etc.

TROUBLE SHOOTING

BROKEN SISPI INTERLOCKS
Sometimes the Interlock and OCS lights will turn red, because of a broken interlock.  When this happens, no images can be taken.  If you notice a broken interlock, first visit the "Interlock Viewer" page, which is one of the GUIs up on the observer1 console:

http://system1.ctio.noao.edu:7001/apps/interlock_viewer/ [15]

Click on the SISPI light blue box in the upper half of the page.  This should fill the lower half of the page with SISPI Interlocks.  Make a note of which of the Interlocks is highlighted in red.

1.  OCS Status -- if the OCS Status is the *only* one that is red, go to the Observer Console GUI, click on the System Control tab, and hit the "Refresh" button.

2.  If the OCS Status + Another Process (eg., FCS_STATUS) shows up in red, go to the "Alarm History" page, which is one of the GUIs up on the observer1 console:

http://system1.ctio.noao.edu:7001/apps/alarm_history/ [16]

Identify what the specific alarm is (for example, check the time of the alarm to isolate the alarm that caused the interlock to break).  In most cases, the Alarm History page will provide more details than the Interlock Viewer page. 

Once you have identified the component that has failed, go to the "Architecht Console" page, which is one of the GUIs up on the observer1 console:

http://system1.ctio.noao.edu:7001/apps/architect_console/ [17]

Find the component that has failed on the left side of the page, and highlight it.  Click on the "Full Log" button on the middle, right part of the page.  A terminal will pop up with a log history.  Scroll all the way to the bottom of the terminal and verify that there is indeed a problem with the component.

Then, hit the "restart" button under "Role Control" in the top, right part of the Architect Console.  Make sure that a red cross appears before the component that was just restarted--this means that the restart worked.  Wait a few seconds for the red cross to become a green check mark.

Lastly, go to the Observer Console GUI, click on the System Control tab, and hit the "Configure" button.


SHUTTING DOWN A SISPI INSTANCE VIA ARCHITECT CONSOLE
1.  Go to the Architect Console:

http://system1.ctio.noao.edu:7001/apps/architect_console/ [17]

2.  Find the System Control Box.  Replace the boxes that say:

Component         Device           Command: Press Enter When Complete

with:

ARCHITECT     restart_role             IB1 (or IB2)

TURNING OFF THE LEDS MANUALLY

1.  Go to the Architect Console:

http://system1.ctio.noao.edu:7001/apps/architect_console/ [17]

2.  Find the System Control Box.  Replace the boxes that say:

Component         Device           Command: Press Enter When Complete

with:

DECAL            DECAL            set leds off

RESETTING A FCM TIMEOUT

1.  Go to the Architect Console:

http://system1.ctio.noao.edu:7001/apps/architect_console/ [17]

2.  Find the System Control Box.  Replace the boxes that say:

Component         Device           Command: Press Enter When Complete

with:

ICS                      FCM              get ad

 

Setup

SETUP

Go to the observer1 station, which is the desk with eight monitors.  It is pictured below.

[1]

At the beginning of your run, you will see DECam GUIs, with a login prompt.
[2]
 

In order to begin taking any images, you must login.  The user name is DECamObserver and the password is the proposal id of the observations taking place.  This password is valid only during the days of the run and will expire automatically afterwards. 

Once you login, a number of windows will pop-up.  These windows can also be accessed here (note that these are only visible if you are on the CTIO network):

http://system1.ctio.noao.edu:7001/apps/ [3]

This is the screen shot of the GUI that you will use to acquire your images with and with which you will operate the system.  More details on the Observer Console GUI can be found here [4].

[5]

First you have to provide information regarding your program. To do this, make sure you are under the System Control tab. 

[6]
 

Click on the Edit button to edit values in the text fields. Click Save where you are done. The values you enter here will be reflected in the primary FITS header of your images. Unless this step is completed, you can not configure DECam.
  • Prop-Id is your NOAO/CTIO proposal Id (eg, 2013A-3013)
  • Under Observers enter the names of the people on shift
  • Program is the name you want to use for this project
  • Proposer is the name of the projects' PI
Now configure SISPI by clicking the Configure button.  Configuration might take 30 seconds to a minute. Check these indicators:
  • Monitor has to be green
  • Interlock has to be green
  • Setup has to be green
  • OCS has to be green and (READY)
  • In the title bar check that DECam is Ready.
  • The vsub and exposure loop indicators can be either green or red at this point.
The Vsub button controls the CCD substrate voltages--press this button to turn this on.

Once all lights are green, as shown below, you are good to go!


[7]
 

Taking Exposures: Getting Started

 

TAKING EXPOSURES--GETTING STARTED

WHERE ARE MY EXPOSURES?

All of your images are copied over to the observer2 console, pictured below.

[8]

They are located in this directory:

/data_local/images/fits/2012B-9999

where 2012B-9999 is your proposal ID (replace 2012B-9999 with your proposal ID). 

TAKING AN EXPOSURE

To take an exposure select the Exposure Control view.  

[9]

Select the desired exposure type, time, and filter.  The other fields are optional. 

  • Filter - Select the filter from the pull down menu. Block is the solid metal plate that blocks all light. Pin hole is the metal plate with a single, small hole. When using the exposure form you can not select multiple filters.
  • Time - requested exposure time in seconds
  • Type - Select the exposure type from the pull down menu (e.g. "object").
  • RA - Select the RA type coordinate from the pull down menu. Options include:

    • (Dec) Coordinate - Enter the coordinate in DD:MM or degree format (dec option) or degrees (delta DEC, EL options)
    • (RA) Coordinate - Enter the coordinate in HH:MM or degree format (RA, HA options) or degrees (delta RA, AZ options).
    • AZ (Azimuth). The dec label will change to EL.
    • HA (hour angle)
    • delta RA - choose this for relative coordinates. The dec label will change to delta dec.
  • Count - If set to n the same exposure request will be submitted n times.
  • Object - Name or identifier of the field to be observed.
  • Focus - Enter either a single value to set the focus (hexapod z parameter) or a sequence of six floats separated by commas for the 6 hexapod degrees of freedom (x, y, z, theta, phi, 0) [The last value has to be 0]
  • Exclude - Explicitly disable a DECam component from participating in the exposure. Use carefully!

    • Hexapod - If checked do not adjust the hexapod (excludes both the look up table and the AOS tweaks)
    • Guider - If checked do use ther guider. No corrections will be sent to the TCS.
    • Bcam - If checked do not fire the Bcam. No Bcam information will be sent to the AOS.
    • AOS - If checked the AOS is not used and no tweaks are sent to the hexapod.
  • Comment - Comment to be added to the exposure FITS header.
You can take your desired exposures by (1) adding these to the observing queue by clicking the "Add" button, or
(2) hit the "Expose" button to take the image.  If you add images to the queue, you start running the queue, by hitting "Go".

TEST EXPOSURE
The first image after Vsub is turned on will not usable.  Make sure you take a test exposure (for example, a zero) before trying to acquire any images that are important to you.
ZEROS
Select the exposure type "zero" and specify the quantity of zeros you would like to take.  Hit either the "Expose" button, or add the images to the queue by hitting the "Add" button.  Run the queue by hitting the green "Go" button.
FLATS
Select the exposure type "flat" and specify the quantity of flats you would like to take.  Hit either the "Expose" button, or add the images to the queue by hitting the "Add" button.  Run the queue by hitting the green "Go" button.  The recommended flat exposure times are given below.
 
Filter
Exposure time (seconds)
ADU per pixel
u
15
15000
g
20
15000
r
10
16000
i
22
16000
z
10
19000
Y
10
17000
 
The flat field LED lights will turn on automatically when you take your first flat field image.  They will shut off automatically when the first "object" image is taken.

 

Taking Exposures: Observing Your Targets

TAKING EXPOSURES--OBSERVING YOUR TARGETS

Observer support will open the dome 1 hour before sunset to clear the air out of the dome. Important: Vsub must be off and filter mechanism blocked while dome is open until 30 min after sunset.

POINTING

Once ready to observe, ask the night assistant to move to a bright star to zero point the telescope.  Take a 1-second object exposure.  To calculate the offset needed to bring the star to the center, go to the observer2 console (or ssh to observer2).  Open up a terminal and type:

> observer

to run the observer tool (aka "Kent Tools"). Type <commands> to see a list of commands, several of which are described below:

prompt> load <exp num> [ccd-id]

loads the image given by unique exp number, e.g., 149001  and ccd, e.g. "S4" (do not include []'s in cmmand). If no image is given, defaults to the last image delivered.
 

prompt> center <exp num>

center is a useful command that will calculate a RA and DEC offset from the current telescope position as measured from a catalog query and positions of objects on the image "exp num."  You may execute these offsets from the exposure control tab in sispi or ask the operator to execute them. You may ask the operator to make a telescope zero point after making the offset.


prompt> seeing

This will allow an interactive measurement of the FWHM of a single star on the frame.
 

FOCUS
 
To verify your images are in focus the telescope, display one of the focus and alignment sensor CCDs and check that the zernike terms is appropriate.  To do this, go to a terminal and type:
> observer
> load "" FS1
Note that you can type two double-quotes to load the latest image.  Otherwise replace the two double-quotes with the image number you are interested in.
> plotInit
This makes sure that a plotting window is open
> donutfit [saoDonutGet]
This command will pause - you position the cursor in the center of a donut and left-click.  It should cut out the donut, do a quick fit, and print out some numbers.  The first number of the last line should be something in the range 10-14 and is the radius of the donut in pixels. Images when the telescope is in-focus will have a value around 12.
 
To manually focus the telescope, first turn the automatic focus finder off by clicking on the "none" button in the Hexapod gui.

[10]

Then go back to the Observer Console gui, click on the Exposure Control tab, and start the focus procedure by selecting "focus" from the exposure type selection.

[11]

Choose an exposure time of 5-15 seconds and your desired filter (for example, r).  Choose a shift of 30 rows, your desired number of focus steps and your desired focus step size.  An image will be taken of N expsosures (number of focus steps specified), stepping the focus and shifting the charge by a number of rows between each one.  A good focus increment is 75 microns and a good number of focus steps is 7.  Then click the "Add" button.

After the exposure is done reading out, you will see an image containing lines of stars like this. 

[12]

Open a terminal on observer2 and load iraf and mscred by typing:

> cl
vocl> mscred

display the image and run the mscfocus command by typing:

mscred> cd /data_local/images/fits/2012B-9999/
(change 2012B-9999 to your proposal ID)
mscred>!ds9 &
mscred>!funpack DECam_00123456.fits.fz
mscred> mscdisp DECam_00123456.fits 1
vocl> mscfocus DECam_00123456.fits
(change DECam_00123456.fits to the focus image you just took)

You will now select stars to use to calucalate the best focus.  Place the cursor on the top star in a cleanly separated and unsaturated sequence and type the "g" key (always use the top star, regardless of whether or not there is a double step between it and its neighbor).  A window will appear displaying the FWHM as a function of focus for that star.  Type "q", place the cursor on the top star of another column, and type "g" again.  Repeat this sequence for a number of different stars.  With the cursor in the ximtool, finally type "q".  You will now see a window overlaying the focus sequences for all the stars you just measured.  If there are large outlying points, place the cursor on them and type "d", which deletes the whole star associated with that point.  Once you are satisfied, type "q", and the program calculates the best focus for you.

You can also use the command:

mscred> mscexam DECam_00123456.fits

Move the mouse over a star and type "r" and/or "e" to see the radial profise and ellipticity of the star.
 

TAKING SCIENCE OBSERVATIONS

The most efficient way to take your observations is by loading a pre-written script of your desired observations.  Writing scripts for DECam uses a friendly ScriptsEditor tool.

To use this tool, on the observer2 or observer1 console, type:

>setup ScriptsEditor
>ScriptsEditor

Then you can fill out the gui as explained here [13] and save your script. 

You may download the stand alone ScriptsEditor code [13] and install it on your computer.  Python (with Tkinter support) is the only requirement. 

 

Troubleshooting

TROUBLE SHOOTING

BROKEN SISPI INTERLOCKS
Sometimes the Interlock and OCS lights will turn red, because of a broken interlock.  When this happens, no images can be taken.  If you notice a broken interlock, first visit the "Interlock Viewer" page, which is one of the GUIs up on the observer1 console:

http://system1.ctio.noao.edu:7001/apps/interlock_viewer/ [15]

Click on the SISPI light blue box in the upper half of the page.  This should fill the lower half of the page with SISPI Interlocks.  Make a note of which of the Interlocks is highlighted in red.

1.  OCS Status -- if the OCS Status is the *only* one that is red, go to the Observer Console GUI, click on the System Control tab, and hit the "Refresh" button.

2.  If the OCS Status + Another Process (eg., FCS_STATUS) shows up in red, go to the "Alarm History" page, which is one of the GUIs up on the observer1 console:

http://system1.ctio.noao.edu:7001/apps/alarm_history/ [16]

Identify what the specific alarm is (for example, check the time of the alarm to isolate the alarm that caused the interlock to break).  In most cases, the Alarm History page will provide more details than the Interlock Viewer page. 

Once you have identified the component that has failed, go to the "Architecht Console" page, which is one of the GUIs up on the observer1 console:

http://system1.ctio.noao.edu:7001/apps/architect_console/ [17]

Find the component that has failed on the left side of the page, and highlight it.  Click on the "Full Log" button on the middle, right part of the page.  A terminal will pop up with a log history.  Scroll all the way to the bottom of the terminal and verify that there is indeed a problem with the component.

Then, hit the "restart" button under "Role Control" in the top, right part of the Architect Console.  Make sure that a red cross appears before the component that was just restarted--this means that the restart worked.  Wait a few seconds for the red cross to become a green check mark.

Lastly, go to the Observer Console GUI, click on the System Control tab, and hit the "Configure" button.

TURNING OFF THE LEDS MANUALLY
1.  Go to the Architect Console:

http://system1.ctio.noao.edu:7001/apps/architect_console/ [17]

2.  Find the System Control Box.  Replace the boxes that say:

Component         Device           Command: Press Enter When Complete

with:

DECAL            DECAL            set leds off

End Of Night

END OF THE NIGHT

  • Important: when done for the night, ensure the Vsub is off, and filter mechanism is in Blocked position.
  • Please fill out the Blanco 4m night report form [14],  user: astronomer; password: check white board in the observing room.
  • Your night lunch form is due at 2:00 PM, but if you don't wake up in time, usually the kitchen staff is merciful.
  • Your observing assistant will close the dome, etc.

 

Source URL (retrieved on 02/09/2013 - 07:11): http://www.ctio.noao.edu/noao/es/content/DECam-Cookbook

Links:
[1] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/control_room1a.JPG
[2] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/login.jpg
[3] http://system1.ctio.noao.edu:7001/apps/
[4] https://cdcvs.fnal.gov/redmine/projects/sispi/wiki/ObsGUI
[5] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/ObsConGreen.png
[6] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/ObsCons1a.png
[7] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/system_status1.jpg
[8] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/photoA.JPG
[9] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/exp_control.jpg
[10] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/hexapod.jpg
[11] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/focus.jpg
[12] http://www.ctio.noao.edu/noao/sites/default/files/decam/Images/focus_0.jpg
[13] https://cdcvs.fnal.gov/redmine/projects/sispi/wiki/ScriptsEditor
[14] http://www.ctio.noao.edu/noao/node/add/night-report
[15] http://system1.ctio.noao.edu:7001/apps/interlock_viewer/
[16] http://system1.ctio.noao.edu:7001/apps/alarm_history/
[17] http://system1.ctio.noao.edu:7001/apps/architect_console/