Complex pointingtable: Difference between revisions

From CASA Guides
Jump to navigationJump to search
mNo edit summary
No edit summary
Line 8: Line 8:
<source lang="python">
<source lang="python">
default "sim_observe"
default "sim_observe"
project          =  "m51p"
# Model sky = Halpha image of M51  
# Model sky = Halpha image of M51  
skymodel        =  "m51ha.fits.txt"
skymodel        =  "m51ha.fits.txt"

Revision as of 12:21, 3 November 2011

simdata and sim_observe can either generate mosaic pointing directions, or you can manually create a list.

Then the directions are calculated for you, you are restricted to having the dwell time at each point in the mosaic be equal to the integration time parameter, i.e. the simulated ms will only have one timestamp per pointing or scan. This is not how real telescopes work, but simplifies the number of input parameters. If you want to do more complex things, for example 6s integrations in 5 min scans, or different integration times on different mosaic pointings, or a calibrator with a shorter integration time than the science pointings, the recommended method is to use sim_observe to generate a simple pointing file (which is just an ascii file) and then edit it.

We'll begin with sim_observe, and use an Halpha image of M51 as a model, which you should download File:M51ha.fits.txt and place in your working directory.

sim_observe will make a copy m51c/m51c.skymodel, and not modify your input image.

default "sim_observe"
project          =  "m51p"
# Model sky = Halpha image of M51 
skymodel         =  "m51ha.fits.txt"

Although the image has a world coordinate system, we want to override most of the parameters.

  • We'll place the source in the southern hemisphere with the indirection parameter,
  • set the pixel size to 0.1arcsec, effectively moving the galaxy further away (M51 itself would require a quite large mosaic, and in any case we need for the input model pixels to be significantly smaller than the synthesized beam that we'll be simulating, or else we won't be learning anything)
  • consistent with simulating a more distant source, we'll set the peak brightness to 0.004 Jy/pixel
  • set the frequency to 330GHz, and since its a 2D image we'll set the single "channel" width to be 50MHz, and peak brightness of 0.004 Jy/pixel - parameters plausible for observing an emission line in a galaxy.
# Set model image parameters:
indirection="B1950 23h59m59.96s -34d59m59.50s"

We'll begin with the 12m ALMA array observation, and have sim_observe calculate a hexagonal mosaic of pointings. We'll set the integration time to 2min, since that's what we'll want for our scan duration or dwell time (if you ran observe with this parameter, as described above, you'd get one measurement every two minutes which would not result in realistic uv coverage).

We want to intersperse a calibrator observation after each pass of the mosaic, using caldirection and calflux

# have sim_observe calculate mosaic pointing locations:
setpointings       =  True
integration        =  "2min"
mapsize            =  "1arcmin"
maptype            =  "hex"
pointingspacing    =  "9arcsec"      # this could also be specified in units of the primary beam e.g. "0.5PB"
caldirection       =  "J2000 22h12m32s -30d10m04s"
calflux            =  "0.9Jy"

Note that we're turning observe=False - we don't want to actually do the calculation (yet).

observe            =  False
graphics           =  "both"