User Tools

Site Tools


operations:aum-hb

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
Last revision Both sides next revision
operations:aum-hb [2020/09/02 23:13]
Lim Chin Chuan
operations:aum-hb [2021/03/09 07:34]
Lim Chin Chuan
Line 10: Line 10:
  
  
-=== Before the Experiment ===+=== Before the Experiment === [Updated by Lim 2021March04]
  
-  * Preparing the schedule file: Do not use the existing slogit scripts, but instead download the skd file directly to pcfshb ​and run drudg to generate the snp and sum files and put them where they'​re needed. +  * Preparing the schedule file: **Do not use the existing slogit scripts** for **Hb** and **Ke**, but instead download the skd file directly to pcfs[hb|ke|yg] ​and run drudg to generate the snp and sum files and put them where they'​re needed.
-  * [[operations:​aum_setup|operations:​aum_setup]]+
  
-<​code>​cd /​usr2/​sched +<​code>​ 
-wget ftp://cddis.gsfc.nasa.gov/​vlbi/​ivsdata/​aux/​2020/aua063/aua063.skd +cd /​usr2/​sched 
-drudg aua063.skd+wget ftp://ivs.bkg.bund.de/pub/​vlbi/​ivsdata/​aux/​2021/aum028/aum028.skd 
 +drudg aum028.skd
    hb (station)    hb (station)
    11 (show/set equipment type)    11 (show/set equipment type)
    1 16 1 1  (none, flexbuff[mark5b],​ none, none)    1 16 1 1  (none, flexbuff[mark5b],​ none, none)
    ​3 ​ (make snap file)    ​3 ​ (make snap file)
-   ​5 ​  ​(print summary) +   ​5 ​ (print summary) 
-   ​0 ​   (exit) +   ​0 ​ (exit) 
-scp /​tmp/​sched.tmp observer@ops-serv2:/​vlbobs/​ivs/​sched/​aua063hb.sum+scp /​tmp/​sched.tmp observer@ops-serv2:/​vlbobs/​ivs/​sched/​aum028hb.sum (tmp summary file might have a different file name! i.e. DR.tmp)
 </​code>​ </​code>​
     ​     ​
-The next step is to create the procedure file with the appropriate commands. The easiest way is to copy the procedure file from a previous experiment using the same mode. For the 32-MHz mode (In use as of March 2020), the SI experiment setup can be used as  the template. e.g:+The next step is to create the procedure file with the appropriate commands. The easiest way is to copy the procedure file from a previous experiment using the same mode. For the 32-MHz mode (In use as of March 2020), the SI experiment setup can be used as the template. e.g:
  
 <​code>​ <​code>​
 cd /usr2/proc/ cd /usr2/proc/
-cp si.prc ​aua063hb.prc +cp si.prc ​aum018hb.prc  (Hb, Ke)
 </​code>​ </​code>​
 +**because Yg now use mark5B instead of flexbuff, use slogit to drudg as usual.**
  
-* Terminate the FS and restart it with "​fs-dummy" ​for both Hb and KeThis ensures ​that the Field system will not connect to the DBBC2 and block the configuration scripts.  +=== Setting up for Hb, Ke === 
- +  ​* Terminate the FS and restart it with "​fs-dummy"​. ​(To ensure ​that the Field system will not connect to the DBBC2 and block the configuration scripts) 
-* From a terminal on the pcsf machine, run the command ''​./​bin/​aum.query.summ.py''​. If the script stalls (and does not return to the command prompt), then it's likely that either one or both of the DBBC control programs are not running, or that something else is  talking to them.  +  ​* Log in to **DBBC3** (''​vncviewer dbbc3hb''​) and make sure that the ''​DBBC3 Control ​DDC_V_v124.exe''​ program is running, and that the final line of output reads ''​Waiting for connection''​).  
-  ​- First log in to DBBC3 (''​vncviewer dbbc3hb''​) and make sure that the ''​DBBC3 Control ​DDC_V_v123.exe''​ program is running, and that the final line of output reads ''​Waiting for connection''​).  +  ​Nextcheck the **DBBC2** (''​vncviewer dbbcho''​ for Hb and ''​vncviewer dbbcke''​ for Ke) and check that the correct control program is running (''​DBBC2 Control DDC v105E_2.exe''​ for Hb, ''​DBBC2 Control DDV v106E_120118.exe''​ for Ke) and displays ''​Waiting for connection''​) 
-  ​Next check the DBBC2 (''​vncviewer dbbcho''​ for Hb and ''​vncviewer dbbcke''​ for Ke) and check that the correct control program is running (''​DBBC2 Control DDC v105E_2.exe''​ for Hb, ''​DBBC2 Control DDV v106E_120118.exe''​ for Ke) and displays ''​Waiting for connection''​) +  * If the server program is not running, please start it from the link on the desktop (and be prepared for a 15-20 minute wait for the DBBC3 after answering "​y"​ to the reconfiguration question). ​
-  * If the server program is not running, please start it from the link on the desktop (and be prepared for a 15-20 minute wait  for the DBBC3 after answering "​y"​ to the reconfiguration question). ​+
   * If it does not read ''​waiting for connection'',​ it should give the IP address of the machine that's currently talking to it (e.g if it reads ''​Command from 131.217.63.201:''​ then the connection is from 131.217.63.201). You can lookup up the name of this machine using ''​nslookup 131.217.63.201''​ - in this example it is the ''​hobart''​ machine that is talking with the DBBC. If a PCFS machine is connected, the best option is to terminate the FS on that machine and restart with a version that will not conflict. For the Hobart example, running ''​fs-auscope''​ will avoid this problem while ''​fs-flexbuff''​ will block communications. ​   * If it does not read ''​waiting for connection'',​ it should give the IP address of the machine that's currently talking to it (e.g if it reads ''​Command from 131.217.63.201:''​ then the connection is from 131.217.63.201). You can lookup up the name of this machine using ''​nslookup 131.217.63.201''​ - in this example it is the ''​hobart''​ machine that is talking with the DBBC. If a PCFS machine is connected, the best option is to terminate the FS on that machine and restart with a version that will not conflict. For the Hobart example, running ''​fs-auscope''​ will avoid this problem while ''​fs-flexbuff''​ will block communications. ​
 +  * From a terminal on the pcfs machine, run the command ''​./​bin/​aum.query.summ.py''​. If the script stalls (and does not return to the command prompt), then it's likely that either one or both of the DBBC control programs are not running, or that something else is talking to them. 
 +  * Once you can run ''​~/​bin/​aum.query.summ.py''​ successfully,​ you should be fine to configure the backend at Hobart 12 with ''​./​bin/​aum.setup.lim.py [exp_name]''​. NB - this script will force a synchronisation of the BBCs and is equivalent to running ''​setupsx''​ and ''​fmset''​ in sequence. **Do not run the setup script during the experiment!**
 +  * **As of March 2021, only dbbc3ke is available at Katherine, please setup using ''​./​bin/​aum.setup.dbbc3only.py''​ instead.**
 +  * Load the procedures with ''​proc=aum018hb''​ and configure the recorder with ''​setupvgos''​
 +  * Check the ''​~/​bin/​aum.query.py''​ returns "​pps_delay/​ [1]: 43 ns, [2] 39 ns, [3] 39 ns, [4] 43 ns, [5] 43 ns, [6] 43 ns, [7] 0 ns, [8] 0 ns". (If not, the dbbc3 may need to be reconfigured or even restarted)
 +  * Check that ''​~/​bin/​aum.query.summ.py''​ returns "​Delays:​ OK" and "​Samplers:​ Ok" (if the IF or BBC power levels are reported as bad, this should be re-checked after a few minutes but they might be out of range when freshly set up). 
 +  * You can make a test recording to check for synchrnoisation problems between the different DBBCs with ''​~/​bin/​sxtimetest.sh''​ which will print out the decoded time of the start of the test recording. All three values should agree and match the time reported in the FS log for when the "​record=on"​ command was issued. If the times differ between the different datastreams,​ you will need to reconfigure the relevant DBBCs. If they are all in agreement but differ from the FS log, please note this difference in the log but proceed on to the next step. 
 +  * Set the log file for the experiment with ''​log=aum018hb''​
 +  * Load the schedule file with ''​sched=aum018hb,#​1''​
  
-* Once you can run ''​~/​bin/​aum.query.summ.py''​ successfully,​ you should be fine to configure the backends with ''​./​bin/​aum.setup.py''​. NB - this script will force a synchronisation of the DBBCs and is equivalent to running ''​setupsx''​ and ''​fmset''​ in sequence. Do not run the setup script during the experiment! +== Setting up for Yg == 
- +  Yarragadee ​should be set up normally, using the DBBC2 (v104_2.exe) and mk5yg - Please make sure this is configured by starting ​the Field System ​with ''​fs''​.
-* Load the procedures with ''​proc=aua063hb''​ and configure the recorder with ''​setupvgos''​ +
- +
-Check that ''​~/​bin/​aum.query.summ.py''​ returns "​Delays:​ OK" and "​Samplers:​ Ok" (if the IF or BBC power levels are reported as bad, this should be re-checked after a few minutes but they might be out of range when freshly ​set up).  +
- +
-* You can make a test recording to check for synchrnoisation problems between ​the different DBBCs with ''​~/​bin/​sxtimetest.sh''​ which will print out the decoded time of the start of the test recording. All three values should agree and match the time reported in the FS log for when the "​record=on"​ command was issued. If the times different between the different datastreams,​ you will need to reconfigure the relevant DBBCs. If they are all in agreement but differ from the FS log, please note this difference in the log but proceed on to the next step.  +
- +
-* Set the log file for the experiment ​with ''​log=aua063hb''​ +
- +
-* Load the schedule file with ''​sched=aua063hb,#​1''​+
  
-==== Revised checklist ====+==== Revised checklist ​for Hb, Ke====
  
 A new script has been created which summarises the DBBC3/DBBC2 status. A version is installed on the pcfs machines as ''​~oper/​bin/​aum.query.summ.py''​ and should be running in the VNC session. The Hobart and Katherine menus on ''​ops8''​ also have a new entry called ''​AUM Monitor''​ which will start a version on ops, running in an xterm and refreshing every 60s. The output is below: A new script has been created which summarises the DBBC3/DBBC2 status. A version is installed on the pcfs machines as ''​~oper/​bin/​aum.query.summ.py''​ and should be running in the VNC session. The Hobart and Katherine menus on ''​ops8''​ also have a new entry called ''​AUM Monitor''​ which will start a version on ops, running in an xterm and refreshing every 60s. The output is below:
Line 132: Line 132:
 == Monitoring == == Monitoring ==
   * Antenna checks as per usual   * Antenna checks as per usual
 +  * Check data is being recorded in three streams (mk5=datastream?​ 0:​3:​sxy:​xx:​xy) and 3 files the same size per scan on flexbuff<​st>​ vbs_ls -lh aum019_* | tail
   * LO check unavailable   * LO check unavailable
   * No autocorrelations   * No autocorrelations
/home/www/auscope/opswiki/data/pages/operations/aum-hb.txt · Last modified: 2021/04/27 05:13 by Pradyumna Kiran Kummamuru