You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the redshift distribution test, N(z), only goes to z = 1. We should extend the redshift range to z = 3 to make sure things look reasonable beyond z > 1. This is particular important for cosmoDC2.
The validation data is valid in the redshift range up to around z = 1.5, so we can plot the redshift range to z = 3, but don't use the data beyond z = 1.5 to calculate the chi^2.
Here's is a DESCQA run with simply modifying the N(z) test config file to increase the redshift range to z=3. Things look good.
Now we need to modify the code to allow setting a different validation range. I'll be developing this in the issue/138/extend-redshift-dist-test branch.
Could we add a single panel for a deeper sample without any validation data, just for the basic sanity check that there are no extremely strange features? (I mean right now each section has 3 panels with a blank space, so could the blank space have everything down to i<25.3 without a validation dataset shown?) Or has a basic sanity check of the overall N(z) for a deeper sample already been done in another context?
@rmandelb@yymao The readiness test plots the basic distribution, as shown in this issue. The N(z) test does have the option of plotting distributions with no validation data. We just have to make a configuration file for it.
Currently the redshift distribution test, N(z), only goes to z = 1. We should extend the redshift range to z = 3 to make sure things look reasonable beyond z > 1. This is particular important for cosmoDC2.
The validation data is valid in the redshift range up to around z = 1.5, so we can plot the redshift range to z = 3, but don't use the data beyond z = 1.5 to calculate the chi^2.
cc @evevkovacs @rmandelb
The text was updated successfully, but these errors were encountered: