Date: February 23, 2007 Reading from the CRM file: We already use the CRM file for checking the pad times. I would like to use this for also recording the correct belt entries and exits, and to check the SI_mode of the diagnostics. Because a RADZONE entry Pseudo code: At the start of the program- read all entries in the CRM file, store two arrays: EEF1000 and XEF1000, record absolute times, pad, and SI_MODE **NOTE pad-checker.pl allows a 7 hour delay for EEF1000/XEF1000 times. Read the backstop: When an RADMON DISABLE entry is found: - check if we are in HRC-S position exit radmon check otherwise - find the closest EEF1000.time to the radmon disable. if((eef1000.time - backstop.time) >= eef1000.PAD and (eef1000.time - backstop.time) <= eef1000.PAD THIS IS THE RADMON DISABLE ASSOCIATED WITH THIS EEF1000 - Record the SI_MODE for the CTI for future. else(THERE IS A RADMON DISABLE NOT NEAR A PREDICTED EEF1000) - Report an error that Radmon is disabled. When an EEF1000 entry is found - check if EEF1000 has been found yet. - Check the EEF1000 entries in the array. if (eef1000.time >= backstop.time-TBD and eef1000.time <= backstop.time+TBD) THIS IS A REAL RADZONE ENTRY - set flag that the EEF1000 has been found(will clear at Perigee) else THIS IS NOT A REAL RADZONE ENTRY - still print out this command to the load review When an XEF1000 entry is found - if(xef1000.time >= backstop.time-TBD and xef1000.time <= backstop.time+TBD) THIS IS A REAL RADZONE EXIT - record the SI_mode for the CTI - if(eef1000 flag not set) -report error that eef1000 was not found -------------------- Psuedo code for the CTI checks: When the code sees HRC-S in the focal plane and the obsid is <=50000, it currently ignores the SI_MODE check. We can change this to look for the RADZONE SI_MODE. These SI_MODES are almost all lookups in our code. We will confirm that the correct parameter block is loaded and this will eliminate the current manual check for this.