FILE: SEQ_GEN_TASKS.DOC Things to do during normal Sequence Generation periods ------------------------------------------------------ ----------------------- --Sequence processing-- ----------------------- Whenever an e-mail comes in regarding a new sequence release: don cd get sef.****** bye Get creation date of the file em sef.****** Rename the file ren sef.e11aig sef_970925.uni_e11aig Copy the KT file into the sequence directory idl .run sofq:cpy_kt cpy_kt,'11' exit If cpy_kt does not execute properly, don't worry, just proceed without it. Process the SEF file idl .run sofq:sef_proc This program will crash with an error if the cpy_kt program did not execute properly. That's OK you have already generated the important files. Print out the SEF_strip file print sef_970924.strip_e11aig Highlight the appropriate observations and sections of the STRIP (MWG=yellow AWG=pink SWG=orange) Verify that the observations are correct by cross-checking them with the OAPELS (start/end times, UVS commands, etc). Report any errors that you find to Kent Tobiska at JPL If this is the first release, make start-time GGGS plots of each observation. If not, re-make plots for any observations that had pointing changes appear in this release. ------------------------------ --As-Run sequence processing-- ------------------------------ Sometimes, during the course of an orbit, a situation presents itself that warrants the need to change the sequence while it is actually executing on the spacecraft. Engineers at JPL send "real-time" commands to the spacecraft to correct any problems that they encounter. Since real-time commands are added after the sequence has been uplinked to the spacecraft, we have no record of them in any of our highlighted sequences that we keep here. Months after an orbit has run to completion, JPL produces an "as-run" sequence. This sequence is identical to the sequence that was uplinked to the spacecraft except that it contains any real-time commands that were sent over the course of sequence execution. Once this as-run sequence is released (you will get an email), we can erase any old versions of this sequence from our directories and copy the as-run over. As-run sequences are located on GLLSVC: GLLSVC$UPLINK:[GSC.UPLINK.ARSEF] The G2A as-run sequence, for example, is called: G02A-ARF.SEF Just copy the as-run sequence to the directory it would normally go in, rename it (with its creation date). ren g02a-arf.sef sef_961105.uni_g02a_asrun For the as-run sequences we do NOT need to create all the extra files that are created when processing the regular sequences. The only file that we need to create is the listing of UVS and EUV commands that we will copy into the Command Archive. idl .run sofq:sef_strip sef_strip _asrun> choose (2) for Command Archive strip. Now copy this new file into the command archive with an appropriate header (see seq_uplink_tasks.doc). ------------------------------ --Retrieving OAPELS from JPL-- ------------------------------ Kent Tobiska will send you an email any time new OAPELS are made available. Copy the OAPLINK files from Kent's GLLSVC directory to our ORBIT_DESIGN directory cd diskk:[orbit_design.12] copy gllsvc::gllsvc$data2:[glluvs.gem.12] * Transfer the OAPLINK files to the Macintosh using VersaTerm FT client. Make sure that you transfer the files using BINARY transfer mode Start up OAPLINK. Open the appropriate OAPLINK file When a small dialog box appears with two entry fields, first type the orbit number and then the letters "GTE". Under the PRINT menu, choose SEQUENCE TOL, then ALL OAPEL FORMS. ---------------------------- --Copying kernels from JPL-- ---------------------------- Whenever you receive mail notifying you of a new kernel available at JPL, you may or may not need to copy it over. Only kernels ending in these extensions need be copied: .plt .bsp .rtr When copying platform kernels (.plt) or rotor kernels (.rtr) the filenames must be changed to reflect the kernel's creation date. You also must remember to copy the label files (.plt_lbl .rtr_lbl) for any platform kernels that you bring over (label files do not need to be renamed). cd plt copy gllsvc::$10$DUA4:[GSC.SPICE.CKER.BIN]cke11aig.plt * cd lbl copy gllsvc::$10$DUA4:[GSC.SPICE.CKER.LAB]cke11aig.plt_lbl * ****CKernals may also be located at GLLSVC::$10$DUB5:[GSC.SPICE.GEM.FILES]**** You must rename platform kernels: Run "spacit" to get the creation date out of the comment area of the kernel. ren cke11aig cke11_970925_aig.plt Don't worry about renaming label files or rotor kernels FINAL platform kernels are released as 1 kernel for an entire orbit. All three (or sometimes two) loads of a specific orbit are combined and a single final kernel is released. By the end of the mission these should be the only kernels that we use. You can tell that a kernel is a FINAL kernel by its name. The E11 FINAL kernel would be named: cke11b.plt (don't ask me why the "b", thats just how it is) Get the creation date for this kernel then rename: ren cke11b.plt cke11_971130_final.plt -------- When copying SPK kernels (geometry kernels .bsp), you need to rename the files on our system. Don't forget to copy the labels for these too. cd spk copy gllsvc::$10$DKA200:[GSC.SPICE.SPKER.BIN]s970918.bsp spk_s970918.bsp_1 cd lbl copy gllsvc::$10$DKA200:[GSC.SPICE.SPKER.LAB]s970918.bsp_lbl spk_s970918.bsp_lbl