First input: Vicar image of target body. This image will be copied to the output with a perspective projection label. For WFPC project (space telescope images only) there may be additional input files. These are ascii files with information which can be searched for by PERSLAB. These are the equivalent of the .SHH and .IMH space telescope auxiliary files. To make use of the naif spice these files must be present. If not then you must provide missing information.
The output image containing the perspective label.
NAIF SP kernels filename. This is the ephemeris kernels file for all planetary bodies of interest. Default is: dev2:[gmy059.naif]jup035-hst.bsp
Sub spacecraft planetocentric latitude in degrees. Normally this is obtained from the input label(s).
Sub spacecraft longitude in degrees west. Normally this is obtained from the input label(s).
Sub solar planetocentric latitude in degrees. Normally this is obtained from the input label(s).
Sub solar longitude in degrees west. Normally this is obtained from the input label(s).
Line of planet center. Normally this is obtained from the input label(s).
Sample of planet center Normally this is obtained from the input label(s).
Distance from spacecraft to planet center in KM. Normally this is obtained from the input label(s).
Camera focal length in mm. Normally this is obtained from the input label(s). or from the PROJECT & CAMERA keywords.
Camera scale in pixels/mm. Normally this is obtained from the input label(s). or from the PROJECT & CAMERA keywords.
The angle measured in degrees clockwise from up of the projection of the planet spin axis (north end) normally onto the image plane. Normally this is obtained from the input label(s).
Line of the camera optical axis. Normally this is obtained from the input label(s). or from the PROJECT & CAMERA keywords.
Sample of the camera optical axis. Normally this is obtained from the input label(s). or from the PROJECT & CAMERA keywords.
Date & time of the image in the form: year day_of_year hour minute second. All 5 values are integers. The only use for this field is to pass through getlabcon these 5 integers so that a program like map3 can compute time intervals for zonal flow correction. Consequently use the compatible format to what map3 will receive in it's parameter REFTIME. ie: 1992 versus 92 for example. Normally this is obtained from the input label(s).
Override the project Normally this is obtained from the input label(s). Example: project=WFPC2
Override camera number Normally this is obtained from the input label(s). For flight projects this is the GETCAMCON camera number. For WFPC 1-Planetary camera, 2=Wide field camera.
Override the julian date. Normally this is obtained from the input label(s). Five integers. (year,dayofyear,hour,minute,second) Note that the julian date is used to compute values from the spice navigation files. Unless the project is WFPC1 or WFPC2 the spice computation will be ignored .
Override the julian date. Normally this is obtained from the input label(s). A string of the form: "1994-186 // 11:59:21" Not presently implemented
Override the julian date. Normally this is obtained from the input label(s). Large floating value. See JULDATE restrictions for project ID.
Override the space telescope V1 axis RA direction. Normally this is obtained from the input label(s). In degrees.
Override the space telescope V1 axis Declination direction. Normally this is obtained from the input label(s). In degrees.
Override the space teleccope V3 axis position angle. Normally this is obtained from the input label(s). In degrees.
Ex: TARGET=GANYMEDE specifies that GANYMEDE is the target in the input image. The TARGET may be a planet, satellite, or asteroid. If defaulted, the target name is extracted from the VICAR label or determined by other TBD means. A complete list of valid target names is located in the ASCII file assigned the logical name (or environmental variable) BODY_IDS.
SPICEMODE=LOCAL specifies that SPICE data is to be retrieved from local SPICE kernels. SPICEMODE=REMOTE specifies that SPICE data is to be retrieved via the SPICE server. If SPICEMODE is defaulted, the logical name (or environmental variable) DEFAULTSPICE is used to determine whether LOCAL or REMOTE is used. Note that if SPICE data is not found in LOCAL or REMOTE mode, the other mode is attempted.
CKNAME is a four character string specifying the C-kernel to be used: CKNAME C KERNEL -------- ------------- DAVI MIPS_DAVI.CK NAV MIPS_NAV.CK FARE MIPS_FARENC.CK NAV2 MIPS_NAV2.CK NEAR MIPS_NEAR.CK AMOS MIPS_AMOS.CK NAIF the best NAIF kernel is used If defaulted, the kernels are searched in the above order.
CKID is an alternative way to specify the prefered C-kernel (see CKNAME
parameter):
CKID CKNAME C KERNEL
---- -------- -------------
M906 DAVI MIPS_DAVI.CK
M905 NAV MIPS_NAV.CK
M904 FARE MIPS_FARENC.CK
M903 NAV2 MIPS_NAV2.CK
M902 NEAR MIPS_NEAR.CK
M901 AMOS MIPS_AMOS.CK
varies NAIF there are a large number of these files
Ex: CKID=M901 specifies the four character ID which uniquely identifies the
C-kernel MIPS_AMOS.CK.
A complete list of the C-kernel IDs is located in the ASCII file assigned the
logical name (or environmental variable) KERNELDB.
If specified, CKID overrides the CKNAME parameter.
USERID is a three character string which identifies the user who created the
camera pointing.
Ex: USERID=HBM identifies Helen Mortensen as the creator of the camera
pointing.
GROUPID is a three character string which identifies the group which created the camera pointing. Ex: GROUPID=040 identifies group 040 as the creator of the camera pointing.
INSTITUTE is a four character string identifying the facility which created the camera pointing. Ex: INSTITUTE=MIPS specifies that MIPS created the camera pointing.
PURPOSE is a four character string identifying the purpose of the observation or the purpose of processing. For example, PURPOSE=MOSA identifies the image as part of a mosaic sequence PURPOSE=COLO identifies the image as part of a color sequence
PROGRAM is the first six characters of the program creating the camera pointing. Ex: PROGRAM=FARENC specifies that FARENC created the camera pointing.
SPKID specifies the four character ID which uniquely identifies the SP kernel used to create the camera pointing. The SP-kernel IDs are located in the ASCII file assigned the logical name (or environmental variable) KERNELDB. Ex: SPKID=N015 specifies the SP kernel GLL_LONG_2.BSP
REQUNUM is a four character string identifying the IPL request number for which the camera pointing was created. Ex: REQNUM=3456 identifies (somewhat) request number R123456
Date and time the camera pointing was created in the form 'YEARMMDDHHMM'.
Ex: CDATE=199602291200 specifies that the pointing was created at noon
on February 29, 1996.