Load Reviews |
On December 1, 2011, the FOT uploaded a patch to the OBC to allow for the Science Only Safing Action loads, also known as SOSA or split loads. In these cases, the weekly commands are now stored in 6 SCS slots, 128,129 &130, for vehicle commands, and 131, 132, & 133 for observational commands.
The health and safety of ACIS depends on a series of checks which have been automated over the years. The latest checklist of health & safety and science checks are listed here.
This page is designed to outline the steps and scripts involved in the
load review process as well as direct you to memos that have been
written on this topic in the past. Should you have any doubts about
how current the memos are, assume that this page contains the most
recent methods of a load review (keeping in mind that some memos
explain the manual load review process and could be needed in the
event of a script malfunction).
The working directory for all of the scripts outlined in this
page is: /data/acis/LoadReviews/script/
Jump to:
Nominal Load Reviews
Load Review Steps
Contingency Reviews
To fix these problems you now MAY apply a load letter to the continuity load. You would do this under these two circumstances:
For the first possibility, we can now issue the following lr command: lr SEP2021B SEP2021A
The second possibility has not happened yet but it may. Here is a possible scenario:
There is an OCT0122 A, B and C load
OCT0122B was uplinked to the spacecraft and run
OCT0822A load comes out for review and the Continuity load is therefore OCT0122B
Therfore the command you should issue is: lr OCT0822A OCT0122B
You don't need to specify the continuity load letter under normal circumstances.
Handling this situation requires a new switch to the lr command: --VO (Vehicle Only).
There are two acceptable values for the switch:
All other lr switchology remains the same (e.g. -T, -B, --nolucky, --nomodels etc).
Under the hood, what happens is that lr will save the CR*.backstop
file to ORIG_CR*.backstop and then copy the ....vehicle/VR*.backstop
into CR*.backstop and the review done by lr is on the "new" CR file. The
benefit of this is that when the review load becomes the continuity
load the next week, lr and the thermal models will automatically
process the correct commands.
The LR command would be:
lr --VO VOC Review-load Continuity-load
This will cause lr to use the .../vehicle/VR*.backstop file in the Continuity directory for assembling a history used by lr and the thermal models.
All other lr switchology remains the same (e.g. -T, -B, --nolucky, --nomodels etc).
The FEB0724 load was interrupted with an SCS-107 due to high Solar
Radiation. There was some talk of postponing the Resumption to Science
load until after Sunday. The approved FEB1224 load had already
been uplinked. If the resumption load wasn't going to begin until
after FEB1224 began, only the FEB1224 vehicle load would
have
been activated. This did not subsequently happen but if it did, the handling
of the LR switches for the following Science Resumption Load reviews takes some
care.
This discussion informs you how to handle that situation if it did occur.
Assuming it did happen, the situation, graphically, would have looked like this:
The FEB0724 load was interrupted at 2024:041:03:23:00.00, via an
SCS-107. This means that the Vehicle-Only portion of the FEB0724 load
continues to execute, but the Science Load stops (as indicated by the vertical red line
through the FEB0724 load).
The FEB1224 load was reviewed and approved prior to the shutdown. It
was uplinked to the satellite. If the start time of the Science
Resumption Load occurs
AFTER the start of the of the FEB1224 load,
some commands in the the vehicle-only portion of the FEB1224 load will
execute.
This means that the Science Resumption Load is interrupting the
FEB1224 load just like a TOO load interrupts an executing load. The
command line should look like this (assuming the Science Resumption
Load is FEB1424A):
lr --VO VOC -b FEB1424A FEB1224
Your responses to the LR questions will inform LR that this should be treated as a TOO (i.e. HRC-S was not inserted into the focal plane).
The VOC switch must be included because only the Vehicle-Only commands of the FEB1224 load were activated (in this scenario) so only the vehicle commands should be include in the assembled history.
Ok but what about the SCS-107 cut time? We never specified that to the system because the FEB1224 load was run as Normal. This is now handled by a change in LR. When it detects the situation like the one we have here: we've specified that the continuity file (and if you did so - the Review load) should be run as VO and you have called this a TOO, it will ask you something like this:
Ok this review load: FEB1124A ... is interrupting the FEB1224 as a TOO interrupt but I also notice that the continuity load, MAY1524, is to be treated as vehicle Only. Was the FEB1224 reviewed as a NORMAL load before its continuity load was interrupted by an SCS-107 (either 107-only or Full Stop) and they uplinked FEB1224 as VO just to keep the spacecraft maneuvering until a Return to Science load could be approved? [y/n]If you answer yes, the ACIS-Continuity.txt file of the Continuity load will be adjusted with the SCS-107 cut time.
If there is an unplanned break in the weekly loads, ie: SCS107 or fast TOO, the continuity of the load products is directly affected. In this case, one cannot simply run lr on the contingency load products as if it were a nominal weekly load. If this were done, the ACIS-History.txt file for the interrupted week would be incorrect since the loads would not have reached that point. The ACIS Ops scientist on duty will have to change the lr usage and run history_files.pl
Note that the SOSA changes to the load paradigm allows for a science resumption load to be used as a maneuver only load. Any time the vehicle is still executing commands, the -b/--break switch must be used.IMPORTANT!Please answer these questions: Has the Spacecraft autonomously put HRC-S in the focal plane? (1=no 2=yes) Please enter the interrupt time in format YYYY:DOY:HH:MM:SS.SS
NOTE: It is important to note if this is an SCS 107/Safing Action or a TOO interrupt.
For SCS-107's, and Full Stops, the "interrupt time" required is the time of the SCS-107 execution itself. For TOO's the "interrupt time" is the start time of the TOO load.
For TOOs, answer NO ("1") for the questions about the spacecraft placing HRC-S in the focal plane. For any interrupt where the spacecraft HAS run SCS 107(whether for radiation or safing action), answer YES ("2"). This will correctly set the radmonitor and focal plane states.
For later versions of loads ("B," "C" etc.) the script simply copies ACIS-History.txt from the oflsa directory. From here, the review is exactly the same as described above. The following sections will describe the extra steps involved in a contingency review.
1. In the event of an SCS107 shutdown, the ACIS Ops scientist on duty
will need to run history-files.pl
once the exact time of the shutdown is known so that the ACIS focal
plane history is correct.
Last updated: 01/14/25