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

Add FOCUSZ header to phosim files

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ts_aos
    • Labels:

      Description

      Add FOCUSZ header to the repackaged phosim images, to conform to the documentation https://confluence.lsstcorp.org/display/SYSENG/ComCam+Header+Information+Topic+Mapping and units for `demand` described at https://ts-xml.lsst.io/sal_interfaces/MTHexapod.html#demand   . This includes correct values for (X,Y,Z,U,V,W) 

        Attachments

          Issue Links

            Activity

            Hide
            ksuberlak Krzysztof Suberlak added a comment -
            Show
            ksuberlak Krzysztof Suberlak added a comment - Related slack conversation at  https://lsstc.slack.com/archives/C9BEJU1T3/p1619128247019600
            Hide
            ksuberlak Krzysztof Suberlak added a comment -

            Bo Xin [X]  - I'm wondering for an example meaning of the `demand`. Are  XY = 0, and Z the defocal +/- 1500 micrometers?  If so, what  are U,V,W  ?

            Show
            ksuberlak Krzysztof Suberlak added a comment - Bo Xin [X]   - I'm wondering for an example meaning of the `demand`. Are   X ,  Y  = 0, and  Z  the defocal +/- 1500 micrometers?  If so, what  are  U,V,W   ?
            Hide
            bxin Bo Xin [X] (Inactive) added a comment -

            those are six DOFs defining the positioning of the hexapod. they are simply (x,y,z,rx,ry,rz). i.e., U is rotation around x-axis, and so on

            Show
            bxin Bo Xin [X] (Inactive) added a comment - those are six DOFs defining the positioning of the hexapod. they are simply (x,y,z,rx,ry,rz). i.e., U is rotation around x-axis, and so on
            Hide
            ksuberlak Krzysztof Suberlak added a comment -

            Following the conversation on slack, I paste the conclusion: "for  the simulated defocal comCam, lsstCam images ,  FOCUSZ would be (0,0,+/-1500, 0,0,0) , and for in-focus images (0,0,0,0,0,0) , while for corner sensors simulated images it would be always (0,0,0,0,0,0) "

            Show
            ksuberlak Krzysztof Suberlak added a comment - Following the conversation on slack, I paste the conclusion: "for  the simulated defocal  comCam, lsstCam  images ,   FOCUSZ  would be  (0,0,+/-1500, 0,0,0)  , and for in-focus images  (0,0,0,0,0,0)  , while for corner sensors simulated images it would be always  (0,0,0,0,0,0)  "
            Hide
            bxin Bo Xin [X] (Inactive) added a comment -

            Note that for corner sensors it won't be (0,0,0,0,0,0) if the entire camera is pistoned to an off-focus position.

            The key point is that the FOCUSZ should simply be the position of the camera hexapod. 

            With your simulations, you are using a "MOVE" command to piston the camera. The value that goes with the "MOVE" command should be in the header as FOCUSZ.

             

            Show
            bxin Bo Xin [X] (Inactive) added a comment - Note that for corner sensors it won't be (0,0,0,0,0,0) if the entire camera is pistoned to an off-focus position. The key point is that the FOCUSZ should simply be the position of the camera hexapod.  With your simulations, you are using a "MOVE" command to piston the camera. The value that goes with the "MOVE" command should be in the header as FOCUSZ.  
            Hide
            ksuberlak Krzysztof Suberlak added a comment -

             Clarification: `demand` in https://ts-xml.lsst.io/sal_interfaces/MTHexapod.html#demand   is a variable that contains (X,Y,Z,U,V,W) and FOCUSZ  in https://confluence.lsstcorp.org/display/SYSENG/ComCam+Header+Information+Topic+Mapping   is a third element of that variable:  demand[2] . So FOCUSZ is +/- 1500 or 0 . 

            Show
            ksuberlak Krzysztof Suberlak added a comment -  Clarification: ` demand` in https://ts-xml.lsst.io/sal_interfaces/MTHexapod.html#demand     is a variable that contains  (X,Y,Z,U,V,W)  and  FOCUSZ   in https://confluence.lsstcorp.org/display/SYSENG/ComCam+Header+Information+Topic+Mapping    is a third element of that variable:   demand [2] . So FOCUSZ is +/- 1500 or 0 . 
            Hide
            ttsai Te-Wei Tsai added a comment -

            The update looks good to me!

            Show
            ttsai Te-Wei Tsai added a comment - The update looks good to me!
            Hide
            ksuberlak Krzysztof Suberlak added a comment -

            Adding FOCUSZ to ts_phosim is included now in Tiago's DM-30128 ticket, marking this one as "Done" 

            Show
            ksuberlak Krzysztof Suberlak added a comment - Adding FOCUSZ to ts_phosim is included now in Tiago's DM-30128 ticket, marking this one as "Done" 

              People

              Assignee:
              ksuberlak Krzysztof Suberlak
              Reporter:
              ksuberlak Krzysztof Suberlak
              Reviewers:
              Te-Wei Tsai
              Watchers:
              Bo Xin [X] (Inactive), Bryce Kalmbach, Krzysztof Suberlak, Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Start date:

                  Jenkins

                  No builds found.