User Tools
operations:documentation.ivs.drudg
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.
| Next revision | Previous revision | ||
|
operations:documentation.ivs.drudg [2010/12/08 02:05] Jim Lovell created |
operations:documentation.ivs.drudg [2011/10/26 06:37] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Preparing Schedule and Procedure Files ====== | ====== Preparing Schedule and Procedure Files ====== | ||
| - | * Obtain the .skd file and put it on pcfsya in /usr2/sched, then: | + | There are two ways of doing this: via the ''slogit.auscope.sh'' script or manually. |
| + | |||
| + | The script is much faster and easier although there are some things to beware of. The script is currently based on ops-serv2 as <code>slogit.auscope.sh</code> | ||
| + | |||
| + | When run, it will prompt you for the experiment code and observatory. 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 log and cover sheets. It will append the standard preob to the prc file, but does not delete the redundant lines. It will pop up an emacs session for you to edit the file though. | ||
| + | |||
| + | Note that the schedule summary file is currently written to /tmp/sched.tmp on pcfs[hb|ke|yg]. A copy needs to be scp'ed back to be printed out. | ||
| + | |||
| + | <note>For Yarragadee, the SNAP file will need to be edited by hand to remove scans and stow the antenna at times that coincide with transmissions from the adjacent USN antenna. | ||
| + | See the following page for information about determining the time ranges: | ||
| + | * [[operations:yg_USN_times|USN Transmission times at Yarragadee]] | ||
| + | To remove the scans from the schedule, comment them out, with a ''"'' in the first column, put a source=stow at the start and specify a wait time at the end. e.g.: | ||
| + | <code> | ||
| + | !2011.187.07:07:01 | ||
| + | data_valid=off | ||
| + | disk_record=off | ||
| + | disk_pos | ||
| + | postob | ||
| + | "Stow antenna due to USN transmissions | ||
| + | source=stow | ||
| + | " scan_name=187-0716,r1490,Yg,43,43 | ||
| + | " source=0727-115,072758.08,-113452.5,1950.0,neutral | ||
| + | " checkmk5 | ||
| + | " setupsx | ||
| + | " !2011.187.07:16:35 | ||
| + | . | ||
| + | . | ||
| + | . | ||
| + | " !2011.187.08:04:58 | ||
| + | " data_valid=off | ||
| + | " disk_record=off | ||
| + | " disk_pos | ||
| + | " postob | ||
| + | !2011.187.08:05:00 | ||
| + | scan_name=187-0806,r1490,Yg,43,43 | ||
| + | source=0727-115,072758.08,-113452.5,1950.0,neutral | ||
| + | checkmk5 | ||
| + | setupsx | ||
| + | </code> | ||
| + | </note> | ||
| + | ====== Manual Instructions ========================= | ||
| + | Obtain the .skd file and put it on pcfshb in /usr2/sched, then: | ||
| <code> | <code> | ||
| Line 50: | Line 91: | ||
| * The pcal functions were also removed from the proc file as we do not have a computer controlled phasecal. | * The pcal functions were also removed from the proc file as we do not have a computer controlled phasecal. | ||
| * The vsi commands could be removed but do not seem to be causing any serious problems or excessive errors in the logs. | * The vsi commands could be removed but do not seem to be causing any serious problems or excessive errors in the logs. | ||
| - | * The preob and midob procedures should be edited to include some mk5 and site specific functions. One problem encountered was difficulty in setting up thee new procedures by editing the proc file directly. The best way of inserting/editing procedures in a proc file is to load it into the fs and then run pfmed from the terminal. To create or edit a procedure, type "edit" and then the name of the procedure. The final procure file is included below. Don't try to paste this text into a proc file as the Wiki formatting may cause strange problems for the interpreter. | + | * The preob and midob procedures should be edited to include some mk5 and site specific functions. |
| + | |||
| + | One problem encountered was difficulty in setting up thee new procedures by editing the proc file directly. The best way of inserting/editing procedures in a proc file is to load it into the fs and then run pfmed from the terminal. To create or edit a procedure, type "edit" and then the name of the procedure. The final procure file is included below. | ||
| + | Don't try to paste this text into a proc file as the Wiki formatting may cause strange problems for the interpreter. | ||
| <code> | <code> | ||
| Line 80: | Line 124: | ||
| enddef | enddef | ||
| </code> | </code> | ||
| - | |||
/home/www/auscope/opswiki/data/attic/operations/documentation.ivs.drudg.1291773958.txt.gz · Last modified: 2011/10/26 06:37 (external edit)
Page Tools
