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

Fix units formatting error in verify.job report

    XMLWordPrintable

Details

    • Bug
    • Status: Done
    • Resolution: Done
    • None
    • DM

    Description

      The ellipticity metrics (TE1, TE2) display values of "0.0" when shown in a lsst.verify.job.report (see example in [this notebook|https://github.com/lsst-dm/DMTR-201/blob/tickets/DM-22457/executions/KPMs/test_KPMs_validate_drp.ipynb]). These values are typically around 1e-6 or 1e-5, so this is just a formatting issue that causes them to display incorrectly (they are indeed usually showing values ~1e-6). 

      Attachments

        Activity

          Setting to "won't fix" because these reporting tools are no longer in regular use. (A replacement task, `print_metricvalues`, is more useful now.)

          jcarlin Jeffrey Carlin added a comment - Setting to "won't fix" because these reporting tools are no longer in regular use. (A replacement task, `print_metricvalues`, is more useful now.)
          tjenness Tim Jenness added a comment -

          Shouldn't we either fix them or delete the tasks?

          tjenness Tim Jenness added a comment - Shouldn't we either fix them or delete the tasks?

          The tasks aren't really broken - they just report false values of 0.0 in some rare cases. I don't know who "owns" lsst.verify, but would leave it up to them to decide whether to remove the tasks. 

          I guess I can go ahead and push a quick fix in the meantime...

          jcarlin Jeffrey Carlin added a comment - The tasks aren't really broken - they just report false values of 0.0 in some rare cases. I don't know who "owns" lsst.verify, but would leave it up to them to decide whether to remove the tasks.  I guess I can go ahead and push a quick fix in the meantime...

          As far as I know nobody "owns" lsst.verify, but both AP and SQuaRE have an interest in it. So if we want to delete this code then I think we'd have to do the usual thing and file an RFC.

          krzys Krzysztof Findeisen added a comment - As far as I know nobody "owns" lsst.verify, but both AP and SQuaRE have an interest in it. So if we want to delete this code then I think we'd have to do the usual thing and file an RFC.

          People

            jcarlin Jeffrey Carlin
            jcarlin Jeffrey Carlin
            Krzysztof Findeisen
            Jeffrey Carlin, Krzysztof Findeisen, Tim Jenness
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Jenkins

                No builds found.