DR1 survey completness data

Question

Hi,

I am having trouble finding the completeness maps for DR1 for each of the bright, dark, and backup programs (as shown in Fig 3. of the DR1 release paper). Are they publicly available anywhere?

Cheers,

Dave

Answer 1

Caveat: It's a bit tricky to define "completeness" for a spectroscopic survey with a bunch of points measured, e.g. are you "complete" in the unobserved area between the points? It becomes a resolution-dependent question.

But you can see how we made those figures and get accompanying data files at that resolution at https://github.com/desihub/dr1paper/tree/main/zenodo .  That uses healpix nside=128 nest=False, which corresponds to a resolution of 0.21 deg^2.

If that doesn't meet your needs, please post additional details and we can followup.  E.g. for detailed DESI analyses we use a set of randoms that can be used to sample what is "in" or "out" of the footprint, but there are additional issues like whether you count a point that could have been observed in DR1 but wasn't because the fiber was placed on a different nearby object. 

Comments

Thanks for pointing me to that link, that would be sufficient for my needs which is really just as a visualization tool alongside my own sample.

While I was able to plot the DR1 completeness, it would be nice to also have the overall boundaries. In the progressplot code under bin, it makes use of a function plot_desi_bounds which relies on a file desi-boundaries.ecsv. I wasnt able to find this file available anywhere.  The public footprint files available at https://desimodel.readthedocs.io/en/latest/footprint.html seems to just be the boundaries of the bright/dark program and don't include the extended boundaries of the backup program.

Is there a way for me to obtain desi-boundaries.ecsv?

Thanks again,

Dave

---

Whoops, desi-boundaries.ecsv was indeed missing.  We just added it to https://github.com/desihub/dr1paper/tree/main/bin (for pragmatic reasons it is in the bin/ directory with the script that reads it, not in the zenodo/ directory).

---

Perfect, thanks for the help!