Help for OMCOR2

PURPOSE
This program updates the first input IBIS SEDR file by changing 
the OM Euler angles in columns 21,22,23 which define camera
pointing via the OM matrix. "omcor2" performs a global function
minimization of tiepoint residuals by determining the OM
matrices which cause the tiepoints to disagree between image
pairs by a minimum.
 
The GLL flight projects permit very little error in north angle. We suggest
that you use the 'FIT2 parameter to reflect this. Your solutions will improve.

"omcor2" differs from omcor in two ways:
1. Control images are not permitted to move (their OM matrices
   are considered known).
2. "omcor2" permits the use of a zonal velocity flow model to shift
   tiepoints to the common time of the ground control image.
   This permits a global solution for the navigation for non solid
   objects like jupiter. See the ZONAL keyword.
3. The FIT2 keyword permits the north angle to remain fixed for all images.

EXECUTION
omcor2 inp=(SEDR.INT,TIEPOINTS.INT,GEOM.COR)
or-
omcor2 inp=(SEDR.INT,TIEPOINTS.INT)

EXAMPLE: (Galileo)
See mosaicking procedure MANUAL4 in MANMATCH.PDF (Help file).

omcor2 inp=(jupsedr.int,jupmatch.int)      'zonal project=GLL camera=1 'fit2

PRECISION
The differences between the unported and ported VAX test logs and the 
differences between the VAX and UNIX test logs are due to the image
space mode being invoked with object space data.  The discrepency is
probably due to two factors:
1. There is no clear solution (bogus test case) so the solution is 
probably very sensitive to precision.
2. Many transformations are made from image to object space resulting in
small errors which get fed into the minimization scheme.

HISTORY
27 AUG 96  ARV  (CIT)  Added FIT2 capability
10 JUL 95  AMS  (CRI)  Made portable for UNIX