Contents
Adsec Setup
Pointing Setup
Misc Utilities
Acquiring a Target
Point to a Star
Align Star on WFS
Closing AO Loop
Optimize Gain
Manual Intervention
Manual Gain Tuning
Shutdown
Troubleshooting
Important Features of Room N507
Overview
You will, in general, be running the LBTI AO system from either the remote observing room (N507) in Tucson, or the control room at the telescope. The remote room computers have been set up with aliases for common LBTI-AO operations. The computers on the mountain haven't yet, simply because we're not often up there. Both versions are covered in the instructions below.
​
The aliases on the 507 machines live in /home/lbtieng/.lbti, and can be changed/added to by editing that file. The file is sourced every time a new terminal window is opened, on any lbtieng@rm507 machine.
​
In the remote room are 5 LBTO workstations, plus Phil's special table with special Mac. The workstations are numbered rm507-1 through rm507-5, in a zigzag fashion. Unless you have some special reason, run SX AO on 507-5 (six-monitor display beneath the weather monitor) and DX AO on 507-3 (six-monitor display beneath the alarms monitor). This isn't mandatory -- all workstations can run the LBTI accounts -- but it's a useful convention. If you decide to move them, at least keep SX to the left of DX or there will be wailing and gnashing of teeth.
Setup
Computer Setup
Login to your workstation as LBTIeng ("LBTI Engineering" in the list). If it isn't in the list, try typing LBTIeng in the "Other" box. Password hint : it includes, but is not limited to, one number, one capital letter, and one punctuation mark.
​
Note: On the rm507 and obs machines, if you highlight text with your mouse, you can then paste it anywhere using middle-mouse-click. Useful for the commands below.
1. Set Up Terminal Windows
a. Open tabs
Open a terminal (right click-->"open in terminal").
At the prompt, type lbti-tabs to open another terminal window with four color-coded tabs. (If it doesn't work, open four tabs manually.)
b. Connect from tabs
The dark blue tab is for the wavefront sensor machine. At the prompt, type
​
go_sxwfs
​
or
​
go_dxwfs
​
If prompted, enter the password. Password hint: same pattern as other machines named lbti-<something>.
Equivalently, or from the mountain, use ssh -YC root@lbti-sxwfs or ssh -YC root@lbti-dxwfs .
​
​
The dark red tab is for the adaptive secondary machine. At the prompt, type
go_sxadsec
or
go_dxadsec
​
If prompted, enter the password. Password hint: a thematically-appropriate word with numbers for vowels.
Equivalently, or from the mountain, use ssh -YC AOeng@sxadsec or ssh -YC AOeng@dxadsec .
The light blue tab is for connecting to a mountain obs machine. If you're already on the mountain, leave it as a local terminal. From the remote room, type
go_obs3
if you're running SX or
go_obs4
for DX.
If prompted, enter the same password you used to login to the workstation here.
Equivalently, ssh -XC lbtieng@obs3 or obs4.
The final black tab can be used as a local terminal.
2. Set Up Browsers
The LBTI web GUIs should be run from Chrome, not Firefox. From your local terminal -- not the pretty colored ones --open a Chrome window using lbti-chrome &
(If that didn't work, type 'source .lbti' and try again.)
In Chrome, go to http://lbti-web:8080 to access many LBTI controls.
There's a read-only version at http://lbti.as.arizona.edu:8081. You'll need a login name and password for that one, but it's useful for spying on the science cameras without fear of accidentally pushing the wrong button.
Open three Chrome tabs with the following:
1. the base lbti-web page (http://lbti-web:8080)
2. the relevant AO Operations page ( for SX: http://lbti-web:8080/ao/ao-ops.html?sx ; for DX: http://lbti-web:8080/ao/ao-ops.html?dx)
( or, from lbti-web:8080 --> "Observing Tools" Menu --> AO --> [SX | DX] Operations)
3. the relevant AO Diagnostics page
(for SX: http://lbti-web:8080/ao/ao-diag.html?sx)
(for DX: http://lbti-web:8080/ao/ao-diag.html?dx)
(from the lbti-web:8080 menu, AO --> [SX | DX] Diagnostics)
WFS Setup
1. Power On Hardware
LBTI controls its own WFS hardware power, but doesn't control the adsec's. We often, but not always, leave the WFS powered on for the duration of the run, so you may find that these are already on. In that case, just verify that the correct ones are powered.
You'll find power controls on lbti-web, under Engineering Tools --> Pulizzis. DX has a single "pulizzi" rack; SX has two until its single one can be fixed. Click the grey oblong to toggle power.
These channels should remain always on, for both sides:
[SX | DX] Cooling Heat Exchanger
[SX | DX] Network Switch
This channel should be switched on with care to make sure you're clicking the right one. It needs to say "WFS" in the name. Leave the SPC/FPC ones alone!
[SX | DX] PI WFS Tip-Tilt Controller
These channels should be turned on if they aren't already:
Cube and Translation Stages
Bayside Zenus Motor Power
JENA Camera Lens
ADAM Power, Port Server #2
ADC/FIlter wheel Power
CCD47 Tray Power
CCD39 Tray and Port Server #1
This channel should be off for nighttime observing:
Arcetri Source
​
From the dark blue WFS terminal, check for communication with port servers (PS) using ping -- type 'ping ' and then either the name or the IP address of each port server:
ping ts839sx
and
ping ts847sx
or
ping ts839dx
and
ping ts847dx
If you've just powered the port servers on, they will take around 30-60sec to come up. If they are still unresponsive after a minute, power cycle the global switch/PS2 channel. If still unresponsive also cycle the PS1 channel. If still unresponsive, repeat. May take 2 or 3 tries on SX (for unknown reasons).
​
The port server IP addresses are
SX = 192.168.154.15 and 192.168.154.22
DX = 192.168.153.12 and 192.168.153.13
You can see a list of IP addresses if you use the command 'cat /etc/hosts' in a wfs terminal.
2. Start WFS Software Suite
a. Start WFS processes
From the WFS terminal, type 'w_check'. A list of processes and their statuses will come up.
If they all say "NOT running", type 'w_start'. If most of them say "running and connected to MsgD", leave them alone.
b. Open WFS GUI-Launcher
From the WFS terminal, type 'startAO.py &'.
A small GUI window will pop up. This is the "mother" GUI for the many WFS control panels, so keep it open.
c. Launch WFS Engineering-Level GUIs
Click the relevant buttons on the GUI-Launcher:
WFS Arbitrator GUI
WFS HW GUI
System Processes