| IOC-MIPS_110a | 10140C | ||||||||
| Title: | Confirmation of MIPS On-board Data Processing Algorithms | ||||||||
| Objective: | Confirm that the linear regression fits to 24um array data are computed correctly. | ||||||||
| (Note that this should essentially be a repeat of a Thermal-Vac test where the linear regression will also be checked) | |||||||||
| Description: | A star will be observed in each of the 3, 10, and 30 second exposure modes 3 times. | ||||||||
| including flow / state diagram | The observing pattern will need to be executed both using the "raw" data mode where all | ||||||||
| 24um readout are sent to the ground and the normal on-board signal computation. | |||||||||
| The exposure pattern will be executed twice -- once for "raw" mode and once for regular. | |||||||||
| Place in Schedule: | After aperture door is opened and telescope has cooled some. | ||||||||
| (relative to water shed events) | |||||||||
| Required Conditions: | Background at 24um must be less than 7x10^-5 watts/m^2/sr. | ||||||||
| T<45K | |||||||||
| Must be able to place a star within the 5'x5' FOV | |||||||||
| Resources: | |||||||||
| duration (best estimate) | 1 hr | ||||||||
| real time downlink (Y / N) | No | ||||||||
| special post event actions (Y / N) | Yes | ||||||||
| Generates 96 DCEs (assuming each "raw" is one DCE) | |||||||||
| Outcome: | |||||||||
| description | Ground reduction of raw data needs to be compared with on-board results. | ||||||||
| can proceed in parallel with other activity | Yes | ||||||||
| must outcome be confirmed before next event / test /activity | Yes | ||||||||
| method of confirmation (sensor TLM, data analysis, etc.) | Data analysis | ||||||||
| estimate of data turn around if required for confirmation | 48 hrs | ||||||||
| Unique or included in planned AOT? | |||||||||
| Uses a standard MIPS command which may become part of an EOT. | |||||||||
| Second part of test can use the standard photometry AOT. | |||||||||
| Contingency Plan: | |||||||||
| "What if..." | If ground calculation does not match on-board results, then the flight code will have to be examined, | ||||||||
| the bug corrected, and a new flight software image uploaded. | |||||||||
| IOC Critical | Y | ||||||||
| References: | |||||||||
| Template last updated: | 9/10/99 | ||||||||
| M. Rieke | |||||||||