ADD2MDILOG(1)
NAME
add2mdilog - Add info to MDI_log.
SYNOPSIS
add2mdilog < control_file
DESCRIPTION
Add2mdilog helps to maintain the mission-long basic
MDI status log. This log dataset contains MDI status
for each mission minute.
Add2mdilog takes a time or a range of times, a keyword, and a value.
Input is from stdin a control line at a time. All lines of stdin are processed
with one action per line. The control line contains 3 fields.
1. range of time specified as ascii time or range of time.
2. Keyword to modify.
3. Value for the keyword.
The time specification should be a normal SSSC time spec. TAI is
assumed unless explicitly otherwise. A range may be specified with
a "_" between two times. No spaces are allowed.
If the keyword is begins with a "+" character or a "-" character
that character will be removed and the remaining kwyword will be
the target of selective bits to be set or cleared depending on
the value. In this case the value should be a hex string.
In the special case where the resolved keyword is "MDI_SW" the
corresponding bits in "MDI_SSW" will be set.
The value part extends to the end of the line from the first non-white
character after the keyword.
The MDI_log dataset is maintained as an appendable dataset by the SSSC.
The dataset is a conforming dataset with CONFORMS=TS_EQ, T_BLOCK=1day,
T_STEP=1minute, T_EPOCH=1993.01.01_00:00:00_TAI. The dataset name
template is implied and is:
setenv mdi_log wd:/soidata/info/mdi_log/lev0/MDI_log_01d,bn:{#%06d#series}
The resulting file names are, e.g for the day of launch, day 1065,
001065.record.rdb and 001065.overview.fits
Note that all datasets will be in the same directory.
A copy of the input lines is appended to "history.txt".
control lines beginning with "#" are ignored as comments.
The MDI_SW keyword contains: (see revised TN-135 when ready...)
MDI_SW MDI Status Word, described in revised (TDB) version
of SOI-TN-135. Contains bit flags for general MDI operation
status. In normal operation, this word will have some lower bits
set. Middle bits are for non-nominal operation.
The DSW should be set from MDI operations logs, housekeeping, telemetry
logs, SSSC processing logs, etc.
Some bit assignments are:
SW_MDI_OK (1 << 0) 0x00 MDI operating in normal modes.
SW_DEP_OK (1 << 1) 0x01 DEP prime sequence running
SW_5K_OK (1 << 2) 0x02 5k telemetry being generated OK.
SW_VC2 (1 << 3) 0x04 160k on in VC/2
SW_VC3 (1 << 4) 0x10 160k on in VC/3
SW_ALT_CAM (1 << 5) 0x20 DEP in 30-second structure mode
SW_5K_OK (1 << 6) 5k data received by SSSC from CDHF
SW_160K_OK (1 << 7) 160k data received by SSSC from CDHF
SW_HK_OK (1 << 8) HouseKeeping data received by SSSC
SW_ORBIT_OK (1 << 9) SOHO Orbit data received by SSSC
SW_P_ERROR (1 << 14) Spacecraft position non-nominal
SW_POINT_ERR (1 << 15) Image center off nominal position
SW_T_REF_ERR (1 << 16) Reference time changed
SW_SQID_ERR (1 << 17) Sequence ID changed
SW_ISS_OFF (1 << 18) Image Stabilization system open loop
SW_FOCUS (1 << 19) Focus non-nominal for SQID
SW_OVEN_ERR (1 << 20) Filter oven temp non nominal
SW_CCD_TEMP (1 << 21) CCD Temperature warmer than -70C.
SW_IP_ERR (1 << 22) IP Error detected, often F000 errors.
SW_V_TABLE_ERR (1 << 25) Velocity table not correct for DPCs
SW_FF_ERR (1 << 26) Flat field table not loaded OK
SW_LOI_ERR (1 << 27) LOI V binning table not correct for DPC
SW_LOI_I_ERR (1 << 28) LOI I binning table not correct for DPC
SW_LIMB_ERR (1 << 29) Limb extract region not correct as per DPC.
SW_XTRACT_ERR (1 << 30) HR Extract region not correct per DPC
SW_CROP_ERR (1 << 31) FD Crop region not correct for DPC
MDI_SSW MDI Status Status Word - bits correspond to MDI_SW and are set if
the correcponding bit in MDI_SW is valid.