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_ops2 [2012/08/15 04:36] Jim Lovell [Before the Observations] |
operations:documentation_ops2 [2012/09/04 06:05] Jim Lovell [Before the Observations] |
||
---|---|---|---|
Line 10: | Line 10: | ||
These are notes on IVS observations from ops2, the six-monitor PC in the AuScope VLBI Operations room in Hobart. | These are notes on IVS observations from ops2, the six-monitor PC in the AuScope VLBI Operations room in Hobart. | ||
- | The main control interface during an observation is [[http://www.econtrol-software.de/|e-Remote Control]], which communicates with the PC Field System (PCFS) machines at the observatories. All the computers at the observatories have names ending with their two-letter telescope ID: | + | If you are unfamiliar with the computers and software used at the sites and in the control room, please read this before continuing: |
- | * Hb = Hobart 12m | + | * [[[[operations:documentation:computers_software|Introductory notes on computers and software]] |
- | * 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 ops2 in the top left of the desktop. e.g. for Yarragadee: | + | |
- | Applications -> AuScope Yarragadee -> VNC -> [choose the server] | + | |
- | {{:operations:ops4applicationsmenu.jpg?500|}} | + | |
- | + | ||
- | VNC sessions can also be started up on the command line. e.g: | + | |
- | <code> | + | |
- | vncviewer -shared pcfshb:1 | + | |
- | vncviewer -shared dbbcke:0 | + | |
- | </code> | + | |
===== IVS Observations ===== | ===== IVS Observations ===== | ||
Line 67: | Line 45: | ||
* On occasions, the Hobart data are written to disk between scans for e-transfer to Tsukuba for ultra-rapid EOP observations. Some additional changes to the schedule files are required in this case: | * On occasions, the Hobart data are written to disk between scans for e-transfer to Tsukuba for ultra-rapid EOP observations. Some additional changes to the schedule files are required in this case: | ||
* [[operations:documentation.ivs.drudg_ureop|Additional schedule preparation for Hb ultra-rapid EOP experiments]] | * [[operations:documentation.ivs.drudg_ureop|Additional schedule preparation for Hb ultra-rapid EOP experiments]] | ||
+ | * [[operations:starting_monitoring_urEOP|Additional tasks prior to starting Ultra-rapid EOP observations]] | ||
+ | |||
+ | |||
+ | == RF and IF signal path == | ||
+ | * [[operations:rf_if_check|Configuring the RF and IF signal paths]] | ||
== Check the maser == | == Check the maser == | ||
Line 82: | Line 65: | ||
* [[operations:documentation.clock_and_delay_check|Checking clock offsets and delays]] | * [[operations:documentation.clock_and_delay_check|Checking clock offsets and delays]] | ||
+ | == Test recording == | ||
+ | * [[operations:documentation.test_recording|Making a test recording]] | ||
- | ===== Test Recording ===== | + | == System Temperature (Tsys) check == |
+ | * [[operations:documentation.test_tsys|Tsys measurement]] check | ||
- | Now make a test recording using the Mark5. This is done through the Operator Input window. | + | == Antenna checks == |
+ | * [[operations:documentation.test_antenna|Antenna checks]] | ||
- | <code>disk_record=on | + | == Weather checks == |
- | mk5=dot? (Output should appear as before, but it should say FHG_on) | + | * [[operations:documentation.weather_check|Weather conditions]] |
- | disk_record=off</code> | + | |
- | Now check the data are OK: | + | |
- | <code>scan_check</code> | + | |
- | Check the last numbers are the correct date at the start of the scan, duration, the data rate (should be 256 for the 8MHz mode, 128 for the 4 MHz mode) and 0 at the end for no problems. Then plot an autocorrelation from the data: | + | |
- | <code>postob</code> | + | |
- | The output should appear in the pcfs[hb|ke|yg] VNC session. Good data should contain quite flat bandpasses and zero phase. See [[operations:monitoring_autocor|autocorrelation spectra plots]] for an example and what problems to look out for. If there's a problem, the DBBC may need reconfiguring. | + | |
- | To clear the disk module, ONLY IF YOU'RE CERTAIN there is no data already on the disk! | + | == Fringe check == |
- | <code> mk5=protect=off; mk5=reset=erase </code> | + | * [[operation:fringe_checking|Fringe checking procedure]] |
- | [[operations:monitoring_autocor|Check that the spectra are OK]]. | + | |
- | If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. | + | |
- | |||
- | |||
- | == Test recording == | ||
- | == System Temperature (Tsys) check == | ||
- | == Antenna checks == | ||
- | == Weather checks == | ||
- | == Fringe check == | ||
== Send a Station Ready email == | == Send a Station Ready email == | ||
+ | * [[operations:documentation.station_ready_email|Sending a station ready email to IVS]] | ||
+ | == Skype == | ||
+ | * Start Skype and begin a chat session with all participating sites plus the on-call person | ||
- | |||
- | |||
- | 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:starting_monitoring|Starting an monitoring the observations]] | + | * [[operations:starting_monitoring_v2|Starting an monitoring the observations]] |
- | * [[operations:starting_monitoring_urEOP|Additional tasks prior to starting Ultra-rapid EOP observations]] | + | |
- | * [[operation:fringe_checking| Fringe-checking the AuScope array]] | + | |
==== After the Observations ==== | ==== After the Observations ==== |