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

Add config to pipelines that points to jointcal WCS (where needed)

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: DM Subsystem Science
    • Labels:
      None

      Description

      Simon is changing the default WCS template to calexp.wcs in faro. For most of our pipelines we'd prefer to use the jointcal WCS by default because it is always guaranteed to exist (unlike FGCM). Update the relevant pipelines' configs to use jointcal.

        Attachments

          Activity

          Hide
          jcarlin Jeffrey Carlin added a comment - - edited

          This snippet shows that the `calexp` is now the default calibration:

          // 
          class MatchedBaseTaskConnections(pipeBase.PipelineTaskConnections,
                                           dimensions=(),
                                           defaultTemplates={"coaddName": "deep",
                                                             "photoCalibName": "calexp.photoCalib",
                                                             "wcsName": "calexp.wcs"}): 

          Show
          jcarlin Jeffrey Carlin added a comment - - edited This snippet shows that the `calexp` is now the default calibration: // class MatchedBaseTaskConnections(pipeBase.PipelineTaskConnections,                                  dimensions=(),                                  defaultTemplates={ "coaddName" : "deep" ,                                                    "photoCalibName" : "calexp.photoCalib" ,                                                    "wcsName" : "calexp.wcs" }): 
          Hide
          jcarlin Jeffrey Carlin added a comment -

          I think that the only place this change needed to be made was in `pipelines/preparation/preparation_matched.yaml` and `preparation_matched_multi.yaml`. 

          Note that there was some naming inconsistency. The subtasks were called `matchCatalogsPatch` and `matchCatalogsTract` in the single-band case, and `matchCatalogPatchMultiBand` (singular) for the multi-band case. I changed the multi-band name to the plural to match the others.

          Show
          jcarlin Jeffrey Carlin added a comment - I think that the only place this change needed to be made was in `pipelines/preparation/preparation_matched.yaml` and `preparation_matched_multi.yaml`.  Note that there was some naming inconsistency. The subtasks were called `matchCatalogsPatch` and `matchCatalogsTract` in the single-band case, and `matchCatalogPatchMultiBand` (singular) for the multi-band case. I changed the multi-band name to the plural to match the others.
          Hide
          krughoff Simon Krughoff added a comment -

          Reviewed

          Show
          krughoff Simon Krughoff added a comment - Reviewed

            People

            Assignee:
            jcarlin Jeffrey Carlin
            Reporter:
            jcarlin Jeffrey Carlin
            Reviewers:
            Simon Krughoff
            Watchers:
            Jeffrey Carlin, Simon Krughoff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: