Pre_eros sequence archive information: --------------------------------------- Beneath the pre_eros subdirectory there are 4 subdirectories that represent the major imaging events during the time period from 1996/051 (launch) through 1998/026. These are: /cruisecals_1 This subdirectory contains all sequence and description files for events during time period 1996-051to 1996-178 /mathilde This subdirectory contains all files pertaining to the mathilde flyby (and pre-flyby inflight simulations) which covers time period 1997-115 to 1997-178. /cruisecals_2 This subdirectory contains sequence and description files for time period 1998-210 to 1998-353 /earthmoon_flyby This subdirectory contain all files pertaining to the earthmoon swingby that occurred January 23-26, 1998. >>>> sequence and information files available in the above subdirectories: 1) Imagelists - an imagelist is available for the Mathilde flyby and the Earthmoon Swingby in each respective subdirectory. These are text files that list information about each image, one image for each line. /mathilde/mathildeimagelist.txt /earthmoon_flyby/earthmoonimagelist.txt see also /earthmoon_flyby/earthmoonimagelist.xls 2) Plots - Instrument fields of view plotted against the target. These are available for many of the earth moon and mathilde observations. These files are all .gif files, located in respective /pre_eros/earthmoon_flyby or pre_eros/mathilde subdirectories, and are linked from spreadsheets. 3) Summary Description files - A number of .txt files exist which contain detailed descriptions of the observations. These are linked from the Detailed Description column. 3) STOL scripts - I was able to find the STOL script for most of these sequences. They will be named things like obsv_nameseq.txt and are linked from the Sequence column for each observation. For some of them I had time to edited in descriptive summaries at the top of the file. For all others see below description for interpretation of the STOL. Interpretation of the STOL: Prior to 1998/210, we did not have the use of SEQGEN for building sequences. SEQGEN is a piece of JPL s/w that the NEAR project acquired for use after the Earth flyby. Prior to this all sequences were built by hand in STOL, a simple programming language used for building spacecraft commanding files. I've included all of the STOL scripts I could dig up, but unfortunately there are a few missing. In most cases, I've put a descriptive summary at the top where I try to explain in real words what the sequence intended to do. This is then followed by the STOL. The STOL is actually quite easily interpreted. Refer to the sequserguide.pdf for more explanation of the commands, and parameters. Here are some examples of how to interpret the basic STOL for acquiring images and commanding pointing: 1. First an msi sequence must be defined by loading it into DPU memory. In the following example, the parameters for MSI Sequence Def 1 are loaded: MDLOAD SS_DATA_LOAD 30 MSI CMD MS_DIA_SEQ 1 2 NONE 1 NONE ON FAST 16 MAN \ 10 999 0 0 0 0 0 0 7 7 0 0 0 0 0 0 2) To take the picture(s), the defined sequence must be executed. In this case Sequence 1 is executed at MET 6172289: CMDLOAD SS_DATA_LOAD 0 MSI CMD MS_EXIA_SEQ 1 6172289 #Execute MSI Sequence 1 Slewing commands are also included in the STOL. The two types of pointing data structures we were allowed to use were the DS40 (inertial position), and DS56 (scan pattern). As with the imaging, you must first load the parameters in the data structures, and then execute. Here is an example of a DS40 being loaded into AIU1 (G&C processor): # Macro AB12 Slew to CANOPUS # MACROLOAD MAC_AB12 0xAB12 REL CT_MACT_LD 0 0 PG2 0X8500 CMDLOAD SS_DATA_LOAD 0 AIU1 CMDLOAD AU_TRN_MSG_ACT CMD FC_DS40_URAM_LD \ 0 \ #J2000 (-0.063080) \ #Aimpt_x 0.602696 \ #Aimpt_y (-0.7954735) \ #Aimpt_z 0.0 \ #scRoll_x 0.0 \ #scRoll_y 1.0 \ #scRoll_z 0 \ #use aimpoint 1.0 \ #j2Roll_x (ignored) 0.0 \ #j2Roll_y (ignored) 0.0 \ #j2Roll_z (ignored) 1.0 \ #Boresight_x 0.0 \ #Boresight_y 0.0 \ #Boresight_z 1 #roll@Sun END END The slew is initiated by the following command. It will remain active until overwritten by another set of DS40 parameters. CMDLOAD SS_DATA_LOAD 0 AIU1 # use latest DS40 CMDLOAD AU_TRN_MSG_ACT CMD FC_STRT_GUI_SCN 1 Here is an example of the parameters for a DS56 being loaded into memory: # Macro AB25 Slow Scan; MSI SEQ_2 & SEQ_3 # MACROLOAD MAC_AB25 0xAB25 REL CT_MACT_LD 0 0 PG2 0X8500 CMDLOAD SS_DATA_LOAD 0 AIU1 CMDLOAD AU_TRN_MSG_ACT CMD FC_DS56_URAM_LD \ 0 \ #Closed-loop flag 0 \ #Coordinate_System (J2000) 0 \ #Reverse_Direction_X_axis 0 \ #Reverse_Direction_Y_axis 0 \ #Reverse_Direction_Z_axis 0 \ #Scan_Hold_Placement_X_axis 0 \ #Scan_Hold_Placement_Y_axis 0 \ #Scan_Hold_Placement_Z_axis 300.0 \ #Rate_Duration_X_axis 300.0 \ #Rate_Duration_Y_axis 300.0 \ #Rate_Duration_Z_axis (-9.36E-5) \ #Rate_X_axis 4.68E-5 \ #Rate_Y_axis 4.29E-5 \ #Rate_Z_axis 0.0 \ #Pause_Duration_X_axis 0.0 \ #Pause_Duration_Y_axis 0.0 #Pause_Duration_Z_axis END END The scan is enabled as follows: CMDLOAD SS_DATA_LOAD 0 AIU1 # Enable Scan CMDLOAD AU_TRN_MSG_ACT CMD FC_SCAN ENA END The scan is disabled as follows. When the scan is diabled, pointing returns to the default DS40 inertial position, which in this case was Canopus. # Macro AB35 Slew back to CANPOUS # MACROLOAD MAC_AB35 0xAB35 REL CT_MACT_LD 0 0 PG2 0X8500 CMDLOAD SS_DATA_LOAD 0 AIU1 # Disable Scan CMDLOAD AU_TRN_MSG_ACT CMD FC_SCAN DIS To decode the timing for these commands, you have to look at the macro timing