Help for SPICE

SPICE lists all the information available on an image from any
flight project. This includes the SPICE/SEDR and the image labels.
The program also acts as a test for the following subroutines.
The output of each will be listed under that routines heading:
GETPLACON
GETCAMCON
GETSPICE
GETPROJ
GETGEOM
GETLABCON
CONVISOS

PARAMETERS:

SPICEMODE specifies whether local or remote SPICE access is to be used.
If defaulted, SPICEMODE is set to the value of the logical name (or
environmental variable) DEFAULTSPICE.


PARAMETERS FOR RETRIEVING THE INITIAL CAMERA POINTING:

Initial camera pointing data is first retrieved from predict C kernels or
from MIPS C kernels.  The following optional parameters permit the user to
specify where this initial pointing is retrieved:

CKNAME and CKID are alternative ways to specify the C kernel from which camera
pointing is to be retrieved.  For example, CKNAME=FARE or CKID=M904 specifies
that the camera pointing should be retrieved from the file MIPS_FARENC.CK.
The CKID is the unique kernel ID assigned to each C kernel.  When CKID is
specified, it overrides the CKNAME parameter.  A complete list
of kernel IDs is located in the ASCII file assigned the logical name (or
environmental variable) KERNELDB.


PARAMETERS FOR STORING THE IMPROVED CAMERA POINTING:

The following optional parameters are used to store provenance information along
with the improved (C-Smithed) camera pointing computed by the program.  This
provenance information is stored in the (C kernel) segment identifier for the
camera pointing data.  In cases where there are several versions of camera
pointing for an image in a given C kernel, this provenance information can
later be used to retrieve a specific instance of camera pointing from the
kernel.

PURPOSE identifies the purpose for creating the camera pointing.
REQNUM identifies the request number associated with the camera pointing.
CDATE specifies the date and time the camera pointing was created.
GROUPID identifies the group which created the camera pointing.
INSTITUTE identifies the facility which created the camera pointing.

See the level 2 help (via the TAE tutor mode) for further details.

Examples:  'LOCAL CKNAME=NAIF specifies that SPICE data be retrieved from
          local kernels using camera pointing from predicts or AACS telemetry.
          Improved camera pointing will later be stored in the local C kernel
          specific to this program.

           'REMOTE INSTITUTE=DLR USERID=TYR retrieves SPICE data remotely
          (from MIPS) via the SPICE server.  When improved camera pointing is
          stored (at MIPS), provenance data regarding the facility (DLR) and
          user (Thomas Roatsch) who created the data is included.
 

EXAMPLE:
      spice inp=a.img
PROGRAM HISTORY:
Written By: J Lorre			1/9/89
Cognizant Programmer: J Lorre
REVISIONS:
  25 Jun GMY  Adde call to init_spice (70964)
  29 Jul OAM  Modified to call getspice2 instead of getspice.
              Included provenance parameters.DFR.
  15 Oct OAM  Included the CAMERA parameter to CONVISOS calls.
              FR 89818. 

PARAMETERS:


INP

1.The image to analyze 2.Geom file

TARGET

Optional 12-char string Target name (planet, satellite, or asteroid)

SPICEMODE

Optional keyword Location of SPICE kernels (LOCAL or REMOTE)

CKNAME

Optional 4-char string C-kernel name

CKID

Optional 4-char string C-kernel ID

USERID

Optional 3-char string User who created camera pointing

GROUPID

Optional 3-char string Group which created camera pointing

INSTITUTE

Optional 4-char string Facility which created camera pointing

PURPOSE

Optional 4-char string Purpose for camera pointing

PROGRAM

Optional 6-char string Program which created camera pointing

SPKID

Optional 4-char string SP kernel for created camera pointing

REQNUM

Optional 4-char string IPL request number for created camera pointing

CDATE

Optional 12-char string Date and time camera pointing was created

UPDATE

To update the SEDR/SPICE with subroutine PUTSPICE

DESTINATION

The name to be associate with the SEDR/SPICE

See Examples:


Cognizant Programmer: