spks19 |
Table of contents
ProcedureSPKS19 ( S/P Kernel, subset, type 19 ) SUBROUTINE SPKS19 ( HANDLE, BADDR, EADDR, BEGIN, END ) AbstractExtract a subset of the data in an SPK segment of type 19 into a new segment. Required_ReadingSPK DAF KeywordsEPHEMERIS SPK DeclarationsIMPLICIT NONE INCLUDE 'spk19.inc' INTEGER HANDLE INTEGER BADDR INTEGER EADDR DOUBLE PRECISION BEGIN DOUBLE PRECISION END Brief_I/OVARIABLE I/O DESCRIPTION -------- --- -------------------------------------------------- HANDLE I Handle of file containing source segment. BADDR I Beginning address in file of source segment. EADDR I Ending address in file of source segment. BEGIN I Beginning (initial epoch) of subset. END I End (final epoch) of subset. Detailed_InputHANDLE, BADDR, EADDR are the file handle assigned to an SPK file, and the beginning and ending addresses of a segment within that file. Together these identify an SPK segment from which a subset is to be extracted. The subset is written to a second SPK file which is open for writing, and in which a new segment has been started. See the $Particulars section below for details. BEGIN, END are the initial and final epochs (ephemeris time) of the subset. The first epoch for which there will be ephemeris data in the new segment will be the greatest time in the source segment that is less than or equal to BEGIN. The last epoch for which there will be ephemeris data in the new segment will be the smallest time in the source segment that is greater than or equal to END. Detailed_OutputNone. See $Files section. ParametersNone. Exceptions1) This routine relies on the caller to ensure that the interval [BEGIN, END] is contained in the coverage interval of the source segment. 2) If BEGIN > END, no data are written to the target file. 3) If a unexpected SPK type 19 subtype is found in the input segment, the error SPICE(INVALIDVALUE) is signaled. 4) The input segment must have valid structure; this routine may fail in unpredictable ways if not. FilesData are extracted from the file connected to the input handle, and written to the current DAF open for writing. The segment descriptor and summary must already have been written prior to calling this routine. The segment must be ended external to this routine. ParticularsThis routine is intended solely for use as a utility by the routine SPKSUB. It transfers a subset of a type 19 SPK data segment to a properly initialized segment of a second SPK file. The exact structure of a segment of data type 19 is described in the section on type 19 in the SPK Required Reading. ExamplesThis routine is intended only for use as a utility by SPKSUB. To use this routine successfully, you must: Open the SPK file from which to extract data. Locate the segment from which data should be extracted. Open the SPK file to which this data should be written. Begin a new segment (array). Write the summary information for the array. Call this routine to extract the appropriate data from the SPK open for read. End the array to which this routine writes data. Much of this procedure is carried out by the routine SPKSUB. The examples of that routine illustrate more fully the process described above. Restrictions1) This routine relies on the input segment being correct; very limited error checking is performed on the input data. Literature_ReferencesNone. Author_and_InstitutionN.J. Bachman (JPL) J. Diaz del Rio (ODC Space) B.V. Semenov (JPL) W.L. Taber (JPL) I.M. Underwood (JPL) E.D. Wright (JPL) VersionSPICELIB Version 2.0.1, 03-JUN-2021 (JDR) Edited the header to comply with NAIF standard. Removed unnecessary $Revisions section. SPICELIB Version 2.0.0, 04-APR-2017 (NJB) Typo in comment fixed. 11-MAY-2015 (NJB) Updated to support subtype 2. SPICELIB Version 1.0.0, 17-OCT-2011 (NJB) (BVS) (WLT) (IMU) (EDW) |
Fri Dec 31 18:36:55 2021