This will involve the updating and review of two sets of notebooks (one set of each of the below for the AGN systems and SNe systems respectively).
1. Adding properties to the strongly lensed catalogs
The catalogs of strongly lensed AGN and strongly lensed SNe do not have Stellar Mass, Radius values, or SEDs for the lens galaxies. As a result we created a notebook to add these properties to the lensed catalogs. A fit for stellar masses is derived from empirical data and then used on the OM10/SNe catalogs to assign stellar mass values to the lens galaxies. Then this stellar mass along with the redshift and ellipticity of the lens galaxy is used to match to an extragalactic catalog object and the SED and radius of this object are added to the lens galaxy.
2. Matching lensed systems to the extragalactic catalog in the uDDF field
This notebook will match galaxies in the uDDF field to lensed systems that will be sprinkled. The galaxy ids will then be cached by the notebook so that when creating instance catalogs they can just be looked up and replaced by sprinkled systems in production.
This will involve the updating and review of two sets of notebooks (one set of each of the below for the AGN systems and SNe systems respectively).
1. Adding properties to the strongly lensed catalogs
The catalogs of strongly lensed AGN and strongly lensed SNe do not have Stellar Mass, Radius values, or SEDs for the lens galaxies. As a result we created a notebook to add these properties to the lensed catalogs. A fit for stellar masses is derived from empirical data and then used on the OM10/SNe catalogs to assign stellar mass values to the lens galaxies. Then this stellar mass along with the redshift and ellipticity of the lens galaxy is used to match to an extragalactic catalog object and the SED and radius of this object are added to the lens galaxy.
2. Matching lensed systems to the extragalactic catalog in the uDDF field
This notebook will match galaxies in the uDDF field to lensed systems that will be sprinkled. The
galaxy ids
will then be cached by the notebook so that when creating instance catalogs they can just be looked up and replaced by sprinkled systems in production.