User Tools
operations:documentation.ivs
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.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
operations:documentation.ivs [2010/12/08 01:52] Jim Lovell |
operations:documentation.ivs [2010/12/08 02:49] Jim Lovell |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| * [[operations:documentation.ivs.drudg|Preparing the schedule and procedure files]] | * [[operations:documentation.ivs.drudg|Preparing the schedule and procedure files]] | ||
| - | * DBBC configuration | + | * [[operations:documentation.DBBCSetupIVS|DBBC configuration]] |
| - | * | + | |
| * [[operations:documentation.ivs.mark5|Mark5B recorder setup]] | * [[operations:documentation.ivs.mark5|Mark5B recorder setup]] | ||
| * [[operations:documentation.ivs.SchedStart|Running the schedule]] | * [[operations:documentation.ivs.SchedStart|Running the schedule]] | ||
| - | |||
| - | **Drudg** | ||
| - | |||
| - | The .skd file was drudged on pcfsya. The rack and recorder hardware was first selected (option 11) and set to "Mark5 rack" "Mark5B recorder" "No second recorder" and "Start with 1" (options 16 14 1 1). Then the procedures and snap file were made, and a summary printed (options 12, 3 and 5 in sequence). Printing from drudg does not seem to work at present so the summary was printed using the command "enscript -r -2 /tmp/DR.tmp" from the terminal. | ||
| - | |||
| - | After drudging the schedule, the procedure file was copied to /usr2/proc/. It then had to be edited to remove procedures using non-existent equipment and to support the Mark5B. The ifdsx and vcsx8 procedures were removed in entirety (as the IF power levels and VC settings are set through the DBBC in our system. It may be worth keeping a copy of the vcsx8 settings to confirm the DBBC frequencies required) and the calls to these functions were removed from the setupsx procedure. 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 preob and midob procedures were edited to include some mk5 and site specific functions. One problem encountered was difficult 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 causes strange problems for the interpreter. | ||
| - | |||
| - | define proc_library 10252181423x\\ | ||
| - | " r4447 hobart12 hb\\ | ||
| - | " drudg version 2008oct08 compiled under fs 9.10.04\\ | ||
| - | "< mark5 rack >< mark5b recorder 1>\\ | ||
| - | enddef\\ | ||
| - | define exper_initi 10252181420x\\ | ||
| - | proc_library\\ | ||
| - | sched_initi\\ | ||
| - | mk5=dts_id?\\ | ||
| - | mk5=os_rev?\\ | ||
| - | mk5=ss_rev?\\ | ||
| - | mk5=status?\\ | ||
| - | enddef\\ | ||
| - | define setupsx 10252181440x\\ | ||
| - | tpicd=stop\\ | ||
| - | mk5b_mode=ext,0x55555555,2\\ | ||
| - | mk5b_mode\\ | ||
| - | bank_check\\ | ||
| - | tpicd\\ | ||
| - | enddef\\ | ||
| - | define preob 10252182950\\ | ||
| - | onsource\\ | ||
| - | systemp12\\ | ||
| - | mk5=dot?\\ | ||
| - | clkoff\\ | ||
| - | enddef\\ | ||
| - | define midob 10252183008\\ | ||
| - | onsource\\ | ||
| - | clkoff\\ | ||
| - | sy = run setcl adapt &\\ | ||
| - | mk5=dot?\\ | ||
| - | enddef\\ | ||
| - | define systemp12 10252182950x\\ | ||
| - | sy=/home/oper/systemp12.sh\\ | ||
| - | enddef\\ | ||
| - | |||
| - | **DBBC** | ||
| - | |||
| - | After editing the proc file, it is necessary to set up the DBBC and Mark5B. The C:\DBBC_CONF\dbbc_config_file.txt has been edited to set the frequencies correctly for R1/R4 type experiments. For other experiments, the DBBC frequencies can be calculated either from the sky frequencies or from the original values of the VCs in the proc file. The sky frequencies are given in the skd file. To convert the VC frequency settings to DBBC frequencies you need to add 480 MHZ for the first 4, add 980.1 for dbbc05-dbbc08, add 120 for dbbc09-dbbc14 and set dbbc15 and dbbc16 to something innocuous (say, 320 MHz) as they're not being recorded. Running C:\DBBC_CONF\DBBC Control.190710.exe and answering yes to configure the system should load the frequencies correctly. One the configuration is complete, you need to set up the IF system. The commands to do this are | ||
| - | |||
| - | dbbcifa=1,agc,1\\ | ||
| - | dbbcifb=4,agc,4\\ | ||
| - | dbbcifc=2,agc,2\\ | ||
| - | dbbcifd=2,agc,2 | ||
| - | |||
| - | It appears that CoMo 3 is reporting low total power levels. It may be that there is a poor connection on one of the SMAs...The target values for the total power readings is 56000. this can be checked by the command dbbcif[abcd]. If the levels are too high or low, then adjust the attenuation on the IF box. | ||
| - | |||
| - | **Mark5B** | ||
| - | |||
| - | As oper@mk5hb, first check if the dimino program is running (ps -ef | grep dim). If not, start it with "dimino -m0&". While you**Drudg** | ||
| - | |||
| - | The .skd file was drudged on pcfsya. The rack and recorder hardware was first selected (option 11) and set to "Mark5 rack" "Mark5B recorder" "No second recorder" and "Start with 1" (options 16 14 1 1). Then the procedures and snap file were made, and a summary printed (options 12, 3 and 5 in sequence). Printing from drudg does not seem to work at present so the summary was printed using the command "enscript -r -2 /tmp/DR.tmp" from the terminal. | ||
| - | |||
| - | After drudging the schedule, the procedure file was copied to /usr2/proc/. It then had to be edited to remove procedures using non-existent equipment and to support the Mark5B. The ifdsx and vcsx8 procedures were removed in entirety (as the IF power levels and VC settings are set through the DBBC in our system. It may be worth keeping a copy of the vcsx8 settings to confirm the DBBC frequencies required) and the calls to these functions were removed from the setupsx procedure. 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 preob and midob procedures were edited to include some mk5 and site specific functions. One problem encountered was difficult 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 causes strange problems for the interpreter. | ||
| - | |||
| - | define proc_library 10252181423x\\ | ||
| - | " r4447 hobart12 hb\\ | ||
| - | " drudg version 2008oct08 compiled under fs 9.10.04\\ | ||
| - | "< mark5 rack >< mark5b recorder 1>\\ | ||
| - | enddef\\ | ||
| - | define exper_initi 10252181420x\\ | ||
| - | proc_library\\ | ||
| - | sched_initi\\ | ||
| - | mk5=dts_id?\\ | ||
| - | mk5=os_rev?\\ | ||
| - | mk5=ss_rev?\\ | ||
| - | mk5=status?\\ | ||
| - | enddef\\ | ||
| - | define setupsx 10252181440x\\ | ||
| - | tpicd=stop\\ | ||
| - | mk5b_mode=ext,0x55555555,2\\ | ||
| - | mk5b_mode\\ | ||
| - | bank_check\\ | ||
| - | tpicd\\ | ||
| - | enddef\\ | ||
| - | define preob 10252182950\\ | ||
| - | onsource\\ | ||
| - | systemp12\\ | ||
| - | mk5=dot?\\ | ||
| - | clkoff\\ | ||
| - | enddef\\ | ||
| - | define midob 10252183008\\ | ||
| - | onsource\\ | ||
| - | clkoff\\ | ||
| - | sy = run setcl adapt &\\ | ||
| - | mk5=dot?\\ | ||
| - | enddef\\ | ||
| - | define systemp12 10252182950x\\ | ||
| - | sy=/home/oper/systemp12.sh\\ | ||
| - | enddef\\ | ||
| - | |||
| - | **DBBC** | ||
| - | |||
| - | After editing the proc file, it is necessary to set up the DBBC and Mark5B. The C:\DBBC_CONF\dbbc_config_file.txt has been edited to set the frequencies correctly for R1/R4 type experiments. For other experiments, the DBBC frequencies can be calculated either from the sky frequencies or from the original values of the VCs in the proc file. The sky frequencies are given in the skd file. To convert the VC frequency settings to DBBC frequencies you need to add 480 MHZ for the first 4, add 980.1 for dbbc05-dbbc08, add 120 for dbbc09-dbbc14 and set dbbc15 and dbbc16 to something innocuous (say, 320 MHz) as they're not being recorded. Running C:\DBBC_CONF\DBBC Control.190710.exe and answering yes to configure the system should load the frequencies correctly. One the configuration is complete, you need to set up the IF system. The commands to do this are | ||
| - | |||
| - | dbbcifa=1,agc,1\\ | ||
| - | dbbcifb=4,agc,4\\ | ||
| - | dbbcifc=2,agc,2\\ | ||
| - | dbbcifd=2,agc,2 | ||
| - | |||
| - | It appears that CoMo 3 is reporting low total power levels. It may be that there is a poor connection on one of the SMAs...The target values for the total power readings is 56000. this can be checked by the command dbbcif[abcd]. If the levels are too high or low, then adjust the attenuation on the IF box. | ||
| **Mark5B** | **Mark5B** | ||
/home/www/auscope/opswiki/data/pages/operations/documentation.ivs.txt · Last modified: 2013/10/03 05:22 by Imogen Jones
Page Tools
