This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:documentation [2011/06/03 01:15] yme |
operations:documentation [2012/01/30 21:59] Jim Lovell [Background] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Operator Documentation ====== | ====== Operator Documentation ====== | ||
- | ===== Observations on the Hobart 12m ===== | ||
- | <note>The Hobart 12m is now using the following computers for observations:\\ | ||
- | PC Field System: pcfshb.phys.utas.edu.au\\ | ||
- | Mark5B+ recorder: mk5ya.phys.utas.edu.au</note> | ||
- | Bring up VNC sessions on the Yarragadee field system, timing PC and DBBC. This can be done via the Application menu in | + | ===== Background ===== |
+ | * [[http://auscope.phys.utas.edu.au|About the AuScope VLBI Project]] | ||
+ | * Operator {{:operations:auscope_operator_training.pdf|training documentation}} (PDF). | ||
+ | * [[operations:background_hardware|Overview of the telescopes and related hardware]] | ||
+ | * [[operations:acronyms|Acronym dictionary]] | ||
- | the top right of the desktop: | + | ===== Observations on the 12m telescopes from the Control Room ===== |
+ | |||
+ | These are notes on IVS observations from ops4, the four-monitor PC in the AuScope VLBI Operations room in Hobart. | ||
+ | |||
+ | The main control interface during an observation is eControl, which communicates with the PC Field System (PCFS) machines at the observatories. All the computers at the observatories have manes ending with their two-letter telescope ID: | ||
+ | * Hb = Hobart 12m | ||
+ | * Ke = Katherine | ||
+ | * Yg = Yarragadee | ||
+ | There are four computers at each site that run the most important items of hardware or software. They are: | ||
+ | |||
+ | ^Type ^ Function ^ Computer Name ^^^ Access with... ^ | ||
+ | ^ ^ ^ Hobart ^ Katherine ^ Yarragadee ^ ^ | ||
+ | |PC Field System | Linux PC that runs Field System software to control the antenna, DBBC and Mark5 | pcfshb | pcfske | pcfsyg | ssh, VNC (display 1) | | ||
+ | |Mark5 recorder | A Linux PC inside the Mark5 recorder which runs dimino, a program the PCFS communicates with to control data recording | mk5hb | mk5ke | mk5yg | ssh | | ||
+ | |Timing PC | Windows PC that monitors the H maser, the CNS-II GPS clock, shows the wind speed and direction, and runs HMI: a GUI for controlling and monitoring the antenna | timehb | timeke | timeyg | VNC display 0| | ||
+ | |DBBC | A Windows PC in the DBBC which runs a server (and optionally a client) program to allow control and monitoring of the DBBC | dbbchb | dbbcke | dbbcyg | VNC display 0| | ||
+ | |||
+ | Each of the above can be accessed either through a terminal via ssh or by starting up a VNC session. It is necessary to bring up the VNC sessions when setting up for an observation or when doing one of the regular ~2 hourly system checks. Given the slow network connection to Yarragadee it is not recommended to keep the VNC sessions up at other times. | ||
+ | |||
+ | VNC or terminal sessions can be started via the Application menu on ops4 in the top left of the desktop: | ||
Applications -> AuScope Yarragadee -> VNC -> [choose the server] | Applications -> AuScope Yarragadee -> VNC -> [choose the server] | ||
+ | {{:operations:ops4applicationsmenu.jpg|}} | ||
- | The Hobart 12m observations are usually set up in a VNC session on pcfshb:1. To view this page: | + | VNC sessions can also be started up on the command line. e.g: |
<code> | <code> | ||
vncviewer -shared pcfshb:1 | vncviewer -shared pcfshb:1 | ||
+ | vncviewer -shared dbbcke:0 | ||
</code> | </code> | ||
- | The status of the 12m controller can be seen via the HMI display on 131.217.63.225. To view this: | + | |
- | <code> | + | |
- | vncviewer -shared 131.217.63.225:0 | + | |
- | </code> | + | |
- | The DBBC for this antenna is running on the KVM and via a VNC session. To view and control the DBBC: | + | |
- | <code> | + | |
- | vncviewer -shared 131.217.63.248:0 | + | |
- | </code> | + | |
==== IVS Observations ==== | ==== IVS Observations ==== | ||
Line 29: | Line 43: | ||
If it has not already been done, it may be necessary to prepare the schedule and procedure files. This is usually done well in advance, but here are the instructions: | If it has not already been done, it may be necessary to prepare the schedule and procedure files. This is usually done well in advance, but here are the instructions: | ||
* [[operations:documentation.ivs.drudg|Preparing the schedule and procedure files]] | * [[operations:documentation.ivs.drudg|Preparing the schedule and procedure files]] | ||
+ | * [[operations:documentation.ivs.drudg_ureop|Additional schedule preparation for Hb ultra-rapid EOP experiments]] | ||
The Digital Base-Band Converter (DBBC) takes the IF signals from the telescope and digitises them for the Mark5 recorder. The DBBC needs to be properly configured prior to an observation: | The Digital Base-Band Converter (DBBC) takes the IF signals from the telescope and digitises them for the Mark5 recorder. The DBBC needs to be properly configured prior to an observation: | ||
* [[operations:documentation.DBBCSetupIVS|Configuring the DBBC]] | * [[operations:documentation.DBBCSetupIVS|Configuring the DBBC]] | ||
Next the Mark5 recorder needs to be prepared for the observations. | Next the Mark5 recorder needs to be prepared for the observations. | ||
* [[operations:documentation.ivs.mark5|Mark5B recorder setup]] | * [[operations:documentation.ivs.mark5|Mark5B recorder setup]] | ||
+ | Lastly, check that the software on the timing PCs is running | ||
+ | * [[operations:documentation.ivs.timingsw|Software on the timing PC]] | ||
+ | |||
=== Starting and Monitoring === | === Starting and Monitoring === | ||
- | * [[operations:monitoring_hb|Starting and Monitoring the observations]] | + | |
- | * Alarms are currently provided by the pmSTALM scripts. This is described [[operations:documentation.pmstalm| here]]. Or you can try out the new [[operations:documentation.logmonitor| log monitor]]. | + | * [[operations:starting_monitoring|Starting an monitoring the observations]] |
+ | * [[operations:starting_monitoring_urEOP|Additional tasks prior to starting Ultra-rapid EOP observations]] | ||
=== After the Observations === | === After the Observations === | ||
Line 52: | Line 72: | ||
* [[operations:documentation.fringe.correlation|Correlation]] | * [[operations:documentation.fringe.correlation|Correlation]] | ||
- | |||
- | ===== Observations on the Yarragadee 12m ===== | ||
- | |||
- | Setting up for a Yarragadee observation. | ||
- | |||
- | This can be done from ops4, the 4-monitor PC in the control room. | ||
- | |||
- | 1. Bring up VNC sessions on the Yarragadee field system, timing PC and DBBC. This can be done via the Application menu in | ||
- | |||
- | the top right of the desktop: | ||
- | Applications -> AuScope Yarragadee -> VNC -> [choose the server] | ||
- | |||
- | 2. Configure the DBBC. The procedure is the same as for Hobart but the DBBC control software is a newer version with two | ||
- | windows, one client window for commands and one server for responding to commands and logging results. To start it up, you need to start the ''DBBC Control net.exe'' program first (shortcut is on the desktop, upper RHS). To get the control interface, you then run ''DBBC Client.exe''. The command syntax is unchanged for this versionof the DBBC software. | ||
- | |||
- | 3. Set up the Mark5 is the same way as for Hobart. The only differences are: | ||
- | * The mark5 PC is called mk5yg | ||
- | * If dimino needs starting, do it via a terminal window in the pcfsyg VNC session. That way if the network goes down, dimino will continue to run | ||
- | |||
- | 4. Start the observations in the same way as Hobart, except the schedule name will end in yg instead of hb. e.g. | ||
- | schedule=r4455yg,#1 | ||
- | |||
- | 5. Start up a checklist GUI on ops4: | ||
- | Applications -> AuScope Yarragadee -> Checklist GUI | ||
- | |||
- | 6. Start econtrol | ||
- | Applications -> AuScope Yarragadee -> econtrol | ||
- | |||
- | Click on the boxes next to “StatusMonitor" and "Logging and Operator Input”. This should trigger the program to connect to pcfsyg and you’ll see a status window and log window. If you don't see any information updating in the status window, type [ctrl]-[shift]-e to start the server process on the field system. You can send PCFS commands and comments from the bottom of the log window. Note you won’t see the log window update until the next scheduled command is sent. | ||
- | |||
- | |||
- | 7. It's best to only have the Yarragadee VNC sessions running when running through the checklist and to rely on econtrol | ||
- | and pmSTALM the rest of the time. Otherwise a lot of network bandwidth is used which can be expensive if it has to go through the Telstra 3G link. You should use the VNC sessions to check that the autocorrelation spectra are ok though. | ||
- | |||
- | 8. Alarms are currently provided by the pmSTALM scripts. This is described [[operations:documentation.pmstalm| here]]. Or you can try out the new [[operations:documentation.logmonitor| log monitor]]. | ||
- | |||
- | 9. At the end, email the operator at Yarragadee to let him know the observation is finished and the telescope has gone to stow. | ||
- | moblas@midwest.com.au | ||