sgwes |
Table of contents
ProcedureSGWES ( Generic segments: End a segment. ) ENTRY SGWES ( HANDLE ) AbstractEnd the generic segment in the DAF file associated with HANDLE. Required_ReadingDAF KeywordsGENERIC SEGMENTS DeclarationsIMPLICIT NONE INTEGER HANDLE Brief_I/OVARIABLE I/O DESCRIPTION -------- --- -------------------------------------------------- HANDLE I Handle of a DAF file opened with write access. Detailed_InputHANDLE is the handle of a DAF file opened with write access. This is the handle of the file which contains the generic segment that we wish to end. Detailed_OutputNone. ParametersThis subroutine makes use of parameters defined in the file 'sgparam.inc'. Exceptions1) If there are no generic segments currently being written, the error SPICE(CALLEDOUTOFORDER) is signaled. 2) If there is no generic segment being written to the file associated with HANDLE, the error SPICE(SEGMENTNOTFOUND) is signaled. FilesSee HANDLE in the $Detailed_Input section. ParticularsThis routine will end the generic segment started by a call to either SGBWFS or SGBWVS that is currently being written to the DAF file associated with HANDLE. ExamplesSee the $Examples section in the header for the main subroutine. It contains examples which demonstrate the use of the entry points in the generic segments sequential writer. The entry points which comprise the generic segments sequential writer must be used together in the proper manner. Rather than repeating the examples for each entry point they are provided in a single location. 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.1.1, 03-JUN-2021 (JDR) Edited the header to comply with NAIF standard. Removed unnecessary $Revisions section. SPICELIB Version 1.1.0, 30-JUL-1996 (KRG) (NJB) Fixed an annoying little bug in the variable segments code when ending a segment. Rather than storing an appropriate offset from the beginning of the segment as the packet address in the packet directory, the absolute address, the DAF address, was stored. This bug has been fixed. The address calculations, see the variable MYADDR, were fixed. This involved initializing the variable outside of the loop that scans through the packet data and then incrementing this variable in the same way as PKTADR. The changes were made in two places, for the explicitly indexed case and for the implicitly indexed case. SPICELIB Version 1.0.0, 05-APR-1995 (KRG) (WLT) |
Fri Dec 31 18:36:48 2021