PDS_VERSION_ID = PDS3
RECORD_TYPE = UNDEFINED
^SAMPLE_ASCII_DOCUMENT =
{ "SWA_0283478400_585_E_00.ASC"
, "SWA_0283478400_585_E_01.ASC"
, "SWA_0283478400_585_E_02.ASC"
, "SWA_0283478400_585_E_03.ASC"
, "SWA_0283507232_586_E_00.ASC"
, "SWA_0283507232_586_E_01.ASC"
, "SWA_0283507232_586_E_02.ASC"
, "SWA_0283507232_586_E_03.ASC"
, "SWA_0283507232_586_E_04.ASC"
, "SWA_0283507232_586_E_05.ASC"
, "SWA_0283507232_586_E_06.ASC"
, "SWA_0283507232_586_S_00.ASC"
, "SWA_0283507232_586_S_01.ASC"
, "SWA_0283507232_586_S_02.ASC"
, "SWA_0283507232_586_S_03.ASC"
, "SWA_0283507232_586_S_04.ASC"
, "SWA_0283507232_586_S_05.ASC"
, "SWA_0316483200_584_E_00.ASC"
, "SWA_0316483200_584_E_01.ASC"
, "SWA_0316483200_584_E_02.ASC"
, "SWA_0316483200_584_E_03.ASC"
, "SWA_0316483200_584_S_00.ASC"
, "SWA_0316483200_584_S_01.ASC"
, "SWA_0316483200_584_S_02.ASC"
, "SWA_0316483200_584_S_03.ASC"
, "SWA_0316483200_584_S_04.ASC"
, "SWA_0316483200_584_S_05.ASC"
, "SWA_0316483200_584_S_06.ASC"
, "SWA_0316483200_584_S_07.ASC"
, "SWA_0316483200_584_S_08.ASC"
, "SWA_0316483200_584_S_09.ASC"
, "SWA_0316483200_584_S_10.ASC"
, "SWA_0316483200_584_S_11.ASC"
, "SWA_0316483200_584_S_12.ASC"
, "SWA_0316483200_584_S_13.ASC"
, "SWA_0316483200_584_S_14.ASC"
}
/*** GENERAL DATA DESCRIPTION PARAMETERS ***/
MISSION_NAME = "NEW HORIZONS"
DATA_SET_ID = "NH-X-SWAP-2-PLUTOCRUISE-V3.0"
PRODUCT_ID = "SWAP_SAMPLES"
PRODUCER_INSTITUTION_NAME = "SOUTHWEST RESEARCH INSTITUTE"
PRODUCT_CREATION_TIME = 2016-11-08T00:00:00
DESCRIPTION = "
This document contains a description of SWAP sample data formats
for SWAP Raw and Calibrated data sets.
"
/*** INSTRUMENT-RELATED PARAMETERS ***/
INSTRUMENT_ID = "SWAP"
INSTRUMENT_HOST_NAME = "NEW HORIZONS"
/* DATA OBJECT POINTERS IDENTIFICATION DATA ELEMENTS */
OBJECT = SAMPLE_ASCII_DOCUMENT
DOCUMENT_NAME = "SWAP Sample files"
PUBLICATION_DATE = 2016-11-08
DOCUMENT_TOPIC_TYPE = "USER'S GUIDE"
INTERCHANGE_FORMAT = ASCII
DOCUMENT_FORMAT = TEXT
DESCRIPTION = "
###########################################################################
###########################################################################
### N.B. THIS PDS LABEL FILE AND THE FILES IT REFERS TO ARE SAMPLES ###
### INTENDED ***ONLY*** TO SUPPORT USERS TRYING TO CONFIRM THEY ###
### ARE DECODING AND INTERPRETING THE DATA CORRECTLY; THESE FILES ###
### ARE ***NOT*** INTENDED FOR SCIENTIFIC DATA ANALYSIS! ###
###########################################################################
###########################################################################
These files, along with the accompanying FITS files (.FIT) with
detached labels (.LBL), are provided to support users who want to
ensure they are extracting the proper values from binary data files,
specifically FITS binary tables (EDUs with XTENSION='BINTABLE') and
FITS images (Primary Data Units and EDUs with XTENSION='IMAGE').
To do this, several quantities, mostly from the FITS header for each
PDU/EDU, are stored in ASCII format, along with a limited extent of
the binary data.
These quantities are in keyword=value format (though they are not
PDS keywords), and are as follows:
KEYWORDS
========
FILENAME=/home/soc/data/...
The full pathname from the Science Operation Center is stored
in lowercase.
PRODCTID=ALI_0043906979_0X4B5_SCI_1
The PDS Product ID of the product from which this sample was
extracted is stored in uppercase.
PATH =/DATA/20070611_004390/
The PATH to the product in the data set is stored in uppercase.
VIDAPPRX=NHJUAL_2XXX
The generic name of the Volume ID for the data set in which the
product resides is stored in uppercase.
By using the Product ID (PRODCTID=) as a lookup into the cumulative
index of any volume that matches the generic Volume ID (VIDAPPRX=),
the user will be able to identify the volume on which the product
resides. The path (PATH =) can then be used to locate the
product on that volume.
XTENSION=IMAGE, or
XTENSION=BINTABLE
This is present, even when the binary data reside in the PDU for which
the PHDU (Primary Header Data Unit) does not have an XTENSION keyword.
It's purpose is to alert the user to whether the binary data is an
IMAGE (or array) or a BINTABLE.
EXTNAME =0
This keyword shows the EXTNAME value of EDUs, and is 0 for PDUs.
NAXIS =N
BITPIX =8
NAXIS1 =5088
NAXIS2 =5088
...
NAXISN =5088
The keywords are copied from the FITS header and describe the
shape of the data. NAXIS states the number of dimensions of the
data and the NAXISn keywords state the size of each dimension.
Note that for binary tables, NAXIS will be 2 and NAXIS2 will be
the number of rows in the table.
BITPIX
The BITPIX keyword gives the size and type of one datum along
the NAXIS1 dimension as stored in the FITS PDU/EDU. Its meaning
is as follows:
BITPIX=8 8-bit byte unsigned data
BITPIX=16 16-bit 2-byte two's complement signed integer data
BITPIX=32 32-bit 4-byte two's complement signed integer data
BITPIX=-32 32-bit 4-byte single precision floating point IEEE data
BITPIX=-64 64-bit 8-byte double precision floating point IEEE data
For all multi-byte quantities, the bytes are stored in MSByte-first
order.
For binary tables (XTENSION=BINTABLE), BITPIX is always 8, and the
column descriptions may combine multiple bytes into a single
quantity.
Refer to the FITS standard for more details.
Description of sampling
=======================
After the keywords, there is a brief statement of how many values
are sampled and converted to ASCII format. The convention depends
on whether the data are an IMAGE or a BINTABLE.
- IMAGE:
First 10x1 values
N.B. No scaling (i.e. ignored BSCAL & BZERO)
- BINTABLE:
Showing all 2 columns, rows 1 to 50
N.B. No scaling (i.e. ignored TSCALn or TZEROn)
For an image, the target sample size is the first 10x10 rectangle
in the data. No more than 10 pixels across will be displayed, but
if the full image is less than 10 pixels across, then the number
of rows of data display will be increased if available. For data
of higher dimensionality than two, only the first plane is sampled.
For a binary table, all columns are shown and, if there or 10 or more
columns, then up to 10 rows of the table are shown as available. For
tables with fewer than ten columns, more rows are shown if available.
The note about scaling will be discussed below.
Sample Data
===========
Once again, the data are displayed slightly differently according
to the XTENSION type:
- IMAGE:
The rectangular array of pixel values, as described in the previous
section, are displayed in ASCII format. Commas and fixed-width
spacing are used to delimit the values. As the purpose of these
files is to allow a user to confirm that they are properly reading
the data, the data are interpreted as native FITS format (MSByte-first
two's complement signed integers, and MSByte-first IEEE floating point
values). No scaling or offsets (BSCAL & BZERO) are applied.
- BINTABLE:
Two lines of column description are displayed before the data:
- The value of TTYPEn i.e. the name of the column
- The value of TFORMn i.e. the shape (NxMxLx...) and data type
(B=❯byte; I=❯16-bit two's complement integer; J=❯32-bit two's
complement integer; F=32-bit single precision floating point;
D=❯64-bit single precision floating point) of each cell in
the table.
The rectangular array of column and row values are displayed in
ASCII format. Commas and fixed-width spacing are used to delimit
the values and keep them in alignment with the TTYPEn & TFORM
headers. As the purpose of these files is to allow a user to
confirm that they are properly reading the data, the data are
interpreted as native FITS format (MSByte-first two's complement
signed integers, and MSByte-first IEEE floating point values).
No scaling or offsets (TSCALn & TZERO) are applied.
If each cell in a column of the full data file contains more than
a single scalar i.e. a one or higher dimensional entity of multiple
values, then only the first value of each cell is displayed.
"
END_OBJECT = SAMPLE_ASCII_DOCUMENT
END
|