M51 at z = 0.1: Difference between revisions

From CASA Guides
Jump to navigationJump to search
Line 53: Line 53:
</source>
</source>


[[simdata Simdata]] wants models in units of Jy / pixel, but the BIMA SONG cube is in units of Jy / beam. That's an easy conversion.
[[simdata|Simdata]] wants models in units of Jy / pixel, but the BIMA SONG cube is in units of Jy / beam. That's an easy conversion.


<source lang="python">
<source lang="python">

Revision as of 12:25, 29 April 2010


This article is under construction. Watch this space!

Overview

This tutorial presents a simulation of ALMA observations of a well-known galaxy, M51, as it would be observed at redshift z = 0.1.

The goal of this tutorial is to provide a complete run-through of a relatively simple simulation. Included in this simulation are the effects of (u, v) sampling of a 50-antenna ALMA, the primary beam of the ALMA antennas, and thermal noise levels appropriate for the ALMA site. Calibration overheads are not included, nor is phase noise owing to a varying troposphere. As such, this simulation should be viewed as somewhat optimistic.

For this tutorial, we'll use the BIMA SONG observations of M51 as the basis for the model. Grab the file NGC5194.bima12m.cm.fits.gz and uncompress it in a working directory.

# in bash (or other unix shell)
gunzip NGC5194.bima.12m.cm.fits

Load these data into CASA. For later convenience, we'll store the name of the resulting measurement set into the python global cubeName.

cubeName = 'm51-song'
importfits(fitsimage='NGC5194.bima12m.cm.fits', imagename=cubeName)

Cosmology Calculations

Next we'll set up some python globals to handle the scaling of the model coordinates and flux densities appropriate for new redshift. We'll primarily need the angular size and luminosity distances for a given cosmology. To keep things simple, we'll use Ned Wright's CosmoCalc with the default cosmology; redshifts are obtained from NED.

#z's 
z_old_cmb = 0.002122 # CMB-referenced z for cosmological distances
z_old_lsrk = 0.001544 # z_obs from BIMA header
z_new = 0.1

# angular size distances from CosmoCalc
da_old = 9.0
da_new = 375.9

# luminosity distances from CosmoCalc
dl_old = 8.937
dl_new = 454.8

The convention is "old" refers to M51 as observed at its proper redshift, and "new" refers to the new, higher redshift for our model.

Preparing the Model

The next step is to scale the M51 data cube into a model cube appropriate for simdata. First, we'll set up some globals to establish some file naming conventions.

suffix = "-p1" # z = 0.1, or point-1; useful to distinguish from repeated simulations at different z's
cubeOut = 'm51-atz' + suffix + '.im' # name for the model image (input to simdata)

Simdata wants models in units of Jy / pixel, but the BIMA SONG cube is in units of Jy / beam. That's an easy conversion.

# BIMA SONG beam -- could use imhead mode = 'get' to automate this step
bmaj = 5.82
bmin = 5.08 # note: BIMA SONG pixels = 1 arcsec, so this is the fwhm in pixels, too
toJyPerPix = 1.0 / (1.1331 * bmaj * bmin) # gaussian beam conversion = beams / pixel

We also need to calculate the flux scaling appropriate for the model's distance. We'll make the approximation that each pixel is a point source

Simdata

Results