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

OBJECT key value incorrect for certain visits

    XMLWordPrintable

    Details

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

      Description

      A few of us have noticed inconsistencies between the value of the OBJECT keyword and the actual data taken for certain visits during the Sep 2022 Engineering Run. These are copied from comments in ticket INSTRM-1727:

      Visits 79990..79997, which are scienceArc s, have been accidentally assigned OBJECT=NGC6633.

      From Yabe-san:

      ... for visit=80842 (and probably other visits) OBJECT in the header looks M39 despite we observed NGC1980.

      A scheme for interpreting the OBJECT card is the subject of another ticket, INSTRM-1737 but the above are simply errors that should be fixed, by correcting the headers using the obs_pfs mechanism.

        Attachments

          Issue Links

          relates to

          Task - A task that needs to be done. INSTRM-1737 Set OBJECT card a bit more carefully.

          • Normal - Normal priorities
          • Open

          Task - A task that needs to be done. INSTRM-1727 fixing pfilamps header keys for september22 engRun

          • Normal - Normal priorities
          • Done

            Activity

              People

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

                Dates

                • Created:
                  Updated: