bugGNU Astronomy Utilities - Bugs: bug #58901, Blank values for non-standard...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #58901: Blank values for non-standard integer types in FITS tables

Submitter:  Mohammad Akhlaghi <makhlaghi>
Submitted:  Wed 05 Aug 2020 12:17:06 AM UTC
   
 
Category:  Table Severity:  3 - Normal
Item Group:  Output not reasonable Status:  Fixed
Privacy:  Public Assigned to:  makhlaghi
Open/Closed:  Closed

Wed 05 Aug 2020 12:24:01 AM UTC, comment #1: 

This bug has been fixed in Commit c75c40e9c1.

Mohammad Akhlaghi <makhlaghi>
Group administrator
Wed 05 Aug 2020 12:17:06 AM UTC, original submission:  

When writing a FITS table column with non-standard FITS types (int8_t, uint16_t, uint32_t and uint64_t), we simply write the blank value into the TNULL keyword. However, according to the FITS standard, TNULL is checked before TZERO or tSCAL are applied to these non-standard data types.

As a result, when reading from that FITS table, the blank elements aren't specified as blank any more!

Mohammad Akhlaghi <makhlaghi>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by makhlaghi (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-08-05 makhlaghi StatusIn Progress Fixed
        Open/ClosedOpen Closed
        SummaryBlank values for non-standard integer types in FITS tables. Blank values for non-standard integer types in FITS tables

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code