-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WL data processing requirements for DC2 validation #340
Comments
The inclusion of bands with poorly determined PSFs is an ongoing issue we are dealing with in DES. It is probable that ultimately we will treat g separately. However, the shear-dependent detection effects will dominate for these DC2 runs. I propose that for DC2 we just keep it simple and do |
For the record, current setup, straight from the package example files, is |
Just to link the two together, the decision we make here should answer LSSTDESC/ImageProcessingPipelines#108 |
@joezuntz gave a very nice overview today at the 3x2pt telecon of the impact of using 3 (r,i,z) or 4 (g,r,i,z) bands in metacal for photometric binning. To summarize the discussion:
At the end of the discussion, @esheldon recommended using the g-band for now in DC2. |
@fjaviersanchez @nsevilla Can you take a look at this please and see if you want to track it as part of the SRV group activities? Thanks! |
I'm opening this thread to document the WL working group needs in terms of data products for DC2 validation, and ultimately for DC2 science-ready data products. This will serve as an input to the DM-DC2 and Data Access task force.
The discussion in particular has been on which bands to run through metacal, how to pipe the metacal photometry to the photo-z pipeline, and what area do we need for robust validation.
Thanks to Heather we now have a confluence page where these requirements can be written down:
https://confluence.slac.stanford.edu/display/LSSTDESC/WL+requirements
Pinging some relevant people @joezuntz @esheldon @johannct @heather999
The text was updated successfully, but these errors were encountered: