User Tools

Site Tools


operations:documentation.ivs.drudg_9.10.5

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.ivs.drudg_9.10.5 [2013/10/23 00:22]
Imogen Jones
operations:documentation.ivs.drudg_9.10.5 [2018/03/21 22:05] (current)
Noor Md Said [Preparing Schedule and Procedure Files]
Line 1: Line 1:
 ====== Preparing Schedule and Procedure Files ====== ====== Preparing Schedule and Procedure Files ======
  
-Open a terminal and ssh into observer@ops-serv2 and run: <​code>​~/slogit.auscope_fs9.10.5.sh</​code> ​+Open a terminal and ssh into observer@ops-serv2 and run: <​code>​slogit.auscope.sh</​code> ​
  
 When run, it will prompt you for the experiment code and observatory. Both should be entered in **lower case**. It will download the schedule file (or ask if you want to re-download the file if it currently exists) to ''/​vlbobs/​ivs/​sched/'',​ copy it to pcfs[hb|ke|yg] (it will check if it will overwrite the file), build the snp and prc files (or offer to re-build them if they exist), copy them to the correct places and finally offer to print off a schedule summary and the procedure file. (Crtl X Ctrl C to print proc file after editing). When run, it will prompt you for the experiment code and observatory. Both should be entered in **lower case**. It will download the schedule file (or ask if you want to re-download the file if it currently exists) to ''/​vlbobs/​ivs/​sched/'',​ copy it to pcfs[hb|ke|yg] (it will check if it will overwrite the file), build the snp and prc files (or offer to re-build them if they exist), copy them to the correct places and finally offer to print off a schedule summary and the procedure file. (Crtl X Ctrl C to print proc file after editing).
  
-**Make sure the ifdsx command has the right IFs selected and the right power settings. ​This is not done by default!** See the [[operations:​currentissues|Current Issues]] page for the correct settings. Note that yg and hb have the latest software ​and the levels ​should be correct **but the input IF settings may not be correct**. Please double check.+**Make sure the ifdsx command has the right IFs selected and the right power settings.** ​Check [[operations:​documentation.dbbcsetupivs_v2|the DBBC setup page]] for the correct settings. Note that this should be done by default now but **please double check**, especially for unusual or non-standard setups. 
 + 
 +The summary file, which contains a scan-by-scan summary of the observations including start and stop times, azimuth and elevation, disk usage predictions is a useful resource when checking on the progress of observations. It can be printed out but to save paper it's recommended you view it in a text editor. You can find it on ops2 or ops-serv2 in ''/​vlbobs/​ivs/​sched/<​obscode><​station_ID>​.sum''​. 
 + 
 +If you are setting up an AUST experiment, please read on... 
 + 
 +===== Extra Step For Austral Experiments ===== 
 + 
 + 
 + 
 +Austral Experiments **may** need to have the proc file edited so that the correct checkmk5 procedure is used. 
 + 
 +Open two terminals on pcfs.  Enter in one terminal: 
 + 
 +<​code>​more /​usr2/​proc/​aust<​previous_exp_number><​station_code>​.prc</​code>​ 
 + 
 +Go to the end of the file and highlight ​the procedure. ​  
 + 
 +On the other terminal, enter > 
 + 
 +<​code>​emacs -nw /​usr2/​proc/​aust<​current_exp_number><​station_code>​.prc</​code>​ 
 + 
 +Go to the bottom of the file and look at the checkmk5 procedure. It should ​already ​be there and the content //between// the ''​define''​ and ''​enddef''​ lines should be identical (except the number code in the first line '​define checkmk5 00000000000x'​ - this is just a date code) . If not, then paste the checkmk5 procedure from the first terminal. 
 + 
 +Ctrl x Crtl c and '​y'​ to save. 
 + 
 +This procedure should ​be done **before** the proc file has been run at all. 
 + 
 +**If you do need to edit the proc file after it has been run, follow these directions:​** 
 + 
 +Open two terminals in the pcfs vnc viewer. 
 + 
 +In one enter: 
 + 
 +<​code>​more /​usr2/​proc/​aust<​previous_exp_number><​station_code>​.prc</​code>​ 
 + 
 +This will open the previous experiment proc file. 
 + 
 +Then in the other terminal, enter: 
 + 
 +<​code>​pfmed</​code>​ 
 + 
 +Then overwrite the current proc file by entering: 
 + 
 +<​code>​pf,​aust<​current_exp_number><​station_code>​.prc</​code>​ 
 + 
 +Then enter: 
 + 
 +<​code>​ed,​checkmk5</​code>​ 
 + 
 +Copy and paste the procedure from the previous experiment proc file in the first terminal to the new procedure file in the second terminal. ​  
 + 
 +Then Ctrl x Ctrl c and '​y'​ to save. 
 + 
 +===== Extra Step For Austral Weekend Experiments ===== 
 + 
 +For the weekend experiments,​ an extra command is needed in the first schedule so that it will automatically start the second schedule. Here's what needs to be done: 
 + 
 +For each telescope:​ 
 +  - Log on to the pcfs, and <​code>​cd /​usr2/​sched</​code>​ 
 +  - Edit the schedule file <​code>​emacs -nw aust<​current_exp_number><​station_code>​.snp</​code>​ 
 +  - go to the end of the schedule file (press [esc], then >) and add the following lines: <​code>​!+1m 
 +schedule=aust<​next_exp_number><​station_code>,#​1</​code>​ 
 +  - Then Ctrl x Ctrl c and '​y'​ to save. 
 +The two new lines will tell the field system to wait 1 minute (for the last checkmk5 procedure to finish), then start the new schedule. 
 + 
 +<​note>​When starting the Saturday weekend session, please also download and drudge the schedules for Sunday!</​note>​
/home/www/auscope/opswiki/data/attic/operations/documentation.ivs.drudg_9.10.5.1382487751.txt.gz · Last modified: 2013/10/23 00:22 by Imogen Jones