Instrument control developmentIcon indicating the project type

Instrument control development

Uploaded image for project: 'Instrument control development'
  1. Instrument control development
  2. INSTRM-572

Track "real" pfsConfigId when taking odd and even quartz flats.

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Normal
    • Resolution: Unresolved
    • Component/s: None
    • Labels:

      Description

      The 2d pipeline expects to match science exposures to their flat and arc calibration exposures using their common pfsConfigId.

      But when taking odd and even fiber quartz exposures, half the cobras will be behind the spots so the actual configId will be wrong.

      Either lie about the configId, or, almost certainly better, include a card with the configId for the full field. Oh, `W_PFIDFL` or something equally ncmprhnsbl.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          rhl rhl added a comment - - edited

          I'm not sure that the premise of this ticket is correct. We build flats and traces from odd/even flats and then declare them to be valid in the calibration database.  So the lookup is done via visit or equivalently time stamp, not via pfsConfigId.  I was expecting the cobra config to take even/odd spots to have different pfsDesignID s (and different pfsConfigID s too)

          Show
          rhl rhl added a comment - - edited I'm not sure that the premise of this ticket is correct. We build flats and traces from odd/even flats and then declare them to be valid in the calibration database .  So the lookup is done via visit or equivalently time stamp, not via pfsConfigId .  I was expecting the cobra config to take even/odd spots to have different pfsDesignID s (and different pfsConfigID s too)
          Hide
          Permalink
          hassan hassan added a comment -

          cloomis: I think we can close this ticket as 'wont fix', correct? It no longer makes sense as we have the FiberStatus.BLACKSPOT enumeration available in PfsConfigs.

          Show
          hassan hassan added a comment - cloomis : I think we can close this ticket as 'wont fix', correct? It no longer makes sense as we have the FiberStatus.BLACKSPOT enumeration available in PfsConfigs.

            People

            • Assignee:
              Unassigned
              Reporter:
              cloomis cloomis
            • Votes:
              0 Vote for this issue
              Watchers:
              Start watching this issue

              Dates

              • Created:
                Updated: