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
Last revision Both sides next revision
operations:documentation.ivs.drudg_9.10.5 [2014/08/11 02:37]
Jim Lovell [Extra Step For Austral Experiments]
operations:documentation.ivs.drudg_9.10.5 [2018/03/21 22:05]
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.** 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. **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 ===== ===== Extra Step For Austral Experiments =====
Line 23: Line 27:
 <​code>​emacs -nw /​usr2/​proc/​aust<​current_exp_number><​station_code>​.prc</​code>​ <​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. If not, then paste the checkmk5 procedure from the first terminal.+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. Ctrl x Crtl c and '​y'​ to save.
Line 66: Line 70:
   - Then Ctrl x Ctrl c and '​y'​ to save.   - 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. 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/pages/operations/documentation.ivs.drudg_9.10.5.txt · Last modified: 2018/03/21 22:05 by Noor Md Said