Skip to content
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

Open
EiffL opened this issue May 10, 2019 · 5 comments
Open

WL data processing requirements for DC2 validation #340

EiffL opened this issue May 10, 2019 · 5 comments

Comments

@EiffL
Copy link
Member

EiffL commented May 10, 2019

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

@esheldon
Copy link

esheldon commented May 13, 2019

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 griz all together, assuming that any biases will be sub-dominant.

@johannct
Copy link
Contributor

johannct commented May 13, 2019

For the record, current setup, straight from the package example files, is riz

@EiffL
Copy link
Member Author

EiffL commented Jun 6, 2019

Just to link the two together, the decision we make here should answer LSSTDESC/ImageProcessingPipelines#108

@EiffL
Copy link
Member Author

EiffL commented Jun 6, 2019

@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:

  • We need metacal photometry simply for the purpose of putting galaxies into photo-z bins, this can be done with any number of approaches (like BTDs, or SOMs) and does not necessarily require the main Photoz pipeline to be ran on this metacal catalog.

  • When including the photometry from the g band, Joe gets much cleaner bins
    image
    (Fraction of objects placed in the correct photo-z bins)
    which in turn translates into much better FoM:
    image
    So, it makes it very likely we want to have the 4 bands for that purpose

  • Now, the issue is that adding the g band may degrade the quality of the shape measurement, in particular we don't know how well the PSF is modeled in the g band.

At the end of the discussion, @esheldon recommended using the g-band for now in DC2.

@katrinheitmann
Copy link
Contributor

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants