OMSANL
This system analyzes 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). First YECMSC is run to create an OMS event file
from the weekly mission schedule. Next, PREPRC is run to produce a
telemetry error file for each aedp subset. This file must exist or
OMSANL will abort. OMSEVT and OMSTLM processes enter sms and telemetry
events into the database OMS_SCHED_TABLE. OMSCHD creates a file listing
telemetry subsets from events in the database table. The file name specifies
a telemetry start and end time on BOACQ boundaries. The start and end time
of each subset in the file file corresponds to the BOF and EOF times in the
PREPROC output file. Each OMSANL run is independent, previous parameters
and events within common blocks are reinitialized at the beginning of a run.
At the end of each run, OMSUPD removes events from the database, enables
archiving of completed subsets, updates the historical database table,
OMS_SU_TABLE and deletes files no longer needed.
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.
Since OMSANL does not modify the database tables, it can run interactively
outside the pipeline environment. Within the pipeline, multiple processes
are allowed.
Format
$ OMSANL i [-w][-c][-r][-g] -f FILENAME [-s]
Parameters
i interactive
This parameter indicates that the command is interactive. Actually any
string without a preceeding dash(-), anywhere within the command
will indicate that the command is interactive.
Note: Interactive commands assume that the mnemonics assigned in the
OPUS_DEFINITIONS_DIR:NULL.PATH file will be used.
-f FILENAME
The name of the AEDP engineering subset file may be specified. This
filename can be wild-carded. Within the pipeline, the directory path
in the resource file is OMS_DATA_DIR. When running interactive, all
files must be in the default directory, except for those in OMS_PDB_DIR
and OMS_INIT_DIR.
Interactively, FILENAME can be a list of subset names. If start and end
times are omitted, the default values are obtained from the PREPRC output
files. If this option is chosen then the qualifier -s should be appended
to the FILENAME.
Qualifiers
-w
The warmstart option is no longer available within the pipeline, a coldstart
is the default and all commons are reinitialized. The warmstart option
was kept for DPT use in recreating operational problems by renaming the
the last SUBSET_MEMORY.DMP file to MEMORY.DMP. A -w will load the common
variables by reading this file. and processing will continue were it left off.
-c
This is the new pipeline default and should be specified when run
interactively. All common variables will be initialized to default values.
-s
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.
-r
Format
$ OMSANL i -c -r -f *.lis -s
-g
This qualifier is required during an interactive run to limit creating
observation logs for observations underway prior to the specified start and end
times, even though all telemetry within the subsets will be processed. When a
START time is other than the BOF time of the first engineering subset (e.g., in
the middle of the subset), very small BM* files will be output in the obslogs
directory specified in the null.path file for all observations whose BOOs occur
between the start of the first subset file and the START time specified on the
command line.
Format
$ OMSANL i -c -g START END -f *.lis -s
START
This qualifier is specified as yyyy.ddd:hh:mm:ss.hhh when processing
missing AEDP files. It will prevent duplicating correct jitter files
that preceded the gap of missing AEDP files.
END
This qualifier is specified as yyyy.ddd:hh:mm:ss.hhh when processing
missing AEDP files. It will prevent duplicating correct jitter files
that followed the gap of missing AEDP files. This time must be later
than START or the command will abort.
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 recentering.
Generally speaking the GS_ACQ information is more observer oriented.
Observation logs
Three observation log files are produced for each observation. The
.JIF file is a FITS binary file containing the jitter image array; the
.CMJ file is a full time-resolution file containing the pointing and
other information in STSDAS table format; and the .JIT file is a
3-second summary of the full resolution .CMJ file with added instrument
specific detail in FITS binary format.
Note: The .JIT is full resolution for exposures less then 3-seconds long.
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, secondary 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 contain 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