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

p_any cutoff #23

Open
satishastro opened this issue Sep 16, 2023 · 1 comment
Open

p_any cutoff #23

satishastro opened this issue Sep 16, 2023 · 1 comment

Comments

@satishastro
Copy link

Q. The value of the p_any cutoff, calculated in the following manner, can be used again to improve the best match or just to report in a paper to show the percentage of false detections.

You can calibrate a p_any cut-off with the following steps:

  1. Create a offset catalogue to simulate random sky positions:
    nway-create-fake-catalogue.py --radius 40 COSMOS_XMM.fits COSMOS_XMM-fake.fits
  2. Match the offset catalogue in the same way as this run:
    ../nway.py COSMOS_XMM-fake.fits :pos_err COSMOS_OPTICAL.fits 0.1 --out=examplenway.fits-fake.fits --radius 20 --prior-completeness 0.9
  3. determining the p_any cutoff that corresponds to a false-detection rate
    nway-calibrate-cutoff.py examplenway.fits examplenway.fits-fake.fits
@JohannesBuchner
Copy link
Owner

That is true; I guess it should be stated clearer in the manual?

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

No branches or pull requests

2 participants