GNU Astronomy Utilities - Tasks: task #14315, Propagate all FITS header keywords...
You are not allowed to post comments on this tracker with your current authentication level.
task #14315: Propagate all FITS header keywords into output FITS files
Submitter: | Lee Kelvin <leeskelvin> | ||
Submitted: | Fri 20 Jan 2017 06:00:34 PM UTC | ||
Should Start On: | Fri 20 Jan 2017 12:00:00 AM UTC | Should be Finished on: | Fri 20 Jan 2017 12:00:00 AM UTC |
Category: | All Gnuastro | Priority: | 5 - Normal |
Item Group: | Enhancement | Status: | None |
Privacy: | Public | Assigned to: | None |
Percent Complete: | 0% | Open/Closed: | Open |
Effort: | 0.00 |
Jump to the original submission
Mon 23 Jan 2017 07:23:47 PM UTC, comment #7: |
Mohammad Akhlaghi <makhlaghi> |
Mon 23 Jan 2017 06:45:05 PM UTC, comment #6:
|
Lee Kelvin <leeskelvin> |
Mon 23 Jan 2017 06:14:44 PM UTC, comment #5: Initially you mentioned that you "favour the latter option of the two". So I tried to elaborate more on it. The latter option was to use the Header program and not internally in each program.
|
Mohammad Akhlaghi <makhlaghi> |
Mon 23 Jan 2017 05:27:25 PM UTC, comment #4: Hi Mohammad,
|
Lee Kelvin <leeskelvin> |
Mon 23 Jan 2017 03:49:10 PM UTC, comment #3: Thanks, I agree, the second/latter method (where the "Header" program would be in charge of propagating headers from one or multiple files into another file) is a much better method, and is in-line with the modularity principle.
|
Mohammad Akhlaghi <makhlaghi> |
Mon 23 Jan 2017 10:27:42 AM UTC, comment #2: I personally favour the latter option of the two you present, adding all keywords which do not already exist in the header. In my own efforts writing FITS read/write software for the R astro package, we arrived at a similar conclusion.
|
Lee Kelvin <leeskelvin> |
Fri 20 Jan 2017 06:27:53 PM UTC, comment #1: This is another very useful suggestion.
|
Mohammad Akhlaghi <makhlaghi> |
Fri 20 Jan 2017 06:00:34 PM UTC, original submission:
When performing an image rotation using ImageWarp, or an image crop using ImageCrop, all user-supplied FITS header keywords should be propagated through to the resultant output file.
|
Lee Kelvin <leeskelvin> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-01-20 | leeskelvin | Attached File | - | Added input.fits, #39521 | |
Attached File | - | Added input_crop.fits, #39522 | |||
Attached File | - | Added input_rotated.fits, #39523 |
Powered by Savane 3.13-f8d8.
Corresponding source code
The whole purpose of these discussions is that it should not up to me ;-), we want to make the best collective descision.
Once it is implemented, anyone can enable and/or disable this feature (as well as all the other features) in all Gnuastro, for the whole system, for a program, for a user, for a directory, or even only for one run of any program. I don't know of any software in astronomy which allow this level of configurability. So I am not against it ;-).
I have also been thinking about this feature for a long time, so I was really happy when you suggested it. I just don't have the mental capacity now to implement this new feauture immediately. All my concentration is on the much more fundamental `gal_data_t' (task #14245). Fixing bugs is easy, but implementing a whole new feature elegantly/robustly takes concentration. So I suggested that I would happily help anyone else who can do it before me ;-).
Thanks again for bringing up this issue ;-)...