Eros sequence archive supporting file information: ------------------------------------------------- I. Organization of Files Beneath the ../eros subdirectory, the support files have been organized into subdirectories that represent the 'sequence weeks' for the time period starting 1998/210 through end of mission. Eros sequences were usually 1 week in duration. The identifier for the sequence files is a five digit number. The first two digits represent the year, and the last 3 the doy. Example, 00066 references the sequence starting on 2000/066. This identifier (equivalent to the subdirectory name) is listed in the Sequence column for each observation in the spreadsheet. The observation in question was executed from the referenced sequence. The associated files are contained in the subdirectory with that name. Example week: 01036 ----- 01036_final_sasf.txt - This is the SEQGEN input file for 01036 sequencing week. An sasf file is a concatenation of Requests. A Request is a concatenation of CASs (Canned Activity Sequences), one CAS per Activity in the Request. CASs are conglomerations of Fragments. Finally, Fragments are strings of spacecraft and instrument commands. CAS and Fragment definitions (the manner in which Fragments are combined to form specific CASs, and the manner in which commands are combined to form specific Fragments) can be found in the SequencerUserGuide.pdf. In most cases, an 'observation' in the spreadsheet is equivalent to a Request in the sasf file, although sometimes several observations make up a single sasf Request. 01036.msi - command expansion of the above sequence for msi, includes g&c (pointing) (See notes below) 01036.nis - command expansion of the above sequence for nis, includes g&c (pointing) 01036.imagelist - only available for 2000 and 2001 sequences. One line for each image, gives summary info about each image. obsv.gif - plot files (see eros_columns.txt for description of the .gif files) >>> the above 4 file types are not individually linked from the spreadsheet, but the sequence week is linked from the Sequence column. Will take the user to that directory. II. Interpretation of Files a. yydoy_final_sasf.txt The 'sasf' file is a merge of the individual science instrument team inputs to the sequence process for week 'yydoy' as described above. The sequserguide.pdf is a detailed description of how to interpret the MSI and NIS CAS's that you will find in these sasf file. b. yydoy_msi.txt file This file is an output of the STATESIM software. STATESIM was a faster-than-realtime s/w simulator that among other things, expands the above sasf input files into the individual commands and lists them out in a time ordered fashion, one line per command including parameter definitions for that command. The yydoy_msi.txt file is a strip of just the msi and guidance commands. 1) Column description for first 5 columns: Col 1 - doy of ground-received time of execution of the command Col 2 - hh:mm:ss of ground-received time of execuction of the command Col 3 - doy of spacecraft event time of execution of the command Col 4 - hh:mm:ss of spacecraft event time of execuction of the command Col 5 - met of spacecraft event time of execution of the command Here are some examples of how commonly used commands are displayed in this file. 2) Loading the msi filter table and seq defs 30, 29, 28: 185 19:06:28 185 18:59:58 138061028 2 MSI RT f21c (MS_FILTRN_TBL 15308 2000 400 1587 581 1001 279 101) 185 19:06:30 185 19:00:00 138061030 2 MSI RT f217 (MS_DIA_SEQ 30 2 NONE 2 TABLE5 ON FAST 16 MAN 103 0 0 0 0 0 0 0 4 4 0 0 0 0 0 0) 185 19:06:30 185 19:00:00 138061030 2 MSI RT f217 (MS_DIA_SEQ 29 1 NONE 1 NONE ON FAST 16 MAN 999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0) 185 19:06:30 185 19:00:00 138061030 2 MSI RT f217 (MS_DIA_SEQ 28 5 NONE 1 NONE ON FAST 16 AUTO 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0) 185 19:06:30 185 19:00:00 138061030 2 MSI RT f217 (MS_DIA_SEQ 27 1 NONE 1 TABLE5 ON FAST 16 AUTO 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0) 3) Taking an image, Example 1: - the following command loads a timetag which will execute an MSI seq def, 185 19:21:57 185 19:15:27 138061957 3 MSI RT f20a (MS_EXIA_SEQ 27 138062453) This means that at 185/19:15:27, the timetag to execute SEQ 27 is loaded. The first image in this execution of Seq 27 will be taken at 138062453. - after the timetag is loaded, this results in the following two commands (Seq 27 only takes one image): 185 19:29:53 185 19:23:23 138062433 0 MSI Acquisition Sequence 27 sent to imager (1 0 1 5 1 1 16 1 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0) 185 19:30:13 185 19:23:43 138062453 0 MSI Automatic exposure image 0 taken with filter 4 MSI Quaterion: -0.365050 0.058196 0.766213 0.525613 - the first command shows when the Seq 27 is initiated and lists the parameter definitions currently loaded for Seq 27. Seq 27 happens to be the opnav Seq Def, and it is defined to take only one image each time it is executed. - the latter is a line that shows when the image is acquired. This should correspond to the met of the image. The quaternion given is calculated by STATESIM using the best available trajectory. A final STATESIM run was usually made (to produce the files that are archived in this document) after the sequence was already on-board the spacecraft. This final STATESIM run was made using what ever trajectory was on-board when this sequence executed. Thus, the .msi files archived here represent the best, final versions. These quaterions should therefore be pretty good. 3) Taking images, Example 2: - load time tag to execute Seq 21, 253 21:34:47 253 21:25:56 143944988 2 MSI RT f20a (MS_EXIA_SEQ 21 143945214) - issue command to execute Seq 21, which will take 8 images, spaced 3 seconds apart, 253 21:36:03 253 21:27:12 143945064 0 MSI Acquisition Sequence 21 sent to imager (8 0 3 0 1 1 16 0 0 0 0 0 0 0 0 0 1 2 3 4 5 6 7 1) - Seq 21 executes, 253 21:36:13 253 21:27:22 143945074 0 MSI Manual exposure image 0 taken with filter 1 MSI Quaterion: 0.330310 -0.517816 -0.678991 0.402160 253 21:36:16 253 21:27:25 143945077 0 MSI Manual exposure image 1 taken with filter 2 MSI Quaterion: 0.332067 -0.516961 -0.679997 0.400110 253 21:36:19 253 21:27:28 143945080 0 MSI Manual exposure image 2 taken with filter 3 MSI Quaterion: 0.333613 -0.516202 -0.680877 0.398302 253 21:36:22 253 21:27:31 143945083 0 MSI Manual exposure image 3 taken with filter 4 MSI Quaterion: 0.334949 -0.515540 -0.681635 0.396738 253 21:36:25 253 21:27:34 143945086 0 MSI Manual exposure image 4 taken with filter 5 MSI Quaterion: 0.336077 -0.514977 -0.682272 0.395419 253 21:36:28 253 21:27:37 143945089 0 MSI Manual exposure image 5 taken with filter 6 MSI Quaterion: 0.337079 -0.514471 -0.682836 0.394248 253 21:36:31 253 21:27:40 143945092 0 MSI Manual exposure image 6 taken with filter 7 MSI Quaterion: 0.337874 -0.514066 -0.683282 0.393324 253 21:36:34 253 21:27:43 143945095 0 MSI Manual exposure image 7 taken with filter 1 MSI Quaterion: 0.338379 -0.513806 -0.683561 0.392744 4) Taking images, Example 3: - load time tag to execute Seq 29. 186 21:10:27 186 21:03:58 138154868 2 MSI RT f21d (MS_EXIA_SEQ_MLT 29 138154929 4 2) Notice this command is slightly different (...SEQ_MLT). This is the single repeat capability within the MSI DPU. It says, execute Seq 29 for a total of 4 iterations, spaced 2 seconds apart. Seq 29 takes a single image through filter 0, 999ms man exp). But with the SEQ_MLT command it will be repeated. The following commands result. 186 21:11:18 186 21:04:49 138154919 0 MSI Acquisition Sequence 29 sent to imager (1 0 1 0 1 1 16 0 999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0) 186 21:11:28 186 21:04:59 138154929 0 MSI Manual exposure image 0 taken with filter 0 MSI Quaterion: -0.039947 0.558376 0.802651 -0.205846 186 21:11:30 186 21:05:01 138154931 0 MSI Manual exposure image 0 taken with filter 0 MSI Quaterion: -0.039948 0.558376 0.802651 -0.205845 186 21:11:32 186 21:05:03 138154933 0 MSI Manual exposure image 0 taken with filter 0 MSI Quaterion: -0.039948 0.558376 0.802651 -0.205845 186 21:11:34 186 21:05:05 138154935 0 MSI Manual exposure image 0 taken with filter 0 MSI Quaterion: -0.039942 0.558378 0.802646 -0.205859