spke08 |
Table of contents
ProcedureSPKE08 ( S/P Kernel, evaluate, type 8 ) SUBROUTINE SPKE08 ( ET, RECORD, STATE ) AbstractEvaluate a single SPK data record from a segment of type 8 (equally spaced discrete states, interpolated by Lagrange polynomials). Required_ReadingSPK TIME KeywordsEPHEMERIS DeclarationsIMPLICIT NONE INCLUDE 'spkrec.inc' DOUBLE PRECISION ET DOUBLE PRECISION RECORD ( * ) DOUBLE PRECISION STATE ( 6 ) Brief_I/OVARIABLE I/O DESCRIPTION -------- --- -------------------------------------------------- ET I Target epoch. RECORD I Data record. STATE O State (position and velocity). Detailed_InputET is a target epoch, at which a state vector is to be computed. RECORD is a data record which, when evaluated at epoch ET, will give the state (position and velocity) of some body, relative to some center, in some inertial reference frame. Normally, the caller of this routine will obtain RECORD by calling SPKR08. The structure of the record is as follows: +----------------------+ | number of states (n) | +----------------------+ | start epoch | +----------------------+ | step size | +----------------------+ | state 1 (6 elts.) | +----------------------+ | state 2 (6 elts.) | +----------------------+ . . . +----------------------+ | state n (6 elts.) | +----------------------+ Detailed_OutputSTATE is the state. In order, the elements are X, Y, Z, X', Y', and Z' Units are km and km/sec. ParametersNone. Exceptions1) The caller of this routine must ensure that the input record is appropriate for the supplied ET value. Otherwise, arithmetic overflow may result. FilesNone. ParticularsThe exact format and structure of type 8 (equally spaced discrete states, interpolated by Lagrange polynomials) segments are described in the SPK Required Reading file. ExamplesThe SPKEnn routines are almost always used in conjunction with the corresponding SPKRnn routines, which read the records from SPK files. The data returned by the SPKRnn routine is in its rawest form, taken directly from the segment. As such, it will be meaningless to a user unless he/she understands the structure of the data type completely. Given that understanding, however, the SPKRnn routines might be used to examine raw segment data before evaluating it with the SPKEnn routines. C C Get a segment applicable to a specified body and epoch. C CALL SPKSFS ( BODY, ET, HANDLE, DESCR, IDENT, FOUND ) C C Look at parts of the descriptor. C CALL DAFUS ( DESCR, 2, 6, DCD, ICD ) CENTER = ICD( 2 ) REF = ICD( 3 ) TYPE = ICD( 4 ) IF ( TYPE .EQ. 8 ) THEN CALL SPKR08 ( HANDLE, DESCR, ET, RECORD ) . . Look at the RECORD data. . CALL SPKE08 ( ET, RECORD, STATE ) . . Check out the evaluated state. . END IF RestrictionsNone. Literature_ReferencesNone. Author_and_InstitutionN.J. Bachman (JPL) J. Diaz del Rio (ODC Space) VersionSPICELIB Version 2.0.1, 12-AUG-2021 (JDR) Edited the header to comply with NAIF standard. SPICELIB Version 2.0.0, 10-DEC-2013 (NJB) RECORD is now strictly an input; it is not overwritten by this routine. Formerly RECORD was used as a workspace array. SPICELIB Version 1.1.0, 25-AUG-2005 (NJB) Updated to remove non-standard use of duplicate arguments in XPOSEG and LGRESP calls. SPICELIB Version 1.0.0, 14-AUG-1993 (NJB) |
Fri Dec 31 18:36:51 2021