File: TORUS1:[GLL_RAW.INFO]HOW_TO_PROCESS_SEQUENCES.DOC June 4, 1996 - Greg Rutz Update Jan 13,98 -KES for playback loc Update Nov 10,99 -JDA JPL directory info Processing New Sequence Files --------------------------------------------------------------------------- When a new sequence becomes available, there are many different products produced at JPL, some which we need, and some we do not. Sequences can be retrieved via anonymous FTP to donatello.jpl.nasa.gov. New sequences are usually announced through e-mail messages and these messages contain a directory[1] on donatello where the sequence can be found. Sequence files on donatello are in the form: . For examle: the SEF file for G1, Load C, version MA would be called-- sef.g01cma The sequence file types that we keep here are: sef, orpro, seqlog, pa2ef, ssf, pbt The pbt files contain playback tables and are usually only produced for cruise sequences when we have recorded data, so when it is available, get the pbt file as well. ;;Jan 13,98: according to Kent, the Playback tables are at the following ;; location - http://michelangelo.jpl.nasa.gov:82/spot/pbt/gem_pbtdev.html When new sequences become available, grab all of the files that are of the above types. Place the files in their appropriate directory on: pre-Jup orbits on DISKH:[GLLSEQ] GEM orbits on GLLUVS2:[GLLSEQ] as of Apr 1998 ---Processing Sequence Files--- All of the sequence files retrieved from donatello need to be renamed according to the following convention (UNI file): _.uni_ The creation date can be found by opening the SEF or ORPRO files and looking through the header for the date on which it was created. For example: sef.g01cma contains a line in the header that reads: *CREATION 96-124/12:30:18.862 So this file would be renamed as: sef_960503.uni_g01cma All of the sequence files for a single version are normally created on the same day so you can go ahead and rename all of the rest of the files with that same date. ---------SEF files------ To process SEF files, go into IDL from the directory containing the SEF uni file and run DISKH:[GLLSEQ.SOFTWARE]sef_proc.pro At the prompt enter the name of the SEF uni file and the orbit. The program will create the UVS/EUV strip, the AACS strip, check for proper loading of EUV and UVS memory. Next, the program will prompt you for a title for the Command Plot procedure. Command Plot creates a set of plots on which certain commands are stripped from the SEF file and plotted on a time line. You can give the plots any title that you want (the title should, however, contain the orbit, the load, and the sequence version number). A plot will appear on the screen along with a menu. From the menu you can: --Choose to create a certain number of plots: This option allows you to specify a certain number of plots to create in order to expand timelines which have a lot of EUV/UVS commands spaced closely together. --Continue viewing the current series of plots: After you have specified a certain number of plots to create, you can view each of the plots by choosing this option. --Print the current series of plots: Sends the current series of plots to whatever printer you specify. --Skip the current plot session: The Command Plot program allows you to create timeline plots for both EUV and UVS commands. If you decide not to plot either or both of these sessions, you can choose this option. --------ORPRO files------- The ORbit PROfile files are processed by using a different strip program. This program is also in DISKH:[GLLSEQ], it is called pa_strip.pro. Run this program from the directory containing the ORPRO files. Select the UNI file you wish to process and then enter the output filename. The output filename is exactly like the original filename, except that the UNI is replaced by STRIP. -------SEQLOG files------- To process SEQLOG files you simply need to get rid of a lot of the file. Emacs the SEQLOG file and then search for the string "". Leave 15 lines of header at the beginning of the file and erase everything else up to the section that contains the string. Now search for the string "", this will be very near the end of the command section. Erase everything after the command section to the end of the file and then save it. [1] JPL Sequence Directory Descriptions: ex: i24/scg/loadb/otm i24/scg/loadb/rbs i24/scg/loadb/op OTM = sequences that are generated for the Orbit Trajectory Maneuvers - there is no science and no UVS grating activity in these. RBS = sequences that are generated for the Reserve Box where special activities occur; for example the NIMS test and the UVS FSW v7.0 test should be located here. OP = sequences that are generated for the Orbit Plan where these are the "in progress sequences for each orbit encounter and cruise, will normally include our UVS/EUV observations for science and grating, and are NOT the final, uplinked sequences. SCG = sequences that are generated for the Sequence Command and Generation where these are the uplinked versions of the sequences. However, the AS-RUN sequences come a few months later when they take into account what actually happened on the s/c, including realtime commands. For archival purposes, the AS-RUN should be our final sequence that most nearly reflects what we really did.