GNU Astronomy Utilities - Tasks: task #15468, Manage vector values inside tables
You are not allowed to post comments on this tracker with your current authentication level.
task #15468: Manage vector values inside tables
Submitter: | Raul Infante-Sainz <infantesainz> | ||
Submitted: | Mon 18 Nov 2019 10:25:47 AM UTC | ||
Should Start On: | Mon 18 Nov 2019 12:00:00 AM UTC | Should be Finished on: | Mon 18 Nov 2019 12:00:00 AM UTC |
Category: | Table | Priority: | 5 - Normal |
Item Group: | Output not reasonable | Status: | None |
Privacy: | Public | Assigned to: | None |
Percent Complete: | 0% | Open/Closed: | Open |
Effort: | 0.00 |
Mon 18 Nov 2019 01:59:13 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi> |
Mon 18 Nov 2019 10:25:47 AM UTC, original submission:
I found some catalogues (fits tables) that instead one value per each column and row, they are arrays. As a particular example it can be checked the catalogue of DECaLS around NGC1035 (link: https://portal.nersc.gov/project/cosmo/data/legacysurvey/dr8/south/tractor/039/tractor-0397m080.fits).
|
Raul Infante-Sainz <infantesainz> |
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.
Powered by Savane 3.13-d3ae.
Corresponding source code
Thanks a lot for bringing this up. This is an interesting format to keep columns with similar values in a FITS table without having to increase the official column number.
Following your task report, it just occurred to me that we can specify sub-columns with a `.N' added to the column name for example in the example you sent, if you wanted the third sub-column of the `apflux_g' column, you can run a command like this:
We can similarly extend the concept to Gnuastro's plain-text table format (to easily print on the command-line or create FITS tables with this feature), so the sub-column metadata would be printed like this (the `.M' part is new):
For example, following the example in that section of the book, such, the meta-data for sub-column 3 of column 5 in a table would look like this:
Unfortunately I am too busy to implement this now, but it is a very good suggestion to add this feature, I can see many scenarios where such array-column can be very useful. So I just tried to build upon the initial suggestion with some possibly useful implementation details.
Until I get the chance to implement this, if anyone is interested to try implementing it, any help would be very welcome.