Next: DESCRIP3
Up: Record Type Format Specifications
Previous: DESCRIP1
  Contents
DESCRIP2
For each Level 2 dimension (1,...,OBJDESC.NDIM2) there must be a single
record in this record type. The descriptor records may be in any order, but
it is recommended that they be in the order 1 through OBJDESC.NDIM2. This
record is considered the authoritative source of information for this
dimension. A parallel description can be supplied in the DESCRIP record
type. There must be a DESCVAL record for each DESCRIP2 record which
specifies the grid points along that dimension. An optional DESCSUP record
may be present if additional information is required.
- name
-
- RECTYPE
-
- I
- is the record type code = 32
- NDEX
-
- I
- specifies which Level 2 dimension is
being described. Counting begins at 0 or 1 as specified in the
TEST.SPECB.IDXSTART
field. Note that this index does not refer to an
index position of an actual data array but is
instead a pointer into the
DIMSPEC2.INDEX field.
See the discussion in Section 2.3.2
- DUPNUM
-
- I
- is the number of DESCRIP records for this dimension
- DESSUP
-
- I
- is the number of floating-point values in the SVALS field of
the following DESCSUP record. If zero, then there is no DESCSUP record
for this dimension
- DESFMT
-
- I
- is the descriptor format code. This code is explained in
Section A.1.1
- DESTYPE
-
- I
- is the quantity code for the physical quantity that the
dimension represents. This code is explained in Section A.1.3
- UNITS
-
- I
- is the units code for the physical quantity that the dimension
represents. This code is explained in Section A.1.4
- STORG
-
- I
- specifies how the values of the descriptor are stored in the
DESCVAL record which follows. The possible values are:
-
-
-
0 |
= |
an explicit array of
DIMSPEC2.GPTNUM
values |
1 |
= |
an implicit specification consisting of a (low-value, interval) pair |
2 |
= |
an implicit specification consisting of a (low-value, high-value) pair |
- RESERVE0
-
- I
- is reserved for future expansion
- RESERVE1
-
- I
- is reserved for future expansion
Next: DESCRIP3
Up: Record Type Format Specifications
Previous: DESCRIP1
  Contents
Eric Nash
2003-09-25