File: TORUS1:[GLL_RAW.INFO]GENERAL_HELP_PHASE1.DOC GALILEO UVS & EUV GENERAL OPERATIONS INFORMATION DOCUMENTATION FOR EARLY MISSION OPS Karen E. Simmons The information in this file describes many aspects of the Galileo UVS/EUV operations. It was designed for a training workshop first held in February 7-8, 1991 at LASP in Boulder, and is being updated thereafter as information changes or is added. The Phase 2 procedures, file locations, etc are more accurately described in separate "HOW_TO..." files in this directory and on the Galileo UVS/EUV Web site at http://miranda.colorado.edu/galileo . - edited April 3, 1991 KES - updated June 5, 1996 KES Discussion Topics 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 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 WHO'S WHO This page updated - see the Web material June 4, 1996 KES Scientists Dr. Charles W. Hord - PI - LASP Dr. Charles A. Barth - CoI - LASP Dr. Larry W. Esposito - CoI - LASP Dr. William E. McClintock - CoI - LASP Dr. Gary E. Thomas - CoI - LASP Dr. A. Ian F. Stewart - CoI - LASP Dr. Joseph M. Ajello - CoI/JPL Team Leader - JPL Dr. A. Lonne Lane - CoI - JPL Dr. Robert A. West - CoI - JPL Dr. A. Lyle Broadfoot - CoI - LPL Dr. Donald M. Hunten - CoI Dr. Bill R. Sandel - CoI - LPL (Tuscon) Dr. Donald F. Shemansky - CoI - LPL (Tuscon) Dr. Wayne R. Pryor - LASP Martin Taylor - LASP - Graduate Student Operations Karen E. Simmons - Experiment Manager - LASP Leslie Tamppari - JPL - 1/2 time UVS Steve Edberg - JPL - 1/2 time UVS Keith Naviaux - LASP - student (1/2 time) Kirk Benell - LASP - student (1/2 time) Jeff Culwell - LASP - student (1/2 time) Engineering Gene McNutt - Experiment Manager - LASP Neil White - LASP Kurt Filsinger - LASP Fred O'Neil - Independent Past Players and Associates Vic Argabright - Engineering Bruce Waggoner - JPL (now IOWA) - Asst. Experiment Rep John Farrar - JPL - engineering Bob Ebbett - JPL - engineering Jack Schwartz - JPL - OET Gaylon McSmith - JPL -OET Pg 1 - Feb 7,91 KES DATA MANAGEMENT WHY * Covert JPL binary and character information for easier use by team * Consistent, central storage of data products and associated information * Provide information about and access to these archives HOW * Data distribution entirely via electronic transfer (SPAN network) * Fortran software for conversion from Univac to Vax and IDL formats * Fortran and IDL quick look analysis and graphics display software (EDRs and EUV cruise memory dump data) * Fortran SPICE (kernel) Toolkit and inhouse software for geometry generation * IDL software for sequence/commanding information processing/archiving * INGRESS data base manager (prototype operational) for data browse and request processing * OPS83 Expert system for Data Certification (prototype operational) * Individual team member's analysis software WHEN UVS/EUV -> S/C -> DSN -> JPL -> LASP |-> Scientists/Engineers -> JOURNALS... |-> ARCHIVES WHERE * Most processing at LASP * Quick look available at JPL on the NERT (Near Real Time) system and on the DTV (Digital Television) display (engineering only) * SANTA prototypes for design of replacement current NERT system * Team member's local sites DSN |-> SFOC (Space Fight Operations Center) (Galileo Prototype) -> SANTA | |-> Engineering DTV system -> DTV display | |-> UNIVAC |-> DMT (Data Management Team computers) -> NERT | |-JPL-ILAN/Microvax-> SVC (Clarke'S Science Vax Cluster) -SPAN-> LASP (ZODIAC::) -SPAN-> Other Team sites (JPL, LPL) Pg 3 - Feb 7,91 KES DATA AND INFORMATION ACCOUNTS GENERAL * Data accounts are "access limited"; only pre-validated accounts are permitted READ access; only data managers have WRITE access * Calibration or general use files must be submitted, with documentation, for placement on these accounts * Protect your passwords * Sequence information is on a separate account * Data management and SPICE Toolkit software reside on a separate accounts * Some information currently resides on non-Galileo disks so access is more difficult (SPICE); will be rectified * Most account directories have READ.ME files containing helpful information; data accounts have summary information files * An attempt is being made to store all pertinent information electronically * Formated and unformated data files are on separate directories * There is a documented Data Management Plan; there is currently no program documentation beyond in-line documentation. Pg 4 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES FILE NAMING CONVENTIONS DATA FILES UVSyydoyhhmm_doyhhmm.DAT - 24 hour process file UVSyydoyhhmm_doyhhmm.TC - UVS temperature data for a 24 hour process file UVS_paname_NOD.DAT - Extracted Observation (named 'paname') data file (_NOD = no Decompression of F-channel data, if present) UVS_paname_NOD.AACS - the associated AACS data for above file's time period EUVyydoyhhmm_doyhhmm.DAT - 24 hour process file: data records EUVyydoyhhmm_doyhhmm.SURF - 24 hour process file: Surface plot matrix (FLTARR(#_SECTORS,128)) EUVyydoyhhmm_doyhhmm.WIB - 24 hour process file: WIB (Wavelength Integration Buffer) array and SIB (Sector Integration Buffer) array (FLTARR(129)) EUVyydoyhhmm_doyhhmm.LIS - 24 hour process file: Error listing from Surface and WIB/SIB processing EUV_paname.DAT - Extracted Observation (named 'paname') data file MROxxxxxx.MROH - EUV cruise Memory Readout file, without header info MROxxxxxx.MRO - EUV cruise Memory Readout file, with header info SEQUENCE FILES SEF_900117.UNI_VE12 - The original SEF (Sequence of Events File) generated on 1990-Jan-17 for the VE-12 (Venus-Earth mission period) SEF_900117.FLAG_VE12 - The above, full SEF file with pertinent items flagged SEF_900117.STRIP_VE12 - The above SEF file striped down to pertinent items ORPRO_900117.UNI_VE12 - The original ORPRO (Orbit Profile) generated on 1990-Jan-17 for the VE-12 (Venus-Earth mission period) ORPLN_900117.UNI_VE12 - The original ORPLN (Orbit Plan) generated on 1990-Jan-17 for the VE-12 (Venus-Earth mission period) Pg 5 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES FILE NAMING CONVENTIONS (Continued) SPICE KERNEL FILES: SPK_yydoyhh_doyhh.BSP - S and P kernel file with begin and end UT time in Years/DOY/HH (Current naming) GLL901204.BSP - JPL naming for Binary S and P kernal files - ??What's it mean: suspect YY+serial number?? SVC Catalog uses these - we will too but with a cross reference file: FILE_INFO.LIS which will indicate begin and end times GLL901204.TSP - JPL naming for Text format (ASCII) S and P kernal files CK_yydoyhr_doyhh.SCANP - C-kernel file for the Scan Platform Actual data with begin and end UT time (Current naming) Some of these have _Load# added to the .SCANP CK_yydoyhr_doyhh.ROTOR - C-kernel file for the Rotot Actual data with begin and end UT time (Current naming) CK_yydoyhr_doyhh.SCAN_PRE - C-kernel file for the Scan Platform Predict data with begin and end UT time (Current naming) CK_yydoyhr_doyhh.ROTOR_PRE - C-kernel file for the Rotot Predict data with begin and end UT time (Current naming) CKyydoyA.PLT_10185 - JPL and SVC Catalog Platform C-kernel naming indicating yy/doy/(A or B) where A=00: to 11:59:00.0 hours and B=12: to 23:59:00.0 hours and a file serial number. SVC Catalog uses these - we will too but with a cross reference file: FILE_INFO.LIS which will indicate begin and end times SSI00012.BC_1 - SSI "smithed" Scan Platform C-kernel with Serial Number (?) Pg 6 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES THE DATA ACCOUNTS disk:directory type ---------------------------------------------------------------------------- DISKK:[GLL_RAW.LRSP] Raw data (transferred from SVC vax LRSP::) SAVED_FILES.TAPE lists everything on archive tapes DISKK:[GLL_RAW.SANTA] Raw, processed data, and software from SANTA prototype for Earth 1 - BEWARE DISKK:[GLL_RAW.EUV] EUV Encounter mode *.DAT Data files *.SURF,*.WIB,*.LIS output/processed data DISKH:[GLL_RAW] A_READ.ME General info on the sub-directory contents DATA_STATUS.LIS Lists data files currently on disks with some processing info DISKH:[GLL_RAW.CALIBRATION] Calibration files READ_ABOUT_CALIBS.ME Sorry, no documentation of these files yet FLIGHT_F_CAL_1.DAT;1 F-channel Flight Wavelength and Sensitivity FLIGHT_G_CAL_1.DAT;2 G-channel Flight Wavelength and Sensitivity FLIGHT_N_CAL_1.DAT;1 N-channel Flight Wavelength and Sensitivity GLL_F_SOLAR_SPECTRUM.DAT;1 Solar Spectrum adjusted to F-channel resolu GLL_G_SOLAR_SPECTRUM.DAT;2 Solar Spectrum adjusted to G-channel resolu SANDEL_PIXEL_FIX_FPN5.DAT;1 Sandel's Hot Pixel (Version #5) corrections UVS_DEAD_TIME.DOC;1 McClintock's UVS F-channel Count Correction DISKH:[GLL_RAW.EUV] Empty, all EUV data moved to DISKK: DISKH:[GLL_RAW.INFO] Data related general information HEADER.INFO Lists EDR/AACS file Header word references (Sorry, currently out of date!) SAGEOM.INFO Gives SAGEOM parameter definitions DISKH:[GLL_RAW.LRSP] Empty, all raw data moved to DISKK: DISKH:[GLL_RAW.MROH] EUV Cruise MROs filename.MROH & filename.MRO general data files EUV_MRO.MAP a cross-reference for MRO dump locations vs (sample x pixel) values TOM_CRUISE.PRO The Cruise analysis program (Barth's name!) START.DAT,STOP.DAT, Cruise analysis tables MRO_FILELIST.LIS (EUV Power On, Off times, file names) DISKH:[GLLSEQ.HISTORY]] Spacecraft Position Information for EUV MROs ALLSPIN_DUALSPIN.LIS lists times of these spin modes (effects EUV sector size) SITURN.LIS lists times of -Z axis adjustments more... Pg 7 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES THE DATA ACCOUNTS (Continued) DISKH:[GLL_RAW.SAGEOM] SAGEOM Predicts (Tables) DISKH:[GLL_RAW.SOLAR] EUV Solar Lyman-alpha Index values READ.ME Documentation information GLL_LYA.DAT IDL format Index file DISKH:[GLL_RAW.SPICE_KERNALS] SPICE kernels FILE_INFO.LIS Lists kernel file names vs UT begin and end times DISKH:[GLL_RAW.TC] UVS temperature data DISKH:[GLL_RAW.UVS] UVS spectra data *.DAT data files *.AACS AACS data for times of data files COMMAND, SEQUENCE, AND DOCUMENT ACCOUNTS DISKH:[GLLSEQ.*] Planning, Sequence and History Information [main] Command construction (cook-book) examples [.load] each mission load period on a separate directory [.GENERAL_INFO] Electronic SRD (Science Requirements Doc) updates, mission planning requests, OAP (Orbit Activity Plan) info [.HISTORY] Mission History directory CMD_ARCHIVE.DOC Archive of all EUV and UVS commands [.LIB] Files containing copies of PA (Profile Activity) documentation, on-board Library Sequences, FPN (EUV Fixed Pattern Noise table) loads, memory loads DISKH:[GALILEO.DOC] Galileo Mission Document Inventory JPL.DOC File lists what 625- documents we have here at LASP/campus more... Pg 8 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES THE SOFTWARE ACCOUNTS DISKH:[GLL_RAW.NAIF_TOOLKIT] Second of three Toolkit deliveries (Oct,90); has no C-kernel or Galileo specific software. Use the one on [GEOM] DISKH:[GLL_RAW.SOFTWARE] General purpose analysis software Sorry, no documentation yet and mostly still in development DISKG:[GEOM.NAIF.TOOLKIT...] All NAIF (Navigation and Ancillary Information Facility) supplied SPICE Toolkit software See the SPICE TOOLKIT ACCOUNT pages for much more detail THE BROWSE CATALOG DISKH:[GLLCAT] The INGRESS programs, browse files, etc; BEWARE: this is a prototype and has not been documented or recently updated THE SVC SPICE KERNEL AND TOOLKIT CATALOG PRINCE::DUA1:[GSC] To use the catalog you must have a PRINCE account. Ask for help if you want to browse this system instead of ours. Pg 9 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES THE SPICE TOOLKIT ACCOUNT DISKG:[GEOM] | +---------------+----------------+ | | [.NAIF] [.BUILD] VAX_INSTALL.TXT PORTING.TXT VAX_LIBSUM.TXT | +-----------------+ | | [.TOOLKIT] [.DATA] | | GLL00002.TLS (Text) Leap Seconds | GLL00002.TPC Planetary Constants | GLL00003.TPC new Planetary Constants | GLL00003.TSC Spacecraft Clock | GLL_LONG_2.TSP S & P kernel sample | GLL25001.TI I-kernel, Instrument #25 | GLL28001.TI | GLL29001.TI | GLL34001.TI " " for UVS | GLL36001.TI | GLL37001.TI | +--------+--+---------+---------+-----------+---------+ | | | | | | [.SPICELIB] [.SPACIT] [.SIMPLE] [.SPTEST] [.COOKBOOK] [.VISTA] | | (A description of the contents of each of these | product directories is given below this | structure.) +------------+ | | | [.REQ] [.SOURCE] [.TXT] | *.REQ + | [.VAX] *.FOR SPICELIB.OLB MAKE_SPICELIB.COM The contents of each program product directory is listed below. more... Pg 10 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES THE SPICE TOOLKIT ACCOUNT SPACIT - A program to convert Text formated data file to Binary formated files, and reverse (for non-Vax network transfer) and a useful tool for browsing kernel data files. [HOME.NAIF.TOOLKIT.SPACIT] | + | [.VAX] SPACIT.MAIN *.FOR MAKE_SPACIT.COM SPACIT.UG SPACIT.EXE SPTEST - A program to test S & P kernel data files [HOME.NAIF.TOOLKIT.SPTEST] | + | [.VAX] SPTEST.MAIN GEN.3 GLL_TEST1.TSP TEST.3 MAKE_SPTEST.COM SPTEST.UG SPTEST.EXE VISTA - A catalog type program to assist in finding Toolkit software routines that match the user selected browse choices. [HOME.NAIF.TOOLKIT.VISTA] | [.VAX] VISTA.MAIN *.FOR MAKE_VISTA.COM VISTA.COM VISTBL.DAT VISTA.EXE more... Pg 11 - Feb 7,91 KES This page updated - see MAP_TO_DIRECTORIES.DOC June 4, 1996 KES THE SPICE TOOLKIT ACCOUNT COOKBOOK - A group of cookbook routines. See the Required reeding documents. [HOME.NAIF.TOOLKIT.COOKBOOK] | + | [.VAX] FSTSPK.MAIN STATES.MAIN SUBPT.MAIN TIME.MAIN FSTSPK.UG STATES.UG SUBPT.UG TIME.UG COOK_01.TC COOK_01.TLS COOK_01.TSC COOK_01.TSP MAKE_COOKBOOK.COM FSTSPK.EXE STATES.EXE SUBPT.EXE TIME.EXE Pg 12 - Feb 7,91 KES LASP Generated NAIF Toolkit/SPICE Routines The directory DISKH:[GLL_RAW.SOFTWARE.CU_SPICE] contains software developed at LASP for use of the Navigation and Ancillary Information Facility (NAIF) generated Toolkit software. The Toolkit software uses the Galileo (and other project generated) SPICE kernels. The term SPICE stands for the type of kernel (or vector) data sets needed to describe all the geometry necessary for spacecraft location, look direction and ephemerides. The acronym stands for: S = Spacecraft location P = Planetary ephemerides I = Instrument information, primarily boresight reference C = C-matrix Pointing offsets from spacecraft axes E = Experiment operation type information Each program in this account has an executable file (files ending with .EXE) and a documentation/use file (ending in .DOC). Each set of these files also corresponds to the Fortran source file of the same name (ending in .FOR) located in the subdirectory DISKH:[GLL_RAW.SOFTWARE.CU_SPICE.SOURCE], for your added reference. The .DOC files indicate what logicals must be defined, what information must be supplied to the routine, a general description of the routine and any additional cautionary information. The raw kernels are located in the directory DISKH:[GLL_RAW.SPICE_KERNALS] and the NAIF software source routines, along with some of the clock and ephemeride kernels, are located on the account DISKG:[GEOM.NAIF...]. Some output files generated by these programs are already available on the directory DISKH:[GLL_RAW.SPICE_OUTPUT]. You should look at the contents of these tables to see if your case has already been executed. (Note too that the directory DISKH:[GLL_RAW.SAGEOM] may contain JPL generated geometry tables of interest. File nomenclature hints, along with general information, is described in a file DISKH:[GLL_RAW.INFO]GENERAL_HELP.DOC. A command file which establishes the logicals necessary to run routines in this directory is in the file SPICE_LOGICALS.COM. You should execute this command file before running any routine. Use the Vax command: @SPICE_LOGICALS Pg 12a - Apr 3,91 KES GEOMETRY KNOWLEDGE PREDICTS * We have some SAGEOM tables of body distances and angles There is no generation documentation supplied with these * POINTER provides knowledge but is readily available in a usable form to LASP science designers * Eventually will be able to use SPICE# predict kernels to develop observation design tables/graphics AFTER THE FACT * AACS (Attitude and Articulation Control Subsystem) information in EDRs (Experiment Data Records) * one minor frame resolution (at RTI=0) * Still some unknowns about axis reference frames, magnitudes (signed or un-signed integers); lack of documentation (is it written down and if so then where? * Still need to correlate with predicted knowledge; have at least seen "limit cycling" of Rotor (Ra,Dec) on the order of 0.1 degree at about 10 deg in Dec. * Will be able to cross check with EUV sectoring * The 12 parameters of AACS are as follows: 1 = Rotor attitude -- RA (0-360 deg) 2 = Rotor Attitude -- DEC (-90 to +90 deg) 3 = Rotor Attitude -- TWIST (0-360 deg) 4 = platform attitude -- RA (0-360 deg) 5 = Platform Attitude -- DEC (-90 to +90 deg) 6 = Platform Attitude -- TWIST (0-360 deg) 7 = Platform Rate -- CONE (-90 to +90 deg) 8 = Platform Rate -- CROSS CONE (-90 to +90 deg) 9 = Rotor Spin Motion Delta assume (0-360 deg) 10 = Rotor Spin Position Angle assume (0-360 deg) 11 = S/C Relative Cone (0-360 deg) 12 = S/C Relative Clock (0-360 deg) NOTE: there is a Phase 2 update to these AACS contents * SPICE# Kernels for spacecraft location, body locations and pointing knowledge * We now (appear) to have all necessary kernel and toolkit software * We are building and testing software and geometry data sets # SPICE stands for the 5 necessary vectors to determine spacecraft location and look direction geometry knowledge: S - Spacecraft position vector P - Planet (body) position vectors and constants I - Instrument knowledge, like Field of View size and orientation C - The "C matrix" which represents the scan platform look vector E - Event knowledge, such as tape recorder usage therefore jiggle Pg 13 - Feb 7,91 KES DOCUMENTATION REFERENCES [1] Galileo UVS Functional Requirement Document GLL-625-205, 4-2034, Rev A of 10 April 1989. [2] Galileo EUV Functional Requirement Document GLL-625-205, 4-2024, 14 August 1989. [3] "Galileo UVS Calibration Report, Preliminary Version" by William McClintock, dated March, 1989. [4] UVS/EUV instrument paper, Draft version, 6 Feb, 1991. by Charles W. Hord, et al. Submitted to Space Science Reviews. [5] Galileo EUV Data System Functional Specification by Fred O'Neil, Revision E of November 3, 1989. [6] SPICE KERNEL ``Required Reading'' files, released by NAIF, available on the Toolkit directory: ZODIAC::DISKG:[GEOM.NAIF.TOOLKIT.SPICELIB.TXT]*.REQ [7] READ.ME files on various accounts [8] Galileo Science Requirements Document, especially Sections 2, 4, and 5. GLL-625-50, Revision D, 18 January, 1989. INTERNAL * Remember to leave a `paper trail': document what you do and keep at least a copy in your own records. Example: Real Time Command Requests * Put the date (spelled out) and your initials on any work * Distribute copies to appropriate groups * Update the documentation when changes are made Example: OAPEL designs Pg 18 - Feb 7,91 KES THE EUV INSTRUMENT FUNCTIONAL DESCRIPTION * Voyager UVS Spectrometer Detector Some Electronics: Timing and Control, Accumulator Logic * Added Microprocessor and RAM New FDS (Voyager's Flight Data System) to Micro interface, Analog Multiplexor, CDS (Command and Data Subsystem) Bus New Low Voltage Power Supply OPTICAL PATH (See Figure) * Cover is (permanently) deployed (Dec, 1989) * Optical path to detector is "open" * Field of View is a slit: 0.87 by 0.17 degrees * Slit is oriented so that short side sweeps as Rotor turns (long axis is parallel to -Z axis) MICROPROCESSOR SOFTWARE NOTE: Phase 2 and Phase 1 are quite different; be sure to check * Micro is an RCA 1802 * 4k bytes RAM * Program takes 1279 bytes * Buffer usage depends on mode * Interrupt driven * Returns 12 bytes of data each 2/3 of a second * Instrument's natural time period is 20.8 milliseconds; the amount of time to read all pixel locations once * Always operated in Pulse Count Mode (never Pulse Integration) * High Voltage levels are selectable to adjust sensitivity * 16 analog engineering values are multiplexed to one channel monitored by the CDS and placed in the engineering packet of the telemetry, once per RIM. Items listed in Functional Requirements document Table 1. * Orientation/sectoring EUV uses AACS sector definition: Spin angle=0 when -X axis crosses North Ecliptic Pole and monitors AACS spin angle to control sky sector knowledge EUV thinks starting sector 0 is 45 degrees before North Pole * Encounter Mode The detector address (pixels 0 to 127) of each photon event is returned The top bit of each byte is used for coding sky sector crossings A Wavelength Integration Buffer (WIB) and Sector Integration Buffer (SIB) are kept on-board (16-bit registers) and are read out periodically in the Housekeeping data more... Pg 20 - Feb 7,91 KES THE EUV INSTRUMENT (CONTINUED) * Cruise Mode Analog engineering and housekeeping continue to be returned 1264 bytes for data buffer and FPNT (Fixed Pattern Noise Table) Buffer space is divided up to hold [(number of pixels X number of sky sectors) X (sector size integration factor)]. See table in EUV Software reference. BEWARE: make sure you get the latest copy, earlier table is invalid. Pixels are selected by loading the FPNT with consecutive numbers in the table locations of the desired pixels. Desired photon events are placed into buffer; others are discarded Data acquisition is accomplished by `memory dump' (called Memory Readout, or MRO) to the CDS engineering telemetry stream MROs include the Fixed Pattern Noise Table in order to document which pixels are selected and are thus contained in the buffered data COMMANDING * The EUV command PA (Profile Activity) has changed since launch to accomodate new microprocessor software capable of Cruise Mode operation (necessary when downlink rate does not contain Low Rate Science (LRS) packets, the normal telemetry allocation; below 9600 bits per second.) * Originally had to command Cruise Mode with a Direct Memory Load (DML) command in order to set the Encounter/Cruise bit = 1 * Seven parameters are necessary: Pulse Mode : always use 1 for Pulse Counting High Voltage : 3 is the normal (range is 0 to 7 but a Fight Rule limit is 4; 0 = High Volts Off) Cruise/Encounter : default is Encounter Mode (=1) Start Integration Spin Position : a hex value up to 7F (avoid 0) Sector Size : a hex value up to 7E (avoid 0) Number of Sectors : a hex value up to 7E (avoid 0) Pg 21 - Feb 7,91 KES THE UVS INSTRUMENT FUNCTIONAL DESCRIPTION OPTICAL PATH (See Figure) * Two Fields of View: N & G are (physically) 1.3 x 0.1 deg N & G are (effectively) 1.0 x 0.1 deg F is (physically) 0.4 x 0.1 deg F is (effectively) ___ x 0.1 deg * Slit is oriented so that short side sweeps as Cone changes (long axis is parallel to -Y axis) MICROPROCESSOR SOFTWARE * Micro is an RCA 1802 * 512 bytes RAM * Program takes all but one byte which is used to designate current program version (5.1 as of launch) * 84 byte circular buffer to telemetry: must have LRS (Low Rate Science, =9.6 bits/sec downlink) to take data * Returns 144 bytes of data each second * Instrument's natural time period is 7.6 milliseconds: up to 6.0 msec for integration and 1.6 for data transfer and gratting step; Integrate first then step. * High Voltage overrides are provided for electronic failures * Cold Start mode is hardwired to provided for electronic failures * 18 analog engineering values are incorporated in data stream each Scan (4.333 sec) before data are read (`the Fidutial') * Full Scan or Mini-scan modes (the old `four position' is replaced with mini-scan mode * Phase 2 software (V6.1) is only slightly different from Phase 1 There is a write-up in the PDS archive materials COMMANDING See Functional Requirements for all parameters except those used for scan positions (summary on next page); use following pages for Version 5.1 changes to allow variable wavelength selection and mini-scan positioning. Pg 25 - Feb 7,91 KES LESSONS LEARNED 1) EUV oversampling at Venus and Earth * FPN was not in soon enough nor blocked sufficient counts for amount of sky that was sectored * Way underestimated the amount of `background', suspect: from Van Allen belts * Did get to internal saturation: not just a t/m rate problem 2) Good news and bad: All UVS N-channel lost due to solar sensor shut off 3) Lack of planning knowledge to interpret data: what happening when and additional geometry parameters 4) Lack of EDR training at LASP, disk space problems 5) Comet Austin problem 6) MRO to 24 problem 7) EUV hit during SP to ST 8) All tape record knowledge in the hands of S/C therefore no `ground truth' for sequence planning or playback knowledge by DMT >>? DMT Pg 25 - Feb 8,91 KES From: ZODIAC::SIMMONS "Karen Simmons at LASP/Colorado" 14-FEB-1991 16:31:07.08 To: @gll_team CC: Subj: SPICE geometry products To: Galileo UVS/EUV team From: Karen Simmons Date: Feb 14,91 Subject: SPICE geometry files We are creating geometry listings from SPICE kernel software for various link observations during Venus and Earth 1 encounters. We are placing these listings on a new directory: DISKH:[GLL_RAW.SPICE_OUTPUT] The file naming convention is as follows: linkname_RIMbeg_RIMend.dtimkey_LIS where linkname = the name one the link associated with this observation (as SYSCAN) RIMbeg = the beginning RIM time RIMend = the ending RIM time dtimkey = an abbreviation for time resolution presented in the file: mf = every minor frame (0.666 sec) mjf = at Major Frames (60.666 sec), or greater Someplace down the line we will be creating IDL Associate files and figuring out a better organization for these products. Suggestions are welcome. Attn: Charles W. Hord zodiac::barth pisces::mcclint zodiac::gthomas zodiac::stewart jplal2::alane issac::rwest zodiac::pryor looney::sandel zodiac::espo lrsp::ajello lrsp::edberg lrsp::ltamppari zodiac::taylor zodiac::simmons