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

Add first metric to fakesAnalysis

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • None
    • 4
    • DRP F19-5, DRP F19-6 (Nov), DRP S20-2 (Jan), DRP S20-3 (Feb), DRP S20-5 (Apr), DRP S20-6 (May), DRP F20-1 (June), DRP F20-2 (July)
    • Data Release Production

    Description

      https://jira.lsstcorp.org/browse/DM-21319#Add the first metric to fakesAnalysis, the metric will be the median magnitude difference between input and extracted magnitudes for fakes stars.

      Attachments

        Activity

          sophiereed Sophie Reed added a comment -

          Thank you for all your help so far, hopefully this will be quicker!

          sophiereed Sophie Reed added a comment - Thank you for all your help so far, hopefully this will be quicker!

          Nice first step in adding more metrics to pipe_analysis. See PR comments regarding the problem of encoding information in metric names. We should use metric specifications for that. I would recommend to revisit this later. See for example SQR-029 it can help you to design your metrics and specifications better.

          afausti Angelo Fausti added a comment - Nice first step in adding more metrics to pipe_analysis. See PR comments regarding the problem of encoding information in metric names. We should use metric specifications for that. I would recommend to revisit this later. See for example SQR-029 it can help you to design your metrics and specifications better.
          sophiereed Sophie Reed added a comment -

          Following discussions over slack I am going to leave the metric names as is currently. I agree that they are too long and that a more succinct format would be preferable. I think that there is a middle ground to be found between completely abbreviated names and too long names, to find this we probably need to use the interface more and have a group discussion about what information would be useful stored where in the interface. This can then be implemented on a different ticket. 

          sophiereed Sophie Reed added a comment - Following discussions over slack I am going to leave the metric names as is currently. I agree that they are too long and that a more succinct format would be preferable. I think that there is a middle ground to be found between completely abbreviated names and too long names, to find this we probably need to use the interface more and have a group discussion about what information would be useful stored where in the interface. This can then be implemented on a different ticket. 
          sophiereed Sophie Reed added a comment -

          Some of the details that are currently encoded in the metric name can be added as metadata_querys in the metric specifications instead. This would allow them to be queried. How easy it is to subsequently display this information and the best way to do so needs to be further investigated.

          sophiereed Sophie Reed added a comment - Some of the details that are currently encoded in the metric name can be added as metadata_querys in the metric specifications instead. This would allow them to be queried. How easy it is to subsequently display this information and the best way to do so needs to be further investigated.

          People

            sophiereed Sophie Reed
            sophiereed Sophie Reed
            Angelo Fausti
            Angelo Fausti, Sophie Reed, Yusra AlSayyad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Jenkins

                No builds found.