GNU Astronomy Utilities - Bugs: bug #58363, Cite exact parts of FITS standard...
You are not allowed to post comments on this tracker with your current authentication level.
bug #58363: Cite exact parts of FITS standard or CFITSIO about primary HDU
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Wed 13 May 2020 12:55:25 AM UTC | ||
Category: | Libraries | Severity: | 3 - Normal |
Item Group: | Addition(s) | Status: | Fixed |
Privacy: | Public | Assigned to: | makhlaghi |
Open/Closed: | Closed |
Sat 23 May 2020 07:42:29 PM UTC, comment #3: |
Mohammad Akhlaghi <makhlaghi> |
Wed 13 May 2020 04:35:16 PM UTC, comment #2: The error message has been updated, what do you think now?
|
Mohammad Akhlaghi <makhlaghi> |
Wed 13 May 2020 06:15:11 AM UTC, comment #1: I implemented 80% of the FITS 4.0 standard a few months ago in Scala language (https://www.scala-lang.org/) and I don't remember any recommendations on how to organize the HDUs. Hence, the message was strange to me.
|
Rafael Morales <rmorales> |
Wed 13 May 2020 12:55:25 AM UTC, original submission:
It was recently mentioned in bug-gnuastro@gnu.org that the statement "Gnuastro leaves the first HDU blank (with no data) and writes the outputs in the second HDU. " is not actually recommended in the FITS standard (as suggested when the error message).
|
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-05-23 | makhlaghi | Status | None | Fixed | |
Assigned to | None | makhlaghi | |||
Open/Closed | Open | Closed | |||
2020-05-13 | makhlaghi | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-d3ae.
Corresponding source code
The correction in the previous commit doesn't cause confusions any more and there was no discussion afterwards. So I am closing this bug.