dasrdc |
Table of contents
ProcedureDASRDC ( DAS, read data, character ) SUBROUTINE DASRDC ( HANDLE, FIRST, LAST, BPOS, EPOS, DATA ) AbstractRead character data from a range of DAS logical addresses. Required_ReadingDAS KeywordsARRAY ASSIGNMENT DAS FILES DeclarationsIMPLICIT NONE INTEGER HANDLE INTEGER FIRST INTEGER LAST INTEGER BPOS INTEGER EPOS CHARACTER*(*) DATA ( * ) Brief_I/OVARIABLE I/O DESCRIPTION -------- --- -------------------------------------------------- HANDLE I DAS file handle. FIRST, LAST I Range of DAS character logical addresses. BPOS, EPOS I Begin and end positions of substrings. DATA O Data having addresses FIRST through LAST. Detailed_InputHANDLE is a file handle for an open DAS file. FIRST, LAST are a range of DAS character logical addresses. FIRST and LAST must be greater than or equal to 1 and less than or equal to the highest character logical address in the DAS file designated by HANDLE. BPOS, EPOS are the begin and end character positions that define the substrings in each of the elements of the output array DATA into which character data is to be read. Detailed_OutputDATA is an array of strings. On output, the character words in the logical address range FIRST through LAST are copied into the characters DATA(1)(BPOS:BPOS), DATA(1)(BPOS+1:BPOS+1), . . . DATA(1)(EPOS:EPOS), DATA(2)(BPOS:BPOS), DATA(2)(BPOS+1:BPOS+1), . . . DATA(R)(BPOS:BPOS) DATA(R)(BPOS+1:BPOS+1) . . . in that order. Note that the character positions of DATA **other** than the ones shown in the diagram remain unmodified. DATA must be declared at least as CHARACTER*(EPOS) DATA ( R ) with the dimension R being at least R = INT( ( LAST - FIRST + SUBLEN ) / SUBLEN ) and SUBLEN, the length of each of the substrings read into the array elements from the DAS file, being SUBLEN = EPOS - BPOS + 1 ParametersNone. Exceptions1) If the input file handle is invalid, an error is signaled by a routine in the call tree of this routine. DATA will not be modified. 2) If EPOS or BPOS are outside of the range [ 1, LEN( DATA(1) ) ] or if EPOS < BPOS, the error SPICE(BADSUBSTRINGBOUNDS) is signaled. 3) If FIRST or LAST are out of range, an error is signaled by a routine in the call tree of this routine. DATA will not be modified. 4) If FIRST is greater than LAST, DATA is left unchanged. 5) If DATA is declared with length less than ( LAST - FIRST + ( EPOS-BPOS+1 ) ) / ( EPOS-BPOS+1 ) the error cannot be diagnosed by this routine. FilesSee the description of the argument HANDLE in $Detailed_Input. ParticularsDAS is a low-level format meant to store and transmit data. As such, character data in DAS files are not interpreted by SPICELIB DAS input or output routines. There are no limits on which character values may be placed in the virtual character array of a DAS file. This routine provides random read access to the character data in a DAS file. These data are logically structured as a one-dimensional array of characters. However, since Fortran programs usually use strings rather than arrays of individual characters, the interface of this routine provides for extraction of data from a DAS file into an array of strings. DASRDC allows the caller to control the amount of character data read into each array element. This feature allows a program to read character data into an array that has a different string length from the one used to write the character data, without losing the correspondence between input and output array elements. For example, an array of strings of 32 characters can be written to a DAS file and read back by DASRDC into a buffer of strings having length 80 characters, mapping each 32-character string to characters 1--32 of the output buffer. ExamplesThe numerical results shown for this example may differ across platforms. The results depend on the SPICE kernels used as input, the compiler and supporting libraries, and the machine specific arithmetic implementation. 1) The following example demonstrates the capabilities of the DAS character data routines. The reader should notice that in these interfaces, the character data are treated not as strings (or arrays of strings) but as a stream of single characters: DAS character data are not limited to human-readable text. For example, one can store images or DEM data as DAS character data. The example shows how to add a variable amount of character data to a new DAS file, how to update some of the character logical addresses within that file, and how to read that data out to a different array. Example code begins here. PROGRAM DASRDC_EX1 IMPLICIT NONE C C Local parameters. C CHARACTER*(*) FNAME PARAMETER ( FNAME = 'dasrdc_ex1.das' ) CHARACTER*(*) TYPE PARAMETER ( TYPE = 'TEST' ) C C Local variables. C CHARACTER*(22) CDATIN ( 3 ) CHARACTER*(30) CDATOU ( 10 ) INTEGER HANDLE INTEGER I DATA CDATOU / '..............................', . '..............................', . '..............................', . '..............................', . '..............................', . '..............................', . '..............................', . '..............................', . ' 1 2 3', . '123456789012345678901234567890' / C C Open a new DAS file. Use the file name as the internal C file name, and reserve no records for comments. C CALL DASONW ( FNAME, TYPE, FNAME, 0, HANDLE ) C C Set the input data. Note that these data will be C considered as a binary data stream: DAS character data C are not limited to human-readable text. For example, C one can store images or DEM data as DAS character data. C CDATIN ( 1 ) = '--F-345678901234567890' CDATIN ( 2 ) = '--S-345678901234567890' CDATIN ( 3 ) = '--T-IRDxxxxxxxxxxxxxxx' C C Add the last 20 characters of the first two elements C of CDATIN, and the 3rd character from the third one. C CALL DASADC ( HANDLE, 41, 3, 22, CDATIN ) C C Update the 10th, 20th and 30th character in the DAS C file with a vertical bar. C DO I = 1, 3 CALL DASUDC ( HANDLE, I*10, I*10, 1, 1, '|' ) END DO C C Close the file. C CALL DASCLS ( HANDLE ) C C Now verify the addition of data by opening the C file for read access and retrieving the data. C CALL DASOPR ( FNAME, HANDLE ) C C Read the 41 characters that we stored on the DAS C file. Update the data on the CDATOU array, placing C 6 characters on each element, starting from the C 10th position. C CALL DASRDC ( HANDLE, 1, 41, 10, 15, CDATOU ) C C Dump the data to the screen. Note that the last C three lines should remain unmodified, and that C only 5 characters will be written on the 7th line. C WRITE (*,*) WRITE (*,*) 'Data from "', FNAME, '":' WRITE (*,*) DO I = 1, 10 WRITE (*,*) CDATOU(I) END DO C C Close the file. C CALL DASCLS ( HANDLE ) END When this program was executed on a Mac/Intel/gfortran/64-bit platform, the output was: Data from "dasrdc_ex1.das": .........F-3456............... .........789|12............... .........345678............... .........9|S-34............... .........56789|............... .........123456............... .........7890T................ .............................. 1 2 3 123456789012345678901234567890 Note that after run completion, a new DAS file exists in the output directory. RestrictionsNone. Literature_ReferencesNone. Author_and_InstitutionN.J. Bachman (JPL) J. Diaz del Rio (ODC Space) K.R. Gehringer (JPL) W.L. Taber (JPL) VersionSPICELIB Version 1.3.0, 09-OCT-2021 (JDR) (NJB) Added IMPLICIT NONE statement. Added FAILED call following DASA2L call. Updated entries in $Revisions section. Edited the header to comply with NAIF standard. Replaced example code with one that demonstrates the usage and effect of all DAS character data routines. SPICELIB Version 1.2.2, 03-JUL-1996 (NJB) Various errors in the header comments were fixed. SPICELIB Version 1.2.1, 19-DEC-1995 (NJB) Corrected title of permuted index entry section. SPICELIB Version 1.2.0, 03-NOV-1995 (NJB) Routine now uses discovery check-in. FAILED test moved inside loops. SPICELIB Version 1.2.0, 14-SEP-1995 (NJB) Bug fix: reference to DASADS in CHKOUT calls corrected. SPICELIB Version 1.1.0, 12-MAY-1994 (KRG) (NJB) Test of FAILED() added to loop termination conditions. Removed references to specific DAS file open routines in the $Detailed_Input section of the header. This was done in order to minimize documentation changes if the DAS open routines ever change. Modified the $Examples section to demonstrate the new ID word format which includes a file type and to include a call to the new routine DASONW, open new for write, which makes use of the file type. Also, a variable for the type of the file to be created was added. SPICELIB Version 1.0.0, 12-NOV-1992 (NJB) (WLT) |
Fri Dec 31 18:36:11 2021