Multiple Overlapping Obsids, Imaging

For this example, we assume that each obsid to be included in our final image has been reduced, as in the previous example, up to but not including combimage. (Not that there is a problem if you have run combimage, it just isn't used for the mosaics.) We assume that in you main analysis directory, that you have a subdirectory for each obsid. The “mosaic.list” file contains a listing of all the directories containing the data.

For the following example, the file mosaic.list contains the following lines:

/Users/kuntz/Data/xmm_m101/0104260101/analysis/base_image/mos1S001
/Users/kuntz/Data/xmm_m101/0104260101/analysis/base_image/mos2S006
/Users/kuntz/Data/xmm_m101/0104260101/analysis/base_image/pnS005
/Users/kuntz/Data/xmm_m101/0164560701/analysis/base_image/mos1S001
/Users/kuntz/Data/xmm_m101/0164560701/analysis/base_image/mos2S002
/Users/kuntz/Data/xmm_m101/0164560701/analysis/base_image/pnS003
/Users/kuntz/Data/xmm_m101/0212480201/analysis/base_image/mos1S001
/Users/kuntz/Data/xmm_m101/0212480201/analysis/base_image/mos2S002
/Users/kuntz/Data/xmm_m101/0212480201/analysis/base_image/pnS003

Note that this is not a directory listing, per se, but a listing of directories and the observing segments within them that should be combined into a mosaic. The contents of an individual 0104260101/analysis/base_image directory is (for example):

mos1S001-bkgimsky-350-1100.fits
mos1S001-cheeset.fits
mos1S001-expimsky-350-1100.fits
mos1S001-fovimsky-350-1100.fits
mos1S001-maskimsky-350-1100.fits
mos1S001-protimsky-350-1100.fits
mos1S001-swcximsky-350-1100.fits
mos2S006-bkgimsky-350-1100.fits
mos2S006-cheeset.fits
mos2S006-expimsky-350-1100.fits
mos2S006-fovimsky-350-1100.fits
mos2S006-maskimsky-350-1100.fits
mos2S006-protimsky-350-1100.fits
mos2S006-swcximsky-350-1100.fits
pnS005-bkgimsky-350-1100.fits
pnS005-cheeset.fits
pnS005-expimsky-350-1100.fits
pnS005-fovimootsky-350-1100.fits
pnS005-fovimsky-350-1100.fits
pnS005-maskimsky-350-1100.fits
pnS005-protimsky-350-1100.fits
pnS005-swcximsky-350-1100.fits

Now, it is quite possible to have other things within this directory, but these are the things that will get made into a mosaic. In particular, notice you could have the results of other observation segments in this directory, but they would not be included in the mosiac unless they are particularly listed in the “mosaic.list” file. Finally, here is a script for putting together a mosaic of M101.

setenv RAPNT 210.8
setenv DECPNT 54.32

#building the individual components of the mosaic

mosaicmerge dirfile=mosaic.list type=1 coordsys=2 crval1=$RAPNT crval2=$DECPNT
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

mosaicmerge dirfile=mosaic.list type=2 coordsys=2 crval1=$RAPNT crval2=$DECPNT
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

mosaicmerge dirfile=mosaic.list type=3 coordsys=2 crval1=$RAPNT crval2=$DECPNT 
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

mosaicmerge dirfile=mosaic.list type=4 coordsys=2 crval1=$RAPNT crval2=$DECPNT
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

mosaicmerge dirfile=mosaic.list type=5 coordsys=2 crval1=$RAPNT crval2=$DECPNT
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

mosaicmerge dirfile=mosaic.list type=6 coordsys=2 crval1=$RAPNT crval2=$DECPNT
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

mosaicmerge dirfile=mosaic.list type=7 coordsys=2 crval1=$RAPNT crval2=$DECPNT
   pixelsize=4.163999e-2 alpha=1.7 elow=350 ehigh=1100 withcheese=yes cheesemasktype='t'

#putting together the image with no smoothing or binning

binadaptmerge elowlist=350 ehighlist=1100 withpartbkg=yes withspbkg=true withswcxbkg=true 
   withmask=true maskfile=mosaic-cheeset.fits withbinning=false withsmoothing=false fill=0