Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-634

Add Gaia DR2 catalog to lsst-dev:/datasets/refcats

    Details

      Description

      I have generated a Gaia DR2 HTM-style reference catalog (DM-20741) and tested that we can use it to fit astrometry (DM-20756, though we will likely need to change our configuration to deal with the higher accuracy and magnitude limits). I am requesting that we add this reference catalog to /datasets/refcats/htm/v1 as gaia_dr2.

      As part of adding the catalog, I will add a readme to /datasets/refcats/htm (we should have had one before!) describing the contents of this new refcat (DM-20267) per policy .

      I also propose that the symlink /datasets/refcats/htm/htm_baseline/gaia be changed to point to this DR2 version, from the DR1 version.

        Attachments

          Issue Links

            Activity

            Hide
            hchiang2 Hsin-Fang Chiang added a comment -

            If I understand correctly (but Michelle Butler should correct me) Felipe Menanteau is taking over my previous role at NCSA, so for the NCSA assistance please keep Felipe Menanteau or whoever Michelle Butler assigns in the loop.

            Show
            hchiang2 Hsin-Fang Chiang added a comment - If I understand correctly (but Michelle Butler should correct me) Felipe Menanteau is taking over my previous role at NCSA, so for the NCSA assistance please keep Felipe Menanteau or whoever Michelle Butler assigns in the loop.
            Hide
            price Paul Price added a comment -

            I suggest including a version string to the catalog's directory name (for the PS1 catalog, I used the date of the catalog construction). This is because you may construct a new Gaia DR2 catalog with improved features in the future, and a version string will allow for disambiguation.

            I also suggest that a detailed README go in the Gaia DR2 catalog directory, explaining how the catalog was constructed (original source, what was done to manipulate it, what papers to cite, who to contact with questions, etc), along with any code or configuration that was used.

            Show
            price Paul Price added a comment - I suggest including a version string to the catalog's directory name (for the PS1 catalog, I used the date of the catalog construction). This is because you may construct a new Gaia DR2 catalog with improved features in the future, and a version string will allow for disambiguation. I also suggest that a detailed README go in the Gaia DR2 catalog directory, explaining how the catalog was constructed (original source, what was done to manipulate it, what papers to cite, who to contact with questions, etc), along with any code or configuration that was used.
            Hide
            Parejkoj John Parejko added a comment -

            Version string is a good idea. So, the directory for the refcat would be gaia_dr2_20190808.

            We have a policy of where the readme should go and what should be in it:

            https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance

            Given the number of files in each refcat, you can't easily ls them to see what's in them. Keeping all the readme info at the top level seems like the best solution, as described in the link above (note: we don't have any readme info for any refcats right now!).

            Show
            Parejkoj John Parejko added a comment - Version string is a good idea. So, the directory for the refcat would be gaia_dr2_20190808 . We have a policy of where the readme should go and what should be in it: https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance Given the number of files in each refcat, you can't easily ls them to see what's in them. Keeping all the readme info at the top level seems like the best solution, as described in the link above (note: we don't have any readme info for any refcats right now!).
            Hide
            Parejkoj John Parejko added a comment - - edited

            Adopting with the versioned directory as written.

            Implementation tickets are: DM-21782 and DM-20267

            Show
            Parejkoj John Parejko added a comment - - edited Adopting with the versioned directory as written. Implementation tickets are: DM-21782 and DM-20267

              People

              • Assignee:
                Parejkoj John Parejko
                Reporter:
                Parejkoj John Parejko
                Watchers:
                Felipe Menanteau, Hsin-Fang Chiang, John Parejko, John Swinbank, Michelle Butler, Paul Price, Tim Jenness, Yusra AlSayyad
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Planned End:

                  Summary Panel