ANN starts 060626 [This is the date you start processing, not the observing date] WALTER helped! ** Nothing to report in the log file; all ok. ** The drift is 17p2 +040812 {Be sure to note the declination!} ** This is a spring drift.... ** The pos file name is therefore: pos_060407a_+040812s.sav -- Working in: /home/dorado5/amartin/06.04.07a cp /home/dorado13/galaxy/idlraw/06.04.07a/*list* . gedit cal060407a.list [make triplets] gedit drift060407a.list [add directory to name] >idl >@wasinit2 >@alfinit -- Perform the calibration, in 2 steps: > callist='cal060407a.list' [assuming you already editted it...] > dir='/home/dorado13/galaxy/idlraw/06.04.07a' [where the raw IDL files are] > calib1,callist,dcalON,dcalOFF,dir=dir > help,dcalon,/st > calib2,dcalON,dcalOFF,ncalib > Any bad boards in system? > help,ncalib,/st > save, ncalib,file='ncalib_060407a.sav' [Please note the naming convention!] ** There are 27 cal values for this run *** ** The calibration for this run looks fine. One point was excluded from several boards. ** -- Set up and run the BPD gui. > bpdgui Enter the new calsession: calsession_060407a.sav Enter the new runpos: pos_060407a_+040812s.sav ***Note the format and syntax!*** the "s" before ".sav" stands for "spring" for fall drifts, use "f.sav" Be sure to set CRAT to "fit", not "median" **The interp regions here are [3490 to 3515]. ** You are now ready to run! Click "Process BP" and go to lunch. When that is done, check that the pos file has been correctly written. -- restore,'pos_060407a_+040812s.sav' help,pos This should tell you that "pos" is array with dimension equal to the number of drifts that were processed. ** There are 27 drifts for this run ** Next, start working on FLAGBB: -- restore,'pos_060407a_+040812s.sav' -- restore,'d214400+294831.526180333.sav' -- flagbb,dred,cont_pt,mask,pos,GAUSAV=11,HAN=3,AGC=1,n1=0,n2=6 at end, save badboxes to file filename = bb then save pos file in case of crash save,pos,file='pos_060407a_+040812s.sav' Thereafter, hit "o" to enter your own filefor BADBOX -------------------------------------------------------------------------------- Keep track of all the drift, give a quality and comment on AGC galaxies detected, others, or rfi problems. Please not any occurrences of GPS. d121500+040812.609685272.sav q1 2AGC strong cont src(6,1) stringiness in 2.1 d122507+040812.609685877.sav q2 2AGC scruff(non-pol) in 3, sw @low chnnrs(faint 4.1, strong 0.1); many small features d123514+040812.609700082.sav q2? Nada sw(early,low chnnr, 0.1); 3,5,2: strange "beating" pattern in time/RA domain d124520+040812.609700687.sav q2? 1AGC same pattern (approx 75s period) in 3,5,2 d125527+040812.609701292.sav q2? 5AGC same pattern d130534+040812.609701897.sav q2? Nada same pattern, sw 0.1(late, low chnnr) d131540+040812.609702502.sav q2 Nada same pattern, sw 2.0(late,hi chnnr), severe sw 2.1 d132547+040812.609703107.sav q2 1AGC same pattern d133554+040812.609703712.sav q2 1AGC same pattern, cont src(6,1) d134600+040812.609704317.sav q2 1AGC same pattern, sw 2.0(early) d135607+040812.609704922.sav q2 Nada same pattern, strong cont src(6,1) at high rec d140630+040812.609705527.sav q2 1AGC same pattern d141637+040813.609706148.sav q2 3AGC same pattern, cont src(1) d142643+040813.609706753.sav q1? 2AGC same pattern but weaker d143650+040812.609707358.sav q1 2AGC same pattern, cont src(6,1) d144657+040813.609707963.sav q1 Nada cont src(4,3,5,0,2,6,1) d145703+040813.609708568.sav q2 Nada GPS, cont src(4,3,5,0,6,1) d150710+040812.609709173.sav q1 Nada cont src(2,6,1) d151717+040812.609709778.sav q1 Nada cont src(4,3,5,0,2) d152724+040813.609710383.sav q1 Nada cont src(5,0) d153730+040813.609710988.sav q1 1AGC cont src(4,3,5,0,2) d154737+040813.609711593.sav q1 Nada cont src(2,6,1) d155744+040812.609712198.sav q2 Nada cont src(6,1) d160750+040813.609712803.sav q1 Nada cont src(3-severe,5,0,2) d161757+040813.609713408.sav q1 Nada cont src(5,0) d162804+040812.609714013.sav q2 Nada same pattern d163810+040812.609714618.sav q2 Nada same pattern, sw(2.0) save,pos,file='pos_060407a_+040812s.sav' 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 good data, except for bm 6, which has frequent power jumps ** altering Sw pattern. In 3 scans GPS is so strong as to mess up full spetrum, ** esp in 535016433 (last scan), rendering some boards nearly unusable.