1 OMSANAL
 This package is a stand-alone version of the OMS analysis software.  That
 system analyses the AEDP engineering subset data in conjunction with the
 mission schedule.  Each engineering event is time stamped, thus one can
 correlate the uplinked commands (mission schedule) with the downlinked
 results (AEDP values).

 The output of this system consists of a large number of ASCII files.  
 These include the instrument specific 'SAVE' files, observation specific 
 log files, as well as several special purpose engineering analysis files.

 Format
	$ OMSANAL[/warm][/cold][/reprocess][/gap] FILENAME[/source]

2 Parameters

FILENAME
 
 The name of the AEDP engineering subset file must be specified.  This
 filename can be wild-carded, and can include a directory path.  In the
 operational environment, these subset files can be found in SUB:[SUBSETS]
 before they have been inserted into the archive candidate list, and in
 BBB:[DAT.SUB] after archive insertion.

 Alternatively FILENAME can be a simple list of filesnames including the
 appropriate directory path.  If this option is chosen then the qualifier
 /source should be appended to the FILENAME

2 Qualifiers

/WARM

 At the end of each run the OMS system dumps a copy of its memory into a
 binary file.  When you next start the OMS system you can elect to initialize
 memory to that state, or to start 'cold' with parameters initialized to
 zeros.

 This capability is important for the OMS system.  One of it's major functions
 is to determined if any engineering parameters have changed their values
 significantly.  If the system has no knowledge of the previous values, one
 can get a number of false warnings.

 However, it is also a dangerous feature.  You don't want to run the system
 with an irrelevant copy of the memory as an initial state.  The system is
 designed to protect the user in this regard: if the initial memory is more
 than an hour old, OMS must be initialized without the 'warm' qualifier.

/COLD
 This qualifier is identical to a /NOWARM qualifier.  OMS memory will not
 be reloaded in this case.

/SOURCE

 This qualifier indicates that the FILENAME specified as the first parameter
 is not an AEDP engineering subset file, but an ASCII list of filenames.
 The software will then open FILENAME and attempt to process each file
 specified in that list.

/REPROCESS

 This qualifier should be given when you wish to reprocess old data and 
 do not wish to produce the SAVE-file information.  This flag causes the
 analysis routine to pass over several calculation steps, speeding up the
 processing.  The observation logs for each observation will be produced
 whether this flag is set or not.

/GAP

 This qualifier is specified to process AEDP files that were missing from
 a previous run. A gap of more than five minutes between AEDP files is
 reported in the log file and a TLM_PROB message appears in header files
 for all observations active during the gap. If the gap is one hour or more,
 then commons are reinitialized. To reprocess missing AEDP files, determine
 which observation has the earliest BOACQ1 time and reprocess this AEDP
 file, and include missing files that coincide with the starting and
 ending gap times reported in the header file. This qualifier forces a
 cold start and prevents corruption of the memory dump file by not reading
 or writing to it. Repoint logicals OMS_OUTPUT_DIR and OMS_PIPELINE_DIR
 to a new empty directory to avoid data corruption. The syntax is

       /GAP=(START,END)
 
 START
 This qualifier is specified as yyyy.ddd:hh:mm:ss.sss when processing 
 missing AEDP files. It will prevent duplicating correct jitter files 
 (CM*) that preceded the gap of missing AEDP files.

 END
 This qualifier is specified as yyyy.ddd:hh:mm:ss.sss when processing 
 missing AEDP files. It will prevent duplicating correct jitter files 
 (CM*) that followed the gap of missing AEDP files. This time must be
 later than START or the command will abort.


2 Output Files

ACQ_TIMING
 A lower lever "autopsy" of all guide star aquisitions, including 
 information on FGS mode, vehicle guiding mode(scheduled and actual),
 FGS search status and radius. It also contains information on all 
 FHST updates, slews, and occultations. Generally speaking the 
 ACQ_TIMING information is more engineering oriented.

AEDP_HEADER
 One AEDP_HEADER file is produced for each engineering subset file
 that OMS reads. It provides information including but not limited to
 the time period covered by a given file, the subset AEDP used to 
 generate the file, the PDB AEDP used to generate the file, and the 
 telemetry format. 

EARTH_AVD
 Contains the time from the moment when the FGS default status is 
 turned ON or OFF to the moment when the vehicle enters or leaves the 
 earth avoidance zone.

FGS_SAVE
 Contains the PMT counts and the FGS star selector angles.
 ** NOTE: In the FN telemetry format, the star selector angles are
 sampled at 20Hz instead of the full 40Hz rate. This was done to avoid 
 interpolating the time and problems with the compressed data. 

GS_ACQ
 A full "autopsy" of all guide star acquisitions and vehicle guidance
 including information on FGS mode, vehicle guiding mode(scheduled and 
 actual), FGS search status and radius, guide stars(i.e. magnitude and
 count threshold), FGS usage, vehicle jitter, statistics on the jitter 
 and PMT counts for each observation, loss of lock, and recenternig. 
 Generally speaking the GS_ACQ information is more observer oriented.

Observation logs (*.cm*)
 Three observation log files are produced for each observation.  The
 CMH file is an ASCII header in keyword format; the CMJ file is a full
 time-resolution file containing the pointing and other information in
 STSDAS table format; and the CMI file is a 3-second summary of the 
 full resolution CMJ file with added instrument specific detail.

OMS_ERRORS
 This file is a log of all SI errors. Red and yellow limits as well
 derived parameters are checked for each SI based on the mode of the
 SI. The mode of each SI is determined from the mission schedule.

OMS_SUMMARY
 A summary of guide star aquisitions including tracking mode, pmt count
 rate, guide star locations, and duration of acquisition. It also
 contains statistics on the jitter and PMT counts for each observation, 
 and loss of lock. Vehicle slews, FHST updates, day/night transitions,
 and earth occultations are reported.

PMT_DARK_CNT
 A one minute average of the PMT count rate as a function of the 
 latitude and longitude of the vehicle when the FGS is not being 
 using for guidance or astrometry is reported.

POWER
 Reports on changes in the bus voltage, battery current, PDU current,
 and the trickle charge.

RECENTER_OBS
 Reports on recentering events only during observations.

RECENTER_OMS
 Reports on all recentering events.

THERMAL
 Selected temperature for the aft shroud, forward shield, light shield,
 primary mirror, seconday mirror, main ring, focal plane, and metering 
 truss are reported on. This is not a "save" file. Maximums, minimums,
 and differences are calculated from equations provided by Lockheed.

HSP/WFPC/FOC/FOS/HRS _SAVE
 These files are simply dumps of all telemetry pertinent to a given SI.
   ** NOTE1: The WFPC and FOC do not conatin every telemetry point 
             relevant to them. The WFPC save set does not contain the
             PROM and RAM telemetry points. The FOC save set is a subset
	     of the FOC telemetry that was defined by the FOC SI engineer. 
   ** NOTE2: All SI save files output a derived sink temperature that is
             calculated by OMS.

