IOC-MIPS_105a |
|
|
|
10140C |
|
|
|
|
Title: |
|
|
On-board Software: Command Expansion and Data Manipulation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Objective: |
|
|
To ensure that on-board command sequences expand appropriately, and to |
|
|
|
|
|
|
|
|
ensure that data manipulation proceeds correctly (e.g., Si slope fitting) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Description: |
|
|
We will issue commands that get expanded on board the spacecraft and then monitor |
|
|
|
|
|
|
|
|
the telemetry from the instrument to make sure that the correct commands were issued. |
|
|
|
|
|
|
|
|
All tests will initially be done without using the on-board expansion, so here we will only test |
|
|
|
|
|
|
|
|
sequences that have been run through the system already as individual commands. |
|
|
|
|
|
|
|
|
To test the Si slope fitting, we will observe the same standard star in both RAW and SUR modes, |
|
|
|
|
|
|
|
|
to make sure that ground processing and on-board processing return similar answers. |
|
|
|
|
|
|
|
|
We will perform two photometry observations, one in RAW and one in SUR mode |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Place in Schedule: |
|
|
The telescope does not have to be cold to show that command sequences trigger the correct |
|
|
|
|
|
|
|
|
actions in the instrument, but testing the Si slope-fitting requires the telescope |
|
|
|
|
|
|
|
|
be cold enough to measure standard stars at 24 microns. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Required Conditions: |
|
|
PCS accuracy need only be good enough to get a source on the array (1' is probably ok), but the stability |
|
|
|
|
|
|
|
|
should be good enough that the standard star does not move around on the array during the |
|
|
|
|
|
|
|
|
observation (< 0.6" in 3 seconds). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resources: |
|
|
|
|
|
|
|
|
|
duration (best estimate) |
|
|
|
|
15 minutes |
|
|
|
real time downlink (Y / N) |
|
|
|
|
n |
|
|
|
special post event actions (Y / N) |
|
|
|
|
n |
|
|
|
|
|
|
|
|
|
|
|
Outcome: |
|
|
|
|
|
|
|
|
|
description |
|
|
|
|
produces RAW and SUR data of the same field |
|
|
|
can proceed in parallel with other activity |
|
|
|
|
y |
|
|
|
must outcome be confirmed before next event / test /activity |
|
|
|
|
n |
|
|
|
method of confirmation (sensor TLM, data analysis, etc.) |
|
|
|
|
analysis |
|
|
|
estimate of data turn around if required for confirmation |
|
|
|
|
|
|
|
|
number of DCEs |
|
|
|
|
72 |
|
|
|
|
|
|
|
|
|
|
|
Unique or included in planned uplink or downlink/analysis tool |
|
|
|
|
|
this task should use planned AOTs, although the RAW mode may require a modification to the AOT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Contingency Plan: |
|
|
|
|
|
This is unlikely to make it through ground testing and then fail on orbit, but if it does, we may need a software update, |
|
|
|
|
|
|
|
|
depending on what the problem is. |
|
|
"What if..." |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
IOC Critical |
|
|
|
|
|
Y |
|
|
|
|
|
|
|
|
|
|
|
References: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Template last updated: |
|
|
|
|
|
13-Sep-99 |
|
|
|
|
|
|
|
|
C.W. Engelbracht |
|
|
|
|
|
|
|
|
|
|
|