file GLLUVS1:[GLL_RAW.PDS_ARCHIVE]USER_HANDBOOK.DOC May, 2000 - kes Note: This document was written when the Galileo Mission was on a Vax computer. Now that the files are archived on the LASP web site the referenced locations will be different. October 31, 2007 - kes ISSUES: * Update SPICE kernels on CD Disks for PDS * s/w provided: Unix or Vax * making geom files GALILEO UVS/EUV DATA USER'S HANDBOOK This document, the GALILEO UVS/EUV DATA USER'S HANDBOOK, is meant to assist the data user in finding and using data from the Galileo (GLL) project. It is divided into sections, as shown below, which should follow the user's natural search for one or more data sets. The descriptive sections may reference the Appendicies at the end for more detailed lists of files or other information. The material covered here is directed at the user of Jupiter-Operations data (Nominal Mission, Europa Mission and Millenium Mission periods) and may differ for data obtained during the Venus-Earth1-Earth2-Cruise periods, covered in the Operations Appendix. The Operations Appendix, the last Appendix, is a collection of materials originally designed for Operations staff training (usually undergraduates). It is useful in it's overview documents and in understanding the flow of GLL data processing. An index of its topics is included below but no further descriptive information is given except in the Appendix itself. Karen E. Simmons Galileo UVS/EUV Experiment Manager May 4, 2000 GALILEO UVS/EUV DATA USER'S HANDBOOK Chapter I. Finding the data you want A. General Data Information INFO directory GEN_TEMPLATES files PDS Label files B. By time of observation Time.lis (EUV or UVS) _STATUS_.LIS (EUV or UVS) C. By Observation name (OAPEL), type or Target 1. OAPEL naming conventions 2. Within an orbit 3. Oapels and Sequence files 4. TARGETS D. By instrument state (wavelength, etc) CMD_ARCHIVE.LIS looking for F/N/G or by FPNT CMDS_USED.LIS _STATUS_.LIS for EUV or UVS Chapter II. Finding the data files A. Where data files are located B. Other data files and supplemental information Chapter III. Reading data files A. label files give lots on f/t and content information B. formats: header and sci info Chapter IV. Reading Geom files A. Attitude and Articulation Control Sys (AACS) B. Footprint (.FOT) files C. SPICE and GGGS output files (LOS), etc Chapter V. Calibration Chapter VI. Publications Chapter VII. Other Supplemental information UVS Temperature history UVS Tube Exposure History Appendix A - Contents of the TORUS1:[GLL_RAW.INFO] Directory Appendix B - Contents of the GLLUVS1:[GLL_RAW.PDS_ARCHIVE] Directory Appendix C - Contents of GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES] Appendix D - Contents of the TORUS1:[GLL_RAW.INFO.HOW_TO] Directory Appendix E - File naming conventions Appendix F - Contents of TORUS1:[GLL_RAW.INFO.WHERE_ARE] Appendix G - Appendix H - Appendix I - Appendix J - Appendix xx - Galileo UVS/EUV Operations Training Document Who's Who Science Engineering Operations Phone Lists/Emergency Contacts A little history The birth of UVS The cloning of EUV Science Requirement descriptions for each Data Management Why/How When Where Who Data and Sequence Information Accounts Personal Accounts Data Accounts Sequence/History accounts General Rules Spacecraft Basics (NEW Topic) Hardware, main systems (CDS,AACS...), axis definitions S/C Commanding basics Attitude and other Sequence & RT Geometry Predict Knowledge After the Fact Knowledge SPICE Kernels AACS EDR Information The EUV instrument Functional description Components Optical Path Microprocessor software description Operation Modes Cruise Encounter Commanding Construction Commanding Rules Analog Engineering Documentation References Internal The UVS instrument Functional description Components Optical Path Microprocessor software description Operation Modes Commanding Construction Usage Rules Analog Engineering Instrument Calibration UVS General How-To Description Boresight Sensitivity Wavelength General Results EUV General Description General Results Hardware Show and Tell Test and Engineering Models, EUV & UVS BCE Operation and Testing Some Science Results Venus Earth Cruise Boresight Cross-Calibration Lessons Learned Venus/Earth Science Observation Designs What Worked What Didn't Pointing Problems? EUV/UVS Operation PWS Noise Test Results EUV Count Saturation Cruise Science SANTA II Operations EUV Cruise Planning Gaspra to Earth-2 Science Observation Design EUV Observation criteria UVS Observation criteria FOV Alignment Drifting vs Slewing Timing/Frequency Constraints Pointer Observation Design General Overview Input Before the Fact: Source Files During the Design Output Plots, Lists Cross-checking/Updating Gaspra Planning EUV Count Control UVS Count Control Activities of the Various Players LASP Roles Karen's Student's JPL Roles Joe's Steve, Keith, Leslie ******************************************************************** ******************************************************************** Chapter I - Finding the data you want A. General Data Information INFO directory GEN_TEMPLATES files PDS Label files B. By time of observation Time.lis (EUV or UVS) CMD_ARCHIVE.LIS C. By Observation name (OAPEL), type or Target 1. OAPEL naming conventions 2. Within an orbit 3. Oapels and Sequence files 4. TARGETS D. By instrument state (wavelength, etc) CMD_ARCHIVE.LIS looking for F/N/G or by FPNT CMDS_USED.LIS _STATUS_.LIS for EUV or UVS Chapter I.A. General Data Information ### UVS is inst 34 and EUV is inst 24 Galileo was launched on October 18, 1989. At this time, May of 2000, the UVS and EUV instruments have generated a large number of raw, reduced, and supplemental data files and information. Over the years we have created new locations to put these data, sometimes reorganizing to the point where we have lost track of where things are. As the project ends and we take stock, I hope this document will bring together our teams' collective memory of what we have and where it is located. The archival of most these data onto the Planetary Data System (PDS) Atmospheric Node, and subsequent writing of compact disks (CDs) of the data, has added another source for the data; unfortunately the PDS CDs are not organized in the same manner as the LASP archive, especially due to the 8-character-file-name restriction that PDS imposes. I will describe the LASP (Vax) archive and I believe the PDS CDs will be recognizable from there. It is expected that a web-based LASP archive of Galileo data will be available shortly. It will follow the LASP organization, not the CD organization. The PDS established a class of 'meta-data' files (information files) in order to provide a location for additional information about the archived data. The 'label' file is meant to describe the contents of an associated data file, especially for automated access, so it contains keywords, equated to values, to quantify such parameters as times, file size and record length for the data file. The label file accurately reflects the data file. It also contains descriptive information about the data file, for example, how to interpret the time tags on the label file versus the data records. The data label files are generally quite extensive but most of the descriptive information is duplicative. These are all found on the PDS CDs and in the PDS archive directory: GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES]. (See Appendix C.) The CDs contain extensive general information as well. CATALOG files (name.CAT) are PDS meta-data files that describe general information about the mission, instruments, people, software, geometry and calibration. DATASET files (nameDS.CAT) are PDS files containing descriptive information about the data files, especially observation types and mission objectives related to their data files. These PDS meta-data files describe general information about the entire data set, especially GOEUVEDR.DS and GOUVSEDR.DS for UVS and EUV EDR data respectively (see discussion in chapter I.C.). Other PDS meta-data files describe general information, for example team personnel is in GOUEPERS.CAT. These files are all on the PDS CDs and most of them also reside on the GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES] archive directory. A listing of GLLUVS1:[GLL_RAW.PDS_ARCHIVE], the archive directory, appears in Appendix B and the contents of the GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES] is in Appendix C. A good deal of general information is available in the directory TORUS1:[GLL_RAW.INFO]. This includes a general spacecraft time clock definition document, acronym definitions, news-releases, and many subdirectories containing HOW_TO, WHERE_ARE, and similar helpful documents. A list of the contents of the INFO directory is shown in Appendix A. Generally speaking the data is organized, and separated, first by Mission Phase and then by instrument. For example, all pre-Jupiter Phase 1 data for both instruments resides on a separate disk from the data files for Jupiter operations, and beyond (Phase 2). EDR (raw, Experiment Data Records) and RDR (Reduced Data Records) are divided below the instrument. All of the EDR data in a Mission class resides in the same instrument directory. A data file is located by knowing some part of the file name. Most Galileo data files are named by orbit number, the real-time or playback format, and observation ID/name. File nomenclature is described in Chapter II. Chapter I.B. Finding data by time of observation Most new Galileo data users need to find data by time. But most of the Galileo data files are named with a code combining orbit number, the real-time or playback format, and observation ID/name. (See the names in Figure 1.1.) Therefore, there are several per-instrument cross- reference files to locate data by time. The user will find one or another to their liking, each having its unique additional information and format. The two key files for EDR data are in GLLUVS1:[GLL_RAW.PDS_ARCHIVE] and are EUV_BEGIN_END_TIME.TAB and UVS_BEGIN_END_TIME.TAB. Several (128-character, wrapped) lines from the UVS file are: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ S/C UTC S/C UTC S/C Start S/C End Start Time End Time Time Time File Name ******************************************************************************** ********************************************************* 1996-179/05:02:25.563 1996-179/05:07:15.563 3497524:00:0 3497528:71:5 GLLUVS2:[GLL_RAW.UVS_P2]G01A_UPB_AMON__01.DAT;1 1996-179/06:11:10.894 1996-179/06:18:11.894 3497592:00:0 3497598:84:5 GLLUVS2:[GLL_RAW.UVS_P2]G01A_UPB_BRTLMB01.DAT;2 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Figure 1.1 - Example of time reference file UVS_BEGIN_END_TIME.TAB. The user can see that a simple SEARCH (Vax, or Unix GREP) command for a specified time will yield the associated data file name. Both the UVS and EUV files are time ordered by S/C UTC, not Spacecraft Clock (SCLK). A secondary time-to-filename cross-reference are the Status files. During the creation of each UVS and EUV EDR data file, a Status file is generated that lists the record times versus instrument state and housekeeping values. These Phase 2 files are in the data directories. A few lines from the UVS EDR Status file, UVS_RTS_G01_STATUS.LIS;14, is shown here: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ GLLUVS2:[GLL_RAW.UVS_P2]G01A_URT_UVSON___.DAT;4 Record Number: 0 Start Time: 3449656 End Time: 3449686 Stamp Rim Time: 30 U 3449653:45:0 96-145/14:20:03.466 34UVS,07,SCAN,NORM,NORM,NORM,SAME,0,OFF,OF F,ON,OFF,OFF,NOOVR,1,2C,9D,00,00; Fiducial Starting W.L. H-V F H-V N H-V G Limb Sensor Logic Temp. Detector Temp. Rim Time Matches Stamp -------------------------------------------------------------------------------- ----------------------------------------------- 1st Fiducial: Yes 38.86 29.50 28.14 28.11 25.65 14 7.46 158.57 30 Yes 2nd Fiducial: Yes 59.00 29.50 28.13 28.20 25.64 14 7.39 158.48 30 Yes (hex) 3b 2nd wl okay Tube Exposure: f = 0.0 n = 0.0 g = 0.0 Record Number: 1 Start Time: 3449687 End Time: 3451110 Stamp Rim Time: 1423 U 3449653:45:0 96-145/14:20:03.466 34UVS,07,SCAN,NORM,NORM,NORM,SAME,0,OFF,OF F,ON,OFF,OFF,NOOVR,1,2C,9D,00,00; Fiducial Starting W.L. H-V F H-V N H-V G Limb Sensor Logic Temp. Detector Temp. Rim Time Matches Stamp -------------------------------------------------------------------------------- ----------------------------------------------- 1st Fiducial: Yes 5.56 2.25 1.21 1.27 5.97 14 3.55 146.32 1423 Yes 2nd Fiducial: Yes 6.37 2.25 1.24 1.28 6.00 14 3.65 146.43 1423 Yes (hex) 6 2nd wl okay Tube Exposure: f = 0.0 n = 0.0 g = 0.0 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Figure 1.2 - Example of a orbit real-time format UVS Status file. (Note that the 128-character lines wrap around in this firgure.) The files contain information grouped by orbit. They are also grouped, only for UVS, by Playback (PB) versus Realtime (RTS) file formats. For example, the file E11_UVS_PB_ORBIT_STATUS.LIS contains all the playback records available for Orbit E11 and file E11_UVS_RT_ORBIT_STATUS.LIS shows the data records for Orbit E11 realtime format records. The advantage of the STATUS files is that a time is given for each record whereas in the .TAB files, only the beginning and end file times are given. The disadvantage of the STATUS files is the subdivision into orbits. Another time-to-file reference is given in the Index file on each PDS CD. These files cross-reference UTC and SCLK times with file names abd also includes the Target name from the data file label. Chapter I.C. Finding data by observation ID/name, type or Target OAPELs (Orbit Activity Plan ELement) are JPL design documents that indicate the observation objectives, time, target and commanding parameters needed for sequence design. Sets of OAPELs are generated by science teams for every orbit. These design documents are then integrated into a sequence load; OAPEL names (or IDs) become Profile Activities (PAs) during sequence development and they are maintained within the sequence products in order to identify individual science observations. The UVS/EUV team maintains these ID/names on our EDR data files. Often the same name is used in several orbits, in which case the ID may change only by the observed body. (See the file name description in Appendix E for more details on OAPEL (and PA) ID/name construction.) In this way, all of the same type of science observa- tions can be located by searching for one observation ID/name. For Example, the file GLLUVS2:[GLL_RAW.UVS_P2]G01A_UPB_BRTLMB01.DAT;2 in figure 1.1 above, has an OAPEL ID of BRTLMB01. This is the first Bright Limb observation of orbit load G01A. Jupiter Bright Limb observations in following orbits usually have the same ID/name. Extensive descriptions of observation types are given in the UVS and EUV data set files GOEUVEDR.DS and GOUVSEDR.DS located on the PDS CDs and in the GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES] archive directory. These science summaries are also listed by orbit in the TORUS1:[GLL_RAW.INFO.SCIENCE_SUMMARIES] directory. The .DS files also list the data files which belong with the observations. A file, DISKH:[GLLSEQ.HISTORY]TARGETS_SHORT.LIS;3, gives a list of commaned targets, derrived from the load sequences, for a portion of the pre-Jupiter Phase 1 period. It ends at 1993-240. The OAPELs list targets and the commanded targets are also given in the sequence files. Phase 1 sequence files are on directories of DISKH:[GLLSEQ]; Phase 2 sequence files are on GLLUVS2:[GLLSEQ]. There are suppose to be PDS CDs of archived sequence loads too. The central target body can usually be ascertained from the ID/name of the observation and data file, see Appendix E. Chapter I.D. Finding data by instrument state (wavelength, etc) Several choices exhist when the desired data needs to be found by instrument state. For the EUV instrument, the key factor is usually the Fixed Pattern Noise Table (FPNT) which controls the wavelength binning during Phase 2. The EUV instrument file has a good discussion of its use, GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES]EUV_INST.TEMPLATE;7. The data file labels contain which FPNT was used during the observa- tion period within the data file. The observation ID/name is also a good quess as to which was used. To be axact however, the file containing the complete EUV and UVS mission command history, DISKH:[GLLSEQ.HISTORY]CMD_ARCHIVE.LIS should be cross-checked to verify the proper FPNT usage. Since starting sky position, number of sectors and scans per sector are given within the EUV EDR data files, the user is rarely concerned with actually viewing this information because the software takes care of using the values to calculate correct sky coverage. For the UVS instrument the CMD_ARCHIVE.LIS file is still a good choice, since the UVS has more commandable parameters that might be searched for. Which detector is being used, what wavelengths covered, etc. The UVS command is described in the PDS instrument file, in the CD Catalog directory, or in the archive directory at GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES]UVS_INST.TEMPLATE;2. The STATUS.LIS files give the data derrived instrument configuration for each record of data however care should be taken to only trust the values in the second fiducial when dealing with Phase 2 RTS data. (RTS summation and grating flyback can corrupt the first fiducial values.) Late in the GEM period, the reported starting wavelength frequently did not report the actualy position (based on science data.) OAPELs list the configuration to be used but can be in error due to last minute sequence changes that did not get incorporated into the OAPEL sheets. Also, Real-time commanding may effect the actual configuration and is reported only in the CMD_ARCHIVE.LIS file. Especially for the Phase 2 period, a file of those UVS commands that were used in flight is given in TORUS1:[GLL_RAW.INFO.CMD_FORMATS] in the files UVS_BCE_CMDS.LIS;28, commands tested in the lab, and in UVS_FLT_CMDS.LIS;3, commands used in flight. The former file contains a more complete description of the commands. ******************************************************************** Chapter II. Finding the data files A. Where data files are located B. Other data files and supplemental information Chapter II.A. Where data files are located Chapter I describes how to find the file name and Appendix E describes the file naming conventions. Now where to look for these files? The five most-used EDR data directories are: Phase 2 EDR files: GLLUVS2:[GLL_RAW.UVS_P2] - UVS GLLUVS2:[GLL_RAW.EUV_P2] - EUV Phase 1 EDR files TORUS1:[GLL_RAW.UVS] - UVS TORUS1:[GLL_RAW.EUV] - EUV real-time and playback TORUS1:[GLL_RAW.MROH] - EUV cruise memory readout (MRO) Supplemental and browse data resides on the above directories as well. The orbit_STATUS.LIS files are there. The EUV IDL image 'save' files, called EUV_orbit.IDLSAVE (and .XDRSAVE), are in the above directories. The UVS orbit_TOR.SL4 and orbit_JUP.SL4 files, and their labels and .LOG files, are in the Phase 2 UVS directory. (The pre-.SL4) orbit.SL3 files are still there too. Some .AACS files exhist for early Jupiter period orbit files. Chapter II.B. Other data files and supplemental information RDR data that has already been deposited in the PDS archive resides on GLLUVS1:[GLL_RAW.PDS_ARCHIVE] subdirectories, along with their PDS label files. See Appendix B, especially in the [.EUV] and [.UVS] subdirectories. The files in TORUS1:[GLL_RAW.INFO.WHERE_ARE] reference other data sets, software, SPICE kernel files, sequence and orbit design documents. See Appendix F for a list of these files. ******************************************************************** ### Chapter III. The HOW_TO subdirectory is particularly useful once data processing begins. A list of the files there is shown in Appendix B. ******************************************************************** Appendix A The following "info" directory contains invaluable information for the Galileo data user. It contains essential reference information and lots of "How To", "Where Is" and "What Is" documents regarding processing data. Directory TORUS1:[GLL_RAW.INFO] Files: ACRONYMS.LIS Galileo acronym definitions GLL_PHONE.LIS Team and relevant phone numbers PUBLICATIONS.LIS Comprehensive list of papers, talks SPICE_LOGICALS.DOC Defines Vax logicals to make GGGS work TARGETS.DOC Lists UVS targets (until 6-SEP-1994) TEAM_MEMBERS.LIS List team members as of Feb, 1996 TIME_CLOCKS.DOC Describes Galileo s/c time clocks, units TOTAL_COUNTS_AT_JUPITER.LIS Total exposure per UVS tube, by sequence Sub-directories: ARCHIVES Lists of contents from all backup mediums CMD_FORMATS Lists of commands used for flight and during testing HDR_FORMATS Documents format and contents of data file header info HOW_TO Documents describe how to perform many tasks JPL_DOCS Lists Galileo formal docs, various JPL How To docs MICRO_LOADS Contains actual UVS and EUV microprocessor loads NEWS_RELEASES Galileo UVS news articles SCIENCE_SUMMARIES Lists science objectives for each orbit SEQ_INFO Information relative to sequence references, files STAR_TABLES Two tables of UVS stars, used by GGGS WHERE_ARE Lists directories and contents Total of 26 files, 168 blocks. end of Appendix A ******************************************************************** Appendix B GLLUVS1:[GLL_RAW.PDS_ARCHIVE] Main level: ARCHIVE_READ.ME;2 - show directory structure and file name conventions USER_HANDBOOK.DOC - the Galileo UVS/EUV User Handbook PDS_LABEL.PRO - the EDR label file generation (IDL) program EUV_BEGIN_END_TIME.TAB--| the EUV and UVS time index files: | references SCLK, ERT, Target and UVS_BEGIN_END_TIME.TAB--| file names for file, each instr. Total of 12 files, 199 blocks. [.CATALOG] - PDS sample templates Total of 9 files, 326 blocks. [.EUV] [.CALIBRATION] - calibration information and files delivered to PDS Total of 2 files, 2 blocks. [.DELIVERED_LISTS] - contains lists of available data files and delivered files, per orbit Total of 62 files, 483 blocks. [.EDR] - contains the pre-Jupiter MRO files/labels and related lists Total of 52 files, 1339 blocks. [.EDR_TEMPLATES] - PDS data label templates for the EUV Phase1 and Phase2 data Total of 9 files, 246 blocks. [.RDR] Total of 8 files, 17 blocks. [.CRUISE_LYA] - contains the delivered "difference" files from the cruise Lyman-Alpha data sets Total of 180 files, 7889 blocks. [.DOCUMENTS] - docuemnts pertaining to cruise files Total of 2 files, 17 blocks. [.SOFTWARE] - contains EUV programs delivered with the EDR data files, used to read and interpret the EUV EDR files EUV_PLOT_PHASE2.PRO - Contains the IDL routines used to process and plot EUV phase2 data. The main program is the procedure euv_plot EUV_TV.PRO - set of IDL routines that produce the TV images of EUV Lya and H2 that Wayne and Joe like JEREMY_EUV_IMAG.PRO;1 - a little program to display the Savefile image matrix PHASE2_FPNS.DAT - lists the Phase2 Fixed Pattern Noise Tables (FPNTs) TIME_CONV.PRO;1 - SPICE Toolkit (converted to IDL) time conversion routines WRITE_EUV_SAVEFILE.PRO;2 - creates the IDL image Savefile Total of 13 files, 258 blocks. [.GEOMETRY] [.GEN_TEMPLATES] - contains templates for general information and formats, including CALINFO.TXT - how to calibrate UVS or EUV, hints, etc CAL_FILES.LIS - lists the calibration files EUV_INST.TEMPLATE - describes the EUV in detail UVS_INST.TEMPLATE - describes the UVS in detail GOEUVEDR.DS - EUV EDR data set catalog: describes observations per orbit, objectives, etc GOUEPERS.CAT - UVS/EUV personnel GOUVSEDR.DS - EUV EDR data set catalog: describes observations per orbit, objectives, etc GOUEPUBS.CAT - lists UVS/EUV, and other relevent Galileo, publications GOUVSRDR.DS - UVS RDR data set catalog: describes observations per orbit, objectives, etc SOFTWARE.EUV - EUV s/w and how to use it SOFTWARE.UVS - UVS s/w and how to use it and initial templates for the Venus-Earth-Earth UVS and EUV catalogs Total of 21 files, 1113 blocks. [.PDS_DOC_INFO] - contains general PDS information about making labels, data sets, etc Total of 1 file, 10 blocks. [.UVS] - all UVS PDS delivered information Total of 7 files, 25 blocks. [.CALIBRATION] - copies of delivered calibration data files and information Total of 24 files, 123 blocks. [.DELIVERED_LISTS] - lists all available data files and delivered files, per orbit Total of 63 files, 692 blocks. [.EDR] - the (76) pre-Jupiter delivered EDR files and labels Total of 76 files, 274330 blocks. [.EDR_TEMPLATES] - the IDL readable templates that create PDS data file labels Total of 9 files, 244 blocks. [.GEOMETRY] [.RDR] - the delivered pre-Jupiter data files Total of 9 files, 25 blocks. [.ALLSKY] - 3-position difference data sets Total of 16 files, 113 blocks. [.AURORA] - logs/lists of aurora data sets (incomplete) Total of 2 files, 23 blocks. [.BROWSE] - the instrument status files, by orbit, go here Total of 2 files, 61 blocks. [.FEATURE_TRACKS] - logs/lists of feature track data (incomplete) Total of 1 file, 81 blocks. [.MOONS] - satellite RDR data from Hendrix Total of 46 files, 7751 blocks. [.SL9] - Shoemaker-Levy 9 delivered data sets, info Total of 15 files, 528 blocks. [.TORUS] - Io torus data sets (empty) Total of 2 files, 38 blocks. [.VENUS] - delivered Venus AWG data sets, geometry, labels Total of 14 files, 599 blocks. [.RDR_TEMPLATES] Total of 4 files, 64 blocks. [.SOFTWARE] Total of 2 files, 25 blocks. Grand total of 30 directories, 670 files, 296649 blocks. end of Appendix B ******************************************************************** Appendix C Contents of GLLUVS1:[GLL_RAW.PDS_ARCHIVE.GEN_TEMPLATES] CALINFO.TXT;29 CAL_FILES.LIS;1 EUV_INST.TEMPLATE;7 GEOMETRY.TXT;1 GOEUVEDR.DS;16 GOEUVRDR.DS;5 GOUEPERS.CAT;1 GOUEPUBS.CAT;2 GOUVSEDR.DS;24 GOUVSRDR.DS;3 SOFTWARE.EUV;3 UVS_INST.TEMPLATE;2 VEE_E_DS.CAT;2 VEE_U_DS.CAT;4 end of Appendix C ******************************************************************** Appendix D Directory TORUS1:[GLL_RAW.INFO.HOW_TO] GENERAL_HELP_PHASE1.DOC;2 5-JUN-1996 HOW_TO_CALC_MUB_DELAY.DOC;4 18-JUN-1996 HOW_TO_CHECK_CKERNELS.DOC;1 16-JUN-1997 HOW_TO_COMPILE_GGGS.DOC;6 21-JUL-1999 HOW_TO_CREATE_A_CD.DOC;3 12-JAN-2000 HOW_TO_CREATE_RTS_PACKET_TIMES_FILE.DOC;4 21-NOV-1997 HOW_TO_CREATE_TORUS_MODEL_DATE.DOC;1 8-JUN-1996 HOW_TO_DO_BACKUP.DOC;3 24-JAN-1997 HOW_TO_DO_GGGS_DESIGNS.DOC;3 6-JUN-1996 HOW_TO_DO_RADIATION_MODEL.DOC;3 16-AUG-1996 HOW_TO_DO_REMOTE_DISPLAY.DOC;4 11-JUN-1996 HOW_TO_FIND_DATA_STATUS_LISTS.DOC;2 3-JUN-1998 HOW_TO_GET_IPF.DOC;12 28-JAN-2000 HOW_TO_GET_IPF.DOC;11 30-JUN-1998 HOW_TO_LOOK_AT_EUV_DATA.DOC;4 19-JUN-1996 HOW_TO_LOOK_AT_UVS_DATA.DOC;4 25-SEP-1997 HOW_TO_MAKE_ANSA_OBSERVATION_LIST_FILES.DOC;2 1-JUL-1998 HOW_TO_MAKE_EUV_SAVEFILE.DOC;7 13-AUG-1999 HOW_TO_MAKE_PDS_LABELS.DOC;1 4-MAY-1998 HOW_TO_MAKE_SL4_FILES.DOC;1 22-JUL-1998 HOW_TO_PHASE2_AND_GEM_OPERATIONS.DOC;2 1-JUL-1998 HOW_TO_PLOT_RT_UVS_HEADER_INFO.DOC;2 19-NOV-1999 HOW_TO_PRINT_OAPELS.DOC;3 6-JUN-1996 HOW_TO_PROCESS_IPF.DOC;14 29-NOV-1999 HOW_TO_PROCESS_KERNELS.DOC;3 7-JAN-1998 HOW_TO_PROCESS_SEQUENCES.DOC;6 10-NOV-1999 HOW_TO_RESTART_QUERY_DAEMON.DOC;2 23-JUN-1998 HOW_TO_RUN_PRE-JUP_PROCESSING.DOC;1 5-JUN-1998 HOW_TO_SETUP_IPF_PROGS.DOC;6 21-APR-1999 HOW_TO_START_GGGS.DOC;2 5-JUN-1996 HOW_TO_TRACK_TUBE_EXPOSURE.DOC;7 29-NOV-1999 HOW_TO_TRANSFER_OAPELS.DOC;4 5-JUN-1998 HOW_TO_WRITE_READ_IANS_SL3_GEOM_FILES.DOC;7 5-MAY-1998 JEREMY_EUV_IMAG.PRO;3 11-AUG-1999 PB_TABLE_DESC.TXT;1 24-JUL-1996 RT_DATA_PLOT_PROC_INFO.DOC;3 19-NOV-1999 SEQ_GEN_TASKS.DOC;8 6-MAY-1998 SEQ_UPLINK_TASKS.DOC;10 26-AUG-1998 end of Appendix D ******************************************************************** Appendix E - File naming conventions This is a description of the nomeclature and time divisions of the mission phases for the files located in GLLUVS1:[GLL_RAW.PDS_ARCHIVE] and data directories. File Nomeclature: PPP_V#_OBSERVATIONNAME.EXT Where: PPP = Phase Abbreviation (see below) V# = The Software Version## Number During Phase 2 this became a three character URT (Realtime data) or UPB (Playback data) OBSERVATIONNAME = The object that the data pertains to, esp. an OAPEL design name EXT = The file extension. .DAT = data file .LBL = label file .XDR = external data representaton file .LXDR = label for .XDR data file .LIS = listing file .PRO = IDL program file .COM = command file .MRO = memory readout file .SL4 = geometry for UVS/EUV Torus observations .LOG = log of SPICE/GGGS information or other processing record .DIFF = difference data files (esp. cruise Memory ReadOut difference sets) Information: Phase Abbreviation ~ The format is as follows: E1 = Earth one E2 = Earth two VEN = Venus SL9 = Shoemaker-Levy IDA = Ida asteriod JUP, nominal = the nominal Jupiter mission Orbit numbers/loads were used; as C22A GEM = Galileo Europa Mission: E12 - C25 GMM = Galileo Millinium Mission: C26 - C32 Once at Jupiter the phase abreviation changes. The format is: mnn where m = targetted sattelite and can be: G = Ganymede C = Callisto E = Europa I = Io. The first digit represents the targetted satellite for that orbit, the following two digits represent the Jupiter orbit number, from 1 through 32. ## Vax software used to reformat JPL data files was updated from Version 1.0 to Version 2.0 to remove several early processing functions. (For example, Version 1.0 reversed some spectra so that wavelength always increased; Version 2.0 does not alter original instrument sampling in any way.) All phase 1 archive data was created with Version 2.0 software so the file naming convention was deleted. end of Appendix E ******************************************************************** Appendix F - Contents of TORUS1:[GLL_RAW.INFO.WHERE_ARE] Directory TORUS1:[GLL_RAW.INFO.WHERE_ARE] MAP_TO_DIRECTORIES-OLD.DOC 15-SEP-1997 MAP_TO_DIRECTORIES.DOC 3-JUN-1998 NAIF_DIRECTORIES.DOC 2-SEP-1993 WHERE_GEOMETRY_PROGRAMS.DOC 16-SEP-1997 WHERE_IS_EUV_GEOMETRY.DOC 6-JUL-1998 WHERE_TO_FIND.DOC 23-AUG-1999 WHERE_TO_FIND_GGGS_PROGRAMS.DOC 5-JUN-1996 WHERE_TO_FIND_KERNELS-SVC.DOC 1-JUL-1999 WHERE_TO_FIND_KERNELS-UNIX.DOC 7-APR-1999 WHERE_TO_FIND_ORBIT_TIMELINES.DOC 23-MAR-1998 WHERE_TO_FIND_PHASE2_DATA.DOC 13-JUN-1996 WHERE_TO_FIND_SEQUENCE_DESIGNS.DOC 28-MAY-1998 WHERE_TO_FIND_SEQUENCE_FINAL.DOC 28-MAY-1998 Total of 13 files, 97 blocks. end of Appendix F ******************************************************************** Appendix G end of Appendix G ******************************************************************** Appendix H The LAST Appendix - Operations Training manual end-of-Appendix xx