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 23Sep09 (DO NOT SMOOTH in Wiper warning!) data combining recipe v. 7: Dana Ficut-Vicas 8Feb10(Blanking related changes, UVDEC issues) data combining recipe v. 8: Dana Ficut-Vicas 10Feb10( 2.5 sigma level in the natural weighted cube) DAH: Add altswtch 090610 DAH: Add naming convention 141010 data combining recipe v. 9: Dana Ficut-Vicas 26Oct10 (clarification regarding the convolution step) Data reduced by Trisha Ashley, Florida International University; 13th of December 2010 1. Newly observed data %%% NOTE: LINCOP data had 20 channels from each end removed during calibration, there is no need for extra UVCOP. B.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 D.1 Shifting the data without Hanning smoothing to a common central velocity D.1.1 executed on 15dec10 DEFAULT CVEL outname 'Haro29b1_nh'; 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)=0 $don't smooth 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; outdisk 2 baddisk 1 getn *.SPLIT D.1.2. Checks: ### Spectrum is shifted, but there is no change in the header frequency, so you need to run a few checks. D.1.2.1. CVEL shifts the spectum so some channels, either at the begining , or at the end will end up without valid information. To identify those we use possm to look at the beginning and end 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 15dec10 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: 0 The number of end channels with invalid information: 0 B2: The number of beginning channels with invalid information: 0 The number of end channels with invalid information: 0 C1: The number of beginning channels with invalid information: 0 The number of end channels with invalid information: 0 C2: The number of beginning channels with invalid information: 1 The number of end channels with invalid information: 0 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: 0 The number of end channels with invalid information: 0 D2: The number of beginning channels with invalid information: 2 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 these 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 particular reason we decide not to get rid of these invalid channels at that stage, then they should be excluded from the continuum subtraction. 4. Repeat 1 or 2 for all the data sets that you have on one particular galaxy 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 13dec10 DEFAULT UVCOP outcla 'TRMCOP'; bchan 7;echan 215; $the decision is taken comparing all imheaders uvcopprm 0; uvcopprm(4) 1; getn *.CVEL B. Glueing. ###Unfortunately DBCON is glueing only two data sets at a time. executed on 13dec10 DEFAULT DBCON Reweight 0 0; Outname 'Haro29b12'; Dopos 0; Doarray 0; Fqtol 0 getn haro29.B1.trmcop get2n haro29.B2.trmcop ----> Haro29b12.dbcon outname 'Haro29bc1' getn Haro29b12.dbcon get2n haro29c1.trmcop ----> Haro29bc1.dbcon outname 'Haro29bc12' getn Haro29bc1.dbcon get2n haro29c2.trmcop ----> Haro29bc12.dbcon outname 'Haro29bc' getn Haro29bc12.dbcon get2n haro29cnb.trmcop ----> Haro29bc.dbcon outname 'Haro29bcd1' getn Haro29bc.dbcon get2n haro29d1.trmcop ----> Haro29bcd1.dbcon outn 'Haro29BCD_nh' getn Haro29bcd1.dbcon get2n haro29d2.trmcop ----> Haro29BCD.dbcon C. Checks: executed on 13dec10 DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29bcd_nh'; cellsize 1.5; imsize 1024; niter 1000; uvwtfn 'na'; dotv -1; calcode '-cal'; getn HARO29BCD_NH.DBCON ##Also inspect the data with TVMOVIE and find which are the Line channels The line channels are: ~60-150 6. Continuum subtraction A. Subtracting the continuum: executed on 16dec10 ###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,55,1,0,155,209,1,0; Order 1; infil '' getn *.DBCON B. Creating the continuum map: executed on 16dec10 DEFAULT AVSPC avoption ''; flagver -1; bif 0;eif 0; channel 0; outcl 'UVCONT' Ichansel 1,55,1,0,155,209,1,0; 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_nh'; cellsize 1; imsize 2048; niter 1000; uvwtfn '';dotv -1; calcode '';robust 0.5; getn *.UVCONT Rms noise is: 0.129 mJy DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'continuum_nh'; cellsize 1; imsize 1024; $in a complex field one might need 2048 niter 10000; uvwtfn ''; dotv -1; calcode '';robust 0.5; flux 0.000258 $it should be set to a 2 sigma level getn *.UVCONT C. Checks executed on 16dec10 Making a dirty cube of the continuum subtracted data DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29_nh'; 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. ###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.88323 mJy robust 0 blc=375 374 trc= 664 649 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 375 374 664 649 $enough to hold all the signal in every channel $its size should have been decided at step 6C bchan 30;echan 35; $select one or more line free channels outn 'noise_nh' 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.858 mJy Field 2(15 asec resolution):1.121 mjy Field 3(45 asec resolution): 1.731 mJy Field 4(135 asec resolution): 3.536 mJy B. Tuning our multi-resolution clean parameters executed on 14dec10 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.858e-3 2*1.121e-3 2*1.731e-3 2*3.536e-3 $ fgaus 2sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 375 374 664 649 $enough to hold all the signal in every channel $its size should have been decided at step 6C bchan 90;echan 95;outn 'test1_nh' 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 Haro29BCD_nh.UVLSF Noise level: 0.8155-3.4461 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. 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 %%%NOTE: No error messages C. If satisfied with the above than put the whole cube through this imaging recipe executed on 14dec10 DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29_nh'; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 2*0.858e-3 2*1.121e-3 2*1.731e-3 2*3.536e-3 niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 375 374 664 649 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 375 374 664 649 bchan 30;echan 35; $select one or more line free channels outn 'noiseNA_nh' 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.784 mJy Field 2(15 asec resolution): 1.125 mjy Field 3(45 asec resolution): 1.83 mJy Field 4(135 asec resolution): 3.731 mJy Test: DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; bchan 90;echan 95;outn 'test1na_nh' ngauss 4;wgauss 0,15,45,135; fgaus 2.5*0.784e-3 2.5*1.125e-3 2.5*1.83e-3 2.5*3.731e-3 $fgaus 2.5 sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 375 374 664 649 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 Making a natural weighted data cube: DEFAULT IMAGR sources 'haro29',''; docalib -1;doband -1;outseq 0; outname 'haro29NA_nh'; cellsize 1.5; imsize 1024; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 2.5*0.784e-3 2.5*1.125e-3 2.5*1.83e-3 2.5*3.731e-3 $fgaus 2.5 sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 375 374 664 649 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 09jan11 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: 2.069e-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.002069; levs 2, 5, 10, 20, 40, 80 $the lowest level is at 2.5sigma; $always between 2-2.5sigma); dotv 1; pixra -0.004138, 0.016552 $ pixrange=(-2sigma to +8sigma); docircle -1; blc 375 374 $ I used the same size as the window in IMAGR trc 664 649 getn *NA.CVL25 to get all interesting channels into PL files: for i=1 to 8;dotv -1; blc(3)= 70+(i-1)*9;trc(3)=69+i*9;go kntr;wait kntr; end to print all created PL files for i=1 to 15; plver =i; print i; go lwpla; wait lwpla; end %%%NOTE: 2*sigma worked well for the galaxy. #########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 B.2 Blank the cube at 2 sigma DEFAULT BLANK opcode 'SELC'; dparm 1, 0, 10000, 0.004138, 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 09jan11 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 09jan11 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 09jan11 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 09jan11 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). 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: This needs to be done with the Robust cube because the beam for the Natural Cube is already beyond the size of the convolving beam (12.42X7.92). DEFAULT CONVL bmaj 10; bmin 10; blc 0; trc 0; opcode ''; outna 'Haro29CVL10'; outclass ''; doblank 0; factor 0; outse 0; getn *.ICL001 DEFAULT BLANK opcode 'IN2C';outclass 'LMV'; getn *.CONVL get2n *.MASTER ON THE CONVOLVED CUBE 11.1 Transposing the cube executed on 09jan11 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 09jan11 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. Naming convention For each uv data set: DDO101_B1_SPLIT.FITS DDO101_B1_CVEL.FITS Combined uv data: DDO101_BCD_DBCON.FITS Minus continuum: DDO101_BCD_UVLSF.FITS Continuum only, uv data and map: DDO101_BCD_UVCONT.FITS DDO101_CONTINUUM_ICL.FITS Product of MSclean: DDO101_NA_ICL001.FITS DDO101_NA_ICL002.FITS DDO101_NA_ICL003.FITS DDO101_NA_ICL004.FITS DDO101_R_ICL001.FITS DDO101_R_ICL002.FITS DDO101_R_ICL003.FITS DDO101_R_ICL004.FITS Blanking: DDO101_NA_CVL_BL.FITS DDO101_NA_MASTER.FITS (frequency changed to velocity) KNTR_2sig.eps Final blanked cubes: DDO101_NA_LMV.FITS (frequency changed to velocity) DDO101_R_LMV.FITS (frequency changed to velocity) Moment maps: DDO101_NA_XMOM0.FITS DDO101_NA_XMOM1.FITS DDO101_NA_XMOM2.FITS DDO101_NA_XMOM3.FITS DDO101_NA_XMOMNC.FITS DDO101_R_XMOM0.FITS DDO101_R_XMOM1.FITS DDO101_R_XMOM2.FITS DDO101_R_XMOM3.FITS DDO101_R_XMOMNC.FITS Moment zero, PBC and REMAG corrections: DDO101_NA_X0_PBC.FITS DDO101_NA_X0_P_R.FITS DDO101_R_X0_PBC.FITS DDO101_R_X0_P_R.FITS Convolved data: Cube: DDO101_CVL10_ICL001.FITS Blanked: DDO101_CVL10_LMV.FITS Moment maps: DDO101_CVL10_XMOM0.FITS DDO101_CVL10_XMOM1.FITS DDO101_CVL10_XMOM2.FITS DDO101_CVL10_XMOM3.FITS DDO101_CVL10_XMOMNC.FITS Moment zero PBC and REMAG corrections: DDO101_CVL10_X0_PBC.FITS DDO101_CVL10_X0_P_R.FITS For the cases where all of the data are new data, we produce a Hanning-smoothed version and a non-smoothed version. The naming above should refer to the smoothed version and DDO101_NA_LMV_noHan.FITS is an example of the naming convention for the non-smoothed version.