Previous: Software
Up: APPENDIX: Data Exchange Proposal
Previous Page: Software
Next Page: About this document ...

Example Binary Table Header

Finally we show an example of a binary table header with 6 columns of number of different data types and dimensions. Columns labeled POS, VEL, and ACC are arrays of dimension 1 and length NDIM. The column labeled CODE is a character string of length 4. The nonstandard keywords TIME, COORDSYS, etc. also appear at the end of the header, and identify global parameters of the dataset. Although copied by any FITS reading program, their meaning is only understood in the context of an `` NBODY BINTABLE''. Note the units are not SI, which is what the IAU recommends to store data in FITS format. The (binary) data followed at a multiple of 2880 bytes after the last keyword of the header (always END) is not displayed.

NOTE: The first two lines of numbers are only present to show card columns and are not part of the table header.

1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
XTENSION= 'BINTABLE'           / Extension type
BITPIX  =                    8 / Binary data
NAXIS   =                    2 / Table is a matrix
NAXIS1  =                   76 / Width of table row in bytes
NAXIS2  =                 1024 / Number of rows in table  (number of Nbodies)
PCOUNT  =                    0 / Random parameter count
GCOUNT  =                    1 / Group count
TFIELDS =                    6 / Number of columns in each row
EXTNAME = 'NBODY   '           / Standardized name of this extension
EXTVER  =                    1 / Version number of table 
TFORM1  = '1D      '           / Double Precision value in col 1
TTYPE1  = 'MASS            '   / Type (label) of column  1
TUNIT1  = 'SOLARM  '           / Physical units of column  1
TFORM2  = '3D      '           / Array of NDIM Double Precision values in col 2
TTYPE2  = 'POS             '   / Type (label) of column  2
TUNIT2  = 'KPC     '           / Physical units of column  2
TFORM3  = '3D      '           / Array of NDIM Double Precision values in col 3
TTYPE3  = 'VEL             '   / Type (label) of column  3
TUNIT3  = 'KM/S    '           / Physical units of column  3
TFORM4  = '1F      '           / Floating point number in col 3
TTYPE4  = 'PHI             '   / Type (label) of column  4
TUNIT4  = 'KM**2/S**2'         / Physical units of column  4
TFORM5  = '3F      '           / Array of NDIM Floating point values in col 5
TTYPE5  = 'ACC             '   / Type (label) of column  5
TUNIT5  = 'KM**2/S**2/KPC'     / Physical units of column  5
TFORM6  = '4A      '           / Character string (4) in col 6
TTYPE6  = 'CODE            '   / Type (label) of column  6
COMMENT   Now follow some 'global' parameters to this dataset
TIME    =                 10.0 / Model time of this snapshot
COORDSYS= 'CARTESIAN'          / Coordinate system
NDIM    =                    3 / Number of dimensions
AUTHOR  = 'Teuben'             / Person who is responsible for the data
ORIGIN  = 'NEMO'               / Originator 
DATE    = '05/12/93'           / dd/mm/yy when file created
DATEOBS = '28/08/93'           / dd/mm/yy when simulation done
HISTORY  NEMO mkplummer out=run301.in nbody=1024 massexpr=pow(m,p)  
HISTORY  NEMO  masspars=p,-2.0 massrange=0.1,10 VERSION=2.5a
HISTORY  NEMO nbody0 in=run301.in out=run301.out eta=0.01 tcrit=20  
HISTORY  NEMO  eps=0.025 VERSION=1.2b
HISTORY  NEMO snaptrim run301.out tmp3421 times=10 VERSION=1.5a
HISTORY  NEMO snapfits tmp3421 run301.t20.fits
END

teuben@.astro.umd.edu