Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-23033

Updates to reference catalog creation documentation

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      1
    • Epic Link:
    • Sprint:
      AP S20-2 (January)
    • Team:
      Alert Production

      Description

      We have some very nice documentation at https://pipelines.lsst.io/modules/lsst.meas.algorithms/creating-a-reference-catalog.html on how to create a reference catalog.

      However, in an effort to make it easy for the user to ingest catalogs spread over multiple files, this page seems to rather bury the lead — which is that the user just needs to run `IngestIndexedReferenceTask` with an appropriate configuration.

      This has caused some confusion. Please update the docs to make clear exactly what's happening.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          swinbank John Swinbank added a comment -

          Hi John,

          Could you take a quick look at https://github.com/lsst/meas_algorithms/pull/186 please?

          If you are happy with it, I will put a comment on the CLO post at https://community.lsst.org/t/creating-and-using-new-style-reference-catalogs/1523 referring to this page.

          Show
          swinbank John Swinbank added a comment - Hi John, Could you take a quick look at https://github.com/lsst/meas_algorithms/pull/186 please? If you are happy with it, I will put a comment on the CLO post at https://community.lsst.org/t/creating-and-using-new-style-reference-catalogs/1523 referring to this page.
          Hide
          Permalink
          Parejkoj John Parejko added a comment -

          Thanks for these updates.

          My only concern is that you do a local docs build to ensure the output looks right: per #dm-docs, docs only changes don't trigger CI.

          Show
          Parejkoj John Parejko added a comment - Thanks for these updates. My only concern is that you do a local docs build to ensure the output looks right: per #dm-docs, docs only changes don't trigger CI.

            People

            Assignee:
            swinbank John Swinbank
            Reporter:
            swinbank John Swinbank
            Reviewers:
            John Parejko
            Watchers:
            John Parejko, John Swinbank
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.