To avoid user collision, direct interaction with the instrument is typically limited to a single IDL session running in a Virtual Network Computing (VNC) session. While the instrument was at UCSC, this session ran on computer gpi-dhcp-17-33.ucolick.org, commonly reffered to as 1733. At Gemini, the VNC sessions are hosted on three virtual machines (VMs), cpogpi01, cpogpi02, and cpogpi03 under user software.
Currently we use VNCs primarily on cpogpi01 and cpogpi02. See table below, and Working Setup for more details.
|Computer||VNC session number||Use/Purpose||Connect via:|
|cpogpi01||33||gpilib IDL control||cpogpi01:5933|
|cpogpi02||42||data reduction pipeline||cpogpi02:5942|
|cpogpi03||53||additional spare data reduction pipeline||cpogpi03:5953|
How to connect to these VNCs depends on what operating system you are using, and on whether you are starting from a computer already on the summit network or need to pass through the Gemini firewall. See VNC Setup and Connecting.
The remainder of this documentation assumes you have already successfully connected and opened, at minimum, the cpogpi01:5917, cpogpi01:5933, and cpogpi02:5940 VNC sessions.
The VNC on screen 17 is intended to be a shared resource for all team members to see instrument and AO system status and is not intended for direct interaction. You should only connect to screen 17 with the ‘view only’ option set.
The status display VNC (screen 17) contains a number of useful diagnostic displays and outputs including:
These displays are all automatically started by running script standardsetup located in the software user’s home directory:
This script also opens the CAL and AOC logs in the second workspace. A copy of this script is included below for reference.
Within the control VNC session (screen 33), you will want to start an IDL session (by running idl from the command line) . Typically, you will want to start IDL from directory /home/software/IDL/gpilib, however, if you are going to be running your own scripts that are not part of gpilib then start IDL in your script directory (or change to that directory with the cd command from the IDL session).
Optionally, you may also want to see the logged output from the various subsystems (see Log Files for details on log locations). To display a log in real time, use:
> tail -n 100 -f filename
The status VNC session has the CAL, AOC and TLC log files in the third workspace, but these are inaccessible if you have connected with viewOnly set.
Finally, in the TLC GUI session (screen 40) open the TLC GUI. Open an SSH connection to the TLC with tunneling (ssh -Y gpi@tlc; also aliased to tlc on cpogpi01). Run the gui command to bring up the TLC GUI.
In addition to gpidiagram, you can use the graphical display built into the TLC GUI (accessed with the ‘Overall Status’ button). This updates much faster than gpidiagram but presents a more schematic view of the system.
The status GUI is fairly resource intensive. You probably don’t want to run too many of these at one time (keeping one open in a shared VNC is a good way to go).
The GPI pipeline is typically run on a separate VNC on cpogpi02. To start the pipeline, run gpi-pipeline from a terminal. For details, please see the pipeline documentation (http://docs.planetimager.org/pipeline).
This is what the standardsetup script does to start the status displays on VNC cpogpi01:17.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
#!/bin/bash #------------------------------------------------------ #Close all windows wmctrl -c 'aoc:dispraw' wmctrl -c 'aoc:dispwfr' wmctrl -c 'aoc:disptwt' wmctrl -c 'aoc:dispint' wmctrl -c 'aoc:dispstat' wmctrl -c 'cal:show' wmctrl -c 'GPI System Diagram 01' wmctrl -c 'aoc:log' wmctrl -c 'cal:log' wmctrl -c 'tlc:log' wmctrl -c 'tlc:sensors' sleep 2 #------------------------------------------------------ #Start all windows wmctrl -s 0 xterm -geometry 25x5 -T 'aoc:dispraw' -e ssh -Y gpi@aoc \ /home/gpi/gpi_root/aoc/bin/dispraw -p 4 & xterm -geometry 1600x10+0+1000 -T 'aoc:dispstat' -e ssh -t gpi@aoc \ /home/gpi/gpi_root/aoc/bin/dispstat & xterm -geometry 25x5 -T 'aoc:dispwfr' -e ssh -Y gpi@aoc \ /home/gpi/gpi_root/aoc/bin/dispwfr & xterm -geometry 25x5 -T 'aoc:disptwt' -e ssh -Y gpi@aoc \ /home/gpi/gpi_root/aoc/bin/disptwt & xterm -geometry 25x5 -T 'aoc:dispint' -e ssh -Y gpi@aoc \ /home/gpi/gpi_root/aoc/bin/dispint & xterm -geometry 125x25+1200+550 -T 'cal:show' -e ssh -t gpi@cal \ /home/gpi/gpi/cal/bin/linux64/calshow -dolphinGmb & sleep 2 # Stuff on the 4th virtual screen: Sensors wmctrl -s 3 xterm -geometry 25x5 -T 'tlc:sensors' -e ssh -Y gpi@tlc \ /data/gpitlc/dev/gpi/current/rel/source/tlc/scripts/gpGuiStartSensorSum.csh & sleep 2 # Stuff on the 2nd virtual screen: Logs wmctrl -s 1 xterm -geometry 100x60+0+0 -T 'aoc:log' -e ssh gpi@aoc \ /home/gpi/gpi_root/aoc/bin/showlatestlog & xterm -geometry 100x60+630+0 -T 'cal:log' -e ssh gpi@cal \ /home/gpi/showlatestlog & xterm -geometry 100x60+1260+0 -T 'tlc:log' -e ssh gpi@tlc \ /home/gpi/showlatestlog & sleep 2 # Stuff on the 3rd virtual screen: #wmctrl -s 2 #sleep 2 # Jump back to first virtual screen wmctrl -s 0 /gemsoft/opt/gpi/ifspython/gpidiagram.py 5 --pos 1500 0 & wmctrl -r 'GPI System Diagram' -N 'GPI System Diagram 01'