Fit an arbitrary sky (image) model to an existing MS

From CASA Guides
Revision as of 09:32, 7 April 2016 by Bmason (talk | contribs)
Jump to navigationJump to search

Simulating and Fitting a Sky Model to an Existing Measurement Set in the UV Domain

version 20may2015, written with CASA v4.3.1 Note: we know of at least some ALMA 12m data for which the procedure documented here does not work. The reasons for this are under investigation (Apr 2016)

This casaguide illustrates how to fit an arbitrary sky image model to an existing MS. Along the way it illustrates how to "get your hands" on the raw visibility data in the python interface and how to compute the Chi-squared of the visibility data to your given model. This could be useful if you have a set of source models you would like to compare in the UV domain, but the models are too complicated to be handled by the set of models provided in CASA's uvmodelfit() task. The methods illustrated here can be used to estimate the scaling and goodness-of-fit of your model to the MS (*although, for absolute goodness of fit, please note the caveat at the end of this page!). They could also be the starting point for a more comprehensive and sophisticated exploration of a set of possible models using the Chi-squared statistic, for instance. The focus of this guide is an ALMA dataset but the techniques are generally applicable.

The example assumes we have an ALMA 7m MS; we are interested in the continuum data only; and we have a sky model as a FITS image which we wish to compare with the UV data (i.e., the MS). As written, this tutorial requires you to process one spectral window (SPW) at a time.

First suppose we have a calibrated ALMA 7m MS called and a sky model image in a FITS file called myskymap.fits. We need to import it into CASA as a CASA image. Furthermore, this image must have four coordinate axes: two spatial coordinates, a FREQUENCY axis, and a STOKES axis. This is true even if the data and simulation are single-polarization continuum data, in which case the FREQUENCY and STOKES axes can be "singleton" axes. We assume our FITS input model image does not have these extra axes. There are two ways you can add them: 1) the CASA importfits() task will fill these in for you if you set defaultaxes=False with the appropriate sub-parameters; 2) the simutil() module will allow you to do it. We illustrate the second case:

default importfits

from simutil import simutil

# Set the INCENTER and INWIDTH for the SPW of interest from the listobs()

In the call to util.modifymodel() we have taken advantage of the fact that modifymodel() does not change axes for which the corresponding function argument is a null string. This is handy, we don't wish to have to redundantly specify the pixel size and image center ("incell" and "indirection") if they are already correct.

Next we split out the SPW and field(s) of interest --- in this example there happens to be only a single field, but the method would work with a mosaic--- and do some time averaging to reduce the data volume (the averaging by default will be limited by scan and field ID). Two copies of the MS are made; one with the split data, the other will be overwritten to contain the calculated visibilities for the model. Note that in principle you can also do this data selection step using the simulator toolkit's setdata() method, but for the time being the recommended method is to create a fully split MS that contains only the data you want to simulate in a given call to the simulator (i.e. to sm.predict()). The simulated visibilities will go in the DATA column of the MS.

# split out one SPW and the field(s) of interest-
#  make two copies, one of which will get overwritten by the MOCK

Currently there is a mismatch in the way real ALMA data are written and how the CASA simulator identifies antennas, with the result that we need to manually set the telescope name in the MS for 7m data (only): for most other telescopes this will not be the case. We do this using the table toolkit, which exists in your casa environment as "tb"--

# set the telescope name manually- the need for this is probably a defect -
#  (sim tool infers primary beam from telescope name)
# ***DO THIS ONLY FOR ALMA 7M data!***
for i in range(len(tel)):


Next we use the simulator toolkit--- which is instantiated in your CASA environment as "sm"--- to generate predicted model visibilities from the model image. Only three calls to sim are needed: one to open the MS; one to set the primary beam (which is done from the telescope name); and one to generate the predicted visibilities.


# you could do data selection using the sm.setdata() method call here,
#  but we have already created a split() MS by SPW and FIELD so don't need to.
#  using SPLIT() is at present the recommended method.

# this sets the primary beam ("voltage pattern")-
# check sanity-

# Note 1: you can also include an optional componentlist argument.
# Note 2: the result has gone in the data column, not the model column

# check sanity again  -

# plot what the observed model would look like, sans noise (dirty map) - 

Note that the primary beam CASA by default uses for ALMA antennas is a rough approximation to the real (known) primary beams: it uses the beam that a uniformly illuminated antenna about 15% smaller would have (an Airy disk).

Now we wish to extract the complex visibilities and their associated weights into python to see how well they match up (i.e., compute Chi-squared) and estimate a scale factor for the model from the data. We do this using the MS tool, which is instantiated in your CASA environment as "ms". For some applications, e.g. high-dynamic range imaging over large regions, this could be a limiting factor in the fit quality requiring special steps beyond the scope of this CASA guide (setting a custom primary beam).
# Set up the ms tool to select the visibilities we want
# generally for ALMA data, datadescid is equal to the SPW number.
#  if in doubt, ms.getspectralwindowinfo() will return a python dictionary
#  showing the properties of the spectral windows and how to map them to datadescid.
# ms.getdata() returns a dictionary, each element of which is a numpy array
# The weights for the model and the data should be identical
#   and equal to 1/error^2 for each visibility.

# now get visibility values from the actual (not mock) data-

With the model and data visibility values in numpy arrays, it is then relatively straightforward to compare them, estimating scaling factors and errors in parameters of interest, etc. Some analysis steps and manipulations are illustrated here --

# what are the dims of the data?

# built-in sqrt method does not work elementwise so import numpy's version -
import numpy as np

# first index indexes polarization (there are two --XX, YY); second is null (probably SPW or IF, nominally)-
# the above plot should match up with the PLOTMS() plot we made just after sm.predict()

# calculate chi2-
c2= (r2[:,0,:]-rr[:,0,:])**2 * wt + (i2[:,0,:]-ii[:,0,:])**2 * wt
# typical data point contributes 1.6 to chi2-
# total chi2 per DOF-
# = 2.31 for this dataset
#  ***NOTE that the absolute normalization of the weights may or may not be correct, so take the 
#      chi-squared values with a grain of salt.

# simple single-parameter linear least squares fit of the model to the data-
numerator =  r2[:,0,:] * rr[:,0,:] * wt + i2[:,0,:]*ii[:,0,:] * wt
denominator =  (rr[:,0,:])**2 * wt + (ii[:,0,:])**2 * wt
# linear least-squares scale factor between data and model -
scalefac= numerator.sum() / denominator.sum()
# uncertainty in scalefac, if the weights are correct in an absolute sense -

*A caveat: in current (4.2.2+) versions of CASA, ALMA data that are calibrated by the automated calibration pipeline have weights which have units of 1/Jy^2 (as they should) and values that are close to correct in an absolute sense. For reasons still be determined the absolute accuracy of these weights is about 20%, i.e. they can routinely be 20% off, depending on the correlator configuration and other variables. Additionally, if no online channel averaging was done during the observation, adjacent spectral channels will be highly correlated due to the lag-domain smoothing which is *always* done by the correlator prior to computing the channelized spectra. This lag-domain -- e.g. Hanning -- smoothing is very common for FX correlators such as the ALMA "Baseline" (12-m array) correlator and serves to reduce spectral ringing due to the finite number of lags measured. An easy way to deal with the channel-to-channel correlations produced by Hanning smoothing is to spectrally average your data by a factor of N >> 2, giving visibilities which are close to statistically independent. Please note also that if you are working with manually calibrated data, or data from a telescope other than ALMA, the specific details of the online smoothing and absolute accuracy of the weights may be different, and you will need to understand them to trust the absolute weights if you cannot reliably estimate them from the data or fit yourself.