User Tools

Site Tools


operations:documentation.parkes_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
operations:documentation.parkes_monitoring [2015/05/06 11:16]
Vasaant Krishnan [Setting up for Parkes observations:]
operations:documentation.parkes_monitoring [2015/05/15 13:12] (current)
Vasaant Krishnan [Setting up for Parkes observations:]
Line 21: Line 21:
   * Specialised program //atsnap// will be used to control antenna.   * Specialised program //atsnap// will be used to control antenna.
         * vex file has to be converted into "​pointing"​ format file //psn//, that contains scan-end times (i.e. moments when antenna should start moving):         * vex file has to be converted into "​pointing"​ format file //psn//, that contains scan-end times (i.e. moments when antenna should start moving):
 +  * Use the snap summary to check that the Parkes antenna is tracking the correct source and that the recorded data volume is correct
   * Parkes Observing Portal will be used for the real-time interactive antenna status retrieval: [[https://​parkes-ops.atnf.csiro.au/​PORTAL/​login.php?​return=/​PORTAL/​index.php]] John Sarkissian from ATNF will tell you about it on Thursday morning at 9am.   * Parkes Observing Portal will be used for the real-time interactive antenna status retrieval: [[https://​parkes-ops.atnf.csiro.au/​PORTAL/​login.php?​return=/​PORTAL/​index.php]] John Sarkissian from ATNF will tell you about it on Thursday morning at 9am.
          * Two tools are running: Portal itself, and FROG. You will use //Portal// to monitor the status of the antenna, use the chat, book observing time, send reports and follow up on any problems. //FROG// is an alert system: [[https://​parkes-ops.atnf.csiro.au/​FROG/​index.php]]          * Two tools are running: Portal itself, and FROG. You will use //Portal// to monitor the status of the antenna, use the chat, book observing time, send reports and follow up on any problems. //FROG// is an alert system: [[https://​parkes-ops.atnf.csiro.au/​FROG/​index.php]]
Line 31: Line 32:
 You will need 4 screens to keep an eye on all necessary windows: PORTAL, FROG, two VNC: joffrey:1 and pictor:3. You will need 4 screens to keep an eye on all necessary windows: PORTAL, FROG, two VNC: joffrey:1 and pictor:3.
   - ** Vex-to-psn File Conversion**   - ** Vex-to-psn File Conversion**
-        * .vex and .skd files can be found on ops2 in /​vlbobs/​ivs/​sched/​ +        * ''​.vex'' ​and ''​.skd'' ​files can be found on ''​ops2'' ​in ''​/​vlbobs/​ivs/​sched/​''​ 
-        * Copy the .vex and .skd files to home directory ​on //observer@ares.phys.utas.edu.au// +        * Copy the .vex and .skd files to home directory ​in: ''​observer@ares.phys.utas.edu.au:​.''​ 
-        * From this directory ​ssh into //your_cass@venice.atnf.csiro.au//​ +        * ssh into: ''​your_cass@venice.atnf.csiro.au''​ and then to: ''​vlbi@hydra''​ (See whiteboard for detailed instructions.) 
-        * Via //venice//, log in to //hydra// or //draco// using your Unix credentials+        * Issue the following commands while in ''​vlbi@hydra'':​ 
 +        * ''​cd ftp''​ 
 +        * ''​mkdir aua003 ''​ (for example) 
 +        * ''​cd aua003 ''​ 
 +        * ''​scp observer@ares.phys.utas.edu.au:​aua003.vex''​ 
 +        * ''​ pkvex.sh aua003.vex ''​ 
 +        * Now convert the ''​.vex''​ using: 
 +        * ''​pkvex.sh aua003.vex''​ 
 +        * Enter the passwords for ''​vlbi@pam0''​ and ''​pcfs (pkvsi2)''​ when prompted. 
 +        * Excellent! Now the ''​.psn''​ file is ready, and you only need to ''​drudg''​ the schedule file. From ''​vlbi@hydra'':​ 
 +        * ''​ssh oper@pkvsi2-ext''​ 
 +        * ''​cd /usr2/sched/''​ 
 +        * ''​scp observer@ares.phys.utas.edu.au:​aua003.skd .''​ 
 +        * ''​drudg aua003.skd''​ 
 +        * Now here's the tricky part! When dealing with the usual Auscope antennae, Jamie'​s ''​slogit''​ script does the ''​drudg''​ing on autopilot. Now however you will actually need to interact with the dinosaur of a script: 
 +        * When prompted: ''​Output for which station (type a code,  :: or q to quit, = for all) ?''​ 
 +        * Tell it: ''​Pa''​ 
 +        * Next, you need to get ''​drudg''​ to do what you want it to do by selecting the number corresponding to the desired ​//menu// option. 
 +        * Check that the equipment is set correctly with menu: ''​11''​. The output needs to read: ''​Rack=Mark5''​ and: ''​Recorder1=Mark5B''​. 
 +        * Next make the ''​proc''​ file with menu: ''​12''​ 
 +        * And the ''​snap''​ file with menu: ''​3''​ 
 +        * Generate a sap summary with menu: ''​5''​ 
 +        * ''​Exit''​ from ''​drudg''​ with menu: ''​0''​ 
 +        * ''​scp''​ the .sum file summary back to ares with: 
 +        * ''​scp ​/tmp/DR.tmp observer@ares.phys.utas.edu.au:​/vlbobs/ivs/sched/aua003pa.sum''​ 
 +        * Note that aua003pa.prc should be identical to aua002pa.prc except for the header. Use: 
 +        * ''​diff ​/usr2/proc/​aua003pa.prc /​usr2/​proc/​aua002pa.prc''​ 
 +        * I think the instructions between the ''​=====''​ borders are now obsolete (vk): 
 +        * ''​===================Start obsolete bit=================================''​
         * Copy .vex-file on that machine         * Copy .vex-file on that machine
         * Convert it into "​pointing"​-format file .psn and copy it to joffry: <​code>​ % vex2psn.pl EXPERIMENT_NAME.vex > EXPERIMENT_NAME.psn         * Convert it into "​pointing"​-format file .psn and copy it to joffry: <​code>​ % vex2psn.pl EXPERIMENT_NAME.vex > EXPERIMENT_NAME.psn
 % scp EXPERIMENT_NAME.psn pksobs@joffrey:​lba </​code>​ % scp EXPERIMENT_NAME.psn pksobs@joffrey:​lba </​code>​
         * Log in to //pkvsi2// (where FS is running) with login oper and password Drudg the .vex-file in a normal way to run the recorder         * Log in to //pkvsi2// (where FS is running) with login oper and password Drudg the .vex-file in a normal way to run the recorder
 +        * ''​===================End obsolete bit=================================''​
   - **Connect to two VNC servers:​** ​   - **Connect to two VNC servers:​** ​
         * Open 1 VNC windows on //joffrey// (ports 1) via ssh tunnel through //venice// (or orion). Note that this way you will have to enter password twice, first your Unix ATNF password, and second password for joffrey which is transient celestial events (on the whiteboard). ​         * Open 1 VNC windows on //joffrey// (ports 1) via ssh tunnel through //venice// (or orion). Note that this way you will have to enter password twice, first your Unix ATNF password, and second password for joffrey which is transient celestial events (on the whiteboard). ​
Line 86: Line 116:
 joffrey% lorun sx.cmd ​ joffrey% lorun sx.cmd ​
 joffrey% cd ~/smsetup joffrey% cd ~/smsetup
-joffrey% ​smsetup ​MK-V_geo.cmd</​code>​+joffrey% ​smrun MK-V_geo.cmd</​code>​
 <​note>​Note any errors. If it has been less than ~60 seconds since you turned "F/C synthesisers",​ wait for another minute or so and try again.</​note>​ <​note>​Note any errors. If it has been less than ~60 seconds since you turned "F/C synthesisers",​ wait for another minute or so and try again.</​note>​
         * There should now be valid levels in all 14 Mk5 VCs.         * There should now be valid levels in all 14 Mk5 VCs.
/home/www/auscope/opswiki/data/attic/operations/documentation.parkes_monitoring.1430910993.txt.gz · Last modified: 2015/05/06 11:16 by Vasaant Krishnan