losupport2ck1 Documentation

losupport2ck1 - Convert Lunar Orbiter az, tilt, & swing to NAIF ck
This program reads the Lunar Orbiter azimuth, tilt, swing, subspacecraft
latitude, and subspacecraft longitude from an ascii table and writes
them out to a NAIF type-1 (discreet) camera kernel (c-kernel).

After a c-kernel is created it should be documented by running the
NAIF program commnt.  An ASCII comment file will need to be supplied
to the commnt program.  For an example of the comments see

        /home/dcook/isis/apps/gen/sample_ck_comments.sav

To run commnt type

        /usgs/naif/ctools/exe/commnt

and follow the prompts.

PROGRAMMER: Debbie A. Cook, U.S.G.S., Flagstaff

ASCII input table

NONE

Input NAIF spacecraft clock file
(no default extension)

NONE

Leapseconds kernel

"/usgs/isisd/data/mk98264a.tls"

Planetary constants kernel

/usgs/isisd/data/pck00005.tpc

Binary planetary constants
kernel

Output NAIF type 1 CK
(no default extension)

NONE

Lunar Orbiter mission number

4

NAIF instrument id

NAIF inertial frame of ck data

NONE

Segment identifier string

NONE

Search tolerance

0.0

ADDITIONAL NOTES:

Parm	Description
TBLFROM	This file is an ASCII table file extracted from the Lunar Orbiter Photographic Supporting Data document. It has the following columns: time, spacecraft altitude, subspacecraft latitude, subspacecraft longitude, tilt angle, tilt azimuth angle, and swing angle. All angles are in degrees and distances are in km.
SCLKFROM	This file is a NAIF ascii spacecraft clock file.
LEAPFILE	This is the NAIF leapseconds kernel file needed to convert the start time in the geometry table to ephemeris seconds past J2000 and finally to the encoded spacecraft clock ticks stored in the output c-kernel.
PCKFROM	This file is a NAIF planetary constants file. Should we use the binary or the ASCII pck?
BPCKFROM	This file is a NAIF binary planetary constants file. Should we use the binary or the ASCII pck? I think we need both to match Clementine.
CK1TO	This is the name of the NAIF type-1 camera kernel. It will the contain discreet pointing data from the input file in a single segment.
LOMISS	This is the Lunar Orbiter spacecraft number that will be translated to a NAIF instrument code and used to specify the encoding of the spacecraft clock time.
INSTID	This is the NAIF instrument id for the input data. NAIF supported instrument id's are listed in the file naif_ids.req. MISSION id Lunar Orbiter 1 -531000 Lunar Orbiter 2 -532000 Lunar Orbiter 3 -533000 Lunar Orbiter 4 -534000 Lunar Orbiter 5 -535000
REFFRAM	This is the NAIF code for the inertial frame of the data. Typical values are J2000 or B1950.
SEGID	This is an identifying string to reference the data. Example: "GLL SCAN PLT -- NAIF -- 18-NOV-90" would identify a ck as Galileo Orbiter scan platform pointing created by NAIF on November 18, 1990.
TOL	The search tolerance is used both to screen kernels as well as to locate pointing data for a specific instance in time. The beginning and ending times recorded in the header of the ck created will be the earliest time less TOL and the latest time plus TOL for each segment. This padding prevents times matching the actual first and last entries from failing the ck screening. Probably a value of 1 will suffice.