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

Investigate stack changes behind chronograf diaSource ratio number changes

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Alert Production
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      AP S21-3 (February)
    • Team:
      Alert Production
    • Urgent?:
      No

      Description

      The ratio of DIASources to Direct Image Sources have changed between 11Jan and 13Jan in the CI-HiTS2015 run. Investigate possible reasons behind this.

        Attachments

          Activity

          Hide
          gkovacs Gabor Kovacs [X] (Inactive) added a comment - - edited

           

          Possible tickets that were merged between 11 Jan - 13 Jan (inclusive). I queried Jira for tickets with Resolution date within this range, also checked commit history for the ProcessCcd-ImageDifference pipeline subtask code repos: afw, cp_pipe, ip_isr, obs_base, ip_diffim, meas_base, meas_algorithms, meas_astrom, meas_deblender.

           

          • meas_deblender, meas_base, ip_diffim: no merges
          • DM-27005: Perhaps not. New stack environment. Merged later on 14 Jan.
          • DM-24702: Perhaps not. Implementation of PiffPsfDeterminer, though default configuration did not change.
          • DM-23159: Most likely. This was merged, then reverted in ip_isr, then merged again after 13 Jan; I could not track down whether it was merged when the CI run took place (are all time stamps in the same time zone? Also, commit dates may not reflect the latest update when rebase happens.). As I understand, this ticket relates to image calibration and changes some default config as well.
          • DM-28258: Considered irrelevant. (wcs epoch)
          • DM-28040: Considered irrelevant. (stamps objects)
          • DM-27766: Considered irrelevant. (astropy erfa)
          • DM-28208: Considered irrelevant. (Fits handling.)
          • DM-28236: Considered irrelevant. (filterLabel)

           

           

          Show
          gkovacs Gabor Kovacs [X] (Inactive) added a comment - - edited   Possible tickets that were merged between 11 Jan - 13 Jan (inclusive). I queried Jira for tickets with Resolution date within this range, also checked commit history for the ProcessCcd-ImageDifference pipeline subtask code repos: afw, cp_pipe, ip_isr, obs_base, ip_diffim, meas_base, meas_algorithms, meas_astrom, meas_deblender.   meas_deblender, meas_base, ip_diffim: no merges DM-27005 : Perhaps not. New stack environment. Merged later on 14 Jan. DM-24702 : Perhaps not. Implementation of PiffPsfDeterminer, though default configuration did not change. DM-23159 : Most likely. This was merged, then reverted in ip_isr, then merged again after 13 Jan; I could not track down whether it was merged when the CI run took place (are all time stamps in the same time zone? Also, commit dates may not reflect the latest update when rebase happens.). As I understand, this ticket relates to image calibration and changes some default config as well. DM-28258 : Considered irrelevant. (wcs epoch) DM-28040 : Considered irrelevant. (stamps objects) DM-27766 : Considered irrelevant. (astropy erfa) DM-28208 : Considered irrelevant. (Fits handling.) DM-28236 : Considered irrelevant. (filterLabel)    
          Hide
          ebellm Eric Bellm added a comment - - edited

          Thanks for following this up.

          Show
          ebellm Eric Bellm added a comment - - edited Thanks for following this up.

            People

            Assignee:
            gkovacs Gabor Kovacs [X] (Inactive)
            Reporter:
            gkovacs Gabor Kovacs [X] (Inactive)
            Reviewers:
            Eric Bellm
            Watchers:
            Eric Bellm, Gabor Kovacs [X] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.