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

Science metrics for photo-z PDF approximation performance assessment #50

Closed
aimalz opened this issue Mar 17, 2017 · 8 comments
Closed

Comments

@aimalz
Copy link
Owner

aimalz commented Mar 17, 2017

Re: conversation with @drphilmarshall today, it's time to give #36 some context. In order to make #39 submittable to a journal, we'll need to perform an end-to-end test on a science case, and it would be appropriate for it to answer the question that inspired qp to be written: "What is the best way to store photo-z PDFs?" @janewman-pitt-edu, we are thinking of the simplest scientifically relevant end product to which inaccuracy in PDF representation could be propagated. n(z) seems like an obvious choice, but I think this application would be best approached after CHIPPR is submitted. Thoughts?

@aimalz aimalz added this to the Mock Photo-z Test milestone Mar 17, 2017
@aimalz aimalz self-assigned this Mar 17, 2017
@janewman-pitt-edu
Copy link

janewman-pitt-edu commented Mar 17, 2017

n(z) may not be ideal as you could have small storage errors that all average to zero and leave n(z) untouched. You thus may want to focus more on applications where individual object p(z)'s matter. Examples include cluster finding, intrinsic alignment mitigation in weak lensing, and strong lensing analyses. Of course Phil is an expert on the latter...

@drphilmarshall
Copy link
Collaborator

I think the strong lensing environment requirements will be similar to those of cosmic shear, and be (more or less) that the n(z) comes out accurately. One cheap alternative to checking the hierarchical inference of n(z) is to use the "stacked p(z)" approximation, just to quantify how n(z) estimation accuracy depends on p(z) approximation.

I like the idea of checking some alternatives to n(z) on scientific grounds. Alex, let's talk to Eli Rykoff today about the cluster-finding application, and we can ask around on Slack for input on the IA application. On the galaxies side, are there uses for p(z)'s that suggest particular combinations of them? Thanks Jeff!

@drphilmarshall
Copy link
Collaborator

Reports from Slack:

"In the simplest scenario, we're interested in the global n(z) of a given sample (e.g. a photo-z redshift bin for a particular population), but ideally including the possible uncertainties on that n(z). It would be great to understand whether the latter can be provided and if so, in what format.
This is for the simplest analysis scenario we're envisaging right now, but other options might need individual p(z)'s."

  • Michael Troxel @matroxel suggested we look at the mean inverse lensing sigma_crit, between pairs of redshift bins (and pointed to the test code he is using in DES here as a guide). He says:

Averaging sigma crit of individual pairs in two bins [tells] you something different [from n(z)].
You can produce sufficient signal to noise to directly measure the inferred bias without rescaling your covariance. We did both [this and the n(z) test] in the DES SV photo-z paper."

Thanks both! We'll look into these.

@aimalz aimalz changed the title Science case Science metrics for photo-z PDF approximation performance assessment Mar 17, 2017
@janewman-pitt-edu
Copy link

For strong lensing, I thought you'd be interested in basically making a foreground mass map, which would require p(mass, z) for each potential foreground object?

For galaxies science I think there are few applications that would ever need very high precision, I'd look towards cosmology instead.

@drphilmarshall
Copy link
Collaborator

drphilmarshall commented Mar 20, 2017 via email

@aimalz
Copy link
Owner Author

aimalz commented Jul 21, 2017

@drphilmarshall Are we still thinking of including metrics on Sigma_crit^-1? I think it's nontrivial to calculate without point estimators of redshift and don't want to muddy the waters with straying too many layers beyond the PDFs -- wouldn't this involve calculating metrics on quantities derived from point estimators derived from PDFs?

@drphilmarshall
Copy link
Collaborator

drphilmarshall commented Jul 23, 2017 via email

@aimalz
Copy link
Owner Author

aimalz commented Aug 17, 2017

I'm closing this along with #57 now that #54 is done.

@aimalz aimalz closed this as completed Aug 17, 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