GNU Astronomy Utilities - Bugs: bug #49274, Problem in identifying string or...
You are not allowed to post comments on this tracker with your current authentication level.
bug #49274: Problem in identifying string or number
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Wed 05 Oct 2016 06:01:12 PM UTC | ||
Category: | Fits | Severity: | 4 - Important |
Item Group: | Output not reasonable | Status: | Fixed |
Privacy: | Public | Assigned to: | makhlaghi |
Open/Closed: | Closed |
Wed 05 Oct 2016 06:49:23 PM UTC, comment #2: |
Mohammad Akhlaghi <makhlaghi> |
Wed 05 Oct 2016 06:04:38 PM UTC, comment #1: Sorry, first command should have been (the keyword's comment was changed):
|
Mohammad Akhlaghi <makhlaghi> |
Wed 05 Oct 2016 06:01:12 PM UTC, original submission:
When given the following command is run on any FITS file (let's say `img.fits' for this bug report), Header will think the value is a number and so write the FITS keyword value as a number, not a string.
|
Mohammad Akhlaghi <makhlaghi> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
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 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-10-05 | makhlaghi | Status | Confirmed | Fixed | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-4b48.
Corresponding source code
This was not actually a problem, because `87095e5' is actually a number not a string! I got this as a short Git commit hash so I was looking at it like a string and didn't notice it can be a number too!
Since this can happen if people want to add commit hashes to the headers of FITS files (to keep track of what parameters created the file), I added a tip to the book explaining the situation and some solutions.