Updated documentation

Author: cschreib

doc/EGG.pdf

@@ -136,6 +136,7 @@ \subsubsection{Reading and using the generated catalog}
 \item \cppinline{lir}: Infrared luminosity from $8$ to $1000\,\um$, in units of $\lsun$.
 \item \cppinline{tdust}: The average dust temperature, in Kelvins.
 \item \cppinline{mdust}: The total dust mass, in $\msun$ (note: not in logarithm...).
+\item \cppinline{ir8}: The ratio of IR to $8\,\um$ luminosity (Elbaz et al.~2011).
 \item \cppinline{fpah}: The fraction of the dust mass that is contributed by PAH molecules ($0$: no PAH, $1$: only PAH).
 \item \cppinline{ir_sed}: Index of the SED in the dust template library that was chosen for this galaxy. Corresponds to a given value of $\tdust$.
 \item \cppinline{bands}, \cppinline{lambda}: Arrays containing the names and reference wavelengths of each photometric band used to produce the observed fluxes. Wavelength is in $\um$.
@@ -157,7 +158,7 @@ \subsubsection{Choosing a seed}
 \subsubsection{Starting from your own galaxies}
 The first step of the program is to generate the galaxies, with their position on the sky, their redshift, their stellar mass, and their star-forming classification (i.e., each galaxy is either star-forming or quiescent according to the \uvj diagram). This is done using the stellar-mass functions that I observed in the GOODS--South field combined with observations in the Local Universe, and this should be fairly realistic between $z=0$ to $z=3$. However, the program also gives you the opportunity to provide these parameters yourself. You could, for example, provide a true (observed) catalog of galaxies, and let the program run its recipes to predict the fluxes of each object.
 
-To do so, you must first create an input catalog suitable for ingestion by \bashinline{egg-gencat}. The program accepts two file formats: either a column-oriented FITS table or a plain ASCII table. The ASCII file must contain $6$ columns in the following order: the ID of the galaxy, the RA and Dec position in degrees (double precision is advisable), the redshift, the base-$10$ logarithm of the stellar mass, and the quiescent flag (1: quiescent, 0: star-forming). The FITS file must contain at least the columns \cppinline{"ra"}, \cppinline{"dec"}, \cppinline{"z"}, \cppinline{"m"}, and \cppinline{"passive"} with the same content as for the ASCII table, and the column \cppinline{"id"} is optional (if you don't provide it, \bashinline{egg-gencat} will create an ID for you, starting from zero and increasing by one for each galaxy).
+To do so, you must first create an input catalog suitable for ingestion by \bashinline{egg-gencat}. The program accepts two file formats: either a column-oriented FITS table or a plain ASCII table. The ASCII file must contain $6$ columns in the following order: the ID of the galaxy, the RA and Dec position in degrees (double precision is advisable), the redshift, the base-$10$ logarithm of the stellar mass, and the quiescent flag (1: quiescent, 0: star-forming). The FITS file must contain at least the columns \cppinline{"ra"}, \cppinline{"dec"}, \cppinline{"z"}, \cppinline{"m"}, and \cppinline{"passive"} with the same content as for the ASCII table, and the column \cppinline{"id"} is optional (if you don't provide it, \bashinline{egg-gencat} will create an ID for you, starting from zero and increasing by one for each galaxy). Your input redshifts must be positive, and the stellar masses must be larger than $4$ and lower than $13$.
 
 I assume you know how to handle ASCII tables yourself. For tables in the FITS format, since column-oriented tables are not very well known, I give below a small example in three common languages.