Difference between revisions of "N891 simdata2"

From CASA Guides
(Created page with '== Nearby edge-on spiral == Roughly modeled after NGC891 {{Under Construction}} - mostly correct, but probably not very thoroughly explained. * model origin: Milky Way 13CO fro…')
 
(Nearby edge-on spiral)
Line 38: Line 38:
 
Sample results:
 
Sample results:
 
{| style="border:1px solid #3366FF; " cellspacing=2
 
{| style="border:1px solid #3366FF; " cellspacing=2
|Input:<br> [[File:N891.skymodel.png|300px]]
+
|Input:<br> [[File:N891d.skymodel.png|300px]]
|Predict:<br> [[File:N891.predict.png|300px]]
+
|Predict:<br> [[File:N891d.predict.png|300px]]
 
|-
 
|-
|Image:<br> [[File:N891.image.png|300px]]
+
|Image:<br> [[File:N891d.image.png|300px]]
|Analyze:<br> [[File:N891.analysis.png|300px]]
+
|Analyze:<br> [[File:N891d.analysis.png|300px]]
 
|}
 
|}

Revision as of 11:53, 24 May 2010

Nearby edge-on spiral

Roughly modeled after NGC891

This article is under construction. Watch this space!

- mostly correct, but probably not very thoroughly explained.

  • I binned the cube to coarser velocity resolution in order to speed the simulation. the fits file is [1]


  • units: K - first convert to flux surface brightness

Jy/Sr = 2x1023 k T / λ2, = 4x108T at 110GHz.

now we need to decide if this model data will work at the desired pixel scale

  • the GRS resolution of 40" at ~10kpc is 0.04" at 10Mpc, so we should be able to do a simulation of observing at ~0.1-0.2". The resolution plot (Beamsummary.png) indicates that for ALMA at 100GHz, configuration 20 is appropriate.
  • if we intend to set cell=0.04arcsec in simdata2, then the cube needs to be multiplied by

4x108 * (.04/206265)2 = 1.4x10-5 to obtain Jy/pixel. The cube peaks at ~20K, so we can perform the simulation with inbright=3e-4, which should yield a peak of ~1mJy/bm.

will we be dominated by the noise in the input model?

  • input noise ~150mK or S/N~20, so at our scaled intensity, ~0.05 mJy/bm. The exposure time calculator says that ALMA will achieve 2.5mJy/bm in 2 hours for the input 212m/s channel width (0.075MHz), so the noise in the input model should not affect our results.
  • We do have a sensitivity issue though - if we decrease the spectral resolution by a factor of 6 (bin the input channels in some other program - simdata will know how to do that in the future but not yet), and plan for 3 8-hr tracks, then the sensitivity calculator suggests that we'll get <0.25mJy rms, or S/N>10 per beam. Rather than simulate 3 days of observing, I'll increase inbright by sqrt(3) and simulate one 8 hour track.

setup:

  • the ALMA 12m primary beam is 50" so we'd space a mosaic by 25", but the model cube has 326x357 pixels, or 13 arcsec with our small pixels. That's a lot smaller than the primary beam, so it doesn't matter much what output image size we ask for.
  • there are 659 channels in the input cube, but as noted above we want to bin those to 109 channels of 1.2 km/s each.

here're the simdata2 inputs : File:N891.simdata2.py

CASA <> execfile("n891.simdata2.py")
CASA <> go simdata2

here's the cube with the simdata's scaling and World Coordinate System: N891.coord.png
and a spectral profile in the box marked in green
N891.grs-24-cube.coord18-59-59.976-40d00m01.972.png

Sample results:

Input:
N891d.skymodel.png
Predict:
N891d.predict.png
Image:
N891d.image.png
Analyze:
N891d.analysis.png