Difference between revisions of "TWHydraBand7 Imaging 4.0"

From CASA Guides
Jump to navigationJump to search
Line 6: Line 6:
* '''Details of the ALMA data are provided at [[TWHydraBand7]]'''
* '''Details of the ALMA data are provided at [[TWHydraBand7]]'''
* '''A simplified version of this guide intended for use at the 13th Synthesis Imaging Workshop is here: [[TwHydraBand7_Imaging_SS12]]''
== Confirm your version of CASA==
== Confirm your version of CASA==

Revision as of 13:31, 22 October 2012

  • This tutorial picks up where TWHydraBand7_Calibration_3.4 leaves off, with fully calibrated, split science target MS. If you wish to skip the Calibration guide: obtain the calibrated data from TWHydraBand7#Getting_the_Data; extract it using tar -xzvf FILENAME; and cd into the extracted directory.

Confirm your version of CASA

This guide has been written for CASA release 3.4.0. Please confirm your version before proceeding.

version = casalog.version()
print "You are using " + version
if (int(version.split()[4][1:-1]) < 19988):
    print "Your version of CASA is appropriate for this guide."

Prepare Continuum Data for Further Processing

In order to speed up imaging/self-calibration for the continuum data we will average channels together, and then flag the few spectral features. This method works well in the case of only a few spectral lines, while retaining enough channelization to aid in multi-frequency synthesis and being able to remove spectral features in the averaged data. The amount of channel averaging should be adjusted to your particular data. Note for wide bandwidth data it is never a good idea to use the continuum estimate generated by uv-continuum subtraction as your continuum data. This worked OK in the past with the narrow band systems like the VLA and low dynamic range instruments like the SMA, but is not advised for ALMA wide bandwidth, high dynamic range data.

<figure id="Cont_spw2.png">

CO(3-2) in spw=2 from the "continuum" channel averaged data.

</figure> <figure id="Cont_spw3.png">

Notice upswing at high channel numbers in spw=3.


One can also flag the spectral features first but in that case make a backup of the file that is analogous to TWHydra_corrected.ms as you will need it later (unflagged) for spectral line imaging. We begin by excluding ~20 channels on each edge, and averaging over 100 channel intervals:

os.system('rm -rf TWHydra_cont.ms*')

Now make a plot of amplitude vs. channel to see what needs to be flagged


The CO(3-2) and HCO+(4-3) lines are obvious. The 4th spw; spw=3 also shows an upswing on the highest channels that is problematic, it was seen on the calibrators too and is likely due to a weak atmospheric feature, we will flag the worst of it.

<figure id="Cont_uvplot.png">

UV-plot of the continuum emission, colors show spws.



Have a look at the continuum as a function of uv-distance (in the plot to the right, the 4 spw are shown in different colors on top of each other). If the data are flat as a function of uv-distance, the source is completely unresolved. If instead you see structure (in this case decreasing amplitude with uv-distance), the source is resolved.


Notice that the spw do not have the same amplitude. Unfortunately, the red spw (highest frequency) should be higher than the green one (lowest frequency) because optically thin dust goes as nu^4, and optically thick as nu^2. This inconsistency is due to imperfect amplitude/absolute flux calibration. The self-calibration below will bring them into agreement with each other, but this is the sort of thing that results in considerable absolute flux uncertainty at submillimeter wavelengths. We are working on how to do this better.

A priori Noise Estimates

<figure id="Corrected_time.png">

Plot for estimating time.

</figure> <figure id="sensitivity_cont.png">

Sensitivity calculator setup with observed continuum parameters for these observations.


To estimate what the expected noise levels are, we first need to know how much time we had on source. Looking at a plot of amplitude vs time for the concatenated but pre-split data (see below) there are 9x8min scans + 6x6min scans + 3x1min + 2x2min scans for about 1.9 hours on source. There are 2 polarizations and about 1.75 GHz of total continuum bandwidth taking into account flagging.

Using this information and https://almascience.nrao.edu/call-for-proposals/sensitivity-calculator, we find that the expected rms noise for the continuum is about 0.3 mJy/beam.

For the spectral line data, which we will image below, with 0.12 km/s channels (needs to be entered in the field bandwidth per polarization), the expected rms noise for the spectral lines is about 32 mJy/beam.

Image and Self-Calibrate the Continuum

If you are unfamiliar with the CASA viewer it is a good idea to pause here and
watch the demo at http://casa.nrao.edu/CasaViewerDemo/casaViewerDemo.html

Create Initial Clean Image

First we will make an initial image using clean, this task will both deconvolve and clean.

If you are unfamiliar with the basic concepts of deconvolution and clean,
pause here and review for example

In clean, we use mode='mfs' to do multifrequency synthesis, in other words grid each uv-channel independently. Since the uv-spacing is a function of frequency, this will actually achieve greater uv-coverage than if all the channels and spws had been averaged in advance. The imsize=100 and cellsize=['0.3arcsec'] were chosen to be appropriate for the Band and antenna configuration. At ALMA Band 7, the Full Width Half Power primary beam is about 20", so we want to make our image at least this big. We've made it a bit larger out to about the 25% power point. For the configuration used to take these data, the resolution is expected to be about 1.5" and it is a good idea to oversample the beam by setting the cell size to be a factor of 4 or 5 smaller than the beam (we have used 5 here).

For doing self-calibration it is essential that only "real" signal be included in the image model, thus it is important to make a clean mask, and clean the first iteration rather conservatively (shallowly) so that you are sure that you do not have clean components in your model that do not represent real source emission. In the example below we set interactive=T so you can interactively make the clean mask and stop clean when the signal from the source starts to approach the surrounding "noise" areas in the residual map.

NOTE: Real emission will not go away if you do not put a clean box on it. Conversely if you put a clean box on something that is NOT real and clean deeply you can amplify that feature. Thus, its best to be conservative and build up your clean box as you go, you can generally see fainter "real" features in the residuals.

NOTE: If you start an interactive clean, and then do not make a mask, clean will stop when you tell it to go on because it has nothing to clean. There is no default mask.

<figure id="Viewer_clean1.png">

Interactive viewer.


os.system('rm -rf TWHydra_contall.*')
      mode='mfs', imagermode='csclean',

NOTE:clean will generate several files automatically with the imagename prepended:

  • <imagename>.image # the final restored image
  • <imagename>.flux # the effective primary beam response (e.g. for pbcor)
  • <imagename>.flux.pbcoverage # the primary beam coverage (ftmachine=’mosaic’ only)
  • <imagename>.model # the model image
  • <imagename>.residual # the residual image
  • <imagename>.psf # the synthesized (dirty) beam

Once the Clean Viewer opens, click on the polygon tool with your left mouse button, and draw a polygon around the continuum emission with the left mouse button. Double click inside the region with the left mouse button when you are happy with it. It will turn from green to white when the clean mask is accepted. To continue with clean use the "Next action" buttons in the green area on the Viewer Display GUI.

The red X will stop clean where you are, the blue arrow will stop 
the interactive part of clean, but continue to clean non-interactively 
until reaching the number of iterations requested (niter) or the flux 
density threshold (whichever comes first), and the green circle arrow 
will clean until it reaches the "iterations" parameter on the left side 
of the green area.  

You should chose the green circle arrow. It will clean 100 iterations (number under iteration in the green area on the Viewer GUI) and then show the residual image again. The middle mouse button is automatically assigned to the "plus" icon, which adjusts the colorscale. If you cannot easily access multiple mouse buttons, you can always assign your one mouse button the icon you want by clicking on it. Adjust the color scale so you can see the structure in the noise better. Also, note that the logger is telling you the amount of clean flux recovered so far, the min/max residuals, and the synthesized beam:

Model 0: max, min residuals = 0.0203454, 0.00267232 clean flux 1.30124
Threshhold not reached yet.
Beam used in restoration: 1.6962 by 1.54549 (arcsec) at pa 28.9043 (deg) 

Already with only 100 iterations, the residuals outside the clean mask are larger than that inside. So we will stop here by hitting the Red X symbol.

1st Round of Continuum Data Phase Self-calibration

Next we can use the clean model to self-calibrate the uv-data. The process of self-calibration tries to adjust the data to better match the model you give it. That is why it is important to make the model as good as you can. clean places a uv-model of the resulting image in the file TWHydra_cont.model. This model can then be used to self-calibrate the data using gaincal. We use gaintype='T' to tell it to average the polarizations before deriving solutions (which gains us a sqrt(2) in sensitivity). A critical parameter to play with is solint; we use solint=30s. From listobs the integration time of these data is about 10 seconds, so using solint=30s then gains us a sqrt(3) in sensitivity. It is often best to start with a larger solint and then work your way down to the integration time if the S/N of the data permits. For the same reasons as described in the TWHydraBand7_Calibration_3.4 tutorial we want to fix up the phases before tackling amplitude by setting calmode='p'.


<figure id="Self_1_phase.png">

Phase solutions from self_1.pcal with solint=30s.


Because combine=' ', we are getting independent solutions for each spw. If you are desperate for S/N, you can try combining them with combine='spw'. We have plenty of S/N in these data so we keep them separate. Look at the solutions.


The magnitude of corrections gives you a sense of how accurate the phase transfer from the calibrators was. You are checking to see that the phases are being well tracked by the solutions, i.e. smoothly varying functions of time within a given scan. Also the solutions for each spw are lying basically on top of each other which indicates that the spw to spw phase offsets are well calibrated already. Overall, these solutions look quite good. If they didn't you could try increasing the solint and/or combining the spw into a single solution.

After checking that you are happy with the solutions, apply them with applycal


<figure id="Viewer_pcal1.png">

Clean residuals after 100 iterations and the 1st phase only self-cal. Residuals inside mask are higher than the "noise" outside.


Next clean the source again, to save time we can start with the clean mask from the last iteration. If you make interactive adjustments to the clean mask, they will be written to the new mask TWHydra_contall_1pcal.mask, and not the old one.

os.system('rm -rf TWHydra_contall_1pcal.*')

Now after the first 100 iterations you see that the residuals inside the clean mask are higher than those outside. This is because flux that had been spread out in the map due to poorly correlated phases has been placed where it belongs on the source, thereby increasing its flux. You may also notice that your original clean mask is a little too small. If so, you can make it a bit larger, just by drawing a new polygon around the area you want to include. When you double click, it will incorporate the new mask into the current mask (if your box goes awry you can use the erase toggle [radio button] to erase and redo the mask). The new mask area need not overlap the original mask (though for this source it probably will). You might also want to use the magnifying glass to zoom in. Again, you assign mouse buttons by clicking on the icon you want. Clean another 100 iterations (for a total of 200) and stop by clicking the red X.

Now open initial and 1st self-cal images to compare them using imview. This is an alternative version of the viewer that is somewhat scriptable.


Once the Viewer Display panel opens, click on the "blink" toggle and then use the tapedeck buttons to alternate between the two images. Because the range was explicitly set, they are on the same color scale. It is obvious that the self-calibrated image is better. To quantify, 1st toggle back to "normal" and then draw a region that excludes the central source with the polygon tool and then double click inside (if you stay in the "blink" view, only the statistics for the last image opened will appear on the terminal instead of both). The basic statistics of the polygon region will print to the terminal:

        Stokes       Velocity          Frame        Doppler      Frequency 
             I          0km/s           TOPO          RADIO    3.50845e+11 
BrightnessUnit       BeamArea           Npts            Sum           Flux 
       Jy/beam        33.0039           2357  -9.434800e-01  -2.858690e-02 
          Mean            Rms        Std dev        Minimum        Maximum 
 -4.002885e-04   7.906752e-03   7.898289e-03  -2.541723e-02   2.172779e-02 

        Stokes       Velocity          Frame        Doppler      Frequency 
             I          0km/s           TOPO          RADIO    3.50845e+11 
BrightnessUnit       BeamArea           Npts            Sum           Flux 
       Jy/beam        33.0039           2357   6.326584e-01   1.916918e-02 
          Mean            Rms        Std dev        Minimum        Maximum 
  2.684168e-04   3.655786e-03   3.646692e-03  -1.215155e-02   1.109403e-02 

The self-calibrated image has more than a factor of 2 lower rms noise!

2nd Round of Continuum Data Phase Self-calibration

Now that we have a better model, we solve for solutions again. This time we will try making the solint smaller -- the integration time is about 10 seconds, so we set solint='int' to have it use the integration time.

<figure id="Self_2_phase.png">

Phase solutions from self_2.pcal with solint='int'.



Now plot the new solutions.


The phases on this shorter solint still seem to be tracking well so we will apply it and make a new image and check to see if there is improvement.


<figure id="Viewer_pcal2.png">

Clean residuals after 2nd phase only self-cal and 250 iterations. The residuals inside the clean mask are lower than those outside, so its time to stop.


Now clean again, updating mask with the most recent mask file.

os.system('rm -rf TWHydra_contall_2pcal.*')

After 200 iterations

Model 0: max, min residuals = 0.00489776, -0.00464541 clean flux 1.44461

It looks like it could use just a little more cleaning, so set iterations=50 in the GUI.

Clean used 50 iterations to approach a threshhold of 0.0015067
0.0107122 Jy <- cleaned in this cycle for  model 0 (Total flux : 1.45532Jy)
Final maximum residual = 0.00326382
Model 0: max, min residuals = 0.00326382, -0.00321361 clean flux 1.45532

The small amount of flux cleaned this cycle indicates that clean is converging and it's about time to stop. Also the residuals inside the clean mask are now smaller than the residuals outside (i.e. the noise) also indicating it's time to stop by hitting the red X on the GUI.

Now repeat the display, blinking, and image statistics steps described above for the 1st and 2nd phase-only self-cal iterations.


The difference is small:

        Stokes       Velocity          Frame        Doppler      Frequency 
             I          0km/s           TOPO          RADIO    3.50845e+11 
BrightnessUnit       BeamArea           Npts            Sum           Flux 
       Jy/beam        33.0039           2466   4.611597e-02   1.397287e-03 
          Mean            Rms        Std dev        Minimum        Maximum 
  1.870072e-05   3.831524e-03   3.832255e-03  -1.414417e-02   1.109403e-02 

        Stokes       Velocity          Frame        Doppler      Frequency 
             I          0km/s           TOPO          RADIO    3.50845e+11 
BrightnessUnit       BeamArea           Npts            Sum           Flux 
       Jy/beam        33.0039           2466   1.159416e-01   3.512963e-03 
          Mean            Rms        Std dev        Minimum        Maximum 
  4.701606e-05   3.811716e-03   3.812199e-03  -1.383034e-02   1.078456e-02 

This small improvement suggests that we have gone as far as we can with phase self-cal.

Continuum Data Amplitude Self-Calibration

Now we will apply the best phase solution table on-the-fly while solving for the amplitude self-cal solutions. Since amplitude changes more slowly and is less constrained than phase, we use a longer solint='inf', as long as combine=' ' this means to do one solution per scan.


It's useful to look at the residual phase in the amplitude calibration table, i.e. since we applied our best phase-only solution while solving for this new amplitude and phase (calmode='ap') solution, the phase should already be corrected.

<figure id="Self_ap_phase.png">

Residual phase solutions from self_ap.cal.

</figure> <figure id="Self_ap_amp.png">

Amplitude solutions from self_ap.cal.



The residuals are very small as expected. (If you see large residuals here, it means that the phase-only solution is suspect, and you were mostly just moving noise around.) Now look at the amplitude solutions.


For the most part these look very good except one rather large deviation on DV06. Apply both the final phase and the amplitude calibration tables.


Plot the corrected data as a function of both time and uv-distance. It is always a good idea to check these after an amplitude self-calbration to be sure that it worked properly. Occasionally, a few spurious bits of data will get blown up by the amplitude self-cal if it is not well-constrained.

<figure id="Selfcal_time.png">

Post self-calibration amplitude vs. time

</figure> <figure id="Selfcal_uvdist.png">

Post self-calibration amplitude vs. uv-distance



The time where we saw a large amplitude correction on DV06 looks consistent here so the large correction we saw in the solutions corrected a real issue.


You will see that this plot looks much better than before.

<figure id="Viewer_apcal.png">

Clean residuals after final amplitude and phase self-cal.


Now make the final continuum image.

os.system('rm -rf TWHydra_contall_apcal.*')

We know we need to clean at least 300 iterations, so set this in the gui and hit the round green arrow. After this notice how much better the residual looks. Clean another 100 iterations. The "circular pattern", and 4 bright spots at each corner you see now in the residual is likely due to non-closing amplitude errors that cannot be removed with an antenna based self-calibration, so this is as good as it gets with pure self-cal. Hit the Red X to stop clean.

Clean used 100 iterations to approach a threshhold of 0.00105507
0.0061808 Jy <- cleaned in this cycle for  model 0
Final maximum residual = 0.00242926
Model 0: max, min residuals = 0.00238278, -0.00242926 clean flux 1.48201

Now repeat the display, blinking, and image statistics described above for the 2nd phase only and the new amplitude & phase self-cal'ed images.


The amplitude and phase self cal'ed image is notably better than phase-only. Quantitatively:

        Stokes       Velocity          Frame        Doppler      Frequency 
             I          0km/s           TOPO          RADIO    3.50845e+11 
BrightnessUnit       BeamArea           Npts            Sum           Flux 
       Jy/beam        33.0039           3542   2.053068e-01   6.220676e-03 
          Mean            Rms        Std dev        Minimum        Maximum 
  5.796351e-05   3.955967e-03   3.956101e-03  -1.383034e-02   1.078456e-02 

        Stokes       Velocity          Frame        Doppler      Frequency 
             I          0km/s           TOPO          RADIO    3.50845e+11 
BrightnessUnit       BeamArea           Npts            Sum           Flux 
       Jy/beam        33.0039           3542   6.044652e-04   1.831495e-05 
          Mean            Rms        Std dev        Minimum        Maximum 
  1.706565e-07   1.270183e-03   1.270362e-03  -4.980673e-03   4.137159e-03 

and indeed, we've gained another factor of 3 in sensitivity.

Overall with this self-calibration we've improved the noise by a factor of 6.7! With a peak flux density of 0.98 Jy, the S/N increased from 115 initially to 770 after. So, well worth the trouble.

It is notable that we are still a factor of more than 4 from the apriori noise estimate of 0.3 mJy/beam. This is likely due to residual sources of non-closing (not antenna based) errors in the data like baseline errors and baseline-dependent bandpass errors. Additionally, polarization errors (which we did not calibrate at all) can contribute, as well as imperfect uv-coverage with only 8 antennas. A dynamic range of 770 is actually quite good in the submillimeter.

Apply self-calibration to Full Dataset and Split Line Data

Now apply the self-calibration derived from the continuum emission to the full unchannel-averaged data.


Split off the CO(3-2) spectral line data in spw=2 and the HCO+(4-3) data in spw=0 for further processing.

os.system('rm -rf TWHydra_CO3_2.ms*')
os.system('rm -rf TWHydra_HCOplus.ms*')

Continuum Subtraction

Next we need to subtract the continuum emission from the spectral line data. It is best to do this in the uv-plane. The first step is to make a channel plot of the spectral data to get the line-free channel ranges for both spectral lines. Since the line emission is simple (one spectral line per spw) and there are more than enough line-free channels we do not need to be very precise just stay well away from the line and whenever possible it is best to chose line-free channel ranges on either side of the line for the best possible baseline subtraction.

<figure id="CO3_2_channel.png">

CO(3-2) line in channel space.

</figure> <figure id="HCOp4_3_channel.png">

HCO+(4-3) in channel space.


Note: after the split above, the original spw ids will be relabeled as 0 in each file because there is only one spectral window in each file.


It is a good idea to stay a little away from the very edges of the baseband which can be noisy. The channel ranges 20~2000 and 2400~3800 look like good choices for CO(3-2).


The channel ranges 20~1500 and 1900~3800 look like good choices for HCO+(4-3).

Next use the identified line-free channel ranges and uvcontsub2 to subtract the continuum model from the line emission.


Note: If you do not have line-free channels on both sides of the line emission, it is safer to use fitorder=0, or the fit may diverge.

Spectral Line Imaging

Now we are ready to make cubes of the line emission. The imaging parameters are similar to the continuum except for those dealing with the spectral setup: mode, start, width, nchan, restfreq, and outframe parameters. When making spectral images you have three choices for the mode parameter: channel, velocity, and frequency. Data are taken using constant frequency channels. For spectral line analysis it's often more useful to have constant velocity channels, and this is also the best way to make images of multiple lines with the exact same channelization for later comparison. For mode='velocity', the desired start and width also need to be given in velocity units for the desired output frame.

It is important to note that ALMA does not do on-line Doppler Tracking and the native frame of the data is TOPO. If you do not specify outframe the output cube will also be in TOPO, which is not very useful for spectral line work. The Doppler Shift is taken out during the regridding to the desired outframe in clean or alternatively it can be done separately by the cvel task which would need to be run before clean.

<figure id="CO3_2_vel.png">

CO(3-2) spectrum in LSRK velocity space.

</figure> <figure id="HCOp4_3_vel.png">

HCO+(4-3) spectrum in LSRK velocity space.


To see what velocity parameters you want to set in clean it is useful to make a plot in plotms in the desired output frame. To make it easier to see, we set a plotrange since we know the LSRK velocity of TW Hya is about 2.88 km/s. Note these plots take a little longer because of the frame shift.


From these plots it looks like imaging the cubes from about -5 to +8 km/s will encompass the line, but still provide several line-free channels on either side so the noise level can be estimated. The channel width is 122 kHz, which at 345.79599 GHz is 0.106 km/s. Recall that the spectral resolution is a factor of two poorer. We will use a velocity channel width of 0.12 km/s for a little oversampling, but the spectral resolution remains 0.2 km/s.

As before, it is very important that you make a clean mask. There are many ways to do this ranging from the complicated to simple. For this example we will make a single clean mask that encompasses the line emission in every channel and apply it to all channels. This is much better than no clean mask, though not quite as good as making an individual mask for each channel. For some sources, one can use the continuum mask to clean the line, however TW Hya is a bit curious in that the continuum emission is not as extended as the line emission (Hughes et al. 2008).

CO(3-2) Imaging

os.system('rm -rf TWHydra_CO3_2line.*')

<figure id="Viewer_55.png">

Interactive Viewer window with CO(3-2) clean mask, before cleaning starts.

</figure> <figure id="Viewer_500.png">

Interactive Viewer window for CO(3-2), after 500 iterations, more cleaning is needed.


It will take a little while to grid the cube, when the interactive viewer opens, use the tapedeck to cycle through the channels. You should see a progress of line emission in channels 40 to 70 or so.

  • Go to channel 57 (about line center)
  • Select the polygon tool with the left mouse button
  • Select the "All Channels" toggle in the green area
  • Draw a polygon around the channel 57 emission, double click inside to activate.
  • Now go to channel 60, this is the channel with the most extent to the SE, draw another polygon that encompasses this emission if necessary,double click inside to activate.
  • Now go to channel 55, this is the channel with the most extent to the NW, draw another polygon that encompasses this emission if necessary,double click inside to activate.
  • Now double check the mask by cycling through channels with real line emission to be sure that your clean box encompasses the emission, but does not extend far beyond it. Again the "erase" toggle can come in handy if things go awry or if you want to just delete a small portion of an existing mask (just draw a polygon around what you want to erase and double click inside), be sure to switch back to "add" before going on.

The figure shows what the final clean box should look like. Now clean using the green circle arrow. You can watch the progress in the logger. When 100 iterations are done, the viewer will show the residual map for each channel. Cycle through the channels and see whether you are still happy with the clean box in each signal channel. The "erase button" can help you fix mistakes. If necessary adjust. It is often useful to adjust the colorscale with the "plus" symbol icon. Keep going until the residual emission looks like the surrounding noise. If it seems to be going slowly, increase the iterations to 300 for a round or two. I stopped cleaning (Red x) when the logger showed (about 900 iterations).

12.9846 Jy <- cleaned in this cycle for  model 0
Final maximum residual = 0.157312
Model 0: max, min residuals = 0.157312, -0.0871295 clean flux 279.304

NOTE: The residuals are still a bit high in the strongest emission channels after it is well cleaned in the weaker channels. This is an indication that the sensitivity is "dynamic range" limited. In other words even with more intrinsic sensitivity per integration (i.e. better system temperature), the dynamic range limit would remain the same unless you get more uv-coverage. The fundamental dynamic range limitations of ALMA will be considerably better with 16 antennas in Early Science and MUCH better with the full 50-antenna array.

HCO+(4-3) Imaging

Now image and clean the HCO+(4-3) line using what you learned above.

os.system('rm -rf TWHydra_HCOplusline.*')

I stopped cleaning when:

4.79833 Jy <- cleaned in this cycle for  model 0
Final maximum residual = 0.0977348
Model 0: max, min residuals = 0.0977348, -0.060484 clean flux 192.066

Image Analysis

Moment Maps

Next we will make moment maps for the image cubes.

To determine channel ranges it is useful to open the cube in viewer as a raster image. Using the statistics tool the rms in a line-free channel is about 25 mJy/beam, however in one of the peak line channels it is as high as 50 mJy/beam. This difference is again because of the dynamic range limitations of the data (as described above for the continuum). Now open the cube again but as a contour map; click "Data Display Options" (wrench icon) on the viewer control bar; set the Unit Contour Level to 0.025 (this is in Jy/beam); set Relative Contour levels to [3] (i.e. this is showing 3-sigma contours). Now find out where the CO(3-2) emission drops below the 3sigma level.

For moment 0 (integrated intensity) maps you do not typically want to set a flux threshold because this will tend to noise bias your integrated intensity.


For higher order moments it is very important to set a conservative flux threshold. Typically something like 6 sigma, using sigma from peak line channel, works well.


Display all three moment maps in the viewer, overlaid with continuum contours.

imview( raster=[ {'file':'TWHydra_CO3_2line.image.mom0'},
                 {'file':'TWHydra_CO3_2line.image.mom.weighted_dispersion_coord'} ], 
        contour={'file':'TWHydra_contall_apcal.image', 'base':0, 'unit':0.0025, 'levels':[3,100]} )

To see all three raster images simultaneously, open the viewer's Panel Display Options (the "P-wrench" icon in the viewer tool bar), click "Number of panels", and change "Number of panels in x" to 3. Then select the "Blink" toggle (radio button) from the Animator panel.

<figure id="TWHya_CO3_2_moments.png">

ALMA CO(3-2) moment maps, with white continuum contours at 3 and 100 sigma. From left to right: integrated intensity, intensity weighted velocity field, intensity weighted velocity dispersion are shown.


Repeat for HCO+(4-3) which has a bit narrower velocity extent than the CO(3-2), but similar rms noise.


Display all three moment maps in the viewer using the same method described above for the CO(3-2) maps.

<figure id="TWHya_HCOp4_3_moments.png">

ALMA HCO+(4-3) moment maps, with white continuum contours at 3 and 100 sigma. From left to right: integrated intensity, intensity weighted velocity field, intensity weighted velocity dispersion are shown.


Channel Maps

Using the Viewer you can make channel map figures. Start the Viewer and then open the CO(3-2) cube as a raster image and then the continuum as a contour image. Then we use the "wrench" icon and "P wrench" icons to set up the channel images, contour levels etc. (If you need help setting up the viewer for this image, see a screen shot of the viewer setup windows, below.)

<figure id="TWHya_channel_co3_2.png">

Channel maps of the CO(3-2) emission with white continuum contours at 3 and 100 sigma.


<figure id="Viewer_setup.png">

The setup windows looked like this


Repeat for HCO+(4-3)

<figure id="TWHya_channel_HCOp4_3.png">

Channel maps of the HCO+(4-3) emission with white continuum contours at 3 and 100 sigma. The color intensity scale is the same as that used for CO(3-2).


Exporting Fits Images

If you want to analyze the data using another software package it is easy to convert from CASA format to FITS.

os.system('rm -rf TWHydra_CO3_2line.image.fits')

Although "FITS format" is supposed to be a standard, in fact most packages expect slightly different things from a FITS image. If you are having difficulty, try setting velocity=T and/or dropstokes=T.


os.system('rm -rf TWHydra_HCOplusline.image.fits')
os.system('rm -rf TWHydra_CO3_2line.image.mom0.fits')
os.system('rm -rf TWHydra_CO3_2line.image.mom.weighted_coord.fits')
os.system('rm -rf TWHydra_CO3_2line.image.mom.weighted_dispersion_coord.fits')
os.system('rm -rf TWHydra_HCOplusline.image.mom0.fits')
os.system('rm -rf TWHydra_HCOplusline.image.mom.weighted_coord.fits')
os.system('rm -rf TWHydra_HCOplusline.image.mom.weighted_dispersion_coord.fits')
os.system('rm -rf TWHydra_contall_apcal.image.fits')

Last checked on CASA Version 3.4.0.