Last update: 09Aug20 mph THIS IS A TEMPLATE LOG PROCESSING FILE. EDIT AS NECESSARY. -- REMOVE THE DETAILED INSTRUCTIONS AS YOU PROCEED. -- BE SURE TO ADD ANY COMMENTS RELEVANT TO THE REDUCTION, DATA QUALITY ETC. THE MORE YOU NOTE THAT IS UNUSUAL OR EXCITING, THE BETTER.... -- BE SURE TO READ CAREFULLY THE DETAILED INSTRUCTIONS ON LEVEL I PROCESSING. -- PLEASE IDENTIFY YOUR COMMENTS WITH "**" AS BELOW. -- PLEASE DELETE comments/extra lines which are irrelevant to future use of this file. -- Hint: Do global replaces in this file of "05.12.09a" with the designation of your block as yy.mm.dd "051209a" similarly with "yymmdd" "+092924" with the declination of your strip "+ddmmss" There are several other places where you will have to change directories etc., and make sure the pos file has the correct designation as "s" for "spring" or "f" for fall. YOURNAME starts 051209 [This is the date you start processing, not the observing date] BE SURE TO CHECK THE OBSERVING LOG FILE AND NOTE ANYTHING UNUSUAL HERE. Include any relevant comments about the observing run (e.g. were the WAPP errors requiring splitting of the cals?) If there isn't anything to report, note that too! ** Nothing to report in the log file; all ok. ** The drift is 39p2 +092924 {Be sure to note the declination!} ** This is a spring drift.... {If it's a fall drift be sure to change!!} ** The pos file name is therefore: pos_051209a_+092924s.sav {or "f.sav' for fall} ** ** If the block includes more than a single calibration period, either because ** a hardware failure caused the power to be readjusted or because more than ** one drift was acquired, please maintain separate calsession/ncalib files, ** identifying them uniquely by adding "_N", N=1,2,3... to the file name. ** You will also APPEND the pos file (rather than starting a new one) after ** the first run of BPD (See below). ** -- Working in: /share/a2010-2/work/haynes/05.12.09a cp /share/a2010-2/data/05.12.09a/*list* . gedit cal051209a.list [make triplets] gedit drift051209a.list [add directory to name] >idl >@wasinit2 >@alfinit -- Perform the calibration, in 2 steps: > callist='cal051209a.list' [assuming you already editted it...] > dir='/share/a2010-2/data/05.12.09a' [where the raw IDL files are] > calib1,callist,dcalON,dcalOFF,dir=dir This runs quickly; check that it worked: > help,dcalon,/st > calib2,dcalON,dcalOFF,ncalib You will be asked: > Any bad boards in system? Answer "n" if none. The current mask will be displayed. Step though the beams. If ok, just hit return. The calratios (Cal/TPcalON-TPcalOFF) and Tsys will be displayed for the drift. Note the amplitude of the variation in calrat (~1 degree). If ok, hit "enter" and fit=1 (or 2 or 3... judge for yourself - think about the statistical significance of anything higher than 3 -- but sometimes curvature is needed and warranted!). Keep track of anything unusual (points deleted, high Tsys etc). Check that it created the file ok: > help,ncalib,/st Save the file (Very important!!) > save, ncalib,file='ncalib_051209a.sav' [Please note the naming convention!] {Then comment on the calibration; was it "normal"? Did you have to delete points?} ** There are 18 cal values for this run *** ** The calibration for this run looks very nice. There is one CalRat for Beam 2, both pols, which is off; the Tsys is also high; probably a continuum source; point deleted. ** If you want, you can plot some of the values (you don't have to do this): > restore,'ncalib_051209a.sav' > plot,ncalib.rahr0,ncalib.decdeg0,psym=4 -- Set up and run the BPD gui. > bpdgui Set the Ncalib file (upper right; use "browse"): The mask should appear in red in the Calmask regions box The Tcals etc should appear. Set the list of files (upper left; use "browse"): drift051209a.list. This takes a minute to load; a small box will appear saying "N files loaded"; click ok and then check that all appears ok. The list of files should appear in the "files list", along with the default interpolation regions; you'll check this below. Coordinates should also appear in the relevant box. In normal circumstances, the #drifts should be equal to #cal values. Check that your drift list has all the files.... and no blank lines! Enter the new calsession: calsession_051209a.sav Enter the new runpos: pos_051209a_+092924s.sav ***Note the format and syntax!*** the "s" before ".sav" stands for "spring" for fall drifts, use "f.sav" **unless you need to APPEND the pos to a previous one already created for the same block, in the event of split cals. Then use the same name but be sure to use the APPEND option. Be sure to set CRAT to "fit", not "median" Now inspect the galactic hydrogen interpolation regions. You want to look at 3 spectra (beginning, mid, end). For each, click on the file in the "raw files" window; after it loads, click interpolation regions. When the spectrum pops up, enter min,max channels a bit beyond the default inter regions (e.g. 3460, 3540 where the regions are 3480, 3520) and hit "zoom". Identify the channels where the galactic HI begins to rise (e.g. here 3485 to 3515); click done, and go to the others. Find the maximum range needed for your spectra. Then click on any one of the entries in the "Interp regions" box. The Inter Reg Edit widget will appear. Enter these new values (usually only 2) and then click "apply to all". The values in the display should update. Be sure to record the interpolation regions here. **The interp regions here are [3485 to 3517] except for the drift ** **around 01h30 where they are set to [3490-3530], to accomodate M33.** You are now ready to run! Click "Process BP" and go to lunch. Often, when BPD finishes, there are some warning messages like % Program caused arithmetic error: Floating underflow % Program caused arithmetic error: Floating overflow % Program caused arithmetic error: Floating illegal operand That should not be a further problem. When that is done, check that the pos file has been correctly written. -- restore,'pos_051209a_+092924s.sav' help,pos This should tell you that "pos" is array with dimension equal to the number of drifts that were processed. ** There are 18 drifts for this run ** It is advisable to logout of IDL after running BPD and restart it. You may also wish to make a copy of the pos file, just in case (of future user error....). Next, start working on FLAGBB: Simple rules: 1. Pay close attention! It is IMPERATIVE that you do a good job. A bad job is worse than no job and will earn you snickers (and we don't mean the candy bar!). 2. Be sure to use the "t" option. 3. Know how big to make your boxes; use the "m" key when you need to! 4. Know what is a continuum source; do not flag continuum sources. 5. Know what is galactic hydrogen; do not flag galactic hydrogen (or HVC's!). 6. Know when to set the status flag. 7. Save the pos file regularly; occasionally make a copy of it. NOTE: In 2010, there is a new version of flagbb that allows you to go back, using the "b" command. Be sure you have the new code! -- restore,'pos_051209a_+092924s.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_051209a_+092924s.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 note any occurrences of GPS (indicate record nrs). d071606+092924.534309061.sav Q1 1 AGC 4/1, 5/1, 6/0-1 poor (power jumps) d072613+092924.534309666.sav Q1 nada d073619+092924.534310271.sav Q1 nada sw 5/1, 6 d074626+092924.534310876.sav Q1 nada strong GPS burst rec 150-215 d075633+092924.534311481.sav Q1 nada (!; none of sev AGC) d080640+092924.534312086.sav Q1 nada d081646+092924.534312691.sav Q2 1 AGC d082653+092924.534313296.sav Q1 1 AGC d083660+092924.534313901.sav Q1 2 AGC d084707+092924.534314506.sav Q2 nada intermods d085713+092924.534315111.sav Q2 maybe 1 AGC intermods d090720+092924.534315716.sav Q1 nada d091727+092924.534316321.sav Q1 nada d092734+092924.534316926.sav Q1 2 AGC d093740+092924.534317531.sav Q1 4 AGC (a group here) ** Be sure to save your pos file regularly! save,pos,file='pos_051209a_+092924s.sav' You can inspect the averaged, smoothed datasets for each beam using STRIP_PV and INSPECT 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 You can review your flagging using reviewbb,dred,cont_pt,mask,pos,GAUSAV=11,HAN=3,AGC=1,n1=0,n2=6 When you think you have completed a whole session, check that you did not miss any drifts by insuring that box 0 is assigned in each one: > print,where(pos.badbox[0,0,0,2] eq 0) If any number is returned, then that drift (remember to start from "0" when you count down the list) has not been flagbb'd correctly. If you get "-1", then you are almost done! There is just one more step; note this is new as of August 2009. Check that all the boxes you have flagged are valid: > check_pos,pos If any problems are returned, fix them. If not, then you are done! Also at the end, add any general comments about the run, note non-AGC galaxies and anything else that seems particularly interesting or exciting. These comments will be used immediately to identify targets for followup work, so some judgement needs to be exercised as to whether you really believe in the detection/identification. Consult an expert where unsure. On the other hand, if you've found something really interesting, we want to followup asap! ** Overall this is a good dataset, with good baselines and not much rfi ** OR ** 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. ** Non=AGC galaxies as follows: ** drift beam rec chan vel optID? optpos comment ** d235543 0 430 3348 776 good 2356430+295318 small blue dwarf ** d021714 1 44 2345 6062 maybe 0218510+294040 spiral? ** ** Wright's cloud detected in several drifts. ** AGC 121174 (KKH13) 0238162+295421 cz = 690 km/s strong and narrow, beam 4; nearby dwarf The more information of relevance you convey here, the more helpful to people later trying to track down some mysterious problem. Also if you find anything **really** interesting and are not sure what it means or whether it **really** is interesting, consult with an expert. Perhaps you have made a great discovery! Anyway, good luck, happy hunting, and thanks for contributing to ALFALFA!