
ATF New Checklist Submission
System Software Startup Database - View Selected Update
Back to the ATF Checklist for Software Database - Main Page
Below is the set of notes/checklist based on the PID number that you requested:
Name: Rob Reid
Email: rreid@nrao.edu
Date/Time: 2007-10-11 18:14:48
Description/Title: System software startup checklist
Checklist Update:
Preliminaries
I recommend you use 2 konsole terminals. Depending on what you will be
doing, you may want them very wide (across 2 screens), with the
"Vertexish" at the top of the display, and the "AECish" one below.
Whenever you need another shell, click on the
yellow-asterisk-above-two-white-tabs icon in the bottom left corner of
a konsole, to create a new tab. Tabs can (and should) be renamed by
right clicking on them.
$> bla bla bla => Type "bla bla bla" in a regular shell terminal.
PSI> bla bla bla => Type "bla bla bla" into psi.
Vx => Vertex = ALMA01, on your right.
AEC => Alcatel = ALMA02, on your left.
The list
-1. Login at the operator's console as yourself.
0. Start VNC:
vncviewer -shared oper01:2
Type password: You should know it, but email/call the on-call person or
Debra Shepherd, dshepher at aoc.nrao.edu if needed. Hint: open your
eyes, and don't use a hyphen.
VNC should start a OMC session (runOMC) automatically. It if asks "Seems the ACS is down...do you want to ...", answer yes.
Wait for containers to go green.
- 28/09/2007: All CCC containers for the Correlator will stay
down (RED).
Click Operational
All subsystems should go to Operational (green).
- 10/11/2007: I think the 9/28/2007 problem has been fixed.
- 28/09/2007: CORR Subsystems is not coming up, and won't come up.
This prevents the whole system to coming up. Need to
Restart the correlator: http://aivwiki.alma.cl/index.php/Correlator_Restart_after_CCC_hung
Note you must try ssh the computer (ssh cob-cc) before Restarting the CORR/CCC containers
(should add this step in the AIVTwiki pages. If you can sshto cob-cc, it is ok to restart
the containers (ping only it is not a sign that the computer is working. Also note the containers
should be restarted from top to bottom, in the order they appear in the ACS tree).
Iconify the VNC window - it's just in case you need remote assistance
from the on-call person. If you want to kill it, press Ctrl-C in the
shell where you started it. The OMC will keep running.
1.
$> runOMC
It will pop up a box asking "Bring the system to operational now?". Answer NO, since it is already running in VNC.
2. Login on the Windows machine (snickers) as ATFoper.
Click on the IFP-BB TPD monitor icon twice.
Right now they should both be monitoring Vx.
In the left one, change MID to 2, hit MainProgramStop, then click on
the white arrow in the upper left corner. It should start monitoring
AEC's baseband voltages.
Both antennas should have voltages roughly around 1V, but they need not
all have the same average level. Note that they saturate at 2.5V.
In case of voltage problems,
$> PSI
or,
$> cd /groups/psi/Public_PSI
$> ./psi
PSI> rs sus
"rs" means "run script" and "rs sus" restarts the electronics. Rename
that tab to PSI. Set the observing frequency to 104 GHz (the ~500 THz
default is the optical pointing telescope):
PSI> rs csib104l
Shrink the line interval in the V displays then reexpand it to reset the V display scale.
3. Create Array
Make the container window in runOMC bigger.
$> mountPanel
$> mountPanel
For each one, File->Select Mount, and choose ALMA01, then ALMA02.
4. Open a new shell (tab). In it,
$> objexp
In the object explorer that pops up, go to
NewMountController->CONTROL/ALMA01. Click on SetObservingFrequency
and enter 104.1e9 (i.e. the observing frequency in Hz). Repeat for
CONTROL/ALMA02.
5. To clear antenna faults (if there are any), see Antonio Hales' version of this checklist.
6. Start the weather monitor, or check that it is running:
$> ~mzambran/pyWEATHER
You should see a listing of pressure, temperature and dew-point from
the VLA weather station. Ctrl-C to stop (it will keep running).
7. Start the alarm monitor
PSI> rs art
8. Check the refraction coefficients.
objexp->CONTROL/ALMA01/MountController->getRefractionCoefficients
Repeat for ALMA02.
a = 2.5e-4 and b = -2.5e-7 are reasonable. The antennas may slightly
differ from each other because each one's refraction coefficients are
only updated when the antenna changes source.