Table of contents
CSPICE_DLAOPN opens a new DLA file and sets the file type.
Given:
fname the name of a new DLA file to be created.
help, fname
STRING = Scalar
The file will be left opened for write access.
ftype a code for type of data placed into a DLA file.
help, ftype
STRING = Scalar
The non-blank part of `ftype' is used as the "file type"
portion of the ID word in the DLA file.
The first nonblank character and the three, or fewer,
characters immediately following it, giving four
characters, are used to represent the type of the data
placed in the DLA file. This is provided as a convenience
for higher level software. It is an error if this string
is blank. Also, the file type may not contain any
nonprinting characters. When written to the DLA file, the
value for the type IS case sensitive.
NAIF has reserved for its own use file types consisting
of the upper case letters (A-Z) and the digits 0-9. NAIF
recommends lower case or mixed case file types be used by
all others in order to avoid any conflicts with NAIF file
types.
ifname the internal file name for the new file.
help, ifname
STRING = Scalar
The name may contain as many as 60 characters. This name
should uniquely identify the file.
ncomch the number of comment characters to allocate.
help, ncomch
LONG = Scalar
`ncomch' is used to establish the number of comment records
that will be allocated to the new DLA file. The number of
comment records allocated is the minimum required to
store the specified number of comment characters.
Allocating comment records at file creation time may
reduce the likelihood of having to expand the
comment area later.
the call:
cspice_dlaopn, fname, ftype, ifname, ncomch, handle
returns:
handle the file handle associated with the file.
help, handle
LONG = Scalar
This handle is used to identify the file in subsequent calls
to other DLA routines.
None.
Any numerical results shown for this example may differ between
platforms as the results depend on the SPICE kernels used as input
and the machine specific arithmetic implementation.
1) Create a DLA file containing one segment; the segment
contains character, double precision, and integer data.
After writing and closing the file, open the file for
read access; dump the data to standard output.
Example code begins here.
PRO dlaopn_ex1
;;
;; IcyUser is a file that makes certain variables global.
;; You must call IcyUser to have access to the parameters used
;; in this example.
;;
;; To use the variables in IcyUser, add the 'src/icy' directory
;; to your IDL path by doing the following in which /path/to is the
;; local path to Icy.
;;
;; pref_set, 'IDL_PATH', '/path/to/icy/src/icy:<IDL_DEFAULT>', $
;; /COMMIT
;;
@IcyUser
;;
;; Local parameters
;;
DLA = 'dlaopn_ex1.dla'
LNSIZE = 61L
MAXC = 5L
MAXD = 50L
MAXI = 100L
;;
;; Local variables
;;
cvals = BYTARR( LNSIZE, MAXC )
cvals2 = BYTARR( LNSIZE, MAXC )
ivals = LONARR( MAXI )
dvals = DBLARR( MAXD )
;;
;; Set the internal file name. Don't reserve characters in
;; the DAS comment area.
;;
ifname = 'Example DLA file for testing'
ncomch = 0L
;;
;; Open a new DLA file.
;;
cspice_dlaopn, DLA, 'DLA', ifname, ncomch, handle
;;
;; Begin a new segment.
;;
cspice_dlabns, handle
;;
;; Add character data to the segment.
;;
for i=0, MAXC-1 do begin
for j=0, LNSIZE-1 do begin
k = ( (j+i+1) MOD 10B )
cvals[j,i] = BYTE('0') + k
endfor
endfor
cspice_dasadc, handle, MAXC*LNSIZE, 0, LNSIZE-1, cvals
;;
;; Add integer and double precision data to the segment.
;;
for i=1L, MAXI do begin
ivals[i-1] = i
endfor
cspice_dasadi, handle, ivals
for i=1L, MAXD do begin
dvals[i-1] = i
endfor
cspice_dasadd, handle, dvals
;;
;; End the segment.
;;
cspice_dlaens, handle
;;
;; Close the file. The routine cspice_dascls flushes the DAS
;; buffers and segregates the file before closing it.
;;
cspice_dascls, handle
;;
;; Now read the file and check the data.
;;
cspice_dasopr, DLA, handle
;;
;; Obtain the segment descriptor for the sole segment
;; in the file. We need not check the found flag
;; in this case because we know there is one segment
;; in the file.
;;
cspice_dlabfs, handle, descr, found
;;
;; Fetch character data from the segment. Obtain the
;; base address of the character data and the
;; character count from the descriptor.
;;
base = descr[SPICE_DLA_CBSIDX]
n = descr[SPICE_DLA_CSZIDX]
cspice_dasrdc, handle, base+1, base+n, 0, LNSIZE-1, cvals2
;;
;; Display the character data.
;;
print, ' '
print, 'Character array:'
for i=0L, (n/LNSIZE)-1L do begin
print, STRING( cvals2[*,i] )
endfor
;;
;; Fetch and display the integer and double precision data.
;;
base = descr[SPICE_DLA_IBSIDX]
n = descr[SPICE_DLA_ISZIDX]
cspice_dasrdi, handle, base+1L, base+n, ivals2
print, ' '
print, 'Integer array:'
for i=0L, (n/10L)-1L do begin
print, format='(10I6)', ivals2[i*10:i*10+9]
endfor
base = descr[SPICE_DLA_DBSIDX]
n = descr[SPICE_DLA_DSZIDX]
cspice_dasrdd, handle, base+1L, base+n, dvals2
print, ' '
print, 'Double precision array:'
for i=0L, (n/10L)-1L do begin
print, format='(10F6.1)', dvals2[i*10:i*10+9]
endfor
;;
;; Close the file.
;;
cspice_dascls, handle
END
When this program was executed on a Mac/Intel/IDL8.x/64-bit
platform, the output was:
Character array:
1234567890123456789012345678901234567890123456789012345678901
2345678901234567890123456789012345678901234567890123456789012
3456789012345678901234567890123456789012345678901234567890123
4567890123456789012345678901234567890123456789012345678901234
5678901234567890123456789012345678901234567890123456789012345
Integer array:
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30
31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50
51 52 53 54 55 56 57 58 59 60
61 62 63 64 65 66 67 68 69 70
71 72 73 74 75 76 77 78 79 80
81 82 83 84 85 86 87 88 89 90
91 92 93 94 95 96 97 98 99 100
Double precision array:
1.0 2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0 10.0
11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0 19.0 20.0
21.0 22.0 23.0 24.0 25.0 26.0 27.0 28.0 29.0 30.0
31.0 32.0 33.0 34.0 35.0 36.0 37.0 38.0 39.0 40.0
41.0 42.0 43.0 44.0 45.0 46.0 47.0 48.0 49.0 50.0
Note that after run completion, a new DLA file exists in the
output directory.
DLA files are built using the DAS low-level format; DLA files are
a specialized type of DAS file in which data are organized as a
doubly linked list of segments. Each segment's data belong to
contiguous components of character, double precision, and integer
type.
This routine creates a new DLA file and sets the type of the
file to the mnemonic code passed to it.
DLA files created by this routine have initialized file records.
The ID word in a DLA file record has the form
DAS/xxxx
where the characters following the slash are supplied by the
caller of this routine.
1) If the input filename is blank, an error is signaled by a
routine in the call tree of this routine. No file will be
created.
2) If the specified file cannot be opened without exceeding the
maximum allowed number of open DAS files, an error is signaled
by a routine in the call tree of this routine. No file will be
created.
3) If the file cannot be opened properly, an error is signaled by
a routine in the call tree of this routine. No file will be
created.
4) If the initial records in the file cannot be written, an error
is signaled by a routine in the call tree of this routine. No
file will be created.
5) If no logical units are available, an error is signaled by a
routine in the call tree of this routine. No file will be
created.
6) If the file type is blank, an error is signaled by a routine
in the call tree of this routine. No file will be created.
7) If the file type contains nonprinting characters, decimal 0-31
and 127-255, an error is signaled by a routine in the call
tree of this routine. No file will be created.
8) If the number of comment characters allocated to be allocated,
`ncomch', is negative, the error SPICE(BADRECORDCOUNT) is
signaled by a routine in the call tree of this routine. No
file will be created.
9) If any of the input arguments, `fname', `ftype', `ifname' or
`ncomch', is undefined, an error is signaled by the IDL error
handling system.
10) If any of the input arguments, `fname', `ftype', `ifname' or
`ncomch', is not of the expected type, or it does not have the
expected dimensions and size, an error is signaled by the Icy
interface.
11) If the output argument `handle' is not a named variable, an
error is signaled by the Icy interface.
See argument `fname'.
None.
DAS.REQ
DLA.REQ
ICY.REQ
None.
J. Diaz del Rio (ODC Space)
-Icy Version 1.0.0, 01-NOV-2021 (JDR)
open a new DLA file
open a new DLA file with write access
|