ISIS 2 Documentation
spicelab - Update SPICE on cube labels Update the keywords on the cube labels with data from the SPICE files for future radiometric and geometric processing. Two types of SPICE files are used: the Event file and the Geom file. The Event files contain information about exposure time, filters, etc. The Geom files contain the camera pointing angles, spacecraft vector, etc. The Event data will only be updated if EVENT='YES'. Also, any values entered by the user for PRODID or NUMBER will be retained even when EVENT='YES'. Programmer: K Teal Thompson, U.S.G.S. Flagstaff, 2 Nov 97
SPICE file name
Output cube name (default extension is .cub)
SPICE geometry file extension (gem,rmb,med,etc)
Update event data (YES,NO)
Look in .gem files (YES,NO) The following parameters are only needed if the values on the labels are wrong:
IMAGE_NUMBER, FSC, FDS, DAS, etc
PRODUCT_ID or PICNO
INSTRUMENT_ID or camera
The SPICE file name is only needed if it does not follow the standard naming convention or is not in $ISISDATA. The naming convention is: dir/planet_mission_camera.ext. Ex: ISISDATA/MOON_CLEMENTINE_1_UVVIS.rmb This parameter is normally used for personal SPICE files.
Output cube file name. If the extension is omitted, then ".cub" will be assumed. This is an existing file and only the labels will be altered.
The extension of the SPICE geometry file name. This can be any of the standard extensions (rmb, gem, swu, cha, med). This parameter will be used if no TBLFROM is entered. The *.rmb files were created by the cartographic group and the *.swu files were created by the photogrammetry group in Flagstaff. The *.cha files were created by the NAIF group at JPL; the *.med files were created by the RAND corporation and the *.gem files were the original files released by JPL during and after each mission.
When EVENT=YES, values from the event file will replace those on the label except for any values input by the user for NUMBER and PRODID. If the user wants to update PLANET or INST, set EVENT=NO. Event data exists for Voyager, Viking and Mariner. The Event data is particularly unreliable for Voyager but the label data has been fairly reliable. For Viking, the Event data has been more reliable than the label data.
Look in .gem files if nothing found in .rmb files for Viking and Voyager missions.
This is the IMAGE_NUMBER on the cube labels. This value is only needed if the value on the labels is wrong.
This is the PRODUCT_ID on the cube labels. This value is only needed if the value on the labels is wrong.
This is the TARGET_NAME on the cube labels. This value is only needed if the value on the labels is wrong.
This is the SPACECRAFT_NAME on the cube labels. This includes the mission name and number such as: VIKING_1. This value is only needed if the value on the labels is wrong.
This is the INSTRUMENT_ID on the cube labels. This value is only needed if the value on the labels is wrong.