Martha starts 06.03.17 Betsey resumes 09.06.02 ** Beam 5.1 is causing problems with power levels. See log file. ** In processing the callist, I see big jumps on the CalRat for ** Beam 5.1, so I am skipping it. ** The drift is 31p1 +072518 ** This is a fall drift.... ** The pos file name is therefore: pos_060908_+072518f.sav ** -- Working in: /home/arecibo10/galaxy/flagbb/proc/06.09.08 cp /home/arecibo10/galaxy/idlraw/06.09.08/*list* . gedit cal060908.list gedit drift060908.list >idl >@wasinit2 >@alfinit -- > callist='cal060908.list' > dir='/home/arecibo10/galaxy/idlraw/06.09.08' > calib1,callist,dcalON,dcalOFF,dir=dir > help,dcalon,/st > calib2,dcalON,dcalOFF,ncalib > Any bad boards in system? y How many bad boards? [enter n] : 1 Enter nbeam, npol of bad board : 5, 1 > help,ncalib,/st > save, ncalib,file='ncalib_060908.sav' ** There are 25 cal values for this run *** ** There is some power drop in one of the middle scans; ** Ignore those points in fitting cal. ** There is a cont source in Beam 3 ** Beam 5 should large variation in CAl ratio; ** So I ignore it in processing ** -- > bpdgui Enter the new calsession: calsession_060908.sav Enter the new runpos: pos_060908_+072518f.sav Be sure to set CRAT to "fit", not "median" **The interp regions here are [3485 to 3520] ** help,pos ** There are 25 drifts for this run ** -- restore,'pos_060908_+072518f.sav' -- restore,' d214400+294831.526180333.sav' -- flagbb,dred,cont_pt,mask,pos,GAUSAV=11,HAN=3,AGC=1,n1=0,n2=6 filename = bb save,pos,file='pos_060908_+072518f.sav' -------------------------------------------------------------------------------- d212001+072519.625181318.sav q1 nada cont 6,1 d213008+072519.625181923.sav q1 0 AGC sw 4.1; FAA radar on, other RFI present d214014+072519.625182528.sav q2 0 AGC GPS burst recs 135-360 d215021+072519.625183133.sav q1 1 AGC d220028+072519.625183738.sav q1 0 AGC sw 4.1; cont 5 d221034+072519.625184343.sav q2 0 AGC some power level changes; strong rfi; sw 1.1 d222041+072519.625184948.sav q3 0 AGC 3.1,5.0,2.0,1.1 striped; sw 1.1; stat=2 for 5.0,2.0,1.1 d223047+072519.625185553.sav q2 0 AGC slight sw bm4,3,1; strong rfi, poor baselines for all beams d224054+072519.625186158.sav q2 2 AGC + 1 nAGC strong rfi and some striping d225101+072519.625200363.sav q1 1 AGC HVC; FAA still strong but everything else is better d230107+072519.625200968.sav q1 0 AGC HVC; mods 1.0; a group here but no clear HI detections d231114+072519.625201573.sav q1 5 AGC 2.0 slight spikes d232120+072519.625202178.sav q1 0 AGC HVC d233127+072519.625202783.sav q1 3 AGC 2 large HVCs d234134+072519.625203388.sav q1 0 AGC HVC d235140+072519.625203993.sav q1 0 AGC HVC d000147+072519.625204598.sav q1 0 AGC mods 1.0 ** Be sure to save your pos file regularly! save,pos,file='pos_060908_+072518f.sav' strip_pv,dred,cont_pt,msmooth,n1=0,n2=6,showpol=3,gausav=11,han=5,rfimod=0,units=1 inspect,msmooth,showpol=3,nstrip=4,agc=1 reviewbb,dred,cont_pt,mask,pos,GAUSAV=11,HAN=3,AGC=1,n1=0,n2=6 > print,where(pos.badbox[0,0,0,2] eq 0) ** Overall this is a somewhat poor dataset ** ** FAA radar is strong and other RFI is present (eg 8,12,etc) ** ** A few drifts suffer from poor data quality with lots of RFI ** ** The pos file has more entries than drifts listed - some of the drifts are listed twice ** ** This means the 'p' option in flagbb can't be used ** ** Non=AGC galaxies as follows: ** drift beam rec chan vel optID? optpos comment ** d224054 1 51 2050 7660 good 2241410+073129 merging/irregular system