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

On missing, unconverted, or invalid numeric values, write a string FITS complaint

    XMLWordPrintable

    Details

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

      Description

      As it stands, when the routines which generate FITS cards get an invalid or missing value, they do not generate the card, but write a COMMENT instead.

      We should write out 'NaN' for floating point numbers and, say, 'INVALID' for integers. Probably leave the semi-informative COMMENTS, but it is better for readers to get invalid values than no card.

      n.b. NaNs are valid pixel values, but NaN is not a valid card value.

        Attachments

          Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. INSTRM-484 Update FITS headers based on Subaru feedback of MCS example PFSC00005800

          • Normal - Normal priorities
          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PIPE2D-404 Support for raw exposures with W_PFDSGN not set

          • Normal - Normal priorities
          • Done

          Task - A task that needs to be done. INSTRM-130 Refactor CCD header generation

          • Normal - Normal priorities
          • Done

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: