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

Update ap_verify refcats

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ap_verify
    • Labels:
    • Story Points:
      4
    • Sprint:
      AP F23-1 (June), AP F23-2 (July)
    • Team:
      Alert Production
    • Urgent?:
      No

      Description

      A deprecation warning in ap_verify suggests that we need to update the refcats that are in the ci data packages:

      lsst.calibrate WARNING: Found version 0 reference catalog with old style units in schema.
      lsst.calibrate WARNING: run `meas_algorithms/bin/convert_refcat_to_nJy.py` to convert fluxes to nJy.
      lsst.calibrate WARNING: See RFC-575 for more details.
      py.warnings WARNING: /Users/sullivan/LSST/code/eups_distrib/stack/miniconda3-py38_4.9.2-6.0.0/DarwinX86/meas_algorithms/gb4bc36e013+10ac321cda/python/lsst/meas/algorithms/loadReferenceObjects.py:808: FutureWarning: Call to deprecated function (or staticmethod) convertToNanojansky. (Support for version 0 refcats (pre-nJy fluxes) will be removed after v25.) -- Deprecated since version v24.0.
        refCat = convertToNanojansky(refCat, self.log)
      

      This particular run was using ap_verify_ci_hits2015, but I suspect all of our CI datasets have the same problem.

        Attachments

          Issue Links

            Activity

            Hide
            Parejkoj John Parejko added a comment -

            On DM-19184 Krzysztof Findeisen said that this had already been done, and checking my own copies of ci_hits2015 and ci_cosmos_pdr2, I see version=1 in the metadata. Are you sure you were working with an updated copy of the ci datasets when you got the warning?

            Show
            Parejkoj John Parejko added a comment - On DM-19184 Krzysztof Findeisen said that this had already been done, and checking my own copies of ci_hits2015 and ci_cosmos_pdr2, I see version=1 in the metadata. Are you sure you were working with an updated copy of the ci datasets when you got the warning?
            Hide
            Parejkoj John Parejko added a comment -

            If ap_verify does run with the the latest daily or weekly, then this ticket can be closed as "Invalid".

            Show
            Parejkoj John Parejko added a comment - If ap_verify does run with the the latest daily or weekly, then this ticket can be closed as "Invalid".
            Hide
            krzys Krzysztof Findeisen added a comment -

            https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Fap_verify/detail/ap_verify/1781 executes the pipeline graph with no failures, but then fails on Sasquatch upload. It's assumed this will be fixed once USDF is fully operational.

            Show
            krzys Krzysztof Findeisen added a comment - https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Fap_verify/detail/ap_verify/1781 executes the pipeline graph with no failures, but then fails on Sasquatch upload. It's assumed this will be fixed once USDF is fully operational.
            Hide
            krzys Krzysztof Findeisen added a comment -

            ap_verify ran this morning with no errors.

            Show
            krzys Krzysztof Findeisen added a comment - ap_verify ran this morning with no errors.

              People

              Assignee:
              Parejkoj John Parejko
              Reporter:
              sullivan Ian Sullivan
              Watchers:
              Eric Bellm, Ian Sullivan, John Parejko, Krzysztof Findeisen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.