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

Deblending metric #532

Open
jmeyers314 opened this issue Aug 19, 2016 · 2 comments
Open

Deblending metric #532

jmeyers314 opened this issue Aug 19, 2016 · 2 comments
Assignees

Comments

@jmeyers314
Copy link
Contributor

The distribution of the best seeing will affect our ability to deblend objects. To start to probe this, @pmelchior and I looked at the spatial distribution of the best seeing. For example, here's a figure showing the 10th percentile best seeing in the i-band over the wide-fast-deep footprint.

minion_1016_10th ile_fwhmgeom_propid_54_and_r_heal_skymap

It appears that our ability to identify blends may vary considerably over the survey footprint.

@drphilmarshall
Copy link
Contributor

Very interesting. Great stuff! @pmelchior https://github.com/pmelchior would
you be interesting in adding a few words as well as this figure to the WL
science case in the white paper? I think it belongs there, since in the end
both the rotational dithering and the best seeing stacks will affect the WL
figure of merit, whose proxy is likely to be some sort of shear systematic
statistic I guess. If you are up for this, please do start a pull request
and let me know when you think you might be ready for it to be merged.
This could be one for version 2 of the paper, for example.

@pmelchior
Copy link

@drphilmarshall: I can add an explanation to why the seeing variation matters. It's not just the effective depth, which changes the statistics budget, but the shear calibrations depend strongly on seeing. The more homogenous the observed seeing is, the easier it will be to apply accurate calibrations (from deeper reference fields or simulations) to the observations.

What's the timescale for version 2?

@drphilmarshall drphilmarshall modified the milestone: Version 2 Development Mar 15, 2017
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

3 participants