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

Fix setting of boresight rotation angle for imsim data

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: obs_lsst
    • Labels:
      None
    • Story Points:
      4
    • Sprint:
      DRP F19-2, DRP F19-4
    • Team:
      Data Release Production

      Description

      For individual obs packages, we are using "translators" to convert metadata from raw files into internally consistent conventions (as many telescopes have different sets of conventions and header naming).  Our convention for boresight rotation angle is:

      At boresightRotAngle = 0, the focal plane pixels are aligned:
      +x: E->W (-ve RA), +y: S->N (+ve Dec)
      

      (and see the documentation).

      Accordingly, the imsim translator in obs_lsst should reflect that:

      boresightRotAngle = 90 deg - ROTANGLE
      

      (where the ROTANGLE is the FITS card in the raw data).

      The reason data is currently being processed properly is due to a compensation (prior to the translator functionality) for this 90 deg shift in the lsstCamMapper here. This latter "correction" should be removed from there and accommodated in the imsim translator.

      This change will be validated by running a visit of DC2 data before and after and checking that we get consistent results.

        Attachments

          Activity

          No work has yet been logged on this issue.

            People

            Assignee:
            lauren Lauren MacArthur
            Reporter:
            lauren Lauren MacArthur
            Reviewers:
            Tim Jenness
            Watchers:
            Eli Rykoff, James Chiang, John Parejko, Lauren MacArthur, Robert Lupton, Simon Krughoff, Tim Jenness, Yusra AlSayyad
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.