| dafws |
|
Table of contents
Procedure
DAFWS ( DAF, write summary )
ENTRY DAFWS ( SUM )
Abstract
Write a new summary for the current array in the current DAF.
Required_Reading
DAF
Keywords
FILES
Declarations
DOUBLE PRECISION SUM ( * )
Brief_I/O
VARIABLE I/O DESCRIPTION
-------- --- --------------------------------------------------
SUM I New summary for current array in the current DAF.
Detailed_Input
SUM is the new summary for the current array. This
replaces the existing summary, including the
addresses (the final two integer components) of
the original summary.
Detailed_Output
None.
Parameters
None.
Exceptions
1) If this routine is called when no search is in progress in the
the current DAF, the error SPICE(DAFNOSEARCH) is signaled.
2) If the DAF containing the "current" array has actually been
closed, an error is signaled by a routine in the call tree of
this routine.
3) If the DAF containing the "current" array is not open for
writing, an error is signaled by a routine in the call tree of
this routine.
4) If no array is current in the current DAF, the error
SPICE(NOCURRENTARRAY) is signaled. There is no current
array when a search is started by DAFBFS or DAFBBS, but no
calls to DAFFNA or DAFBNA have been made yet, or whenever
DAFFNA or DAFFPA return the value .FALSE. in the FOUND
argument.
Files
DAFWS updates the DAF currently being searched. The handle
of this DAF can be retrieved using the routine DAFGH.
Particulars
Unless you are reordering the arrays in the file being searched,
you should be using DAFRS instead of this routine.
See also DAFFA, DAFRS.
Examples
None.
Restrictions
1) Calls that do or may change DAF addresses of DAF summaries,
names, or data of a given DAF file should not be made during
a search of that file initiated by either DAFBFS or DAFBBS.
No such changes should be made between the start of a search
and calls to any entry point that reads or writes to the
summary of the "current array" found by that search, or
that returns a "found" flag indicating whether the current
array exists.
Changing the size of the comment area while a search is in
progress can invalidate record numbers stored in local data
structures of this routine. This can cause corrupted array
summaries and names to be returned upon read access and file
corruption to occur upon write access.
Adding arrays (aka "segments") while either a forward or
backward search is in progress can cause the search to miss
the new segments.
Literature_References
None.
Author_and_Institution
N.J. Bachman (JPL)
J. Diaz del Rio (ODC Space)
W.L. Taber (JPL)
I.M. Underwood (JPL)
E.D. Wright (JPL)
Version
SPICELIB Version 2.0.3, 27-OCT-2021 (JDR) (NJB)
Edited the header to comply with NAIF standard.
Updated $Restrictions section.
SPICELIB Version 2.0.2, 18-AUG-2011 (EDW)
Eliminated unneeded $Revisions section.
Removed the obsolete Reference citation to "NAIF
Document 167.0."
SPICELIB Version 2.0.1, 10-MAR-1992 (WLT)
Comment section for permuted index source lines was added
following the header.
SPICELIB Version 2.0.0, 04-SEP-1991 (NJB) (WLT)
Updated to support simultaneous searches of multiple DAFs.
Bug fix made to handle case of having no current array.
This routine now operates on the current DAF---the one at
the head of the active list. All saved state variables
used by this routine are now part of the state table, or
its associated set of pointers.
In addition, this routine now checks whether an array
is current before trying to read its summary. The routine
previously crashed under these conditions.
SPICELIB Version 1.0.0, 28-MAR-1991 (IMU)
|
Fri Dec 31 18:36:10 2021