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 Caroline Simpson, FIU, 04Aug11 Usernumber 759 12Aug 11: NOTE: First time through, dbconned and uvlsf'ed data, when imaged, was of poor quality: low level stripes were visble. The robust moment maps ended up with numerous blanked individual pixels ("pinholes") where there should have been emission. Running xmom with optype 'NBIV' got rid of them, but produced an insanely-valued velocity map. Elias says "The pinholes are introduced by XMOM and, at least in the case of DDO75, are a byproduct of the stripes/flaky data. Some intensities are off to such an extent that at several pixels the values in the velocity field (XMOM1 map) become "crazy". XMOM checks if the calculated velocity falls within the observed bandwidth and if it doesn't, it sets the offending pixel to magic value blanking. Now, you can suppress this by, in XMOM, specifying OPTYPE 'NBIV'. Caroline ran this test and now the pinholes have disappeared, but the velocity field looks horrendous (isn't XMOM clever?!?)." So the decision was made to edit the data to improve the quality. The D1 data set had bad interference which we let UVLSF try to remove; but it may have been masking other problems. I will investigate the individual data sets in more detail now. 16Aug11: I further edited the B2H and D1 data sets. The B2H.TRIM was SPFLGed and reSPLIT to apply the new flag table. I ran UVLSF on the D1.TRIM to remove most of the bad data, then used SPFLG on the D1.UVLSF. I then copied the FG table from that over to the original D1.TRIM and reSPLIT. The history was: D75_B2.SPLIT .1 ->CLIP->FG.1->CVEL-> UVDEC ->TRIM->SPFLG:FG.1->CLIP:FG.2->B2H.SPLIT.1 D75_D1.SPLIT .1 ->UVFIX;1-> UVFIX;2->TRIM->SPFLG ON D1.UVSLF;TACOP FG.4 TO TRIM.1->SPLIT.2 Then I re-dbconned and reimaged. There was essentially no difference from the un-edited data run. I further investigated the various data sets, looking for the cause of the low-level striping and resulting pinholes, but was unsuccessful. Elias thinks the problem is at a low level in the UV data, so very hard to find. So: the XMOM0 maps have pinholes. ------- DDO 75 (Sextans A) AB: TEST 17Jun1994: Archival 0.675 hrs B1a: AH 866 09May2004: Archival 1.91 hrs B1b: AH 866 10May2004: Archival 4.0 hrs B2: AO 215 21Nov2007: New 7.9 hrs C1: TEST 09May1992, 10May1992: Archival 2.3 hrs C2: AH 836 14May2004, 15May2004: Archival 4.4 hrs C3: AO 215 16Mar2008: New 2.4 hrs D1: TEST 13Jul1992: Archival 1.5 hrs x D2: AO 215 12Jul2008 --> unusable (phase cal problem; not calibrated) 0.6 hrs D3: AO 215 17Aug2008: New 1.5 hrs 0. Read in data DDO75_AB_UV_CALIB_LINCOP.fits ---> D75-AB.LINCOP.1 107 channels; 12.2kHz 1950 SextansA DDO75_B1a_UV_CALIB_LINCOP.FITS ---> D75_B1A.LINCOP.1 107 channels; 12.2kH 2000 SextansA DDO75_B1b_UV_CALIB_LINCOP.FITS ---> D75_B1B.LINCOP.1 107 channels; 12.2kH 2000 SextansA DDO75_B2_UV_CALIB_LINCOP.FITS ---> D75-B2.LINCOP.1 215 channels; 6.1kH 2000 SexA DDO75_C1_UV_CALIB_LINCOP.FITS ---> D75_C1.LINCOP.1 107 channels; 12.2kH 1950 SextansA DDO75_C2_UV_CALIB_LINCOP.FITS ---> D75_C2.LINCOP.1 107 channels; 12.2kH 2000 SextansA DDO75_C3_UV_CALIB_LINCOP.FITS ---> D75-C3.LINCOP.1 215 channels; 6.1kH 2000 SexA DDO75_D_UV_CALIB_LINCOP.FITS ---> D75_D1.LINCOP.1 107 channels; 12.2kH 1950 SextansA DDO75_D3_UV_CALIB_LINCOP.FITS ---> D75-D3.LINCOP.1 215 channels; 6.1kH 2000 SexA 1. Newly observed data x A.If in the calibration recipe one has taken out only 10 channels from the begining and end channels for the new data (5 channels from both sides for the old data)then a new UVCOP is necessary here for the new data which will take out another ten channels on both sides. executed on >> Not necessary for any data sets. DEFAULT UVCOP outcla 'LINCOP';bchan 10;echan 231; uvcopprm 0; uvcopprm(4) 1; getn *.LINCOP ----> *.LINCOP.2 ###Note: One should take the same even number of channels from both sides of the band and in such a way that one remains with a data set with an odd number of channels.THIS preserves the convention that (n+1)/2 is the central channel B. Splitting the data and applying the calibration and the flags. ###Note: Check values for GAINUSE and FLAGVER in case of non-standard reduction. executed on 04Aug11, 05Aug11 DEFAULT SPLIT Sources 'sextansa',''; 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 source 'sexa' getn 4 $ D75-B2.LINCOP.1 ----> D75_B2.SPLIT.1 source 'sexa' getn 7 $ D75-C3.LINCOP.1 ----> D75_C3.SPLIT.1 source 'sexa' getn 9 $ D75-D3.LINCOP.1 ----> D75_D3.SPLIT.1 >> Note: ran RENAME on file to get proper names, instead of SEXTANSA.SPLIT etc. C. Clipping 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!!! ^ default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance getn 13 $ D75_B2.SPLIT.1 >> Flag at 15 Jy getn 16 $ D75_C3.SPLIT.1 >> clip at 11 JY getn 18 $ D75_D3.SPLIT.1 >> Clip at 16 Jy executed on 05Aug11 DEFAULT CLIP aparm 0 aparm(1) 15 $ clip any parallel hand visibilities amplitude greater than 6Jy; $the clipping level should be set according to the previous UVPLT $or WIPER checks getn 13 $ D75_B2.SPLIT.1 aparm(1) 15 ----> FG;1 getn 16 $ D75_C3.SPLIT.1 aparm(1) 11 ----> FG;1 getn 18 $ D75_D3.SPLIT.1 aparm(1) 16 ----> FG;1 x D.1 Shifting the data without Hanning smoothing to a common central velocity ^ D.2 Shifting the data with Hanning smoothing This step is needed if data are to be combined with archive data observed with Hanning smoothing. D.2.1 executed on 05Aug11 DEFAULT CVEL outname 'd75_b2-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)=325e3; $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 13 $ D75_B2.SPLIT.1 >> There were 12 scans; so copious CVEL output. I have put it in a separate file: D75_B2.SPLIT_CVEL.MSG ----> D75_B2-NH.CVEL.1 getn 16 $ D75_C3.SPLIT.1 outna 'D75_C3-nh' >> output to D75_C3.SPLIT_CVEL.MSG ----> D75_C3-NH.CVEL.1 getn 18 $ D75_D3.SPLIT.1 outna 'D75_D3-nh' >> output to D75_D3.SPLIT_CVEL.MSG ----> D75_D3-NH.CVEL.1 ^D.2.2. Checks: ### Spectrum is shifted, but there is no change in the header frequency, so you need to run a few checks. ^D.2.2.1. Has CVEL done anything? executed on 06Aug11 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='sexa','' $ your galaxy stokes 'rr' dotv 1 tvinit grchan 1; getn 13 $ *D75_B2.SPLIT.1 flagver -1;grchan 2; getn 19 $ D75_B2-NH.CVEL.1 tvinit grchan 1; getn 16 $ D75_C3.SPLIT.1 grchan 2; getn 20 $ D75_C3-NH.CVEL.1 tvinit grchan 1; getn 18 $ D75_D3.SPLIT.1 grchan 2; getn 21 $ D75_D3-NH.CVEL.1 >> B2: ~ 5 channel shift? >> C3: ditto? >> D3: ditto? ###You should see the SPLIT and the CVEL do not overlap perfectly ^D.2.2.2. CVEL shifts the spectum so some channels, either at the beginning, 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. >> NOTE: I will be UVCOPPING off the end channels anyway; to match the 104 channels I will end up with for the archival data due to bad interference in the D1 data in channel 105. executed on 06Aug11 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='sexa','' $ your galaxy bchan 1;echan 20; $ choose the beginning 20 channels to make more obvious $ the channels with invalid information dotv 1 tvinit getn 19 $ D75_B2-NH.CVEL.1 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='sexa','' $ your galaxy bchan 195;echan 215; $ choose the last 20 channels to make more obvious $ the channels with invalid information dotv 1 tvinit getn 19 $ D75_B2-NH.CVEL.1 >> D75_B2-NH.CVEL.1: >> The number of beginning channels with invalid information: 0 >> The number of end channels with invalid information: 4 >> (211 last valid channel) tvinit tget possm bchan 1;echan 20 getn 20 $ D75_C3-NH.CVEL.1 tvinit bchan 195; echan 215 >> D75_C3-NH.CVEL.1: >> The number of beginning channels with invalid information: 0 >> The number of end channels with invalid information: 4 >> (211 last valid channel) tvinit tget possm bchan 1;echan 20 getn 21 $ D75_D3-NH.CVEL.1 tvinit bchan 195; echan 215 >> D75_D3-NH.CVEL.1: >> The number of beginning channels with invalid information: 0 >> The number of end channels with invalid information: 4 >> (211 last valid channel) ###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. ^D.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 06Aug11 >> Reference channel is 108/215, so I want the even channels DEFAULT UVDEC chinc 2 $to take every second channel outn 'd75_B2H';outcl 'UVDEC' bchan 2;echan 0; getn 19 $ D75_B2-NH.CVEL.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B2-NH.CVEL.1 ----> D75_B2H.UVDEC.1 DEFAULT UVDEC chinc 2 $to take every second channel outn 'd75_C3H';outcl 'UVDEC' bchan 2;echan 0; getn 20 $ D75_C3-NH.CVEL.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C3-NH.CVEL.1 ----> D75_C3H.UVDEC.1 DEFAULT UVDEC chinc 2 $to take every second channel outn 'd75_D3H';outcl 'UVDEC' bchan 2;echan 0; getn 21 $ D75_D3-NH.CVEL.1 >>AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D3-NH.CVEL.1 ----> D75_D3H.UVDEC.1 ## In UVDEC is necessary to ensure that among the channels you are taking is the reference pixel.If before CVEL you 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). ^D.2.3.2 UVDEC has been found not to update the header properly (This should have been fixed by Eric in the mean time). 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. >> D75_B2H.UVDEC.1 inp gethead getn 22 $ D75_B2H.UVDEC.1 keyword 'ALTRPIX' gethead inp puthead keyval 54,0 inp puthead puthead imh $ to check if it worked >> Yes, it did. >> D75_C3H.UVDEC.1 inp gethead getn 23 $ D75_C3H.UVDEC.1 keyword 'ALTRPIX' gethead inp puthead keyval 54,0 inp puthead puthead imh $ to check if it worked >> Yes, it did. >> D75_D3H.UVDEC.1 inp gethead getn 24 $ D75_D3H.UVDEC.1 keyword 'ALTRPIX' gethead inp puthead keyval 54,0 inp puthead puthead imh $ to check if it worked >> Yes, it did. ######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. >> All headers are fine; no indication of phase shifting. x inp gethead x getn 22 $ *.UVDEC x keyword 'YSHIFT' x gethead x inp puthead x keyval 0 x inp puthead x puthead x imh $ to check if it worked 2. Archival data ^A. Splitting the data and applying the calibration and the flags. executed on DEFAULT SPLIT Sources 'ddo133',''; 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 source 'sextansa' getn 1 $ D75-AB.LINCOP.1 ----> D75_AB.SPLIT.1 source 'sextansa' getn 2 $ D75_B1A.LINCOP.1 ----> D75_B1A.SPLIT.1 source 'sextansa' getn 3 $ D75_B1B.LINCOP.1 ----> D75_B1B.SPLIT.1 source 'sextansa' getn 5 $ D75_C1.LINCOP.1 ----> D75_C1.SPLIT.1 source 'sextansa' getn 6 $ D75_C2.LINCOP.1 ----> D75_C2.SPLIT.1 source 'sextansa' getn 8 $ D75_D1.LINCOP.1 ----> D75_D1.SPLIT.1 ^B. Clipping 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!!! ^ default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance getn 10 $ D75_AB.SPLIT.1 >> looks fine; nothing above 3 Jy getn 11 $ D75_B1A.SPLIT.1 >> looks fine; nothing above 6 Jy getn 12 $ D75_B1B.SPLIT.1 >> a few points > 7.5 Jy; will clip getn 14 $ D75_C1.SPLIT.1 >> clip at 3.5 Jy getn 15 $ D75_C2.SPLIT.1 >> This data set has bad interference in Channel 105; recommendation is to UVCOP to channel 104. This will need to be done for all data sets. Sigh. CALIB notes and WIPER without channel 105 show some high stuff on short bl (up to 17 Jy); probably solar? getn 17 $ D75_D1.SPLIT.1 >> lots of high stuff (up to 25 Jy) on short bl (< 1 Jy). Calib notes say "Elias recommends "DBCON, UVLSF, and IMAGR and see what the damage is, and check on a line free channel what the shortest baseline is that you can still tolerate. Often UVLSF does the trick. You can then do the UVCOP trick, run WIPER (and if required CLIP), and then go on with the recipe as usual." The UVCOP trick is to use UVCOP to copy over everything except the contaminated short baselines by setting a UVRANGE. ***WILL NOT CLIP AT THIS POINT *** executed on 06Aug11 ^ DEFAULT CLIP aparm 0 aparm(1) 6 $ $ clip any parallel hand visibilities amplitude greater than 6Jy; getn 12 $ D75_B1B.SPLIT.1 aparm(1) 7.5 ----> FG;1 getn 14 $ D75_C1.SPLIT.1 aparm(1) 3.5 ----> FG;1 getn 15 $ D75_C2.SPLIT.1 aparm(1) 6.0 ----> FG;1 ^C. Applying the flag table created in CLIP ###We need to apply the flag table here as we do not run CVEL on archival data. executed on ^DEFAULT SPLIT Sources 'sextansa', ''; 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 1; Doband -1; Bpver 1; Smooth 0; Douvcomp -1; Aparm 0; Nchav 1; Chinc 1; Ichansel 0; Baddisk 0 getn 12 $ D75_B1B.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B1B.SPLIT.1 ----> D75_B1B.SPLIT.2 getn 14 $ D75_C1.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C1.SPLIT.1 ----> D75_C1.SPLIT.2 getn 15 $ D75_C2.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C2.SPLIT.1 ----> D75_C2.SPLIT.2 ^ D. If the data was observed in B1950 coordinates then precess the data from B1950 to B2000 coordinates. >> The AB, C1, and D1 are in B1950 executed on 06Aug11 To correct the u,v,w's to the original (J2000) position: >> D75_AB.SPLIT.1 $ no clip done so not resplit DEFAULT UVFIX getn 10 $ D75_AB.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_AB.SPLIT.1 ----> D75_AB.UVFIX.1 To shift the phases and the u,v,w's to the new position: DEFAULT UVFIX getn 28 $ D75_AB.UVFIX.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_AB.UVFIX.1 ----> D75_AB.UVFIX.2 >> D75_C1.SPLIT.2 $ clipped, so resplit DEFAULT UVFIX getn 26 $ D75_C1.SPLIT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C1.SPLIT.2 ----> D75_C1.UVFIX.1 DEFAULT UVFIX getn 30 $ D75_C1.UVFIX.1 >>AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C1.UVFIX.1 ----> D75_C1.UVFIX.2 >> D75_D1.SPLIT.1 $ o clip done so not resplit DEFAULT UVFIX getn 17 $ D75_D1.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.SPLIT.1 ----> D75_D1.UVFIX.1 DEFAULT UVFIX getn 32 $ D75_C1.UVFIX.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.UVFIX.1 ----> D75_D1.UVFIX.2 ^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. >> Issues: New (ANGST) data (B2, C3, C3) had 215 channels; smoothed it ---> last 4 channels in each data set (212, 213, 214, 215) now invalid, but then removed odd numbered channels, so now 212, 214 are only invalid channels; and are renumbered as 106, 107. Also, archival data C2 has bad channel 105 (of 107). So I need to trim all data sets so that channel 104 is last channel. This will also clip out the invalid channels for the ANGST data; convenient! >> Data sets to be trimmed (all): 29 D75_AB.UVFIX.2 11 D75_B1A.SPLIT.1 25 D75_B1B.SPLIT.2 22 D75_B2H.UVDEC.1 31 D75_C1.UVFIX.2 27 D75_C2.SPLIT.2 23 D75_C3H.UVDEC.1 33 D75_D1.UVFIX.2 24 D75_D3H.UVDEC.1 executed on 06Aug11 DEFAULT UVCOP outcla 'TRIM'; bchan 1;echan 104; $ the decision is taken comparing all imheaders uvcopprm 0; uvcopprm(4) 1; getn 29 $ D75_AB.UVFIX.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_AB.UVFIX.2 ----> D75_AB.TRIM.1 getn 11 $ D75_B1A.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B1A.SPLIT.1 ----> D75_B1A.TRIM.1 >> PRTMSG: D75_COMBINE_PRTMSG1; clrmsg getn 25 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B1B.SPLIT.2 ---> D75_B1B.TRIM.1 getn 22 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B2H.UVDEC.1 ----> D75_B2H.TRIM.1 getn 31 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C1.UVFIX.2 ----> D75_C1.TRIM.1 getn 27 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C2.SPLIT.2 ----> D75_C2.TRIM.1 getn 23 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C3H.UVDEC.1 ----> D75_C3H.TRIM.1 getn 33 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.UVFIX.2 ----> D75_D1.TRIM.1 getn 24 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D3H.UVDEC.1 ----> D75_D3H.TRIM.1 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 12Aug11 DEVIATION FROM RECIPE HERE to find Bad Data. I'm assuming it's in D1. I will run UVLSF on the D1 data. DEFAULT UVLSF Shift 0 0; Flux 0; Dooutput -1; Ichansel 1,30,1,0,77,104,1,0; Order 1; infil '' getn 41 $ D1.TRIM >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.TRIM.1 >> ----> D75_D1.UVLSF.1 default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance getn 130 $ D75_D1.UVLSF.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.UVLSF.1 >> screen shot: d75_d1_uvslf_wiper.jpg >> highish points from bl 4-5, some with 3-4. Up to 8 Jy. I noted, >> during calibration, that 4-5 looked odd in SPFLG, but left it >> in. This is NOT the cause of the 8kl spike I saw in the DBCONned >> WIPER. This is from my D calib notes: >> stokes RR and LL: Some baselines quite bad; mostly in the first >> scan. Eventually loaded all antennas with all baselines and poked >> around; what I'm seeing is probably solar interference after all -- >> it seems to be from the short baselines. An example is here: >> -----> d75_d_baseline4-5_spflg.jpg >> Hmm. Try some line-free channels default WIPER imsize 512 512 bchan 5; echan 25 bparm(2) 1 $ amp. vs. uv-distance getn 130 $ D75_D1.UVLSF.1 >> screen shot: d75_d1_uvlsf_linefree_wiper.jpg >> Looks much better - can still see 4-5, but at lower level. Great. :(. >> Let's do some wipers on the .TRIM datasets... default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance >> D75_AB.TRIM.1: Fine. Max 2.5 Jy or so >> D75_B1A.TRIM.1: Fine. Max 5.7 Jy >> D75_B1B.TRIM.1: Fine. Max 7.4 Jy >> D75_B2H.TRIM.1: DING DING DING! Found the bad baseline. 6-13, >> as we know. Use SPFLG? >> D75_C1.TRIM.1. Fine. Max 3.5 Jy >> D75_C2.TRIM.1. Fine. Some short bl stuff; max ~6 Jy. >> D75_C3H.TRIM.1. Fine. max 6.7 Jy >> D75_D3H.TRIM.1. Fine. Shortest bl (12-18) highish. Max 14.5 Jy. default SPFLG antenna 6 0; baseline 13 0 dparm(6) 10 getn 37 $ D75_B2H.TRIM.1 >> A few bad times in both stokes; flagged. default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance getn 37 $ D75_B2H.TRIM.1 >> Better. Clip at 7.5 now. Back to D1: SPFLG on 4-5: default spflg antenna 4 0; baseline 5 0 dparm(6) 60 getn 130 $ D75_D1.UVLSF.1 >> two scans; first scan is very bad; channel dependent. >> screen shot: d75_d1_uvlsf_bl4-5_wiper.jpg >> FLAG AREA: first scan, both stokes. default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance getn 130 $ D75_D1.UVLSF. >> Better. Still some baddish baselines default SPFLG antenna 17 0; baseline 23 0 dparm(6) 60 getn 130 $ D75_D1.UVLSF.1 >> 17-23: first scan bad, just like 4-5; rr mostly; Flagged RR, LL first scan. >> 3-4: ditto. >> 2-8: RR only; just first few integrations in first scan bad; >> flagged. default WIPER imsize 512 512 bparm(2) 1 $ amp. vs. uv-distance getn 130 $ D75_D1.UVLSF. >> Much better. Fine now. >> screen shot: d75_d1_uvslf_final_edit_wiper.jpg >> Now, need to apply new flag tables to edited datasets. >> B2H.TRIM ---> clip at 7.5 Jy and resplit default CLIP aparm 0 aparm(1) 7.5 getn 37 $ D75_B2H.TRIM.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B2H.TRIM.1 DEFAULT SPLIT Sources '', ''; 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 getn 37 $ D75_B2H.TRIM.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B2H.TRIM.1 >> ----> D75_B2H.SPLIT.1 >> Copy the FG;4 table to the .TRIM data and resplit. default TACOP inext 'fg' invers 4 outvers 0 getn 130 $ D75_D1.UVLSF.1 geto 41 $ D75_D1.TRIM.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.UVLSF.1 >> AIPS 1: Got(O) disk= 1 user= 759 type=UV D75_D1.TRIM.1 >> Copied FG file from vol/cno/vers 1 130 4 to 1 41 1 >> Resplit to apply FG table DEFAULT SPLIT Sources '', ''; 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 1; Doband -1; Bpver 1; Smooth 0; Douvcomp -1; Aparm 0; Nchav 1; Chinc 1; Ichansel 0; Baddisk 0 getn 41 $ D75_D1.TRIM.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.TRIM.1 >> ----> D75_D1.SPLIT.2 >> PRTMSG --> D75_COMBINE_PRTMSG_12AUG11; clrmsg %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ^ B. Gluing. ### Unfortunately DBCON is glueing only two data sets at a time. >> 12Aug11: combining TRIM datasets for all except B2H and D1, which were further edited and resplit after trimming. >> Issues: different pointing centers: D75_AB.TRIM.1 10 11 01.287 -04 40 48.411 A D75_B1A.TRIM.1 10 10 50.107 -04 39 49.960 B D75_B1B.TRIM.1 10 10 50.107 -04 39 49.960 B D75_B2H.SPLIT.1 10 11 00.800 -04 41 34.000 C D75_C1.TRIM.1 10 11 01.287 -04 40 48.411 A D75_C2.TRIM.1 10 10 50.107 -04 39 49.960 B D75_C3H.TRIM.1 10 11 00.800 -04 41 34.000 C D75_D1.SPLIT.2 10 11 01.287 -04 40 48.411 A D75_D3H.TRIM.1 10 11 00.800 -04 41 34.000 C >> so, off by 2.75' or so. Hope DBCON can handle this... A = B1950 data (precessed to J2000) B = J2000 data C = ANGST data >> Will DBCON the data with the pointing centers together first; that way if DBCON can't handle it, I will UVFIX to do the shift manually on the data set that needs it, but others will be ok. . executed on 12Aug11 DEFAULT DBCON Reweight 0 0; Outname 'Dummy'; Dopos 1,0; Doarray 0; Fqtol 0 >> A set: 10 11 01.287 -04 40 48.411 getn 34 $ D75_AB.TRIM.1 get2n 38 $ D75_C1.TRIM.1 outna 'dummy_A1' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_AB.TRIM.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV D75_C1.TRIM.1 ----> DUMMY_A1.DBCON.1 getn 83 $ D75_D1.SPLIT.2 get2n 43 $ DUMMY_A1.DBCON.1 outna 'dummy_a' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D1.SPLIT.2 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV DUMMY_A1.DBCON.1 ----> DUMMY_A.DBCON.1 >> B set: 10 10 50.107 -04 39 49.960 getn 35 $ D75_B1A.TRIM.1 get2n 36 $ D75_B1B.TRIM.1 outna 'dummy_b1' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B1A.TRIM.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV D75_B1B.TRIM.1 ----> DUMMY_B1.DBCON.1 getn 39 $ D75_C2.TRIM.1 get2n 45 $ DUMMY_B1.DBCON.1 outna 'dummy_b' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_C2.TRIM.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV DUMMY_B1.DBCON.1 ----> DUMMY_B.DBCON.1 >> C set: 10 11 00.800 -04 41 34.000 getn 82 $ D75_B2H.SPLIT.1 get2n 40 $ D75_C3H.TRIM.1 outna 'dummy_c1' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_B2H.SPLIT.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV D75_C3H.TRIM.1 ----> DUMMY_C1.DBCON.1 getn 42 $ D75_D3H.TRIM.1 get2n 47 $ DUMMY_C1.DBCON.1 outna 'dummy_c' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_D3H.TRIM.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV DUMMY_C1.DBCON.1 ----> DUMMY_C.DBCON.1 >> Combining... LT: 10:10:59.2 -04:41:56 ---> closest to "C" dataset. Use this as preferred pointing position. "A" and "C" datasets closest in position; combine those first >> "A" and "C" dopos 1,0 getn 48 $ get2n 44 $ outna 'dummy_AC' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV DUMMY_C.DBCON.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV DUMMY_A.DBCON.1 galaxy> DBCON1: Task DBCON (release of 31DEC08) begins galaxy> DBCON1: RA does not match, will shift second galaxy> DBCON1: DEC does not match, will shift second ----> DUMMY_AC.DBCON.1 >> AC and "B" dopos 1,0 getn 49 $ DUMMY_AC.DBCON.1 get2n 46 $ DUMMY_B.DBCON.1 outna 'd75_bcd' >> AIPS 1: Got(1) disk= 1 user= 759 type=UV DUMMY_AC.DBCON.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=UV DUMMY_B.DBCON.1 galaxy> DBCON1: RA does not match, will shift second galaxy> DBCON1: DEC does not match, will shift second ----> D75_BCD.DBCON.2 >> It worked!! :) RA: 10 11 00.800 DEC: -04 41 34.000 ^C. Checks: executed on 12Aug11 DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'd75.dirt'; cellsize 1.5; imsize 1024; niter 1000; uvwtfn 'na'; dotv -1; calcode '-cal'; getn 84 $ D75_BCD.DBCON.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.DBCON.2 galaxy> IMAGR1: IMACPY: Only 1680933 samples of 1683100 fell on UV grid galaxy> IMAGR1: **** WARNING data discarded outside usable part of UV plane **** galaxy> IMAGR1: **** Actual Umax 5.2530E+04 exceeds limit 4.8034E+04 **** galaxy> IMAGR1: **** Use cellsize < 1.37164 not 1.50000 to get all data **** galaxy> IMAGR1: **** using a U guard band of 0.300 of a radius **** galaxy> IMAGR1: **** WARNING data included out of inner portion of UV plane **** galaxy> IMAGR1: **** Watch for high-frequency & other poor cleaning effects **** >> Can ignore this. Use 1.5" cells. ##Also inspect the data with TVMOVIE and find which are the Line channels >> Sadly, this seems to be identical to pre-edited version. :( >> Perhaps this is because all that interference is still in the >> D1 data... >> The line channels are: 34 - 75ish ^ 6. Continuum subtraction ^A. Subtracting the continuum: executed on 12Aug11 ###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,30,1,0,80,104,1,0; Order 1; infil '' getn 84 $ .DBCON;2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.DBCON.2 >> ---->D75_BCD.UVLSF.2 >> Because of short baseline contamination in D1 dataset; want to check it here. Let's try wiper on the UVLSF;2 data OMG. BL 6-18 still there! Wait... it was 6-13 before? Doing line-free channels: 1-25: looks fine. >> running wipers, setting subarrays (which distinguish between the data sets). Subarray 2 has bad baseline; is a B dataset. Turns out to be the B2 dataset. >> SPFLG... default SPFLG subarray 2 antenna 6 0; baseline 18 0 dparm(6) 10 getn 85 $ D75_BCD.UVLSF.2 >> Flagged several areas/times for both stokes >> WIPER on the UVLSF: subarray 2: looks fine now. Phew. I should have edited the DBCON data (I want to redo the continuum subtraction) instead of the UVLSF; so I will copy the FG table from the UVLSF over to the DBCON, then split the DBCON to apply the FG table. default TACOP inext 'fg' invers 0; outvers 0 getn 85 $ D75_BCD.UVLSF.2 geto 84 $ D75_BCD.DBCON.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVLSF.2 >> AIPS 1: Got(O) disk= 1 user= 759 type=UV D75_BCD.DBCON.2 >> Copied FG file from vol/cno/vers 1 85 1 to 1 84 1 DEFAULT SPLIT Sources '', ''; 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 1; Doband -1; Bpver 1; Smooth 0; Douvcomp -1; Aparm 0; Nchav 1; Chinc 1; Ichansel 0; Baddisk 0 getn 84 $ D75_BCD.DBCON.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.DBCON.2 >> ----> D75_BCD.SPLIT.1 >> redo continuum subtraction DEFAULT UVLSF Shift 0 0; Flux 0; Dooutput -1; Ichansel 1,30,1,0,80,104,1,0; Order 1; infil '' getn 91 $ D75_BCD.SPLIT.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.SPLIT.1 >> ----> D75_BCD.UVLSF.3 >> rename D75_BCD.SPLIT.1 ----> D75_BCD.DBCON.3 >> AIPS 1: Rename D75_BCD .SPLIT . 1 (UV) on disk 1 cno 91 >> AIPS 1: To D75_BCD .DBCON . 3 (UV) on disk 1 cno 91 ^ B. Creating the continuum map: executed on 13Aug11 ^ DEFAULT AVSPC avoption ''; flagver -1; bif 0;eif 0; channel 0; outcl 'UVCONT' Ichansel 1,30,1,0,80,104,1,0; $the line free channels getn 91 $ *.DBCON.3 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.DBCON.3 >> ----> D75_BCD.UVCONT.2 >> The continuum (UVCONT) will still contain the D1 bad data. I think. Let's try UVPLT on the UVCONT. default UVPLT dotv -1 $ PLVER 1 getn 93 $ D75_BCD.UVCONT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVCONT.2 >> print to file default LWPLA outfile 'D75:D75_uvcont2_uvplt.ps getn 93 $ D75_BCD.UVCONT.2 >> Wow. Short baselines up to ~ 25 Jy; a few longer baselines (4-5 kl) up to 3 Jy. Try uvplt with only D1 data. Not sure which subarray it is though... will try them, one at a time... tget UVPLT dotv 1 subarray 1 >> short bl up to 9 subarray 2: few scattered points on short bl to 2.5 Jy. subarray 3: fine subarray 4: DING DING DING! This is the bad one. Look at others anyway. subarray 5: wow. Mjy signals only. subarray 6: ditto subarray 7: short bl up to 6 Jy subarray 8: max to 1.0 Jy subarray 9: few scattered points on short bl to 2.0 Jy. >> To remove bad D3 data from UVCONT: UVFLG it default UVFLG $ ---> FG;1 subarray 4 opcode 'flag' reason 'bad D1 data' $ Orig though subarray 4 was D1; later found it was D3 but flag says D1 getn 93 $ D75_BCD.UVCONT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVCONT.2 >> Wrote 1 flags to flag table version 1 >> Check: default UVPLT subarray 0 $ all in dataset dotv 1 getn 93 $ D75_BCD.UVCONT.2 >> Yes; it worked. No D3 data. NOTE: THERE IS A FG table I have not applied via split. ###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 93 $ *.UVCONT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVCONT.2 ----> CONTINUUM.ICL001.3 Rms noise is: 0.2536 mJy/B >> pretty ugly. Worried about pos/neg beam pattern around bright continuum source; result of poor pointing center shifting by DBCON? (tests on unshifted data showed that this is NOT a shift issue). %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% DEPARTURE FROM RECIPE: >> Try imaging unshifted dataset: "B" data: contains B1a, B1b, C3: DEFAULT AVSPC avoption ''; flagver -1; bif 0;eif 0; channel 0; outcl 'UVCONT' Ichansel 1,30,1,0,80,104,1,0; $the line free channels getn 46 $ DUMMY_B.DBCON.1 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV DUMMY_B.DBCON.1 >> ----> DUMMY_B.UVCONT.1 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 94 $ *.UVCONT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV DUMMY_B.UVCONT.1 >> ----> CONTINUUM.ICL001.4 >> AIPS 1: Rename CONTINUUM .ICL001. 4 (MA) on disk 1 cno 99 >> AIPS 1: To DUMMY_B_CONT.ICL001. 1 (MA) on disk 1 cno 99 >> AIPS 1: Rename CONTINUUM .IBM001. 2 (MA) on disk 1 cno 98 >> AIPS 1: To DUMMY_B_CONT.IBM001. 1 (MA) on disk 1 cno 98 >> Looks very similar: same weird beam pattern. So I will assume that the BCD DBCONned data with the different pointing centers shifted just fine. These data are just ... ugly. %%%%%%%%%%%%%%%%%%%%%%%%%%%% DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'continuum'; cellsize 1; imsize 2048; $in a complex field one might need 2048 niter 50000; $ had to raise from 10000; hit limit before 2sigma uvwtfn ''; dotv -1; calcode '';robust 0.5; flux 0.507e-3 $it should be set to a 2 sigma level getn 90 $ *.UVCONT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVCONT.2 >> ----> CONTINUUM.ICL001.4 (IMB.2) ^ C. Checks executed on 6Aug11 >> 13Aug 11 I did this first time through (6Aug11; before editing out bad baselines) on the entire cube. From that, I know I need a 2048 image with a 1024 clean box. However, I will run this on a set of line-free channels using the newly edited UVLSF data just to find the noise level. Making a dirty cube of the continuum subtracted data >> there is no 'b array dirty cube' -- I have B1a, B1a, B2... I will use the rms from B1b image -- has same velocity resolution as DBCON, and was 4 hrs on-source; B1a was 2... use 1.7 mJy/B >> 13Aug11: ^ DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'd75'; cellsize 1.5; imsize 2048; niter 1e6; uvwtfn ''; dotv -1; calcode '-cal';imagrprm(10) 1 bchan 5; echan 25;robust 0.5; flux 0.0051 $set this to 3 times the sigma of the B array dirty cube getn 89 $ *.UVLSF.3 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVLSF.3 >> ----> D75.ICL001.2 galaxy> IMAGR1: IMACPY: Only 1680929 samples of 1683084 fell on UV grid galaxy> IMAGR1: **** WARNING data discarded outside usable part of UV plane **** galaxy> IMAGR1: **** Actual Umax 5.2531E+04 exceeds limit 4.8081E+04 **** galaxy> IMAGR1: **** Use cellsize < 1.37294 not 1.50000 to get all data **** galaxy> IMAGR1: **** using a U guard band of 0.300 of a radius **** galaxy> IMAGR1: **** WARNING data included out of inner portion of UV plane **** galaxy> IMAGR1: **** Watch for high-frequency & other poor cleaning effects **** >> Not to worry. Ok. ###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. >> 13Aug11: previous reductions showed that I need a 1024 clean box. >> getn 100 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75.ICL001.2 >blc 10 10 0 >trc 2038 2038 0 >imstat >> rms= 5.1586E-04 JY/BEAM ^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 '',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 2048; 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 512 512 1536 1536 bchan 15;echan 20; $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 getn 89 $ *.UVLSF.3 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVLSF.3 galaxy> IMAGR1: IMACPY: Only 1680921 samples of 1683078 fell on UV grid galaxy> IMAGR1: **** WARNING data discarded outside usable part of UV plane **** galaxy> IMAGR1: **** Actual Umax 5.2536E+04 exceeds limit 4.8081E+04 **** galaxy> IMAGR1: **** Use cellsize < 1.37282 not 1.50000 to get all data **** galaxy> IMAGR1: **** using a U guard band of 0.300 of a radius **** galaxy> IMAGR1: **** WARNING data included out of inner portion of UV plane **** galaxy> IMAGR1: **** Watch for high-frequency & other poor cleaning effects **** galaxy> IMAGR1: Create NOISE .IBM001. 1 (MA) on disk 1 cno 101 galaxy> IMAGR1: Create NOISE .IBM002. 1 (MA) on disk 1 cno 102 galaxy> IMAGR1: Create NOISE .IBM003. 1 (MA) on disk 1 cno 103 galaxy> IMAGR1: Create NOISE .IBM004. 1 (MA) on disk 1 cno 104 galaxy> IMAGR1: Create NOISE .IIM001. 1 (MA) on disk 1 cno 105 galaxy> IMAGR1: Create NOISE .IIM002. 1 (MA) on disk 1 cno 106 galaxy> IMAGR1: Create NOISE .IIM003. 1 (MA) on disk 1 cno 107 galaxy> IMAGR1: Create NOISE .IIM004. 1 (MA) on disk 1 cno 108 The rms noise measured in a line free channel is: Field 1(5asec resolution): 0.51 mJy Field 2(15 asec resolution): 0.64 mjy Field 3(45 asec resolution): 1.02 mJy Field 4(135 asec resolution): 2.03 mJy >> PRTMSG: D75_COMBINE_PRTMSG_13AUG11_1; clrmsg >> 10Aug11: NOTE: on 8Aug11, I proceeded with the recipe through the >> kntr step, using a 1024 imsize and a CLBOX of 281.00 311.00 755.00 >> 760.00. However, the images looked noisy and stripy with areas of >> possible poor cleaning/extended emission/noise? This became very >> apparent in the 25" convolved cube. I reran the NA imagr at that >> point with a 2048 imsize and a CLBOX of the inner 1024. I convolved >> it and ran kntr and compared with the kntr of the 1024 NA cube. The >> larger imsize was definitely less noisy and less stripy, even though >> the rms level was similar (0.0096 1024, 0.00093 2048). So I am >> redoing the Robust and NA cubes at 2048. We only need the inner 1024 >> really (the emission fits in that, but just barely), but we need to >> clean a 1024 box so... 2048 it is. >> 13Aug11: the reduction from 10Aug11 turned out to result in poor enough image data that XMOM produced useless maps: pinholes in the MOM0 due to bad velocity values. Went back and re-edited data; this is the next run through. B. Tuning our multi-resolution clean parameters executed on 8Aug11 (1024 imsize) reexectued 10Aug11 (2048 imsize) re-reexecuted 13Aug11 (newly edited data) DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 2048; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 2*0.51e-3 2*0.64e-3 2*1.02e-3 2*2.03e-3 $ fgaus 2sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 512 512 1536 1536 bchan 50;echan 55;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 89 $ *.UVLSF.3 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVLSF.3 1 6 13-AUG-2011 14:08:36 IMAGR IMACPY: Only 1680915 samples of 1683076 fell on UV grid 1 6 13-AUG-2011 14:08:36 IMAGR **** WARNING data discarded outside usable part of UV plane **** 1 6 13-AUG-2011 14:08:36 IMAGR **** Actual Umax 5.2552E+04 exceeds limit 4.8081E+04 **** 1 6 13-AUG-2011 14:08:36 IMAGR **** Use cellsize < 1.37240 not 1.50000 to get all data **** 1 6 13-AUG-2011 14:08:36 IMAGR **** using a U guard band of 0.300 of a radius **** 1 6 13-AUG-2011 14:08:36 IMAGR **** WARNING data included out of inner portion of UV plane **** 1 6 13-AUG-2011 14:08:36 IMAGR **** Watch for high-frequency & other poor cleaning effects **** 1 2 13-AUG-2011 14:08:38 IMAGR Create TEST1 .IBM001. 1 (MA) on disk 1 cno 109 1 2 13-AUG-2011 14:08:39 IMAGR Create TEST1 .IBM002. 1 (MA) on disk 1 cno 110 1 2 13-AUG-2011 14:08:40 IMAGR Create TEST1 .IBM003. 1 (MA) on disk 1 cno 111 1 2 13-AUG-2011 14:08:42 IMAGR Create TEST1 .IBM004. 1 (MA) on disk 1 cno 112 1 2 13-AUG-2011 14:08:43 IMAGR Create TEST1 .ICL001. 1 (MA) on disk 1 cno 113 1 2 13-AUG-2011 14:08:44 IMAGR Create TEST1 .ICL002. 1 (MA) on disk 1 cno 114 1 2 13-AUG-2011 14:08:45 IMAGR Create TEST1 .ICL003. 1 (MA) on disk 1 cno 115 1 2 13-AUG-2011 14:08:46 IMAGR Create TEST1 .ICL004. 1 (MA) on disk 1 cno 116 ########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 outprint 'd75:d75_imagr7b_13Aug11' $ the name of the file to write to docrt -1 prtmsg $ D75_IMAGR7B_13Aug11 clrmsg $ (IMAGR only) >> no bad messages Noise level: 0.48 mJy/B #### Look at the maps, see if there are any indicatives of calibration problems or imaging problems >> 13 Aug11: first time through with 1024 imsize, cube looked overcleaned (pos/neg beam-sized holes; ran a 2.5 sig and 3 sig clean; decided on 3 sigma clean. 2048 cube with 2 sigma clean looks overcleaned as well; will go straight to full cube clean with 3 sigma instead of rerunning tests. >> 13Aug11: I *think* the data looks less stripey than previous runs. >> tvmovie: TEST1.ICL001.1: Looks overcleaned to me: negative beam-sized holes... TEST1.ICL002.1: ok. Very very faint galaxy emission pattern visible TEST1.ICL003.1: ok. Very very faint galaxy emission pattern visible TEST1.ICL004.1: ok. Nothing much visible. ^ C. If satisfied with the above than put the whole cube through this imaging recipe executed on 8Aug11 reexecuted 10Aug11 re-reexecuted 13Aug11: 3 sigma DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'DDO75_R'; cellsize 1.5; imsize 2048; uvwtfn ''; dotv -1; calcode '-cal'; robust 0.5; ngauss 4;wgauss 0,15,45,135; fgaus 3*0.51e-3, 3*0.64e-3, 3*1.02e-3, 3*2.03e-3 $ 3 sigma niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 512 512 1536 1536 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 89 $ *.UVLSF >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVLSF.3 1 6 13-AUG-2011 14:38:50 IMAGR IMACPY: Only 1680929 samples of 1683084 fell on UV grid 1 6 13-AUG-2011 14:38:50 IMAGR **** WARNING data discarded outside usable part of UV plane **** 1 6 13-AUG-2011 14:38:50 IMAGR **** Actual Umax 5.2530E+04 exceeds limit 4.8081E+04 **** 1 6 13-AUG-2011 14:38:50 IMAGR **** Use cellsize < 1.37298 not 1.50000 to get all data **** 1 6 13-AUG-2011 14:38:50 IMAGR **** using a U guard band of 0.300 of a radius **** 1 6 13-AUG-2011 14:38:50 IMAGR **** WARNING data included out of inner portion of UV plane **** 1 6 13-AUG-2011 14:38:50 IMAGR **** Watch for high-frequency & other poor cleaning effects **** >> as usual. No worries. 1 2 13-AUG-2011 14:39:09 IMAGR Create DDO75_R .IBM001. 1 (MA) on disk 1 cno 117 1 2 13-AUG-2011 14:39:30 IMAGR Create DDO75_R .IBM002. 1 (MA) on disk 1 cno 118 1 2 13-AUG-2011 14:39:50 IMAGR Create DDO75_R .IBM003. 1 (MA) on disk 1 cno 119 1 2 13-AUG-2011 14:40:11 IMAGR Create DDO75_R .IBM004. 1 (MA) on disk 1 cno 120 1 2 13-AUG-2011 14:40:32 IMAGR Create DDO75_R .ICL001. 2 (MA) on disk 1 cno 121 1 2 13-AUG-2011 14:40:52 IMAGR Create DDO75_R .ICL002. 2 (MA) on disk 1 cno 122 1 2 13-AUG-2011 14:41:10 IMAGR Create DDO75_R .ICL003. 2 (MA) on disk 1 cno 123 1 2 13-AUG-2011 14:41:32 IMAGR Create DDO75_R .ICL004. 2 (MA) on disk 1 cno 124 default prtmsg prtask 'IMAGR' $ the task for which you want the aips messages outprint 'd75:d75_imagr7c_13Aug11' $ the name of the file to write to docrt -1 prtmsg $ D75_IMAGR7c_13Aug11 clrmsg $ (IMAGR only) >> no bad messages >> tvmovie on the cubes: >> DDO75_R.ICL001.2: some emission channels look a bit stripey... >> DDO75_R.ICL002.2: some pos/neg emission pattern visible >> DDO75_R.ICL003.2: ditto, but fainter >> DDO75_R.ICL004.2: nothing much visible >> Comparison to original 2048 image (before this editing run): ran COMB on channel 54 of robust cube for this run and previous. DDO75_R.SUM.1. There IS a difference: the difference image has clear vertical stripes at the ~50 microJy level; and fainter horizontal ones. No diagonal ones though; and it's a diagonal stripe pattern I've been seeing... Apparently, not much I can do about it. I just hope the editing was enough to end up with decent moment maps... >> screen shot of difference map: d75_run2-run1_comb.jpg Computing the noise levels for the natural weigthing setting: ^ DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; cellsize 1.5; imsize 2048; uvwtfn ''; dotv -1; calcode '-cal'; 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 512 512 1536 1536 bchan 15;echan 20; $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' getn 89 $ *.UVLSF.3 galaxy> IMAGR1: IMACPY: Only 1680921 samples of 1683078 fell on UV grid galaxy> IMAGR1: **** WARNING data discarded outside usable part of UV plane **** galaxy> IMAGR1: **** Actual Umax 5.2536E+04 exceeds limit 4.8081E+04 **** galaxy> IMAGR1: **** Use cellsize < 1.37282 not 1.50000 to get all data **** galaxy> IMAGR1: **** using a U guard band of 0.300 of a radius **** galaxy> IMAGR1: **** WARNING data included out of inner portion of UV plane **** galaxy> IMAGR1: Create NOISENA .IBM001. 1 (MA) on disk 1 cno 126 galaxy> IMAGR1: Create NOISENA .IBM002. 1 (MA) on disk 1 cno 127 galaxy> IMAGR1: Create NOISENA .IBM003. 1 (MA) on disk 1 cno 128 galaxy> IMAGR1: Create NOISENA .IBM004. 1 (MA) on disk 1 cno 129 galaxy> IMAGR1: Create NOISENA .IIM001. 1 (MA) on disk 1 cno 130 galaxy> IMAGR1: Create NOISENA .IIM002. 1 (MA) on disk 1 cno 131 galaxy> IMAGR1: Create NOISENA .IIM003. 1 (MA) on disk 1 cno 132 galaxy> IMAGR1: Create NOISENA .IIM004. 1 (MA) on disk 1 cno 133 >> tvmovie NOISENA.IIM001.1: looks somewhat stripey (diagonal) >> imstat: blc 10 10 0; trc 2038 2038 6 The rms noise measured in a line free channel is: Field 1(5asec resolution): 0.46 mJy Field 2(15 asec resolution): 0.61 mjy Field 3(45 asec resolution): 0.96 mJy Field 4(135 asec resolution): 1.79 mJy >> These noise levels are essentially identical to pre-editing run. Making a natural weighted data cube: >> 14Aug11 DEFAULT IMAGR sources '',''; docalib -1;doband -1;outseq 0; outname 'ddo75NA2048'; cellsize 1.5; imsize 2048; uvwtfn ''; dotv -1; calcode '-cal'; ngauss 4;wgauss 0,15,45,135; fgaus 3*0.46e-3 3*0.61e-3 3*0.96e-3 3*1.79e-3 $fgaus 3sigma in all fields niter 1e6 $just to ensure we reach the Fgauss limits nbox 1 clbox 512 512 1536 1536 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 89 $ *.UVLSF.3 galaxy> IMAGR1: **** WARNING data discarded outside usable part of UV plane **** galaxy> IMAGR1: **** Actual Umax 5.2530E+04 exceeds limit 4.8081E+04 **** galaxy> IMAGR1: **** Use cellsize < 1.37298 not 1.50000 to get all data **** galaxy> IMAGR1: **** using a U guard band of 0.300 of a radius **** galaxy> IMAGR1: **** WARNING data included out of inner portion of UV plane **** galaxy> IMAGR1: **** Watch for high-frequency & other poor cleaning effects **** 1 2 14-AUG-2011 12:47:37 IMAGR Create DDO75NA2048 .IBM001. 1 (MA) on disk 1 cno 134 1 2 14-AUG-2011 12:47:54 IMAGR Create DDO75NA2048 .IBM002. 1 (MA) on disk 1 cno 135 1 2 14-AUG-2011 12:48:11 IMAGR Create DDO75NA2048 .IBM003. 1 (MA) on disk 1 cno 136 1 2 14-AUG-2011 12:48:31 IMAGR Create DDO75NA2048 .IBM004. 1 (MA) on disk 1 cno 137 1 2 14-AUG-2011 12:48:48 IMAGR Create DDO75NA2048 .ICL001. 2 (MA) on disk 1 cno 138 1 2 14-AUG-2011 12:49:09 IMAGR Create DDO75NA2048 .ICL002. 2 (MA) on disk 1 cno 139 1 2 14-AUG-2011 12:49:25 IMAGR Create DDO75NA2048 .ICL003. 2 (MA) on disk 1 cno 140 1 2 14-AUG-2011 12:49:43 IMAGR Create DDO75NA2048 .ICL004. 2 (MA) on disk 1 cno 141 default prtmsg prtask 'IMAGR' $ the task for which you want the aips messages outprint 'd75:d75_imagr7c_na_14Aug11' $ the name of the file to write to docrt -1 prtmsg $ D75_IMAGR7c_NA_14Agu11 clrmsg $ (IMAGR only) >> no bad messages >> tvmovie: >> DDO75NA2048.ICL001.2: emission in channels 36 - 75? Still a bit >> stripey... >> DDO75NA2048.ICL002.2: faint pos/neg emission in line channels; >> stripes still visible... >> DDO75NA2048.ICL003.2: faint pos/neg emission in line channels; not >> stripey though >> DDO75NA2048.ICL004.2: not much visible 8. Convolution and Blanking executed on 9Aug11 reexecuted 14Aug11 ^A. Convolution DEFAULT CONVL blc 0; trc 0; outname ''; opcode ''; bmaj 25; bmin 25 outclass 'CVL25' getn 138 $ *NA2048.ICL001 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.ICL001.2 >> ----> DDO75NA2048.CVL25.2 galaxy> CONVL1: Task CONVL (release of 31DEC08) begins galaxy> CONVL1: CLEAN beam : MAJ: 11.9360 MIN: 10.0220 PA: 4.2 galaxy> CONVL1: Convolve with: MAJ: 22.9033 MIN: 21.9666 PA: 94.2 galaxy> CONVL1: Using factor = 5.22478E+00 to scale image galaxy> CONVL1: Create DDO75NA2048 .CVL25 . 2 (MA) on disk 1 cno 125 galaxy> CONVL1: BMAJ= 25.0000 BMIN= 25.0000 BPA= 0.0/Output beam galaxy> CONVL1: CVBMAJ= 22.9033 CVBMIN= 21.9666 CVBPA= 94.2/Convl. beam >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.CVL25.2 ### Get rms in convolved cube: 0.93 ^B. Blanking ^B.1 Making contour plots to identify the true line from the noise. DEFAULT KNTR docont 1; dogrey -1;dovect -1; ny 6; ltype 6; clev 0.00093; levs 2.5, 5, 10, 20, 40, 80 dotv 1; pixra -0.0019, 0.0074 $ pixrange=(-2sigma to +8sigma); docircle -1; blc 512 512 trc 1536 1536 getn 141 $ *NA2048.CVL25.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.CVL25.2 to get all interesting channels into PL files: ny 3 for i=1 to 5;dotv -1; blc(3)= 35+(i-1)*9;trc(3)=34+i*9;go kntr;wait kntr; end >> to print all created PL files to one multi-page file: default lwpla plver 1; invers 5 outfile 'D75:DDO75NA2048_2_kntr.ps ###We are going to use the NAtural weighted cube to create the master blanking cube. ^B.2 Blank the cube at 2.5 sigma DEFAULT BLANK opcode 'SELC'; dparm 1, 0, 10000, 0.002325, 0 outclass 'CVL_BL'; trc 0; blc 0; bchan 0; echan 0 getn 141 $ *NA2048.CVL25.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.CVL25.2 ^B.3 Blank cube by hand - output is the master cube DEFAULT BLANK opcode 'TVCU'; doinvers -1; outclass 'master' txinc 4; tyinc 4 $ 2048 cube requires this getn 142 $ *NA2048.CVL_BL.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.CVL_BL.2 ----> DDO75NA2048.MASTER.2 ^B.4 use the master cube to blank the full resolution cube and the robust=0.5 cube >> This is the NEW corrected step that fixes DPARM problem discovered by >> Elias on 03 Aug 11. ^ DEFAULT BLANK DPARM 1,0,1000,-1000,0 opcode 'IN2C';outclass 'LMV'; getn 121 $ *NA.ICL001 $the robust resolution cube, the one created at step 7B get2n 143 $ *.MASTER >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.ICL001.2 >> AIPS 1: Got(2) disk= 1 user= 759 type=MA DDO75NA2048.MASTER.2 ----> DDO75_R.LMV.2 getn 137 $ *.ICL001 $the full resolution cube, the one created at step 7B get2n 143 $ *.MASTER DPARM 1,0,1000,-1000,0 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.ICL001.2 >> AIPS 1: Got(2) disk= 1 user= 759 type=MA DDO75NA2048.MASTER.2 ----> DDO75NA2048.LMV.2 ^9. ON THE ROBUST CUBE ^9.1 Transposing the cube executed on 11Aug11 reexecuted 14Aug11 DEFAULT TRANS outclass ''; blc 0; trc 0; transcod '312' getn 144 $ *.LMV >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.LMV.2 ----> DDO75_R.TRANS.2 ^ 9.2 Switching the header from frequency description to spectral-line velocity description getn 146 $ *. TRANS >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.TRANS.2 ALTSW ^ 9.3 Final products executed on 11Aug11 reexecuted 14Aug11 A. Moment maps: DEFAULT XMOM flux -10000; icut -10000; blc 0; trc 0 getn 146 $ *.TRANS >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.TRANS.2 galaxy> XMOM 1: Create DDO75_R .XMOMNC. 3 (MA) on disk 1 cno 147 galaxy> XMOM 1: Create DDO75_R .XMOM0 . 3 (MA) on disk 1 cno 148 galaxy> XMOM 1: Create DDO75_R .XMOM1 . 3 (MA) on disk 1 cno 149 galaxy> XMOM 1: Create DDO75_R .XMOM2 . 3 (MA) on disk 1 cno 150 galaxy> XMOM 1: Create DDO75_R .XMOM3 . 3 (MA) on disk 1 cno 151 >> We still have the 'pinhole' problem in the mom0 map. After much discussion and testing (I tried creating data sets without the most suspicious data sets, but got essentially NO difference in anything), the decision was made to just continue and let REMAG deal with the pinholes for now ^ 9.4 Primary Beam Corrections getn 148 $ *_R.XMOM0.3 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.XMOM0.3 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 148 $ *_R.XMOM0.3 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.XMOM0.3 >> ----> DDO75_R.X0_PBC.1 ^ 9.5 Replacing blanks with 0 DEFAULT REMAG pixval 0; blc 0; trc 0; outclass 'X0_P_R' getn 293 $ *.X0_PBC >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.X0_PBC.1 >> ----> DDO75_R.X0_P_R.1 ^ 10. ON THE NATURAL CUBE ^10.1 Transposing the cube executed on 14Aug11 ^DEFAULT TRANS outclass ''; blc 0; trc 0; transcod '312' getn 145 $ * NA.LMV >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.LMV.2 >> ----> DDO75NA2048.TRANS.1 ^10.2 Switching the header from frequency description to spectral-line velocity description getn 152 $ *. TRANS >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.TRANS.1 ALTSW ^10.3 Final products executed on 14Aug11 ^ A. Moment maps: DEFAULT XMOM flux -10000; icut -10000; blc 0; trc 0 getn 152 $*.TRANS >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.TRANS.1 galaxy> XMOM 1: Create DDO75NA2048 .XMOMNC. 1 (MA) on disk 1 cno 153 galaxy> XMOM 1: Create DDO75NA2048 .XMOM0 . 1 (MA) on disk 1 cno 154 galaxy> XMOM 1: Create DDO75NA2048 .XMOM1 . 1 (MA) on disk 1 cno 155 galaxy> XMOM 1: Create DDO75NA2048 .XMOM2 . 1 (MA) on disk 1 cno 156 galaxy> XMOM 1: Create DDO75NA2048 .XMOM3 . 1 (MA) on disk 1 cno 157 ^10.4 Primary Beam Corrections getn 154 $ *NA.XMOM0 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.XMOM0.1 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 154 $ *NA.XMOM0 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.XMOM0.1 >> ----> DDO75NA2048.X0_PBC.1 ^10.5 Replacing blanks with 0 DEFAULT REMAG pixval 0; blc 0; trc 0; outclass 'X0_P_R' getn 92 $ *.X0_PBC >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75NA2048.X0_PBC.1 >> ----> DDO75NA2048.X0_P_R.1 ^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. >> DDO75NA2048.ICL001.2: Conv size= 11.94 X 10.02 >> DDO75_R.ICL001.2: Conv size= 7.55 X 6.45 >> Going to have to convolve the Robust cube ^ DEFAULT CONVL bmaj 10; bmin 10; blc 0; trc 0; opcode ''; outna 'D75CVL10'; outclass ''; doblank 0; factor 0; outse 0; getn 61 $ *R.ICL001 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA DDO75_R.ICL001.2 >> ----> D75CVL10.CONVL.1 >> galaxy> CONVL1: CLEAN beam : MAJ: 7.5529 MIN: 6.4514 PA: 13.7 >> galaxy> CONVL1: Convolve with: MAJ: 7.6406 MIN: 6.5539 PA: 103.7 >> galaxy> CONVL1: Using factor = 2.05226E+00 to scale image >> galaxy> CONVL1: BMAJ= 10.0000 BMIN= 10.0000 BPA= 0.0/Output beam >> galaxy> CONVL1: CVBMAJ= 7.6406 CVBMIN= 6.5539 CVBPA= 103.7/Convl. beam ^ DEFAULT BLANK opcode 'IN2C';outclass 'LMV'; DPARM 1,0,1000,-1000,0 getn 90 $ *.CONVL get2n 71 $ *.MASTER >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.CONVL.1 >> AIPS 1: Got(2) disk= 1 user= 759 type=MA DDO75NA2048.MASTER.2 >> ----> D75CVL10.LMV.1 ON THE CONVOLVED CUBE ^ 11.1 Transposing the cube executed on 17Aug11 ^ DEFAULT TRANS outclass ''; blc 0; trc 0; transcod '312' getn 91 $ $ *CVL10.LMV >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.LMV.1 >> ----> D75CVL10.TRANS.1 ^ 11.2 Switching the header from frequency description to spectral-line velocity description getn 92 $ *. TRANS >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.TRANS.1 ALTSW ^ 11.3 Final products executed on 17Aug11 ^A. Moment maps: DEFAULT XMOM flux -10000; icut -10000; blc 0; trc 0 getn 92 $ .TRANS >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.TRANS.1 galaxy> XMOM 1: Create D75CVL10 .XMOMNC. 1 (MA) on disk 1 cno 93 galaxy> XMOM 1: Create D75CVL10 .XMOM0 . 1 (MA) on disk 1 cno 94 galaxy> XMOM 1: Create D75CVL10 .XMOM1 . 1 (MA) on disk 1 cno 95 galaxy> XMOM 1: Create D75CVL10 .XMOM2 . 1 (MA) on disk 1 cno 96 galaxy> XMOM 1: Create D75CVL10 .XMOM3 . 1 (MA) on disk 1 cno 97 ^11.4 Primary Beam Corrections getn 94 $ *CLV10.XMOM0 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.XMOM0.1 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 94 $ *.XMOM0 >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.XMOM0.1 >> ----> D75CVL10.X0_PBC.1 ^11.5 Replacing blanks with 0 DEFAULT REMAG pixval 0; blc 0; trc 0; outclass 'X0_P_R' getn 98 $ *.X0_PBC >> AIPS 1: Got(1) disk= 1 user= 759 type=MA D75CVL10.X0_PBC.1 >> ----> D75CVL10.X0_P_R.1 >> PRTMSG: D75_COMBINE_PRTMSG_17AUG11; clrmsg ^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. >> ALTSW run on: CONTINUUM.ICL001.4 DDO75_R.ICL001.2 DDO75_R.ICL002.2 DDO75_R.ICL003.2 DDO75_R.ICL004.2 DDO75NA2048.ICL001.2 DDO75NA2048.ICL002.2 DDO75NA2048.ICL003.2 DDO75NA2048.ICL004.2 DDO75NA2048.CVL_BL.2 DDO75NA2048.MASTER.2 DDO75_R.LMV.2 DDO75NA2048.LMV.2 DDO75_R.XMOM0.3 DDO75NA2048.XMOM0.1 DDO75NA2048.X0_PBC.1 DDO75NA2048.X0_P_R.1 DDO75_R.X0_PBC.1 DDO75_R.X0_P_R.1 D75CVL10.CONVL.1 D75CVL10.LMV.1 D75CVL10.XMOM0.1 D75CVL10.X0_PBC.1 D75CVL10.X0_P_R.1 14. Naming convention >> Prior to archiving, I'm running SPLIT on the .UVCONT.2 dataset, which has a FG table. This will apply the FG table. default SPLIT getn 58 $ .UVCONT.2 >> AIPS 1: Got(1) disk= 1 user= 759 type=UV D75_BCD.UVCONT.2 >> ----> D75_BCD.SPLIT.1 >> AIPS 1: Rename D75_BCD .SPLIT . 1 (UV) on disk 1 cno 100 >>> AIPS 1: To D75_BCD .UVCONT. 3 (UV) on disk 1 cno 100 For each uv data set: ^DDO75_AB_TRIM.FITS ^DDO75_B1A_TRIM.FITS ^DDO75_B1B_TRIM.FITS ^DDO75_C1_TRIM.FITS ^DDO75_C2_TRIM.FITS ^DDO75_C3H_TRIM.FITS ^DDO75_D3H_TRIM.FITS ^DDO75_B2H_SPLIT.FITS ^DDO75_D1_SPLIT.2.FITS Combined uv data: ^DDO75_BCD_DBCON.FITS Minus continuum: ^DDO75_BCD_UVLSF.FITS Continuum only, uv data and map: ^DDO75_BCD_UVCONT.FITS ^DDO75_CONTINUUM_ICL.FITS Product of MSclean: ^DDO75_R_ICL001.FITS ^DDO75_R_ICL002.FITS ^DDO75_R_ICL003.FITS ^DDO75_R_ICL004.FITS ^DDO75_NA_ICL001.FITS ^DDO75_NA_ICL002.FITS ^DDO75_NA_ICL003.FITS ^DDO75_NA_ICL004.FITS Blanking: ^DDO75_NA_CVL_BL.FITS ^DDO75_NA_MASTER.FITS ^DDO75_KNTR_2.5sig.eps Final blanked cubes: ^DDO75_NA_LMV.FITS ^DDO75_R_LMV.FITS Moment maps: ^DDO75_NA_XMOMNC.FITS ^DDO75_NA_XMOM0.FITS ^DDO75_NA_XMOM1.FITS ^DDO75_NA_XMOM2.FITS ^DDO75_NA_XMOM3.FITS ^DDO75_R_XMOMNC.FITS ^DDO75_R_XMOM0.FITS ^DDO75_R_XMOM1.FITS ^DDO75_R_XMOM2.FITS ^DDO75_R_XMOM3.FITS Moment zero, PBC and REMAG corrections: ^DDO75_NA_X0_PBC.FITS ^DDO75_NA_X0_P_R.FITS ^DDO75_R_X0_PBC.FITS ^DDO75_R_X0_P_R.FITS Convolved data: Cube: ^DDO75_CVL10_ICL001.FITS Blanked: ^DDO75_CVL10_LMV.FITS Moment maps: ^DDO75_CVL10_XMOMNC.FITS ^DDO75_CVL10_XMOM0.FITS ^DDO75_CVL10_XMOM1.FITS ^DDO75_CVL10_XMOM2.FITS ^DDO75_CVL10_XMOM3.FITS Moment zero PBC and REMAG corrections: ^DDO75_CVL10_X0_PBC.FITS ^DDO75_CVL10_X0_P_R.FITS galaxy> FITTP1: Writing to disk file: D75F:DDO75_BCD_DBCON.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_BCD.DBCON.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_BCD_UVLSF.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_BCD.UVLSF.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_BCD_UVCONT.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_BCD.UVCONT.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CONTINUUM_ICL.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name CONTINUUM.ICL001.4 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_ICL001.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.ICL001.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_ICL002.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.ICL002.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_ICL003.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.ICL003.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_ICL004.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.ICL004.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_ICL001.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.ICL001.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_ICL002.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.ICL002.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_ICL003.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.ICL003.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_ICL004.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.ICL004.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_CVL_BL.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.CVL_BL.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_MASTER.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.MASTER.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_LMV.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.LMV.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_LMV.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.LMV.2 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_XMOMNC.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.XMOMNC.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_XMOM0.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.XMOM0.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_XMOM1.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.XMOM1.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_XMOM2.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.XMOM2.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_XMOM3.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.XMOM3.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_X0_PBC.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.X0_PBC.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_NA_X0_P_R.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.X0_P_R.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_XMOMNC.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.XMOMNC.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_XMOM0.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.XMOM0.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_XMOM1.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.XMOM1.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_XMOM2.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.XMOM2.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_XMOM3.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75_R.XMOM3.3 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_X0_PBC.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.X0_PBC.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_R_X0_P_R.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name DDO75NA2048.X0_P_R. galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_ICL001.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.CONVL.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_LMV.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.LMV.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_XMOMNC.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.XMOMNC.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_XMOM0.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.XMOM0.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_XMOM1.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.XMOM1.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_XMOM2.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.XMOM2.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_XMOM3.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.XMOM3.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_X0_PBC.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.X0_PBC.1 galaxy> FITTP1: Writing to disk file: D75F:DDO75_CVL10_X0_P_R.FITS galaxy> FITTP1: Writing image: User 759 Disk 1 Name D75CVL10.X0_P_R.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_AB_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_AB.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_B1A_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_B1A.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_B1B_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_B1B.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_C1_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_C1.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_C2_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_C2.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_C3H_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_C3H.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_D3H_TRIM.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_D3H.TRIM.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_B2H_SPLIT.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_B2H.SPLIT.1 galaxy> FITTP1: Writing to disk file: UF:DDO75_D1_SPLIT.2.FITS galaxy> FITTP1: Writing UV data: User 759 Disk 1 Name D75_D1.SPLIT.2