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

Unsigned, uncompressed FITS images written with incorrect BZERO

    Details

    • Type: Bug
    • Status: Done
    • Priority: Undefined
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: afw
    • Labels:
      None
    • Templates:
    • Story Points:
      1
    • Sprint:
      DRP F18-4
    • Team:
      Data Release Production

      Description

      Writing an uncompressed Image with an unsigned integer type to FITS with our code results in a BZERO value one less than what CFITSIO or astropy write (without our code intervening in the cast of CFITSIO), and this confuses CFITSIO, astropy, and our own code about the type of the pixels when reading the image back in (because the convention is to use BZERO to distinguish between signed and unsigned types). I'm not sure if the same problem appears in compressed images or not.

      I think this can be fixed by modifying the Bzero traits class in fitsCompression.cc, and if that's right most of the work here will just be test code.

        Attachments

          Container Issues

            Issue Links

              Activity

                People

                • Assignee:
                  jbosch Jim Bosch
                  Reporter:
                  jbosch Jim Bosch
                  Reviewers:
                  Paul Price
                  Watchers:
                  Jim Bosch, Paul Price
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Summary Panel