[task #15468] Manage vector values inside tables

[Raul Infante-Sainz]

URL:
  <https://savannah.gnu.org/task/?15468>

                 Summary: Manage vector values inside tables
                 Project: GNU Astronomy Utilities
            Submitted by: infantesainz
            Submitted on: 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
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

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).
In this catalogue there are multiple columns, but just focusing on the one
with name `apflux_g' it can be seen that there are multiple values for a
single object (row). They correspond to photometry measurements on different
apertures. When considering this table with the program `Table', it gives as
an output a no-sense result.

Consider the column `apflux_g' and the last row, with `asttable':

 
asttable tractor-0397m080.fits -capflux_g


the result is: 


0.274843


It is a single value. However, the real value is an array (read with
`topcat'): 
 

(0.15832691, 0.33208665, 0.523447, 0.87126434, 1.099582, 1.4097637, 1.3801724,
1.514054)





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/task/?15468>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/