User Tools

Site Tools


operations:documentation:lba_starting_and_monitoring

This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
operations:documentation:lba_starting_and_monitoring [2013/03/14 03:08]
Jim Lovell
operations:documentation:lba_starting_and_monitoring [2013/03/14 04:14]
Jim Lovell [Starting]
Line 5: Line 5:
  
 ===== Starting ===== ===== Starting =====
 +If you are stopping the previous schedule early (e.g. finishing a Fringe Check schedule ahead of time), use ''​halt''​ to stop the schedule and then make sure the disk has stopped recording:
 +<​code>​
 +halt
 +disk_record=off
 +</​code>​
 +
 +Now make sure you have the correct Mark5 module selected. Type <​code>​mk5=vsn?</​code>​ and check the serial number against what you think it should be. For the March LBA session, a list of modules agains experiments is given in the [[http://​ra-wiki.phys.utas.edu.au/​index.php?​n=Schedules.LBAMar13|Observing Roster]] page. If you need to change modules use the ''​mk5=bank_set''​ command. e.g. to change to Bank B:<​code>​mk5=bank_set=b</​code>,​ then run <​code>​mk5=dot?</​code>​to check.
 +
 If time permits, make a recording test before starting and check the bit stats and autocorrelations (note this won't work from a fringe-checking schedule): If time permits, make a recording test before starting and check the bit stats and autocorrelations (note this won't work from a fringe-checking schedule):
  
Line 21: Line 29:
  
 <​code>​ <​code>​
-schedule=v252aike+schedule=v252aike,#1
 </​code>​ </​code>​
  
 ===== Monitoring ===== ===== Monitoring =====
-During the runmake sure that +See these sections for notes on known problemsthings to watch out for etc: 
- +    * [[operations:​currentissues|Current Issues]] 
-====== Checklist Parameter Descriptions ====== +    * See the "Other things ​to watch out for" on the [[operations:starting_monitoring_9.10.5|Starting and Monitoring IVS sessions]] page.
- +
-Below is an explanation of the current list of items to check during an observation:+
  
 +During the run, make sure that:
   * **Antenna: drives OK**\\ Check the antenna status display in the system monitor window for the antenna. If Drive Status is green then all is well.    * **Antenna: drives OK**\\ Check the antenna status display in the system monitor window for the antenna. If Drive Status is green then all is well. 
   * **Antenna: Time OK (i.e. SNTP server OK)**\\ Check the Controller Clock status display in the system monitor window for the antenna. ​ If it's green and "​OK"​ then the controller knows the time. If not, the antenna probably doesn'​t know where its pointing, there'​s a problem. Check the HMI display on the time[hb|ke|yg] VNC session for more information. If HMI isn't running or you want to restart it here are some notes on [[software:​hmi|Starting HMI]].   * **Antenna: Time OK (i.e. SNTP server OK)**\\ Check the Controller Clock status display in the system monitor window for the antenna. ​ If it's green and "​OK"​ then the controller knows the time. If not, the antenna probably doesn'​t know where its pointing, there'​s a problem. Check the HMI display on the time[hb|ke|yg] VNC session for more information. If HMI isn't running or you want to restart it here are some notes on [[software:​hmi|Starting HMI]].
Line 58: Line 65:
 If monitoring from Mt. Pleasant, use pmSTALMke.sh to monitor the alarms. If you want the station alarms to go off when there’s an error (rather than playing a sound through the speakers), use pmSTALMke.newsmerd.sh. I’d recommend changing the title of the terminal window to make it clear which alarms are from which station If monitoring from Mt. Pleasant, use pmSTALMke.sh to monitor the alarms. If you want the station alarms to go off when there’s an error (rather than playing a sound through the speakers), use pmSTALMke.newsmerd.sh. I’d recommend changing the title of the terminal window to make it clear which alarms are from which station
  
-See the [[operations:​currentissues|Current Issues]] section for known problems and how to fix them.  
- 
-See also these notes on 
/home/www/auscope/opswiki/data/pages/operations/documentation/lba_starting_and_monitoring.txt · Last modified: 2014/11/22 09:01 by Jesse Swan