|
1 | 1 | \subsubsection{Basic usage} |
2 | 2 |
|
3 | | -These two tools can be used to create the images corresponding to a given mock catalog created by \bashinline{egg-gencat}. They provide a simple alternative to \skymaker, with the added limitation that galaxies are all considered as point sources. This is usually fine for long wavelength images (\spitzer MIPS and \herschel, typically) in cosmological deep fields. In addition, more control is given relative to the noise properties. |
| 3 | +These two tools can be used to create the images corresponding to a given mock catalog created by \bashinline{egg-gencat} (custom catalogs are also supported, see below). They provide a simple alternative to \skymaker, with the added limitation that galaxies are all considered as point sources. This is usually fine for long wavelength images (\spitzer MIPS and \herschel, typically) in cosmological deep fields. In addition, more control is given relative to the noise properties. |
4 | 4 |
|
5 | 5 | The typical call sequence consists of two steps: creating the noise map with \bashinline{egg-gennoise}, then painting the galaxies on top of it with \bashinline{egg-genmap}. The standard way to use \bashinline{egg-gennoise} is the following: |
6 | 6 | \begin{bashcode} |
@@ -31,7 +31,7 @@ \subsubsection{Basic usage} |
31 | 31 |
|
32 | 32 | \subsubsection{Using a custom astrometry and image dimensions} |
33 | 33 |
|
34 | | -The tool \bashinline{egg-gennoise} can compute automatically a suitable astrometry and image dimensions according the input catalog. However, you also have the possibility to copy the astrometry and image properties of an existing file. To do so, just use the \bashinline{astro} command line argument and make it point to the FITS image you want to copy the data from: |
| 34 | +The tool \bashinline{egg-gennoise} can compute automatically a suitable astrometry and image dimensions according to the input catalog. However, you also have the possibility to copy the astrometry and image dimensions of an existing file. To do so, just use the \bashinline{astro} command line argument and make it point to the FITS image you want to copy the data from: |
35 | 35 | \begin{bashcode} |
36 | 36 | egg-gennoise cat=egg-20151201.fits out=pacs160-noise.fits \ |
37 | 37 | psf=herschel-pacs160.fits rms=1.68e-5 verbose \ |
@@ -70,14 +70,16 @@ \subsubsection{Generate error and coverage maps} |
70 | 70 |
|
71 | 71 | \subsubsection{Using a custom noise map} |
72 | 72 |
|
73 | | -The whole point of separating the map-making process into two steps is that one can be used without the other. Indeed, \bashinline{egg-genmap} can work with noise map, provided that it contains valid WCS astrometry. The tool can handle sources outside of the map, so it is fine if the provided noise map does not overlap perfectly with the input catalog. Just make sure that the PSF you provide is tabulated on the same pixel scale as your noise map. If you use the \bashinline{beam_smoothed} option, note that the noise map must be provided \emph{unfiltered} (i.e., before beam convolution). |
| 73 | +The whole point of separating the map-making process into two steps is that one can be used without the other. Indeed, \bashinline{egg-genmap} can work with any noise map, provided that it contains valid WCS astrometry. The tool can handle sources outside of the map, so it is fine if the provided noise map does not overlap perfectly with the input catalog. Just make sure that the PSF you provide is tabulated on the same pixel scale as your noise map. If you use the \bashinline{beam_smoothed} option, note that the noise map must be provided \emph{unfiltered} (i.e., before beam convolution). |
74 | 74 |
|
75 | 75 | For example, realistic \herschel noise maps can be obtained by jackknifing the observed data, and provide noise statistics (correlation, amplitude, etc.) that match very well the real images. Such kind of map can be fed naturally to \bashinline{egg-genmap} through the \bashinline{noise_map} argument. |
76 | 76 |
|
77 | 77 |
|
78 | 78 | \subsubsection{Using a custom flux catalog} |
79 | 79 |
|
80 | | -Similarly, both tools can work with input catalogs that were not produced by \bashinline{egg-gencat}. They only need a limited set of columns: \cppinline{"ra"} and \cppinline{"dec"} to know the position of each galaxy on the sky, and \cppinline{"flux"} and \cppinline{"bands"} to know their flux. The format of these columns must be the same as that created by \bashinline{egg-gencat}, but this can be easily achieved in any language. Alternatively, the program can also work with a \cppinline{"flux"} column containing a single band (i.e., a 1D vector column), in which case the \cppinline{"bands"} column and the \bashinline{band} command line argument are useless and can be omitted. |
| 80 | +Similarly, both tools can work with input catalogs that were not produced by \bashinline{egg-gencat}. They only need a limited set of columns: \cppinline{"ra"} and \cppinline{"dec"} to know the position of each galaxy on the sky, and \cppinline{"flux"} must contain the flux of each galaxy in $\uJy$. |
| 81 | +
|
| 82 | +Catalogs produced by \bashinline{egg-gencat} contain multiple fluxes per galaxy, so in this case you also need the \cppinline{"bands"} column and the \bashinline{band} command line argument to identify the correct flux. Alternatively, the program can also work with a \cppinline{"flux"} column containing a single band (i.e., a 1D vector column), in which case the \cppinline{"bands"} column and the \bashinline{band} command line argument can be omitted. If you prefer to use ASCII format, the order of the columns must be \cppinline{"ra"}, \cppinline{"dec"} and \cppinline{"flux"} (1D only). |
81 | 83 |
|
82 | 84 |
|
83 | 85 | \subsubsection{Adjusting accuracy and speed} |
|
0 commit comments