User Tools

Site Tools


lbaops:webmonitoring

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
lbaops:webmonitoring [2014/05/30 11:31]
ste616
lbaops:webmonitoring [2019/02/28 16:03] (current)
cormac
Line 1: Line 1:
 The web page that we now commonly use for monitoring the entire LBA is at: The web page that we now commonly use for monitoring the entire LBA is at:
  
-[[http://​www.narrabri.atnf.csiro.au/​vlbi/​lba_monitor.html]]+[[https://​www.narrabri.atnf.csiro.au/​vlbi/​lba_monitor.html]]
  
 The monitoring the page uses requires access to a number of MoniCA servers, and some pre-computed JSON files generated by scripts. This wiki describes how to start all the connections and scripts required to make the LBA monitor page work. The monitoring the page uses requires access to a number of MoniCA servers, and some pre-computed JSON files generated by scripts. This wiki describes how to start all the connections and scripts required to make the LBA monitor page work.
Line 16: Line 16:
 To setup the Hobart connection, login to mentok as vlbi and give the command: To setup the Hobart connection, login to mentok as vlbi and give the command:
  
-<​code>​ screen -S hobart ssh -L mentok:​8051:​newsmerd:​8051 -L mentok:​8052:​newsmerd:​8052 \+<​code>​ screen -S hobart ssh -L mentok:​8051:​newsmerd:​8051 -L mentok:​8052:​newsmerd:​8052 ​-L mentok:​8053:​pcfshb:​8051 -L mentok:​8054:​pcfske:​8051 -L mentok:​8055:​pcfsyg:​8051 ​\
      ​observer@newsmerd.phys.utas.edu.au </​code>​      ​observer@newsmerd.phys.utas.edu.au </​code>​
  
Line 70: Line 70:
 Two other observatories are monitored without MoniCA: Tid and Hart. Two other observatories are monitored without MoniCA: Tid and Hart.
  
-The monitoring from Tid is pushed by the Tid computers to the location ''​/u/vlbi/tid/​cdscc_monitor''​, and is in JSON formatThe monitoring web page knows how to get this information. If the Tid monitoring isn't working, contact Tid staff, as there is nothing we can do to fix it.+====  Tidbinbilla monitoring ==== 
 + 
 +The monitoring from Tid comes from the file /home/vlbi/antenna_monitor/​cdscc_monitor ​on the tdvsi machine. This is a JSON file, but it needs to get into the ATNF network for the LBA monitor to use it. 
 + 
 +To make this happen, we need to set up some more screen sessions. Login to mentok as the vlbi user, and give the command: 
 + 
 +<​code>​ screen -S tidtunnel ssh -L 2230:​203.5.58.205:​22 vlbi@pam0 </​code>​ 
 + 
 +This sets up an SSH tunnel through pam0 (the only machine able to directly SSH into tidvsi) to tidvsi. We now have to run a script that gets the cdscc_monitor file every 5 seconds and puts it in the right placeTo do this, as vlbi on mentok, give the command: 
 + 
 +<​code>​ screen -S tidget -d -m /n/vlbi/monitoring/​gettidmon.pl </​code>​ 
 + 
 +There should be no feedback from this command except the monitoring working on the web page. 
 + 
 +If the Tid monitoring isn't working, contact Tid staff, as there is nothing we can do to fix it. 
 + 
 +====  Hart monitoring ====
  
 For Hart we need to use a script to grab the monitoring information they make available from [[http://​spyda.hartrao.ac.za/​cgi-bin/​hartrao_26_lba.txt]] and turn it into a JSON file so it can be manipulated properly by the monitoring page. The script that does this is located at ''/​n/​vlbi/​monitoring/​hart2json.pl''​. We run this in a screen session as well and it will fetch new information every second and turn it into the file ''/​n/​vlbi/​monitoring/​hart.json'',​ which the web page knows how to get. For Hart we need to use a script to grab the monitoring information they make available from [[http://​spyda.hartrao.ac.za/​cgi-bin/​hartrao_26_lba.txt]] and turn it into a JSON file so it can be manipulated properly by the monitoring page. The script that does this is located at ''/​n/​vlbi/​monitoring/​hart2json.pl''​. We run this in a screen session as well and it will fetch new information every second and turn it into the file ''/​n/​vlbi/​monitoring/​hart.json'',​ which the web page knows how to get.
Line 79: Line 95:
  
 There should be no feedback from this command except the monitoring working on the web page. There should be no feedback from this command except the monitoring working on the web page.
 +
 +If the Hart 15m is being used instead of the 26m, start the monitoring script with:
 +
 +<​code>​ screen -S hart -d -m /​n/​vlbi/​monitoring/​hart2json.pl 15 </​code>​
  
 =====  Monitoring the recorders ===== =====  Monitoring the recorders =====
Line 136: Line 156:
  
 This will create the files ''/​n/​vlbi/​monitoring/​horec.json''​ and ''/​n/​vlbi/​monitoring/​cdrec.json''​ that will refresh every 20 seconds or so. This will create the files ''/​n/​vlbi/​monitoring/​horec.json''​ and ''/​n/​vlbi/​monitoring/​cdrec.json''​ that will refresh every 20 seconds or so.
 +
 +=====  VEX checking =====
 +
 +The LBA monitor page can use the VEX file for the experiment to check that what is being observed is what the schedule specifies. To make this work however we need to convert the VEX file into JSON format and put it in the place that the web page expects it to be.
 +
 +Creating the JSON file is easy. Grab the VEX file and put it into the directory ''/​n/​vlbi/​monitoring''​. Log in to mentok as the VLBI user and change to that same directory. Now use the ''​vex2json.pl''​ script in that directory to do the conversion. For example, if you have the VEX file ''​v486d.vex'',​ you would give the command:
 +
 +<​code>​ /​n/​vlbi/​monitoring/​vex2json.pl v486d.vex > v486d.json </​code>​
 +
 +This would make the file ''​v486d.json''​ in the same directory.
 +
 +To put this JSON file where the web page can grab it, copy it to ''/​n/​vlbi/​monitoring/​currentvex.json''​ (overwriting that file).
 +
 +The web page is designed so that it will look at that file when the page is loaded, or when the last scan in the VEX file that it currently has is in the past. So all you need to do is make sure the new JSON file is in place a few minutes before the end of the current experiment and the web page should pick up the new JSON automatically.
 +
 +Sometimes the browser will stop looking for the new JSON file if it sees that it hasn't varied for a long time. In this case you will need to clear the browser'​s cache before it will pick up the new schedule.
 +
lbaops/webmonitoring.1401413470.txt.gz · Last modified: 2015/12/18 16:39 (external edit)