Combining data sets of different array configurations and different observation dates ===================================================================================== data combining recipe v. 1.0 : Dana Ficut-Vicas 22Dec08 data combining recipe v. 2.0 : Dana Ficut-Vicas 5Jan09 data combining recipe v. 2.1: Dana Ficut-Vicas 2Mar09 data combining recipe v. 4: Dana Ficut-Vicas 20Jul09 data combining recipe v. 5: Dana Ficut-Vicas 23Jul09 data combining recipe v. 6: Dana Ficut-Vicas 23Sepember09 (DO NOT SMOOTH in Wiper warning!) data combining recipe v. 7: Dana Ficut-Vicas 8February10 (Blanking related changes, UVDEC issues) data combining recipe v. 8: Dana Ficut-Vicas 10February10 (2.5 sigma level in the natural weighted cube) Data reduced by Trisha Ashley, Florida International University; 1st of September 2010 1. Newly observed data %%% NOTE: LINCOP data had 20 channels from each end removed during calibration, no need for extra UVCOP. A. Spliting the data and applying the calibration and the flags. ###Note: Check values for GAINUSE and FLAGVER in case of non-standard reduction. executed on 01Sep10 DEFAULT SPLIT Sources 'haro29',''; Qual -1; Calcode ''; Timerang 0; Stokes ' '; Selband -1; Selfreq -1; Freqid 1; Bif 0; Eif 0; Bchan 1; Echan 0; Subarray 0; Docalib 1; Gainuse 3; Dopol -1; Blver -1; Flagver 2; Doband 1; Bpver 1; Smooth 0; Douvcomp -1; Aparm 0; Nchav 1; Chinc 1; Ichansel 0; Baddisk 0 B.Cliping the hot pixels Either check calibration recipe WIPER on source result or run a quick WIPER to select the CLIP level. DO NOT SMOOTH within WIPER!!! Clip levels for: B1: 16 mJy B2: 14 mJy C1: 16 mJy C2: 16 mJy CnB: 14 mJy D1: 16 mJy D2: 14 mJy executed on 01Sep10 DEFAULT CLIP aparm 0 aparm(1) 16 $ clip any parallel hand visibilities amplitude greater than 16mJy; $B2, CnB, and D2 --->aparm(1) 14 getn *.SPLIT C.2 Shifting the data with Hanning smoothing This step is needed if data are to be combined with archive data observed with Hanning smoothing. C.2.1 executed on 01Sep10 DEFAULT CVEL outname 'Haro29b1'; outcl 'cvel'; outdi 1; aparm 0, 108, 1, 0, 1420E6, 405752, 1, 0, 0; $aparm(2)=the reference pixel which can be found in $the header;aparm(5) and aparm(6)set the Hydrogen $rest frequency;aparm(3)to choose heliocentric as $velocity type;aparm(7)=1 for VLA data; aparm(1)=281e3; $the velocity you want in the central channel aparm(9)=2 $smooth crosscorrelation spectra by Hanning sources ''; qual -1; timerang 0; selband -1; selfreq -1; freqid 1; subarray 0; flagver 1; $apply the flag table which we created when clipping doband -1; bpver -1; gainuse 0; getn *.SPLIT C.2.2. Checks: ### Spectrum is shifted, but there is no change in the header frequency, so you need to run a few checks. C.2.2.1. Has CVEL done anything? executed on 01Sep10 DEFAULT POSSM docal -1 ; doband -1; freqid 1 $ set this to match the calibrator flagver 1; aparm 0 $ Plot data solint 0 $ average all time nplots 0 $ average all baselines aparm 0 aparm(1) 0 $ scalar average source='Haro29','' dotv 1 tvinit grchan 1; getn *.SPLIT flagver -1;grchan 2; getn *.CVEL ###You should see the SPLIT and the CVEL do not overlap perfectly C.2.2.2. CVEL shifts the spectum so some channels, either at the begining , either at the end will end up without real, valid information. To identify those we use possm to look at the begining and ending channels. You will recognize them by having very low values compared with the rest. The number of these kind of channels depends on how much the spectrum has been shifted. executed on 01Sep10 DEFAULT POSSM docal -1 ; doband -1; freqid 1 flagver -1; aparm 0 $ Plot data solint 0 $ average all time nplots 0 $ average all baselines aparm 0 aparm(1) 0 $ scalar average source='Haro29','' bchan 1;echan 20; $ choose the beginning 20 channels to make more obvious $ the channels with invalid information dotv 1 tvinit getn *.CVEL DEFAULT POSSM docal -1 ; doband -1; freqid 1 flagver -1; aparm 0 $ Plot data solint 0 $ average all time nplots 0 $ average all baselines aparm 0 aparm(1) 0 $ scalar average source='Haro29','' bchan 195;echan 215; $ choose the last 20 channels to make more obvious $ the channels with invalid information dotv 1 tvinit getn *.CVEL B1: The number of beginning channels with invalid information: 1 The number of end channels with invalid information: 1 B2: The number of beginning channels with invalid information: 1 The number of end channels with invalid information: 1 C1: The number of beginning channels with invalid information: 1 The number of end channels with invalid information: 1 C2: The number of beginning channels with invalid information: 1 The number of end channels with invalid information: 1 CnB: The number of beginning channels with invalid information: 6 The number of end channels with invalid information: 0 D1: The number of beginning channels with invalid information: 1 The number of end channels with invalid information: 1 D2: The number of beginning channels with invalid information: 3 The number of end channels with invalid information: 0 ###Note: For the moment we just take a note of this channels. We can get rid of this channels at a later stage, when we are triming in preparation for DBCON, which requires all data sets to have the same number of channels.If for any paritcular reason we decide not to get rid of these invalid channels at that stage, then they should be excluded from the continuum subtraction. C.2.3.1 CVEL will shift and smooth for you, however it will not get you rid of the every second channel which will be the case in a Hanning smoothed data set in the archive.To do that we use UVDEC. executed on 02Sep10 DEFAULT UVDEC chinc 2; $to take every second channel outn 'Haro29b1';outcl 'UVDEC' bchan 2;echan 0; getn *.CVEL ## In UVDEC is necessary to ensure that among the channels you are taking is the reference pixel.If before CVEL you had an odd number of channels than the reference pixel will be in an odd channel number so in UVDEC you want to take chnnels 1, 3, 5 etc. (see above). C.2.3.2 UVDEC has been found not to update the header properly(This should have been fixed by Eric in the mean time). However if it still happens, then the header has to be updated by hand. The problem is with the ALTRPIX which is not updated. This should be the same as the REFPIX. inp gethead getn *.UVDEC keyword 'ALTRPIX' gethead inp puthead keyval 54,0 inp puthead puthead imh $ to check if it worked ######UVDEC is likely to introduce more trouble, it may introduce a phase shift. It will appear in the header as: AIPS 1: Phase shifted in X 0.000 in Y 1800.000 #####Check for it by comparing the headers before and after UVDEC. If after UVDEC you have a phase shift then correct for it as follows. inp gethead getn *.UVDEC keyword 'YSHIFT' gethead inp puthead keyval 0 inp puthead puthead imh $ to check if it worked 4. Repeat 1 or 2 for all the data sets that you have on one particular galaxy (for Haro29 there are 7 in total) 5. Now we glue the three array configurations together in one dataset. A. We trim the data sets where necessary to ensure same number of channels in all data sets and the same velocity in the central channel.At this stage one might consider trimming away the channels with invalid information created by CVEL, or alternatively if one is trimming the archival data to the number of channels of the new data, it might be more time efficient to trim the beginning or end channels of invalid information created by CVEL after the glueing stage of DBCON. executed on 02Sep10 DEFAULT UVCOP outcla 'TRMCOP'; bchan 4;echan 106; $the decision is taken comparing all imheaders uvcopprm 0; uvcopprm(4) 1; getn *.UVDEC B. Glueing. ###Unfortunately DBCON is glueing only two data sets at a time. executed on 02Sep10 DEFAULT DBCON Reweight 0 0; Outname 'haro29b12'; Dopos 0; Doarray 0; Fqtol 0 getn haro29b1.trmcop get2n haro29b2.trmcop ----> haro29b12.dbcon outname 'haro29b12c1' getn haro29b12.dbcon get2n haro29c1.trmcop ----> haro29b12c1.dbcon outname 'haro29b12c12' getn haro29b12c1.dbcon get2n haro29c2.trmcop ----> haro29b12c12.dbcon outname 'har29b12c12n' getn haro29b12c12.dbcon get2n haro29cnb.trmcop ----> har29b12c12n.dbcon outname 'haro29bcd1' getn haro29b12c12n.dbcon get2n har29d1.trmcop ----> haro29bcd1.dbcon outn 'haro29bcd' getn haro29bcd1.dbcon get2n haro29d2.trmcop ----> haro29bcd.dbcon C. Checks: executed on 02Sep10 DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29.first'; cellsize 1.5; imsize 1024; niter 1000; uvwtfn 'na'; dotv -1; calcode '-cal'; getn haro29bcd.dbcon ##Also inspect the data with TVMOVIE and find which are the Line channels %%% NOTE: Some really awesome rotation, looks like a search light! The line channels are: 25-75 6. Continuum subtraction A. Subtracting the continuum: executed on 02Sep10 ###Before subtracting the continuum make sure that the channels with invalid information created by CVEL when shifting were trimmed away using UVCOP. Those channels should not be used in the continuum subtraction. If they were not removed, their input can be avoided by setting ICHANSEL in UVLSF and AVSPC. DEFAULT UVLSF Shift 0 0; Flux 0; Dooutput -1; Ichansel 1,18,1,0,80,103,1,0; Order 1; infil '' getn *.DBCON B. Creating the continuum map: executed on 02Sep10 DEFAULT AVSPC avoption ''; flagver -1; bif 0;eif 0; channel 0; outcl 'UVCONT' Ichansel 1,18,1,0,80,103,1,0; $the line free channels getn *.DBCON ###To make a continuum map we thus need a proper cleaning down to a flux level which depends on how many line free channels we have. A quick and dirty IMAGR is necessary here to establish the flux level to clean down to. DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'continuum'; cellsize 1; imsize 2048; niter 1000; uvwtfn '';dotv -1; calcode '';robust 0.5; getn *.UVCONT Rms noise is: 0.129mJy DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'continuum'; cellsize 1; imsize 1024; $in a complex field one might need 2048 niter 10000; uvwtfn ''; dotv -1; calcode '';robust 0.5; flux 0.00026 $it should be set to a 2 sigma level getn *.UVCONT C. Checks executed on 02Sep10 Making a dirty cube of the continuum subtracted data DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29'; cellsize 1.5; imsize 1024; niter 1e6; uvwtfn ''; dotv -1; calcode '-cal';imagrprm(10) 1 bchan 1; echan 0;robust 0.5; flux 0.0045 $set this to 3 times the sigma of the B array dirty cube getn *.UVLSF ###Having a whole dirty cube at this stage will enable you to decide what the MSCLEAN IMAGR window should be.Use TVWIN to get coordinates of the window you mark yourself on the TVscreen. blc= 366 356 trc= 647 668 ###Some close by galaxies might need a 2048 imsize in IMAGR;this necessity will become obvious when looking at the D array data. ##Inspect the cube and note down the noise level. In this particular case it was: 0.5 mJy robust 0 7. Imaging A. Noise TESTS: We need the rms noise in a line free channel as given by MSCLEAn with no cleaning.The rms noise is measured by setting a window with TVWIN and than running an IMSTAT.It is this noise level that we will further use with MSCLEAN. DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 0 $ no fgauss levels are necessary as we are not cleaning niter 0 $no cleaning, we just want to quantify the rms noise nbox 1 clbox 366.00 356.00 647.00 668.00 $enough to hold all the signal in every channel $its size should have been decided at step 6C bchan 12;echan 16; $select one or more line free channels outn 'noise' imagrprm 0; imagrprm(10) 1; $multiplier of max image size to set beam size imagrprm(11) 0.2; $the alpha parameter, which steers MSCLEAN towards certain scale components The rms noise measured in a line free channel is: Field 1(5asec resolution): 0.517 mJy Field 2(15 asec resolution): 0.7 mjy Field 3(45 asec resolution): 1.06 mJy Field 4(135 asec resolution): 2.053 mJy B. Tuning our multi-resolution clean parameters executed on 02Sep10 DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 2*0.517e-3 2*0.7e-3 2*1.06e-3 2*2.053e-3 $ fgaus 2sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 366.00 356.00 647.00 668.00 $enough to hold all the signal in every channel $its size should have been decided at step 6C bchan 45;echan 50;outn 'test1' imagrprm 0; imagrprm(10) 1; $multiplier of max image size to set beam size imagrprm(11) 0.2; $the alpha parameter, which steers MSCLEAN towards certain scale components getn Har029_BCD.UVLSF Noise level: 0.5-2.3 millyJy #### Look at the maps, see if there are any indicatives of calibration problems or imaging problems ########Monitor the AIPS_MSGRV for any warning messeages especiallly ones like : "SOMETHING IS GOING WRONG.ABANDON CLEAN" or "Clean has begun to diverge.Stopping". IMAGR is running too fast to be able to make a true statistics of these messages, that is why the easiest way to go is after running IMAGR, run a PRTMSG and write the messages in a text file where you can easily scroll through and even use a query-replace to replace the text of the offending messages with more obvious lines of text to be able to see them faster. %%% NOTE: No error messages default prtmsg prtask 'IMAGR' $ the task for which you want the aips messages prtime 1 $ all IMAGRS younger than 1 day ouprint ' $ the name of the file to write to docrt -1 prtmsg &prtmsg is a verb not a task C. If satisfied with the above than put the whole cube through this imaging recipe executed on 02Sep10 DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29'; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 2*0.517e-3 2*0.7e-3 2*1.06e-3 2*2.053e-3 $fgaus 2sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 366.00 356.00 647.00 668.00 imagrprm 0; imagrprm(10) 1; $multiplier of max image size to set beam size imagrprm(11) 0.2; $the alpha parameter, which steers MSCLEAN towards certain scale components getn *.UVLSF ###Some close by galaxies might need a 2048 imsize in IMAGR;this necessity will become obvious when looking at the D array data. #### Look at the maps, see if there are any indicatives of calibration problems or imaging problems ########Monitor the AIPS_MSGRV for any warning messeages especiallly ones like : "SOMETHING IS GOING WRONG.ABANDON CLEAN" or "Clean has begun to diverge.Stopping". IMAGR is running too fast to be able to make a true statistics of these messages, that is why the easiest way to go is after running IMAGR, run a PRTMSG and write the messages in a text file where you can easily scroll through and even use a query-replace to replace the text of the offending messages with more obvious lines of text to be able to see them faster.See above, at step 7B for how to set PRTMSG. ###########Limit your cleaning if your science project allows it to the channels with line emission. In this sense worry if you see the above mentioned offending messages in line emission channels. Also it is possible that IMAGR scoops in one field, shoots out the message, gets out of the major cycle, restores components in all fields and by doing so also corrects the negativity of the problematic field.In the message file, where you see IMAGR after having given the warning message, return to that same field it means that MSCLEAN was able to correct itself. The big worry comes in when MSCLEAN stops cleaning alltogether, especially when that happens in a line emission channel. ##################Report any galaxies that do not comply to the above set of parameters.When you find that cleaning leaves behind a negative bowl, or when you find repeated offending messages with no indication of MSCLEAN correcting itself, let Elias or Dana know.Thanks Computing the noise levels for the natural weigthing setting: DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 0 $ no fgauss levels are necessary as we are not cleaning niter 0 $no cleaning, we just want to quantify the rms noise nbox 1 clbox 366.00 356.00 647.00 668.00 $enough to hold all the signal in every channel $its size should have been decided at step 6C bchan 12;echan 16; $select one or more line free channels outn 'noiseNA' imagrprm 0; imagrprm(10) 1; $multiplier of max image size to set beam size imagrprm(11) 0.2; $the alpha parameter, which steers MSCLEAN towards certain scale components uvwtfn 'na' The rms noise measured in a line free channel is: Field 1(5asec resolution): 0.48 mJy Field 2(15 asec resolution):0.695 mjy Field 3(45 asec resolution):1.05 mJy Field 4(135 asec resolution): 1.127 mJy Making a natural weighted data cube: DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29NA'; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 2.5*0.48e-3 2.5*0.695e-3 2.5*1.05e-3 2.5*1.127e-3 $fgaus 2.5sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 366.00 356.00 647.00 668.00 imagrprm 0; imagrprm(10) 1; $multiplier of max image size to set beam size imagrprm(11) 0.2; $the alpha parameter, which steers MSCLEAN towards certain scale components uvwtfn 'NA' $this will override the robust setting getn *.UVLSF 8. Convolution and Blanking executed on 04Sep10 A. Convolution DEFAULT CONVL blc 0; trc 0; outname ''; opcode ''; bmaj 25; bmin 25 outclass 'CVL25' getn *NA.ICL001 ###We are going to use the NAtural weighted cube to create the master blanking cube. ### Get rms in convolved cube: 1.19e-3 B. Blanking B.1 Making contour plots to identify the true line from the noise. DEFAULT KNTR docont 1; dogrey -1;dovect -1; ny 3; ltype 6; clev 0.00119; levs 2.25, 5, 10, 20, 40, 80 $the lowest level is at 2.5sigma; $always between 2-2.5sigma); dotv 1; pixra -0.00238, 0.00952 $ pixrange=(-2sigma to +8sigma); docircle -1; blc 366.00 356.00 $ I used the same size as the window in IMAGR trc 647.00 668.00 getn *NA.CVL25 to get all interesting channels into PL files: for i=1 to 7;dotv -1; blc(3)= 25+(i-1)*9;trc(3)=24+i*9;go kntr;wait kntr; end to print all created PL files for i=15 to 21; plver =i; print i; go lwpla; wait lwpla; end %%% NOTE: Quite noisy at a 2 sigma level, 2.25 sigma worked much better (2.5 looked like it may have been missing too much). #########You do KNTR first with the lowest contour at 2 sigma ; if this is 'too busy' , run another KNTR with the lowest contour at 2.5 sigma, or even 3 sigma. Once you have found the best value for the lowest contour, you run the automatic blanking in B.2 with that level and blank everything below it. That way, the KNTR plots and the BLANKed cube will look absolutely identical %%% NOTE: There are two "blobs" of gas that may be separated from the galaxy in space that appear in channels 52-57 and 60-62. They are likely to just be seperated in velocity rather than in space, but to see the difference, two Master cubes will be made for these, the one with the extra "blobs" will be denoted with the word BLOB in the following files. B.2 Blank the cube at 2 sigma DEFAULT BLANK opcode 'SELC'; dparm 1, 0, 10000, 0.0026775, 0 outclass 'CVL_BL'; trc 0; blc 0; bchan 0; echan 0 getn *NA.CVL25 B.3 Blank cube by hand - output is the master cube DEFAULT BLANK opcode 'TVCU'; doinvers -1; outclass 'master' txinc 2; tyinc 2 getn *NA.CVL_BL B.4 use the master cube to blank the full resolution cube and the robust=0.5 cube DEFAULT BLANK opcode 'IN2C';outclass 'LMV'; getn *NA.ICL001 $the full resolution cube, the one created at step 7B get2n *.MASTER DEFAULT BLANK opcode 'IN2C';outclass 'LMV'; getn *.ICL001 $the full resolution cube, the one created at step 7B get2n *.MASTER ### It blanks the full resolution cube using the MASTER cube as a blanking model. 9. ON THE ROBUST CUBE 9.1 Transposing the cube executed on 04Sep10 DEFAULT TRANS outclass ''; blc 0; trc 0; transcod '312' getn *.LMV 9.2 Switching the header from frequency description to spectral-line velocity description getn *. TRANS ALTSWCH 9.3 Final products executed on 18May10 A. Moment maps: DEFAULT XMOM flux -10000; icut -10000; blc 0; trc 0 getn *.TRANS ###Note: The Primary beam correction(PBCOR) has not been applied. Something to think about would be which final products we want and which ones among those should be primary beam corrected#### 9.4 Primary Beam Corrections ***Corrects an image for the primary beam attenuation of the 25-meter antennas used at the VLA. altsw $PBCOR needs the FREQ axis rather than the velocity one $ use this verb to switch between the two DEFAULT PBCOR doinvers -1; coord 0; bparm 0; outclass 'X0_PBC' REMARK: If one wants to take a spectrum and needs the correct value of the flux in that spectrum, than the whole cube should be primary beam corrected. For more details contact Elias or Dana. 9.5 Replacing blanks with 0 DEFAULT REMAG pixval 0; blc 0; trc 0; outclass 'X0_P_R' getn *.X0_PBC REMARK: The REMAG task is useful not only for moment0 maps but for any map in which you would like the magic values of AIPS to be replaced with zeroes, for better data handling when outside AIPS(In programs like KARMA the magic values will disturb your histogram, in programs like IDL the magic values can lead to calculation errors). 10. ON THE NATURAL CUBE 10.1 Transposing the cube executed on DEFAULT TRANS outclass ''; blc 0; trc 0; transcod '312' 10.2 Switching the header from frequency description to spectral-line velocity description getn *. TRANS ALTSWCH 10.3 Final products executed on A. Moment maps: DEFAULT XMOM flux -10000; icut -10000; blc 0; trc 0 getn *.TRANS ###Note: The Primary beam correction(PBCOR) has not been applied. Something to think about would be which final products we want and which ones among those should be primary beam corrected#### 10.4 Primary Beam Corrections ***Corrects an image for the primary beam attenuation of the 25-meter antennas used at the VLA. altsw $PBCOR needs the FREQ axis rather than the velocity one $ use this verb to switch between the two DEFAULT PBCOR doinvers -1; coord 0; bparm 0; outclass 'X0_PBC' REMARK: If one wants to take a spectrum and needs the correct value of the flux in that spectrum, than the whole cube should be primary beam corrected. For more details contact Elias or Dana. 10.5 Replacing blanks with 0 DEFAULT REMAG pixval 0; blc 0; trc 0; outclass 'X0_P_R' getn *.X0_PBC REMARK: The REMAG task is useful not only for moment0 maps but for any map in which you would like the magic values of AIPS to be replaced with zeroes, for better data handling when outside AIPS(In programs like KARMA the magic values will disturb your histogram, in programs like IDL the magic values can lead to calculation errors). %%% NOTE: The "blobs" were not separated from the galaxy spatially, only in velocity. 11. Convolutions REMARK: If the beam size allows it is better to produce the convolved cube from the natural weighted cube which has a better signal to noise. %%%NOTE: Cannot convolve the natural weighted cube here because the beam size is already 12.42 X 7.92 . In light of this, the Robust Cube will be used for the convolution. DEFAULT CONVL bmaj 10; bmin 10; blc 0; trc 0; opcode ''; outna 'Haro29CV10_R'; outclass ''; doblank 0; factor 0; outse 0; getn *.ICL001 DEFAULT BLANK opcode 'IN2C';outclass 'LMV'; $ outname 'Haro29CvRblb' for the data blanked with the blob master cube getn *.CONVL get2n *.MASTER ON THE CONVOLVED CUBE 11.1 Transposing the cube executed on 10dec10 DEFAULT TRANS outclass ''; blc 0; trc 0; transcod '312' 11.2 Switching the header from frequency description to spectral-line velocity description getn *. TRANS ALTSWCH 11.3 Final products executed on 10dec10 A. Moment maps: DEFAULT XMOM flux -10000; icut -10000; blc 0; trc 0 getn *.TRANS ###Note: The Primary beam correction(PBCOR) has not been applied. Something to think about would be which final products we want and which ones among those should be primary beam corrected#### 11.4 Primary Beam Corrections ***Corrects an image for the primary beam attenuation of the 25-meter antennas used at the VLA. altsw $PBCOR needs the FREQ axis rather than the velocity one $ use this verb to switch between the two DEFAULT PBCOR doinvers -1; coord 0; bparm 0; outclass 'X0_PBC' getn *.XMOM0 11.5 Replacing blanks with 0 DEFAULT REMAG pixval 0; blc 0; trc 0; outclass 'X0_P_R' getn *.X0_PBC REMARK: The REMAG task is useful not only for moment0 maps but for any map in which you would like the magic values of AIPS to be replaced with zeroes, for better data handling when outside AIPS(In programs like KARMA the magic values will disturb your histogram, in programs like IDL the magic values can lead to calculation errors). 12. DAH: Before FITTPing the data to disk and then copying to NRAO, please do an ALTSWTCH on the map cubes so that the axis is in velocity units rather than frequency units. 14. Names of files For each uv data set: Haro29_B1_SPLIT.FITS Haro29_B1_CVEL.FITS Combined uv data: Haro29_BCD_DBCON.FITS Minus continuum: Haro29_BCD_UVLSF.FITS Continuum only, uv data and map: Haro29_BCD_UVCONT.FITS Haro29_CONTINUUM_ICL.FITS Product of MSclean: Haro29_NA_ICL001.FITS Haro29_NA_ICL002.FITS Haro29_NA_ICL003.FITS Haro29_NA_ICL004.FITS Haro29_R_ICL001.FITS Haro29_R_ICL002.FITS Haro29_R_ICL003.FITS Haro29_R_ICL004.FITS Blanking: Haro29_NA_CVL_BL.FITS Haro29_NA_MASTER.FITS (frequency changed to velocity) Haro29_NA_MASTER_BLOB.FITS kntr_2.25sigma kntr_2.5sigma kntr_2sigma Final blanked cubes: Haro29_NA_LMV.FITS (frequency changed to velocity) Haro29_NA_LMV_BLOB.FITS (frequency changed to velocity) Haro29_R_LMV.FITS (frequency changed to velocity) Haro29_R_LMV_BLOB.FITS (frequency changed to velocity) Moment maps: Haro29_NA_XMOM0.FITS Haro29_NA_XMOM1.FITS Haro29_NA_XMOM2.FITS Haro29_NA_XMOM3.FITS Haro29_NA_XMOMNC.FITS Haro29_NA_XMOM0_BLOB.FITS Haro29_NA_XMOM1_BLOB.FITS Haro29_NA_XMOM2_BLOB.FITS Haro29_NA_XMOM3_BLOB.FITS Haro29_NA_XMOMNC_BLOB.FITS Haro29_R_XMOM0.FITS Haro29_R_XMOM1.FITS Haro29_R_XMOM2.FITS Haro29_R_XMOM3.FITS Haro29_R_XMOMNC.FITS Haro29_R_XMOM0_BLOB.FITS Haro29_R_XMOM1_BLOB.FITS Haro29_R_XMOM2_BLOB.FITS Haro29_R_XMOM3_BLOB.FITS Haro29_R_XMOMNC_BLOB.FITS Moment zero, PBC and REMAG corrections: Haro29_NA_X0_PBC.FITS Haro29_NA_X0_PBC_BLOB.FITS Haro29_NA_X0_P_R.FITS Haro29_NA_X0_P_R_BLOB.FITS Haro29_R_X0_PBC.FITS Haro29_R_X0_PBC_BLOB.FITS Haro29_R_X0_P_R.FITS Haro29_R_X0_P_R_BLOB.FITS Convolved data: Cube: Haro29_CVL10_ICL001.FITS Blanked: Haro29_CVL10_LMV.FITS Moment maps: Haro29_CVL10_XMOM0.FITS Haro29_CVL10_XMOM1.FITS Haro29_CVL10_XMOM2.FITS Haro29_CVL10_XMOM3.FITS Haro29_CVL10_XMOMNC.FITS Moment zero PBC and REMAG corrections: Haro29_CVL10_X0_PBC.FITS Haro29_CVL10_X0_P_R.FITS